Still hoping UO.NET user/developers will check to see if they are logging to see if anyone else has these UO.NET logs.
The site has a connection pooling license but pooling isn't activated in this application. Good recommendation on system.diagnostics/switches. I'll see if we can try it. Tweaks to web.config in a live site are avoided at all cost, and the possible performance hit of using tracing could also be an issue, but we gotta do what we gotta do. ..NET Reflector won't help in this case. The error doesn't seem to occur frequently. As a poster child for the "Clear Message Initiative", the text file doesn't provide any indication of the method or line (source/IL) in UO.NET where failure occurred, nor of the method in the client code which invoked UO.NET functionality. Thanks for nothing, Microsoft. But sincere thanks to you, Symeon! :) T > From: Symeon Breen > Are you using pooling ? > I have had problems because pooling uses > performancecounters and these can get corrupted in the > registry and have to be reset, the process also needs > permissions to access that part of the registry > > Also there is a configuration you can do to enable > logging within uniobjects > <system.diagnostics> > <switches> [snip] > Or dare i suggest .Net Reflector ;) _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
