[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 622
  • Last Modified:

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

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/iuident.cab
2) http://servername/selfupdate/au/x86/xp/en/wuaucomp.cab

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 -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly"/>
    </system.web>
</configuration>
 

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 -->

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

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.

Thanks,
TREOST


0
TREOS
Asked:
TREOS
  • 5
  • 4
1 Solution
 
LazarusCommented:
WSUS v3.0 no longer uses the web client to manage the WSUS Server. It uses it's own MMC for it. wsus.msc
They can not be on the same server.
0
 
TREOSAuthor Commented:
Hi Lazarus,

Thanks for the quick reply! I am not running WSUS 3.0 on the server. Now I have WSS 3.0 and WSUS 2.0 on the windows server 2003 sp1. WSUS 2.0 is producing the problems described in my previous post.

thanks,
treost
0
 
LazarusCommented:
I thought you had said you upgraded to WSUS 3.0, that would have broke teh WSUS 2.0. So you would need to uninstall teh 2.0 and either re-install 2.0 or just install 3.0. If I'm hearing your correctly that is.
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 
LazarusCommented:
Forgive the crappy spelling, I seem to have become dyslexic. "Teh"seems to have taken on new meaning in my typing.
0
 
TREOSAuthor Commented:
this is what i had. I had windows sharepoint services 2 and wsus 2 on the same server. I upgraded windows sharepoint services 2 to 3 while keeping wsus 2 on the same server. after the upgrade, wsus 2.0 broke!

So, you are sayin I should just uninstall and reinstall wsus 2.0 or 3.0. what will happen to my wsus 2 database on the sql server 2005

thanks,
treost
0
 
TREOSAuthor Commented:
i have been using this wsus 2 database for almost a year and a half now.

thanks,
treost
0
 
LazarusCommented:
Look at this Q&A about WSUS ans WSS:
http://www.petri.co.il/forums/showthread.php?p=74820

Not sure if this will help but... Read this WSUS 2.0 Release notes:
http://technet2.microsoft.com/windowsserver/en/library/4244109a-395a-4ff8-9989-ea55ab0964a31033.mspx?mfr=true

There are problems having them on the same server, but easy to overcome. Use this link to help you:

http://blogs.technet.com/sbs/archive/2007/05/22/trouble-installing-sharepoint-3-0-after-wsus-3-0.aspx

I realize the above is about SBS, but being as it's the Do All be all, it will probably cover it too.
0
 
TREOSAuthor Commented:
Thanks for the links, lazarus...I am still not sure why I am getting the application error message for selfupdate folder under default site. clientwebservice folder works fine under default site. Something is broken. the selfupdate folder under WSUS Administration node works just fine. You think maybe I should just save that config and then move it to the default website. Do they both have the same config?

Thanks for your help!

thanks,
treost
0
 
LazarusCommented:
Well, you could always uninstall it and re-install. It doesn't take long and its pretty easy to get back to normal.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now