Jan, Did you ever run the DB with FASTLOCK OFF? If so, did you note any performance (speed) difference in your LAN between ON/OFF for FASTLOCK?
The reason I'm asking is a couple of years ago, reading the r:list regarding this issue, I experimented with switching FASTLOCK ON (already running STATICDB ON), and noted a performance hit. Switched back to FASTLOCK OFF and speed returned (user connection time, transaction processing, print jobs, forms to screen, etc.). There could of course been other things happening in my database in combination with the FASTLOCK setting, but, I scratched the idea and DB behavior returned to normal at that time. Just curious, Jan. Brad From: [email protected] [mailto:[email protected]] On Behalf Of jan johansen Sent: Wednesday, January 18, 2012 2:05 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Application "hanging" Larry, While not an answer to your question, I always run the database with STATICDB ON FASTLOCK ON At first this was a little inconvenient but once you get used to the fact that you cannot make any structure changes while everyone is connected it has created a more reliable database. Since moving to 7.6 (currently 9.1) we have never had to use R:Scope. Jan -----Original Message----- From: Lawrence Lustig <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Wed, 18 Jan 2012 13:57:18 -0800 (PST) Subject: [RBASE-L] - RE: Application "hanging" I have been dealing with the same issue, RB76. Problem appears to occur only on RDP sessions on a Win 2088 terminal server. Application will run fine for a day or more and then a problem occurs. When the problem occurs no R:base session, RDP or workstation, can attach to the database files. Stations already attached appear to hang, the application stops working. The problem can be solved by rebooting the terminal server (the file server and workstations do not need to be rebooted). I believe that the problem can also be solved by clearing the open file connections to all R:Base sessions originating on the terminal server without actually rebooting the server, but I'm not 100% sure of that. After the problem is solved, all users can access the database again without requiring a reboot of the file server. The files are intact, except that operations in progress may have left cursor or row locks on tables that cannot them be cleared. In other words, it appears that one of the sessions on the terminal server is obtaining some kind of lock on one or more of the database files that is affecting both new and already existing connections to the file(s). QUESTION: For those users seeing something similar, are you running with STATICDB on? I'm wondering if that setting would cause fewer locking issues, at least on RB1. -- Larry _____ From: John Engwer <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Wednesday, January 18, 2012 10:09 AM Subject: [RBASE-L] - RE: Application "hanging" Dennis, I am seeing a similar problem with my V8 application running MS server 2008. (users local on Terminal Services, RDP). The application will intermittently hand and post a "Cross-Thread error" in the OS event log. The application is fairly large and the hangs can occur anywhere in the application. If you search the list you will see my prior postings on this subject. John Engwer (412) 751-2433 -----Original Message----- From: [email protected] [mailto: [email protected] <mailto:[email protected]> ] On Behalf Of Dennis Fleming Sent: Tuesday, January 17, 2012 10:30 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Application "hanging" Using Rtime 7.1 The customer recently moved four plants to their corporate server and using RDP. Running slowly but usually OK. Occasional "Application Hangs" are an issues. In this environment the server is just pushing screens and printouts to client and receiving keyboard/mouse input. Is this the same as a timeout? TIA, Dennis ***** Dennis Fleming IISCO www.TheBestCMMS.com Phone: 570 775-7593 Mobile: 570 351-5290
