Need help with a Bindery Problem

Thread View: comp.os.netware.misc

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Bob Dahm Wed, 20 Dec 1995 00:00

#507

Author: Bob Dahm
Date: Wed, 20 Dec 1995 00:00

26 lines
1923 bytes

I need some help with a Bondery problem I am having.

I was doing some end of the year admin on our Netware 3.12 file server 
when I ran into this problem.  I was backing up the Bindery when I got a 
Network error saying that NET$VAL.SYS could not be read.  I tried BINDFIX 
and it will not fix it.  BINDFIX gives a quick little message saying that 
it can't fix the bindery.  So I tried to vrepair the SYS volume and 
vrepair says that it can't find V_MAC.NLM.  When the Server boots up now, 
I get a error reading NET$VAL.SYS, but the SYS volume mounts and from a 
user stand point everything looks OK.

My first question is: What am I doing wrong here? Am I missing something?

I had an idea that I could delete NET$VAL.SYS and netware would generate 
a new one, but then I thought I should ask the net first before doing 
anything I might regret later.  If it is OK to delete NET$VAL.SYS, what 
do I loss? Do I need to regenerate one or will netware do that for me.

Thanks for any help in advance.

         /======================================================/
       /     Robert Dahm - ConQuest Software                  /
     /       Internet Address: Abu@access.digex.com         /
   /          "And Thank You for Your Support"            /
 /======================================================/

Re: Need help with a Bindery Problem

#506

Author: t3623ad
Date: Fri, 22 Dec 1995 00:00

48 lines
2875 bytes

abu@access2.digex.net (Bob Dahm) writes:

>I need some help with a Bondery problem I am having.

>I was doing some end of the year admin on our Netware 3.12 file server 
>when I ran into this problem.  I was backing up the Bindery when I got a 
>Network error saying that NET$VAL.SYS could not be read.  I tried BINDFIX 
>and it will not fix it.  BINDFIX gives a quick little message saying that 
>it can't fix the bindery.  So I tried to vrepair the SYS volume and 
>vrepair says that it can't find V_MAC.NLM.  When the Server boots up now, 
>I get a error reading NET$VAL.SYS, but the SYS volume mounts and from a 
>user stand point everything looks OK.

>My first question is: What am I doing wrong here? Am I missing something?

>I had an idea that I could delete NET$VAL.SYS and netware would generate 
>a new one, but then I thought I should ask the net first before doing 
>anything I might regret later.  If it is OK to delete NET$VAL.SYS, what 
>do I loss? Do I need to regenerate one or will netware do that for me.

>Thanks for any help in advance.

>         /======================================================/
>       /     Robert Dahm - ConQuest Software                  /
>     /       Internet Address: Abu@access.digex.com         /
>   /          "And Thank You for Your Support"            /
> /======================================================/   
> 
Only a few hints.
1. You may start vrepair for SYS from the startup drive only (usually c:).
   To Do this all necessary files must reside on this drive. VREPAIR
   will give you the names of the necessary modules.
2. The old bindery files will be named netxxxx.old.
   Copy these three files to floppy or a local hard disk. Look for the
   attributes of these files. There mus be normal access possible.
   By no means write protection is allowed. This gives a desaster, if
   you call bindfix.
3. Try deleting the *.old files and repeat bindfix.
4. The very very last attempt:
   Restore the *.old files from the backup medium and run
      bindrest
   But take into account: all information concerning new users since the
   last bindfix will be lost.
By the way: it is impossible to delete the bindery files.

Rainer Haessner
TU Muenchen
rh@linda.org.chemie.tu-muenchen.de

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads