Board index » delphi » IIS 6 ISAPI.DLL won't unload

IIS 6 ISAPI.DLL won't unload


2004-11-19 03:50:40 AM
delphi181
I ran an install of my application on an IIS 6 server to test problems that
might occur there. I wanted to replace the dll with a newer one. I was
surprised that unlike IIS 5, the DLL did not seem locked and I was able to
replace it. Trouble is, the old DLL is still executing. I tried restarting
IIS which is what I used to do with IIS 5 in order to replace the DLL. That
didn't work. Then I found someone talking about doing a "recycle" on the
app pools. That didn't work. I could try rebooting the machine, but surely
that isn't necessary.
Anyone have any ideas how to get IIS to recognize my replaced DLL?
p.s.
I have a command that shows the DLL version, so I know the version that
is responding to the web browser is not the version that I replaced it with.
The other piece of information that may be relevant is that I am running
on a Windows VM machine. I did notice that when I log in to my app, I
redirect the browser to another page using ScriptName + '/mycommand'. I was
surprised that when I ran the browser from another machine, it switched to
"localhost" instead of continuing to use the virtual machine. I think this
is a symptom of a different problem, but thought I should mention it.
 
 

Re:IIS 6 ISAPI.DLL won't unload

Things seem to be working as expected now. I changed a few things
apparently with no effect, but after a reboot of the virtual machine things
seem to be working as they should. My guess is that the problem was related
to the virtual machine. We'll see what problems today brings :-)
"Mark L. Tiede" <XXXX@XXXXX.COM>writes
Quote
I ran an install of my application on an IIS 6 server to test problems
that
might occur there. I wanted to replace the dll with a newer one. I was
surprised that unlike IIS 5, the DLL did not seem locked and I was able to
replace it. Trouble is, the old DLL is still executing. I tried
restarting
IIS which is what I used to do with IIS 5 in order to replace the DLL.
That
didn't work. Then I found someone talking about doing a "recycle" on the
app pools. That didn't work. I could try rebooting the machine, but
surely
that isn't necessary.

Anyone have any ideas how to get IIS to recognize my replaced DLL?

p.s.
I have a command that shows the DLL version, so I know the version that
is responding to the web browser is not the version that I replaced it
with.

The other piece of information that may be relevant is that I am
running
on a Windows VM machine. I did notice that when I log in to my app, I
redirect the browser to another page using ScriptName + '/mycommand'. I
was
surprised that when I ran the browser from another machine, it switched to
"localhost" instead of continuing to use the virtual machine. I think
this
is a symptom of a different problem, but thought I should mention it.


 

Re:IIS 6 ISAPI.DLL won't unload

That's why you have the Webappde{*word*81} tool, you have to build your
application as Web App De{*word*81} executable when you start your websnap
project. you can load/unload it with that tool, and when you're ready
to deploy on IIS, you have to convert it to ISAPI.
Edgar.
On Fri, 19 Nov 2004 07:38:38 -0500, "Mark L. Tiede"
<XXXX@XXXXX.COM>writes:
Quote
Things seem to be working as expected now. I changed a few things
apparently with no effect, but after a reboot of the virtual machine things
seem to be working as they should. My guess is that the problem was related
to the virtual machine. We'll see what problems today brings :-)



"Mark L. Tiede" <XXXX@XXXXX.COM>writes
news:419cfc15$XXXX@XXXXX.COM...
>I ran an install of my application on an IIS 6 server to test problems
that
>might occur there. I wanted to replace the dll with a newer one. I was
>surprised that unlike IIS 5, the DLL did not seem locked and I was able to
>replace it. Trouble is, the old DLL is still executing. I tried
restarting
>IIS which is what I used to do with IIS 5 in order to replace the DLL.
That
>didn't work. Then I found someone talking about doing a "recycle" on the
>app pools. That didn't work. I could try rebooting the machine, but
surely
>that isn't necessary.
>
>Anyone have any ideas how to get IIS to recognize my replaced DLL?
>
>p.s.
>I have a command that shows the DLL version, so I know the version that
>is responding to the web browser is not the version that I replaced it
with.
>
>The other piece of information that may be relevant is that I am
running
>on a Windows VM machine. I did notice that when I log in to my app, I
>redirect the browser to another page using ScriptName + '/mycommand'. I
was
>surprised that when I ran the browser from another machine, it switched to
>"localhost" instead of continuing to use the virtual machine. I think
this
>is a symptom of a different problem, but thought I should mention it.
>
>