Discussion:
WSUS won't download updates
(too old to reply)
Brian Rottman
2005-08-30 13:44:11 UTC
Permalink
New installation of WSUS wn't download updates. It synchronized just fine
but just sits at "Downloading 0.00 MB of 11,693.96 MB"

Any ideas?
Arek Iskra [MVP]
2005-08-30 14:31:13 UTC
Permalink
Post by Brian Rottman
New installation of WSUS wn't download updates. It synchronized just fine
but just sits at "Downloading 0.00 MB of 11,693.96 MB"
Any ideas?
Have you checked WindowsUpdate.log in Windows folder?
--
Arek Iskra
MVP for Windows Server - Software Distribution
Brian Rottman
2005-08-30 14:50:11 UTC
Permalink
I don't see anything wrong here...

2005-08-30 10:37:00 1456 196c Misc =========== Logging initialized
(build: 5.8.0.2469, tz: -0400) ===========
2005-08-30 10:37:00 1456 196c Misc = Process:
C:\WINDOWS\System32\svchost.exe
2005-08-30 10:37:00 1456 196c Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2005-08-30 10:37:00 1456 196c Service *************
2005-08-30 10:37:00 1456 196c Service ** START ** Service: Service startup
2005-08-30 10:37:00 1456 196c Service *********
2005-08-30 10:37:00 1456 196c Agent * WU client version 5.8.0.2469
2005-08-30 10:37:00 1456 196c Agent * SusClientId =
'39650416-6c25-46fb-bd58-43bc34c93c6f'
2005-08-30 10:37:00 1456 196c Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2005-08-30 10:37:00 1456 196c Agent * Access type: No proxy
2005-08-30 10:37:00 1456 196c Agent * Network state: Connected
2005-08-30 10:37:45 1456 196c Agent *********** Agent: Initializing
Windows Update Agent ***********
2005-08-30 10:37:45 1456 196c Agent *********** Agent: Initializing
global settings cache ***********
2005-08-30 10:37:45 1456 196c Agent * WSUS server: <NULL>
2005-08-30 10:37:45 1456 196c Agent * WSUS status server: <NULL>
2005-08-30 10:37:45 1456 196c Agent * Target group: (Unassigned
Computers)
2005-08-30 10:37:45 1456 196c Agent * Windows Update access disabled: No
2005-08-30 10:37:45 1456 196c DnldMgr Download manager restoring 0
downloads
2005-08-30 10:37:45 1456 196c AU ########### AU: Initializing Automatic
Updates ###########
2005-08-30 10:37:45 1456 196c AU # Approval type: Pre-install notify
(User preference)
2005-08-30 10:37:45 1456 196c AU # Auto-install minor updates: No (User
preference)
2005-08-30 10:37:45 1456 196c AU AU setting pending client directive to
'Install Approval'
2005-08-30 10:37:45 1456 196c Report *********** Report: Initializing
static reporting data ***********
2005-08-30 10:37:45 1456 196c Report * OS Version = 5.2.3790.1.0.131346
2005-08-30 10:37:46 1456 196c Report * Computer Brand = Intel
2005-08-30 10:37:46 1456 196c Report * Computer Model = SWV25
2005-08-30 10:37:46 1456 196c Report * Bios Revision =
SWV25.86B.0190.P16.0310281020
2005-08-30 10:37:46 1456 196c Report * Bios Name = SWV25 v10.00
2005-08-30 10:37:46 1456 196c Report * Bios Release Date =
2003-10-28T00:00:00
2005-08-30 10:37:46 1456 196c Report * Locale ID = 1033
2005-08-30 10:37:46 1456 196c AU #############
2005-08-30 10:37:46 1456 196c AU ## START ## AU: Search for updates
2005-08-30 10:37:46 1456 196c AU #########
2005-08-30 10:37:46 1456 196c AU <<## SUBMITTED ## AU: Search for updates
[CallId = {7C7D84E9-A8EE-4E65-8DCB-B5C476E4E269}]
2005-08-30 10:37:46 1456 5dc Agent *************
2005-08-30 10:37:46 1456 5dc Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-30 10:37:46 1456 5dc Agent *********
2005-08-30 10:37:47 1456 5dc Agent * Added update
{F89C6A2F-F6C2-4B27-8C93-1561EE55B715}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{745BEB74-FCB0-4323-ADF3-470A9AF3C615}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{A9711EF4-689B-4833-975B-0FBF38D7236A}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{9766EE68-0156-4898-9BB8-D1BC08E0F4B1}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{BA825FF2-7B5B-411A-B066-B0212DC66425}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{43CFE95C-26ED-48BC-957B-675AEC692DF0}.101 to search result
2005-08-30 10:37:47 1456 5dc Agent * Found 6 updates and 10 categories
in search
2005-08-30 10:37:47 1456 5dc Agent *********
2005-08-30 10:37:47 1456 5dc Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-30 10:37:47 1456 5dc Agent *************
2005-08-30 10:37:47 1456 1ad0 AU >>## RESUMED ## AU: Search for updates
[CallId = {7C7D84E9-A8EE-4E65-8DCB-B5C476E4E269}]
2005-08-30 10:37:47 1456 1ad0 AU # 6 updates detected
2005-08-30 10:37:47 1456 1ad0 AU #########
2005-08-30 10:37:47 1456 1ad0 AU ## END ## AU: Search for updates
[CallId = {7C7D84E9-A8EE-4E65-8DCB-B5C476E4E269}]
2005-08-30 10:37:47 1456 1ad0 AU #############
2005-08-30 10:37:51 1456 1ad0 Report REPORT EVENT:
{BF3D5B50-4B29-4414-82F5-8D58DA04857C} 2005-08-30
10:37:45-0400 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Reboot completed.
2005-08-30 10:37:59 1456 196c AU AU found 1 sessions to launch client into
2005-08-30 10:37:59 1456 196c AU Launched new AU client for directive
'Install Approval', session id = 0x0
2005-08-30 10:38:00 7936 1240 Misc =========== Logging initialized
(build: 5.8.0.2469, tz: -0400) ===========
2005-08-30 10:38:00 7936 1240 Misc = Process:
C:\WINDOWS\system32\wuauclt.exe
2005-08-30 10:38:00 7936 1240 AUClnt Launched Client UI process
2005-08-30 10:38:00 7936 1240 AUClnt AU client got new directive =
'Install Approval', serviceId = {9482F4B4-E343-43B6-B170-9A65BC822C77},
return = 0x00000000
2005-08-30 10:38:00 7936 1240 AUClnt AU client creating default WU/WSUS UI
plugin
2005-08-30 10:38:00 1456 1610 AU AU setting client response for sessionId
0x0 to 'Pending'





On Tue, 30 Aug 2005 10:31:13 -0400, Arek Iskra [MVP]
Post by Arek Iskra [MVP]
Post by Brian Rottman
New installation of WSUS wn't download updates. It synchronized just
fine but just sits at "Downloading 0.00 MB of 11,693.96 MB"
Any ideas?
Have you checked WindowsUpdate.log in Windows folder?
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Arek Iskra [MVP]
2005-08-30 15:02:58 UTC
Permalink
Post by Brian Rottman
I don't see anything wrong here...
2005-08-30 10:37:00 1456 196c Misc =========== Logging initialized
(build: 5.8.0.2469, tz: -0400) ===========
C:\WINDOWS\System32\svchost.exe
C:\WINDOWS\system32\wuaueng.dll
2005-08-30 10:37:00 1456 196c Service *************
2005-08-30 10:37:00 1456 196c Service ** START ** Service: Service
startup
2005-08-30 10:37:00 1456 196c Service *********
2005-08-30 10:37:00 1456 196c Agent * WU client version 5.8.0.2469
2005-08-30 10:37:00 1456 196c Agent * SusClientId =
'39650416-6c25-46fb-bd58-43bc34c93c6f'
C:\WINDOWS\SoftwareDistribution
2005-08-30 10:37:00 1456 196c Agent * Access type: No proxy
2005-08-30 10:37:00 1456 196c Agent * Network state: Connected
2005-08-30 10:37:45 1456 196c Agent *********** Agent: Initializing
Windows Update Agent ***********
2005-08-30 10:37:45 1456 196c Agent *********** Agent: Initializing
global settings cache ***********
2005-08-30 10:37:45 1456 196c Agent * WSUS server: <NULL>
2005-08-30 10:37:45 1456 196c Agent * WSUS status server: <NULL>
2005-08-30 10:37:45 1456 196c Agent * Target group: (Unassigned
Computers)
2005-08-30 10:37:45 1456 196c Agent * Windows Update access disabled: No
2005-08-30 10:37:45 1456 196c DnldMgr Download manager restoring 0
downloads
2005-08-30 10:37:45 1456 196c AU ########### AU: Initializing Automatic
Updates ###########
2005-08-30 10:37:45 1456 196c AU # Approval type: Pre-install notify
(User preference)
2005-08-30 10:37:45 1456 196c AU # Auto-install minor updates: No (User
preference)
2005-08-30 10:37:45 1456 196c AU AU setting pending client directive to
'Install Approval'
2005-08-30 10:37:45 1456 196c Report *********** Report: Initializing
static reporting data ***********
2005-08-30 10:37:45 1456 196c Report * OS Version = 5.2.3790.1.0.131346
2005-08-30 10:37:46 1456 196c Report * Computer Brand = Intel
2005-08-30 10:37:46 1456 196c Report * Computer Model = SWV25
2005-08-30 10:37:46 1456 196c Report * Bios Revision =
SWV25.86B.0190.P16.0310281020
2005-08-30 10:37:46 1456 196c Report * Bios Name = SWV25 v10.00
2005-08-30 10:37:46 1456 196c Report * Bios Release Date =
2003-10-28T00:00:00
2005-08-30 10:37:46 1456 196c Report * Locale ID = 1033
2005-08-30 10:37:46 1456 196c AU #############
2005-08-30 10:37:46 1456 196c AU ## START ## AU: Search for updates
2005-08-30 10:37:46 1456 196c AU #########
2005-08-30 10:37:46 1456 196c AU <<## SUBMITTED ## AU: Search for updates
[CallId = {7C7D84E9-A8EE-4E65-8DCB-B5C476E4E269}]
2005-08-30 10:37:46 1456 5dc Agent *************
2005-08-30 10:37:46 1456 5dc Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-30 10:37:46 1456 5dc Agent *********
2005-08-30 10:37:47 1456 5dc Agent * Added update
{F89C6A2F-F6C2-4B27-8C93-1561EE55B715}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{745BEB74-FCB0-4323-ADF3-470A9AF3C615}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{A9711EF4-689B-4833-975B-0FBF38D7236A}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{9766EE68-0156-4898-9BB8-D1BC08E0F4B1}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{BA825FF2-7B5B-411A-B066-B0212DC66425}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{43CFE95C-26ED-48BC-957B-675AEC692DF0}.101 to search result
2005-08-30 10:37:47 1456 5dc Agent * Found 6 updates and 10 categories
in search
2005-08-30 10:37:47 1456 5dc Agent *********
2005-08-30 10:37:47 1456 5dc Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-30 10:37:47 1456 5dc Agent *************
2005-08-30 10:37:47 1456 1ad0 AU >>## RESUMED ## AU: Search for updates
[CallId = {7C7D84E9-A8EE-4E65-8DCB-B5C476E4E269}]
2005-08-30 10:37:47 1456 1ad0 AU # 6 updates detected
2005-08-30 10:37:47 1456 1ad0 AU #########
2005-08-30 10:37:47 1456 1ad0 AU ## END ## AU: Search for updates
[CallId = {7C7D84E9-A8EE-4E65-8DCB-B5C476E4E269}]
2005-08-30 10:37:47 1456 1ad0 AU #############
{BF3D5B50-4B29-4414-82F5-8D58DA04857C} 2005-08-30 10:37:45-0400 1 202 102
{00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success
Content Install Reboot completed.
2005-08-30 10:37:59 1456 196c AU AU found 1 sessions to launch client into
2005-08-30 10:37:59 1456 196c AU Launched new AU client for directive
'Install Approval', session id = 0x0
2005-08-30 10:38:00 7936 1240 Misc =========== Logging initialized
(build: 5.8.0.2469, tz: -0400) ===========
C:\WINDOWS\system32\wuauclt.exe
2005-08-30 10:38:00 7936 1240 AUClnt Launched Client UI process
2005-08-30 10:38:00 7936 1240 AUClnt AU client got new directive =
'Install Approval', serviceId = {9482F4B4-E343-43B6-B170-9A65BC822C77},
return = 0x00000000
2005-08-30 10:38:00 7936 1240 AUClnt AU client creating default WU/WSUS UI
plugin
2005-08-30 10:38:00 1456 1610 AU AU setting client response for sessionId
0x0 to 'Pending'
On Tue, 30 Aug 2005 10:31:13 -0400, Arek Iskra [MVP]
Post by Arek Iskra [MVP]
Post by Brian Rottman
New installation of WSUS wn't download updates. It synchronized just
fine but just sits at "Downloading 0.00 MB of 11,693.96 MB"
Any ideas?
Have you checked WindowsUpdate.log in Windows folder?
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Are you using any proxy to connect to Internet? If you are, it might be that
because of proxy cache the status is not reflected accurately (e.g. it will
change when the full patch is downloaded). I have experienced it here, where
we use hardware device for proxying Internet requests.
--
Arek Iskra
MVP for Windows Server - Software Distribution
Brian Rottman
2005-08-30 15:17:57 UTC
Permalink
We are not using a proxy server for our internet connection. We do have a
Watchguard Firebox III though... would that make any difference?
Post by Arek Iskra [MVP]
Are you using any proxy to connect to Internet? If you are, it might be
that because of proxy cache the status is not reflected accurately (e.g.
it will change when the full patch is downloaded). I have experienced it
here, where we use hardware device for proxying Internet requests.
Lawrence Garvin
2005-08-30 17:10:47 UTC
Permalink
Maybe...... what's in the Event Logs?

Also, lacking anything in the Event Logs (doubtful), also check:
%PROGRAMFILES%\Update Services\logfiles\SoftwareDistribution.log
Post by Brian Rottman
We are not using a proxy server for our internet connection. We do have a
Watchguard Firebox III though... would that make any difference?
Post by Arek Iskra [MVP]
Are you using any proxy to connect to Internet? If you are, it might be
that because of proxy cache the status is not reflected accurately (e.g.
it will change when the full patch is downloaded). I have experienced it
here, where we use hardware device for proxying Internet requests.
Brian Rottman
2005-08-31 14:03:55 UTC
Permalink
Looking through that log I see a bunch of this:

File WindowsXP-KB890047-X86-ELL.exe: ActualState: 10; Step: AddFile;
Message: System.UnauthorizedAccessException: Access is denied.

Any idea?
Lawrence Garvin
2005-08-30 17:09:46 UTC
Permalink
Arek... not meaning any disrespect, but since you're flying that
MVP-Software Distribution flag on your sig, perhaps you could take some time
to update your /SUS/ skills to /WSUS/ before offering solutions - especially
solutions that are not only incorrect, but actually point the poster in the
opposite direction of the problem.

When a WSUS /server/ doesn't download updates... the absolutely incorrect
place to be looking is in a client-side logfile. See my post to Brian,
describing the correct diagnostics, and most likely cause(s) of his very
common problem.

Furthermore, when provided with this client-side log file.... did you
totally miss the fact that the /client/ isn't even connecting to the WSUS
server, and isn't even /configured/ to connect to the WSUS server -- but
did /successfully/ connect to WindowsUpdate, and download and install a half
dozen updates, and then was restarted?

Or that this WindowsUpdate.log file is from a Windows XP SP1 system and
could not possibly have even come from the /SERVER/?
Post by Arek Iskra [MVP]
Post by Brian Rottman
On Tue, 30 Aug 2005 10:31:13 -0400, Arek Iskra [MVP]
Post by Arek Iskra [MVP]
Post by Brian Rottman
New installation of WSUS wn't download updates. It synchronized just
fine but just sits at "Downloading 0.00 MB of 11,693.96 MB"
Any ideas?
Have you checked WindowsUpdate.log in Windows folder?
Are you using any proxy to connect to Internet? If you are, it might be
that because of proxy cache the status is not reflected accurately (e.g.
it will change when the full patch is downloaded). I have experienced it
here, where we use hardware device for proxying Internet requests.
--
Arek Iskra
MVP for Windows Server - Software Distribution
Arek Iskra [MVP]
2005-08-31 14:59:46 UTC
Permalink
Post by Lawrence Garvin
Arek... not meaning any disrespect, but since you're flying that
MVP-Software Distribution flag on your sig, perhaps you could take some
time to update your /SUS/ skills to /WSUS/ before offering solutions -
especially solutions that are not only incorrect, but actually point the
poster in the opposite direction of the problem.
No offence taken. However, I think you are jumping to your guns too fast.
Explanation below.
Post by Lawrence Garvin
When a WSUS /server/ doesn't download updates... the absolutely incorrect
place to be looking is in a client-side logfile. See my post to Brian,
describing the correct diagnostics, and most likely cause(s) of his very
common problem.
Maybe I was not clear enough, but I meant the log file from _server_ side
(apologies Brian).
Post by Lawrence Garvin
Furthermore, when provided with this client-side log file.... did you
totally miss the fact that the /client/ isn't even connecting to the WSUS
server, and isn't even /configured/ to connect to the WSUS server -- but
did /successfully/ connect to WindowsUpdate, and download and install a
half dozen updates, and then was restarted?
Exactly what I wanted to verify. If it is able to connect to WU and download
updates, there is no connectivity problem. Perhaps I could ask to check if
Brian can connect to Windows Update portal.

Do you find it to be totally irrelevant, Lawrence?
Post by Lawrence Garvin
Or that this WindowsUpdate.log file is from a Windows XP SP1 system and
could not possibly have even come from the /SERVER/?
It's good when more than one pair of eyes are looking into the problem. I
missed that one.

Peace my friend.
--
Arek Iskra
MVP for Windows Server - Software Distribution
Lawrence Garvin
2005-08-31 15:15:50 UTC
Permalink
Post by Arek Iskra [MVP]
Post by Lawrence Garvin
Arek... not meaning any disrespect, but since you're flying that
MVP-Software Distribution flag on your sig, perhaps you could take some
time to update your /SUS/ skills to /WSUS/ before offering solutions -
especially solutions that are not only incorrect, but actually point the
poster in the opposite direction of the problem.
No offence taken. However, I think you are jumping to your guns too fast.
Explanation below.
Post by Lawrence Garvin
When a WSUS /server/ doesn't download updates... the absolutely incorrect
place to be looking is in a client-side logfile. See my post to Brian,
describing the correct diagnostics, and most likely cause(s) of his very
common problem.
Maybe I was not clear enough, but I meant the log file from _server_ side
(apologies Brian).
You /specifically/ asked for the WindowsUpdate.log.

Complicated by the fact that Brian grabbed one from an XP SP1 system.. not
the WSUS server!

Even so.. the WindowsUpdate.log will have /nothing/ addressing WSUS SERVER
issues.
The WindowsUpdate.log on the SERVER only logs activity of the /WUA/ on that
server.
Post by Arek Iskra [MVP]
Post by Lawrence Garvin
Furthermore, when provided with this client-side log file.... did you
totally miss the fact that the /client/ isn't even connecting to the WSUS
server, and isn't even /configured/ to connect to the WSUS server -- but
did /successfully/ connect to WindowsUpdate, and download and install a
half dozen updates, and then was restarted?
Exactly what I wanted to verify. If it is able to connect to WU and
download updates, there is no connectivity problem. Perhaps I could ask to
check if Brian can connect to Windows Update portal.
Who cares about the WindowsUpdate portal..... the question is why the
/server/ cannot download /CONTENT/ after a successful synchronization. The
fact that the sychronization succeeded already tells us there is good
connectivity. The /only/ reason downloads do not succeeded (as observed to
date) is due to something internal to the organizational network. Either:

(1) There is an issue with the proxy server, not supporting protocols
necessary to operate WSUS, or
(2) The WSUS server is misconfigured.
Post by Arek Iskra [MVP]
Do you find it to be totally irrelevant, Lawrence?
Yes I do.. the LOG was from a Windows XP SP1 system! And even if it had been
from the server, it wouldn't have told us anything we didn't already know,
by virtue of the fact that the server had successfully synchronized.
Post by Arek Iskra [MVP]
Post by Lawrence Garvin
Or that this WindowsUpdate.log file is from a Windows XP SP1 system and
could not possibly have even come from the /SERVER/?
It's good when more than one pair of eyes are looking into the problem. I
missed that one.
Peace my friend.
Peace to you.. also.. but we have enough people here throwing out "ideas"
off the top of their head with no basis in reality without those who are
supposed to be the /experts/ doing the same thing.

Forgive my "reaction". I now understand your logic, but I disagree with its
relevance to the issue.
Post by Arek Iskra [MVP]
--
Arek Iskra
MVP for Windows Server - Software Distribution
Arek Iskra [MVP]
2005-09-02 15:25:23 UTC
Permalink
Post by Lawrence Garvin
Peace to you.. also.. but we have enough people here throwing out "ideas"
off the top of their head with no basis in reality without those who are
supposed to be the /experts/ doing the same thing.
I respect your knowledge in WSUS field. Really. As for myself, I have never
claimed to be an expert on WSUS. Yes, I have participated in beta tests. I
have run it in my virtual lab ever since. We are going to (finally)
implement it in our company soon. If you have concluded me to be an expert
from my sig, then there is more to software distribution than WSUS.
Post by Lawrence Garvin
Forgive my "reaction". I now understand your logic, but I disagree with
its relevance to the issue.
Heck, there is no need to forgive. But my day was spoilt anyway. Nobody
enjoys being flamed like this for making wrong assumptions... We all make
mistakes after all.

Passion for helping others is a virtue, so is the attitude. Keeping a good
balance between those two is important. Remember it is a public newsgroup,
even if you want to treat it as your second home. It surely needs people
with your knowledge on the subject, no doubt. But we can keep friendly
atmosphere at the same time. Look around, people on other public Microsoft
newsgroups don't get reprimanded so easily unless they've done something
serious against Netiquette.

Well, enough of public bandwidth wasted by myself, sorry. If you would like
to continue the discussion, I suggest we bring it offline. Just remove
"nospam_" from my email address. You are more than welcome to pop by.
--
Arek Iskra
MVP for Windows Server - Software Distribution
Lawrence Garvin
2005-08-30 17:04:15 UTC
Permalink
Well, there's a lot wrong here.. but it's not affecting your server
downloads...

For one... this XP SP1 system is not configured (via policy) to use the WSUS
server.
Post by Brian Rottman
2005-08-30 10:37:45 1456 196c Agent * WSUS server: <NULL>
2005-08-30 10:37:45 1456 196c Agent * WSUS status server: <NULL>
Second.... why even would you look in a /client/ log to try to troubleshoot
a /server/ download issue??????
Post by Brian Rottman
I don't see anything wrong here...
2005-08-30 10:37:00 1456 196c Misc =========== Logging initialized
(build: 5.8.0.2469, tz: -0400) ===========
C:\WINDOWS\System32\svchost.exe
C:\WINDOWS\system32\wuaueng.dll
2005-08-30 10:37:00 1456 196c Service *************
2005-08-30 10:37:00 1456 196c Service ** START ** Service: Service
startup
2005-08-30 10:37:00 1456 196c Service *********
2005-08-30 10:37:00 1456 196c Agent * WU client version 5.8.0.2469
2005-08-30 10:37:00 1456 196c Agent * SusClientId =
'39650416-6c25-46fb-bd58-43bc34c93c6f'
C:\WINDOWS\SoftwareDistribution
2005-08-30 10:37:00 1456 196c Agent * Access type: No proxy
2005-08-30 10:37:00 1456 196c Agent * Network state: Connected
2005-08-30 10:37:45 1456 196c Agent *********** Agent: Initializing
Windows Update Agent ***********
2005-08-30 10:37:45 1456 196c Agent *********** Agent: Initializing
global settings cache ***********
2005-08-30 10:37:45 1456 196c Agent * WSUS server: <NULL>
2005-08-30 10:37:45 1456 196c Agent * WSUS status server: <NULL>
2005-08-30 10:37:45 1456 196c Agent * Target group: (Unassigned
Computers)
2005-08-30 10:37:45 1456 196c Agent * Windows Update access disabled: No
2005-08-30 10:37:45 1456 196c DnldMgr Download manager restoring 0
downloads
2005-08-30 10:37:45 1456 196c AU ########### AU: Initializing Automatic
Updates ###########
2005-08-30 10:37:45 1456 196c AU # Approval type: Pre-install notify
(User preference)
2005-08-30 10:37:45 1456 196c AU # Auto-install minor updates: No (User
preference)
2005-08-30 10:37:45 1456 196c AU AU setting pending client directive to
'Install Approval'
2005-08-30 10:37:45 1456 196c Report *********** Report: Initializing
static reporting data ***********
2005-08-30 10:37:45 1456 196c Report * OS Version = 5.2.3790.1.0.131346
2005-08-30 10:37:46 1456 196c Report * Computer Brand = Intel
2005-08-30 10:37:46 1456 196c Report * Computer Model = SWV25
2005-08-30 10:37:46 1456 196c Report * Bios Revision =
SWV25.86B.0190.P16.0310281020
2005-08-30 10:37:46 1456 196c Report * Bios Name = SWV25 v10.00
2005-08-30 10:37:46 1456 196c Report * Bios Release Date =
2003-10-28T00:00:00
2005-08-30 10:37:46 1456 196c Report * Locale ID = 1033
2005-08-30 10:37:46 1456 196c AU #############
2005-08-30 10:37:46 1456 196c AU ## START ## AU: Search for updates
2005-08-30 10:37:46 1456 196c AU #########
2005-08-30 10:37:46 1456 196c AU <<## SUBMITTED ## AU: Search for updates
[CallId = {7C7D84E9-A8EE-4E65-8DCB-B5C476E4E269}]
2005-08-30 10:37:46 1456 5dc Agent *************
2005-08-30 10:37:46 1456 5dc Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-30 10:37:46 1456 5dc Agent *********
2005-08-30 10:37:47 1456 5dc Agent * Added update
{F89C6A2F-F6C2-4B27-8C93-1561EE55B715}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{745BEB74-FCB0-4323-ADF3-470A9AF3C615}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{A9711EF4-689B-4833-975B-0FBF38D7236A}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{9766EE68-0156-4898-9BB8-D1BC08E0F4B1}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{BA825FF2-7B5B-411A-B066-B0212DC66425}.100 to search result
2005-08-30 10:37:47 1456 5dc Agent * Added update
{43CFE95C-26ED-48BC-957B-675AEC692DF0}.101 to search result
2005-08-30 10:37:47 1456 5dc Agent * Found 6 updates and 10 categories
in search
2005-08-30 10:37:47 1456 5dc Agent *********
2005-08-30 10:37:47 1456 5dc Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-30 10:37:47 1456 5dc Agent *************
2005-08-30 10:37:47 1456 1ad0 AU >>## RESUMED ## AU: Search for updates
[CallId = {7C7D84E9-A8EE-4E65-8DCB-B5C476E4E269}]
2005-08-30 10:37:47 1456 1ad0 AU # 6 updates detected
2005-08-30 10:37:47 1456 1ad0 AU #########
2005-08-30 10:37:47 1456 1ad0 AU ## END ## AU: Search for updates
[CallId = {7C7D84E9-A8EE-4E65-8DCB-B5C476E4E269}]
2005-08-30 10:37:47 1456 1ad0 AU #############
{BF3D5B50-4B29-4414-82F5-8D58DA04857C} 2005-08-30 10:37:45-0400 1 202 102
{00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success
Content Install Reboot completed.
2005-08-30 10:37:59 1456 196c AU AU found 1 sessions to launch client into
2005-08-30 10:37:59 1456 196c AU Launched new AU client for directive
'Install Approval', session id = 0x0
2005-08-30 10:38:00 7936 1240 Misc =========== Logging initialized
(build: 5.8.0.2469, tz: -0400) ===========
C:\WINDOWS\system32\wuauclt.exe
2005-08-30 10:38:00 7936 1240 AUClnt Launched Client UI process
2005-08-30 10:38:00 7936 1240 AUClnt AU client got new directive =
'Install Approval', serviceId = {9482F4B4-E343-43B6-B170-9A65BC822C77},
return = 0x00000000
2005-08-30 10:38:00 7936 1240 AUClnt AU client creating default WU/WSUS UI
plugin
2005-08-30 10:38:00 1456 1610 AU AU setting client response for sessionId
0x0 to 'Pending'
On Tue, 30 Aug 2005 10:31:13 -0400, Arek Iskra [MVP]
Post by Arek Iskra [MVP]
Post by Brian Rottman
New installation of WSUS wn't download updates. It synchronized just
fine but just sits at "Downloading 0.00 MB of 11,693.96 MB"
Any ideas?
Have you checked WindowsUpdate.log in Windows folder?
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Lawrence Garvin
2005-08-30 17:01:43 UTC
Permalink
The WindowsUpdate.log is the wrong place to look for issues concerning the
/server/ downloading files from microsoft.com

Brian..... please scan the server's EVENT LOGS as well as the Home Page of
the WSUS Admin Console for information concerning why the download is
failing, but the most common reasons are:

(1) The proxy server does not support HTTP v1.1 Range Protocol Headers

(2) The WSUS server does not have the correct proxy configuration
settings -- including authentication.

(3) Security access permissions on the server are incorrect, most notably
that the "Network Service" account (on Windows Server 2003) does not have
READ permissions to the root of a non-system drive which stores the ~\WSUS
folder tree.
Post by Arek Iskra [MVP]
Post by Brian Rottman
New installation of WSUS wn't download updates. It synchronized just fine
but just sits at "Downloading 0.00 MB of 11,693.96 MB"
Any ideas?
Have you checked WindowsUpdate.log in Windows folder?
--
Arek Iskra
MVP for Windows Server - Software Distribution
Arek Iskra [MVP]
2005-08-31 15:01:58 UTC
Permalink
Post by Lawrence Garvin
The WindowsUpdate.log is the wrong place to look for issues concerning the
/server/ downloading files from microsoft.com
Brian..... please scan the server's EVENT LOGS as well as the Home Page of
the WSUS Admin Console for information concerning why the download is
(1) The proxy server does not support HTTP v1.1 Range Protocol Headers
RFC Specification for HTTP 1.1 has been around since circa 1999, very
unlikely that Watchguard Firebox III will not support it.
Post by Lawrence Garvin
(2) The WSUS server does not have the correct proxy configuration
settings -- including authentication.
That would prevent the server from getting to _any_ Internet resource.
--
Arek Iskra
MVP for Windows Server - Software Distribution
Lawrence Garvin
2005-08-31 15:29:11 UTC
Permalink
Post by Arek Iskra [MVP]
Post by Lawrence Garvin
The WindowsUpdate.log is the wrong place to look for issues concerning
the /server/ downloading files from microsoft.com
Brian..... please scan the server's EVENT LOGS as well as the Home Page
of the WSUS Admin Console for information concerning why the download is
(1) The proxy server does not support HTTP v1.1 Range Protocol Headers
RFC Specification for HTTP 1.1 has been around since circa 1999, very
unlikely that Watchguard Firebox III will not support it
Yeah.. and three dozen SonicWall customers have said the same thing. :-)
Post by Arek Iskra [MVP]
Post by Lawrence Garvin
(2) The WSUS server does not have the correct proxy configuration
settings -- including authentication.
That would prevent the server from getting to _any_ Internet resource.
Not properly authenticating /might/ prevent the server from getting to /any/
Internet resource. But really that's a function of how the proxy server and
clients are configured for authentication. But authentication is but one
factor affecting this issue, thus my add on statement "---including
authentication", meaning that there are many aspects to the proxy
configuration that need to be checked (and that check needs to also include
authentication).


All of this issue is very rich history, and probably ranks in the top five
"issues" seen with WSUS Server Operations since back when the product was
still in beta testing. Reading the historical posts in the newsgroup would
be very helpful, I think.

There are dozens of examples of this problem arising, and the solutions, in
every case, were one of the two above. Either the proxy was not supporting
the protocol, the proxy was not configured correctly to support
multi-protocol access from a single client, or the WSUS server was not
configured correctly to use the proxy server involved.

Now.. that's not to say that I'm so blind as to think this particular
scenario might be a brand new never-before-seen cause, but before I go down
that road, I'd prefer to eliminate the very common and well-discussed basic
causes -- which are all proxy related causes.

Very specifically, synchronization is done on HTTPS/443, file downloading is
done on HTTP/80. If the client is only talking to one generic proxy port
(e.g. 8080), the proxy server needs to be able to distinguish whether the
request is HTTPS or HTTP, and route it to the correct destination port.
Experience has shown us in the past several months that many proxy server
either cannot do that, or are not configured properly to support that.

We've seen several (perhaps dozens) of situations where the WSUS server
successfully synchronized, and then was unable to download content because
the proxy server didn't recognize the change in protocol within the session
between it and the WSUS server.

Either the proxy needs to be configured to listen on multiple ports to
support "simultaneous" HTTP and HTTPS sessions from the same client, or the
proxy needs to be able to properly route the client request based on
protocol to the correct destination ports and make that determination on a
per-request basis, not a per-session basis.

If the WSUS server needs to route traffic to separate ports on the proxy for
HTTP and HTTPS, that needs to be configured at the WSUS server, and it
cannot be configured via the WSUS interface, but requires use of proxycfg
(and, to make things easier, the IE proxy configuration dialog box).
Post by Arek Iskra [MVP]
--
Arek Iskra
MVP for Windows Server - Software Distribution
Brian Rottman
2005-08-31 15:23:17 UTC
Permalink
You sir are the man, adding the Network Service to the root of the drive
fixed the problem. Thanks!!!

Brian
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Laddo Domacinovic
2005-09-09 11:49:05 UTC
Permalink
I am having same problem just on win 2000 server. this is part of
SoftwareDistribution.log, help if you can

2005-09-08 12:04:07.671
UTC Info aspnet_wp.128 ThreadEntry SusEventDispatcher.DispatchManagerDatabasePollingThreadProc
2005-09-08 12:04:07.734
UTC Info aspnet_wp.37 ThreadEntry ISAPIRuntime.ProcessRequest
2005-09-08 12:04:07.765 UTC Error aspnet_wp.37 UpdateServer.LogMessage EXT:
Administration Interface encountered an error. Exception:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpResponse.Redirect(String url, Boolean endResponse)
at System.Web.HttpResponse.Redirect(String url)
at Administration.DefaultPage.CheckForErrorConditions()
at Administration.DefaultPage.Page_Load(Object sender, EventArgs e)

at
Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.LogMessage(LogLevel,
String, Object[])
at Administration.Common.UIError.DisplayError(Exception, Boolean)
at Administration.DefaultPage.Page_Load(Object, EventArgs)
at System.Web.UI.Control.OnLoad(EventArgs)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain()
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext)
at
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep, Boolean&)
at System.Web.HttpApplication.ResumeSteps(Exception)
at
System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext, AsyncCallback, Object)
at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest)
at System.Web.HttpRuntime.ProcessRequest(HttpWorkerRequest)
at System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr, Int32)
2005-09-08 12:04:07.765
UTC Info aspnet_wp.128 SusEventDispatcher.TriggerEvent TriggerEvent called
for NotificationEventName: LanguageChange, EventInfo: LanguageChange
2005-09-08 12:04:07.843
UTC Info aspnet_wp.128 SusEventDispatcher.TriggerEvent TriggerEvent called
for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
2005-09-08 12:04:07.859
UTC Info aspnet_wp.128 SusEventDispatcher.TriggerEvent TriggerEvent called
for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
2005-09-08 12:04:07.859
UTC Info aspnet_wp.128 SusEventDispatcher.TriggerEvent TriggerEvent called
for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
2005-09-08 12:04:07.859
UTC Info aspnet_wp.128 SusEventDispatcher.TriggerEvent TriggerEvent called
for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2005-09-08 12:04:07.875
UTC Info aspnet_wp.608 ThreadEntry SusEventDispatcher.DispatchManagerWorkerThreadProc
2005-09-08 12:04:07.921
UTC Info aspnet_wp.608 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2005-09-08 12:04:12.984
UTC Info aspnet_wp.128 SusEventDispatcher.TriggerEvent TriggerEvent called
for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2005-09-08 12:04:13.140
UTC Info aspnet_wp.773 ThreadEntry SusEventDispatcher.DispatchManagerWorkerThreadProc
2005-09-08 12:04:13.171
UTC Info aspnet_wp.773 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2005-09-08 12:04:15.250
UTC Info StartServer.9 ThreadEntry SusEventDispatcher.DispatchManagerDatabasePollingThreadProc
2005-09-08 12:04:15.265
UTC Info StartServer.9 SusEventDispatcher.TriggerEvent TriggerEvent called
for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2005-09-08 12:04:15.281
UTC Info StartServer.14 ThreadEntry SusEventDispatcher.DispatchManagerWorkerThreadProc
2005-09-08 12:04:15.281
UTC Info StartServer.14 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2005-09-08 12:04:19.234
UTC Info aspnet_wp.128 SusEventDispatcher.TriggerEvent TriggerEvent called
for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
2005-09-08 12:04:19.265
UTC Info wsusservice.4 ThreadEntry SusService.SusServiceStartUpThreadProc
2005-09-08 12:04:19.281
UTC Info wsusservice.4 SusService.SusServiceStartUpThreadProc Update Services
Service Started
2005-09-08 12:04:19.562
UTC Info wsusservice.4 SusService.CleanUpIntermediateFileDownload CleanupIntermediateFileDownload
2005-09-08 12:04:20.015
UTC Info wsusservice.8 ThreadEntry SusEventDispatcher.DispatchManagerDatabasePollingThreadProc
2005-09-08 12:04:20.015
UTC Info wsusservice.8 SusEventDispatcher.TriggerEvent TriggerEvent called
for NotificationEventName: CatalogSyncAgent, EventInfo: Startup
2005-09-08 12:04:20.015
UTC Info wsusservice.8 SusEventDispatcher.TriggerEvent TriggerEvent called
for NotificationEventName: ContentSyncAgent, EventInfo: Startup
2005-09-08 12:04:20.031
UTC Info wsusservice.10 ThreadEntry SusEventDispatcher.DispatchManagerWorkerThreadProc
2005-09-08 12:04:20.031
UTC Info wsusservice.10 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: CatalogSyncAgent
2005-09-08 12:04:20.046
UTC Info wsusservice.8 SusEventDispatcher.TriggerEvent TriggerEvent called
for NotificationEventName: StateMachineReset, EventInfo: Startup
2005-09-08 12:04:20.062
UTC Info wsusservice.12 ThreadEntry CatalogSyncAgent.WakeUpWorkerThreadProc
2005-09-08 12:04:20.078
UTC Info wsusservice.12 CatalogSyncAgent.WakeUpWorkerThreadProc ServerHealth:
Updating Server Health for Component: CatalogSyncAgent, Marking as Running
2005-09-08 12:04:20.062
UTC Info wsusservice.13 ThreadEntry SusEventDispatcher.DispatchManagerWorkerThreadProc
2005-09-08 12:04:20.078
UTC Info wsusservice.13 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ContentSyncAgent
2005-09-08 12:04:20.078
UTC Info wsusservice.13 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: StateMachineReset
2005-09-08 12:04:20.078
UTC Info wsusservice.12 CatalogSyncAgent.WakeUpWorkerThreadProc Handling
systemStartup work...
2005-09-08 12:04:20.296
UTC Info wsusservice.16 ThreadEntry ResetStateMachineAgent.WakeUpWorkerThreadProc
2005-09-08 12:04:20.312
UTC Info StartServer.9 SusEventDispatcher.TriggerEvent TriggerEvent called
for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
2005-09-08 12:04:20.328
UTC Info wsusservice.16 ResetStateMachineAgent.WakeUpWorkerThreadProc State
Machine Reset Agent Starting
2005-09-08 12:04:20.312
UTC Info wsusservice.12 CatalogSyncAgent.WakeUpWorkerThreadProc Finished
systemStartup work.
2005-09-08 12:04:20.328
UTC Info wsusservice.15 ThreadEntry ContentSyncAgent.WakeUpWorkerThreadProc
2005-09-08 12:04:20.359
UTC Info wsusservice.8 SusEventDispatcher.TriggerEvent TriggerEvent called
for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2005-09-08 12:04:20.484
UTC Info wsusservice.15 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
2005-09-08 12:04:20.484
UTC Info wsusservice.17 ThreadEntry SusEventDispatcher.DispatchManagerWorkerThreadProc
2005-09-08 12:04:20.500 UTC Info wsusser
Post by Brian Rottman
You sir are the man, adding the Network Service to the root of the drive
fixed the problem. Thanks!!!
Brian
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Continue reading on narkive:
Loading...