internetcreations
asked on
WSUS does not work at all
This is a Windows 2003 SBS server with OS SP2 and SBS SP1. All the clients disappeared from WSUS so I removed it completely and reinstalled it. Now, I get errors in the softwaredistribution log shown at the bottom of this post. Additionally, I get errors saying:
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 7/20/2009
Time: 10:36:24 AM
User: N/A
Computer: SBSWAYNE
Description:
EventType clr20r3, P1 i41wbvnfm2ht0amgvidw5cwymw
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12052
Date: 7/20/2009
Time: 10:36:13 AM
User: N/A
Computer: SBSWAYNE
Description:
The DSS Authentication Web Service is not working.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
2009-07-20 14:40:31.017 UTC Error w3wp.7 SusEventDispatcher.Dispatc
at Microsoft.UpdateServices.I
at Microsoft.UpdateServices.I
at Microsoft.UpdateServices.I
at Microsoft.UpdateServices.I
at Microsoft.UpdateServices.I
at Microsoft.UpdateServices.I
at System.Threading.ThreadHel
at System.Threading.Execution
at System.Runtime.CompilerSer
at System.Threading.Execution
at System.Threading.Execution
at System.Threading.ThreadHel
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 7/20/2009
Time: 10:36:24 AM
User: N/A
Computer: SBSWAYNE
Description:
EventType clr20r3, P1 i41wbvnfm2ht0amgvidw5cwymw
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12052
Date: 7/20/2009
Time: 10:36:13 AM
User: N/A
Computer: SBSWAYNE
Description:
The DSS Authentication Web Service is not working.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
2009-07-20 14:40:31.017 UTC Error w3wp.7 SusEventDispatcher.Dispatc
at Microsoft.UpdateServices.I
at Microsoft.UpdateServices.I
at Microsoft.UpdateServices.I
at Microsoft.UpdateServices.I
at Microsoft.UpdateServices.I
at Microsoft.UpdateServices.I
at System.Threading.ThreadHel
at System.Threading.Execution
at System.Runtime.CompilerSer
at System.Threading.Execution
at System.Threading.Execution
at System.Threading.ThreadHel
ASKER
It is WSUS version 3 SP1. I did just install it from a Microsoft download. It worked for a while.
internetcreations,
While I am not that familiar with SBS ... have you tried reinstalling the IIS Windows Component? A simple uninstall and reinstall may not be enough at this point. I mean your getting .NET and a "Web Services" error in addition to your database errors. Did you use the Windows Internal Database or did you use a Simple WSUS Installation with SQL installed?
I would say we need a little more data on exactly what chain of events occured leading up to this.
Please advise.
Naerwen
While I am not that familiar with SBS ... have you tried reinstalling the IIS Windows Component? A simple uninstall and reinstall may not be enough at this point. I mean your getting .NET and a "Web Services" error in addition to your database errors. Did you use the Windows Internal Database or did you use a Simple WSUS Installation with SQL installed?
I would say we need a little more data on exactly what chain of events occured leading up to this.
Please advise.
Naerwen
WSUS has to be installed in a separate directory on SBS. Sharepoint & OWA are already installed along with IIS, so WSUS has to be in a sub-directory, i.e. http://server/wsus
Looks like your using the WID with ... what has to be a custom port installation because of your other Web Apps. So you're using 8530. I am not sure off the top of my head but you may want to thumb through this:
http://technet.microsoft.c
... specifically the 'Configuring IIS' ... If I remember correctly you need to have the INET_*** system account allowed anonymous access to the 80 site. Even though you have a custom port the WSUS service uses the default web sit for:
"Client self-update
WSUS uses IIS to update most client computers automatically to WSUS-compatible Automatic Updates software. To accomplish this, WSUS Setup creates a virtual directory named Selfupdate under the Web site running on port 80 of the WSUS server. This virtual directory, called the self-update tree, contains the WSUS-compatible Automatic Updates software. "
===Then again===
"Using the WSUS custom Web site
If you configure WSUS on a custom port, you must have a Web site running on port 80. The Web site on port 80 does not have to be dedicated to WSUS. In fact, WSUS uses the site on port 80 only to host the self-update tree.
Malicious programs can target port 80 for HTTP traffic. If WSUS is using a custom port, you can temporarily shut down port 80 throughout your network, but still be able to distribute updates to combat malicious programs.
If you already have a Web site on the computer where you intend to install WSUS, you should use the setup option for creating a custom Web site. This option puts the WSUS Web site on port 8530. This port is not configurable"
It's not much ... but I think you're experiencing authentication errors because you are running several web apps on the same IIS installation. And, perhaps, there is conflicting permissions. MS will ALWAYS choose the more restrictive of the rules. ... That too has been said by you, I know. But I would say. Completely remove WSUS, even the separate directory make sure that you choose to remove the database. I know that option is there. This will mean that you have to start over completely, even recreating the groups.
Read the documentation from TN and that may help.
Just remember that when you reload WSUS IT WILL STOP IIS and then restart it.
That's all I got for you. Maybe someone has a better idea.
Naerwen
http://technet.microsoft.c
... specifically the 'Configuring IIS' ... If I remember correctly you need to have the INET_*** system account allowed anonymous access to the 80 site. Even though you have a custom port the WSUS service uses the default web sit for:
"Client self-update
WSUS uses IIS to update most client computers automatically to WSUS-compatible Automatic Updates software. To accomplish this, WSUS Setup creates a virtual directory named Selfupdate under the Web site running on port 80 of the WSUS server. This virtual directory, called the self-update tree, contains the WSUS-compatible Automatic Updates software. "
===Then again===
"Using the WSUS custom Web site
If you configure WSUS on a custom port, you must have a Web site running on port 80. The Web site on port 80 does not have to be dedicated to WSUS. In fact, WSUS uses the site on port 80 only to host the self-update tree.
Malicious programs can target port 80 for HTTP traffic. If WSUS is using a custom port, you can temporarily shut down port 80 throughout your network, but still be able to distribute updates to combat malicious programs.
If you already have a Web site on the computer where you intend to install WSUS, you should use the setup option for creating a custom Web site. This option puts the WSUS Web site on port 8530. This port is not configurable"
It's not much ... but I think you're experiencing authentication errors because you are running several web apps on the same IIS installation. And, perhaps, there is conflicting permissions. MS will ALWAYS choose the more restrictive of the rules. ... That too has been said by you, I know. But I would say. Completely remove WSUS, even the separate directory make sure that you choose to remove the database. I know that option is there. This will mean that you have to start over completely, even recreating the groups.
Read the documentation from TN and that may help.
Just remember that when you reload WSUS IT WILL STOP IIS and then restart it.
That's all I got for you. Maybe someone has a better idea.
Naerwen
Hi, I am checking in to monitor this question:
You should run the WSUS client diag. That will tell a story. It is the clients responsibility to check in. It is the client that pulls updates from the server. So, it is the client we should probably be targetting.
You should run the WSUS client diag. That will tell a story. It is the clients responsibility to check in. It is the client that pulls updates from the server. So, it is the client we should probably be targetting.
However, he is showing "Web Service" and .NET 2.0 runtime errors along with WID errors. This would suggest that there is a problem with the WSUS service rather than a random client.
Though I do agree, there is a WSUS diagnostics tool that is available. Not in the office now ... so I can't look it up.
Also, I'm not knockin' you CheifIT ... just respectfully disagreeing.
Thanks,
Naerwen
Though I do agree, there is a WSUS diagnostics tool that is available. Not in the office now ... so I can't look it up.
Also, I'm not knockin' you CheifIT ... just respectfully disagreeing.
Thanks,
Naerwen
Well, I do see a couple errors that wouldn't probably be the root of this problem
SP1 for 2003 server has some bugs in the TCP/IP sys file. The MTU channels were miscoded, causing intermittent Network connectivity. That problem doesn't relate to this problem, but will be a problem.
Then, I also see that he may have the misconfigured port. That problem could cause clients not to check in.
As far as the .Net errors, I beleive you have to be at a certain level in Netframework for WSUS. It will be in the prerequisites to installing WSUS, (white papers).
Furthermore, I would consider downloading to the best .NET as well as a compatible MMC console for WSUS.
It looks like a bunch of updates and a few configuration changes may considerably change the circumstances.
I do agree that > .NET is a problem, but not the sole problem in this WSUS case. So, no appologies. In fact, I think you have a pretty good observation there.
My intent was to see the overall scope of issues before recommending fixes. I agree that .NET should be updated first, then MMC, Then, Service pack 1 on the OS. Then the Service pack of WSUS or the version of WSUS. White paper prerequisites of WSUS should be followed prior to installing and configuring WSUS. So, those would prove helpful.
Your doing a fine job, and I would like to watch. I hope these comments help.
SP1 for 2003 server has some bugs in the TCP/IP sys file. The MTU channels were miscoded, causing intermittent Network connectivity. That problem doesn't relate to this problem, but will be a problem.
Then, I also see that he may have the misconfigured port. That problem could cause clients not to check in.
As far as the .Net errors, I beleive you have to be at a certain level in Netframework for WSUS. It will be in the prerequisites to installing WSUS, (white papers).
Furthermore, I would consider downloading to the best .NET as well as a compatible MMC console for WSUS.
It looks like a bunch of updates and a few configuration changes may considerably change the circumstances.
I do agree that > .NET is a problem, but not the sole problem in this WSUS case. So, no appologies. In fact, I think you have a pretty good observation there.
My intent was to see the overall scope of issues before recommending fixes. I agree that .NET should be updated first, then MMC, Then, Service pack 1 on the OS. Then the Service pack of WSUS or the version of WSUS. White paper prerequisites of WSUS should be followed prior to installing and configuring WSUS. So, those would prove helpful.
Your doing a fine job, and I would like to watch. I hope these comments help.
ASKER
This started working today without any changes on my part. I don't understand that, but it is fine now.
internetcreations,
I guess I am glad that it is working again. However, I would not be optimistic that it will sustain. There is definately a problem somewhere. And, as I have stated before, I believe it to be related to IIS or one of existing your Web Apps. To verify, you did nothing? You didn't iisreset /noforce????? Just asking ... sometimes when we troubleshoot we don't remember everything we did.
If you wish/want, I am happy to remain engaged and assist further. If so, please send the relevant event logs and also get the IIS log file and post it. If not, then no worries and I wish you the best.
Thank you,
Naerwen.
I guess I am glad that it is working again. However, I would not be optimistic that it will sustain. There is definately a problem somewhere. And, as I have stated before, I believe it to be related to IIS or one of existing your Web Apps. To verify, you did nothing? You didn't iisreset /noforce????? Just asking ... sometimes when we troubleshoot we don't remember everything we did.
If you wish/want, I am happy to remain engaged and assist further. If so, please send the relevant event logs and also get the IIS log file and post it. If not, then no worries and I wish you the best.
Thank you,
Naerwen.
There are still issues that will cause you problems.
SP1, maybe MMC console, Netframework version, ect....
SP1, maybe MMC console, Netframework version, ect....
All,
OK ... here are the MS documentation referencing the prerequisites to be installed:
Start here:
- This is MS' SBS How to Install on SBS docs: http://technet.microsoft.c
- Also, review this Technet article as it tells you exactly what is needed to have installed PRIOR to deploying WSUS 3.0: http://technet.microsoft.c
Confirm your installation meets these minimum requirements and then let us know. I would still like to see some log files when you get the chance. To date, we're still going on the initial 3 errors.
I will remain engaged until you are satisfied.
Thank you,
Naerwen
OK ... here are the MS documentation referencing the prerequisites to be installed:
Start here:
- This is MS' SBS How to Install on SBS docs: http://technet.microsoft.c
- Also, review this Technet article as it tells you exactly what is needed to have installed PRIOR to deploying WSUS 3.0: http://technet.microsoft.c
Confirm your installation meets these minimum requirements and then let us know. I would still like to see some log files when you get the chance. To date, we're still going on the initial 3 errors.
I will remain engaged until you are satisfied.
Thank you,
Naerwen
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Found this too ... not sure if it's relevant ... but have a read ... http://www.wsus.info/index.php?showtopic=8348
In addition to what Naerwen is saying:
SP1 is one of your more serious issues right now. Let me show you why>
http://support.microsoft.com/default.aspx?scid=kb;en-us;898060
SP1 is famed for intermittent network connectivity.
Naerwen provided you with some good information on prerequisites, to include netframework version, and how to install MMC console. So, I think you are armed with enough ammo to fix some discrepancies on this server.
Refer back with questions.
@Naerwen:
If you see anyone with 2003 server SP1, they should upgrade to SP2. A lot of fixes to the discrepancies in SP1 were done in SP2.
SP1 is one of your more serious issues right now. Let me show you why>
http://support.microsoft.com/default.aspx?scid=kb;en-us;898060
SP1 is famed for intermittent network connectivity.
Naerwen provided you with some good information on prerequisites, to include netframework version, and how to install MMC console. So, I think you are armed with enough ammo to fix some discrepancies on this server.
Refer back with questions.
@Naerwen:
If you see anyone with 2003 server SP1, they should upgrade to SP2. A lot of fixes to the discrepancies in SP1 were done in SP2.
CheifIT,
Thank you. I was not aware of that.
Naerwen
Thank you. I was not aware of that.
Naerwen
ASKER
thx
What procedure did you use to initially install WSUS? Did you just install it, outright?
Give the document at the following URL a read.
http://www.microsoft.com/downloads/details.aspx?FamilyID=28c43d57-2e15-47b2-9a6f-1514aa3ed05f&displaylang=en
/F