Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Programs hangs only in one machine
Message
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 6
OS:
Windows 2000
Network:
Windows 2000 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01080172
Message ID:
01081699
Views:
10
>Hi there,
>
>I'm maintaining a vfp 6 app and it hangs up most of the time when executing a scan, like in the example below, sometime the process is completed after a long while.
>
>SELECT so_detail
>SCAN FOR so_number = so_header.so_number
><>
>ENDSCAN
>
>* There's an index for so_number by the way, I've re-indexed but haven't re-created the index from scratch.
>
>The problem is that these hang ups are occurring only in one machine, in the other machines the process finishes. Before this machine had no problem, but since monday this is happening, I've been trying to find out if they installed anything on the machine but user says no, I'm thinking maybe some spyware but I don't think that should have much to do with it since other parts of the software seem to be working fine, it's just the part of the software.
>
>Any ideas?
>
>Thanks.


Single machine problems are either hardware or configuration issues on the machine.

Hardware possibilities include:

Bad sectors on the hard drive
Corrupted directory on the hard drive
Network card going bad
Video card going bad
RAM going bad
Bad power/electricity getting to the machine - spikes causing data loss somewhere. Also could be a bad power supply or fans in the machine.
This particular system has RAID or other 'specialized' hardware that performs its own caching/buffering to 'speed things up' - potentially in conflict with your immediate data access needs. Replace with a 'non-specialized' system.

Configuration issues to check:

Temp file setup
(I've seen user temp folders deleted and systems spending tons of time trying to figure out where to store stuff to. I've also seen temp files set to go back out to the network somewhere which really can throw off the timing as well.)
Not enough free hard drive space and you've simply run out of room for the temp files being created.
Read-Ahead or Write-Behind caching is enabled and the workstation can't handle the load that can cause - turn them off.
Auto Disconnect is on and the 15 minute 'inactive' window has elapsed because of the 'exclusive' nature of the routine - network disconnects - bye bye...
Opportunistic locking is on at the server and the overall load of the caching is more than this particular workstation can keep up with.
Anti-Virus is on and set to autocheck everything - turn it off and test - reconfigure to ignore your application during it's 'live' search for viruses.

Good hunting!
Steven D. Supinski
The American Contractor
Santa Cruz, CA 95062
Phone: (800) 333-8435 ext 4017
Email: ssupinski@theamericancontractor.com
Previous
Reply
Map
View

Click here to load this message in the networking platform