Balmong
asked on
WSUSService not running, why isn't it?
I installed wsus3.0 on a server 2003 sp2 server. the WSUS console is currently displaying the following message:
In services.msc the Update Services...service is not started and when I try to the bar freezes and an error 1053 is displayed stating that the service did not respond in a timely manner accompanied by event id 7000/7009 in the event log(timeout 30000/ did not respond in a timely fashion).
The server connects to the internet via a proxy through port 8080. It can update itself manually and I created an access rule for it in ISA 2004 Firewall policy for http/Https/Kerboros udp protocol that allows the server to external. there are no other firewalls...
Any suggestions?
One or more Update Service components could not be contacted. Check your server status and ensure that Windows Server Update Services is running. Non-running services: WSUSService.
In services.msc the Update Services...service is not started and when I try to the bar freezes and an error 1053 is displayed stating that the service did not respond in a timely manner accompanied by event id 7000/7009 in the event log(timeout 30000/ did not respond in a timely fashion).
The server connects to the internet via a proxy through port 8080. It can update itself manually and I created an access rule for it in ISA 2004 Firewall policy for http/Https/Kerboros udp protocol that allows the server to external. there are no other firewalls...
Any suggestions?
Sorry, I was wrong, I am running on Server 2008 not 2003. Still, WSUS 3 should run on 2003 with at least SP1 so I'd still look at doing what I suggested.
If you're note running the latest SP of WSUS, you might also try updating to that.
If you're note running the latest SP of WSUS, you might also try updating to that.
ASKER
Kaspersky Av/space security and print server and I am trying to run the latest version, wsus3.0sp2.
Question. Is the Update Service startable if behind a firewall or is it connection dependent?
Question. Is the Update Service startable if behind a firewall or is it connection dependent?
Firewall shouldn't keep the services from starting. You might need an outbound hole for the MS servers depending on the firewall and the firewall config.
Wouldn't think that print server would be an issue, but you might try temporarily removing Kaspersky to see if that makes a difference.
Wouldn't think that print server would be an issue, but you might try temporarily removing Kaspersky to see if that makes a difference.
I would verify your WSUS settings
Verifying WSUS Server Settings
http://technet.microsoft.com/en-us/library/cc708545%28WS.10%29.aspx
You may also need to go over....
http://blogs.technet.com/b/asksbs/archive/2008/06/02/troubleshooting-multiple-errors-on-wsus-13042-13051-and-12032.aspx
Verifying WSUS Server Settings
http://technet.microsoft.com/en-us/library/cc708545%28WS.10%29.aspx
You may also need to go over....
http://blogs.technet.com/b/asksbs/archive/2008/06/02/troubleshooting-multiple-errors-on-wsus-13042-13051-and-12032.aspx
ASKER
Verified setting, all seemed fine to me andafter that I unistalled, restarted and installed again.. same thing.
I also tried to off the antivirus and connect and it was no use. Is there an easy way to verify my connection and what might be blocking it?
The internet access is through a proxy server on port 8080, does that mean whether I open a port or not for the WSUS server it will use that single port for internet access and render the others closed?
I also tried to off the antivirus and connect and it was no use. Is there an easy way to verify my connection and what might be blocking it?
The internet access is through a proxy server on port 8080, does that mean whether I open a port or not for the WSUS server it will use that single port for internet access and render the others closed?
Assuming this is the case, you should be able to approach this one of two ways. One would be to build a rule on the proxy server allowing any traffic from this server out to anywhere or at least out to the server that MS uses for WSUS updates.
The other approach would be to set the proxy configuration in WSUS so that the connection can penetrate to the INternet.
The other approach would be to set the proxy configuration in WSUS so that the connection can penetrate to the INternet.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That solved it, but I used 86400000 for the time value as mentioned here:
http://support.microsoft.com/kb/824344
IS there an explaination to why the timeout has to be adjusted for the service to work?
http://support.microsoft.com/kb/824344
IS there an explaination to why the timeout has to be adjusted for the service to work?
Balmong:
You know you set the timeout value to 24 hours (1 day) by using that value??
The service error 1053 usually occurs when there are some problems between the service you are trying to stop/pause and the Advapi32.dll file. This DLL file is part of one of the advanced API services library that supports several APIs that include several security and registry calls.
Regards,
You know you set the timeout value to 24 hours (1 day) by using that value??
The service error 1053 usually occurs when there are some problems between the service you are trying to stop/pause and the Advapi32.dll file. This DLL file is part of one of the advanced API services library that supports several APIs that include several security and registry calls.
Regards,
I'd start by looking for the obvious, what else is running, am I doing AV on this server, what kind of free resources do I have and similar things.
Next, I'd ry to completely uninstall WSUS, reboot and then reinstall.