“CS0016: Could not write to output file” error when starting an app in IIS 7

Question

I am running Windows 7, and am not usually a developer in this setting, and have recently built a WCF Rest Service in C#, that I\'m now trying to deploy to IIS just on my lo

Answer 1

For me the solution was a combination of the fixes described here. I had to give to the NETWORK_SERVICE account full control on

C:\Windows\Temp

and

C:\Windows\Microsoft.NET\Framework[related framework]\Temporary ASP.NET Files\

and also change the Application Pool Identity to NetworkService.

Also do not forget to restart the IIS after you give full control to NETWORK_SERVICE on the Temp folders

Answer 2

This KB resolved it for me, it appears that the temp file path was nonexistent in the OS environmental variables.

http://support.microsoft.com/kb/825791

Answer 3

I have permissions but I'm starting to get that error. "restart machine" works for me

Answer 4

There're 3 step to do:

1 - check if "Application Pool Identity" is NetworkService

2 - NETWORK_SERVICE account needs full control on:
    . C:\Windows\Temp
    . C:\Windows\Microsoft.NET\Framework[related framework]\Temporary ASP.NET Files\

3 - restart the IIS

Error Solved

You could also try re-running regiis. "%windir%\Microsoft.NET\Framework[related framework]\aspnet_regiis -i"

Answer 5

On Windows 8/Server 2012 there is no support for aspnet_regiis any more. I tried reinstall using windows features: fail. I tried reinstalling IIS: fail. I tried reinstall through WebPI: fail.

I solved the issue by setting the ACL's on the Windows Temp Directory.

Here is a powershell that does the job:

$dir = "C:\Windows\Temp"
$acl = get-acl -path $dir
$new = "IIS_IUSRS","Modify","ContainerInherit,ObjectInherit","None","Allow"
$accessRule = new-object System.Security.AccessControl.FileSystemAccessRule $new
$acl.SetAccessRule($accessRule)
$acl | Set-Acl $dir

Answer 6

Sounds like the account that the WCF service is running under does not have access to write to the "Temporary ASP.NET Files" directory.

You could also try re-running regiis.

%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -i

ASP.NET IIS Registration Tool (Aspnet_regiis.exe)