First -
Always check to make sure that the process is cancelled from the ADSM
server.
If you don't cancel the process you will crash the server.

we put the following lines in the DSM.OPT file:

NWPWFILE YES
NWUSER ".CN.OU.OU.O"

Replace the NDS context to fit your environment. We use "" because out
backup operator account name has spaces.

This identifies the account name that ADSM uses.
NWPWFILE creates an encrypted password file for that account.

Good luck!


__________________________
Cris Robinson
Sr. Telecommunications Analyst
Technical Support
Liberty Mutual Insurance
cris.robinson AT libertymutual DOT com
(603) 431-8400 Ext. 54837


> -----Original Message-----
> From: Frank Ramke [SMTP:ramke AT VNET.IBM DOT COM]
> Sent: Thursday, October 23, 1997 11:03 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Novell gurus out there...
>
> May be a problem trying to open the encrypted password file that
> yesterday's backup created. Try putting the nwuser option in the
> dsm.opt file instead:
>
> NWUSer servername\user:password
>
> By the way, IBM and Novell both recommend that you not run dsmc.nlm
> on the SFTIII complex to start with. It is safer to run dsmc.nlm
> outside the complex and use the tsa to connect and backup the SFTIII
> server remotely.
>
> Frank Ramke
>
> > Hi everyone,
>
> > I have had a strange occurrence and wondered if any=20
> > of you Novell people could help here...
> >
> > Our environment is as follows:
> > OS/2 ADSM backup server - Latest PTF level=20
> > for OS/2 ADSM server - Fixpak27 loaded.
> > Novell adsm client - Latest Novell client, but here
> > is where I'm wondering - the server is SFT111...
> > What happens is schedules/backups run fine -=20
> > Did a full backup last night - went through no problem.
> > Tried a restore of a file today and the process starts=20
> > up to where it would ask the password, but then hangs.
> > Can not unload the dsmc - If we do that the console also=20
> > starts to hang and we end up having to re-boot the server.
> > The OS/2 server does not even show this session starting.
> > Has anyone seen this - or should we start looking at running
> > traces?
> >
> > Here is what comes out on the 2nd server's console:
>
> >
> > Abend: Page Fault Processor Exception (Error code 00000000)
> >     OS version: Novell NetWare SFT III IOEngine 4.11  August 22,
> 1996
> >     Running Process: DSMC.NLM        0 Process
> >     Stack: 5C C3 A8 07 00 00 00 00 BF 6F 26 E1 6C CC A8 07
> >            54 C3 A8 07 2D 54 4F 44 41 54 45 00 32 38 00 30
> >            38 00 31 39 39 37 00 04 4C 04 E6 04 FF FF FF FF
> >
> > Additional Information:
> >     The CPU encountered a problem executing code in DSMC.NLM.  The
> >     problem may be in that module or in data passed to that module
> >     by another NLM.
> >
> > The running process will be suspended.
> >
> > 10-23-97   3:00:25 pm:    IOENGINE-4.11-4631
> >     WARNING! Server GRAND experienced a critical error.  The
> offending
> > process
>      was suspended or recovered.  However, services hosted by this
> server
> > may
> >      have been effected.
> >
> >
> > 10-23-97   3:02:19 pm:    RSPX-4.10-28
> >      Remote console connection granted for 1E1E1E1E:0004AC837FED
> >
> > GRAND_IO1 <1>:
> >
> > Hope this makes sense to someone.
> >
> > TIA
> > Christo Heu=EBr
> > ABSA Group=20
> > Johannesburg
> > South Africa
> > E-Mail: christoh AT absa.co DOT za=20