Mysterious "Error Reading File"

[Shanachie]

The background: Pretty stable application, running for several years, frequently unpgraded but not huge changes. One feature that the client wanted was the ability to run multiple sessions. That way, while working on one customer's order, if another customer calls, the rep can minimize the currrent session, deal the the caller through a second session, and switch back to where she (usually) left off. It took some doing but I found a way to do it. Always worked fine.

Recently, the IS department decided to improve things by switching from Novell to Windows Server 2003. As soon as that was implemented, the reps started having sessions crash when more than one session was running. They get an "Error reading file" message and cannot "ignore" their way out; a series of errors follows if they don't "cancel". (I believe that these are "cascading errors", resulting from the first, not errors that are there anyway.) This never happens when there is only one session running. It can happen either to the first or the second session. It may or may not happen immediately; sometime they can go into a second session for several minutes and have no problem. A few say it only happens to them rarely. Also, I haven't been able to make it happen within the VPF development environment.

I'm convinced that this is a network problem; the client's network folks say it's application specific, not their problem.

Anybody got any ideas? I'm stumped.


TIA,
Shanachie

 

[craigber]

Hogwash to the network guys. The first rule of troubleshooting is to look at what was most recently changed.

Some things to look at:
- Make sure write caching is turned off on the server and the workstation
- Check the network cards and wiring. Make sure both are in tip top condition
- Verify the protocols being used

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com

Author, CrysDev: A Developer's Guide to Integrating Crystal Reports"

 

[darrellblackhawk]

I'd recommend adding some error traps for the run time
environment. Of course you may not get an error trap until
the second OS error fires, since this sounds like an OS
issue.

You'll need the data to prove to the IS department that
this was caused by their action, but of course, it's bad
form and counter-productive to push blame too hard down
your clients throat.

Also, you may be encountering issues regarding system
security on the file server. I've had a number of anomalous
errors to correct when I've ported older applications to
Windows 2000+ and Windows XP.

Darrell






'We all must do the hard bits so when we get bit we know where to bite'