.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

merg replication error

Posted By:      Posted Date: September 22, 2010    Points: 0   Category :Sql Server


When i am configuring replication its throwing error mentione below

This publication differs from the publication to which the subscription was initially created. The original publication may have been deleted and replaced with a new publication with the same name. At the subscriber, delete the subscription and recreate it for the new publication


any suggestions

View Complete Post

More Related Resource Links

merg replication error



 When i am reinitializeing subscriber getting following error

unexpected eof encountered in bcp datafile

more details:

·          The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001

·          The process could not bulk copy into table '"dbo"."MSmerge_contents"'. (Source: MSSQL_REPL, Er

Error in Replication: connection was chosen as the victim in a deadlock

I'm using a merge replication with SQL 2008 at server and SQL Express 2008 on subscribers. We are using around 100 subscribers. I'm getting the following error once two subscribers replicate at the same time. The final number of transaction uploaded to the server is always arong 100 and a similar number in the downloads, so the amount of transaction is not an issue. I'he been playing with the merge profile with no luck. The merge process could not replicate one or more INSERT statements to the 'Publisher'. A stored procedure failed to execute. Troubleshoot by using SQL Profiler. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200990) Get help: http://help/MSSQL_REPL-2147200990 A query executing on Publisher 'xxxxx' failed because the connection was chosen as the victim in a deadlock. Please rerun the merge process if you still see this error after internal retries by the merge process. (Source: MSSQLServer, Error number: 1205) Get help: http://help/1205 Any idea? This is getting to a critical point where transactions are not being uploaded to the server.  Additonally, there are a lot of blocks between the subscribers, and they are mainly associated with table MSmerge_partition_groups  

XML Column containing single quote causes replication error

We have SQL Server 2005 transactional replication set up, and some of our tables have XML datatype columns.  We have run into an issue with the following error in the publication: Incorrect syntax near 's'. (Source: MSSQLServer, Error number: 102) Get help: http://help/102 Looking at the distribution database, I was able to extract the offending command, and it turns out that the XML column has a single quote (') embedded in it, and the command that was generated for inserting the row into the subscriber table has bad syntax because of the single quote (i.e., it is not escaped).  One interesting note is that the single quote happens to also show up in a non-XML column, and the command segment for that column was generated correctly (it was escaped). Is there a workaround / solution for this?

error in merge replication

Hi ALL,      I have merge replication configured between republishers( sql 2008) and subscribers( sql 2000)...i am getting the following error while trying to sync   The merge process could not update the list of subscriptions. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201010) Get help: http://help/MSSQL_REPL-2147201010 Cannot insert duplicate key row in object 'dbo.sysmergesubscriptions' with unique index 'uc1sysmergesubscriptions'. (Source: MSSQLServer, Error number: 2601) Get help: http://help/2601 The subscription could not be created. (Source: MSSQLServer, Error number: 14057)   Any suggestions y i am getting this error TIA

Replication Error - Can't Insert Null into MSSubscription_agents.allow_subscription_copy

In attempting to set up a transactional replication subscription via the UI, I keep getting the error that I cannot insert a Null into the MSSubscription_agents table.  Originally, this was on the allow_subscription_copy column.  One resource suggested altering the column to allow Nulls but that only moved the issue to the attach_state and, later, attach_version columns.  My immediate issue was resolved with these changes BUT I'm really concerned that I need to alter a system table in order to allow a fairly simple replication subscription to be configured.  Has anyone run into this issue and is there a better work around available? I'm running SQL 2008 Enterprise Edition SP1 in a 64-bit environment on both the Publisher/Distributor and Subscriber servers.

report error replication sql 2008

In 2000 sql error occurred when the replications showed the line and record with, exactly what record. As I see it in sql 2008?

Replication : Error: subscription already exists

I am receiving an error when i try to recreate a subscription. Error: subscription already exists. I ran expired subscription clean up job but still received this error. what am i missing?

Merge replication error

Hi ALL,  I have merge replication configured on sql server 2008. After two weeks snapshot agent ran again and when merge agent is running it throwing error you must rerun snapshot because current snapshot files are obsolete i dnt change anything on publication or snapshot folder location but still i am getting error   Any suggestion...TIA

Error: The replication agent has not logged a progress message in 10 minutes

Hello,      We are consistently getting the error message below on our subscribers that have blob images. Is there a way to increase a setting to avoid SQL to throw this error, or another suggestion? Thanks in advance.   John   Error messages: The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active.   18 -BcpBatchSize 10000018 -ChangesPerHistory 10018 -DestThreads 218 -DownloadGenerationsPerBatch 518 -DownloadReadChangesPerBatch 10018 -DownloadWriteChangesPerBatch 10018 -FastRowCount 118 -HistoryVerboseLevel 318 -KeepAliveMessageInterval 30018 -LoginTimeout 1518 -MaxBcpThreads 218 -MaxDownloadChanges 018 -MaxUploadChanges 018 -MetadataRetentionCleanup 118 -NumDeadlockRetries 518 -PollingInterval 6018 -QueryTimeout 40018 -SrcThreads 218 -StartQueueTimeout 018 -UploadGenerationsPerBatch 318 -UploadReadChangesPerBatch 10018 -UploadWriteChangesPerBatch 10018 -Validate 018 -ValidateInterval 60   Due to the memory leak issue with respect to replicating blobbed images we have changed UploadGenerationsPerBatch to = 3.

Error message in opening a view after Replication server restored

Hi, Yesterday Replication was broken as Publisher was down. After it was restored, I tried to open a view in Subscriber and I get the following error message [Microsoft] [ODBC SQL Server Driver] [SQL Server] Login failed for user 'Repl admin'   Any suggestions to get around this problem.   Thanks in advance -Jaya

Replication error

what does this error mean? Replication monitor could not start the snapshot agent to generate a new snapshot. you must start the snapshot agent manually before the subscription can be reinitialized. error 22022?

Tx Replication Error

Receiving error on subscriber: an error occured while attempting the access the subscription . (view synchronization status) . The subscription does not exist.  It just suddenly stopped working.

Tx Replication Error when renaming Subscription Database

Tx Replication Errors when renaming Subscription Database. Please help. It seemed to work earlier, but now is giving errors when i rename subscription database.

Tx Replication Error


Command attempted:

if @@trancount > 0 rollback tran
(Transaction sequence number: 0x00001E880000202E000800000000, Command ID: 1)

Error messages:

The row was not found at the Subscriber when applying the replicated command. (Source: MSSQLServer, Error number: 20598)
Get help: http://help/20598

TX Replication Error: Agent set to verbose 2


Tx Replication is giving an error

Command attempted:

if @@trancount > 0 rollback tran
(Transaction sequence number: 0x00001E880000202E000800000000, Command ID: 1)

Error messages:

2010-09-16 20:10:17.543 Microsoft SQL Server Log Reader Agent 10.0.2531.0
2010-09-16 20:10:17.597 Copyright (c) 2008 Microsoft Corporation
2010-09-16 20:10:17.622 Microsoft SQL Server Replication Agent: logread
2010-09-16 20:10:17.647
2010-09-16 20:10:17.663 The timestamps prepended to the output lines are expressed in terms of UTC time.
2010-09-16 20:10:17.717 User-specified agent parameter values:
   -Publisher Server_A
   -PublisherDB db_A
   -Distributor Server_b
   -DistributorSecurityMode 1
   -Output C:\Users\xyz\Desktop\OUTPUTFILE.txt
   -Outputverboselevel 1
   -XJOBID 0x052684F1D410C746B5AFE798220E5440
   -XJOBNAME Server_A-db_A-5
   -XSUBSYSTEM LogReader
   -XSERVER Server_A
   -XCancelEventHandle 0000000000000960
   -XParentProcessHandle 00000000000009F0

Tx Replication Error: VIEW


I have a Tx Replication in place. The Publisher db and the subscriber db have different names. Now, we have a view that references two databases. One of them is this replicated db and the other is a db restored on the subscriber server. How can i go about replicating the view without running into errors? 


Server A------------------->Server B

Db_A(pub)------------------>DB_A'(subscriber Database Renamed)

Db_B  DB_B(restored)


View(references Db_A & Db_B)--------Need to be replicated------>Server B

Serve to server Transaction Replication error


I have windows 2003 sp2 servers each hosts SQL Server 2008 SP1 standard edition. I am trying to replicate both servers, using the tutorial available in the online documentation <Tutorial: Replicating Data Between Continuously Connected Servers> which can be found at: ms-help://MS.SQLCC.v10/MS.SQLSVR.v10.en/s10rp_1devconc/html/9c55aa3c-4664-41fc-943f-e817c31aad5e.htm

I have created the users (repl_logreader, repl_distibution, repl_snapshot, and repl_merge and setting their security. Then I have created the distibutor, setting database security as mentioned in the document, and last creating the publication with a snapshot to be run immediately, distributor and publisher are on the same server and the publication will be pushed to the subscriber. Once the publication is created succesfully, I am checking the agents to see the errors. I am always stuck with the following two error messages:

1- snapshot agent error:

Error messages:

Message: Failed to create AppDomain "mssqlsystemresource.dbo[runtime].1090".
The domain manager specified by the host could not be instantiated.
Failed to create AppDomain "mssqlsystemresource.dbo[runtime].1091".
The domain manager sp

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend