Hi magnus.kirkhaug,
Based on my experience, the issue should caused by the unhandled exception from web application running in the aspnet_wp.exe process. After Visual Studio is installed on a server, the default behavior when an unhandled exception occurs is to show an Exception dialog that requires user intervention to either start Just-In-Time debugging or ignore the exception.
This may be undesirable for unattended operation. To configure the server to no longer show a dialog when an unhandled exception occurs, use the registry editor to delete the following registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger
For the detailed information, please check the following link:
Just-In-Time Debugging
http://msdn2.microsoft.com/en-us/library/5hs4b7a6(vs.80).aspx
However, please understand the above workaround doesn?t fix the exception. It?s just a workaround to avoid the exception dialog. To fix the issue, you should make web applications to handle such exceptions. For example, you can add application level error event handler in the Global.asax file. For the detailed information, please refer to the following link:
How to: Handle Application-Level Errors
http://msdn2.microsoft.com/en-us/library/24395wz3(vs.80).aspx
Sincerely,
Benson Yu
Microsoft Online Community Support
Please remember to click ?Mark as Answer? on the post that helps you, and to click ?Unmark as Answer? if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.