I agree with your assessment that the virtual server environment is probably not the cause of the problem.
In general I strongly recommend against the use of shared drive letters, because the configuration is too brittle. Things can easily break if you change the user, or use a system service. We therefore don't have much (any?) experience with NET USE calls in conjunction with FoxWeb. I would not be surprised if it simply does not work when running FoxWeb as a service. Another possibility is that UAC is to blame.
FoxWeb Support Team
Sent by Jeff Grippe on 09/24/2012 09:21:20 AM:
1. It does correct itself and we have been looking for network issues that we can address and solve although we haven't been able to find any.
2. We have used both UNC path's and mapped drives with no effect on the problem. For most of what we do, we are using UNC path's.
We think (although we aren't sure) that the problem began when we went from physical to virtual with the server. There is no reason that the virtual server should be the source of the problem.
As far as you know, is there any reason why a batch file that call's NET USE wouldn't run from a script? Is there something I should do to get it to run? It works fine in the VFP command box but I'm getting no result when I call it from a PRG that is called from an FWX script.
Sent by FoxWeb Support on 09/21/2012 05:51:42 PM:
Does the problem correct itself eventually, or do you need to reboot, or restart FoxWeb? If the file corrects itself, I would check the network itself.
My assumption is that you are using UNC paths (\\Server\ShareName\Path\File) instead of mapped drives. You should never use mapped drives with services.
FoxWeb Support Team
Sent by Jeff Grippe on 09/21/2012 04:56:54 PM:
There are long periods where it works fine otherwise my web users would kill me.
When it is failing to open files, I have tried putting in code that calls ShellExecute to capture the NET USE information to a text file and log it.
While I can run the script just fine from a command window, when it is run as part of the script, nothing ever gets captured.
The error log is showing me VFP Error 1 (file does not exist) for files that clearly do exist.
Instead of simply USEing them, I have been using the FILE function to detect if they exist. I keep looking for them for 10 seconds. If FILE still returns .f., I execute the code that attempts to copy the NET USE information and then I let the USE execute anyway so that I get a copy in the error log.
I'm open to any suggestions as to how to better diagnose the problem.
Sent by FoxWeb Support on 08/28/2012 03:48:34 PM:
I doubt that this issue is specific to FoxWeb running in a VM. Under normal circumstances, I would have guessed that there is a permissions problem, but given the intermittent nature this does not seem to be the case.
Could it be a networking issue? What is the nature of the "intermittency"? Is it really random from request to request, or do you get periods during which file access consistently fails, followed by times when it works fine?
Are there any differences between the periods when things are working and when they are not, such as the FoxWeb operational mode (system service/regular application)?
FoxWeb Support Team
Sent by Jeff Grippe on 08/28/2012 09:24:13 AM:
We did a P2V conversion of our FoxWeb server and it is now running as a VM. For the most part it works well but we have an issue related to connecting to our file server which we did not have when FoxWeb (and IIS) were running on a physical box.
In the error log, we will see error 1, which is ...does not exist.
The statement causing the error is a USE statement and the DBF that it is attempting to USE does exist.
It is an intermittent problem so we are find it hard to diagnose.
Do you have any information about problems with running FoxWeb on a VM?
We are running:
VFP 7 SP 1
Win Server 2003 SP 2
100 MB Buffer Mem. Size
Thank you for your help