Hello All
Server
Novell Netware server 5.1 SP4
Pervasive 2000i SQL SP4
communicating over SPX/IPX
Novell Server does Not have TCP/IP installed.

Client workstations are all WinXP Professional SP2
Pervasive 2000i 7.94 some client only some workstation engine and client
Using Novell Client 4.83 SP2

Problem
System is up and running for 1 year
Most workstations only have SPX installed (i.e. no TCP/IP) the problem one
and a few others do have TCP/IP and SPX/IPX installed (Spx for Novell Server
/ TCP/IP for Internet)
2 days ago 1 workstation stopped working with the Pervasive engine (all
others continue to work correctly)
When I run any program on the problem workstation it hangs when it tries to
open a Btrieve file, No error returned it just hangs. (I have to force it to
exit with task manager)
PCC will not work on the problem workstation it hangs while trying to
initialize.
PSA will not run
Windows explorer continues to see the Netware volumes
I left smartscout running the communications stress test and it successfully
completed over 30,000 tests

The same programs work when operating on local files on this machine.
All other workstations continue to work running the same programs using
Server data.
I connected the problem workstation to the network cable of another working
workstation and it still does not work.
I upgraded the Novell client to 4.91 and this makes no difference
I have rebooted both the server and the workstation to no avail.
On the server monitor there is the following message
BPSPXCOM-11 Bad connection ID detected on send. The SPX connection was lost
after the initial request began.

I have looked at the Pervasive website and at Bills paper on Status 95 but
if it is a communication problem how come all other workstations are working
fine and this workstation can still see the Novell Volumes and xcopy files
etc?

The last few entries in the PVSW.log are below
08-16-2005 15:39:06 NWMKDE 0000002D NWMKDE.NLM FITZ02
W
MicroKernel Database Engine
(c) Copyright Pervasive Software Inc. 1989-2001
All Rights Reserved


08-16-2005 15:39:17 NWBST100 0000002D BTRIEVE.NLM FITZ02
I
Btrieve for NetWare v7.90
(c) Copyright Pervasive Software Inc. 1989-2001
All Rights Reserved.


08-16-2005 15:39:20 NWBSRVCM 0000002D NWBSRVCM.NLM FITZ02
I Btrieve Communications Manager 7.90.230.033
Copyright (C) Pervasive Software Inc. 2001
All Rights Reserved.



08-16-2005 15:39:21 BSPXCOM 0000002D BSPXCOM.NLM FITZ02
I Btrieve SPX Communications Module 7.90.230.033
Copyright (C) Pervasive Software Inc. 2001
All Rights Reserved.



08-16-2005 18:26:46 BSPXCOM 0000002D BSPXCOM.NLM FITZ02
W BSPXCOM-11: Bad connection ID detected on send.
The SPX connection was lost after the initial request began.



08-16-2005 18:26:56 BSPXCOM 0000002D BSPXCOM.NLM FITZ02
W BSPXCOM-11: Bad connection ID detected on send.
The SPX connection was lost after the initial request began.



08-16-2005 18:27:06 BSPXCOM 0000002D BSPXCOM.NLM FITZ02
W BSPXCOM-11: Bad connection ID detected on send.
The SPX connection was lost after the initial request began.

Any ideas?

TIA

Eoin Fitzpatrick, Dublin

Hi Eoin,

I'm wondering whether TCP/IP is causing the problem. I appreciate
you're not using it, but I think that may be the issue... TCP/IP is the
default protocol for P.SQL, so I think it'll be trying to establish an
IP connection and this may be the hang.

Try setting the problem workstations to only try SPX for P.SQL, using
Control Center | {Workstation} | Configuration | Comms. Protocols |
Supported Protocols.

It may be that the BSPXCOM errors are caused by the unexpected demise of
the tasks you're having to kill on the workstations.

Jon Grieve
Southdown House Software Ltd.

The U.K's #1 for Pervasive Software

http://www.southdown.co.uk/db/






Eoin Fitzpatrick, Dublin wrote:

You'll also want to patch to PSQL2000i Service Pack 4 AND the HotFix
updates (there are multiple downloads to this one).


It could simply be that one DLL has gone bad on that workstation, due
to random HD corruption. If you have a utility like Beyond Compare
(www.scootersoftware.com) then you can compare the drive of this
machine with one that works. Be sure to set it for a binary comparison
for each file, as you may find one that has the same date/time of the
file, but the contents may differ.

I agree with Jon that the SPX errors are simply artifacts -- the client
makes a connection attempt under SPX, but hangs and never acknowledges
the response from the server. As such, this is more a symptom that a
cause.

Be sure that you disable NETBIOS when you're changing the client
settings as well...
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive.SQL Service & Support - November, 2005 ***
*** Chicago: Pervasive DataExchange Class - November, 2005 ***


Eoin Fitzpatrick, Dublin wrote:

Hello,

I've seen this problem some times in the past (P.SQL 8.6).
I guess the true cause of this network hardware -
the station's network card , cable , switch or server's network card.
In my case replacing switch and server's network card caused the
problem to disappear.

There's a way that you can cause this messages to disappear , but it's
not like a cure.
It causes Netware to be "lazier" to close sessions that don't respond .
Use SPXCNFG netware server module for that, link below may be a clue:
http://rcswww.urz.tu-dresden.de/~pol...s/htm/021.html

In my case this didn't really help. Stations were just working very
slowly instead of totally hanging. The cause was in a hardware.
My 2 cents. HTH.

Przem

BTW. I guess that btrieve/pervasive uses SPX part which is high level
protocol, whereas file manipulation routines use IPX part , which is so
called connectionless layer, more resistant to network failures.

Hello all
Thanks to all for replying
I never did find out what was causing the problem.
As I had a 8.7 licence (purchased from Jon) lying around I went ahead with a
complete upgrade to the newer engine. I also changed over from SPX/IPX to
TCP/IP (a previous suggestion from Bill) and thus the problem has been
eliminated!

Thanks all for your help

Eoin Fitzpatrick


<przemm (AT) poczta (DOT) onet.pl> wrote