Event ID: 503 Source: Windows Server Update

Event ID/Source search

Keyword search

Example: Windows cannot unload your registry file

EvLog 3.0 – Monitor an unlimited number of servers with $49/year

With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case.
New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers.

Event ID: 503 Source: Windows Server Update

Source: Windows Server Update

Type: Error

Description:
The Windows Server Update Services Server experienced an error while attempting to write to the log file.
1696.37
System.UnauthorizedAccessException: Access to the path "C:\Program Files\Update Services\LogFiles\SoftwareDistribution.log" is denied.
   at System.IO.__Error.WinIOError(Int32 errorCode String str)
   at System.IO.FileStream..ctor(String path FileMode mode FileAccess access FileShare share Int32 bufferSize Boolean useAsync String msgPath Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path FileMode mode FileAccess access FileShare share)
   at Microsoft.UpdateServices.Internal.TraceLogger.OpenFile()
   at Microsoft.UpdateServices.Internal.TraceLogger.WriteLine(String message).

English: Request a translation of the event description in plain English.

Comments:
Andy Helsby
In my case, resetting the permissions on the file itself did not help as when the file gets renamed to be ".old", the new version does not have permissions to be created. It is therefore critical that the permissions be set on the folder.
Click if the comment is good!

^{x
8}

Danny McGrath
I received this error after a clean install of WSUS because there was no ownership or permissions on the file: C:\Program Files\Update Services\LogFiles\SoftwareDistribution.log. I took ownership of the file with the currently logged in user, set it to inherit permissions from the parent folder and the problem was solved.
Click if the comment is good!

^{x
14}

Private comment: Subscribers only. See example of private comment

Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...

Feedback: Send comments or solutions - Notify me when updated

Printer friendly