A
Andrew Fisher
Hi all,
Thought I would mention this as I could only find 1 reference to it on
a web page and having just experienced the problem the more references
with solutions will hopefully help others.
Like many people out there in corporate dev land, I am running IIS on
my workstation as a temporary development environment before moving it
to a production or proper staging server. Like many people also, I
have had virus software put on my computer [NAV in this case].
Recently they included a feature to disable scripts that are being run
which is nice as it slows down things like VBS virii etc. All of a
sudden code that used to work nicely stopped. Needless to say this
caused some panic and like any programmer the first thought was that
it was my code to blame, not something in the virus software that had
been running in the background for some time.
The bug, if you like, is that IIS will just hang when you run a script
that does ANYTHING with the FSO - kind of like sending it it into an
unterminated while loop. NAV doesn't tell you about it even though
from its settings it indicates it should pop up and ask you to
authorise execution. When this happens, you can't restart IIS - you'll
have to do a full reboot of the machine.
The solution is simple, though undocumented. Go into NAVs settings and
completely switch off Script Blocking. Whilst this will leave your
machine somewhat more open to malicious code, until Symantec can write
something properly we don't have any choice. You will need to do a
full system restart for the change to take effect.
This is the case for Win2K and WinXP running any version of IIS using
the FSO and all versions of NAV that use liveUpdate to pull down new
definitions and components.
I hope this helps.
Cheers
AndrewF
Thought I would mention this as I could only find 1 reference to it on
a web page and having just experienced the problem the more references
with solutions will hopefully help others.
Like many people out there in corporate dev land, I am running IIS on
my workstation as a temporary development environment before moving it
to a production or proper staging server. Like many people also, I
have had virus software put on my computer [NAV in this case].
Recently they included a feature to disable scripts that are being run
which is nice as it slows down things like VBS virii etc. All of a
sudden code that used to work nicely stopped. Needless to say this
caused some panic and like any programmer the first thought was that
it was my code to blame, not something in the virus software that had
been running in the background for some time.
The bug, if you like, is that IIS will just hang when you run a script
that does ANYTHING with the FSO - kind of like sending it it into an
unterminated while loop. NAV doesn't tell you about it even though
from its settings it indicates it should pop up and ask you to
authorise execution. When this happens, you can't restart IIS - you'll
have to do a full reboot of the machine.
The solution is simple, though undocumented. Go into NAVs settings and
completely switch off Script Blocking. Whilst this will leave your
machine somewhat more open to malicious code, until Symantec can write
something properly we don't have any choice. You will need to do a
full system restart for the change to take effect.
This is the case for Win2K and WinXP running any version of IIS using
the FSO and all versions of NAV that use liveUpdate to pull down new
definitions and components.
I hope this helps.
Cheers
AndrewF