How do I temporarily shut down just my website? 1

[TroyMcClure]

...Or maybe shutting it down isn't needed. The problem is that I am running standard ASP, and there is a visual basic .dll that the ASP pages call for certain functions. When I need to make a change to that dll and put a new one in the winnt\system32 directory, the file can't be copied because the website is using it.

So...There are a couple of other websites running on the IIS box that I do NOT want to shut down. So how do I 'free' that .dll so I can replace it? Prior to this I was force to shut the whole IIS down and restart it, but as I said, now there are other sites running on the server.

So do I have to shut down IIS, or is there another way to kill just the .dll process so the file can be replaced?

Thanks,
T

 

[ChrisHirst]

if only the one site is using the .dll just stop that one site running.

Chris.

Indifference will be the downfall of mankind, but who cares?

http://www.candsdesign.co.uk

A website that proves the cobblers kids adage.

http://www.cram-system.com

Nightclub counting systems

So long, and thanks for all the fish.

 

[TroyMcClure]

Thanks Chris,
I should clarify--I have several of what I call 'sites' (I guess they're actually sub-sites) all within the 'Default Web Site' of IIS. I guess I could make a separate site and put my sub-site in that, rather than the Default where everything else is.

But in the near term, can I stop an individual sub-site within the Default Web Site of IIS without stopping the other sub-sites within the Default?
--T

 

[DreXor]

for more in depth on this you may want to try this question in the IIS forum

DreX
aKa - Robert
if all else fails, light it on fire and do the happy dance!

 

[Homersim2600]

The short answer is NO. You should really look into making all of your subsites actual websites, this will clean things up for you and help you to manage them better. The only way to release the connection from the dll file is to stop the default web site, it is the default web site that holds the connection rather than the subsite. Hope this helps...

LF

 

[ChrisHirst]

forum41 BTW for IIS

but you can't shut down sub folders. quickest way will be to stop the service from the computer management console. that way it should only need to be down for a couple of minutes.



Chris.

Indifference will be the downfall of mankind, but who cares?

http://www.candsdesign.co.uk

A website that proves the cobblers kids adage.

http://www.cram-system.com

Nightclub counting systems

So long, and thanks for all the fish.

 

[DreXor]

also for testing/updating components in the past, instead of dropping the site, you can place the DLL in a new location, example :

root/components/component A/version1/original.dll
root/components/component A/version2/updated.dll

and just regsvr32 it so the registry points to it instead. then at a more opportune time ( like 2 am or something ) restart services to release the old one.

DreX
aKa - Robert
if all else fails, light it on fire and do the happy dance!

 

[Homersim2600]

DreXor,
What a great idea! You get a star!

LF

 

[DreXor]

also, with the old one on hand it's easy to do a rollback to it, and you maintain a version archive this way.

DreX
aKa - Robert
if all else fails, light it on fire and do the happy dance!

 

[Homersim2600]

WOW! Even cooler!!! Ghessh, why didn't I think of that...

LF

 

[TroyMcClure]

Thanks very much Homersim2600, I guess it was a long shot.
Drexor, I'll try to relocate/re-register the component, but the component is already in use by the site, so I'm not sure it will just drop the existing and go to the new one, but maybe a new session will, I'll check it out.
--T

 

[DreXor]

actually, even though it's in use, you can copy it to a new location, then re-register it at the new location, then stop/restart services to release the old one completely, but until you stop/restart, it'll run on the newly registered one, but wont let go of the old one.

DreX
aKa - Robert
if all else fails, light it on fire and do the happy dance!