New Reply Post

I have a terminal server installation that has been running paradox 11 runtime.  All users on this installation access paradox through the terminal server.

After running fine for the initial four months, I recently ran into a curuption problem that looked a lot like the old Oplocks of NT days or Terminal User settings of Win TS server 2003.

I could watch two users viewing the same table, the edits of user A would not appear for user B after user A committed the edits and the table would get immediately currupted.  It looked to me that both users were holding the tables in memory and not committing changes to disk until the user left the table.  A single user could function normally in the application without curruption.  I tried a lot of things on that server to try to fix it including oplocks and terminal user reg edits, but I couldn't correct the problem.

I recovered the entire server from a month old backup, prior to the start of the problem, installed the current paradox app and Data, and everything was fine again.  It has been running fine since then, about two months.  But I would still like to figure out what happened.

Is anyone else running Paradox 11 on a 2008 terminal server?  Has anyone else seen a similar problem?

The one change I can point to at that has a rough correspondence with the start of the problem is that someone tried terminal server "RemoteApp" publishing of paradox on that server.  It is  a special rdp connection to the server that allows the user access only to a given application on the server. The RDP window looks essentially like a paradox app window on the remote workstation to the casual user. It limits the remote users access to anything else on that server.  My working theory is there are some restrictions setup for the published application, similar to oplocks, that carried over to the normal TS users.

http://technet.microsoft.com/en-us/library/cc730673(v=WS.10).aspx

Any comments?

-SS