WSUS_MANAGER Fails After Integration w/FEP 2010 Installation
WSUS is failing now that FEP2010 integration is installed: New SCCM setup (replacing a prrof of concept that went well, and which setup was well documented...so the re-build should have been good) System is Windows Server 2008R2/SCCM 2007 R3/SQL Server 2008 (not-R2) System was up for a few days, including a Pilot deployent of Software Updates. NOTE: This Pilot included me selecting my Products in Software Updates, which I could see in the WSUS Console (I only looked at the WSUS after this failure, but it does tell me that my SCCM control of WSUS was working at one point) I then installed (serversetup.exe) the SCCM/Forefront Endpoint Protection 2010 integration. Problem: Now SMS_WSUS_CONFIGURATION_MANAGER and SMS_WSUS_CONTROL_MANAGER are lit up all Red with Errors in the Site Status screen and I notice that my SCCM changes no longer roll down to the WSUS native console (again, I realize WSUS console should not be used, I'm only using this to notice that something ain't right.) Any ideas? The only changes between the good status and failure are: Installation of KB2271736 (required for FEP) Setting to Automatic-start the Windows Server "SQL Agent" (required by FEP) FEP 2010 serversetup.exe running Now WSUS is in the toilet...
June 16th, 2011 7:12am

None of the above should have any influence on your WSUS server. You need to look at the wcm.log and wsusctrl.log to start troubleshooting.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund
Free Windows Admin Tool Kit Click here and download it now
June 16th, 2011 7:51am

Great, and now it's working with a reboot (the fift time is the trick!) I was getting: Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111~ $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 11:14:20.592 2011 Eastern Daylight Time><thread=3996 (0xF9C)> Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001~ $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 11:14:20.594 2011 Eastern Daylight Time><thread=3996 (0xF9C)> The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 11:14:20.595 2011 Eastern Daylight Time><thread=3996 (0xF9C)> Failed to create instance of Microsoft.SystemsManagementServer.WSUS.WSUSServer. error = The parameter is incorrect.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 11:14:20.597 2011 Eastern Daylight Time><thread=3996 (0xF9C)> Remote configuration failed on WSUS Server.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 11:14:20.598 2011 Eastern Daylight Time><thread=3996 (0xF9C)> STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=XSCCM1 SITE=CCP PID=2312 TID=3996 GMTDATE=Thu Jun 16 15:14:20.600 2011 ISTR0="XSCCM1" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 11:14:20.600 2011 Eastern Daylight Time><thread=3996 (0xF9C)> I am now getting: File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 12:54:51.506 2011 Eastern Daylight Time><thread=3756 (0xEAC)> Successfully connected to server: XSCCM1.CCS.LOCAL, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 12:54:51.521 2011 Eastern Daylight Time><thread=3756 (0xEAC)> Subscribed Update Categories <?xml version="1.0" ?>~~<Categories>~~ <Id>7c40e8c2-01ae-47f5-9af2-6e75a0582518</Id>~~ <Id>5cc25303-143f-40f3-a2ff-... Subscribed Update Classifications <?xml version="1.0" ?>~~<Classifications>~~ <Id>e6cf1350-c01b-414d-a61f-263d14d133b4</Id>~~ <Id>e0789628-ce08-4437-be74- Configuration successful. Will wait for 1 minute for any subscription or proxy changes~ $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 12:54:51.697 2011 Eastern Daylight Time><thread=3756 (0xEAC)> I did absolutely nothing to correct this except delete all the *.log files and reboot.
June 16th, 2011 12:58pm

Great, and now it's working with a reboot (the fift time is the trick!) I was getting: Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111~ $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 11:14:20.592 2011 Eastern Daylight Time><thread=3996 (0xF9C)> Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001~ $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 11:14:20.594 2011 Eastern Daylight Time><thread=3996 (0xF9C)> The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 11:14:20.595 2011 Eastern Daylight Time><thread=3996 (0xF9C)> Failed to create instance of Microsoft.SystemsManagementServer.WSUS.WSUSServer. error = The parameter is incorrect.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 11:14:20.597 2011 Eastern Daylight Time><thread=3996 (0xF9C)> Remote configuration failed on WSUS Server.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 11:14:20.598 2011 Eastern Daylight Time><thread=3996 (0xF9C)> STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=XSCCM1 SITE=CCP PID=2312 TID=3996 GMTDATE=Thu Jun 16 15:14:20.600 2011 ISTR0="XSCCM1" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 11:14:20.600 2011 Eastern Daylight Time><thread=3996 (0xF9C)> I am now getting: File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 12:54:51.506 2011 Eastern Daylight Time><thread=3756 (0xEAC)> Successfully connected to server: XSCCM1.CCS.LOCAL, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 12:54:51.521 2011 Eastern Daylight Time><thread=3756 (0xEAC)> Subscribed Update Categories <?xml version="1.0" ?>~~<Categories>~~ <Id>7c40e8c2-01ae-47f5-9af2-6e75a0582518</Id>~~ <Id>5cc25303-143f-40f3-a2ff-... Subscribed Update Classifications <?xml version="1.0" ?>~~<Classifications>~~ <Id>e6cf1350-c01b-414d-a61f-263d14d133b4</Id>~~ <Id>e0789628-ce08-4437-be74- Configuration successful. Will wait for 1 minute for any subscription or proxy changes~ $$<SMS_WSUS_CONFIGURATION_MANAGER><Thu Jun 16 12:54:51.697 2011 Eastern Daylight Time><thread=3756 (0xEAC)> I did absolutely nothing to correct this except delete all the *.log files and reboot.
Free Windows Admin Tool Kit Click here and download it now
June 16th, 2011 12:58pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics