posted 21 years ago
Thanks for reporting this. We have run into this error on occasion before, and still have not identified a cause. However, if this becomes more common we will start working with the vendor to find a solution.
We have not noticed that there are any ill effects from this, so hopefully you are back to working OK.
"JavaRanch, where the deer and the Certified play" - David O'Meara