This started a few weeks ago - let it hang out for a bit to see if it was a random blip, but unfortunately this is still happening.
I inherited this from someone who left the company abruptly, so i'm unsure unfortunately about how this was setup and haven't ran into any WSUS issues previously.
Note : if i do turn off the 2 maintenance requirements that are erroring, obviously it's fine. if i turn them back on.
CM Version : 2309
Component : SMS_WSUS_SYNC_MANAGER
Errors :
- ConfigMgr failed to connect to SUSDB and could not delete obselete updates.
- ConfigMgr failed to connect to SUSDB and could not add custom indexes.
Went to my management point and checked the WSyncmgr log
- It looks fine and connecting as it's doing some maintenance, but not indexes or some obsolete updates which is confusing as per the component status above.
- Errors
- Indexing Failed. Could not connect to SUSDB. SqlException thrown while connect to SUSDB in Server: [SERVER}com. Error Message: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:06:26 AM 25952 (0x6560)
- Indexing Failed. Could not connect to SUSDB. SqlException thrown while connect to SUSDB in Server: {SERVER}com. Error Message: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:07:25 AM 25952 (0x6560)
- Could not Delete Obselete Updates because ConfigManager could not connect to SUSDB: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) UpdateServer: adcmecm02.a-dec.com SMS_WSUS_SYNC_MANAGER 5/17/2024 4:08:56 AM 25952 (0x6560)
- Sql Exeception was thrown while attempting to delete obselete updates. Error Message: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:09:10 AM 25952 (0x6560)
I found one men
Full WSYNCmgr log for one sync this morning at 4am
Wakeup for scheduled regular sync SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:00 AM 23720 (0x5CA8)
Starting Sync SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:00 AM 23720 (0x5CA8)
Performing sync on regular schedule SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:00 AM 23720 (0x5CA8)
Read SUPs from SCF for {OMITTED}.{OMITTED}.com SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:00 AM 23720 (0x5CA8)
Found 1 SUPs SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:00 AM 23720 (0x5CA8)
Found active SUP {OMITTED}{OMITTED}.{OMITTED}.com from SCF File. SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:00 AM 23720 (0x5CA8)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS={OMITTED}.{OMITTED}.COM SITE={OMITTED} PID=23936 TID=23720 GMTDATE=Fri May 17 11:00:00.365 2024 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:00 AM 23720 (0x5CA8)
Sync Surface Drivers option is not set SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:01 AM 23720 (0x5CA8)
Synchronizing WSUS, default server is {OMITTED}{OMITTED}.{OMITTED}.com SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:01 AM 23720 (0x5CA8)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS={OMITTED}.{OMITTED}.COM SITE={OMITTED} PID=23936 TID=23720 GMTDATE=Fri May 17 11:00:01.402 2024 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:01 AM 23720 (0x5CA8)
Using account {OMITTED}\srvsmssvc to connect to WSUS Server SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:01 AM 23720 (0x5CA8)
https://{OMITTED}{OMITTED}.{OMITTED}.com:8531 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:01 AM 8480 (0x2120)
Attempting connection to WSUS server: {OMITTED}{OMITTED}.{OMITTED}.com, port: 8531, useSSL: True SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:01 AM 8480 (0x2120)
Synchronizing WSUS server {OMITTED}{OMITTED}.{OMITTED}.com ... SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:02 AM 8480 (0x2120)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:02 AM 8480 (0x2120)
sync: WSUS synchronizing categories SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:13 AM 8480 (0x2120)
sync: WSUS synchronizing updates SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:19 AM 8480 (0x2120)
sync: WSUS synchronizing updates, processed 344 out of 344 items (100%) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:49 AM 8480 (0x2120)
Done synchronizing WSUS Server {OMITTED}{OMITTED}.{OMITTED}.com SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:49 AM 8480 (0x2120)
Sync Catalog Drivers SCF value is set to : 0 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:49 AM 8480 (0x2120)
SyncGracePeriod not set, use default 120000 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:49 AM 8480 (0x2120)
Sleeping 120 more seconds for WSUS server sync results to become available SMS_WSUS_SYNC_MANAGER 5/17/2024 4:00:49 AM 8480 (0x2120)
Set content version of update source {EFCD7126-2DA5-4E15-830F-880A0266C41D} for site {OMITTED} to 17601 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:49 AM 23720 (0x5CA8)
Resetting MaxInstall RunTime for Cumulative updates. SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:49 AM 23720 (0x5CA8)
Synchronizing SMS database with WSUS, default server is {OMITTED}{OMITTED}.{OMITTED}.com SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 23720 (0x5CA8)
Third party updates are enabled, SMS sync operations will use default WSUS server exclusively. SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 23720 (0x5CA8)
STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS={OMITTED}.{OMITTED}.COM SITE={OMITTED} PID=23936 TID=23720 GMTDATE=Fri May 17 11:02:51.313 2024 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 23720 (0x5CA8)
Using account {OMITTED}\srvsmssvc to connect to WSUS Server SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 23720 (0x5CA8)
https://{OMITTED}{OMITTED}.{OMITTED}.com:8531 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 18368 (0x47C0)
Attempting connection to WSUS server: {OMITTED}{OMITTED}.{OMITTED}.com, port: 8531, useSSL: True SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 18368 (0x47C0)
Synchronizing SMS database with WSUS server {OMITTED}{OMITTED}.{OMITTED}.com ... SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 18368 (0x47C0)
sync: Starting SMS database synchronization SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 18368 (0x47C0)
requested localization languages: en SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 18368 (0x47C0)
Syncing updates arrived after 05/17/2024 00:02:42 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 18368 (0x47C0)
Requested categories: Company=Patch My PC, Company=Patch My PC, Product=Microsoft SQL Server Management Studio v18, Product=Visual Studio 2022, Product=Microsoft Application Virtualization 5.0, Product=Visual Studio 2015, Product=Office 2016, Product=PowerShell - x64, Product=Microsoft 365 Apps/Office 2019/Office LTSC, Product=.NET 6.0, Product=.NET 7.0, Product=Microsoft SQL Server 2012, Product=Visual Studio 2019, Product=Visual Studio 2017, Product=Microsoft Advanced Threat Analytics, Product=Office 2013, Product=Windows 11, Product=.NET Core 3.1, Product=.NET Core 2.1, Product=Microsoft Defender Antivirus, Product=Microsoft SQL Server 2016, Product=Microsoft SQL Server 2019, Product=Visual Studio 2005, Product=System Center Endpoint Protection, Product=Windows 10, Product=Visual Studio 2012, Product=Microsoft SQL Server 2022, Product=Windows 10, version 1903 and later, Product=.NET 5.0, Product=Microsoft Application Virtualization 4.6, Product=Visual Studio 2010, Product=Microsoft SQL Server 2017, Product=Microsoft SQL Server 2014, Product=Visual C++ Redist for Visual Studio 2012, Product=Visual Studio 2010 Tools for Office Runtime, Product=Visual Studio 2013, Product=Windows 10 LTSB, Product=Microsoft SQL Server Management Studio v17, Product=Visual Studio 2010 Tools for Office Runtime, Product=Visual Studio 2015 Update 3, Product=Visual Studio 2008, Product=Microsoft SQL Server Management Studio v19, ProductFamily=Windows Subsystem for Linux, ProductFamily=Windows Admin Center, UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Upgrades, UpdateClassification=Feature Packs, UpdateClassification=Updates, UpdateClassification=Definition Updates, UpdateClassification=Critical Updates SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 18368 (0x47C0)
Checking WSUS for third-party signing certificate... SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 18368 (0x47C0)
Getting signing certificate from WSUS server. SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 18368 (0x47C0)
WSUS signing certificate details: Thumbprint: '{OMITTED}', Start Date: '06/19/2023 11:55:01', Expiration Date: '06/19/2028 11:55:01', Issuer: 'CN=PatchMyPC Service', Subject: 'CN=PatchMyPC Service' SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 18368 (0x47C0)
Getting active WSUS signing certificate thumbprint from database. SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 18368 (0x47C0)
Found WSUS signing certificate with thumbprint {OMITTED} SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 18368 (0x47C0)
WSUS signing certificate has not changed. Thumbprint: {OMITTED} SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:51 AM 18368 (0x47C0)
Successfully downloaded and stored WSUS signing certificate with thumbprint {OMITTED}. SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:52 AM 18368 (0x47C0)
Finished checking for third-party signing certificate. SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:52 AM 18368 (0x47C0)
sync: SMS synchronizing categories SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:52 AM 18368 (0x47C0)
sync: SMS synchronizing categories, processed 0 out of 456 items (0%) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:52 AM 18368 (0x47C0)
sync: SMS synchronizing categories, processed 456 out of 456 items (100%) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:54 AM 18368 (0x47C0)
sync: SMS synchronizing categories, processed 456 out of 456 items (100%) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:54 AM 18368 (0x47C0)
sync: SMS synchronizing updates SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:54 AM 18368 (0x47C0)
SyncBatchCount not set, using default 1 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:54 AM 18368 (0x47C0)
SyncBatchMinCreationDate not set, using default 01/01/2001 00:00:00 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:54 AM 18368 (0x47C0)
sync: SMS synchronizing updates, processed 0 out of 3 items (0%) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:56 AM 18368 (0x47C0)
Synchronizing update 75b807d5-5b8a-49cc-83a3-603b6602aa61 - Security Intelligence Update for Windows Defender Antivirus - KB915597 (Version 1.411.196.0) - Current Channel (Broad) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:02:56 AM 18368 (0x47C0)
Synchronizing update 28118802-b197-4337-9825-112d7721bff9 - Security Intelligence Update for Microsoft Endpoint Protection - KB2461484 (Version 1.411.196.0) - Current Channel (Broad) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:03:04 AM 18368 (0x47C0)
Synchronizing update 2c31ad9b-64a8-4e60-9fce-6bc6df61839b - Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.411.196.0) - Current Channel (Broad) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:03:30 AM 18368 (0x47C0)
sync: SMS synchronizing updates, processed 3 out of 3 items (100%) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:09 AM 18368 (0x47C0)
sync: SMS performing cleanup SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:09 AM 18368 (0x47C0)
Removed 178 unreferenced updates SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:24 AM 18368 (0x47C0)
Done synchronizing SMS with WSUS Server {OMITTED}{OMITTED}.{OMITTED}.com SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:24 AM 18368 (0x47C0)
Set content version of update source {EFCD7126-2DA5-4E15-830F-880A0266C41D} for site {OMITTED} to 17602 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:25 AM 23720 (0x5CA8)
Resetting MaxInstall RunTime for Cumulative updates. SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:25 AM 23720 (0x5CA8)
Starting cleanup on WSUS, default server {OMITTED}{OMITTED}.{OMITTED}.com SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:26 AM 23720 (0x5CA8)
Using account {OMITTED}\srvsmssvc to connect to WSUS Server SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:26 AM 23720 (0x5CA8)
https://{OMITTED}{OMITTED}.{OMITTED}.com:8531 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:26 AM 25952 (0x6560)
Attempting connection to WSUS server: {OMITTED}{OMITTED}.{OMITTED}.com, port: 8531, useSSL: True SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:26 AM 25952 (0x6560)
Cleaning up WSUS server {OMITTED}{OMITTED}.{OMITTED}.com ... SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:26 AM 25952 (0x6560)
sync: Starting SMS database synchronization SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:26 AM 25952 (0x6560)
requested localization languages: en SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:26 AM 25952 (0x6560)
Syncing updates arrived after 05/17/2024 04:02:51 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:26 AM 25952 (0x6560)
Requested categories: Company=Patch My PC, Company=Patch My PC, Product=Microsoft SQL Server Management Studio v18, Product=Visual Studio 2022, Product=Microsoft Application Virtualization 5.0, Product=Visual Studio 2015, Product=Office 2016, Product=PowerShell - x64, Product=Microsoft 365 Apps/Office 2019/Office LTSC, Product=.NET 6.0, Product=.NET 7.0, Product=Microsoft SQL Server 2012, Product=Visual Studio 2019, Product=Visual Studio 2017, Product=Microsoft Advanced Threat Analytics, Product=Office 2013, Product=Windows 11, Product=.NET Core 3.1, Product=.NET Core 2.1, Product=Microsoft Defender Antivirus, Product=Microsoft SQL Server 2016, Product=Microsoft SQL Server 2019, Product=Visual Studio 2005, Product=System Center Endpoint Protection, Product=Windows 10, Product=Visual Studio 2012, Product=Microsoft SQL Server 2022, Product=Windows 10, version 1903 and later, Product=.NET 5.0, Product=Microsoft Application Virtualization 4.6, Product=Visual Studio 2010, Product=Microsoft SQL Server 2017, Product=Microsoft SQL Server 2014, Product=Visual C++ Redist for Visual Studio 2012, Product=Visual Studio 2010 Tools for Office Runtime, Product=Visual Studio 2013, Product=Windows 10 LTSB, Product=Microsoft SQL Server Management Studio v17, Product=Visual Studio 2010 Tools for Office Runtime, Product=Visual Studio 2015 Update 3, Product=Visual Studio 2008, Product=Microsoft SQL Server Management Studio v19, ProductFamily=Windows Subsystem for Linux, ProductFamily=Windows Admin Center, UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Upgrades, UpdateClassification=Feature Packs, UpdateClassification=Updates, UpdateClassification=Definition Updates, UpdateClassification=Critical Updates SMS_WSUS_SYNC_MANAGER 5/17/2024 4:05:26 AM 25952 (0x6560)
STATMSG: ID=6717 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS={OMITTED}.{OMITTED}.COM SITE={OMITTED} PID=23936 TID=25952 GMTDATE=Fri May 17 11:06:26.136 2024 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:06:26 AM 25952 (0x6560)
Indexing Failed. Could not connect to SUSDB. SqlException thrown while connect to SUSDB in Server: {OMITTED}{OMITTED}.{OMITTED}.com. Error Message: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:06:26 AM 25952 (0x6560)
STATMSG: ID=6717 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS={OMITTED}.{OMITTED}.COM SITE={OMITTED} PID=23936 TID=25952 GMTDATE=Fri May 17 11:07:25.699 2024 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:07:25 AM 25952 (0x6560)
Indexing Failed. Could not connect to SUSDB. SqlException thrown while connect to SUSDB in Server: {OMITTED}{OMITTED}.{OMITTED}.com. Error Message: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:07:25 AM 25952 (0x6560)
Done Indexing SUSDB. Custom indexes were created if they didn't exist previously. {OMITTED}{OMITTED}.{OMITTED}.com SMS_WSUS_SYNC_MANAGER 5/17/2024 4:07:25 AM 25952 (0x6560)
sync: SMS performing cleanup SMS_WSUS_SYNC_MANAGER 5/17/2024 4:07:25 AM 25952 (0x6560)
Cleanup processed 1086 total updates and declined 0 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:07:56 AM 25952 (0x6560)
Done Declining updates in WSUS Server {OMITTED}{OMITTED}.{OMITTED}.com SMS_WSUS_SYNC_MANAGER 5/17/2024 4:07:56 AM 25952 (0x6560)
Starting Deletion of ObseleteUpdates SMS_WSUS_SYNC_MANAGER 5/17/2024 4:07:56 AM 25952 (0x6560)
STATMSG: ID=6719 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS={OMITTED}.{OMITTED}.COM SITE={OMITTED} PID=23936 TID=25952 GMTDATE=Fri May 17 11:08:56.025 2024 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0 SMS_WSUS_SYNC_MANAGER 5/17/2024 4:08:56 AM 25952 (0x6560)
Could not Delete Obselete Updates because ConfigManager could not connect to SUSDB: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) UpdateServer: {OMITTED}{OMITTED}.{OMITTED}.com SMS_WSUS_SYNC_MANAGER 5/17/2024 4:08:56 AM 25952 (0x6560)
Sql Exeception was thrown while attempting to delete obselete updates. Error Message: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) SMS_WSUS_SYNC_MANAGER 5/17/2024 4:09:10 AM 25952 (0x6560)
0 update(s) were deleted from SUSDB in Server: \\.\pipe\MICROSOFT##WID\tsql\query Database: SUSDB SMS_WSUS_SYNC_MANAGER 5/17/2024 4:09:10 AM 25952 (0x6560)
Deletion Completed SMS_WSUS_SYNC_MANAGER 5/17/2
