we are on IBm websphere adn win 2003 server (sql 2005)
Anyone have any issues stopping these services /
when I try to stop websphere it times out ?
It shows as stopped, then we try to stop lawson adn it also times out.
We also have issue of webspere starting before lawson - although websphere is dependant on lawson service ? Wierd.
There are a couple of things you can do.
First, start/stop order are very important:
Start Order:
Database (for Lawson if on same machine and for LDAP if using Tivoli) LDAP (i.e. Tivoli) Lawson Websphere IIS
Reverse the order for shutdown.
Second, don't set dependencies for the services, and turn all of them to 'Manual'.
Third, use a .bat file with 'net start xxx' & 'net stop xxx' commands, where xxx are service names.
Lastly, you can increase the allowed timeout via a registry setting (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control, Create new DWORD ServicesPipeTimeout with a value representing number of milliseconds [default is 30 secs])
Thanks
We will try this, once we get our test server back from the application group.
I think the dependancies is probably the thing holding everything up and changing to manual will help on any restarts.
If one of the services is starting out of order then the dependencies are probably not set right. It can be tricky as some services may have dependencies already. I think there may be a patch that addresses the Websphere timeout as well, depending on your version. I am running LSF 9.004 / WAS 6.1 / Win 2003 / ADAM / SQL2000. I have dependencies set up in my registry and my services start and stop ok on reboot. When I do system maint. I use John's method of net start XXX in my scripts. We have 2 environments, so it was easy to test without disrupting the users - if you only have one, it can be tedious.
LSF9 works with SQL 2000?