drtester
asked on
Problem with FoxPro application on Win2k Server in Terminal Services
Hello,
I've got a real weird problem: I've got an application written in FoxPro (recent version), that is mostly accessed by people using terminal services on the Win2k server to access it. At seemingly random times, people are kicked out of the app with an error, and often subsequent restarts of the app fail with a Windows error message (unfortunately I don't have the exact wording at the moment, but it says something about Fatal Error, no real other description or numbers).
The odd part is that it starts affecting a few handful of profiles, then seems to get worse with time. There is one profile that seems to generally always work. Even the Administrator account will do it.
If I copy the file some where else, then copy it back over itself, the problem goes away! For a while.. then a week or two later, it starts coming back.
If I access the same file through a share, and load it on a remote workstation, it runs fine.
I've checked and double-checked permissions, and all is ok. There doesn't appear to be any write-lock on the file when this problem occurs.
I've spoken with the software authors, and they said that the error is not coming from FoxPro, as their error dialog boxes look different - it is some microsoft windows error message we're seeing. Everyone is stumped. This is a fairly fresh install of Win2k Server, so there's not much else on it that could be messing up. No spyware or viruses.
Any idea what I should look for? The strange thing is that it is pretty random, and only affects certain profiles... at first. When it was bombing out, I tried creating a new profile, but still no dice, so it doesn't seem to be too tied-in to the profile data.
I've got a real weird problem: I've got an application written in FoxPro (recent version), that is mostly accessed by people using terminal services on the Win2k server to access it. At seemingly random times, people are kicked out of the app with an error, and often subsequent restarts of the app fail with a Windows error message (unfortunately I don't have the exact wording at the moment, but it says something about Fatal Error, no real other description or numbers).
The odd part is that it starts affecting a few handful of profiles, then seems to get worse with time. There is one profile that seems to generally always work. Even the Administrator account will do it.
If I copy the file some where else, then copy it back over itself, the problem goes away! For a while.. then a week or two later, it starts coming back.
If I access the same file through a share, and load it on a remote workstation, it runs fine.
I've checked and double-checked permissions, and all is ok. There doesn't appear to be any write-lock on the file when this problem occurs.
I've spoken with the software authors, and they said that the error is not coming from FoxPro, as their error dialog boxes look different - it is some microsoft windows error message we're seeing. Everyone is stumped. This is a fairly fresh install of Win2k Server, so there's not much else on it that could be messing up. No spyware or viruses.
Any idea what I should look for? The strange thing is that it is pretty random, and only affects certain profiles... at first. When it was bombing out, I tried creating a new profile, but still no dice, so it doesn't seem to be too tied-in to the profile data.
ASKER
THanks for the reply.
Memory tests check out OK.
There wouldn't be network errors on switches, because everything is running "locally", as it is when running in terminal server mode that barfs. Ironically, running it over the network works fine!
There are no errors logged in the event logger.
Any more ideas?
Memory tests check out OK.
There wouldn't be network errors on switches, because everything is running "locally", as it is when running in terminal server mode that barfs. Ironically, running it over the network works fine!
There are no errors logged in the event logger.
Any more ideas?
ASKER
The solution was never really found. I ended up moving the data to a linux server, running the app on the windows box. Works 100%, although there is a decrease in performance speed due to having to fetch the data over the network connection (from the linux box) compared to getting it locally. Gigabit ethernet helped, but still isn't the same.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I had this same problem. I would just copy to the data from the network to my computer and then back and the problem would go away.
I would run OS and Hardware diagnostics as well asn Memory tests on all related servers.
Also check for any network erros on switches etc.
Did you check the event logs on all related machines ?
I hope this helps !