For some reason, on all our drivers (edir, ad, jdbc, looback), driver
tracing will not start nor stop unless we restart the driver. It has
become quite annoying to restart the driver anytime we need to analyze a
driver trace. And again to restart the trace to get it to turn off. It
is like the driver won't read the misc tab unless the driver starting.
Anybody seen this before?

hollingsworthba's Profile:
View this thread: