March 4, 2013 at 2:37 pm
Hi all,
I have Snapshot replication setup. I added a new article to my publication. I then went to the Replication monitor and right clicked on Reinitialize all Subscriptions. I get the error below. But when I manually run the SQL job which creates the snapshot and then run the job for the subscriber, everything runs fine. I don't understand the Reinitialize all subscriptions error message. I first thought this was a permissions issue, but have played around with the permissions in the distribution database and nothing has resolved the error.
Replication Monitor could not reinitialize one or more subscriptions that support automatic initilization. Additional Information: An exception occurred while executing a transact sql statement or batch. (Microsoft.SQLServer.ConnectionInfo)
The subscripttion status of the object could not be changed. Could not update the distribution database subscription table. The subscription status could not be changed. Changed database context to "TestDatabase". (Microsoft SQL Server: Error 14068)
June 14, 2013 at 2:25 pm
I am getting the same error.
Was this ever resolved?
June 14, 2013 at 2:43 pm
Hi Michael,
I do not have a resolution to this error. Instead, I've been working around it and initializing the subscription from where the job runs and running it directly from there. I would like to be able to reinitialize with the GUI if possible, but have not been able to figure out what causes the error.
March 25, 2015 at 8:21 am
Hi jjolk
Can you pls explain how you are managing the workaround from jobs?
jjolk (6/14/2013)
Hi Michael,I do not have a resolution to this error. Instead, I've been working around it and initializing the subscription from where the job runs and running it directly from there. I would like to be able to reinitialize with the GUI if possible, but have not been able to figure out what causes the error.
Online Trainer For SQL DBA and Developer @RedBushTechnologies with 18 yrs exp.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply