469,575 Members | 1,432 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,575 developers. It's quick & easy.

re-start IIS 5 work process

We have a web server that runs on Windows 2000/IIS 5. We have multiple site
of web application on the web server. Each site has it own assembly versions
of ASP.Net application. They are all developed with ASP.Net 1.0. When we
test a site of the application, it sometimes pops up stating that a file is
locked another process and can not be accessed. I try to stop the ASPNET_WP
process via task manager on the web server, the service will start up by
itself again. I often have to re-start the IIS to get rid of the file
locking issue. As I understand that IIS 5 runs on single work process, stop
work process means it will affect all the web site on the web server. My
questions are
1. What could be the possible causes of the file locking in the deployed
webserver? How to find out why?
2. Can I re-start the work process without re-starting the IIS. What's the
proper way to re-start the work process?
3. How can I configure the IIS 5 so that if any of the site has problem, it
won't affect the other site on same web server?
4. Is this issue addressed in IIS 6? If so, how to configure it?
Any help appreciated.
Henry
Nov 18 '05 #1
1 1500
Does it come when you start debugger? Make sure
you've .net framework 1.0 service pack 2 is installed
http://msdn.microsoft.com/netframewo...2/default.aspx

I believe this is the same problem as addressed in the
following knowledgebase article.
http://support.microsoft.com/?id=329065

--
Hope this helps,
Zeeshan Mustafa, MCSD
"Henry Chen" <he********@postiive.com.au> wrote in message
news:eN**************@TK2MSFTNGP12.phx.gbl...
We have a web server that runs on Windows 2000/IIS 5. We have multiple site of web application on the web server. Each site has it own assembly versions of ASP.Net application. They are all developed with ASP.Net 1.0. When we
test a site of the application, it sometimes pops up stating that a file is locked another process and can not be accessed. I try to stop the ASPNET_WP process via task manager on the web server, the service will start up by
itself again. I often have to re-start the IIS to get rid of the file
locking issue. As I understand that IIS 5 runs on single work process, stop work process means it will affect all the web site on the web server. My
questions are
1. What could be the possible causes of the file locking in the deployed
webserver? How to find out why?
2. Can I re-start the work process without re-starting the IIS. What's the
proper way to re-start the work process?
3. How can I configure the IIS 5 so that if any of the site has problem, it won't affect the other site on same web server?
4. Is this issue addressed in IIS 6? If so, how to configure it?
Any help appreciated.
Henry


Nov 18 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Craig Bailey | last post: by
11 posts views Thread by James | last post: by
10 posts views Thread by James | last post: by
8 posts views Thread by Beowulf | last post: by
8 posts views Thread by Lothar Scholz | last post: by
1 post views Thread by joost | last post: by
2 posts views Thread by sky2070 | last post: by
1 post views Thread by Brian | last post: by
1 post views Thread by Clarice Almeida Hughes | last post: by
2 posts views Thread by Frans Schmidt | last post: by
reply views Thread by suresh191 | last post: by
4 posts views Thread by guiromero | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.