Rowguid not created on publishing a merge publication

I have a problem creating new merge publication on my database. My database contains several tables that don't have keys, so when I create the publication it was prompted that a  unique rowguid column will be automatically added. But when the creation of publication completed successfully I didn't find any new column added in my tables, and the snapshot can't be created too, so it can't be replicated.
Can anybody help me to solve this problem?
yentoAsked:
Who is Participating?
 
danblakeConnect With a Mentor Commented:
IF you create the rowguid manually (then it would not allow you to alter this unless replication/subscription was disabled on the tables you were looking at, so I'm presuming this has been done and then the publication/subscribers have been recreated).

The snapshot will not be created until a subscriber exists.  
(So I'm presuming here that you've now created a subscriber and havn't yet rerun the snapshot agent.  Try now rerunning the snapshot agent, and lets have a look at the logs then)

Can you also catch all the information of the agents for the moment:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;312292
This should allow us to debug what is going on.. (I am interested in the error msgs/output msgs from the snapshot agent in this instance).


Can you also let me know which version/edition of sql-server you are using.
0
 
danblakeCommented:
0
 
yentoAuthor Commented:
Yes, I've applied SP1.
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
danblakeCommented:
We may have to create this manually,
  add a uniqueidentifier data-type to every table as required.
  Specify that this data-type is a ROWGUIDCOL,
  and specify newid() as the default value.

I've seen somebody else where the merge replication has not added the correct column as required.


I didn't find any new column added in my tables, and the snapshot can't be created too, so it can't be replicated.
--> Did the snapshot generate an error ?
What happens when you start the snapshot agent to generate a snapshot manually ?
0
 
yentoAuthor Commented:
If I create the snapshot manually, it was done as if it has succeeded, but there was nothing created in the ReplData folder, and when I try to create a new subscription it was completed but with a message:
"Subscriptions were created successfully at the following Subscribers:
      MYSERVER
The subscription at Subscriber 'MYSERVER' cannot be initialized immediately because the snapshot for this publication is not yet available. To initialize the subscription, start the Merge Agent after the snapshot is available."

I've tried to create the rowguid manually, but the results are the same.
0
 
yentoAuthor Commented:
The problem is solved. When I use the replication logging, I found that the snapshot agent failed to access the ReplData folder. When I see the permission on the folder I found that the user had a read only permission. After I changed the permission to full access, the snapshot is created succesfully.
Thanks for the clue... :)
0
 
danblakeCommented:
No worries, glad to help.
0
All Courses

From novice to tech pro — start learning today.