tags:

views:

87

answers:

2

Hi All,

I get the following error when overwriting my asp.net .dll sometimes on my web server. The server is running Windows 2008 and IIS7. The only way I can seem to resolve the issue is to restart IIS7 completely.

Compilation Error Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: The compiler failed with error code -1073741502.

Version Information: Microsoft .NET Framework Version:2.0.50727.4016; ASP.NET Version:2.0.50727.4016

If anyone can help then it would be appreciated.

A: 

This problem occurs when a third-party component is running in the W3wp.exe process that has attached a console to the process. The Vbc.exe compiler process and the Csc.exe compiler process then inherit this console. If the console uses a windowstation that does not contain a desktop named DEFAULT, this may cause the compiler processes, or any other process that is spawned from the W3wp.exe process that depends on the User32.dll file, not to start.

Pierreten
so that's the why, any pointers on a solution?
Sam Holder
What 3rd party component are you using that get referenced in the page request?
Pierreten
I am not using Visual Basic and when I googled this I got your exact response. This problem was linked to VB. I am not debugging or anything, literally overwriting the file. And Im not using any 3rd party components I don't think ...
webnoob
A: 

Same problem here. I run multiple websites, and one of them uses WebsitesScreenshot.com DLL. This uses Internet Explorer to make a screenshot of a website, and it seems that it doesn't close it properly, causing this error. Interestingly, one site being down should not cause other sites to go down, but it would seem like, randomly. All sites use their own AppPools. Also, few sites use ErrorSnitch service that may cause similar problem, but at least one other website which doesn't use any of these 3rd party DLLs was seen to crash like that. Obviously, doing IISRESET solves the issue.

Any ideas?

Dami