SCCM & WSUS error

[mike]

Log Name: Application

Source: SMS Server

Date: 7/8/2009 2:09:58 PM

Event ID: 6703

Task Category: SMS_WSUS_SYNC_MANAGER

Level: Error

Keywords: Classic

User: N/A

Computer: SCCM Server Name

Description:

On 7/8/2009 2:09:58 PM, component SMS_WSUS_SYNC_MANAGER on computer computername reported: SMS WSUS Synchronization failed.

Message: UssCommunicationError: WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did n.

Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAct

ion.SyncWSUS.

The operating system reported error 2148734464:

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="SMS Server" />

<EventID Qualifiers="49152">6703</EventID>

<Level>2</Level>

<Task>73</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2009-07-08T19:09:58.000Z" />

<EventRecordID>39292</EventRecordID>

<Channel>Application</Channel>

<Computer>computername</Computer>

<Security />

</System>

<EventData>

<Data>Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSync

Action.SyncWSUS</Data>

<Data>UssCommunicationError: WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did n</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>On 7/8/2009 2:09:58 PM, component SMS_WSUS_SYNC_MANAGER on computer sccm server name reported: </Data>

<Data> The operating system reported error 2148734464: </Data>

</EventData>

</Event>

 

SCCM 2007 SP 1 Win2K8 with WSUS

WSUS was working fine without any issues until about 3 weeks ago when this error kept popping up very now and then. Came across a suggestion to remove the FQDN from the site settings of the SUP. (Site DB>Site Managemnet>Site>Site Settings>Site Systems>ConfigMgr software update point) I removed the role and re-added the role without the FQDN and the WSUS has been updating without issues for 2 days now.

 

Not sure why it was working then stopped (maybe anyone has an idea) but hopefully this will help others.

[bdazle]

Had the same issue this morning and came across this thread only to find no replies.

 

The fix for me was that last month we changed Primary Site>Site Settings>Site Systems> %servername% >ConfigMgr Software Update Point.

 

We had changed the proxy to our new ISA servers and enabled *use credentials to connect to the proxy server* with a service account. As soon as a pointed it back to our old proxy server (which didnt require authentication) the components status went back to OK.