Question : Sharepoint Server Error in '/' Application

When I try to log on to Sharepoint I get the following error -

Server Error in '/' Application.
The current identity (OYSTER-TECH\spcontentpool) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: The current identity (OYSTER-TECH\spcontentpool) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): The current identity (OYSTER-TECH\spcontentpool) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.]
   System.Web.HttpRuntime.SetUpCodegenDirectory(CompilationSection compilationSection) +3570267
   System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags) +218

[HttpException (0x80004005): The current identity (OYSTER-TECH\spcontentpool) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3465427
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +69
   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +279


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


I can resolve this by going to the following locations and adding permission for the admin users accounts I have set up for Sharepoint.

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files
C:\WINDOWS\System 32\Log Files
C:\WINDOWS\Temp

After the correct permissions have been added, Sharepoint works as normal but after a while the problem comes back. All the changeswith permisions that I had made to the folders above are gone.

I also get the following warning in the event viewer -

Source : ASP.NET 2.0.50727.0
Event ID : 1309

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 18/04/2008 20:05:19
Event time (UTC): 18/04/2008 19:05:19
Event ID: 2f81d4433d1b49d2ac343e90c351900a
Event sequence: 1
Event occurrence: 1
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/1705862194/Root-74-128530191192531973
    Trust level:  
    Application Virtual Path: /
    Application Path: C:\Inetpub\wwwroot\wss\VirtualDirectories\80\
    Machine name: SHAREPOINT
 
Process information:
    Process ID: 640
    Process name: w3wp.exe
    Account name: OYSTER-TECH\spcontentpool
 
Exception information:
    Exception type: HttpException
    Exception message: The current identity (OYSTER-TECH\spcontentpool) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.
 
Request information:
    Request URL: https://sharepoint.oyster-tech.com:443/favicon.ico
    Request path: /favicon.ico
    User host address: 194.125.72.188
    User:  
    Is authenticated: False
    Authentication Type:  
    Thread account name: OYSTER-TECH\spcontentpool
 
Thread information:
    Thread ID: 17
    Thread account name: OYSTER-TECH\spcontentpool
    Is impersonating: False
    Stack trace:    at System.Web.HttpRuntime.SetUpCodegenDirectory(CompilationSection compilationSection)
   at System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags)
 
 
Custom event details:

For more information, see Help and Support Center at  


Any ideas?

Answer : Sharepoint Server Error in '/' Application

I found this link, that may can be used in your application.
It is not the same issue as you are having, but look at the principal behind everything given.
You may use the GPO settings they specify with the 'Impersonate a client after authentication' setting.
You may also try the commands use to the resolution of this particular issue.

Let me know...
-B