Link to home
Start Free TrialLog in
Avatar of Starr Duskk
Starr DuskkFlag for United States of America

asked on

How to stop a webservice from running

I have a webservice that ran with a bug in it. The web service is still running and I'd like to stop it from continuing to loop.

I am using Windows Server 2012R2 and IIS Version 8.5. It is a Windows Web Server.

I have stopped the website. I have stopped the application pool. I have waited a few minutes before restarting them.

But the webservice still keeps running in the background.

I have not reboot the box, but that is the next thing I am considering.

Any ideas? Thanks!
Avatar of zc2
zc2
Flag of United States of America image

Why just not kill the w3wp.exe process?

If the service is the only application on the server, restart the whole IIS by executing the command "iisreset" (as Administrator).
Avatar of Starr Duskk

ASKER

okay, I googled that:

At the command prompt type “taskkill /IM w3wp.exe /F”. Press Enter.

How do I start it up again though?
oh, I was reading this about it.
https://nathondalton.wordpress.com/2013/04/15/quick-tip-how-to-kill-net-worker-process/

It says it is a task, so I was thinking, I should just be able to kill the IIS Worker Process in the task manager?

Looks like there are 3 running. But I don't know enough about it to know I'm not going to break something.

What is the IIS Worker Process?
SOLUTION
Avatar of zc2
zc2
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks! I don't know if that didn't kill the process or if I have something else going on. It's still creating the bogus records as though it is still running. So back to the drawing board.
When you stop a WP, it will be started again if the IIS still receives requests to the app.
I found this method is being called elsewhere in the code, not in the webservice, so that is what is triggering the failed records also.

I'll have to publish the fix tonight and hopefully we'll be all good.

Thanks!
Was glad to help!