Cathi,

Thanks for the help.

Currently in both web server's machine.config, I have the username and password set to the admin account.

But I did try adding Impersonation to both web servers web.config with the admin username and password. I also added the ASPNET account on both web servers to Act as Part of the Operating System.

However, now I get an error message while just trying to display the ASPX page:

Server Error in '/mydir' Application.
Configuration Error
Parser Error Message: Could not create Windows user token from the credentials specified in the config file. Error from the operating system 'A required privilege is not held by the client. '


If I take the impersonation out of the web.config, then I can bring up the first page but still get the invalid path or file name when I press the query button.

Any other suggestions or help would be great.

Thanks,

Jerry



>Jerry,
>
>Have you tried using impersonation? It sounds like you re having permission problems. Try impersonating an admin user to see if that makes a difference. Then you will know why the error was occuring. See Message #682735 to see how to setup impersonation.
>
>>I am using ASP.Net to access VFP tables over a shared network drive. But when I perform the query I keep getting a "Invalid path or file name." in my Asp.Net page.
>>
>>I am using the correct UNC path. One way to tell this is that I can do a DIR from a command prompt using the UNC path.
>>
>>Also, in my machine.config, I set the user name and password to an admin account just so there is not a permission issue.
>>
>>My connection string looks like this:
>>Provider=VFPOLEDB.1;Data Source=\\\\MyDomain\\myshare\\mydir\\mydir\\
>>
>>Also, I am on a web farm, but I changed the machineKey to the same values on all the servers in the farm. So my ViewState should be set on all web servers.
>>
>>Also, I copied the dbf to a local drive on all my web servers in the farm and changed the connection string to:
>>Provider=VFPOLEDB.1;Data Source=C:\\Data\\
>>This Works great, it just won't work over the share drive.
>>
>>What else can I do to fix this?
>>
>>
>>Thanks,
>>
>>Jerry