Re: BTCPCOM.NLM does not load when server starts

This is neither Btrieve nor Unix error. Instead, it is a NetWare OS
error number, and you'll need to look this up in the Novell manuals.

This is usually caused by a lack of memory. If the server is
physically low on memory, consider adding more. It may just be a
conflict at Startup where not enough memory is available for a short
time.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach@xxxxxxxxxxxxxxxxxxxx
http://www.goldstarsoftware.com
*** Chicago: Pervasive.SQL Service & Support - March, 2006 ***
*** Chicago: Pervasive DataExchange Class - March, 2006 ***


Guy Dawson wrote:

> Hi!
>
> We have a Netware 5.1SP8, server running NDS and P.SQL 8.6.
>
> When we boot it it loads btrieve and P.SQL using the
>
> BSTART.NCF
> MGTSTART.NCF
>
> files.
>
> Recently, BTCPCOM.NLM has failed to start. The log in PVSW.LOG is
>
> 01-09-2006 15:08:19 NWBSRVCM 00000040 NWBSRVCM.NLM CONCORDE
> W NWBSRVCM-8: Btrieve Communications Manager could not
> load/initialize BTCPCOM.NLM (errno=21).
>
> 01-09-2006 15:08:19 BSPXCOM 00000040 BSPXCOM.NLM CONCORDE
> I Btrieve SPX Communications Module 8.60.192.030
> Copyright (C) Pervasive Software Inc. 2004
> All Rights Reserved.
>
> However, when we load it manually at the console all is well:
>
> 01-09-2006 15:24:02 BTCPCOM 00000040 BTCPCOM.NLM CONCORDE
> I Btrieve TCP/IP Communications Module 8.60.192.030
> Copyright (C) Pervasive Software Inc. 2004
> All Rights Reserved.
>
> The errno result is odd. Assuming it's errno as in the UNIX error
> number then error 21 is 'is a directory'. This typically means
> something has tried to do a file operation on a directory.
>
> Assiuming it's a P.SQL/Btrieve error then error 21 is 'key buffer
> parameter is too short'.
>
> Neither of these make sense to me!
>
> Any thoughts?
>
> Guy
> --
> --------------------------------------------------------------------
> Guy Dawson I.T. Manager Crossflight
> Ltd gnues@xxxxxxxxxxxxxxxxx

.