.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

Replication : Error: subscription already exists

Posted By:      Posted Date: September 14, 2010    Points: 0   Category :Sql Server
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?

View Complete Post

More Related Resource Links

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.

error occurred while I tried to setup transaction replication with updateable subscription

   when I tried to setup transactional replication with updatable subscriptions between two nodes, an error occurred.

The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "REPL1 " was unable to begin a distributed transaction. Changed database context to 'database1'.

OLE DB provider "SQLNCLI" for linked server "REPL1" returned message "No transaction is active.". (.Net SqlClient Data Provider)
 May I know whether in order to setup transactional replication, do I need to run replication agents under domain users or local users?

thank you

Merge Replication - Subscription Error


Hi All,


I get this error when I try to run the sync on a subscription. I found that this actually has something to do with permissions.

“ String or binary data would be truncated. [SQLSTATE 22001] (Error 8152). The step failed

If the account I am using is a server sysadmin does it still have to be part of the db_owner in publication and distribution dbs as shown below? It has write access to the file share as well so I am not sure I understand what the problem is? It is also a sysadmin on the client where the subscription is going?




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  

Merge Replication: Fails using Replication.SaveProperties when changing Subscription Info

I'm trying to use SQL Server/Compact Framework 3 Merge Replication functionality and am running into a problem when calling Replication.SaveProperties (using c#). I was hoping to get some clarification on whether its my interpretation on how things should work vs a coding problem. Basically, the Merge Replication seems to work as I can sync information between my handheld and server databases.  However, I've created a form on my handheld so that the user can change some synchronication settings (e.g. Publication or Publisher Name) and then save it.  What I've noticed is : 1) You can NOT call Replication.SaveProperties until after a synchronization is performed (otherwise you get an error message).  Assuming this is so that it can create the "__sysMergeSubscriptions" table. Does this sound right? 2) If I then try to change the saved Subscriber information via another call to Replication.SaveProperties (e.g. change the Publication info), I then get an error message that says: The subscription was not found. Publisher, PublisherDatabase, or Publication  could be incorrect. Is this normal behavior?  Does this mean that you can you NOT change subscriber information; only add or drop it? Thanks,  Ed

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?

For a Data-driven Subscription, If it Processes 20 but 2 error , how do i just run the ones that err

 I'm trying to figure out if there is a way to just run the errored out ones.  Sometimes I have up to 100 being processed and need to only rerun the ones that error out. Is there a way to do this? and how?

Merge Replication, Push Subscription : The snapshot takes centuries to apply

Well, not centuries, except that the users are storming the gate. I'm trying to find how to get the snapshot moved to the subscriber and applied in a reasonable time. Last time was successful, but took 2 1/2 days to build the subscriber database from the snapshot. Hillary responded: Something is very wrong here. You should be able to generate your snapshot, copy it manually over to the subscriber - using the altsnapshotfolder parameter and then apply it there. So now I have my snapshot, a folder with lots of .cft .bcp .dri .prc .sch  and .trg files. Getting this to the subscriber computer shouldn't take long. Once I get it there, how do I use it to get the subscriber set up?  You can't be successful at this unless you're at least 1/2 a bubble off level.

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

Dynamics Ax report mail subscription error

I created a Dynamics Ax report. In this report some axapta static functions are called. When I run the report in browser it shows data normal. I created for this report email subscription(Setted the execution account).In the email is attached the report in pdf format, but for textboxes where it has to show data with results from axapta functions it shows "#Error". Running the report from link attached in mail shows data normal(Without"#Error"). What can be the solution for this problem?   The error from Event viewer: "The complete data cache has been flushed to request from session 13".      

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.

Why is that I am not able to create login? Error:Server Prindipal 'ms\**** already exists

Hi,   When I try to cretae a login, it gives the following error: Server Prindipal 'ms\**** already exists. The login is not there in sys.server_principals table also.  

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?

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?
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