ADSM-L

Re: Notes Agent time zone update

1999-03-10 23:36:12
Subject: Re: Notes Agent time zone update
From: Nathan King <nathan.king AT USAA DOT COM>
Date: Wed, 10 Mar 1999 22:36:12 -0600
Are you sure ADSM has gone down?

The message

        -----Original Message-----
        From:   Sean Stecker [SMTP:Stecker.Sean AT ORBITAL-LSG DOT COM]
        Sent:   Wednesday, March 10, 1999 3:50 PM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Notes Agent time zone update

        All,

        It seems that the message I posted earlier did not go through. Let
me try again.
        Maybe I got some misinformation concerning the archive bit.  Must
have been
        wrong.  Either way, it was a logical explanation to us since it is
working now.
        If there is an archive bit or there isn't, I don't know. Sorry for
the mass
        hysteria.

        Next,  we are experiencing an anomoly with our Notes Agent and would
like to
        know if anyone has experienced this.  When we run an incremental
from
        dsmnotes.exe, it bumps up the time on our Domino server 7 hours to
GMT.  We are
        in Arizona, mountain time right now.  This is conflicting with the
scheduling
        feature of Lotus Notes for our users.  Any Ideas??

        Third,  when accessing the ADSM server from another workstation, my
desk for
        instance, if an incorrect login takes place, it shuts down the ADSM
server
        service.  I lose all connectivity to the tape library, and basically
any
        functionality from ADSM.  After running dsmserv.exe, it restarts the
services
        and ADSM comes back online.  Here is the message from the activity
log:

        ANR0423W  session 150 for administrator steck (  ) refused -
        administrator name not registered.       ( I used an incorrect login
here)

        This is when the server service dies.  Here is the message after
running
        dsmserv.exe:

        [Nathan King]  ANR09901  ADSM server restart recovery in progress.
        ANR0259E  unable to read complete restart / checkpoint information
from any
        database or recovery log volume.

        Even though the last error would lead me to believe something went
wrong, it
        seems to come back just fine. Could this just be something with our
server, or
        is this a known issue?  Any comments would be appreciated.  There
are very few
        places a person can get help just by asking. Thanks again for all
the responses.

        Sean M. Stecker
        stecker.sean AT orbital-lsg DOT com
<Prev in Thread] Current Thread [Next in Thread>