Sync failure isssue. Failed to connect to the SQL Server, connection type: SMS ACCESS.

Question

Hello,

Hope everyone is doing well and good.

We are facing sccm sync issue from one of the replica server (Untrusted forest) to its upstream server.

WCM.log:

Using szusa\saprxxx credentials for network connections SMS_WSUS_CONFIGURATION_MANAGER 10/09/2021 13:27:22 3284 (0x0CD4)
Attempting connection to WSUS server: USVMDMZXXX..., port: 8531, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/09/2021 13:27:22 3284 (0x0CD4)
Successfully connected to server: USVMDMZXXX...,, port: 8531, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/09/2021 13:27:22 3284 (0x0CD4)
Verify Upstream Server settings on the WSUS Server USVMDMZXXX..., SMS_WSUS_CONFIGURATION_MANAGER 10/09/2021 13:27:22 3284 (0x0CD4)
No changes - WSUS Server settings are correctly configured and Upstream Server is set to USVMOPSCCMXX. SMS_WSUS_CONFIGURATION_MANAGER 10/09/2021 13:27:22 3284 (0x0CD4)

***** Failed to connect to the SQL Server, connection type: SMS ACCESS. SMS_WSUS_CONFIGURATION_MANAGER 10/09/2021 13:27:22 3284 (0x0CD4)
IsSafeToGetSCF: Failed to get SQL connection SMS_WSUS_CONFIGURATION_MANAGER 10/09/2021 13:27:22 3284 (0x0CD4)
Info: Currently Site P02 is initializing Site Control Data. Can't get Master SCF from database at this time. Will try later. SMS_WSUS_CONFIGURATION_MANAGER 10/09/2021 13:27:22 3284 (0x0CD4)
For USVMOPSCCMXX, failed to get master SCF SMS_WSUS_CONFIGURATION_MANAGER 10/09/2021 13:27:22 3284 (0x0CD4)
CWSUSConfigManager::ConnectWMI() - Failed to connect to USVMOPSCCMXX. SMS_WSUS_CONFIGURATION_MANAGER 10/09/2021 13:27:22 3284 (0x0CD4)**

Wsycmgr.log

sync: Replica WSUS synchronizing categories
Sync failed: UssInternalError: SoapException: Fault occurred~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS SMS_WSUS_SYNC_MANAGER 11/09/2021 00:25:00 15984 (0x3E70)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=USVMOPSCCMXX SITE=P02 PID=10688 TID=15984 GMTDATE=Sat Sep 11 05:25:00.489 2021 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" ISTR1="UssInternalError: SoapException: Fault occurred~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X80131500 SMS_WSUS_SYNC_MANAGER 11/09/2021 00:25:00 15984 (0x3E70)
Sync failed. Skipping USVMDMZXXX SMS_WSUS_SYNC_MANAGER 11/09/2021 00:25:00 15984 (0x3E70)

Some couple of troubleshooting method I tried but it didn't help

Stop the WSUS Service. Remove the WSUS website and wsus app pool, Rename the WSUS content folder to old and run the wsusutil post install cmdline with existing SUSDB settings.

Ensured that ConfigMgr WebServer certificate assciated with WSUS adminstration site and verified the SSL settings to all WSUS virtual directories.

Ran the wsusutil Configuressl cmdline to enable the SSL setting.

Restart the WSUS service and SQL service and reboot the site system in SZ domain.

Restart the WCM and WSUS configuration Manager component in primary site server.

Tried to initiate the sync from WSUS console from SZ replica server to upstream server. But unfortunately the sync is failed from WSUS console

Is anything related to SQL?? Is anyone help us to spot the root cause for this problem.

Answer 1

Hi @Dinesh Vinay ，

Yes, it might be related with SQL Server problem. We could try these solution:

1. Review the immediately preceding status messages from this component about SQL Server errors.
2. Verify that this computer can reach the SQL Server computer.
3. Verify that SQL Server services are running.
4. Verify that the site can access the site database.
5. Verify that the site database, transaction log, and tempdb are not full.

And we might need to get a SQL admin to help us to solve this problem.

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Anything in wsusctrl log?