|
|
Error:
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Core
Event ID: 10032
Date: 2007/05/28
Time: 11:58:40 AM
User: N/A
Computer: XXXXX
Description:
The server is failing to download some updates.
1) No other WSUS errors logged in event log
2) wsusutil checkhealth shows this as the only issue
3) As far as I can see from the update logs, only one warning:
Warning w3wp.12 SoapUtilities.CreateException ThrowException: actor =
https://server:8531/ClientWebService/client.asmx, ID=6d1019b8-
f68c-4780-a2e7-e2ff08ac62ff, ErrorCode=ServerChanged, Message=Server
rolled back since last call to GetCookie, Client=c96cc21b-
b626-495f-8710-9666ee409689
4) I abolutely hate seeing an error in the event log, esp as I do not
know *why* this is occurring and even more, where can I actually check
to see *which* updates are failing. I'd hate to rebuild this from
scratch.
5) The upstream server is MU, and all sync's are looking OK.
6) As far as I can see clients are connecting and getting updated.
7) This server was upgraded from WSUS2 SP1, and the database has been
moved to SQL 2005 as per procedure in installation notes. I do not see
any problems on the DB side though.
Any pointers appreciated.
|
|
"eugenevr" <evrng[ at ]yahoo.com> wrote in message
news:1180347779.443509.287630[ at ]h2g2000hsg.googlegroups.com...
[Quoted Text] > Error:
> Event Type: Error
> Event Source: Windows Server Update Services
> Event Category: Core
> Event ID: 10032
> Date: 2007/05/28
> Time: 11:58:40 AM
> User: N/A
> Computer: XXXXX
> Description:
> The server is failing to download some updates.
>
> 1) No other WSUS errors logged in event log
> 2) wsusutil checkhealth shows this as the only issue
Okay....
Have you determined which updates are failing to download?
What can you tell me about the environment? Is the WSUS server configured to
use a proxy? If so, what proxy server do you use? Do you have the ability to
configure the proxy server, or does somebody else own that system? If
somebody else owns it.. have they changed anything on it?
>7) This server was upgraded from WSUS2 SP1, and the database has been
>moved to SQL 2005 as per procedure in installation notes. I do not see
>any problems on the DB side though.
If using a proxy configuration, did you address the issue described in the
very first paragraph of the Release Notes, after performing your upgrade?
Important configuration issue: You must overwrite the proxy server password
in the configuration wizard
If you are using a proxy server that requires user name/password
authentication, the WSUS server may fail to synchronize updates if you do
not overwrite the proxy server password when running the WSUS Server
Configuration Wizard. Because the configuration wizard is launched
automatically at the end of setup, this problem can cause synchronization
errors after you upgrade to WSUS 3.0 from an older version of WSUS.
You can avoid this problem by cancelling the configuration wizard after
upgrade, or by re-entering the correct proxy password when the configuration
wizard runs. To recover from this problem after it has occurred, go to
Update Source and Proxy Server on the Options page, re-enter the proxy
password, and then save the setting.
> 3) As far as I can see from the update logs, only one warning:
>
> Warning w3wp.12 SoapUtilities.CreateException ThrowException: actor =
> https://server:8531/ClientWebService/client.asmx, ID=6d1019b8-
> f68c-4780-a2e7-e2ff08ac62ff, ErrorCode=ServerChanged, Message=Server
> rolled back since last call to GetCookie, Client=c96cc21b-
> b626-495f-8710-9666ee409689
This is the *client* log, and has absolutely nothing to do with the above
error found in the Event Log.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
Hi Lawrence, tx for the response.
1) The server is using an ISA 2006 box as proxy, and the rule is
unauthenticated. I have full control over that box.
2) WSUS is running on a mngmt server, and we also download Trend AV
updates on this box via ISA, no issues.
3) The server was never configured to use any proxy pwds
4) I've checked our OPSNotices and no changes were made on the ISA box
(will follow up and double check though, will also check the ISA logs
just to be sure)
5) The weird thing is that WSUS does not specify "which" updates
aren't being downloaded!
6) FYI: Just looked at the last couple of hours and summary of events:
a. 18:07 - The server is failing to download some updates
b. 23:07 - Catalog last syn'ed 1 or more days ago
c. 12:07 - The server is failing to download some updates
d. 01:02 - (WSUS MMC) - Sync OK, 4 new updates, 5 expired
e. 06:07 - The server is failing to download some updates
7) *No* other warnings or alerts in the event logs either side of all
these events...
8) I've done other in-place upgrades of 3.0 at other clients, but they
all seem to be fine.
*** Your help is appreciated!!
On 29 May, 00:49, "Lawrence Garvin \(MVP\)"
<onsit...[ at ]community.nospam> wrote:
[Quoted Text] > "eugenevr" <e...[ at ]yahoo.com> wrote in message > > news:1180347779.443509.287630[ at ]h2g2000hsg.googlegroups.com... > > > Error: > > Event Type: Error > > Event Source: Windows Server Update Services > > Event Category: Core > > Event ID: 10032 > > Date: 2007/05/28 > > Time: 11:58:40 AM > > User: N/A > > Computer: XXXXX > > Description: > > The server is failing to download some updates. > > > 1) No other WSUS errors logged in event log > > 2) wsusutil checkhealth shows this as the only issue > > Okay.... > > Have you determined which updates are failing to download? > > What can you tell me about the environment? Is the WSUS server configured to > use a proxy? If so, what proxy server do you use? Do you have the ability to > configure the proxy server, or does somebody else own that system? If > somebody else owns it.. have they changed anything on it? > > >7) This server was upgraded from WSUS2 SP1, and the database has been > >moved to SQL 2005 as per procedure in installation notes. I do not see > >any problems on the DB side though. > > If using a proxy configuration, did you address the issue described in the > very first paragraph of the Release Notes, after performing your upgrade? > Important configuration issue: You must overwrite the proxy server password > in the configuration wizard > If you are using a proxy server that requires user name/password > authentication, the WSUS server may fail to synchronize updates if you do > not overwrite the proxy server password when running the WSUS Server > Configuration Wizard. Because the configuration wizard is launched > automatically at the end of setup, this problem can cause synchronization > errors after you upgrade to WSUS 3.0 from an older version of WSUS. > > You can avoid this problem by cancelling the configuration wizard after > upgrade, or by re-entering the correct proxy password when the configuration > wizard runs. To recover from this problem after it has occurred, go to > Update Source and Proxy Server on the Options page, re-enter the proxy > password, and then save the setting. > > > 3) As far as I can see from the update logs, only one warning: > > > Warning w3wp.12 SoapUtilities.CreateException ThrowException: actor = > > https://server:8531/ClientWebService/client.asmx, ID=6d1019b8- > > f68c-4780-a2e7-e2ff08ac62ff, ErrorCode=ServerChanged, Message=Server > > rolled back since last call to GetCookie, Client=c96cc21b- > > b626-495f-8710-9666ee409689 > > This is the *client* log, and has absolutely nothing to do with the above > error found in the Event Log. > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D09...> > Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/...> > And, almost everything else is at http://wsusinfo.onsitechsolutions.com> ....
|
|
|
|
Thanks.
OK under "All updates" I saw a number of updates that show "failed".
Most of them had the "This file has not been downloaded...". I
cancelled the download, and then re-approved all of them.
The error message is now gone and I get the "WSUS is healthy message",
*but*, and this is the q behind my q: after about 12 hours I still
have the same downloads in the list, all still show failed, and all
the ones that were not downloaded still have the same status...
I guess that for the failed ones we can look at the specific clients
involved, might be specific issues on those units (normally there is
about 1 out of 250 odd that had an issue). As for the ones that remain
"undownloaded", simply don't know. I don't want to decline those?
Again, tx for your help.
E
On 29 May, 08:43, "Lawrence Garvin \(MVP\)"
<onsit...[ at ]community.nospam> wrote:
[Quoted Text]
|
|
"eugenevr" <evrng[ at ]yahoo.com> wrote in message
news:1180502506.061899.177760[ at ]o5g2000hsb.googlegroups.com...
[Quoted Text] > Thanks.
> OK under "All updates" I saw a number of updates that show "failed".
> Most of them had the "This file has not been downloaded...". I
> cancelled the download, and then re-approved all of them.
> The error message is now gone and I get the "WSUS is healthy message",
> *but*, and this is the q behind my q: after about 12 hours I still
> have the same downloads in the list, all still show failed, and all
> the ones that were not downloaded still have the same status...
An indication that the downloads are still failing.
But, at least you now know which ones. Next Q: Are *all* of the downloads
failing, or just some of them?
> I guess that for the failed ones we can look at the specific clients
> involved, might be specific issues on those units (normally there is
> about 1 out of 250 odd that had an issue). As for the ones that remain
> "undownloaded", simply don't know. I don't want to decline those?
These are not failures of the client downloading from the WSUS server...
they are a failure of the WSUS server downloading from it's upstream server
(microsoft.com in a single server deployment).
The most common cause for this failure is interference from a proxy server
or firewall.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
There seems to be about 10 or so failing, all the others are
fine...which is really puzzling. (And of course today the error is
back in the log...)
I'm about to just give up and do a clean install really; taking far
more time than it is worth to be honest. I love troubleshooting but
I've got multiple other projects running so I'm going to get rid of
this thorn in the flesh in the shortest possible way I guess.
Thanks for the help anyway!
Eugene
On 30 May, 15:16, "Lawrence Garvin \(MVP\)"
<onsit...[ at ]community.nospam> wrote:
[Quoted Text] > "eugenevr" <e...[ at ]yahoo.com> wrote in message > > news:1180502506.061899.177760[ at ]o5g2000hsb.googlegroups.com... > > > Thanks. > > OK under "All updates" I saw a number of updates that show "failed". > > Most of them had the "This file has not been downloaded...". I > > cancelled the download, and then re-approved all of them. > > The error message is now gone and I get the "WSUS is healthy message", > > *but*, and this is the q behind my q: after about 12 hours I still > > have the same downloads in the list, all still show failed, and all > > the ones that were not downloaded still have the same status... > > An indication that the downloads are still failing. > > But, at least you now know which ones. Next Q: Are *all* of the downloads > failing, or just some of them? > > > I guess that for the failed ones we can look at the specific clients > > involved, might be specific issues on those units (normally there is > > about 1 out of 250 odd that had an issue). As for the ones that remain > > "undownloaded", simply don't know. I don't want to decline those? > > These are not failures of the client downloading from the WSUS server... > they are a failure of the WSUS server downloading from it's upstream server > (microsoft.com in a single server deployment). > > The most common cause for this failure is interference from a proxy server > or firewall. > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D09...> > Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/...> > And, almost everything else is at http://wsusinfo.onsitechsolutions.com> ....
|
|
On May 31, 12:50 am, eugenevr <e...[ at ]yahoo.com> wrote:
[Quoted Text] > There seems to be about 10 or so failing, all the others are > fine...which is really puzzling. (And of course today the error is > back in the log...) > > I'm about to just give up and do a clean install really; taking far > more time than it is worth to be honest. I love troubleshooting but > I've got multiple other projects running so I'm going to get rid of > this thorn in the flesh in the shortest possible way I guess. > > Thanks for the help anyway! > > Eugene > > On 30 May, 15:16, "Lawrence Garvin \(MVP\)" > > <onsit...[ at ]community.nospam> wrote: > > "eugenevr" <e...[ at ]yahoo.com> wrote in message > > >news:1180502506.061899.177760[ at ]o5g2000hsb.googlegroups.com... > > > > Thanks. > > > OK under "All updates" I saw a number of updates that show "failed". > > > Most of them had the "This file has not been downloaded...". I > > > cancelled the download, and then re-approved all of them. > > > The error message is now gone and I get the "WSUS is healthy message", > > > *but*, and this is the q behind my q: after about 12 hours I still > > > have the same downloads in the list, all still show failed, and all > > > the ones that were not downloaded still have the same status... > > > An indication that the downloads are still failing. > > > But, at least you now know which ones. Next Q: Are *all* of the downloads > > failing, or just some of them? > > > > I guess that for the failed ones we can look at the specific clients > > > involved, might be specific issues on those units (normally there is > > > about 1 out of 250 odd that had an issue). As for the ones that remain > > > "undownloaded", simply don't know. I don't want to decline those? > > > These are not failures of the client downloading from the WSUS server... > > they are a failure of the WSUS server downloading from it's upstream server > > (microsoft.com in a single server deployment). > > > The most common cause for this failure is interference from a proxy server > > or firewall. > > > -- > > Lawrence Garvin, M.S., MCTS, MCP > > Independent WSUS Evangelist > > MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D09...> > > Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/...> > > And, almost everything else is at http://wsusinfo.onsitechsolutions.com> > ....
Hi I am having a similar problem, but ALL of my updates are failing.
I did not upgrade from version 2 this is a clean install of version 3.
My server is not using a proxy.
It is behind a Sonicwall firewall, but version 2 was working behind
the same firewall. On that firewall ports 80 and 443 are open for all
outbound traffic.
WSUS is running on a server running Windwos Server 2003 Web Edition.
The server is also running Ipswitch's Whats Up Gold.
Thanks
|
|
On May 31, 12:50 am, eugenevr <e...[ at ]yahoo.com> wrote:
[Quoted Text] > There seems to be about 10 or so failing, all the others are > fine...which is really puzzling. (And of course today the error is > back in the log...) > > I'm about to just give up and do a clean install really; taking far > more time than it is worth to be honest. I love troubleshooting but > I've got multiple other projects running so I'm going to get rid of > this thorn in the flesh in the shortest possible way I guess. > > Thanks for the help anyway! > > Eugene > > On 30 May, 15:16, "Lawrence Garvin \(MVP\)" > > <onsit...[ at ]community.nospam> wrote: > > "eugenevr" <e...[ at ]yahoo.com> wrote in message > > >news:1180502506.061899.177760[ at ]o5g2000hsb.googlegroups.com... > > > > Thanks. > > > OK under "All updates" I saw a number of updates that show "failed". > > > Most of them had the "This file has not been downloaded...". I > > > cancelled the download, and then re-approved all of them. > > > The error message is now gone and I get the "WSUS is healthy message", > > > *but*, and this is the q behind my q: after about 12 hours I still > > > have the same downloads in the list, all still show failed, and all > > > the ones that were not downloaded still have the same status... > > > An indication that the downloads are still failing. > > > But, at least you now know which ones. Next Q: Are *all* of the downloads > > failing, or just some of them? > > > > I guess that for the failed ones we can look at the specific clients > > > involved, might be specific issues on those units (normally there is > > > about 1 out of 250 odd that had an issue). As for the ones that remain > > > "undownloaded", simply don't know. I don't want to decline those? > > > These are not failures of the client downloading from the WSUS server... > > they are a failure of the WSUS server downloading from it's upstream server > > (microsoft.com in a single server deployment). > > > The most common cause for this failure is interference from a proxy server > > or firewall. > > > -- > > Lawrence Garvin, M.S., MCTS, MCP > > Independent WSUS Evangelist > > MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D09...> > > Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/...> > > And, almost everything else is at http://wsusinfo.onsitechsolutions.com> > ....
Hi I am having a similar problem, but ALL of my updates are failing.
I did not upgrade from version 2 this is a clean install of version 3.
My server is not using a proxy.
It is behind a Sonicwall firewall, but version 2 was working behind
the same firewall.
WSUS is running on a server running Windwos Server 2003 Web Edition.
The server is also running Ipswitch's Whats Up Gold.
Thanks
|
|
On May 31, 12:50 am, eugenevr <e...[ at ]yahoo.com> wrote:
[Quoted Text] > There seems to be about 10 or so failing, all the others are > fine...which is really puzzling. (And of course today the error is > back in the log...) > > I'm about to just give up and do a clean install really; taking far > more time than it is worth to be honest. I love troubleshooting but > I've got multiple other projects running so I'm going to get rid of > this thorn in the flesh in the shortest possible way I guess. > > Thanks for the help anyway! > > Eugene > > On 30 May, 15:16, "Lawrence Garvin \(MVP\)" > > <onsit...[ at ]community.nospam> wrote: > > "eugenevr" <e...[ at ]yahoo.com> wrote in message > > >news:1180502506.061899.177760[ at ]o5g2000hsb.googlegroups.com... > > > > Thanks. > > > OK under "All updates" I saw a number of updates that show "failed". > > > Most of them had the "This file has not been downloaded...". I > > > cancelled the download, and then re-approved all of them. > > > The error message is now gone and I get the "WSUS is healthy message", > > > *but*, and this is the q behind my q: after about 12 hours I still > > > have the same downloads in the list, all still show failed, and all > > > the ones that were not downloaded still have the same status... > > > An indication that the downloads are still failing. > > > But, at least you now know which ones. Next Q: Are *all* of the downloads > > failing, or just some of them? > > > > I guess that for the failed ones we can look at the specific clients > > > involved, might be specific issues on those units (normally there is > > > about 1 out of 250 odd that had an issue). As for the ones that remain > > > "undownloaded", simply don't know. I don't want to decline those? > > > These are not failures of the client downloading from the WSUS server... > > they are a failure of the WSUS server downloading from it's upstream server > > (microsoft.com in a single server deployment). > > > The most common cause for this failure is interference from a proxy server > > or firewall. > > > -- > > Lawrence Garvin, M.S., MCTS, MCP > > Independent WSUS Evangelist > > MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D09...> > > Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/...> > > And, almost everything else is at http://wsusinfo.onsitechsolutions.com> > ....
Hi I am having a similar problem, but ALL of my updates are failing.
I did not upgrade from version 2 this is a clean install of version 3.
My server is not using a proxy.
It is behind a Sonicwall firewall, but version 2 was working behind
the same firewall. On that firewall ports 80 and 443 are open for all
outbound traffic.
WSUS is running on a server running Windwos Server 2003 Web Edition.
The server is also running Ipswitch's Whats Up Gold.
Have you found a solution?
Thanks
|
|
<emerson.lenon[ at ]gmail.com> wrote in message
news:1180631346.970163.88810[ at ]q19g2000prn.googlegroups.com...
[Quoted Text] >> > The most common cause for this failure is interference from a proxy
>> > server
>> > or firewall.
> Hi I am having a similar problem, but ALL of my updates are failing.
> I did not upgrade from version 2 this is a clean install of version 3.
> My server is not using a proxy.
> It is behind a Sonicwall firewall, but version 2 was working behind
> the same firewall. On that firewall ports 80 and 443 are open for all
> outbound traffic.
Well... given the history of SonicWall being non-compliant with protocols,
I'd suggest starting with SonicWall technical support.
Unless version 2 was working because you put BITS in "foreground" mode,
which would have hidden any interference from your SonicWall device, and the
necessary HTTP v1.1 protocols needed to support BITS in "background" mode.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
> On May 31, 12:50 am, eugenevr <e...[ at ]yahoo.com> wrote:
>> There seems to be about 10 or so failing, all the others are
>> fine...which is really puzzling. (And of course today the error is
>> back in the log...)
>>
>> I'm about to just give up and do a clean install really; taking far
>> more time than it is worth to be honest. I love troubleshooting but
>> I've got multiple other projects running so I'm going to get rid of
>> this thorn in the flesh in the shortest possible way I guess.
>>
>> Thanks for the help anyway!
>>
>> Eugene
>>
>> On 30 May, 15:16, "Lawrence Garvin \(MVP\)"
>>
>> <onsit...[ at ]community.nospam> wrote:
>> > "eugenevr" <e...[ at ]yahoo.com> wrote in message
>>
>> >news:1180502506.061899.177760[ at ]o5g2000hsb.googlegroups.com...
>>
>> > > Thanks.
>> > > OK under "All updates" I saw a number of updates that show "failed".
>> > > Most of them had the "This file has not been downloaded...". I
>> > > cancelled the download, and then re-approved all of them.
>> > > The error message is now gone and I get the "WSUS is healthy
>> > > message",
>> > > *but*, and this is the q behind my q: after about 12 hours I still
>> > > have the same downloads in the list, all still show failed, and all
>> > > the ones that were not downloaded still have the same status...
>>
>> > An indication that the downloads are still failing.
>>
>> > But, at least you now know which ones. Next Q: Are *all* of the
>> > downloads
>> > failing, or just some of them?
>>
>> > > I guess that for the failed ones we can look at the specific clients
>> > > involved, might be specific issues on those units (normally there is
>> > > about 1 out of 250 odd that had an issue). As for the ones that
>> > > remain
>> > > "undownloaded", simply don't know. I don't want to decline those?
>>
>> > These are not failures of the client downloading from the WSUS
>> > server...
>> > they are a failure of the WSUS server downloading from it's upstream
>> > server
>> > (microsoft.com in a single server deployment).
>>
>>
>> > --
>> > Lawrence Garvin, M.S., MCTS, MCP
>> > Independent WSUS Evangelist
>> > MVP-Software Distribution
>> > (2005-2007)https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D09...
>>
>> > Everything you need for WSUS is
>> > athttp://technet2.microsoft.com/windowsserver/en/technologies/featured/...
>>
>> > And, almost everything else is athttp://wsusinfo.onsitechsolutions.com
>> > ....
>
> Thanks
>
|
|
|