Thursday, July 2, 2009

Compiler Error Message: BC31019: Unable to write to output file 'c:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET

After installing Instant Archive Viewer and browsing the site you may encounter a Compiler Error message: Compiler Error Message: BC31019: Unable to write to output file 'c:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Here are some possible causes for the error and solutions for each:
1. Cause:
If you run Index Server (Cisvc.exe), then Index Server may rescan the Temporary ASP.NET Files directory while it requests a Microsoft ASP.NET page.

Solution:
Disable the Microsoft Index Services for the temp folder:

http://support.microsoft.com/default.aspx?scid=kb;en-us;329065#appliesto


2. Cause: Temp Environment variable issue

Solution:
Change your temp folder directory by clicking on advanced tab from
system settings and environment variables.
http://geekswithblogs.net/ranganh/archive/2005/05/13/39582.aspx

3. Cause:
IIS 6.0 and ASP.NET are installed on the server before the server is promoted to a domain controller.
Solution:
1. cDrive:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
2. Add the appropriate permissions to the Network Service group for the Temporary ASP.NET Files folder. To do this, type the following line, and then press ENTER: aspnet_regiisir
http://support.microsoft.com/kb/823379

4. Cause:
A web site which is set (in the web.config file) to impersonate a user which does not have access to the logged in user's temp directory cannot be published

Solution:
Remove the impersonation identity from web.config, and either add it back manually upon deployment, or use Web Deployment Projects to automatically add back the in the impersonation identity to web.config during publishing. Note that on the server you will also need to grant read/write permissions to the impersonated identity to the Temporary ASP.NET Files folder.

https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=341470

5. Cause:
something strange with your TEMP environment variable?
Solution:
Try running the application as an administrator by right clicking
on ITIMArchiveviews/run as..:

http://social.msdn.microsoft.com/forums/en-US/windowsgeneraldevelopmentissues/thread/a25c607a-fc7b-4fef-9978-fd9604052bd5/

No comments: