WSUS3 issues on Win2008
- Can I be included in this post or do you prefer that I begin another? - I'm experiencing the same issue. Neophyte Server 2008 user so things need to be spelled out a bit more in detail than I sure you are use to. SOrry.
Here are my details:
Server 2008 Enterprise, SP2 v.113 64bit. 8GB Ram, Intel Cor 2 Duo E8400 @ 3.00 GHz.
SQL Server 2008 Config Manager does not show a service for WSUS that I can determin. I don't know how to find the admin area.
IIS was failing during start up initially so I set LogOn as Local System account and interaction with the desktop in the Services Admin. That resolved the IIS issue bit it did not resolve the WSUS issue. The messages below are after the IIS error was resolved. However - along with the WSUS info below - IIS receives this information Event:A worker process with process id of '4952' serving application pool 'WsusPool' was shutdown due to inactivity. Application Pool timeout configuration was set to 20 minutes. A new worker process will be started when needed.
I tried to remove the Windows Server Update Services (and Web Server (IIS) roles but it errors: "Setup Not Completed! The Windows Server Update Services 3.0 SP1 was not removed successfully because an error occurred."(Even if I include WSUS 3.0SP1 DB, Log files and Downloaded update files) Error Message received for WSUS = "Attempt to un-install Windows Server Update Services failed with error code 0x80070643. Fatal error during installation."
WSUS Event Info:
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
System.Net.WebException -- The request failed with HTTP status 405: Method Not Allowed.
Source
Microsoft.UpdateServices.Administration
Stack Trace:
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()
at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
at Microsoft.UpdateServices.UI.SnapIn.Common.ExtensionSnapInManager.OnInitialize()
+ System - Provider [ Name] Windows Server Update Services - EventID 7032 [ Qualifiers] 0 Level 3 Task 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2009-07-01T19:50:38.000Z EventRecordID 127629 Channel Application Computer RQDEV.trellis.dev Security - EventData The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.WebException -- The request failed with HTTP status 405: Method Not Allowed. Source Microsoft.UpdateServices.Administration Stack Trace: at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args) at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer() at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer() at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer() at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole) at Microsoft.UpdateServices.UI.SnapIn.Common.ExtensionSnapInManager.OnInitialize()
OK - so that's as much as I can do. I'm new to Server 2008 - any Server Technology for that matter so I hope this info is helpful. I've done as much as I can do as a beginner. LMK if you need more info.
Thanks in advance.
Richard (alias Q!)- DivididoLawrence GarvinMVP, Moderadormiércoles, 01 de julio de 2009 21:01Nature of issue significantly different from other issues in thread
Respuestas
Hi Lawrence,
I was able to determine that WSUS is using the Internal Database "SUSDB". However when I view it with MS SQL Server Management Studio Express (\\.\pipe\mssql$microsoft##SSEE\sql\query) the SUSDB has no tales. There is nothing to expand and view. Could this be my issue with WSUS?
Thanks,
Richard (alias Q!)
It's more likely that the account you used to connect to the database via SSMS does not have permissions to access the database. I wouldn't really worry about access to the database - the only thing that needs access is the Updates Services service, and if it can't get access, we'll know.
As for your IIS question -- it's my suspicion that your IIS issues are contributing to your WSUS issue, but I wont' know that for certain until you resolve that issue. If IIS is configured as specified in the WSUS documentation and it's working without issue, and WSUS still does not work -- then we'll be in a better position to evaluate what's not working with WSUS, and be certain that it's not an issue caused by IIS. If there's nothing else running on this machine, you might even consider starting from scratch as the safest way to ensure IIS and WSUS are installed correctly. Remove WSUS, then remove all web-related roles and features from the machine. Reboot, and then reconfigure the Web Server and related roles/features as documented in the WSUS Deployment Guide. Then reinstall WSUS.
It's not lost on me that you have already tried to uninstall them once -- unsuccessfully -- and that's probably the *best* reason why you should get them uninstalled and reinstall them. If something won't uninstall, it's because something isn't configured the way the uninstaller expects it to be - which is evidence of a bad installation. To the matter of removing a Win2008 Role that won't remove, you may need to seek assistance in the Win2008 forums to explore methodologies for dealing with that scenario.
If there's nothing else running on this server -- you might even determine it's simpler to just reinstall the whole Operating System from scratch. And, to that point, I'm curious why you were using SQL 2008 Config Manager to find the WSUS database, and whether or not IIS/WSUS are the only roles installed on this machine -- or is there other stuff installed/activated that's not been mentioned (and might be related to this issue).
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)- Marcado como respuestaRumpldRich jueves, 02 de julio de 2009 16:11
Todas las respuestas
- Note 1:
SQL Server 2008 Config Manager does not show a service for WSUS that I can determin. I don't know how to find the admin area.
WSUS v3 is installed to/with the Windows Internal Database, by default. Unless you explicitly directed the WSUS installer to install to a SQL Server 2008 instance, in which case you should already know the instance name where the database is stored, then WSUS is installed in the W.I.D. and the SQL Server Configuration Manager cannot see the W.I.D.
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009) - Note 2:
IIS was failing during start up initially so I set LogOn as Local System account and interaction with the desktop in the Services Admin.
Before it makes any sense at all to troubleshoot any WSUS issues, you need to resolve this "IIS was failing during start up" issue, and then reset the service account credentials to the correct account.
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009) - Thanks Lawerence!
Note 1: The default must have been used because I did not direct WSUS to intall to a SQL Server 2008 instance. I'll research how to confirm this and only bother you if I am unable to.
Note 2: I will also research my IIS issue in depth to see if I can resolve that issue. I'm thinking that it has something to do with account permissions and I've given full access to the Administrator account for the local machine but it doesn't fix the issue. I'll keep researching this before moving further into the WSUS problem.
However, If IIS is no longer failing diring start up with the current account credentials can I make the assumption that my WSUS issue is not related to this?
THanks,
Q! - Hi Lawrence,
I was able to determine that WSUS is using the Internal Database "SUSDB". However when I view it with MS SQL Server Management Studio Express (\\.\pipe\mssql$microsoft##SSEE\sql\query) the SUSDB has no tales. There is nothing to expand and view. Could this be my issue with WSUS?
Thanks,
Richard (alias Q!) Hi Lawrence,
I was able to determine that WSUS is using the Internal Database "SUSDB". However when I view it with MS SQL Server Management Studio Express (\\.\pipe\mssql$microsoft##SSEE\sql\query) the SUSDB has no tales. There is nothing to expand and view. Could this be my issue with WSUS?
Thanks,
Richard (alias Q!)
It's more likely that the account you used to connect to the database via SSMS does not have permissions to access the database. I wouldn't really worry about access to the database - the only thing that needs access is the Updates Services service, and if it can't get access, we'll know.
As for your IIS question -- it's my suspicion that your IIS issues are contributing to your WSUS issue, but I wont' know that for certain until you resolve that issue. If IIS is configured as specified in the WSUS documentation and it's working without issue, and WSUS still does not work -- then we'll be in a better position to evaluate what's not working with WSUS, and be certain that it's not an issue caused by IIS. If there's nothing else running on this machine, you might even consider starting from scratch as the safest way to ensure IIS and WSUS are installed correctly. Remove WSUS, then remove all web-related roles and features from the machine. Reboot, and then reconfigure the Web Server and related roles/features as documented in the WSUS Deployment Guide. Then reinstall WSUS.
It's not lost on me that you have already tried to uninstall them once -- unsuccessfully -- and that's probably the *best* reason why you should get them uninstalled and reinstall them. If something won't uninstall, it's because something isn't configured the way the uninstaller expects it to be - which is evidence of a bad installation. To the matter of removing a Win2008 Role that won't remove, you may need to seek assistance in the Win2008 forums to explore methodologies for dealing with that scenario.
If there's nothing else running on this server -- you might even determine it's simpler to just reinstall the whole Operating System from scratch. And, to that point, I'm curious why you were using SQL 2008 Config Manager to find the WSUS database, and whether or not IIS/WSUS are the only roles installed on this machine -- or is there other stuff installed/activated that's not been mentioned (and might be related to this issue).
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)- Marcado como respuestaRumpldRich jueves, 02 de julio de 2009 16:11
- For removing WSUS, you can try this step:
Made the following changes under registry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup
Value for "wYukonInstalled". if the value is set to 1, changed it to 0
Try again to uninstall WSUS.
Also, like Lawrence said, prepare a clean system to install WSUS will be better.
- Great info Lawrence. This server is stand alone and all I use it for is rnning multiple development VM's for a BizTalk solution. I use ADDS and connect VM's to the base machines domain. Pretty simple ... that is now that I know how to do it anyway. :-) It really won't kill me to perform a complete OS reinstall from scratch. Besides it's good practice...right? I think you hit the nail on the head in that it's most likely that I did not configure IIS properly before installing WSUS. I'll download the WSUS deployment guide for the next round.
Thanks for your feedback and assistance - it really helps make the learning experience more enjoyable! Each install is a little cleaner and more stable.
Best Regards,
Richard
425-367-9025 - Thanks Eric. I'm going to perform a clean OS install. And IIS will be configured per the WSUS deployment guide.
Q!
