View Complete Post
We have one customer that has two subscribers with the one distributor. there are three publications being merged. two of them are fine, but one publication is receiving an error:
The merge process was unable to access row metadata at the 'Subscriber'.
it seems to be from one table because the next error is for that table and to check the permissions. i know they are correct because i can access the table fine from SSMS.
Does anyone have any suggestions to start debugging this?
We're using sql 2005 ent merge replication (SP2) and replicate 65GB binary data. However, after merge job running around 60 hours and nearly finished, it has the error messages like this :
From distribution.msrepl_errors and distribution.msmerge_history:
"The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to write to the message file. When troubleshooting, restart the synchronization with verbose history logging and
specify an outfile to write" (Error Number: MSSQL_REPL-2147201001)
"The process could not read file "E:\Program files\Microsoft SQL Server\MSSQL.1\MSSQL\ReplData\unc\IMDNACMPS33_MPSERVER_MPSERVER\20110411220596\NoticeInfo_2.cft" due to OS Error 2(Error Number: MSSQL_REPL20216)
Please note that the above messages kept continuously appear in both event viewer and system tables between 1 minutes. Any suggestions or help to fix this?? Do I need to click 'stop synchronizing' and click 'start synchronizing' to restart the merge job
again or click 'reinit subscription'? An urgent response is indeed necessary for this case. Thanks a lot.
Thanks and regards,
P.S: for your reference please find the attached error photo
Steps by Step document for configuration Merge Replication in 2005 Hi ,
Can anyone provide link to configure Merge Replication in 2005 with print screen.Also let me know the difference between Transcation level and Merge Replication.
I am using SQL Server 2005 enterprise edition, I Confirured the Merge Replication to my database). I have a replication of 21 database from various locations.
Problem is: When is trying to remove one subriction from the publisher and add a fresh subriciton to it. it is poping any error saying the Identity Range value exceed its Max Limit try to change from int to bigint. is there any solution for it not changing
from int to bigint.
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)
View(references Db_A & Db_B)--------Need to be replicated------>Server B
I configured merge replication using SQL Server 2005 SP3 running on Windows Server 2008 R2 x64 with IIS 7.
My client is a .NET Compact 3.5 (RTM) application running on an embedded controller (Beckhoff CX1000) with Windows CE 6.0 installed. I am using SQL Compact 3.5 SP1 on the client. The preconfigured Win CE only had .NET Compact 2.0 installed, so I installed
version 3.5 on the CompactFlash card attached to the controller.
Syncing over HTTP works perfecly using anonymous authentication.
I then executed the Web Sync Config Wizard and configured Basic Authentication without SSL. For authentication I use a local account even though my server is a member of our domain. The same account is used for access to the publication and distribution
DBs (all located on the same server running IIS).
When I ran my client trying to sync, all I get is the 28011 error (Authentication failed).
The strange thing is that a test application on my desktop machine using .NET 3.5 (not Compact) can sync without problems. I even wrote a little test application for the embedded controller using the .NET HttpWebRequest object to connect to the server and
I get the expected "Microsoft SQL Server Compact Server Agent" message.
I dug a little deeper into the issue and analyzed the HTTP packet getting sent to the server (using Wireshark). App
We have a republishing merge replication setup of SQL Server 2005 Head Office (HO) publishing to SQL Server 2005 Regional Offices (RO) re-publishing to SQL Server 2005 Express Stores (ST). The problem we are having is that of strange conflicts. They can
be grouped into the following types:
1) Update conflicts where the data is the same on both sides and one side hasn't made a change since the last replication event.
2) Delete/Update conflict where the delete is real but the update isn't. Like #1 the update never occured.
3) Delete/Delete confluct where one of the deletes are real but the other isn't which then create a Unique identifer error in the conflict resolver.
We have looked over the SQL Server CU's both nothing describes our problem as we are running SP3. We've also search for other reported problems and can confirm that we don't have filters on DateTime fields only GUID fields and the join filter table hierarchy
isn't deep. We've also tried a re-initialisation and verified that the collation is the same over every SQL instance.
Has anyone also come across and found a solution for this?
Ihave merge replication set up between two sites. Everything worked fine up until the subscriber wanted to update the publisher. I get the following error:
The merge process is retrying a failed operation made to article 'X' - Reason: 'The Merge Agent was unable to synchronize the row due to one or more unanticipated errors in the batch of changes. When troubleshooting, increase the -OutputVerboseLevel setting,
restart the agent, and check for and resolve any errors generated by the database engine. '.
I am using SQL Server 2005 Developer Edition for Creating & Testing Database.
I had created Merge Publication WITHOUT FILTERING ROWS and Created Push or Pull Subscription. Now if I Add or Drop column using ALTER TABLE (T-SQL) in Table OR modify stored procedure using ALTER PROCEDURE in
Published Database then while Synchronizing It replicate same in Subscriber Database and works very fine.
But when I had created Merge Publication WITH FILTERING ROWS (Parameterize or Static) and Created Push / Pull Subscription and I try to Add or Drop column
using ALTER TABLE (T-SQL) in Table OR modify stored procedure using ALTER PROCEDURE in Published Database then while Synchronizing It
DOESN'T REPLICATE in Table of Subscriber Database but
tries Replicate in Stored Procedure and display error.
After Adding Column in Table of Published Database, If I Checked Article in property of Publication then it Adds column but it doesn't
selects it. I also checked using sp_enumeratependingschemechenges it displays pending schema changes of stored procedure but
We are planning to implement Merge Replication between SQL Server 2008 "Not R2 Version" (Publisher) and SQL Server 2005 (Subscriber). Will this setup work, or there are some limitations ?
I have a merge publication configured that has been running fine with no issues for many weeks. Here is my setup... Publisher - SQL 2008 SP1, Distributor - SQL 2008 R2, Subscriber - SQL 2008 SP1.
On Wednesday and Thursday of last week, I created a few hundred foreign keys referencing a table (user information for auditing). Then, on Friday evening, I started to receive this message:
Msg 8621, Level 17, State 1, Procedure MSmerge_sel_sp_18DB84E1A521483601D2A6D477F6483D, Line 85
The query processor ran out of stack space during query optimization. Please simplify the query.
I have traced it down, this command gets executed:
exec MSmerge_sel_sp_18DB84E1A521483601D2A6D477F6483D @maxschemaguidforarticle = 'F990B1EE-D52F-4DCA-8EEF-C1783DA47A0F', @type = 6
Which executes this:
I have a web app that runs on local and use merge replcation using sql server 2005 standard on the server and sql express 2005 on clients on XP. As you know, XP Pro laptops are getting hard to find. We are trying to change to Windows 7 Pro x64. I installed SQL Express 2005 and I don't see a subscription on "Sync Center" after I created local subscription using SSMS. I normally see the subscription in Synchronize in XP Pro right away.
I googled about this issue and not really have a good solution. There is one link saying Windows 7 not supporting Express 2005 anymore. http://blogs.msdn.com/b/repltalk/archive/2010/03/24/using-windows-synchronization-manager-on-x64-to-synchronize-replication-revised.aspx
If so, I would like to know what would be a solution such as can I use Sql Express 2008 R2 instead of Sql Express 2005 for client even if the server is still SQL Server 2005 Standard edition. We are planning to upgrade, but we need to hire 5 to 10 people now. My boss does not want us to keep using XP Pro.
Any suggestion would be appreciated.