ADSM-L

Re: ADSM v3.1.2 (NT - type)

1999-03-04 13:08:31
Subject: Re: ADSM v3.1.2 (NT - type)
From: Richard Sims <rbs AT BU DOT EDU>
Date: Thu, 4 Mar 1999 13:08:31 -0500
>A scheduled Archive of a server failed with Message: ANR0484W - Protocol
>violation detected.

ANR0484W Session ____ for node ______ (___) terminated - protocol violation
         detected.
        Usual cause:  The specified client is attempting to establish a session,
        but no password has been established.  When you registered the client on
        the server you established a password, which must be used when the
        client session is invoked, either implicitly with
        "Passwordaccess Generate", or explicltly with "Passwordaccess Prompt".
        Do 'dsmc q sch', a basic client-server query which goes through all the
        password and network stuff that backup does, and will prompt for and
        establish the password in the client area if "Passwordaccess Generate"
        is in effect.  If such a password is in effect, a good response will
        verify the client-server interaction.
        Another cause:  A Client Schedule is defined with ACTion=Macro and the
        macro whose file name is coded in OBJects= contains administrative
        commands instead of client commands.  (Use Administrative Schedules for
        executing administrative commands.)
        Another cause:  An ADSMv2 HSM defect in which it caused the password
        entry in /etc/security/adsm to be obliterated.
        Accompanied by message ANR0444W.

Richard Sims, BU
<Prev in Thread] Current Thread [Next in Thread>