Hello - I have two servers both with distinctive install configurations. However, on both servers, the exact same errors occur during installation. I have gone through the Microsoft Step by Step guide and all roles/components are installed. The first server is an upgrade from 2003 x64 and running as a Hyper-V server and running the Symantec SEP client. The second server is a fresh install of 2008 x64 running as a physical server and is not running any antivirus software at the moment.
The installation gets to the end and when it tries to run the WSUS wizard, I get a box that says, "An unexpected error occurred, and this wizard must be closed. You may restart the WSUS Server Configuration Wizard from the Options page in the WSUS 3.0 console." I can launch the WSUS console, but when I try to connect to the WSUS server, it says it cannot connect. I check the WSUS event logs and see the following:
The DSS Authentication Web Service is not working.
The SimpleAuth Web Service is not working.
The Client Web Service is not working.
The Server Synchronization Web Service is not working.
The API Remoting Web Service is not working.
The Reporting Web Service is not working.
Self-update is not working.
The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console.
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
I'm at a loss. I've tried everything I can think of and tried everything I can find on the Internet but all attempts and suggestions fail. I'm truly beginning to think it is an R2 issue but I can't find anything that supports that.