Status 91 on Novell 
Author Message
 Status 91 on Novell
A customer upgraded from Btrieve 6.10 to Pervasive 2000 on a Novel
4.11 server Friday and all seemed fine. Monday morning when running a
DOS app they get status 91 after a long delay. They are running spx
requester BREQUEST. Tried installing the windows client and the
conectivity tests failed for both spx and tcip. Frame types are set to
802.2 and they have 10 user licences. The Btrieve NLM is up and
running on the server.
Any idea's as to were to start looking?

Sent via Deja.com http://www.***.com/
Before you buy.



Fri, 06 Sep 2002 03:00:00 GMT
 Status 91 on Novell

Assuming that you've checked file & user privileges, here's a couple of
ideas.....

1.  Run the configuration utility and make sure that SPX is one of the
allowed protocols on the server.
2.  Make sure that you remove all occurrences of BtrBox on the client
machines.  It completely kills the ability to use brequest with a dos app.
Make sure you kill all the registry entries and delete the .exe and .vxd
from the drive, then reboot.

 - Dina

Quote:

> A customer upgraded from Btrieve 6.10 to Pervasive 2000 on a Novel
> 4.11 server Friday and all seemed fine. Monday morning when running a
> DOS app they get status 91 after a long delay. They are running spx
> requester BREQUEST. Tried installing the windows client and the
> conectivity tests failed for both spx and tcip. Frame types are set to
> 802.2 and they have 10 user licences. The Btrieve NLM is up and
> running on the server.
> Any idea's as to were to start looking?

> Sent via Deja.com http://www.deja.com/
> Before you buy.



Fri, 06 Sep 2002 03:00:00 GMT
 Status 91 on Novell

Quote:
> A customer upgraded from Btrieve 6.10 to Pervasive 2000 on a Novel
> 4.11 server Friday and all seemed fine. Monday morning when running a
> DOS app they get status 91 after a long delay. They are running spx
> requester BREQUEST. Tried installing the windows client and the
> conectivity tests failed for both spx and tcip. Frame types are set to
> 802.2 and they have 10 user licences. The Btrieve NLM is up and
> running on the server.

Welcome to the wonderful world of 'Btrieve today'! After you have lost
half of your hair trying to figure out exact mixture of various DLL's
from various manufacturers which works in your particular configuration
with your particular set of other applications, you'll come to
appreciate the days of DOS and 6.10c, just as I did.

Meanwhile, you can look for hints at http://www.***.com/

btw, I'm still looking for viable alternative to Btrieve (that does
not cost me all my money with 3 drops of {*filter*} on top), too.



Sat, 07 Sep 2002 03:00:00 GMT
 Status 91 on Novell

Quote:

>A customer upgraded from Btrieve 6.10 to Pervasive 2000 on a Novel
>4.11 server Friday and all seemed fine. Monday morning when running a
>DOS app they get status 91 after a long delay. They are running spx
>requester BREQUEST. Tried installing the windows client and the
>conectivity tests failed for both spx and tcip. Frame types are set to
>802.2 and they have 10 user licences. The Btrieve NLM is up and
>running on the server.
>Any idea's as to were to start looking?

First of all, which version of brequest are you using? There is a 6.10
version in the public directory, remove it and replace it with the
2000 version.
If you have the windows client installed the btrbox requester is
installed. This requester will absolutely kill brequest. If you're on
a win9x workstation you should run btrbox95 and bdosstub instead, on a
NT or Win2k station you shouldn't run any requester what-so-ever.

You say connectivity tests fail from windows. Most probable cause for
this would be "weird" internet products (ftp, telnet, trumpet) or bad
NIC drivers. If you have NICs with a RTL8019/29/39 chip, surf to the
Realtek site and download their latest driver. Kick of the NE2000
compatible driver Windows installed for you, put in the Realtek driver
and you should be in business. The fault could also be on the server
side, which could be the result of name change/address change.

Gordon



Sat, 07 Sep 2002 03:00:00 GMT
 Status 91 on Novell
I have made sure that brequest in the public subdirectory is the 2000
version and that there are no other copies of it.

I have only installed the windows client on one machine to see if it would
work, but it does not.  Several of the customers machines are win 3.x so
btrbox would not help.

I just recieved a reply from pervasive saying that Brequest does not work
with 2000 but since I have a dozen or so other customers using it I find
that hard to believe.

Thanks to all for your sugestions I will keep trying to figure it out.

Quote:

> First of all, which version of brequest are you using? There is a 6.10
> version in the public directory, remove it and replace it with the
> 2000 version.
> If you have the windows client installed the btrbox requester is
> installed. This requester will absolutely kill brequest. If you're on
> a win9x workstation you should run btrbox95 and bdosstub instead, on a
> NT or Win2k station you shouldn't run any requester what-so-ever.

> You say connectivity tests fail from windows. Most probable cause for
> this would be "weird" internet products (ftp, telnet, trumpet) or bad
> NIC drivers. If you have NICs with a RTL8019/29/39 chip, surf to the
> Realtek site and download their latest driver. Kick of the NE2000
> compatible driver Windows installed for you, put in the Realtek driver
> and you should be in business. The fault could also be on the server
> side, which could be the result of name change/address change.

> Gordon



Sun, 08 Sep 2002 03:00:00 GMT
 Status 91 on Novell
91: The application encountered a server error.

The MicroKernel returns this status code in one of the following situations:

* The Requester cannot establish a session with the server. Either the
client/server MicroKernel is not loaded or the server is not active.
* The SPX drivers are not installed or are outdated
* The value for the Number of Sessions configuration option is too low. Use
the Setup utility to specify a higher value for this option.
* An application specified a path for a file and did not include the volume
name in the path.
* The Btrieve Message Router has not been loaded, and the following
situation has occurred: an application that uses both the Btrieve Message
Router and the MicroKernel to make remote calls (and which therefore
includes the server and volume name when performing an Open operation) has
attempted to open a remote file. Because the Btrieve Message Router does not
interpret the server name, the MicroKernel attempts to do so but cannot.

* A communication or network addressing problem exists in your network
environment, so the MicroKernel requests never reach their destination
server address. Ensure that your workstation and server network components
are up to date and certified for your network environment.
* For NetWare servers, the Maximum Packet Receive Size configuration option
is inappropriate for you environment. For example, the setting should be
1500 for an Ethernet LAN.
* For NetWare servers, the user count limit has been exceeded. Either close
a session or upgrade your user count. For more information about purchasing
and installing additive user counts, refer to the User's Guide.

* For NetWare servers, ensure that the NDS network number is the same as the
Internal Network Number viewed by BINDER.EXE output.
* For NetWare servers, you ran BUTIL.NLM to roll forward a file using a log
file name other than the default, and your BLOG.CFG file did not contain a
correct entry such as "\dir\file.ext=vol:\dir\log.ext".

Quote:

> A customer upgraded from Btrieve 6.10 to Pervasive 2000 on a Novel
> 4.11 server Friday and all seemed fine. Monday morning when running a
> DOS app they get status 91 after a long delay. They are running spx
> requester BREQUEST. Tried installing the windows client and the
> conectivity tests failed for both spx and tcip. Frame types are set to
> 802.2 and they have 10 user licences. The Btrieve NLM is up and
> running on the server.
> Any idea's as to were to start looking?

> Sent via Deja.com http://www.deja.com/
> Before you buy.



Mon, 09 Sep 2002 03:00:00 GMT
 
 [ 6 post ] 

 Relevant Pages 

1. Status code 91

2. Status 91

3. PSQL 2000 status 91

4. Status 91/NLM lockup

5. status code 91

6. ?Help Status Code 91, NT Server, NT Workstation, Btrieve 7.00.200

7. Btrieve status: 91

8. HELP : Error 91 : Run-Time Error 91 Object Variable or With

9. Error 91-Object or block with variable not set

10. 91 open variable

11. Run Time error 91

12. ODBC - Object variable or With block variable not set (Error 91)


 
Powered by phpBB® Forum Software