Click to See Complete Forum and Search --> : File System Object (FSO)


tjsully
11-05-2003, 02:57 PM
I'm working with FSO in an ASP page that crawls files and folder structure on another file server. All worked fine, my users could navigate the structure and drill down to and open files. We were using NT security to limit access to this application. Several months have passed and now we get an error "Error Type:
Microsoft VBScript runtime (0x800A004C)
Path not found" My sysadmin insists no security has changed. The code hasn't changed either. I changed a copy of the code to point to the local Web server and it works. Only recent change was to IIS, we no longer allow anonymous access to the server. Anybody have any ideas?

tjsully
11-05-2003, 03:36 PM
We set IIS up to use anomyous access and set in a generic user account forthe anomyous user to use. FSO works as advertised. If I disallow anomyous access and uns integrated NT Security for accessing the web server then FSO Breaks.

PeOfEo
11-06-2003, 05:03 PM
humm maybe it is a problem with not seeing the user accounts for non annonimous logins or something. I use asp.net not asp classic first of all, but on my pages I am doing something called identity impersonate. Basically the impersinate my identity on all aspx pages so the server allows them to access those pages. Maybe if you tried something like that for the sample but bunched that all up in its own virtual directory. I do not know asp classic though so I would not be able to give you an equivilent. But there is most likely something just like it you can use if you are not doing so already. This is just a theory but you never know this might be the problem or this might simplify things atleast.

tjsully
11-07-2003, 07:28 AM
Thanx to everyone who read, and replied. We found the answer. It is an issue with NT, yup we're still running on NT 4. IIS can't send the proper credentials to a remote server when setup as Windows authentication. In fact even with using anonymous access the account and password must also exist on the remote server as a local account. Two MS articles address the issue. We either move the files that FSO will crawl to the Web server, use anonymous authentication or Basis authentication and present a login dialog to the users every time then access the Web server.

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q197/9/64.ASP&NoWebContent=1

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnauth/html/dnauth_security.asp