Hi there,
On out distributing server I receive the following message:
Replication-Replication Transaction-Log Reader Subsystem: agent
AIRWARE_SQL1-Airware-3 scheduled for retry. The process could not
execute 'sp_replcmds' on 'AIRWARE_SQL1'..
This has happened several times now. I have looked up info ons this sp
and I can't find why this error occurs: the distributer is the only
client connecting to the publishing server.
I have stopped and restarted MS SQL Server service on the distributor,
to no avail. I do not wish to stop and start the publishing server yet,
since this is heavily used, unless there is no alternative.
Is there a way to check if sp_replcmds is used by another client? Any
other reason why this error could occur?
Some config info:
Publisher and Distributor are on different machines. The Distributor
also distributes another database on the same Publisher, there is no
problem there. Both servers run W2K with the latest patches, and both
run SQL Server 2000 with sp 3a.
Last Friday someone found it necessary to reboot the Distributor and the
SQL Server Agent was not started. This morning I found out that ther was
a huge transactionlog on the Publisher full of non-replicated
transactions. I restarted the SQLServerAgent and replicationprocess
started; some logspace is freed.
A little later a connectionfailure from the Publisher to a completely
different server,nothing to do with the replicationprocess. This had to
do with autorityproblems with the SQLServerAgent account, which were
changed. The Windows Administrator on duty solved the problem and
connections could be made. From aproximately that time on the
replicationproblems happened.
-------------------------
Tnx,
Hans Brouwer
On out distributing server I receive the following message:
Replication-Replication Transaction-Log Reader Subsystem: agent
AIRWARE_SQL1-Airware-3 scheduled for retry. The process could not
execute 'sp_replcmds' on 'AIRWARE_SQL1'..
This has happened several times now. I have looked up info ons this sp
and I can't find why this error occurs: the distributer is the only
client connecting to the publishing server.
I have stopped and restarted MS SQL Server service on the distributor,
to no avail. I do not wish to stop and start the publishing server yet,
since this is heavily used, unless there is no alternative.
Is there a way to check if sp_replcmds is used by another client? Any
other reason why this error could occur?
Some config info:
Publisher and Distributor are on different machines. The Distributor
also distributes another database on the same Publisher, there is no
problem there. Both servers run W2K with the latest patches, and both
run SQL Server 2000 with sp 3a.
Last Friday someone found it necessary to reboot the Distributor and the
SQL Server Agent was not started. This morning I found out that ther was
a huge transactionlog on the Publisher full of non-replicated
transactions. I restarted the SQLServerAgent and replicationprocess
started; some logspace is freed.
A little later a connectionfailure from the Publisher to a completely
different server,nothing to do with the replicationprocess. This had to
do with autorityproblems with the SQLServerAgent account, which were
changed. The Windows Administrator on duty solved the problem and
connections could be made. From aproximately that time on the
replicationproblems happened.
-------------------------
Tnx,
Hans Brouwer