Comments
3 comments
-
Hi Mr D,
This sounds very similar to the last problem, where w3wp.exe exited because impersonation didn't seem to be working.
Whatever the answer is, it probably involves some changes to your application's web.config file. There may be a trust level setting that needs to be elevated. Sometimes introducing the profiler dll into your application invalidates the security because it's unmanaged code, so a trust level of at least Medium would be needed to get it working.
You may also want to try setting debug=true. This works through some security issues sometimes.
If this does work make sure you make a note of the original settings so you you can change things back and don't replicate the elevated priviliges to your production site! -
Brian,
I've got debug=true set, and am still having trouble, so it may be a problem with impersonation, as you suggested. Could you please send me a link to the other thread where this was dealt with so that I can look into this further?
Thanks!
Mr. D -
Add comment
Please sign in to leave a comment.
Has anyone else seen this before and/or do you know what steps need to be taken to resolve it? Any help would be appreciated.
Thanks,
Mr. D