all groups > sql server replication > september 2007 >
You're in the

sql server replication

group:

transactional rep agent thinks Snapshot wasn't run



transactional rep agent thinks Snapshot wasn't run Jon
9/12/2007 3:10:02 PM
sql server replication: Hi,

I get this "Action Message" when I look at the "View Details" for a
transactional replication agent:

The concurrent snapshot for the publication '[publication name]' is not
available because it has not fully generated or the Log Reader Agent is not
running to activate it. If generation of the concurrent snapshot was
interrupted, the Snapshot Agent for the publication

It seems like I get this for every transactional replication I attempt to
set up. I've looked at permissions on the folder containing the snapshot
files.

The publisher is a SQL 2005 server (uses same server as distributor). There
are currently several merge replications successfully replicating from the
same server.

Re: transactional rep agent thinks Snapshot wasn't run Hilary Cotter
9/13/2007 12:00:00 AM
Make sure the log reader agent is running and try to run the snapshot again.
The way it works is a snapshot is generated and then distributed. Then the
log is consulted at the point the snapshot started to see what changes
occurred since the start and these changes are also sent to the subscriber.

--
RelevantNoise.com - dedicated to mining blogs for business intelligence.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
[quoted text, click to view]

Re: transactional rep agent thinks Snapshot wasn't run Yuri Budilov
9/19/2007 10:32:00 PM
Couple of more thoughts.

I had this occur recently (SQL 2005 SP2). In my case the problem was due to
a lot of undistributed commands from other (unrelated) publications in
distribution db and also a lot of transactions still in the T-Log yet to be
loaded into distribution db. Once they all synchronised the troublesome
shapshot become available (without having to re-generate it) and applied
successully. YMMV.

I use Read_Committed_Snapshot on publication database and the snapshot was
of the concurrent kind so perhaps there was a long running update transaction
that could have caused it i.e. once completed the snapshot was deemed
"completed".
--
Yuri Budilov
Melbourne, Australia


[quoted text, click to view]
AddThis Social Bookmark Button