{"id":189,"date":"2006-02-10T09:30:25","date_gmt":"2006-02-10T13:30:25","guid":{"rendered":"http:\/\/www.soulhuntre.com\/items\/date\/2006\/02\/10\/solving-an-iis-security-issue\/"},"modified":"2006-02-10T09:30:25","modified_gmt":"2006-02-10T13:30:25","slug":"solving-an-iis-security-issue","status":"publish","type":"post","link":"http:\/\/legacyiamsenseiken.local\/2006\/02\/10\/solving-an-iis-security-issue\/","title":{"rendered":"Solving an IIS security issue…"},"content":{"rendered":"
<\/p>\n
I was installing some stuff for a client under ASP.NET<\/a> 2.0 and IIS in Windows Server 2003<\/a>. The installation was going fine though it is much more complicated than it needs to be. There is such a thing as an installer and a wizard and WordPress<\/a> can do a 5 minute install, come on people. Anyway, heres the security situation…<\/p>\n Sounds fine right? I thought so too… but no…<\/p>\n The current identity (IUSR_froo<\/i>) does not have write access to ‘C:WINDOWSMicrosoft.NETFrameworkv2.0.50727Temporary 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.<\/p><\/blockquote>\n\n