Re: WSUS 3.0 Sp1 Sync fails

[[ Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP.

On the web:
http://www.microsoft.com/communities...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_services
]]


Gabriel Camacho wrote:
> I had installed WSUS 3.0 SP1 on a Windows 2008 server in Jan of this year.
> It
> was working fine until April it seemed to occasionaly start giving me
> failed
> syncronization errors. Since June syncronication started to fail all the
> time. I believe I deleted the files in
> C:\WINDOWS\SoftwareDistribution\Download and got syncs working again. Now
> it
> fails all the time again and nothing I have tried will work. I have even
> tried doing a fresh install on Windows 2003 server Sp2 and receive the
> similar errors when trying to sync. I will post the errors I receive from
> the
> different installations. Any help or suggestions are greatly appreciated.
> Thanks
>
> Windows Server 2008 Std SP1
> IOException: Unable to read data from the transport connection: An
> existing
> connection was forcibly closed by the remote host. --->
> System.Net.Sockets.SocketException: An existing connection was forcibly
> closed by the remote host
> at System.Net.ConnectStream.Read(Byte[] buffer, Int32 offset, Int32 size)
> at
> Microsoft.UpdateServices.ServerSync.ServerSyncComp ressionProxy.GetWebResponse(WebRequest
> webRequest) at
> System.Web.Services.Protocols.SoapHttpClientProtoc ol.Invoke(String
> methodName, Object[] parameters)
> at
> Microsoft.UpdateServices.ServerSyncWebServices.Ser verSync.ServerSyncProxy.GetUpdateData(Cookie
> cookie, UpdateIdentity[] updateIds) at
> Microsoft.UpdateServices.ServerSync.CatalogSyncAge ntCore.WebserviceGetUpdateData(UpdateIdentity[]
> updateIds, List`1 allMetadata, List`1 allFileUrls, Boolean isForConfig)
> at
> Microsoft.UpdateServices.ServerSync.CatalogSyncAge ntCore.GetUpdateDataInChunksAndImport(List`1
> neededUpdates, List`1 allMetadata, List`1 allFileUrls, Boolean
> isConfigData)
> at
> Microsoft.UpdateServices.ServerSync.CatalogSyncAge ntCore.SyncConfigUpdatesFromUSS()
> at
> Microsoft.UpdateServices.ServerSync.CatalogSyncAge ntCore.ExecuteSyncProtocol(Boolean
> allowRedirect)
>
>
> Windows Server 2003 Std SP2 -
> IOException: Unable to read data from the transport connection: An
> existing
> connection was forcibly closed by the remote host. --->
> System.Net.Sockets.SocketException: An existing connection was forcibly
> closed by the remote host
> at System.Net.ConnectStream.Read(Byte[] buffer, Int32 offset, Int32 size)
> at
> Microsoft.UpdateServices.ServerSync.ServerSyncComp ressionProxy.GetWebResponse(WebRequest
> webRequest) at
> System.Web.Services.Protocols.SoapHttpClientProtoc ol.Invoke(String
> methodName, Object[] parameters)
> at
> Microsoft.UpdateServices.ServerSyncWebServices.Ser verSync.ServerSyncProxy.GetUpdateData(Cookie
> cookie, UpdateIdentity[] updateIds) at
> Microsoft.UpdateServices.ServerSync.CatalogSyncAge ntCore.WebserviceGetUpdateData(UpdateIdentity[]
> updateIds, List`1 allMetadata, List`1 allFileUrls, Boolean isForConfig)
> at
> Microsoft.UpdateServices.ServerSync.CatalogSyncAge ntCore.GetUpdateDataInChunksAndImport(List`1
> neededUpdates, List`1 allMetadata, List`1 allFileUrls, Boolean
> isConfigData)
> at
> Microsoft.UpdateServices.ServerSync.CatalogSyncAge ntCore.SyncConfigUpdatesFromUSS()
> at
> Microsoft.UpdateServices.ServerSync.CatalogSyncAge ntCore.ExecuteSyncProtocol(Boolean
> allowRedirect)

> Gabriel Camacho wrote:

>> It was working fine until April it seemed to occasionaly start giving me
>> failed syncronization errors. Since June syncronication started to fail
>> all the
>> time.

This suggests a situation that was growing progressively worse over time.

>> I believe I deleted the files in
>> C:\WINDOWS\SoftwareDistribution\Download and got syncs working again.

I can assure you nothing you did in that directory had anything to do with
WSUS synchronizations -- unless you're out of disk space on your SYSVOL.
Failed synchronizations due to disk space issue does fit with your observed
behavior from April until now.

>> I have even
>> tried doing a fresh install on Windows 2003 server Sp2 and receive the
>> similar errors when trying to sync.

This suggests that the issue is being caused by an external impact.

>> IOException: Unable to read data from the transport connection: An
>> existing connection was forcibly closed by the remote host.

Typically caused when something between the WSUS Server and microsoft.com
aborts the connection. Can also happen if the WSUS Server runs out of disk
space and times out a connection, resulting in the "remote host" dropping
the connection.



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

I have confirmed that disk space is not an issue on either server i have
setup. I don't believe anything has changed in the last couple of months and
I also reviewed my sonicwall log and confirmed that no errors or warnings
show up when trying to sync. Any other suggestions that might help me find a
cause of the problem ? Thanks
--
Gabriel Camacho


"Lawrence Garvin [MVP]" wrote:

> > Gabriel Camacho wrote:
>
> >> It was working fine until April it seemed to occasionaly start giving me
> >> failed syncronization errors. Since June syncronication started to fail
> >> all the
> >> time.
>
> This suggests a situation that was growing progressively worse over time.
>
> >> I believe I deleted the files in
> >> C:\WINDOWS\SoftwareDistribution\Download and got syncs working again.
>
> I can assure you nothing you did in that directory had anything to do with
> WSUS synchronizations -- unless you're out of disk space on your SYSVOL.
> Failed synchronizations due to disk space issue does fit with your observed
> behavior from April until now.
>
> >> I have even
> >> tried doing a fresh install on Windows 2003 server Sp2 and receive the
> >> similar errors when trying to sync.
>
> This suggests that the issue is being caused by an external impact.
>
> >> IOException: Unable to read data from the transport connection: An
> >> existing connection was forcibly closed by the remote host.
>
> Typically caused when something between the WSUS Server and microsoft.com
> aborts the connection. Can also happen if the WSUS Server runs out of disk
> space and times out a connection, resulting in the "remote host" dropping
> the connection.
>
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

"Gabriel Camacho" <> wrote in message
news:56B2A955-EEEF-43C6-AC15-...
>I have confirmed that disk space is not an issue on either server i have
> setup. I don't believe anything has changed in the last couple of months
> and
> I also reviewed my sonicwall log and confirmed that no errors or warnings
> show up when trying to sync. Any other suggestions that might help me find
> a
> cause of the problem ? Thanks

Just FYI.. -- following the fresh thread between you and Swarup_Gupta, who
apparently both have SonicWall appliances -- the SonicWall appliances have a
long history of being shipped in non-compliant configurations.

There's a long standing issue with a configuration option designed to
support Range Protocol Headers (which is required by WSUS and the WUAgent to
download content) being disabled in shipping products.

I would suggest the SonicWall support site, and reviewing the configs and
docs of the appliance with a fine tooth comb.

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Thank you very much Lawrence! I unplugged one of my servers from our network
and configured it to work on a DSL line using a Netopia box as a router.
Tested syncing and it works! Sonicwall has to be the problem. What's weird is
how it worked for many months without a problem and all of a sudden stopped
working (we have changed nothing on the sonicwall). Do you know where I could
find detailed information on the Range Protocol Headers that WSUS needs to
function so I can work with sonicwall support to resolve this issue ? Thanks
again for all your help.
--
Gabriel Camacho


"Lawrence Garvin [MVP]" wrote:

> "Gabriel Camacho" <> wrote in message
> news:56B2A955-EEEF-43C6-AC15-...
> >I have confirmed that disk space is not an issue on either server i have
> > setup. I don't believe anything has changed in the last couple of months
> > and
> > I also reviewed my sonicwall log and confirmed that no errors or warnings
> > show up when trying to sync. Any other suggestions that might help me find
> > a
> > cause of the problem ? Thanks
>
> Just FYI.. -- following the fresh thread between you and Swarup_Gupta, who
> apparently both have SonicWall appliances -- the SonicWall appliances have a
> long history of being shipped in non-compliant configurations.
>
> There's a long standing issue with a configuration option designed to
> support Range Protocol Headers (which is required by WSUS and the WUAgent to
> download content) being disabled in shipping products.
>
> I would suggest the SonicWall support site, and reviewing the configs and
> docs of the appliance with a fine tooth comb.
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

On Mon, 27 Jul 2009 12:53:02 -0700, Gabriel Camacho <>
wrote:

>Thank you very much Lawrence! I unplugged one of my servers from our network
>and configured it to work on a DSL line using a Netopia box as a router.
>Tested syncing and it works! Sonicwall has to be the problem. What's weird is
>how it worked for many months without a problem and all of a sudden stopped
>working (we have changed nothing on the sonicwall). Do you know where I could
>find detailed information on the Range Protocol Headers that WSUS needs to
>function so I can work with sonicwall support to resolve this issue ? Thanks
>again for all your help.

I don't use Sonic Wall but this topic has been hot since WSUS 2.0 days.
http://smbiz.blogspot.com/2005/08/so...-two-play.html
May help a bit but goggle "Sonic wall Wsus" and you get hundreds of hits.

Beats me why Sonic Wall and MS have not put up a KB article on this as it has
been an issue for so long.
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.