troubleshooting Question

WSS 2 to WSS 3 upgrade screwed up the WSUS 2.0 service on the same server

Avatar of TREOS
TREOS asked on
Windows Server 2003Microsoft SharePoint
9 Comments1 Solution704 ViewsLast Modified:
Hi guys,

I had WSS 2.0 and WSUS 2.0 running on a Windows 2003 SP1 server. Few days ago, I upgraded WSS 2.0 to 3.0 and it all went well. Soon after, I couldn't get WSUS 2.0 to run. They both use SQL 2005 databases. All the virtual directories under "WSUS Administration" site on port 8530 works just fine.  The webclientservice and selfupdate under default website dont work at all. I did the wsus test by opening a web browser and typing the following into the address field.

1) http://servername/selfupdate/
2) http://servername/selfupdate/au/x86/xp/en/

For the above links, I got the following error.

Server Error in '/Selfupdate' Application.

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.

Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".

<!-- Web.Config Configuration File -->

        <customErrors mode="RemoteOnly"/>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

        <customErrors mode="On" defaultRedirect="mycustompage.htm"/>

And, then I tried the following link to check if webclientservice works.

1) http://servername/webclientservice/suserverversion.xml

For this, I got the login prompt and once the credentials were entered I got the following error.

The page cannot be found
The page you are looking for might have been removed, had its name changed, or is temporarily unavailable.


Please try the following:

If you typed the page address in the Address bar, make sure that it is spelled correctly.

Open the bp-ny-dc-01 home page, and then look for links to the information you want.
Click the  Back button to try another link.
Click  Search to look for information on the Internet.

HTTP 404 - File not found
Internet Explorer  

I am not sure what's causing all these problems as I had WSUS 2.0 and WSS 2.0 both working on the same server before I upgraded WSS 2 to WSS 3 few days ago. I am totally confused and would like your guidance on getting it resolved.


Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 9 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 9 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros