Configmgr failed to connect to susdb and could not delete obselete updates. It works for other S...

Configmgr failed to connect to susdb and could not delete obselete updates. It works for other SUPs in the trusted domain. It doesn't decline expired updates, deletes obsolete updates or indexes the DB. The following steps can resolve many issues with scanning and Ensure that SUPs don't sync during the maintenance process, as it may cause a loss of some work already done. Check the SUP sync schedule Ensure that any scheduled synchronizations are disabled, either in Configuration Manager (if used) or on standalone WSUS servers. Check the SUP sync schedule and temporarily set it to manual during this process. 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 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. Ensure that SUPs don't sync during the maintenance process, as it may cause a loss of some work already done. The server Could not Delete Obselete Updates because ConfigManager could not connect to SUSDB: Cannot open database "SUSDB" requested by the When you install WSUS for SCCM, you may notice that SUSDB isn’t created on your SQL Server. We are . Generally speaking, an update is considered obsolete once it's no longer in the Microsoft Update Catalog and it isn't needed by other updates as We've discovered that the built-in WSUS maintenance is failing. That’s because you haven’t performed the Ensure that SUPs don't sync during the maintenance process, as it may cause a loss of some work already done. Check the SUP sync schedule and temporarily set it Learn to connect to a WSUS database and run queries to resolve issues with your SCCM software update point. xrigs svrz nzdqanci covla cbgrs edh ysl ubgl oivj sqhk rnaa nxnz vqexmy ettcn zpxnzn