Hello Julie,

we had this problem today (I think this is the same). We set authentication
ON and the NT scheduler would not start correctly. We had to launch a manual
backup before restarting the scheduler (to force the correct encryption of
the passwordin the registry).

Regards,

Rene Lambelet
Nestec SA - 55, Av. Nestle - CH-1800 Vevey
Tel: ++41'21'924'35'43 / Fax: ++41'21'924'45'89
E-Mail: rene.lambelet AT nestle DOT com



> -----Original Message-----
> From: Julie Phinney [SMTP:jphinney AT HUMANA DOT COM]
> Sent: Tuesday, 10. November 1998 18:48
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: NT ADSM Client Loop
>
> We're having that problem right now too on our 3.1.0.5 clients.  Not all
> of
> them, but it keeps popping up.  I have to stop the ADSM server, then start
> it again and lock the offending node before it makes contact again.    I
> saw the fix was to use DSMCUTIL UPDATEPW to update the password, but we
> have one where that didn't fix it.     What's strange is, it appears to
> fix
> it, the schedule service starts successfully and lists it's next schedule
> time, then within minutes starts looping again.   The password, the client
> name, the server name   all appear to be right.
> We just started rolling out 3.1.0.5 last week and now are having a daily
> headache with this loop.
> We had to put a hold on the roll-out too.
>
>
>
>
> Eric LEWIS <eric.lewis AT CCMAIL.ADP.WISC DOT EDU> on 11/10/98 10:44:07 AM
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> To:   ADSM-L AT VM.MARIST DOT EDU
> cc:    (bcc: Julie Phinney/Green Bay/Humana)
> Subject:  NT ADSM Client Loop
>
>
>
>
>
>      Hi:  We are having problems with the infinite loop that afflicts the
>      win32 ver 3.1.0.5 client.  The problem, as you can see below, is
>      related to incorrect passwords AND unregistered nodes.
>
>      I recall a problem with the .3 client, was there a problem with
>      failure to trim schedule logs?
>
>      Can anyone suggest a ptf release that is reliable?  (And how to get
>      it?  I do still have a copy of the 3.1.0.3 client install set.)
>
>      Thanks.
>
>      Eric Lewis UW-Madison
>      eric.lewis AT doit.wisc DOT edu
>
>
> ______________________________ Reply Separator
> _________________________________
> Subject: Re[2]: NT ADSM Client Loop
> Author:  James SPORER at DoIT-MAIL1
> Date:    11/10/98 8:48 AM
>
>
>      Eric,
>      This doesn't just happen for incorrect password.  It happened on
>      Friday on Bucky1 and Monday on Bucky2 when somebody tried to connect
>      to the wrong server.  No node existed on the server they attempted to
>      connect to.  The operators realized the problem rather quickly on
>      bucky1 because they can see the errors on the console but on bucky2
> it
>      isn't so obvious.  I would rather we give them the .3 version, if the
>      error isn't in that version, than propagate a version with a rather
>      serious flaw that will catch us down the road.
>      Jim
>
>
>
> ______________________________ Reply Separator
> _________________________________
> Subject: Re: NT ADSM Client Loop
> Author:  Eric LEWIS at DoIT-MAIL1
> Date:    11/9/98 4:41 PM
>
>
>      Well, I could pull the page . . . or use ptf 3 . . . if you scream
>      really loud I might hear you but gee, why can't our customers use the
>      correct password?
>
>      I will put a message out to the Bucky Relay to urge caution.
>
>      erl
>
>
>
>
> ______________________________ Reply Separator
> _________________________________
> Subject: NT ADSM Client Loop
> Author:  James SPORER at DoIT-MAIL1
> Date:    11/9/98 4:13 PM
>
>
>      This is the status of the nt client problem that has caused several
>      problems recently on both bucky1 and bucky2.
>      Hi James,
>      IC22093 is targeted for PTF6.  It's hard to gauge the exact date the
>      PTF will be released. I believe it is targeted for release before the
>      end of the year.
>      Thanks,
>      John
>
>      It can't be soon enough.  Eric, maybe we should put a hold on nt
>      customers upgrading to version 3.
>      Jim