Problem - Clipper systems in Terminal Services 1

[Guest_imported]

Hi everybody,

Need some help here. I have some problems running a clipper application in Terminal Services Servers. From times in times, the users receives error messages when the application try to open some DBF´s files - the DBFs and EXE files stays in a shared folder, on a file server. The application opens these files in shared mode. I have 50-100 concurrents conections trying to use this application.
The users receive this message when the problem occurs:

Error DBFNTX/1012 Corruption Detected <Path and File Name>
Dos Error 5

and the Terminal Server is Windows 2000.

If anyone have a clue of what the hell is going on, please help.

 

[ProfReynolds]

locate config.nt (probably c:\winnt\system32\config.nt).

look at the last couple lines.

change files=20 to files=whatever

 

[aker]

More likely the solution lies with overcoming the infamous
&quot;Opportunistic Locking&quot; problem.

see the following articles:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q296264&

http://www.dataaccess.com/whitepapers/opportunlockingreadcaching.html

http://www.elevatesoft.com/bulletin.htm

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q307982

http://www.dataaccess.com/kbase.asp

Keep searching for Opportunistic Locking and let us know if you find the solution.
Regards

ps. Out of curiosity, does the program work ok under terminal as my system took a massive reduction in response time making it almost impossible to use. Why not share the directory (.EXE and .DFBs) on the server and map the network drive on the workstations so that they run the program locally (assuming it's a LAN).

 

[timeslice]

I´m working in a very extensive WAN network, so i need to use TS... I disabled Op Locking by following Q266264 from Microsoft web site after your answers. Until now, i dont have any reports of Dos Error 5. I ll wait for more 2 or 3 days, to be sure that thats is the solution.
I ll return with answers.

Thanks for the help

 

[timeslice]

Hi,

I have something to say... i hate Op Locking. I disabled Op Locking and the App works fine now. Thanks for the help.