Forum Discussion
Mike_Janson_623
Jun 06, 2008Nimbostratus
Thanks for the suggestion--we'll try that, although as this does not seem to be consistently reproducible we have no way of verifying; we can only hope that by changing things in our test environment, and not witnessing the error over a week or more, it will also clean things up in production.
But this does seem like more of a workaround, than a fix; in the interest of explaining why this is happening, does firmware/Tcl seem like the most likely culprit or is there something else we may want to consider?