Hi Lubomir,

We had the same problem, determined it to be a W2000 terminal server issue. I also found this solution on the Compuserv forum. Hope it helps.

Regards,

Ken
***********
I found the info I was looking for. Yesterday I got the error when working on the LMF Terminal server interactively on VFP. I had several tables open in browse windows. I clicked from one window to another and attempted to scroll the table, I immediately got the error 'ERROR READING FILE'. If you ignore that, the next error 'ILLEGAL SEEK OFFSET' comes up. You cannot get past thee errors. Must use Task Manager to kill VFP at that point.

Here is the text from a Compuserve message of 8/24/2001 from a developer who had the exact problem. These errors were hitting his users fast and furious:

______

Here"s the registry fixes. We had support from Microsoft on this. They had a customer in the US with this problem and ROSS were investigating (ROSS = Reactive On_Site Services)

There are TWO solutions, the recommendation from MS and what we actually did. Our solution is simpler, the same patch to all machines, and it works well I don't know why our OPS department didn't do exactly what MS outlined. but it worked for us anyway... At this stage the 1104 errors have stopped.

ROSS RECOMMENDATION:
The KB does document a hotfix which did not work for this customer. The following RegKeys did however resolve the problem:

On the Windows 2000 sp2 Terminal Servers, add thefollowing register keys

HKLM\System\CCS\Services\Mrxsmb\Parameters
OpLocksDisabled
DWORD: 0x1

HKLM\System\CCS\Services\LanmanServer\Parameters
CachedOpenLimit
DWORD: 0x0

HKLM\System\CCS\Services\LanmanWorkstation\Parameters
UtilizeNTCaching
DWORD: 0x0

HKLM\System\CCS\Services\RDR\Parameters
UseWriteBehind
DWORD: 0x0

On the Windows 2000 sp2 File Server which hosts the VFP6 Application, add the following register keys

HKLM\System\CCS\Services\Lanmanserver\Parameters
EnableOpLocks
DWORD: 0x0

HKLM\System\CCS\Services\Lanmanserver\Parameters
CachedOpenLimit
DWORD: 0x0

HKLM\System\CCS\Services\LanmanWorkstation\Parameters
UtilizeNTCaching
DWORD: 0x0

________________________
Here is what we actually did and the problem went away

Apply these register keys to ALL WIN2K servers, Data Servers and Terminal servers. The spurious 1104 errors stopped and we've not seen any since

HKLM\System\CCS\Services\Mrxsmb\Parameters
OpLocksDisabled
DWORD: 0x1

HKLM\System\CCS\Services\Lanmanserver\Parameters
CachedOpenLimit
DWORD: 0x0

HKLM\System\CCS\Services\LanmanWorkstation\Parameters
UtilizeNTCaching
DWORD: 0x0

________________________________________________________


Hope this helps,

Ken








>I have the same problem on VFP 7.0 and Citrix Metaframe 1.8 for Windows. Error reading file (1104), Record is out of range (5), Invalid seek offset (1103), 2005 (error reading .SCX)
>Only when the aplication read data or program from network (file server W2000), not from local disk.
>When aplication is on local disk (local Metaframe), no problem.
>Reading off SQL data(Microsoft SQL server) is OK.
>
>
>>We are testing this now at a couple of sites, but have not experienced the problem you describe (yet!).
>>
>>Have you tried posting your question at the Citrix developer forum? (If not, you will have to register first (free) to use it):
>>
>>Register to use forum at:
>>http://apps.citrix.com/CDN/login.asp
>>Forum:
>>http://forums.citrix.com/default.asp
>>
>>
>>>I have a VFP 7.0 app that runs on Citrix Metaframe XPA Feature Release 1, Windows 2000 SP2 and the ICA client 6.01.961.
>>>
>>>Users often get "error reading file" messages when idle for 5-10 minutes or when another user wuits the application. It looks like the Citrix session is loosing the exe in memory or something like that.
>>>
>>>Before, with VFP5 and Windows NT 4.0 we never had this message.
>>>
>>>We don't have this problem on local versions, just on Citrix.
>>>
>>>TIA