bc31019 unable to write to output file

This issue comes when the application pool user is not having sufficient permission to read and write on asp.net temporary folder.

Solution:
1. Goto the application pool and right click on it, and select the identity tab.By default network service account is configured.Some time application will not work due to not sufficient permission with Network service account.So click on radio button configurable and give any other user name and password and apply
2.This user that you have configured in application pool should be member of iis_WPG.

Updating the value of default URL in TeamSessions plug-in preferences for deployment

Administrators would want to update the default URL to point it to their Team Sessions server for easy deployment. Take following steps to update the URL.

1. Download the plug-in install site from http://team.instant-tech.com/download (if you do not already have the install site) using your login credentials

2. Unzip the install site

3. After unzipping the install site you should see the ‘com.ibm.collaboration.realtime.instant.team._ST8_1.0.xx.jar’ file in ‘\plugins’ folder.

4. ‘com.ibm.collaboration.realtime.instant.team._ST8_1.0.xx.jar’ is a standard zip file.

5. You will need to extract this jar file using any popular zipping application like WinZip or WinRar.

6. After extracting the jar file you should see the ‘settings.properties’ file in ‘com.ibm.collaboration.realtime.instant.team._ST8_1.0.xx\com\ibm\collaboration\realtime\instant\team\settings’ folder.

7. Open the ‘settings.properties’ file using any text editor.

8. Update the value for the property: SERVER_URL to point it to your Instant Team Sessions server.

9. Format of the value should be: http\://your server FQDN/itsessions.nsf/ChatPlaceID?ReadViewEntries&Count\=2000

10. Save your changes and close the properties file.

11. Next use your zipping application to create back the zip file from the folder.

12. Rename the created zip file ‘com.ibm.collaboration.realtime.instant.team._ST8_1.0.xx.zip’ to: com.ibm.collaboration.realtime.instant.team._ST8_1.0.xx.jar

Now the updated plug-in jar can be pushed to Sametime clients using the install site. We used WinRar while following above-mentioned steps.

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_regiis –ir
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/