Remote configuration failed on WSUS Server (part 3)

Another post on the error message "Remote configuration failed on WSUS Server" with ConfigMgr and WSUS. This time the error message came back multiple times, so software updates cannot be synchronized anymore. Both solution mentioned on my other blogposts weren't working here:
- Remote configuration failed on WSUS Server (part 1)
- Remote configuration failed on WSUS Server (part 2)

When looking in Site and System status the following is seen: WSUS Synchronization failed. Message: WSUS server not configured. Please refer to WCM.log for configuration error details..

When looking in WCM.log: Remote configuration failed on WSUS Server.
When looking in wsyncmgr.log: Sync failed. Will retry in 60 minutes

The solution for this is not that hard. Open WSUS console first. You will see that WSUS isn't working at the moment. "Reset Server Node" isn't helping here.
 

Open Server Manager > IIS Manager > Application Pools. You will see that Wsuspool is stopped. Starting the pool will solve the issue temporary. Don't start it yet, but configure it first!

Just open Advanced settings on Wsuspool instead, and change the memory value there. This is needed to make sure the same error will not come back after a few days.

Change the Private Memory Limit to 4GB (4000000 KB). The default value is 1843200 KB here. After that Application Pool must be started manually. When things are okay now, WSUS is working again.

Happy with this easy solution!

Source: Microsoft

Remote configuration failed on WSUS Server (part 2)

Two weeks ago I wrote a blogpost about WSUS issues after a System Center 2012 SP1 upgrade. This blogpost can be found HERE. I mentioned my environment was already provided with KB2720211 and KB2734608, and was working okay before the SP1 upgrade. Looking in the logfiles the following error messages were seen in: "Remote configuration failed on WSUS Server". Here we go again!
 
This time another message is seen in the wsyncmgr.log also, "DB Server not detected for SUP <ConfigMgr FQDN>".
 

 
In the WCM.log there's another error message seen: "Source file C:\Windows\TEMP\********.cs" could not be found. That's a nice one!
 

 
For me this did the trick:

• Assign NETWORK SERVICE permissions on the Windows\Temp folder (List Folder/Read Data & Delete) 

After that WSUS synchronisation is running fine again! This permissions are needed to let NETWORK SERVICE write to the folder.

Remote configuration failed on WSUS Server

Last week I upgraded my ConfigMgr 2012 environment to SP1. All went fine, but after the upgrade Endpoint Protection wouldn't update anymore. Strange thing is my environment was already provided with KB2720211 and KB2734608, and was working okay before the SP1 upgrade. Looking in the logfiles the following error messages were seen in: "Remote configuration failed on WSUS Server".

WindowsUpdate.log

wsyncmgr.log

WCM.log (before)


Looking on MS TechNet I found the following post: Remote configuration failed on WSUS Server.

For me this did the trick:

1) Uninstall WSUS (without database, logfiles, updates)
2) Install WSUS again + KB2720211 + KB2734608 updates
3) Reboot the server (you never know)
4) Start "Synchronize Software Updates"


WCM.log (after)

After that WSUS synchronization is working again and Endpoint Protection is up-to-date on all servers now. Good thing to know when you update your environment to SP1 I think.

Update 8-1-2013: For it seems it's a known issue in SP1 when using specific WSUS ports. Just change the ports back to the ports configured earlier on your Software Update Point and you'll be fine!