mattguil
asked on
WSUS error: Compiler Error Message: CS0016: Could not write to output file...access is denied
Hello, all-
I have an issue regarding a WSUS installation that has me completely unnerved. The error message is given after completing a WSUS install, then accessing the home administration page. WSUS was up and running smoothly for over one year, then I noticed this and have been unable to troubleshoot it effectively.
I've completely removed WSUS and all downloaded components to start from scratch...error remains constant.
Here is the error in its entirety:
Server Error in '/WSUSAdmin' Application.
-------------------------- ---------- ---------- ---------- ---------- ---------- ----
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS0016: Could not write to output file 'c:\WINDOWS\Microsoft.NET\ Framework\ v1.1.4322\ Temporary ASP.NET Files\wsusadmin\f88e1ebf\a e1e5c8d\is olbzpj.dll ' -- 'Access is denied. '
Show Detailed Compiler Output:
c:\windows\system32\inetsr v> "c:\windows\microsoft.net\ framework\ v1.1.4322\ csc.exe" /t:library /utf8output /R:"c:\windows\microsoft.n et\framewo rk\v1.1.43 22\mscorli b.dll" /R:"c:\windows\microsoft.n et\framewo rk\v1.1.43 22\tempora ry asp.net files\wsusadmin\f88e1ebf\a e1e5c8d\as sembly\dl2 \0afdce00\ 00f74862_2 f67c501\ad minstrings .dll" /R:"c:\windows\assembly\ga c\system.e nterprises ervices\1. 0.5000.0__ b03f5f7f11 d50a3a\sys tem.enterp riseservic es.dll" /R:"c:\windows\assembly\ga c\system.d ata\1.0.50 00.0__b77a 5c561934e0 89\system. data.dll" /R:"c:\windows\assembly\ga c\system.w eb.mobile\ 1.0.5000.0 __b03f5f7f 11d50a3a\s ystem.web. mobile.dll " /R:"c:\windows\assembly\ga c\system.d rawing\1.0 .5000.0__b 03f5f7f11d 50a3a\syst em.drawing .dll" /R:"c:\windows\microsoft.n et\framewo rk\v1.1.43 22\tempora ry asp.net files\wsusadmin\f88e1ebf\a e1e5c8d\as sembly\dl2 \235055fe\ 00819851_2 f67c501\ad mincontrol s.dll" /R:"c:\windows\assembly\ga c\system.x ml\1.0.500 0.0__b77a5 c561934e08 9\system.x ml.dll" /R:"c:\windows\assembly\ga c\system.w eb.service s\1.0.5000 .0__b03f5f 7f11d50a3a \system.we b.services .dll" /R:"c:\windows\microsoft.n et\framewo rk\v1.1.43 22\tempora ry asp.net files\wsusadmin\f88e1ebf\a e1e5c8d\as sembly\dl2 \01e9e814\ 0016535c_2 f67c501\ad ministrati on.dll" /R:"c:\windows\assembly\ga c\system\1 .0.5000.0_ _b77a5c561 934e089\sy stem.dll" /R:"c:\windows\assembly\ga c\system.w eb\1.0.500 0.0__b03f5 f7f11d50a3 a\system.w eb.dll" /out:"C:\WINDOWS\Microsoft .NET\Frame work\v1.1. 4322\Tempo rary ASP.NET Files\wsusadmin\f88e1ebf\a e1e5c8d\is olbzpj.dll " /D:DEBUG /debug+ /optimize- /warnaserror /w:1 "C:\WINDOWS\Microsoft.NET\ Framework\ v1.1.4322\ Temporary ASP.NET Files\wsusadmin\f88e1ebf\a e1e5c8d\is olbzpj.0.c s"
Microsoft (R) Visual C# .NET Compiler version 7.10.6310.4
for Microsoft (R) .NET Framework version 1.1.4322
Copyright (C) Microsoft Corporation 2001-2002. All rights reserved.
error CS0016: Could not write to output file 'c:\WINDOWS\Microsoft.NET\ Framework\ v1.1.4322\ Temporary ASP.NET Files\wsusadmin\f88e1ebf\a e1e5c8d\is olbzpj.dll ' -- 'Access is denied. '
******
Please note that I have verified file access permissions for the following:
1. %systemroot%\temp, %systemroot%\tmp
2. %systemroot%\WINDOWS\Micro soft.NET, including all child objects
I can't believe it is a file permissions issue as the error states because I've done the following, simply to test:
1. I've ensured localmachine\aspnet account has full permissions to folders and child objects
2. I've added localmachine\aspnet account to the localmachine\administrator s group
3. I've done steps 1 and 2 for the network service account
4. Effective permissions shows these accounts to have full control.
Am I missing something?
The way things have gone lately, I'm seriously considering getting away from Microsoft's instability.
Thanks,
Matt
I have an issue regarding a WSUS installation that has me completely unnerved. The error message is given after completing a WSUS install, then accessing the home administration page. WSUS was up and running smoothly for over one year, then I noticed this and have been unable to troubleshoot it effectively.
I've completely removed WSUS and all downloaded components to start from scratch...error remains constant.
Here is the error in its entirety:
Server Error in '/WSUSAdmin' Application.
--------------------------
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS0016: Could not write to output file 'c:\WINDOWS\Microsoft.NET\
Show Detailed Compiler Output:
c:\windows\system32\inetsr
Microsoft (R) Visual C# .NET Compiler version 7.10.6310.4
for Microsoft (R) .NET Framework version 1.1.4322
Copyright (C) Microsoft Corporation 2001-2002. All rights reserved.
error CS0016: Could not write to output file 'c:\WINDOWS\Microsoft.NET\
******
Please note that I have verified file access permissions for the following:
1. %systemroot%\temp, %systemroot%\tmp
2. %systemroot%\WINDOWS\Micro
I can't believe it is a file permissions issue as the error states because I've done the following, simply to test:
1. I've ensured localmachine\aspnet account has full permissions to folders and child objects
2. I've added localmachine\aspnet account to the localmachine\administrator
3. I've done steps 1 and 2 for the network service account
4. Effective permissions shows these accounts to have full control.
Am I missing something?
The way things have gone lately, I'm seriously considering getting away from Microsoft's instability.
Thanks,
Matt
ASKER
Here is the solution you posted:
-----
Workaround
You see this error if you have previously run IISLockdown on this machine.
If so, please check the permissions on C:\WINNT\Microsoft.NET\Fra mework\v1. 1.4322\cvt res.exe. Depending on the options used, IISLockdown many have denied ASP.NET access to this file.
ASP.NET requires Read & Execute permissions on this file.
If you review my submitted question...this has been done. Tha
-----
I have already followed these steps using this article. No dice.
-----
Workaround
You see this error if you have previously run IISLockdown on this machine.
If so, please check the permissions on C:\WINNT\Microsoft.NET\Fra
ASP.NET requires Read & Execute permissions on this file.
If you review my submitted question...this has been done. Tha
-----
I have already followed these steps using this article. No dice.
oops...sorry...I saw the Everyone part, but glanced over the asp.net part you posted.
And the OS is ??
And the OS is ??
ASKER
Server 2003 standard.
Most I can do is point you in a general direction...since I'm not there:
http://technet2.microsoft.com/WindowsServer/en/Library/298d6204-88a0-4a11-a4b9-a4adb4b3ca3a1033.mspx
and basically: http://www.google.com/search?hl=en&q=WSUS+asp.net
I wish I could be more help...
You said WSUS was up and running smooth for over a year, but right before that you say you get the error during an install. What happened? Was the server's role possibly changed (like running dcpromo or similar) or did you install SP1 or what? Just curious what might have changed after it'd been running fine for so long.
http://technet2.microsoft.com/WindowsServer/en/Library/298d6204-88a0-4a11-a4b9-a4adb4b3ca3a1033.mspx
and basically: http://www.google.com/search?hl=en&q=WSUS+asp.net
I wish I could be more help...
You said WSUS was up and running smooth for over a year, but right before that you say you get the error during an install. What happened? Was the server's role possibly changed (like running dcpromo or similar) or did you install SP1 or what? Just curious what might have changed after it'd been running fine for so long.
ASKER
That's the mystery. I can't pinpoint any major changes made...it is a project server that is running WSUS and Spysweeper Enterprise. I had an ipconflict that I resolved, but other than that...nothing major.
While troubleshooting, I rolled back all OS updates, including .Net Framework updates back to version 1.4...still no dice.
Very frustrating to say the least. I believe I'll wind up backing up the Spysweeper install, and reformatting the server. Tough to swallow, especially with an already overflowing workload.
Ah, the life of an admin.
Thanks for the help. I appreciate it, and will follow the links you sent. More than likely, I've already checked into them as I've completely exhausted my googles.
Thanks again,
matt
While troubleshooting, I rolled back all OS updates, including .Net Framework updates back to version 1.4...still no dice.
Very frustrating to say the least. I believe I'll wind up backing up the Spysweeper install, and reformatting the server. Tough to swallow, especially with an already overflowing workload.
Ah, the life of an admin.
Thanks for the help. I appreciate it, and will follow the links you sent. More than likely, I've already checked into them as I've completely exhausted my googles.
Thanks again,
matt
Have you tried reapplying updates at this point like SP1 and .NET framework 2.0 ?
I'm curious especially if applying .NET framework would help.
I'm curious especially if applying .NET framework would help.
ASKER
I'll do that now. sp1 is installed, and was from the beginning (pre-good-functioning-wsus -install).
I never removed sp1.
I'll let you know how reapplying the updates goes.
I never removed sp1.
I'll let you know how reapplying the updates goes.
Check the permissions on the temp path that the *system* environment variables "Temp" and "Tmp" point to.
Set the necessary permissions as described here:
PRB: CS0013 or CS0016 Compilation Errors in ASP.NET Web Applications
http://support.microsoft.com/?kbid=825791
Set the necessary permissions as described here:
PRB: CS0013 or CS0016 Compilation Errors in ASP.NET Web Applications
http://support.microsoft.com/?kbid=825791
ASKER
Already tried that. No dice.
Thanks for the input.
Thanks for the input.
ASKER
Okay, updates complete with the same error result.
I'm wondering if this may be an issue concerning the Microsoft SQL Desktop Engine.
However, I'm having trouble finding documentation on how/when that engine is actually used. Could a misconfigured or non functioning MS SQL Desktop Engine be the culprit involved in the admin page errors?
I'm wondering if this may be an issue concerning the Microsoft SQL Desktop Engine.
However, I'm having trouble finding documentation on how/when that engine is actually used. Could a misconfigured or non functioning MS SQL Desktop Engine be the culprit involved in the admin page errors?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Same Problem, Same steps, Same rate of dandruff production - As a footnote did you exclude certain system files/folder from whatever Anti Virus file level scanner you use/d ?
ASKER
Same result.