ConfigMgr 2012R2 SP1 - Unable to get WSUS updates after upgrade

[surfincow]

Hello,

 

After performing the upgrade from 2012R2 to R2 SP1, I found quite a number of things broke. Application Catalog, Boot Images, Client Registration, Inventory Data, PXE to name a few. I have fixed most of them, but now as I go to push out some critical patches, I noticed that updates downloaded from WSUS since the upgrade are not making it into configuration manager.

 

Looking at the wsusctrl.log and also WCM.log, I see Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701 every 8 hours (the sync schedule)

 

I found some posts with users having similar issues. One of the suggested fixes was changing the WsusPool in IIS to use .net Framework from v.2.0 to v.4.0. I'm not sure what kind of affect this might have so I'm wondering your thoughts?

 

As far as my upgrade goes, the SQL DB test didn't have any errors. The install itself was OK; however there are some references to .Net registration with Fx 2.0, but successful registration with .Net 4.0

 

INFO: Registering F:\Program Files\Microsoft Configuration Manager\bin\x64\wsyncact.dll Configuration Manager Setup 7/28/2015 4:29:27 PM 3832 (0x0EF8)

CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\RegAsm.exe" "F:\Program Files\Microsoft Configuration Manager\bin\x64\wsyncact.dll" Configuration Manager Setup 7/28/2015 4:29:27 PM 3832 (0x0EF8)
CTool::RegisterManagedBinary: Failed to register F:\Program Files\Microsoft Configuration Manager\bin\x64\wsyncact.dll with .Net Fx 2.0 Configuration Manager Setup 7/28/2015 4:29:27 PM 3832 (0x0EF8)

CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe" "F:\Program Files\Microsoft Configuration Manager\bin\x64\wsyncact.dll" Configuration Manager Setup 7/28/2015 4:29:27 PM 3832 (0x0EF8)
CTool::RegisterManagedBinary: Registered F:\Program Files\Microsoft Configuration Manager\bin\x64\wsyncact.dll successfully Configuration Manager Setup 7/28/2015 4:29:27 PM 3832 (0x0EF8)

 

Would this indicate it failed to register with 2.0 but with 4.0 is was successful? Therefore, possibly the suggestion to change the IIS settings would be correct.. but not sure why configmgr setup didn't set that to the correct value automatically.

 

One strange thing, I can publish updates from SCUP without any issue, its just updates downloaded by WSUS from MS that are not working.

 

Any thoughts?