Log shipping using Enterpirse Ed. Monitor DB getting out of sync

We are testing the canned log shipping built into sqlserver2k ent. Somehow,
the monitor db that tracks what has been backed-up, shipped, etc is out of
sync. The primary and secondary DBs are synced up and the shipping is
working fine but the monitor doesnt seem to know that. We suspect we know
what happened (sqlAgent was stopped when log shipping was started) but this
raises a bigger question.
If the monitor db should get out of sync (say, for example, it is stopped
for some time), how to we resync it? Conceptually, we want to tell it that
the primary and secondary are in sync (which we can separately verify). Any
ideas? Is this even the right news group?
-alanNever mind. It was an NT domain security issue. We just needed to make the
userName match for all the services (sqlserver and agent) on all the
machines.
"Alan Berezin" <aberezin@.drillinginfo.com> wrote in message
news:eEjNKJkRDHA.1924@.TK2MSFTNGP12.phx.gbl...
> We are testing the canned log shipping built into sqlserver2k ent.
Somehow,
> the monitor db that tracks what has been backed-up, shipped, etc is out of
> sync. The primary and secondary DBs are synced up and the shipping is
> working fine but the monitor doesnt seem to know that. We suspect we know
> what happened (sqlAgent was stopped when log shipping was started) but
this
> raises a bigger question.
> If the monitor db should get out of sync (say, for example, it is stopped
> for some time), how to we resync it? Conceptually, we want to tell it
that
> the primary and secondary are in sync (which we can separately verify).
Any
> ideas? Is this even the right news group?
> -alan
>sql