This is not a joke.

I’ve got OS/2 systems that have suddenly quit accessing Btrieve on a
Netware Server. If there is any one who know anything about OS/2 and
Btrieve in a Netware environment I need help desperately. Please reply
to this message for details.


--
David Ruggles
CCNA MCSE (NT) CNA A+
Network Engineer Safe Data, Inc.
(910) 285-7200 david (AT) nosafespamdatausa (DOT) com

David:

I worked on a system with OS/2 clients to a NetWare server a LONG time
ago, in a land not far from Oz (in Kansas, of course). I've also dealt
with an OS/2 web server accessing a bank system (also on NetWare) via a
WAN -- which was really ugly.

Are you getting any status codes or other error messages back? Where is
the site located? Is there someone there who can obtain a network trace
(i.e. from LANalyzer, Sniffer, Ethereal, etc.) of the attempted connection
to see what is really happening?

I'm at a user group conference for a software company in FL for the next
two days, but you can reach me via E-mail if you need to. My website has
info on my pager number as well...
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Pervasive.SQL Service & Support Classes ***
Chicago: June, 2004: See our web site for details!


David Ruggles wrote:

Bill,
I will try to shed some additional light on the issue David brought
here. BTW: We work together.

It seems that for some reason Netware was refusing the IPX connection
from OS/2 systems when trying to load the Btrieve DDF files; however,
from that point on network access was available. Because of this OS/2
seemed to be "reverting to mama" and loading its local BTrieve
engine, thereby locking every file it opened. This was "bad" since we
have 10 OS/2 systems and even more Win systems attached to this
server.

Upon further investigation we found that many times files (not
necessarily BTrieve files) were being locked and not released by
Windows systems as well. We also discovered that users were still
being shown "logged in" to Netware even when there system was
shutdown.

After running several tests on our backup Novell server (that was
configured the same) we found no problems with any of the above
situations. Needless to say, we spent Tue. night moving data from our
primary server to the backup server.

In conclusion, we believe (at this point) that something went
"haywire" with the server and NOT the OS/2 systems or BTrieve engine.
Would love to determine "what", but since we're not Novell experts,
we'll probably just have to file this one under "unknown".

Thanks for your reply - I like your idea of doing a network trace.
Such a tool would be nice to have.

Lee Peedin
VP Research/Development
Safe Data, Inc.




On 11 May 2004 22:06:05 EDT, Bill Bach <bbach (AT) cncdsl (DOT) com> wrote:

Bill,

Thanks for the reply.

Currently we've returned to an operational state on another server. I
haven't had time to return the original server for further testing yet,
but I hope to be able to do that soon. I will be doing network tracing
(I use Ethereal) and I if I still am unable to figure out the cause I
may contact you via the information on your website. Thanks again for
the reply.

Bill Bach wrote:

--
David Ruggles
CCNA MCSE (NT) CNA A+
Network Engineer Safe Data, Inc.
(910) 285-7200 david (AT) nosafespamdatausa (DOT) com