search
Categories
Sponsors
VirtualMetric Hyper-V Monitoring, Hyper-V Reporting
Archive
Blogroll

Badges
MCSE
Community

Cozumpark Bilisim Portali
ASP.NET write access error on IIS7.5
Posted in Hosting & IIS7 | No Comment | 43,400 views | 08/11/2009 10:02

If you use domain users for IIS, you may get this write access error.

The current identity (VPOOL\iusr_yusufozturkinfo) does not have write access to ‘C:\Windows\Microsoft.NET\Framework64\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 (VPOOL\iusr_yusufozturkinfo) does not have write access to ‘C:\Windows\Microsoft.NET\Framework64\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 (VPOOL\iusr_yusufozturkinfo) does not have write access to ‘C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files’.]
System.Web.HttpRuntime.SetUpCodegenDirectory(CompilationSection compilationSection) +11336505
System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags) +356

[HttpException (0x80004005): The current identity (VPOOL\iusr_yusufozturkinfo) does not have write access to ‘C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files’.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +11301302
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +88
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +4338644

Solution: Create a new active directory user group named “IIS_IUSERS” in Users OU. Then join your iis users to this group. After that, adding that user group to local IIS_IUSRS group solves your problem.



Leave a Reply