I am also experienbcing similar problems for past on monthwhen the users double clicks the EXE on the Terminal Server nothing happens when i check in the Task Manager the EXE shows and running but nothing happens but all other applications seem to work perfectly EXCEPT only the rbase Compiled EXE doesnt seem to run then we have to reboot the Teminal Sever and then the Rbase EXE works ok i am using windows 2008 termminal server will appreciate any suggestions Mohammed Sattar Utah Group of Companies
_____ From: [email protected] [mailto:[email protected]] On Behalf Of Bob Thompson Sent: Tuesday, October 18, 2011 11:05 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Hanging terminal server sessions? It was very sporadic in that I could never pin point the cause, but it happened frequently. Sometimes a couple of days would go by without issue and other times it would happen 2-3 times on the same day. I use the TMP setting now (which was somewhat new back then), so it should be. OK. However when creating RDP users, one does specify where the users profile resides. I can offer hope in that we run this system extensively now on (2) terminal servers accessing one file server. Some production programs have form timers that fire every 10 seconds, rotary encoders inputting real time and production employees that are constantly entering data via touch screens every few seconds as well. I.E. a LOT of data I/O. I have not had this hang up issue since the above modifications two years ago. So I think it can be resolved. Bob Thompson LaPorte, IN 219-363-7441 Sent from my iPod On Oct 18, 2011, at 10:55 AM, Lawrence Lustig <[email protected]> wrote: Thanks Bob. I don't believe there are any ODBC connections in this system (I recall writing an R:Base-to-R:Base ODBC thing for them years ago but I believe it's rarely if ever used). Is the Windows RDP profile temp folder different from setting SCRATCH to TMP? How do you get this folder from the environment? When you saw this problem was it sporadic? The report I have is sporadic -- sometimes once a week, sometimes several times a day. But the system does run most of the time. -- Larry _____ From: Bob Thompson <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Tuesday, October 18, 2011 10:54 AM Subject: [RBASE-L] - Re: Hanging terminal server sessions? Larry, I experienced the very same symptoms a couple of years ago, running 7.5 compiled. I was able to resolve my issue, however I modified more than one possible cause, so I'm not 100% sure which fixed it. So I will list what I did and perhaps, where applicable, one might help. ODBC connections: My database had several ODBC connections to non-Rbase tables. Some of these were originally attached without a "using" clause. This resulted in all columns being a "Qualkey" link in these tables. I corrected this to have only one QualKey column. I also changed code to DisConnect ODBC connections after use where ever I could, not leaving them open "all day" Temp files: I originally was using a shared TEMP folder for all RDP user's $$$ files. I changed the code to use the user's Windows RDP profile temp folder. I set the RDP user's rights to full for the shared Database folder. (This added erase authority, but I was grasping for solutions) Compiled file: I had about 20 RDP sessions running from 1 shared folder and compiled .exe. I made 4 duplicate folders and went to about 5 users per .exe. This might seem strange, but I had reasons to suspect some odd trerminal server issue running so many copies of the same exe. Anyway, after the above, my issue went away. I could introduce one back in at a time, but the system is working great and I do not have the time for that luxury. I suspect the ODBC changes were probably causing my iisues, but it could have been any of the above. Good luck. Bob Thompson LaPorte, IN 219-363-7441 Sent from my iPod On Oct 18, 2011, at 8:07 AM, Lawrence Lustig < <mailto:[email protected]> [email protected]> wrote: A client has recently started having problems with their R:Base system "hanging" -- all attached sessions stop running and the database files become unavailable until the server is rebooted. I believe that the onset of this problem more or less coincides with their changing some machines in their facility from networked workstations to thin clients attaching to RDP sessions. I'm wondering if dropped or incorrectly terminated RDP sessions could account for the sudden onset of problems they're seeing. Does anyone have an experience with this? -- Larry
