I agree. Also set 'run in separate memory space' for that website in IIS.
Also, you can unload from this tab also (it's the 'directory' tab in
properties). Unload will release the memory that ASP has high jacked and
then start and stopping that website should work. Sounds like someone gave
you some bad ASP code that is eating up resources. Move the ASP code to a
floppy and burn it (or just fix it).
Running in a separate memory space and unloading the website before
stopping and starting that website should stop you from having to start and
stop the IIS admin service, therefore not letting this bad site bring down
your three good ones when you restart it daily. If you don't know how or
don't have the time to fix that ASP code, then set a CRON to start and stop
that site every couple of hours or daily.
-----Original Message-----
From: John Cesta - Lists [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 28, 2001 8:50 PM
To: CF-Server
Subject: RE: IIS/ASP and ColdFusion 4.5.1
Take a long hard look at the code in that particular ASP site.
John Cesta
ColdFusion ASP ActiveState PERL Hosting
---------------------
Includes 10 Domains
100% Browser Based Administration
--------------------------------------------
http://www.cybersmarts.net
--------------------------------------------
LogFileManager - IIS LogFile Management Tool
--------------------------------------------
http://www.serverautomationtools.com
> -----Original Message-----
> From: Steven Crozier [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 28, 2001 10:04 AM
> To: CF-Server
> Subject: IIS/ASP and ColdFusion 4.5.1
>
>
> We have a IIS 4.0 / CF 4.5.1 SP2 Web server running on Windows NT 4.0
> SP4. The server is hosting five web sites, each assigned their own IP
> number. Three of the sites are CF sites and two are ASP.
>
> We are finding that the one of the ASP sites randomly goes down giving
> the dreaded "Page cannot be displayed" error. Only the one site is
> affected and the other continue without problem (and it is always the
> same ASP site). We can still "ping" the affected site and get a
> response, but the site is dead.
>
> Stopping/Starting the site has no effect, neither does starting and
> stopping the CF service or WWW service. The whole web server must be
> shut down and restarted in order for the site to reactivate. Needless
> to say, this is a less than ideal situation!
>
> We have contacted Microsoft, and they claim it is a CF problem and will
> not help. We pressed them into helping and they are receiving process
> dumps from us on a regular basis, and they cannot find anything in the
> dumps. We contacted Allaire, and they flat out refused to help because
> it was an ASP problem.
>
> HELP! We're caught in the middle, with nowhere to turn! Has anyone
> heard of this problem before? Any suggestions on where to start looking
> or what resources are available to track down the problem? If possible,
> we would like to refrain from rewriting the site at the moment.
>
> Steven L. Crozier
> MSR Inc.
> Phone: (416) 630-3000
> Fax: (416) 630-3300
> E-mail: [EMAIL PROTECTED]
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
