SCCM Software Update Sync Fails with 0x80131500

Question

_{Tuesday, July 4, 2017 4:40 PM}

Hi Experts, 

In our Environment software update sync is getting failed with error 0X80131500, we have a primary site and few secondary sites is reporting to the primary site. Synchronization was working fine till last week but all of sudden this week we started to face this issue. 

as per the WCM log we are not see any errors but in wsyncmanager.log we are getting the below given log. 

"Sync failed: Unknown: TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy' threw an exception. > System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)~~at System.Runtime.Remoting.RemotingServices.AllocateUninitializedObject(RuntimeType objectType). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"

"STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=******** SITE=** PID=19444 TID=19320 GMTDATE=Tue Jul 04 16:23:44.823 2017 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" ISTR1="Unknown: TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy' threw an exception. > System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No connection could b" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0"

and after this step this goes for retry and this process continues for every one hour. herewith below find the log file details. 



Kindly suggest on what could be issue and how this can be fixed. 

Thanks & regards

Balaji S

All replies (4)

_{Tuesday, July 11, 2017 6:47 PM ✅Answered}

Hi Jason, 

yes we were able to connect without issues, from primary with FQDN, Short name & IP we are able to ping and it is working fine. 

But the issue is resolved now we have re-started the wsus services in primary server and saw that the issue is fixed. 

i hope if you are facing the above given issue the best option would be to restart the wsus services. 

Thanks for all the help. 

Balaji S

_{Tuesday, July 4, 2017 6:52 PM}

Have you performed any troubleshooting like ensuring that the ports are open, the DNS name resolution is working, that the WSUS services are started on the secondary site servers, that you can ping them, etc.?

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Wednesday, July 5, 2017 10:56 AM}

Hi Jason, 

We have checked wsus services is running in the server and all the ports were open, from primary we are able to ping all the secondary without issues. 

But still we are seeing the issue. 

thanks 

balaji S

_{Wednesday, July 5, 2017 3:40 PM}

What are you using to ping? IP, short name, FQDN?

If you open the WSUS console on the WSUS instance in the primary site, can you connect to the WSUS instance in the secondary site?

Jason | http://blog.configmgrftw.com | @jasonsandys