WSUS 3 SP1 Install - Clients can't connect (Event 13042)

[Asgar]

I was having Windows Server 2003 service pack 2 on my computer and I recently installed WSUS 3 with Service Pack 1 on it as a clean install. I have put in all the required applications as well. The server is the production host of internal webpage. There are no errors at the time of installation which goes smoothly. I have configured the system the want i want it to be and synchronization is also successful and the clients are pointed to the server via group policy. But the clients are not able to connect to the server and I also get the below in Event Log:

13042 - Self-Update is not working
12002 - Reporting Web Service is not working
12032 - Server Synchronization Web Service is not working
12022 - Client Web Service is not working
12042 - SimpleAuth Web Service is not working
12052 - DSS Authentication Web Service is not working

Can anyone tell me how to solve this issue? Thanks

[spookshow]

I dont think anybody knows why self-update will not run. I have also tried installing WSUS 3 SP1 on a test server but it will not install there. I will get till 90% completion and then it will say that there seems to be an issue with the installer package and also tells that one of the components did not complete as expected. I am also not using any kind of external database. All I am doing is just letting the Wsus install the Windows Internal Database for it.

[HELLIAN]

I have found a solution for this problem that you might look into:

1. First of all open the Intenret Services Manager MMC
2. After that you need to click on the server name node at the top of the left-hand tree and choose "Modules"
3. Now you can right-click on DynamicCompressionModule and choose "Unlock" and then right-click on StaticCompressionModule and choose "Unlock"
4. After that click on WSUS Administration to select it and choose Modules
5. Now you have to right-click on DynamicCompressionModule and choose "Remove" and also right-click on StaticCompressionModule and choose "Remove"
6. After that run IISReset and re-open the WSUS Administration console and all will be fine