I'm not exactly sure what you mean by deploy it. We use a network share
that stores all of the snapshots generated by the snapshot jobs. The
machine was connected to the LAN when we set up the subscription. When we
set it up, there was no subscription on the target machine. There was also
no merge agent listed on the publisher for that subscriber. Does that help,
"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:u5e5dxS3GHA.4024@TK2MSFTNGP03.phx.gbl...
> How did you deploy your snapshot? It sounds like there is a lingering
> merge subscription somehow.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> 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 >
>
>
> "footyplayer" <anonymous@discussions.microsoft.com> wrote in message
> news:uciYJWP3GHA.3828@TK2MSFTNGP06.phx.gbl...
>> Hi All,
>>
>> We are running SQL2KSP4 and have 40+ subscribers (anonymous) using merge
>> replication. We added a subscription to a machine, and when we try to
>> synchronize it we receive:
>>
>> Invalid subscription type is specified. A subscription to publication
>> 'xxx' already exists in the database with a different subscription type.
>>
>> We are using the SQL Merge ActiveX control to accomplish synchronization.
>> I implemented error handling as shown in Books Online. If I look in the
>> merge agent list for the publication, I only see one merge agent present
>> for the subscriber in question. Any suggestions??
>>
>> Thanks in Advance,
>> Brad
>>
>
>