Finally I have it solved. It seemed that with the latest Anti Virus update
from Norton Anti Virus, some script-blocking mechanism is installed as well
(after a prompt). For regular script files it warns you, but you have the
option to run them anyway (if you are sure about the content). However,
this mechanism seems to block ASP scripts utilizing the FileSystemObject
all together, without any warning or log at all (as far as I have
discovered, that is).
Things appear to be working again, now the anti virus is no longer updated.
Terminal Services didn't have anything to do with it. Just a coincidence.
The machine rebooted after the install, after which the auto update feature
of the virus software was run....... :-(
Just thought I'd let you guys know in case you run in to this yourself as well.
At 09:59 AM 3/18/2001 -0500, you wrote:
>The only case that I can think of that FSO might have problems is on
>hidden or otherwise protected files. Try uninstalling the Terminal
>Services(if possible) and see if the page runs again.
>From: Imar Spaanjaars [mailto:Imar@S...]
>Sent: Saturday, March 17, 2001 1:04 PM
>To: How To
>Subject: FileSystemObject and rights
>On one of our development servers we recently got Windows Terminal
>installed. After the program was installed, we noticed some strange
>behavior related to user rights.
>Before it was installed, we had an archiving page that used the
>FileSystemObject to move a bunch of files from one directory to a couple
>others. Now this page won't run anymore. It seems as if the page does
>have enough rights to run the FileSystemObject and access the
>Is anybody aware of this situation? I have checked all the proper rights
>the directories, synchronized the IUSR password etc etc but nothing
>I have a strong feeling that Terminal Services has something to do with
>because it does something to IIS when it gets installed.
>Thanks in advance,