Tuesday, July 5, 2016

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

1 comment:

  1. fixed my problem, thanks a lot, always helpful articles!

    ReplyDelete