Replication Monitor Reporting Error

I am continually having problems with the replication monitor reporting
erronous errors. I have read in the past that this can be resolved by
restarting SQL, but that does not solve my problem because SQL is restarted
nightly on all SQL servers with the commands listed below....
REM Stop SQL Server Agent
net stop sqlserveragent
REM Stop SQL Server
net stop MSSQLServer
REM Start SQL Server
net Start MSSQLServer
REM Start SQL Server Agent
net start sqlserveragent
I am at a loss. I have 17 SQL servers and the problem does not exist on all
of them, but where the error is being reported, it is always the same servers.
HELP!!!
Larry...
Which agent is generating the error.
Normally you can use sp_MSloadresetstatus to fix this problem. I'm not
totally sure if this the name of the proc but do a search like this
select name from master.dbo.sysobjects where name like '%load%' and name
like '%status%' and type='p' and it will show up
"Larry" <Larry@.discussions.microsoft.com> wrote in message
news:AFFB37CD-AB2A-4451-ADFB-53DDBBED8348@.microsoft.com...
>I am continually having problems with the replication monitor reporting
> erronous errors. I have read in the past that this can be resolved by
> restarting SQL, but that does not solve my problem because SQL is
> restarted
> nightly on all SQL servers with the commands listed below....
> REM Stop SQL Server Agent
> net stop sqlserveragent
> REM Stop SQL Server
> net stop MSSQLServer
> REM Start SQL Server
> net Start MSSQLServer
> REM Start SQL Server Agent
> net start sqlserveragent
> I am at a loss. I have 17 SQL servers and the problem does not exist on
> all
> of them, but where the error is being reported, it is always the same
> servers.
> HELP!!!
> Larry...
|||Hilary,
I ran sp_MSload_replication_status, on both the Master dB and the dB
reporting the error, but the pesky red X did not clear up. Any other ideas?
Larry...