SCCM 2012 will not Sync with WSUS Server, Event ID 6703 Source SMS Server

Question

I have read, read, read many forums/posts about this issue however I cannot find one that solves my issue.

Setup:

1 Server running 2008 R2 with SCCM installed. We will call it SRV1.

2nd Server running 2008 R2 running our WSUS. We will call it SRV2.

I pointed my Software Update Point role to the 2nd server, when I try to sync all updates I get the following error:

On 7/11/2012 7:38:58 AM, component SMS_WSUS_SYNC_MANAGER on computer SRV1.domain reported:   WSUS Synchronization failed.

 Message: WSUS server not configured. Please refer to WCM.log for configuration error details..

 Source: CWSyncMgr::DoSync.

  The operating system reported error 2147500037: Unspecified error

Log Name: Application
Source: SMS Server
Event ID 6703
Level: Error
User N/A
Task Category: SMS_WSUS_SYNC_MANAGER

Now I added SRV1 Computer object to SRV2's Local Admin group to see if this will help, no it failed.

SRV1 Domain functional level is 2008 Native mode so I saw that SSL needed to be enabled on SRV2 for WSUS to work with SRV1.
I created my Certificate and enabled SSL but now I cannot even open WSUS console on SRV1 or my PC.

I imported the certificate to SRV1 but that still fails.

I confirmed BITS was set to automatic and service has started.

On SRV1 (SCCM 2012) I added the Application Catalog Web Service Point and App Catalog Website Point.

Should those 2 services be on SRV2 since it has the SUP role?

The reason I ask this is because I get 2 other errors in my Event Log pertaining to those services:

Log Name:      Application
Source:        SMS Server
Date:          7/11/2012 8:05:39 AM
Event ID:      1037
Task Category: SMS_SITE_COMPONENT_MANAGER
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SRV1.domain

Description:
On 07/11/12 08:05:39, component SMS_SITE_COMPONENT_MANAGER on computer SRV1.Domain reported:  Site Component Manager could not access site system "\\SRV2.DOMAIN". The operating system reported error 2147942405: Access is denied.

Possible cause: The site system is turned off, not connected to the network, or not functioning properly.
Solution: Verify that the site system is turned on, connected to the network, and functioning properly.

Possible cause: Site Component Manager does not have sufficient access rights to connect to the site system.
Solution: Verify that the Site Server's computer$ account has administrator rights on the remote site system.

Possible cause: Network problems are preventing Site Component Manager from connecting to the site system.
Solution: Investigate and correct any problems on your network.

Possible cause: You took the site system out of service and do not intend on using it as a site system any more.
Solution: Remove this site system from the list of site systems for this site. The list appears in the Site Systems node of the Administrator console.

Log Name:      Application
Source:        SMS Server
Date:          7/11/2012 8:05:47 AM
Event ID:      1016
Task Category: SMS_AWEBSVC_CONTROL_MANAGER
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SRV1.Domain

Description:
On 07/11/12 08:05:47, component SMS_SITE_COMPONENT_MANAGER on computer SRV1.Domain reported:  Site Component Manager failed to install this component on this site system.

Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in  minutes. To force Site Component Manager to immediately retry the installation, stop and restart Site Component Manager using the Configuration Manager Service Manager.

I have been trying to fix this issue for 4 days now and no luck, any help would be greatly appreciated!

Answer 1

Please, show the WCM.log

Answer 2

The following guide is for CM 2007 and I don't think any significant change in ConfigMgr 2012. I think, you may just go back and confirm every thing is in place or not.

http://www.windows-noob.com/forums/index.php?/topic/812-install-a-sup-on-remote-server/ 

---

Anoop C Nair - @anoopmannur :: MY Site:  www.AnoopCNair.com :: FaceBook:  ConfigMgr(SCCM) Page :: Linkedin:  Linkedin<

Answer 3

CM12 Guide:

WSUS, SUP

And in my experience, please check auto-config proxy in IE . If check the proxy boxes in the SUP, it fails there also.

Answer 4

Any recommendations of a log viewer for better formatting?

Notepad is all jumbled up.

Answer 5

CMTrace.exe  in ...:\Program Files\Microsoft Configuration Manager\tools

Answer 6

did you find a solution to this problem?

Answer 7

Hello. i've been experiencing the same exact issue with sccm 2012 + wsus

did the OP find a solution ?

thanks.

Answer 8

Is your WSUS also remote? Are you also seeing "Site Component Manager could not access site system "\\SRV2.DOMAIN". The operating system reported error 2147942405: Access is denied."?

---

Torsten Meringer | http://www.mssccmfaq.de

Answer 9

I never did find the solution for it. My WSUS was on a remote server at the time. I reinstalled SCCM 2012 as I had other issues and installed the WSUS on the SCCM server as well. I had some issues with the SCCM being the SUP so I run both separate for now. I think I had some issues with the GPOs affecting my clients pointing to the SUP. I never went back to test it again as I moved on to other projects and this was no longer a priority.

Wish I had some info to help the rest of you out but I just couldnt figure it out myself.

Answer 10

I am having the same issue here

Windows 2008 R2 Server

WSUS 3.0 SP2 & SCCM 2012

WCM Log File:

Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONFIGURATION_MANAGER 12/20/2012 11:04:20 AM 356 (0x0164)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 12/20/2012 11:04:20 AM 356 (0x0164)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONFIGURATION_MANAGER 12/20/2012 11:04:20 AM 356 (0x0164)
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.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.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)~~   --- End of inner exception stack trace ---~~   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)~~   at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)~~   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)~~   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)~~   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)~~   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)~~   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)~~   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)~~   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)~~   at System.Net.ConnectStream.WriteHeaders(Boolean async)~~   --- End of inner exception stack trace ---~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONFIGURATION_MANAGER 12/20/2012 11:04:20 AM 356 (0x0164)
Remote configuration failed on WSUS Server. SMS_WSUS_CONFIGURATION_MANAGER 12/20/2012 11:04:20 AM 356 (0x0164)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=UAEDXB-MEP.NationalLogistics.com SITE=DXB PID=1528 TID=356 GMTDATE=Thu Dec 20 07:04:20.714 2012 ISTR0="UAEDXB-MEP.NationalLogistics.com" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 12/20/2012 11:04:20 AM 356 (0x0164)

Application Event Log:

Log Name:      Application
Source:        SMS Server
Date:          12/20/2012 12:10:02 PM
Event ID:      6703
Task Category: SMS_WSUS_SYNC_MANAGER
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      UAEDXB-MEP.NationalLogistics.com
Description:
On 12/20/2012 12:10:02 PM, component SMS_WSUS_SYNC_MANAGER on computer UAEDXB-MEP.NationalLogistics.com reported:   WSUS Synchronization failed.
 Message: WSUS server not configured. Please refer to WCM.log for configuration error details..
 Source: CWSyncMgr::DoSync.
  The operating system reported error 2147500037: Unspecified error

Event Xml:
<Event xmlns=
  <System>
    <Provider Name="SMS Server" />
    <EventID Qualifiers="49152">6703</EventID>
    <Level>2</Level>
    <Task>73</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-12-20T08:10:02.000000000Z" />
    <EventRecordID>1847</EventRecordID>
    <Channel>Application</Channel>
    <Computer>UAEDXB-MEP.NationalLogistics.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>CWSyncMgr::DoSync</Data>
    <Data>WSUS server not configured. Please refer to WCM.log for configuration error details.</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>On 12/20/2012 12:10:02 PM, component SMS_WSUS_SYNC_MANAGER on computer UAEDXB-MEP.NationalLogistics.com reported:  </Data>
    <Data> The operating system reported error 2147500037: Unspecified error
</Data>
  </EventData>
</Event>

is there any updates to this issue?

Answer 11

"System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host
--- End of inner exception stack trace ---~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~"

That's most likely caused by the network or proxy etc ... netsh winhttp show proxy can be used to display proxy settings.

---

Torsten Meringer | http://www.mssccmfaq.de

Answer 12

I ran the "netsh winhttp show proxy"

Current WinHTTP proxy settings:

Direct access (no proxy server).

I have also double checked to make sure there is no proxy configured.

ATM WSUS is sucsessfully connected to the Microsoft Upstream server and can sync updates with the server.

The only issue I am facing is SCCM does not want to sync.

Answer 13

I reinstalled both WSUS and SCCM 2012, I am getting the same error in the Event Log but a diffrent one in WCM log.

WCM Log:

Waiting for changes for 1 minutes SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:37:34 PM 1708 (0x06AC)
Wait timed out after 1 minutes while waiting for at least one trigger event. SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:34 PM 1708 (0x06AC)
Timed Out... SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:39 PM 1708 (0x06AC)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:39 PM 1708 (0x06AC)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:39 PM 1708 (0x06AC)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:39 PM 1708 (0x06AC)
Successfully connected to server: UAEDXB-MEP.NationalLogistics.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:39 PM 1708 (0x06AC)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:39 PM 1708 (0x06AC)
WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:39 PM 1708 (0x06AC)
Successfully connected to server: UAEDXB-MEP.NationalLogistics.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:39 PM 1708 (0x06AC)
Successfully got update categories from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:50 PM 1708 (0x06AC)
Successfully connected to server: UAEDXB-MEP.NationalLogistics.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:50 PM 1708 (0x06AC)
Successfully got update classifications from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:50 PM 1708 (0x06AC)
Successfully connected to server: UAEDXB-MEP.NationalLogistics.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:50 PM 1708 (0x06AC)
Successfully got update languages from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:50 PM 1708 (0x06AC)
Successfully connected to server: UAEDXB-MEP.NationalLogistics.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:55 PM 1708 (0x06AC)
Not yet ready to set WSUS Server subscription as returned by WSUS Server. Will try again. SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:56 PM 1708 (0x06AC)
This error is transient and will be retried in 1 minutes. SMS_WSUS_CONFIGURATION_MANAGER 1/17/2013 3:38:56 PM 1708 (0x06AC)

Answer 14

Did anyone ever get this fixed?  I got this error after applying KB2720211.  Reinstalling SUP and WSUS does not fix it.   Installed a fresh copy on Server 2012 didn't go so well either.

Answer 15

Same error is logged after upgrade SCCM 2012 RTM to SP1 .I've applied KB2734608 on SCCM server and its fixed this issue  

More info you can find here  http://seneej.com/2013/06/24/sms_wsus_sync_manager-wsus-synchronization-is-failed-event-id-6703-sms-server-sms_site_component_manager-event-id-1037-sms-server/

Answer 16

i had the same issue,

i have applied 

KB2720211

KB2734608

after words it will take some time to fix, may you can wait 3/4 hours. in my case.

it fixed my issue.

you can check more about it in my Blog

www.aniyanetworks.net

Answer 17

I was getting this same message on all the clients in my domain.

What I found was that the WSUS install on my SCCM server would not open and I was unable to Reset the Node. The services also stopped running Automatically at reboot. Since I don't store any information in WSUS and it is all stored in SCCM I removed the WSUS Role from the server (including the WSUS Database) then reboot and then reinstalled the WSUS role.

SCCM saw it right away and since it was in the same location as the old WSUS SCCM did not require any reconfiguration. As soon as I rebooted and Opened WSUS to finish the Post install setup my clients started communication right away.

Hope this helps