>-----Original Message-----
>first off change your heartbeat interval to something
huge - i'd try 2-3
>days. To do this connect to your SQL Server in EM, right
click on
>Replication Monitor and select Refresh Rate and
Settings, then select
>Inactivity Threshold and set this value to something
like 4000 minutes.
>
>Next you really should reboot your Publisher.
Replication relies on caching
>replication metadata and I have run into instances where
the log reader
>hangs on initialization like what you are seeing. A
reboot clears this
>condition. When you encounter this condition your log
reader generally gives
>the message initializing before goign to the suspect
method.
>
>The underlying problem is that your replication topology
has choked on this
>large amount of data. I'd consider beefing up the amount
of hardware you
>have as replication can handle such large bulk inserts.
>
>You might want to try dropping your subscription, and
then refreshing, to
>clear this condition as well.
>
>"larry" <anonymous@discussions.microsoft.com> wrote in
message
>news:19a4901c42230$9cb10d00$a601280a@phx.gbl...
>> Running SQL 2K & Win 2K
>>
>> I had to bulk insert 220,000 records into a table that
is
>> replicated via a transactional publication.
>>
>> The Log Reader gave me an error indicating that I had
to
>> increase the size allocatedto the dB. I did this and
>> this error disappeared. I am now getting a timeout
>> error 'The agent is suspect. No response within last
10
>> minutes.'
>>
>> This error continued for 36 hours. I deleted the
>> publication and recreated it via SQL. I am still
getting
>> the same error on the log reader....'The agent is
>> suspect. No response within last 10 minutes.'
>>
>> Nothing is replication from this location due to this
>> error. How can I clear out the Log Reader so of this
220L
>> records so replicaton will restart.
>>
>> Any help is appreciated,
>>
>> Larry....
>>
>>
>
>
>.