Export (0) Print
Expand All

Troubleshooting Software Update Point Configuration Issues

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2

This section provides information about troubleshooting software update point issues in Configuration Manager 2007.

After creating an active software update point, the configuration failed on WSUS server entry is written to the WSM.log file or the WSUS not configured entry is written to wsyncmgr.log on the site server in <ConfigMgrInstallationPath>\Logs. In Component Status, status message ID 6703 is displayed for the SMS_WSUS_SYNC_Manager component when synchronization fails.

Possible Solution

Windows Server Update Services (WSUS) running on the active software update point for child primary sites must not be configured as a replica server. Open the WSUS administration console, click Options, and then click Update Source and Proxy Server. On the Update Source tab, verify that the This server is a replica of the upstream server setting is not enabled. If it is enabled, clear the setting and then click OK. WSUS Configuration Manager should be able to configure the WSUS server, and WSUS Synchronization Manager should be able to initiate WSUS synchronization after this setting has been cleared.

After the active software update point is installed, WSUS Control Manager connects to WSUS running on the software update point to configure the WSUS settings. There is a known issue where the WsusPool in Internet Information Services (IIS) stops responding and must be restarted. When the WsusPool is in this state, WSUS Control Manager will write an error message similar to Server was unable to process request and the error code 0x80131401 is written to WSUSCtrl.log on the software update point. The following are sample entries when this condition exists:

Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111

Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=2.0.0.0, Major Version = 0x20000, Minor Version = 0x0

The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.6000.1)

System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.IO.FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)~ STATMSG: ID=7000 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONTROL_MANAGER" SYS=NOVAPHYB4N05 SITE=U44 PID=4456 TID=4344 GMTDATE=Fri Aug 10 00:34:58.312 2007 ISTR0="NOVAPHYB4N05" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes

System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.IO.FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)~

STATMSG: ID=7003 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONTROL_MANAGER" SYS=NOVAPHYB4N05 SITE=U44 PID=4456 TID=4344 GMTDATE=Fri Aug 10 00:34:58.421 2007 ISTR0="NOVAPHYB4N05" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

Failures reported during periodic health check by the WSUS Server NOVAPHYB4N05. Will retry check in 1 minutes

Waiting for changes for 1 minutes

Possible Solution

Restart the WsusPool application pool in IIS. In the Internet Information Services (IIS) Manager, navigate to the Application Pools node, right-click WsusPool, click Stop, right-click WsusPool, and then click Start.

For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft