Discussion:
sp_MSload_replication_status
(too old to reply)
larry
2004-09-29 16:31:41 UTC
Permalink
What dB should sp_MSload_replication_status executed in
to fix that pesky red 'X' in replication monitor?
Paul Ibison
2004-09-29 19:03:25 UTC
Permalink
Larry,
it doesn't matter which database you run this from.
If it doesn't work, try restarting the sql server agent.
HTH,
Paul Ibison

(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
a***@discussions.microsoft.com
2004-09-29 20:40:04 UTC
Permalink
Paul,

The SQL Server gets restarted nightly and this problem
still occurs. I cannot restart SQL in the middle of the
day, because it is a production server.

When I run sp_MSload_replication_status, there is no
effect. Any other ideas??

Larry...
-----Original Message-----
Larry,
it doesn't matter which database you run this from.
If it doesn't work, try restarting the sql server agent.
HTH,
Paul Ibison
http://www.nwsu.com/0974973602p.html)
.
Paul Ibison
2004-09-29 21:44:50 UTC
Permalink
Larry,
these rogue red x's should be removed when restarting the server, so I'd
just wait till the reboot - after all they aren't actually a problem. BTW
I'm asuming that they are rogue icons - ie the error isn't registered
correctly in one of the agents.
Rgds,
Paul Ibison

(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Hilary Cotter
2004-09-30 01:56:45 UTC
Permalink
can you query the msrepl_errors table in the distribution database to get an
idea of any possible errors that might have occured.

select * from msrepl_errors where error_type_id is not null
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Post by Paul Ibison
Larry,
these rogue red x's should be removed when restarting the server, so I'd
just wait till the reboot - after all they aren't actually a problem. BTW
I'm asuming that they are rogue icons - ie the error isn't registered
correctly in one of the agents.
Rgds,
Paul Ibison
http://www.nwsu.com/0974973602p.html)
a***@discussions.microsoft.com
2004-09-30 14:47:29 UTC
Permalink
Hilary,

The query returned 4 rows, but the are errors were
resolved.

Violation of PRIMARY KEY constraint 'PK_PO_Detail'.
Cannot insert duplicate key in object 'PO_Detail'.

Larry..

Loading...