Timeout error running snapshot agent

[Kohn]

We have been unable to create a new snapshot since the first one that was
created when we initialized the publication. Below is the log entry of the
offending step. Any ideas on the cause or how to find the cause?

Thanks,

2006-05-12 05:28:15.76 [0%] Preparing table '[dbo].[TestsAsmReadings]' for
merge replication
2006-05-12 05:28:15.76 [0%] Preparing table '[dbo].[TestsSecondData]' for
merge replication
2006-05-12 05:28:15.78 [0%] Preparing table '[dbo].[TestsTsiReadings]' for
merge replication
2006-05-12 05:28:15.78 [0%] Preparing table '[dbo].[TestsVehicle]' for merge
replication
2006-05-12 05:28:15.79 [0%] Preparing table '[dbo].[TestsSafetyItems]' for
merge replication
2006-05-12 05:28:18.61 [0%] Setting up the publication for filtered articles
2006-05-12 05:58:23.73 [0%] The replication agent had encountered an
exception.
2006-05-12 05:58:23.73 Source: Replication
2006-05-12 05:58:23.73 Exception Type:
Microsoft.SqlServer.Replication.SqlCommandTimeoutException
2006-05-12 05:58:23.73 Exception Message: Timeout expired. The timeout
period elapsed prior to completion of the operation or the server is not
responding.
2006-05-12 05:58:23.73 Message Code: -2
2006-05-12 05:58:23.73

[Paul Ibison]

It could be a blocking issue - if you are doing transactional replication
you might want to try the concurrent snapshot processing option.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

[Kohn]

The application uses merge replication and the snapshot agent was started at
a time when there would not be any activity. Even if this were not the case,
I'm curious if you'r. saying that snapshots cannot be taken on systems that
have any activity. Is there a way to determine the offending activity?

Post by Paul Ibison
It could be a blocking issue - if you are doing transactional replication
you might want to try the concurrent snapshot processing option.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
http://www.nwsu.com/0974973602p.html)

[Paul Ibison]

Snapshots require an exclusive lock on the source table for the read. You
could use the sp_blocker_pss80 scripts to find out more details on the
blocking you are experiencing
(http://www.support.microsoft.com/default.aspx?scid=kb;en-us;271509). NB if
you're using SQL Server 2005 you can monitor this event directly in profiler
using the 'Blocked Process Report'.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)