Invalid Seek Offset errors under VFP8 runtime (SP2) and Terminal Services (Windows Server 2008 Standard)

Question

I have a VFP 8 application running on a dedicated Windows Server 2008 machine under Terminal Services.  Every once in a while, there is a spurt of Invalid Seek Offset errors, hit by several users more or less simultaneously.  For instance, this morning there were six errors between 8:54 and 9:04, then three more at 9:07, 9:16 and 9:29, spread among seven different users (two users had multiple instances of the program running, thus each had two errors seconds apart).  The last previous instance of the error was on September 3, when 9 different users hit the error between 11:39 and 11:55 am.

Internet searching has shown me several sources that agree the likely cause of the error is a loss of network connection, blamed on router, cabling, or such.  However, when I suggested this to the network support person, his answer was that there can be no connectivity issue as the users are all running Terminal Services on the same physical drive on which the application and data reside.

Every time the error hits, it winds up hitting several people - but not everyone who is logged in at the time.  (All told there are somewhere between 20 and 30 users logged in at peak times.)   And the error logs show that each of the users was in a different spot in the program, accessing different tables and different routines. 

When the error has hit, the users have logged off of the network and back on, after which they ran fine. 

Does anyone have any ideas what could be causing this?

Answer 1

Check Below Link It may be Helpful to you.

http://fox.wikis.com/wc.dll?Wiki~InvalidSeekOffsetError1103~VFP

---

Please "Mark as Answer" if this post answered your question. :)

Kalpesh Chhatrala | Software Developer | Rajkot | India

Kalpesh's Blog

Answer 2

I had already seen that FoxWiki entry - which again, is not helpful at all, unless someone can explain how there can be connectivity issues when a single machine is both hosting the Terminal Services and contains the application and data. 

The Wiki entry also says that there is an indexing issue, but how can an index cause multiple people, no two of which are sharing a particular table or index, to fail around the same time, and then let them all back in without error moments later?  And, all without interrupting other people who are using the same tables and indices?

Thanks anyway.