Couple of more thoughts.
I had this occur recently (SQL 2005 SP2). In my case the problem was due to
loaded into distribution db. Once they all synchronised the troublesome
successully. YMMV.
that could have caused it i.e. once completed the snapshot was deemed
"completed".
"Hilary Cotter" wrote:
> 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 > "Jon" <Jon@discussions.microsoft.com> wrote in message
> news:7F43689B-D509-4AE1-917F-4C7075071937@microsoft.com...
> > 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.
> >
> > Thanks
>
>