This page has moved. You will be automatically redirected to its new location in 10 seconds. If you aren't forwarded to the new page, click here.

Search This Blog

Thursday, March 5, 2009

“The compiler failed with error code 128”

I received the same error  last week which was resolved after running a disk cleanup on the server, and logging off and logging in.


 

However, today this error would not go with the above mentioned steps, so I performed another search over how to resolve the issue and following are the main findings which I concluded and tried:


 

  • run the the aspnet_regiis.exe and it solved my problem. 
    C:\(your windows directory)\Microsoft.NET\Framework\(your version of .net framework)\aspnet_regiis.exe -i 
  • Go to C:\(your windows directory)\Microsoft.NET\Framework\(your version of .net framework)\Temporary ASP.NET Files and remove your virtual directory from here
  • Repair .NET framework


 

The above two solutions did not work; but finally I was able to resolve the error by:

  • Changing the IDENTITY of the Application Pool in which our virtual directory resides from "Network Service" to "Local System"


 

I have explained all the possible solutions of removing the error from the system just for your information. In our case the solution was changing identity of the application pool.


 

Here is a link from where I found out this solution:


 

http://social.msdn.microsoft.com/Forums/en-US/asmxandxml/thread/7878c90d-814d-48b6-9694-112cc4a39d12/


 

No comments:

Post a Comment