Hello:
Having trouble with a virtual NAS and moving our Web Connection Server to a Windows file server.
Our App works when running the VFP server manually. When we use IIS in COM or File mode the server hangs.
Application pools look right; Identity is "LocalSystem".
Read write access to temp folder and InetPub folder looks right.
What am I missing?
Thanks,
Josh
We worked through this offline and it turns out that the issue here was permissions.
Scenario is:
COM Servers were loaded using the SYSTEM account, with the FoxPro Web Connection COM Server trying to access resources on a remote file share over the network. Local SYSTEM doesn't have rights on a remote machine so the server was hanging.
Additionally server didn't have Unattended Mode enabled in the configuration so the file access failure resulted in a File Open Dialog which effectively hung the server.
Steps to fix:
- Turn on Unattended Mode
- Run application and get the real error - Unable to access file
- Fix Application Pool Identity to an Domain (or remote server ) account with rights to access the folder on the remote.
+++ Rick ---
+++ Rick ---
re: Moving Web connection 5.70 to new server Josh Klein
Rick Strahl
Apr 10, 2020 @ 09:56am
The application pool identity change to our domain user account worked in seeing the data on a share on our server, thanks. Unfortunately, it did not work on a SCO Unix share, a Samba drive that we need.
We use a NET USE command in a batch file configure in the Local Computer Policy/Computer Configuration/Scripts/Startup setting.
Josh
The Samba share is on a Unix domain with a different user. Is there a way to have the IIS application pool identity see two users?
Josh
re: Moving Web connection 5.70 to new server Rick Strahl
Josh Klein
Apr 10, 2020 @ 01:55pm
The Samba share is on a Unix domain with a different user. Is there a way to have the IIS application pool identity see two users?
No. You can't. You can only be logged in as one user obviously.
But... you can certainly create a new user that has rights to both the Windows folders/box and the Samba drive.
Also remember that drive mapping has to be done as part of the Application startup - the machine's drive mapping done on the INTERACTIVE account is not visible to the SYSTEM account. So the drive mapping if you do it either has to be done in a custom startup profile (that also gets fired by SYSTEM) or - probably better - you have to map the drive as part of the startup routine for the application (in yourServer::OnLoad()).
Alternately you need to reference the remote drive using UNC syntax:
\\192.168.50.200\share
+++ Rick ---
