SCCM - WSUS and SQL with another server

Question

Hi

I trying to get SCCM working to have SQL/WSUS in another server:

Primary Site: (SCCM)

• Component Server
• Distribution Point
• Management Point
• Service Connection Point
• Site Server
• Site System
• SMS Provider

Site System Server (WSUS/SQL)

• Component Server
• Site Database Server
• Site System
• Software Update Point

Error Site status

• Component Server

Site Component Manager failed to reinstall 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 reinstallation in 60 minutes. To force Site Component Manager to immediately retry the reinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager.

Site Component Manager could not start the SMS_SERVER_BOOTSTRAP_XXXX service on site system "\XXXXX" to install component SMS_WSUS_CONTROL_MANAGER with the service logging on as account "". The operating system reported error 997: Overlapped I/O operation is in progress.

Possible cause: Site Component Manager does not have sufficient access rights to administer the site system.
Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system.

WCM.LOG show that:

Checking for supported version of WSUS (min WSUS 4.0)
SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 12:43:05 5488 (0x1570)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 12:43:05 5488 (0x1570)
Did not find supported version of assembly Microsoft.UpdateServices.Administration. SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 12:43:05 5488 (0x1570)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 12:43:05 5488 (0x1570)
Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701. SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 12:43:05 5488 (0x1570)
Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 12:43:05 5488 (0x1570)
STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ENDPOINTMANAGER.duck.com SITE=SOK PID=3168 TID=5488 GMTDATE=fre dec 30 11:43:05.866 2022 ISTR0="wsus.duck.com" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0 SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 12:43:05 5488 (0x1570)
Remote configuration failed on WSUS Server. SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 12:43:05 5488 (0x1570)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ENDPOINTMANAGER.duck.com SITE=SOK PID=3168 TID=5488 GMTDATE=fre dec 30 11:43:05.884 2022 ISTR0="wsus.duck.com" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0 SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 12:43:05 5488 (0x1570)
Waiting for changes for 60 minutes SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 12:43:05 5488 (0x1570)
Wait timed out after 60 minutes while waiting for at least one trigger event. SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 13:42:55 5488 (0x1570)
Timed Out... SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 13:43:05 5488 (0x1570)
Checking for supported version of WSUS (min WSUS 4.0) SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 13:43:05 5488 (0x1570)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 13:43:05 5488 (0x1570)
Did not find supported version of assembly Microsoft.UpdateServices.Administration. SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 13:43:05 5488 (0x1570)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 13:43:05 5488 (0x1570)
Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701. SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 13:43:05 5488 (0x1570)
Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 13:43:05 5488 (0x1570)
STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ENDPOINTMANAGER.duck.com SITE=SOK PID=3168 TID=5488 GMTDATE=fre dec 30 12:43:05.898 2022 ISTR0="wsus.duck.com" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0 SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 13:43:05 5488 (0x1570)
Remote configuration failed on WSUS Server. SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 13:43:05 5488 (0x1570)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ENDPOINTMANAGER.duck.com SITE=SOK PID=3168 TID=5488 GMTDATE=fre dec 30 12:43:05.948 2022 ISTR0="wsus.duck.com" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0 SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 13:43:05 5488 (0x1570)
Waiting for changes for 60 minutes SMS_WSUS_CONFIGURATION_MANAGER 2022-12-30 13:43:05 5488 (0x1570)

I have local admin and machine account in both servers.
I have reinstalled Management Point and SUP without success.

WSUS server working fine with updates, but not show up and working SCCM Server

Any idea what I can do ?

Answer 1

in the log you posted...

"
Site Component Manager could not start the SMS_SERVER_BOOTSTRAP_XXXX service on site system "\XXXXX" to install component SMS_WSUS_CONTROL_MANAGER with the service logging on as account "". The operating system reported error 997: Overlapped I/O operation is in progress.

Possible cause: Site Component Manager does not have sufficient access rights to administer the site system.
Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system.
"

Does the server known as ENDPONTMANAGER.duck.com, possibly called YourDomain\EndPointManager$ in active directory, is it nested into the local Administrators' group on the server known as wsus.duck.com, AND (if you separate those rights), does YourDomain\EndpointManager$ also have rights to the SQL installation and susdb on wsus.duck.com

Answer 2

to check sql security, you need to launch SQL Server Manager, connect to your wsus server, and look at security.

another thought... have you tried the time-honored "just reboot everything, and try again" troubleshooting step?

Answer 3

Deploying SCCM before configuring the DataBase creates issues because wsus is the not a single system it is database capability. Make sure that SQL Server is deployed before and configured as well as connection is taking place.