November 21, 2007 at 1:29 pm
I am running into a "The publication '%' does not exist" error when trying to programmatically sync between publisher and subscriber both running Windows XP Pro s2 and MSDE2000 sp4.
The publisher was setup to store the snapshot files in a directory similar to the one given below, and they are being compressed. Before setting this up, I programmatically create and share the folder giving EVERYONE full-access (both local and remote) to the ReplicationData folder. I have also tested to make sure the subscriber is not having access issues. Here's the snapshot folder assigned to the publication:
[font="Courier New"]\\publisher_server_name\ReplicationData\ReplData[/font]
The subscriber is setup to have an alternate snapshot folder location, which is being set to the same address as above. As I stated above, the subscriber is able to access this folder with full-access:
[font="Courier New"]\\publisher_server_name\ReplicationData\ReplData[/font]
The publisher and subscriber are both being setup without any errors, and I have confirmed that the settings work when using a SQL2005 publisher and MSDE2000 subscriber. This makes me assume that there must be some issue when dealing with both the Pub and Sub running MSDE2000.
My issue arrises immediately when STARTING the sync, but I have not been able to figure out why. I have searched the web for people experiencing a similar problem, but so far have not found any answers. Please help!
p.s. I would have provided a code sample, but it is literally hundreds of lines of code, and I'm pretty sure there is either some underlying issue that I am not aware of, or I am simply missing some setting that I did not mention above. I tried to explain my setup as best as possible. Please let me know if I need to clarify anything.
November 21, 2007 at 3:40 pm
Here are some replies I made to a different forum I have this posted at. Past comments are in bold. My responses follow.
What type of replication are you using? snapshot/trans/merge?
* I am using merge replication.
What do you mean by "... trying to programatically sync..." are
you using dmo to manage?
* I just meant that I am setting everything up in an application
using SQL stored procedures. I'm use Microsoft's ActiveX component
for replication management.
You cannot use msde 2k as publisher in transactional replication.
You can use as pub of snapshot and merge, and as subscriber to all 3.
You cannot use a remote distributor w/ msde 2k.
* The Distributor and Publisher are the same server. Subscribers
are remote. Could this be the issue? I'm not sure I fully understand
it.
Also - watch the size of you db's - 2 gig limit will cause agents
to stop.
* None of the databases exceed 2GB.
November 21, 2007 at 3:46 pm
By the way, I am creynolds (the original poster). I didn't realize I already had an active account.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply