IIS "Deny access to temporary directory" workaround

The blog program was deployed to a Aliyun Windows host today, and the following error occurred while accessing through the browser:

An error occurred while creating the Blogconfigurationsettings configuration section handler: Access to the temporary directory was denied. "IIS apppool\www.cnblogs.com", as it runs XmlSerializer, does not have sufficient privileges to access the temporary directory. The CodeDom will use the user account that this process uses for compiling, so if the user does not have access to the system temp directory, it will not compile. Use the Path.gettemppath () API to locate the temporary directory location.

Access to the Temp directory is denied. Identity ' IIS apppool\www.cnblogs.com ' under which XmlSerializer is running does do not have sufficient to access The temp directory. CodeDom would use the ' user account ' the ' process is ' using to do ' compilation, so if the user doesnt have access to system Temp directory, you are not is able to compile. Use Path.gettemppath () APIs to find out the temp directory location.

CS0016: Failed to write to output file ' c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary asp.net files\root\946055b8\92eead15\ App_global.asax.qakaesxx.dll "--" Deny access. ”

The issue is initially thought to be the "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary asp.net Files" folder permissions, but how to set this permission will not solve the problem.

The problem is resolved later when the load user profile is set to true in the application pool settings.

More Wonderful content: http://www.bianceng.cnhttp://www.bianceng.cn/webkf/aspx/