ADSM-L

Re: ANR2020E Invalid parameter - ORIGINATOR.

1998-07-05 19:46:38
Subject: Re: ANR2020E Invalid parameter - ORIGINATOR.
From: Trevor Foley <Trevor.Foley AT BANKERSTRUST.COM DOT AU>
Date: Mon, 6 Jul 1998 09:46:38 +1000
Yep! Known problem with the V3 NT Admin client talking to a V2 server.
As far as I know, there is no solution, other than to upgrade your
server to V3.


Trevor
------------------------------------------------------------------------
------------------------------------------------
------------------------------------------------
Trevor Foley
Trevor Foley
Bankers Trust Australia Limited
Phone: 61-2-9259 3944    Fax: 61-2-9259 2659


        -----Original Message-----
        From:   Rupp Thomas (Illwerke) [SMTP:thomas.rupp AT ILLWERKE.CO DOT AT]
        Sent:   Saturday, July 04, 1998 11:13 PM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        ANR2020E Invalid parameter - ORIGINATOR.

        Hi ADSM gurus!
        I've a small problem with the ADSM Administrative Client
        (3.1.01) on Windows NT 4.0 (SP 3). Server is ADSM for VM
        2.1.0 without PTF's.

        I've changed the Activity Log include message times to narrow
        the amount of messages. But now I always get the message

        ANR2020E Invalid parameter - ORIGINATOR.

        even if I reset the values.
        Has anybody seen this problem before?

        Kind regards
        Thomas Rupp
        Vorarlberger Illwerke AG
        thomas.rupp AT illwerke.co DOT at
<Prev in Thread] Current Thread [Next in Thread>