Can't Stop a service

[smurfer]

I am tring to stop a service on nt 4.0 server, however the stop button is grayed out, and if I click the startup properties button to change to manual from auto, it says the database service is locked? Can I stop this service somehow or unlock it?
THanks,
sm

 

[ntnet]

What exactly is the service ?
Please be more specific...
You mentionned "the database service is locked"...
What do you see running in task manager ?
Are there dependent services ? S. Gagner
MIS
A+ MCP

 

[smurfer]

The service is IBM Websphere. It does not appear that anything is running in task manager that is using this application, it is sort of a stand alone piece.

 

[pbxman]

You dont have proper permissions to stop the service. Apparently, another admin started the service under a different account. If you need access, add yourself "System" permissions, and logon at the machine as a local admin account.
NOTE: any dependencies will need their own respective login permissions as well.

 

[smurfer]

pbxman,
I am actually logging into the machine as the administrator, which is the same account used to start the service. (Only ID used on this server). Could it still somehow be a permissions issue?
sm

 

[pbxman]

Yes - it is still a permissions issue. Are you able to view the properties of the service? Such as "logon as.xxxxxxx. Box"...is that blank, or is it filled with ******* etc.."

You need domain admin permissions to access the domain account in which the permission to stop the service resides. Make sense? It ay not be a local account that runs the service...

 

[smurfer]

Yes I am able to view those permissions, modify them etc. I am loggin in as domain admin, this machine only has 2 accts on it, local admin and domain admin, both with same rights. Strange thing is, after stopping IIS and restarting the machine (repeating this a few times), the service suddenly stopped on it's own. This is actually the second time I have seen this happen on this machine, (how I knew to keep restarting), I do not believe this machine and this app were installed and configured properly as it had not worked as planned since I took it over. Anyway, it is resolved now, thank you for your assistance, and hopefully with further research I can find out why it happens this way..
thanks again,
sm