WSUS Sync Error 386

I am having sync issues with WSUS 2.0. I have three WSUS servers. One server
is in each site location. One location is getting the updates from Microsoft,
and the other two locations are setup in replica mode to point to the
location that is getting the updates from Microsoft. Both WSUS
installations and configuration are setup the same in the other 2 sites.
However one location is unable to synchronize.

I get an event log error message generated after the start of the sync
process.

Event ID: 386
“Synchronization failed. Reason: The underlying connection was closed. An
unexpected error occurred on a receive..�

The other site is able to sync correctly. There is no proxy’s setup in any
site locations. However the site location that is having an issue is
connected to primary server via a WAN VPN communication link. All ports are
open through the VPN connection and have many other services running with no
issue. I am able to access it via DNS with a PING, and TRACERT. The site
location that is working is connected via a WAN PTP communication link.

Before upgrading to WSUS 2.0, we had SUS running in the same configuration
with the SUS servers running in the same manner with no sync communication
issues.

Please provide me with any information to get this issue resolved. The
other option I have not explored because of ease of system management this
way. Is to uninstall and reinstall WSUS at this location and direct it to
Microsoft. However I would like to avoid this if at all possible.

I am not sure of the communication differences in WSUS vs. SUS. I believe
that WSUS is using the BITS service. Is it possible that it is not as
forgiving as the SUS communication method when dealing with latency? This
site location is overseas and there is about a 250 MS latency difference than
the working location.

(cross-post added to WSUS NG)
"Justin" <> wrote in message
news:C16C43AD-52EA-4758-AAFF-...


Justin,

You are posting to an NNTP newsgroup using a web interface.
Depending on which portal you are using you may be able to access
the more relevant newsgroup by clicking on the other newsgroup
name which will appear in the header of my reply.

Otherwise, assuming you have default associations for NNTP news
you can copy the following URL to your Address bar and open
that newsgroup in Outlook Express.

news://msnews.microsoft.com/microsof...pdate_services


In addition, I have included all of your original message, so someone
reading this cross-posted reply may even reply to you in this newgroup
through it.


HTH

Robert Aldwinckle
---


>I am having sync issues with WSUS 2.0. I have three WSUS servers. One server
> is in each site location. One location is getting the updates from Microsoft,
> and the other two locations are setup in replica mode to point to the
> location that is getting the updates from Microsoft. Both WSUS
> installations and configuration are setup the same in the other 2 sites.
> However one location is unable to synchronize.
>
> I get an event log error message generated after the start of the sync
> process.
>
> Event ID: 386
> “Synchronization failed. Reason: The underlying connection was closed. An
> unexpected error occurred on a receive..�
>
> The other site is able to sync correctly. There is no proxy’s setup in any
> site locations. However the site location that is having an issue is
> connected to primary server via a WAN VPN communication link. All ports are
> open through the VPN connection and have many other services running with no
> issue. I am able to access it via DNS with a PING, and TRACERT. The site
> location that is working is connected via a WAN PTP communication link.
>
> Before upgrading to WSUS 2.0, we had SUS running in the same configuration
> with the SUS servers running in the same manner with no sync communication
> issues.
>
> Please provide me with any information to get this issue resolved. The
> other option I have not explored because of ease of system management this
> way. Is to uninstall and reinstall WSUS at this location and direct it to
> Microsoft. However I would like to avoid this if at all possible.
>
> I am not sure of the communication differences in WSUS vs. SUS. I believe
> that WSUS is using the BITS service. Is it possible that it is not as
> forgiving as the SUS communication method when dealing with latency? This
> site location is overseas and there is about a 250 MS latency difference than
> the working location.
>

Thanks I looked all over the web portal for the correct Discussion Group and
was unable to find it. When trying to access the group listed from the web
portal it isn't listed. I guess I will need to break out the NNTP Client..

"Robert Aldwinckle" wrote:

> (cross-post added to WSUS NG)
> "Justin" <> wrote in message
> news:C16C43AD-52EA-4758-AAFF-...
>
>
> Justin,
>
> You are posting to an NNTP newsgroup using a web interface.
> Depending on which portal you are using you may be able to access
> the more relevant newsgroup by clicking on the other newsgroup
> name which will appear in the header of my reply.
>
> Otherwise, assuming you have default associations for NNTP news
> you can copy the following URL to your Address bar and open
> that newsgroup in Outlook Express.
>
> news://msnews.microsoft.com/microsof...pdate_services
>
>
> In addition, I have included all of your original message, so someone
> reading this cross-posted reply may even reply to you in this newgroup
> through it.
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
>
> >I am having sync issues with WSUS 2.0. I have three WSUS servers. One server
> > is in each site location. One location is getting the updates from Microsoft,
> > and the other two locations are setup in replica mode to point to the
> > location that is getting the updates from Microsoft. Both WSUS
> > installations and configuration are setup the same in the other 2 sites.
> > However one location is unable to synchronize.
> >
> > I get an event log error message generated after the start of the sync
> > process.
> >
> > Event ID: 386
> > “Synchronization failed. Reason: The underlying connection was closed. An
> > unexpected error occurred on a receive..�
> >
> > The other site is able to sync correctly. There is no proxy’s setup in any
> > site locations. However the site location that is having an issue is
> > connected to primary server via a WAN VPN communication link. All ports are
> > open through the VPN connection and have many other services running with no
> > issue. I am able to access it via DNS with a PING, and TRACERT. The site
> > location that is working is connected via a WAN PTP communication link.
> >
> > Before upgrading to WSUS 2.0, we had SUS running in the same configuration
> > with the SUS servers running in the same manner with no sync communication
> > issues.
> >
> > Please provide me with any information to get this issue resolved. The
> > other option I have not explored because of ease of system management this
> > way. Is to uninstall and reinstall WSUS at this location and direct it to
> > Microsoft. However I would like to avoid this if at all possible.
> >
> > I am not sure of the communication differences in WSUS vs. SUS. I believe
> > that WSUS is using the BITS service. Is it possible that it is not as
> > forgiving as the SUS communication method when dealing with latency? This
> > site location is overseas and there is about a 250 MS latency difference than
> > the working location.
> >
>
>
>

"Justin" <> wrote in message
news:8A5B8163-5765-48A3-B053-...
> Thanks I looked all over the web portal for the correct Discussion Group and
> was unable to find it. When trying to access the group listed from the web
> portal it isn't listed. I guess I will need to break out the NNTP Client..


Or just use a different portal. E.g. under this one it is listed but only
when you figure out the right category to expand:

http://www.microsoft.com/communities...&lang=en&cr=us


Good luck

Robert
---

Thanks for the info ..


Stilll looking for answer to my question?

"Robert Aldwinckle" wrote:

> (cross-post added to WSUS NG)
> "Justin" <> wrote in message
> news:C16C43AD-52EA-4758-AAFF-...
>
>
> Justin,
>
> You are posting to an NNTP newsgroup using a web interface.
> Depending on which portal you are using you may be able to access
> the more relevant newsgroup by clicking on the other newsgroup
> name which will appear in the header of my reply.
>
> Otherwise, assuming you have default associations for NNTP news
> you can copy the following URL to your Address bar and open
> that newsgroup in Outlook Express.
>
> news://msnews.microsoft.com/microsof...pdate_services
>
>
> In addition, I have included all of your original message, so someone
> reading this cross-posted reply may even reply to you in this newgroup
> through it.
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
>
> >I am having sync issues with WSUS 2.0. I have three WSUS servers. One server
> > is in each site location. One location is getting the updates from Microsoft,
> > and the other two locations are setup in replica mode to point to the
> > location that is getting the updates from Microsoft. Both WSUS
> > installations and configuration are setup the same in the other 2 sites.
> > However one location is unable to synchronize.
> >
> > I get an event log error message generated after the start of the sync
> > process.
> >
> > Event ID: 386
> > “Synchronization failed. Reason: The underlying connection was closed. An
> > unexpected error occurred on a receive..�
> >
> > The other site is able to sync correctly. There is no proxy’s setup in any
> > site locations. However the site location that is having an issue is
> > connected to primary server via a WAN VPN communication link. All ports are
> > open through the VPN connection and have many other services running with no
> > issue. I am able to access it via DNS with a PING, and TRACERT. The site
> > location that is working is connected via a WAN PTP communication link.
> >
> > Before upgrading to WSUS 2.0, we had SUS running in the same configuration
> > with the SUS servers running in the same manner with no sync communication
> > issues.
> >
> > Please provide me with any information to get this issue resolved. The
> > other option I have not explored because of ease of system management this
> > way. Is to uninstall and reinstall WSUS at this location and direct it to
> > Microsoft. However I would like to avoid this if at all possible.
> >
> > I am not sure of the communication differences in WSUS vs. SUS. I believe
> > that WSUS is using the BITS service. Is it possible that it is not as
> > forgiving as the SUS communication method when dealing with latency? This
> > site location is overseas and there is about a 250 MS latency difference than
> > the working location.
> >
>
>
>

Justin, can you post the complete Event Log message, please?

--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
.....


"Justin" <> wrote in message
news:13F4A867-3FAF-42A1-A12C-...
> Thanks for the info ..
>
>
> Stilll looking for answer to my question?
>
> "Robert Aldwinckle" wrote:
>
>> (cross-post added to WSUS NG)
>> "Justin" <> wrote in message
>> news:C16C43AD-52EA-4758-AAFF-...
>>
>>
>> Justin,
>>
>> You are posting to an NNTP newsgroup using a web interface.
>> Depending on which portal you are using you may be able to access
>> the more relevant newsgroup by clicking on the other newsgroup
>> name which will appear in the header of my reply.
>>
>> Otherwise, assuming you have default associations for NNTP news
>> you can copy the following URL to your Address bar and open
>> that newsgroup in Outlook Express.
>>
>> news://msnews.microsoft.com/microsof...pdate_services
>>
>>
>> In addition, I have included all of your original message, so someone
>> reading this cross-posted reply may even reply to you in this newgroup
>> through it.
>>
>>
>> HTH
>>
>> Robert Aldwinckle
>> ---
>>
>>
>> >I am having sync issues with WSUS 2.0. I have three WSUS servers. One
>> >server
>> > is in each site location. One location is getting the updates from
>> > Microsoft,
>> > and the other two locations are setup in replica mode to point to the
>> > location that is getting the updates from Microsoft. Both WSUS
>> > installations and configuration are setup the same in the other 2
>> > sites.
>> > However one location is unable to synchronize.
>> >
>> > I get an event log error message generated after the start of the sync
>> > process.
>> >
>> > Event ID: 386
>> > â?oSynchronization failed. Reason: The underlying connection was
>> > closed. An
>> > unexpected error occurred on a receive..â?�
>> >
>> > The other site is able to sync correctly. There is no proxyâ?Ts setup
>> > in any
>> > site locations. However the site location that is having an issue is
>> > connected to primary server via a WAN VPN communication link. All
>> > ports are
>> > open through the VPN connection and have many other services running
>> > with no
>> > issue. I am able to access it via DNS with a PING, and TRACERT. The
>> > site
>> > location that is working is connected via a WAN PTP communication link.
>> >
>> > Before upgrading to WSUS 2.0, we had SUS running in the same
>> > configuration
>> > with the SUS servers running in the same manner with no sync
>> > communication
>> > issues.
>> >
>> > Please provide me with any information to get this issue resolved. The
>> > other option I have not explored because of ease of system management
>> > this
>> > way. Is to uninstall and reinstall WSUS at this location and direct it
>> > to
>> > Microsoft. However I would like to avoid this if at all possible.
>> >
>> > I am not sure of the communication differences in WSUS vs. SUS. I
>> > believe
>> > that WSUS is using the BITS service. Is it possible that it is not as
>> > forgiving as the SUS communication method when dealing with latency?
>> > This
>> > site location is overseas and there is about a 250 MS latency
>> > difference than
>> > the working location.
>> >
>>
>>
>>

I believe that was the complete event log message for that Event ID 386.
Since my post I had cleared the event log. However, now I am getting a
diffrent Event ID and error message when syncing. I am able to sync from
another server to the same primary server as this one being used on this
problem server to pull from. Keep in mind all of these servers were able to
sync the same way prior with SUS. All I did was upgrade to WSUS. Any help
is welcomed.

I have recieved this everyday since and always around the same time:

Event Type: Error
Event Source: WUSyncService
Event Category: None
Event ID: 101
Date: 10/30/2006
Time: 11:01:08 PM
User: N/A
Computer: SERVER
Description:
Software Update Services encountered a failure during synchronization.

View the synchronization log on this server for details of what failed
during synchronization. To view the synchronization log, go to the Software
Update Services Admin Web site (http://<YourServerName>/SUSAdmin), and click
the View synchronization log link. (Error 0x80072EFE: The connection to the
server was lost.)

User Action
Try synchronizing the server again to see if the error occurs again. To
synchronize the server, go to the Software Update Services Admin Web site,
and click the Synchronize server link. Then click the Synchronize Now button.

Additional Data
The most common reason for failed synchronization is incorrect proxy server
configuration. If you are using a proxy server, please confirm your
configuration by going to the Software Update Services Admin Web site and
clicking the Set options link. Confirm your configuration in the results pane.

For troubleshooting information, see the Microsoft Software Update Services
Deployment Guide (http://go.microsoft.com/fwlink/?LinkId=6928).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.




Also recieved this one, however I have not received it since the date listed:

Event Type: Warning
Event Source: WUSyncService
Event Category: None
Event ID: 107
Date: 10/20/2006
Time: 12:56:21 PM
User: N/A
Computer: SERVER
Description:
Software Update Services failed to load some configuration information.
Examples of configuration information include: proxy server configuration,
content location, and client locales to support. Because not all
configuration information was loaded successfully, the default settings will
be used instead.

User Action
To confirm your configuration, go to the Software Update Services Admin Web
site (http://<YourServerName>/SUSAdmin), and click the Set options link.

Additional Data
One or more errors occurred while loading the settings file
'D:\Shared\Virtual
Webs\Default\InetPub\wwwroot\autoupdate\dictionari es\settings.txt'. (Error
0x80070057: The parameter is incorrect.)

For more information about administering a server running Software Update
Services and for a list of the default values, see the Microsoft Software
Update Services Deployment Guide
(http://go.microsoft.com/fwlink/?LinkId=6928).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.



"Lawrence Garvin (MVP)" wrote:

> Justin, can you post the complete Event Log message, please?
>
> --
> Lawrence Garvin, M.S., MVP-Software Distribution
> Everything you need for WSUS is at
> http://technet2.microsoft.com/window...s/default.mspx
> And, everything else is at
> http://wsusinfo.onsitechsolutions.com
> .....
>
>
> "Justin" <> wrote in message
> news:13F4A867-3FAF-42A1-A12C-...
> > Thanks for the info ..
> >
> >
> > Stilll looking for answer to my question?
> >
> > "Robert Aldwinckle" wrote:
> >
> >> (cross-post added to WSUS NG)
> >> "Justin" <> wrote in message
> >> news:C16C43AD-52EA-4758-AAFF-...
> >>
> >>
> >> Justin,
> >>
> >> You are posting to an NNTP newsgroup using a web interface.
> >> Depending on which portal you are using you may be able to access
> >> the more relevant newsgroup by clicking on the other newsgroup
> >> name which will appear in the header of my reply.
> >>
> >> Otherwise, assuming you have default associations for NNTP news
> >> you can copy the following URL to your Address bar and open
> >> that newsgroup in Outlook Express.
> >>
> >> news://msnews.microsoft.com/microsof...pdate_services
> >>
> >>
> >> In addition, I have included all of your original message, so someone
> >> reading this cross-posted reply may even reply to you in this newgroup
> >> through it.
> >>
> >>
> >> HTH
> >>
> >> Robert Aldwinckle
> >> ---
> >>
> >>
> >> >I am having sync issues with WSUS 2.0. I have three WSUS servers. One
> >> >server
> >> > is in each site location. One location is getting the updates from
> >> > Microsoft,
> >> > and the other two locations are setup in replica mode to point to the
> >> > location that is getting the updates from Microsoft. Both WSUS
> >> > installations and configuration are setup the same in the other 2
> >> > sites.
> >> > However one location is unable to synchronize.
> >> >
> >> > I get an event log error message generated after the start of the sync
> >> > process.
> >> >
> >> > Event ID: 386
> >> > â?oSynchronization failed. Reason: The underlying connection was
> >> > closed. An
> >> > unexpected error occurred on a receive..â?�
> >> >
> >> > The other site is able to sync correctly. There is no proxyâ?Ts setup
> >> > in any
> >> > site locations. However the site location that is having an issue is
> >> > connected to primary server via a WAN VPN communication link. All
> >> > ports are
> >> > open through the VPN connection and have many other services running
> >> > with no
> >> > issue. I am able to access it via DNS with a PING, and TRACERT. The
> >> > site
> >> > location that is working is connected via a WAN PTP communication link.
> >> >
> >> > Before upgrading to WSUS 2.0, we had SUS running in the same
> >> > configuration
> >> > with the SUS servers running in the same manner with no sync
> >> > communication
> >> > issues.
> >> >
> >> > Please provide me with any information to get this issue resolved. The
> >> > other option I have not explored because of ease of system management
> >> > this
> >> > way. Is to uninstall and reinstall WSUS at this location and direct it
> >> > to
> >> > Microsoft. However I would like to avoid this if at all possible.
> >> >
> >> > I am not sure of the communication differences in WSUS vs. SUS. I
> >> > believe
> >> > that WSUS is using the BITS service. Is it possible that it is not as
> >> > forgiving as the SUS communication method when dealing with latency?
> >> > This
> >> > site location is overseas and there is about a 250 MS latency
> >> > difference than
> >> > the working location.
> >> >
> >>
> >>
> >>
>
>
>

"Justin" <> wrote in message
news:964CD39A-405D-4D58-AA38-...
>I believe that was the complete event log message for that Event ID 386.
> Since my post I had cleared the event log. However, now I am getting a
> diffrent Event ID and error message when syncing. I am able to sync from
> another server to the same primary server as this one being used on this
> problem server to pull from. Keep in mind all of these servers were able
> to
> sync the same way prior with SUS. All I did was upgrade to WSUS. Any
> help
> is welcomed.

Your original post stated this:

> >> >I am having sync issues with WSUS 2.0. I have three WSUS servers. One
> >> >server
> >> > is in each site location. One location is getting the updates from
> >> > Microsoft,
> >> > and the other two locations are setup in replica mode to point to the
> >> > location that is getting the updates from Microsoft. Both WSUS
> >> > installations and configuration are setup the same in the other 2
> >> > sites.
> >> > However one location is unable to synchronize.
> >> >
> >> > I get an event log error message generated after the start of the
> >> > sync
> >> > process.
> >> >
> >> > Event ID: 386


> I have recieved this everyday since and always around the same time:
>
> Event Type: Error
> Event Source: WUSyncService
> Event Category: None
> Event ID: 101
> Date: 10/30/2006
> Time: 11:01:08 PM
> User: N/A
> Computer: SERVER
> Description:
> Software Update Services encountered a failure during synchronization.

But /THIS/ is not a WSUS v2.0 service. This is a /SUS/ v1 service!

So... WHICH product do you actually have installed???

--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
.....

Sorry for my confusion...
I assumed WUSyncService was related to the WSUS services. All of these
servers had SUS running prior to the upgrade and migration to WSUS. We did
the upgrade and migration based of the Technet posted instructions here:
http://go.microsoft.com/fwlink/?linkid=49070.

Below are the details that appear in effected WSUS server after the the
failed attempt to sync:
WebException: The underlying connection was closed: An unexpected error
occurred on a receive.
at System.Web.Services.Protocols.WebClientProtocol.Ge tWebResponse(WebRequest
request)
at
System.Web.Services.Protocols.HttpWebClientProtoco l.GetWebResponse(WebRequest
request)
at System.Web.Services.Protocols.SoapHttpClientProtoc ol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.UpdateServices.Internal.Authorization.Do wnstreamServerAuthorizationProxy.GetAuthorizationC ookie(String
accountName, String accountGuid, String location)
at
Microsoft.UpdateServices.Internal.Authorization.Do wnstreamServerAuthorizationPlugIn.GetAuthorization Cookie(Uri url, String parameter)
at
Microsoft.UpdateServices.Internal.Authorization.Do wnstreamServerAuthorizationPlugIn.GetAuthorization Cookie(String url, String parameter)
at
Microsoft.UpdateServices.ServerSync.ServerSyncLib. Authenticate(AuthorizationManager
authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie
cookie, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.Se

And here is the correct messages from the event log:
Event Type: Information
Event Source: Windows Server Update Services
Event Category: Synchronization
Event ID: 381
Date: 11/1/2006
Time: 7:00:00 PM
User: N/A
Computer: SERVER
Description:
A scheduled synchronization was started.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Synchronization
Event ID: 386
Date: 11/1/2006
Time: 7:01:53 PM
User: N/A
Computer: SERVER
Description:
Synchronization failed. Reason: The underlying connection was closed: An
unexpected error occurred on a receive..

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

"Justin" <> wrote in message
news:CF50D0E9-0833-4916-BBEC-...
> Sorry for my confusion...
> I assumed WUSyncService was related to the WSUS services. All of these
> servers had SUS running prior to the upgrade and migration to WSUS. We
> did
> the upgrade and migration based of the Technet posted instructions here:
> http://go.microsoft.com/fwlink/?linkid=49070.

But.. have you disabled the /SUS/ servers, yet?

If not.. that's why the WUSyncService is still running.

--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
.....