Re: Replication Monitor disappears

Tech-Archive recommends: Fix windows errors by optimizing your registry

Yes, I am sure its rights issue but not sure why my replication monitor did
not come up after I have started the SQL Agent service with dev admin account.

FYI If it helps-
SQL Agent started only when I have retyped dev admin and password.

Regards


"Hilary Cotter" wrote:

> This could be a rights issue. Connect to the problem server using the sa
> account and see if it shows up.
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "SQL Replicatio Guy" <SQL Replicatio Guy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message news:F6019804-2776-4532-836D-C51156354A45@xxxxxxxxxxxxxxxx
> > All,
> > I have setup transactional replication in our dev environment with
> > publisher, distributor and subscriber on same box for testing and it was
> > running fine for some time. When I was setting up replication I had SQL
> > Service logged on using local system account and sql agent login was dev
> > admin account.
> >
> > Yesterday when we have restarted the server, sql service came fine but SQL
> > Agent did not start. when I tried to start agent it manually it errored
> > saying login donot have permissions.
> >
> > When I have checked Agent login, its using same dev admin login which
> should
> > have all permissions. Finally I was able to start the SQL Agent service by
> > retyping dev admin and password from services.
> >
> > This time though SQL Agent started Replication monitor disappeared from
> > Enterprise manager. Any suggesstions why it happened..??
> >
> >
> >
> >
>
>
>
.

Relevant Pages

  • Re: Solution to agent failure - A required privilege is not held by the client.
    ... Director of Text Mining and Database Strategy ... Looking for a SQL Server replication book? ... error when using domain accounts for the SQL Agent and replication ... agents (which results in proxy accounts) with SQL 2005 replication: ...
    (microsoft.public.sqlserver.replication)
  • SQLServer Error: 22046, Encryption error using CryptProtectData
    ... Running transactional and snapshot replication on a SQL 2005 Enterprise SP2 ... Tried using both the SQL agent service account and a proxy account created ... Both produce the following error in SQL Agent: ... There's an SPN for the SQL service account but there is no delegation. ...
    (microsoft.public.sqlserver.replication)
  • Replication Monitor disappears
    ... When I was setting up replication I had SQL ... Service logged on using local system account and sql agent login was dev ... When I have checked Agent login, its using same dev admin login which should ...
    (microsoft.public.sqlserver.replication)
  • Solution to agent failure - A required privilege is not held by the client.
    ... error when using domain accounts for the SQL Agent and replication ... agents (which results in proxy accounts) with SQL 2005 replication: ... if your company uses GPOs to control the local policy user ...
    (microsoft.public.sqlserver.replication)