Bindery locked (sorry, prev was mistake)

dbe...@munisoft.ca

unread,

Jul 30, 2002, 12:48:19 PM7/30/02

to

New to Novell, workstation getting kicked out of program then gets 'login
denied bindery locked' have to reset server before users can log back in.
Can anyone point me in some direction?

Dave Kearns-NSCV

unread,

Jul 30, 2002, 2:12:12 PM7/30/02

to

<dbe...@munisoft.ca> wrote in message
news:nrz19.3780$n.10...@prv-forum2.provo.novell.com...

When you look at the server's console, are there any messages? If you
go into SYSCON and read the error log, is there anything relevant? If
you type
ENABLE LOGIN <enter>
at the server console, can users log in?

Is there a backup running at night? Has it completed in the morning?

--
Dave Kearns
Novell Support Connection Volunteer

dbe...@munisoft.ca

unread,

Jul 30, 2002, 5:15:13 PM7/30/02

to

Thanks for the tips, there aren't any msgs on the server, it is actually a
remote site and I didn't know about checking the error logs with SYSCO,
thanks, when the client calls back I'll check those. I'm not familiar with
the ENABLE LOGIN command either but will try it. There is a nightly backup
but it appears to be running fine.

Would BINDFIX be helpful?

Thanks again
Dean Bergen

Felton Green (SysOp)

unread,

Jul 30, 2002, 6:25:43 PM7/30/02

to

No.. not unless you're to login

--
Felton Green (SysOp)
Novell Support Connection Forums

Felton Green (SysOp)

unread,

Jul 30, 2002, 6:26:30 PM7/30/02

to

also sounds like the server is still doing backup

dbe...@munisoft.ca

unread,

Jul 30, 2002, 6:49:44 PM7/30/02

to

Not sure I understand what you mean there. The users can all log in fine
but after a few hours one will get a bindery message and then they will
all be logged out until the server is restarted.

Dean Bergen

dbe...@munisoft.ca

unread,

Jul 30, 2002, 6:51:59 PM7/30/02

to

I'm not sure that it does sound like that, read my reply to your previous
message.

Thanks,
Dean Bergen

Felton Green (SysOp)

unread,

Jul 30, 2002, 7:02:09 PM7/30/02

to

Hi

What is your patch status and can you describe the full error message?

Felton Green (SysOp)

unread,

Jul 30, 2002, 7:04:20 PM7/30/02

to

I went off on a tangent... sorry

Dave Kearns-NSCV

unread,

Jul 30, 2002, 7:19:00 PM7/30/02

to

Are you saying that users are logged in, but trying to re-login causes
the message? Could you explain the exact sequence?

If the users are terminating their session without logging out (i.e.,
power cycle) then getting a "login denied" message, it could simply be
that their previous session is still active. Have them wait 20 minutes
and try again. Or, load MONITOR and look at connection status. If the
user shows up in MONITOR, delete the session then have the user login
again.

-dave

dbe...@munisoft.ca

unread,

Jul 31, 2002, 10:54:19 AM7/31/02

to

This is a remote site (very remote) and this is not an easy client to get
info from but as I understand it the sequence is: The users can all log in
fine and go to work, after a period of time one user will get an error msg
which may or may not refer to the bindery, at this point all users are
locked out of the server until the server is restarted. I haven't had a
chance yet to check the connection status as the client keeps resetting
the server without calling in.

Thanks again for your help Dave,
Dean

It is very possible that we just have to terminate their session from
MONITOR, however this still leaves the cause of the problem unknown.

dbe...@munisoft.ca

unread,

Jul 31, 2002, 11:48:17 AM7/31/02

to

The error msg on the server when the problem appears is:

System halted - general protection processor expception (error code
00000000) OS version novell netware v3.12 (25 user) 8/12/93

running process interupted service routine (nested count 2)
interupted process polling process eip:00168D3A

Dave Kearns-NSCV

unread,

Jul 31, 2002, 11:54:04 AM7/31/02

to

That should help. A GPPE is almost always a hardware problem,
frequently RAM related but often RAM on the network card. You should
consider swapping out the NIC, but also be prepared to swap out RAM
modules. The server crash is causing the error messages on the
workstations which are an effect, not a cause.

Note that if you've recently added new network cards or drivers these
would be highly suspect.

-dave

dbe...@munisoft.ca

unread,

Jul 31, 2002, 1:00:14 PM7/31/02

to

Found the problem: 'insert boot disk and press any key'
total hard drive crash, thanks for all the help though

Dave Kearns-NSCV

unread,

Jul 31, 2002, 1:17:12 PM7/31/02

to

<dbe...@munisoft.ca> wrote in message
news:yIU19.46$lP6....@prv-forum2.provo.novell.com...

> Found the problem: 'insert boot disk and press any key'
> total hard drive crash, thanks for all the help though
>

That can do it too. Good luck....

-dave