|
Hi David, Thanks very much for your ideas and
comments. Currently, the problem occurs on all workstations (windows XP
and windows 2000). I can cause it to happen at will on any machine.
We have moved the RBTI path to a local machine on one critical workstation
where running local seems to help. Scott Sherer From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
M. Blocker Scott 99 times out of 100 in my experience, this kind of problem
is related to a hardware problem with one or more workstations, or network
setup issue. It can be VERY frustrating to track it down, but what's
required is a systematic record keeping / testing over a period of time. First gather some data: 1. Do the problems occur on ALL workstations, or are
some reporting more often than others? If you don't have this
information, ask your users to cooperate in keeping a simple tally sheet of the
number of occurances per day per workstation. see if there is a
pattern. 2. If it's happening more often on some workstations
than others, check network wiring / slave card on those workstations. You
could even try NOT USING those for a day or two and see if it helps the others
as well. That will tell you it's workstation based. 3. If it's happening equally often on all, then it's most
likely a network setup issue. David Blocker ----- Original Message ----- From: Scott Sherer 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 |
- [RBG7-L] - RE: rbase crash Dawn Oakes
- [RBG7-L] - RE: rbase crash Dan Goldberg
- [RBG7-L] - Re: rbase crash Bernard Lis
- [RBG7-L] - RE: rbase crash Javier Valencia
- [RBG7-L] - RE: rbase crash Walker, Buddy
- [RBG7-L] - Re: rbase crash David M. Blocker
- [RBG7-L] - Re: rbase crash Scott Sherer
- [RBG7-L] - Re: rbase crash Scott Sherer
- [RBG7-L] - Re: rbase crash A. Razzak Memon
- [RBG7-L] - Re: rbase crash David M. Blocker
- [RBG7-L] - Re: rbase crash Scott Sherer
