[RBG7-L] - Re: rbase crash

[Scott Sherer]

Hi Bernie,   We start Rbase from a server, although we have one critical workstation starting from a local drive because of this problem.  Starting from a local drive seems to circumvent the problem, whatever it is.  Tonight at 5pm we’re switching from a Novell server to a Windows server so we’ll see if that has any impact.  Thanks very much for your thoughts below.  I’ll keep reading them and see if I can come up with any other ideas.   Scott Sherer   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Lis Sent: Thursday, July 01, 2004 8:45 AM To: RBG7-L Mailing List Subject: [RBG7-L] - Re: rbase crash   Scott, I don't have the same scenario as yours but on my workstation, I opened one session, then immediately opened a second on a different database. then I cycled back and forth several times. No problem. I have 764 MB RAM on my XP Pro workstation (not running on a network) , how much ram are on your workstations? Is rbase loaded from the server or do you have it on each individual workstation? Do you have this problem if only one session of rbase is running? You might try copying the databases to one of your workstations and running it that way to see if the problem has anything to do with the server or Novell.   Bernie Lis ----- Original Message ----- From: Scott Sherer To: RBG7-L Mailing List Sent: Thursday, July 01, 2004 9:04 AM Subject: [RBG7-L] - rbase crash   Hello everyone,   My company has been experiencing an Rbase bug and I’ve reported it several times on the rbase website.  The developers say they can’t reproduce the problem and yet it happens ten to twenty times per day in my company.  (bug 71526).  We’re running an eleven user license and running patch 73. Our file server is netware 5.1 and our workstations are windows XP.  This bug occurs under two scenarios.   Scenario 1: If you start two copies of Rbase on the same workstation within a second or two of each other.  The first copy of Rbase starts successfully.  The second copy of Rbase (pointing to a different database) fails within a few seconds of starting with the following message. “unable to find help.rid”.  After displaying the message, Rbase goes into a loop. While in the loop it acquires 250 megabytes of memory and everything crashes on the workstation, requiring a reboot of the workstation.   Secenario 2: We have Set Timeout 30 in all of our programs.  My employees complain that they have to terminate Rbase when they’re done using it because when the timeout occurs, Rbase fails as in Scenario 1 above.  Same symptoms…   The Rbase development folks don’t believe me and yet this is a huge problem for us.  Has anyone else experienced this?   Scott Sherer