SQL PULL Merge Replication over web - totally unreliable?

Hi,
We have problems performing SQL PULL merge replication over the web.  Most of the time it works fine, but periodically we experience issues as described below.  Our application uses SQL Express for subscribers and we have our own C# RMO code for
the agent.  We have eliminated our application as the source of the problem by setting up a full SQL Server as a subscriber and using the built in agent.  It experiences the same problems.
1. Unable to download a snapshot.
After reinitializing a subscriber, the snapshot will partially download and will then suddenly stop with the error:
    The connection with the server was terminated abnormally
There is no obvious timeout issue, the error typically occurs as soon as one of the .bcp files is about to be downloaded.  It's often the same .bcp file that has the problem, but not always so there is no consistency.
The only solution is to continually retry until the download eventually succeeds.  Recreating the snapshot before retrying seems to improve the chances of a successful sync.
2. Unable to perform a normal sync (i.e. an update, rather than a full snapshot)
An attempt to perform a sync results in the following information being logged:
    The upload message to be sent to Publisher 'SERVER2' is being generated
    The merge process is using Exchange ID 'F82F1A56-A81A-4786-A469-7A76259F9ED8' for this web synchronization session.
    No data needed to be merged.
    Request message generated, now making it ready for upload.
    Upload request size is 1895 bytes.
At this point the sync simply stops doing anything.  There are no errors, the agent still appears to be running, but nothing else happens.
We typically experience this problem once every few weeks.  Reinitializing a subscriber does not help, the same problem occurs.  The only solution is to recreate the snapshot and then to reinitialize the subscriber.  This then requires the
subscriber to perform a full sync which takes around 45 minutes for our dataset.
I am aware through online searches that others have experienced similar issues with SQL replication over web.  Are there any practical solutions to these issues, or is SQL replication over web simply broken?

Hi Brandon, I noticed a post from you back towards the end of last year where you said you were giving up on it.  Did you ever get it resolved?  If not, did you identify a viable alternative solution?
We need to replicate a SQL database to mobile tablets over 3G.  We've invested a lot of time and effort trying to make this solution work and to find that even using straight SQL server to SQL server has the same issues is disconcerting.
One possible option is that although we currently use merge replication, that was really just a bad design decision taken early on.  We only perform one way replication, all our articles are flagged as one way only, server down to clients.  I have
considered maybe moving towards transactional replication but unless I'm 100% certain I won't hit the same kind of issues, it really isn't viable to invest the time and effort.

Similar Messages

  • Identity Management in a Pull Merge Replication at Subscriber

    I am facing SQL Server Replication issue (Identity Management in a Pull Merge Replication at Subscriber).
    Replication situation:
    Distributor and the Publisher are in one server running Windows Server 2012 Std and SQL Server 2012 Std
    One Subscriber PC running Windows 7 Professional and SQL Server 2012 Express Edition
    Both are connected through the internet using VPN
    The Problem:
    Subscriber has an article (Table) [DocumentItems] where its Identity field [DocumentItemsID] is managed by Replication and was assigned the following range:
    ([DocumentItemsID]>(280649) AND [DocumentItemsID]<=(290649) OR [DocumentItemsID]>(290649) AND DocumentItemsID]<=(300649)
    The server was disconnected from electricity several times. Every time the Subscriber PC is up, The [DocumentItemsID] field will pick an identity out of its range like 330035 when inserting new rows.
    The issue happened 3 times. I fixed the problem by a manual reseed:
        DBCC CHECKIDENT('DocumentItems' , RESEED, xxxx)
    Where xxxx is the MAX existing value for [DocumentItemsID] + 1
    Once the electricity is disconnected again, the same problem occurs.
    Does anybody have any idea what is happening? And why the [DocumentItemsID] field was assigned values out of its range?
    Thanks

    I am confused as to where/when this problem is happening.
    From what you describe the publisher is disconnected from the subscriber by the power failure. During this time is your subscriber accepting data?
    The subscriber will not increment it's range until it does a synchronization. Perhaps what is happening is that you have a power failure, and the subscriber is still running. It accepts inserts and eventually an insert is more than the assigned range. In
    this case all inserts will fail until the subscriber syncs and after that the range in incremented. If these inserts are done in a batch, lets say 100,000 rows then entire batch will fail as it exceeds the possible identity values and then you will find that
    your identity range is incremented even though the inserts failed.
    What I would do is use manual identity range management and set your subscriber range manually to somehting high, or to have a -ve increment and a seed of 0.
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • Slow merge replication over a WAN link - only downloads

    Hi all,
    We've been using SQL Server merge replication for a few years to synchronise data between our data centres, but we are now suffering with a big performance issue. This may be because the amount of data we are synchronising has increased a lot this year.
    Our publisher is an always-on data centre in the UK. Our subscriber is a mobile data centre that travels around the world and is on for periods of up to a week at a time, approx. 25 times a year. However, it also spends the same amount of time (if not more)
    switched off whilst on its travels - it is a well travelled data centre!
    We have 5 database that we synchronise on these servers. However, one of our databases has high numbers of data changes between periods of subscriber downtime and our issue is that it take days to catch up when the server is powered up - the other databases
    are fine.
    Downloads from publisher to subscriber run at about 1.5 rows a second (which is annoying when we have hundreds of thousands of rows) but strangely uploads from subscriber to publisher run about ten times faster.
    Things I have checked / tried:
    all tables have non-clustered primary keys on guid columns that have the rowguid property set
    changing the generation levelling threshold doesn't help
    setting the agent profile to high volume doesn't help
    running a trace at the publisher and subscriber shows the queries are all running very fast (less than 20 m/s generally, but there are gaps of 200 m/s or so between some batches of queries)
    analysis on our WAN link shows we have huge amounts of bandwidth spare
    analysis on our servers show we have huge amounts of Ram and CPU spare
    Some of the places the subscriber is at do suffer from high latency but this doesn't seem to have an impact - 300 m/s or 100m/s and we still get the same poor performance.
    One things I did wonder about - does the replication confirm to the publisher every time it has successfully processed a row at the subscriber? If we have thousands of rows and there is a latency on the line will this compound the issue if it confirms each
    item? If this does happen, is there a way to batch up messages between publisher and subscriber?
    Any help that you can offer will be gladly received!
    Thanks
    Mark

    1) merge replication processes the uploads/downloads in batches. So no, there is no confirmation for each row processes, but there is per batch. If there is an error/conflict a batch is retried as singletons (a single row processed at a time), so you need
    to minimize conflicts/errors.
    2) No, but you should use pull and wan accelerators for max performance and change your profile to use 2000 for the following:
    MaxDownloadChanges 
    MaxUploadChanges
    UploadGenerationsPerBatch  
    DownloadGenerationsPerBatch 
    UploadReadChangesPerBatch 
    DownloadReadChangesPerBatch 
    UploadWriteChangesPerBatch 
    DownloadWriteChangesPerBatch 
    set network packet size to a large value - you will need to work with your wan engineer to find out what works best. 32k will likely be best.
    Also you may want to copy a file of a known size from your publisher to your subscriber and then from your subscriber to your publisher to see if there is a significant difference in time. For drives will yield significant differences.
    I have found that you may have a trigger which is generating a large volume of unnessary changes. You will need to see what table/article is generating all the changes and evaluate whether the changes are legit.
    Precomputed partitions should speed up the enumeration times. Ensure you have supporting indexes - the missing indexes DMV helps here.
    Lastly you may find that a reinitialization is faster than processing the changes.
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • SQL Server 2012 Web synchronization option for SQL Server Merge Replication

    I have 2 servers for this:
    1. WIndows Server 2008 with SQL SERVER 2012
    2. Windows Web SErver 2008 With IIS 7 - and SQL Client Conectivity Tools installed
    https://192.168.100.8/sqlreplication/replisapi.dll?diag  i have the next results:
    Class Initialization test:
    Class Status
    ErrorCode
    replisapi.dll classes SUCCESS 0x0
    CLSID_SQLReplErrors FAILED 0x80040154
    replrec.dll classes FAILED 0x80040154
    msxml6.dll classes SUCCESS 0x0
    Where replrec.dll is supposed to be? On the WebServer or Database Server? And if the answer is on the Webserver, how can i install it?
    Thank you,
    biionut

    Hi biionut,
    Did you install SQL Server 2012 Replication Components on the IIS server?  The steps to install replication components are covered in
    How to: Install SQL Server Replication Components.
    Also, is your IIS server running 64-bit Windows?  If so you will need to allow 32-bit applications to run on the IIS server:
    cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
    Brandon Williams (blog |
    linkedin)

  • Update query is slow with merge replication

    Hello friend,
    I have a database with enabling merge replication.
    Then the problem is update query is taking more time.
    But when I disable the merge triggers then it'll update quickly.
    I really appreciate your
    quick response.
    Thanks.

    Hi Manjula,
    According to your description, the update query is slow after configuring merge replication. There are some proposals for you troubleshooting this issue as follows.
    1. Perform regular index maintenance, update statistics, re-index, on the following Replication system tables.
        •MSmerge_contents
        •MSmerge_genhistory
        •MSmerge_tombstone
        •MSmerge_current_partition_mappings
        •MSmerge_past_partition_mappings
    2. Make sure that your tables involved in the query have suitable indexes. Also do the re-indexing and update the statistics for these tables. Additionally, you can use
    Database Engine Tuning Advisor to tune databases for better query performance.
    Here are some related articles for your reference.
    http://blogs.msdn.com/b/chrissk/archive/2010/02/01/sql-server-merge-replication-best-practices.aspx
    http://technet.microsoft.com/en-us/library/ms177500(v=sql.105).aspx
    Thanks,
    Lydia Zhang

  • SQL Server Compact 3.5 Merge Replication With SQL Server 2012 - Causing IIS App Pool to Crash

    Hi, I may be the only person in the world doing this but I wanted to give this information to anyone else who may follow this path in the future, and hopefully avoid a headache, or at least a paid support call to Microsoft.
    My original scenario was we had a SQL Server 2008 Server using Merge Replication through and IIS (web server) to several Windows Mobile 6 devices.  This has worked fairly well for a few years.
    Recently we upgraded our SQL server to version 2012 SP 1.  After moving the database over to the new server, and re-setting the merge replication stuff, we couldn't get merge replication to work on the Windows Mobile 6 handheld devices.  The replication
    would appear to start, and then we would get a message saying that the device could not get to the web site.  The message on the handheld device was this:
    "The IIS service is not available."
    After doing some more research, we found that the start of the replication process was causing the Thread Pool that was running the SQLCESA35.dll to crash.  
    The SQLCESALOG.txt file had this information:
    Date Time == SQLCESA Version ==> 3.5.8088.0
    Date Time Hr=80004005 ERR:Couldn't find existing RSCB 1
    After 2 days of trying to figure out the issue on our own, we gave in and called for paid Microsoft support.  They eventually found a known issue where a cumulative update was able to fix the problem.
    We installed the update on the IIS server and everything ran smoothly again.
    FIX: Merge replication fails when you use SQL Server Compact to perform a merge replication that synchronizes changes with a publisher in SQL Server 2012
    http://support.microsoft.com/kb/2845550
    Seth O'Neal

    Hi sonealtx,
    Glad to hear that the issue is resolved. Thanks for your sharing, other community members could benefit from your solution.
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • SQL Server upgrade with merge replication

    We are planning to upgrade SQL Server 2005 to SQL Server 2012 and both the databases will be hosted on two different servers. SQL Server 2005 has around 25 merge publication and have around 400 laptops that subscribe to these publications. The new SQL server
    2012 will also have same replication setup as the old server. The data base size on the existing server is 66 GB and takes about 1.5 hrs for initial sync up.
    Due to various business constraints we can't move over to new server in a single switch. Instead we need to keep both the servers running for a month or two. During this process, we need to replicate (uni-directional) data from SQL server 2005 to SQL server
    2012 on a daily basis. To achieve this we have tried the following approaches so far:
    DB backup and restore from SQL 2005 to SQL 2012 server - In this approach, the publications are dropped by SQL 2012 after we restore.
    SQL native replication - Could not setup Transactional, Merge and Snapshot replication due SQL server constraints. Cannot setup merge replication between SQL 2005(publisher) and SQL 2012(subscriber)
    Microsoft Sync framework – Sync fwk expects identify column or primary key for the sync to work but database has 76 tables without any primary key
    SSIS – DB consists of 170 tables and will require significant effort to write and maintain the package to sync update and delete operations on the DB. Insert operations on the other hand are easy to support.
    We are looking for different options to setup server to server replication with given constraints. 

    You will need to use some form of change tracking to gather the changes up and replay them on the SQL 2012 server.
    You can hack into the msmerge_Contents and msmerge_tombstone to do this. It will be fairly laborious to set up, but it is doable. You can do this as a batch operation so you can run it nightly to do your syncs.
    A lower tech way of doing it would be to run tablediff between the two servers and then replay the script nightly.
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • Merge Replication from 2012 SQL Server publisher/distributor to 2014 SQL Express subscriber

    Hi, I'm having a question about which version to use when running SQL Merge Replication.
    In my test enviroment I have a SQL 2012 server running as Publisher and Distributor for my Merge Replication. I have now set up a test client running Win7 with SQL 2014 Express as a subscriber. The subscription initializes and runs perfectly.
    But according to the SQL documentation this should not be possible as it states that the subscriber should have a version number equal or lower than the publisher. My subscription client was set ut using SQL-scripting, if I try using the wizard it will just
    cause an error message telling that this is not possible since the client has a newer version number. I still not encountered any problems after I set it up using the script with the sp_addmergepullsubscription and sp_addmergepullsubscription_agent procedures.
    The roll-out of my solution will start in a few weeks and I now have to decide whether to use 2014 Express or 2012 Express on the clients. Using 2014 Express will save me for a lot of upgades in a year or two. The 2012 SQL Server running as publisher/distributor
    will be upgraded to/replaced with a 2014 Server in some few months.
    I'm looking for good advices and recommendations for what to choose on the clients, 2012 Express or 2014 Express. Are the any known problems with using 2014 Express as a subscriber to a publisher/distributor running 2012 SQL Server?
    All responses are welcome!
    Regards, Anders

    Hi,
    As you understand that a Subscriber to a merge publication can be any version less than or equal to the Publisher version. When you set up a subscription from a publisher to a subscriber using SQL Server Management Studio, you will get error
    “The selected Subscriber does not satisfy the minimum version compatibility level of the selected publication.” And you can use T-SQL script to get around this error message.
    I would install SQL Server 2012 Express on the clients. Here is the reasons:
    1. If you upgrade the publisher to SQL Server 2014, it is still working with SQL Server 2012 on the subscriber.
    2. I cannot tell whether there are other potential problems if I choose the later one besides the error message.
    Reference:
    http://msdn.microsoft.com/en-us/library/ms143699(v=sql.120).aspx
    Thanks.
    Tracy Cai
    TechNet Community Support

  • Merge Replication Error When Initialising subscription

    I have a SQL server 2005 server with a merge publication of 6 articles all of which are tables which is also the distributor. I have two existing subscriptions one from a SQL 2005
    Server and one from a SQL Server 2008 R2 Server both of which are working fine on this publication. I am trying to setup a third subscription to another SQL Server 2008 R2 server, the only difference with this server is that it is a named instance. I have
    forced the port to 1433, and created an alias on the publisher connectivity is not an issue or at least i don't think so.
    when I try to initialise the subscription from a new snapshot I get the below error;
    Error: 14151, Severity: 18, State: 1.
    Replication-Replication Merge Subsystem: agent failed. No subscription is on this publication or article.
    I've changed the agent profile and turned on verbose logging and output the results to a file the snapshot delivery is failing on the below for the first table;
    call sys.sp_MSsetup_identity_range (?,?,?,?,?,?,?,?)
    I've checked the subscriber and the table does indeed get dropped and created, permissions / routes don't seem to be an issue. I've included some of the verbose logging output below.
    2012-01-11 12:05:40.684 Microsoft SQL Server Merge Agent 9.00.3042.00
    2012-01-11 12:05:40.700 Copyright (c) 2005 Microsoft Corporation
    2012-01-11 12:05:40.716 Microsoft SQL Server Replication Agent: replmerg
    2012-01-11 12:05:40.716 
    2012-01-11 12:05:40.731 The timestamps prepended to the output lines are expressed in terms of UTC time.
    2012-01-11 12:05:40.747 User-specified agent parameter values:
    -Publisher PubServerName
    -PublisherDB UserDBName
    -Publication MtoC_M
    -Subscriber SubServerName
    -SubscriberDB UserDBName
    -Distributor PubServerName
    -DistributorSecurityMode 1
    -Continuous
    -OutputVerboseLevel 4
    -Output G:\CMcReplicationLogging\OUTPUT.TXT
    -XJOBID 0x5FFBC73C3A4A494A9E10C369696B1C72
    -XJOBNAME PubServerName-UserDBName-MtoC_M-SubServerName-29
    -XSTEPID 2
    -XSUBSYSTEM Merge
    -XSERVER PubServerName
    -XCMDLINE 0
    -XCancelEventHandle 000008EC
    -XParentProcessHandle 00000E9C
    2012-01-11 12:05:40.841 Percent Complete: 0
    2012-01-11 12:05:40.841 Connecting to Distributor 'PubServerName'
    2012-01-11 12:05:40.856 Repl Agent Status: 3
    2012-01-11 12:05:40.856 Connecting to OLE DB Distributor at datasource: 'PubServerName', location: '', catalog: '', providerstring: '' using provider 'SQLNCLI'
    2012-01-11 12:05:42.137 OLE DB Distributor: PubServerName
    DBMS: Microsoft SQL Server
    Version: 09.00.3042
    catalog name: 
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2012-01-11 12:05:42.137 OLE DB Distributor 'PubServerName': {call sp_MSgetversion }
    2012-01-11 12:05:42.153 OLE DB Distributor 'PubServerName': {call sp_helpdistpublisher (N'PubServerName') }
    2012-01-11 12:05:42.169 OLE DB Distributor 'PubServerName': {call sp_MShelp_repl_agent (N'PubServerName', N'UserDBName', N'MtoC_M', N'SubServerName', N'UserDBName', 1)}
    2012-01-11 12:05:42.169 OLE DB Distributor 'PubServerName': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'PubServerName')
    2012-01-11 12:05:42.184 OLE DB Distributor 'PubServerName': {call sp_MShelp_merge_agentid (0,N'UserDBName',N'MtoC_M',null,N'UserDBName',90,N'SubServerName')}
    2012-01-11 12:05:42.184 OLE DB Distributor 'PubServerName': {call sp_MShelp_profile (29, 4, N'')}
    2012-01-11 12:05:42.184 Percent Complete: 0
    2012-01-11 12:05:42.184 Connecting to OLE DB Publisher at datasource: 'PubServerName', location: '', catalog: 'UserDBName', providerstring: '' using provider 'SQLNCLI'
    2012-01-11 12:05:42.200 Initializing
    2012-01-11 12:05:42.200 Repl Agent Status: 1
    2012-01-11 12:05:42.216 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:42.216 Percent Complete: 0
    2012-01-11 12:05:42.231 Connecting to Publisher 'PubServerName'
    2012-01-11 12:05:42.231 Repl Agent Status: 3
    2012-01-11 12:05:42.231 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:43.153 OLE DB Publisher: PubServerName
    DBMS: Microsoft SQL Server
    Version: 09.00.3042
    catalog name: UserDBName
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2012-01-11 12:05:43.169 OLE DB Publisher 'PubServerName': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation,
    N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end
    as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
    2012-01-11 12:05:43.169 OLE DB Publisher 'PubServerName': {call sp_MSgetversion }
    2012-01-11 12:05:43.200 Connecting to OLE DB Publisher at datasource: 'PubServerName', location: '', catalog: 'UserDBName', providerstring: '' using provider 'SQLNCLI'
    2012-01-11 12:05:44.137 OLE DB Publisher: PubServerName
    DBMS: Microsoft SQL Server
    Version: 09.00.3042
    catalog name: UserDBName
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2012-01-11 12:05:44.137 OLE DB Publisher 'PubServerName': {call sp_MSchecksnapshotstatus (N'MtoC_M')}
    2012-01-11 12:05:44.153 OLE DB Publisher 'PubServerName': {call sp_helpmergepublication (N'MtoC_M')}
    2012-01-11 12:05:44.153 OLE DB Publisher 'PubServerName': {call sys.sp_MSgetreplicainfo(?,?,?,?,?,?,?,90)}
    2012-01-11 12:05:44.169 OLE DB Distributor 'PubServerName': {call sp_MShelp_repl_agent (N'PubServerName', N'UserDBName', N'MtoC_M', N'SubServerName', N'UserDBName', 1)}
    2012-01-11 12:05:44.169 Connecting to OLE DB Subscriber at datasource: 'SubServerName', location: '', catalog: 'UserDBName', providerstring: '' using provider 'SQLNCLI'
    2012-01-11 12:05:44.747 OLE DB Subscriber: SubServerName
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: UserDBName
    user name: distributor_MtoC
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2012-01-11 12:05:45.122 OLE DB Subscriber 'SubServerName': {call sp_MSgetversion }
    2012-01-11 12:05:45.216 OLE DB Subscriber 'SubServerName': {call sp_MSreplcheck_subscribe}
    2012-01-11 12:05:45.309 OLE DB Subscriber 'SubServerName': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation,
    N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end
    as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
    2012-01-11 12:05:45.419 Percent Complete: 0
    2012-01-11 12:05:45.419 OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.419 Connecting to Subscriber 'SubServerName'
    2012-01-11 12:05:45.434 Repl Agent Status: 3
    2012-01-11 12:05:45.434 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.559 Percent Complete: 0
    2012-01-11 12:05:45.559 OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.559 Retrieving publication information
    2012-01-11 12:05:45.575 Repl Agent Status: 3
    2012-01-11 12:05:45.575 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.653 OLE DB Subscriber 'SubServerName': {call sys.sp_MSmerge_upgrade_subscriber(1,?)}
    2012-01-11 12:05:45.653 Percent Complete: 0
    2012-01-11 12:05:45.669 Retrieving subscription information.
    2012-01-11 12:05:45.669 Repl Agent Status: 3
    2012-01-11 12:05:45.684 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.763 OLE DB Publisher 'PubServerName': {call sys.sp_MSgetreplicainfo(?,?,?,?,?,?,?,90)}
    2012-01-11 12:05:45.763 OLE DB Publisher 'PubServerName': {call sys.sp_MShelpmergearticles (?,9000000,?) }
    2012-01-11 12:05:45.778 OLE DB Publisher 'PubServerName': {call sp_MSenumschemachange (?,?,9000000,?,0,1) }
    2012-01-11 12:05:45.794 OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.888 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.888 Percent Complete: 0
    2012-01-11 12:05:45.903 Applying the snapshot to the Subscriber
    2012-01-11 12:05:45.903 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.903 Repl Agent Status: 3
    2012-01-11 12:05:45.919 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.919 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.919 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.934 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.950 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.950 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.966 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.981 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.997 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.997 OLE DB Subscriber 'SubServerName': {call master..sp_helpreplicationoption ('merge')}
    2012-01-11 12:05:46.091 OLE DB Subscriber 'SubServerName': {call sys.sp_MSmergesubscribedb ('true', 0) }
    2012-01-11 12:05:47.263 OLE DB Subscriber 'SubServerName': {call sp_MSpublicationcleanup (?,?,?)}
    2012-01-11 12:05:47.372 OLE DB Subscriber 'SubServerName': {call sp_MSCleanupForPullReinit (?,?,?)}
    2012-01-11 12:05:47.481 OLE DB Subscriber 'SubServerName': {call sp_MSdropconstraints (N'tblEmailMessages',N'dbo')}
    2012-01-11 12:05:47.606 OLE DB Subscriber 'SubServerName': {call sp_MSdropconstraints (N'tblUser',N'dbo')}
    2012-01-11 12:05:47.716 OLE DB Subscriber 'SubServerName': {call sp_MSdropconstraints (N'tblDPVLocked',N'dbo')}
    2012-01-11 12:05:47.809 OLE DB Subscriber 'SubServerName': {call sp_MSdropconstraints (N'tblCaptureAppToken',N'dbo')}
    2012-01-11 12:05:47.903 OLE DB Subscriber 'SubServerName': {call sp_MSdropconstraints (N'tblCreditThresholdNotification',N'dbo')}
    2012-01-11 12:05:48.013 OLE DB Subscriber 'SubServerName': {call sp_MSdropconstraints (N'tblCreditPot',N'dbo')}
    2012-01-11 12:05:48.106 OLE DB Subscriber 'SubServerName': {call sys.sp_MSaddinitialpublication (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:48.247 OLE DB Subscriber 'SubServerName': {call sp_MSunmarkifneeded (N'tblEmailMessages',?, 1, ?, ?)}
    2012-01-11 12:05:48.403 OLE DB Subscriber 'SubServerName': {call sp_MSunmarkifneeded (N'tblUser',?, 1, ?, ?)}
    2012-01-11 12:05:48.513 OLE DB Subscriber 'SubServerName': {call sp_MSunmarkifneeded (N'tblDPVLocked',?, 1, ?, ?)}
    2012-01-11 12:05:48.606 OLE DB Subscriber 'SubServerName': {call sp_MSunmarkifneeded (N'tblCaptureAppToken',?, 1, ?, ?)}
    2012-01-11 12:05:48.700 OLE DB Subscriber 'SubServerName': {call sp_MSunmarkifneeded (N'tblCreditThresholdNotification',?, 1, ?, ?)}
    2012-01-11 12:05:48.809 OLE DB Subscriber 'SubServerName': {call sp_MSunmarkifneeded (N'tblCreditPot',?, 1, ?, ?)}
    2012-01-11 12:05:48.903 OLE DB Publisher 'PubServerName': {call sp_MShelpmergeschemaarticles(?)}
    2012-01-11 12:05:48.919 OLE DB Subscriber 'SubServerName': {call sp_MSaddinitialsubscription (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}
    2012-01-11 12:05:49.059 OLE DB Distributor 'PubServerName': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'PubServerName')
    2012-01-11 12:05:49.059 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_mergesubentry_indistdb (0,N'PubServerName',N'UserDBName',N'MtoC_M',N'SubServerName',N'UserDBName',0,1,0,N'',?,90)}
    2012-01-11 12:05:49.075 OLE DB Subscriber 'SubServerName': {call sp_MScreateglobalreplica (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,90)}
    2012-01-11 12:05:49.341 Connecting to OLE DB Subscriber at datasource: 'SubServerName', location: '', catalog: 'UserDBName', providerstring: '' using provider 'SQLNCLI'
    2012-01-11 12:05:49.825 OLE DB Subscriber: SubServerName
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: UserDBName
    user name: distributor_MtoC
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2012-01-11 12:05:50.185 OLE DB Subscriber: SubServerName
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: UserDBName
    user name: distributor_MtoC
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2012-01-11 12:05:50.325 OLE DB Subscriber 'SubServerName': {call sys.sp_MSregistermergesnappubid(?, ?)}
    2012-01-11 12:05:50.450 OLE DB Subscriber 'SubServerName': sp_MSacquiresnapshotdeliverysessionlock
    2012-01-11 12:05:50.544 OLE DB Subscriber 'SubServerName': sp_MStrypurgingoldsnapshotdeliveryprogress
    2012-01-11 12:05:50.810 OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:50.966 [2%] OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    ꜻä㹒 ꜐äB 11 12:05ä谼砗꜐ä镴ĀPercent Complete: 4
    2012-01-11 12:05:50.997 Propagated 1 schema changes: 1 total
    2012-01-11 12:05:51.013 Repl Agent Status: 3
    2012-01-11 12:05:51.013 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:51.091 [6%] OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    ꜻä㹒 ꜐äB 11 12:05ä谼砗꜐ä镴ĀPercent Complete: 6
    2012-01-11 12:05:51.122 Propagated 1 schema changes: 2 total
    2012-01-11 12:05:51.153 Repl Agent Status: 3
    2012-01-11 12:05:51.153 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:51.200 OLE DB Subscriber 'SubServerName': {call sp_MSunmarkreplinfo (N'tblEmailMessages')}
    2012-01-11 12:05:51.200 [6%] Percent Complete: 6
    2012-01-11 12:05:51.231 Propagated 1 schema changes: 3 total
    2012-01-11 12:05:51.247 Repl Agent Status: 3
    2012-01-11 12:05:51.263 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:51.325 OLE DB Subscriber 'SubServerName': sp_MSissnapshotitemapplied @snapshot_session_token = N'E:\Microsoft SQL Server\MSSQL.1\MSSQL\repldata\unc\PubServerName_UserDBName_MTOC_M\20120111115787\', @snapshot_progress_token = N'E:\Microsoft
    SQL Server\MSSQL.1\MSSQL\repldata\unc\PubServerName_UserDBName_MTOC_M\20120111115787\tblEmailMessages_2.sch'
    2012-01-11 12:05:51.435 drop Table [dbo].[tblEmailMessages]
    go
    SET ANSI_PADDING ON
    go
    SET ANSI_NULLS ON
    GO
    SET QUOTED_IDENTIFIER ON
    GO
    CREATE TABLE [dbo].[tblEmailMessages](
    [EmailMessageId] [bigint] IDENTITY(1,1) NOT FOR REPLICATION NOT NULL,
    [Guid] [nvarchar](32) NOT NULL,
    [Recipients] [varchar](8000) NOT NULL,
    [CcRecipients] [varchar](8000) NULL,
    [BccRecipients] [varchar](8000) NULL,
    [Sender] [varchar](8000) NOT NULL,
    [Subject] [nvarchar](4000) NOT NULL,
    [BodyText] [nvarchar](max) NULL,
    [BodyHTML] [nvarchar](max) NULL,
    [IsBodyEncrypted] [bit] NOT NULL CONSTRAINT [DF_tblEmailMessages_IsBodyEncrypted] DEFAULT ((0)),
    [Status] [tinyint] NOT NULL CONSTRAINT [DF_tblEmailMessages_Status] DEFAULT ((1)),
    [DateAdded] [datetime] NOT NULL CONSTRAINT [DR_tblEmailMessages_DateAdded] DEFAULT (getdate()),
    [rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT [MSmerge_df_rowguid_207F75F229994684BC3FAAE5BE4CD6EB] DEFAULT (newsequentialid())
    GO
    GRANT DELETE ON [dbo].[tblEmailMessages] TO [odintermediary]
    GO
    GRANT INSERT ON [dbo].[tblEmailMessages] TO [odintermediary]
    GO
    GRANT SELECT ON [dbo].[tblEmailMessages] TO [odintermediary]
    GO
    GRANT UPDATE ON [dbo].[tblEmailMessages] TO [odintermediary]
    GO
    SET ANSI_NULLS ON
    go
    SET QUOTED_IDENTIFIER ON
    go
    ALTER TABLE [dbo].[tblEmailMessages] ADD CONSTRAINT [PK_tblEmailMessage] PRIMARY KEY CLUSTERED 
    [EmailMessageId] ASC
    )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON)
    GO
    2012-01-11 12:05:51.450 OLE DB Subscriber 'SubServerName': drop Table [dbo].[tblEmailMessages]
    2012-01-11 12:05:51.560 OLE DB Subscriber 'SubServerName': SET ANSI_PADDING ON
    2012-01-11 12:05:51.669 OLE DB Subscriber 'SubServerName': SET ANSI_NULLS ON
    2012-01-11 12:05:51.778 OLE DB Subscriber 'SubServerName': SET QUOTED_IDENTIFIER ON
    2012-01-11 12:05:51.872 OLE DB Subscriber 'SubServerName': CREATE TABLE [dbo].[tblEmailMessages](
    [EmailMessageId] [bigint] IDENTITY(1,1) NOT FOR REPLICATION NOT NULL,
    [Guid] [nvarchar](32) NOT NULL,
    [Recipients] [varchar](8000) NOT NULL,
    [CcRecipients] [varchar](8000) NULL,
    [BccRecipients] [varchar](8000) NULL,
    [Sender] [varchar](8000) NOT NULL,
    [Subject] [nvarchar](4000) NOT NULL,
    [BodyText] [nvarchar](max) NULL,
    [BodyHTML] [nvarchar](max) NULL,
    [IsBodyEncrypted] [bit] NOT NULL CONSTRAINT [DF_tblEmailMessages_IsBodyEncrypted] DEFAULT ((0)),
    [Status] [tinyint] NOT NULL CONSTRAINT [DF_tblEmailMessages_Status] DEFAULT ((1)),
    [DateAdded] [datetime] NOT NULL CONSTRAINT [DR_tblEmailMessages_DateAdded] DEFAULT (getdate()),
    [rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT [MSmerge_df_rowguid_207F75F229994684BC3FAAE5BE4CD6EB] DEFAULT (newsequentialid())
    2012-01-11 12:05:51.981 OLE DB Subscriber 'SubServerName': GRANT DELETE ON [dbo].[tblEmailMessages] TO [odintermediary]
    2012-01-11 12:05:52.091 OLE DB Subscriber 'SubServerName': GRANT INSERT ON [dbo].[tblEmailMessages] TO [odintermediary]
    2012-01-11 12:05:52.200 OLE DB Subscriber 'SubServerName': GRANT SELECT ON [dbo].[tblEmailMessages] TO [odintermediary]
    2012-01-11 12:05:52.294 OLE DB Subscriber 'SubServerName': GRANT UPDATE ON [dbo].[tblEmailMessages] TO [odintermediary]
    2012-01-11 12:05:52.403 OLE DB Subscriber 'SubServerName': SET ANSI_NULLS ON
    2012-01-11 12:05:52.497 OLE DB Subscriber 'SubServerName': SET QUOTED_IDENTIFIER ON
    2012-01-11 12:05:52.606 OLE DB Subscriber 'SubServerName': ALTER TABLE [dbo].[tblEmailMessages] ADD CONSTRAINT [PK_tblEmailMessage] PRIMARY KEY CLUSTERED 
    [EmailMessageId] ASC
    )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON)
    2012-01-11 12:05:52.716 OLE DB Subscriber 'SubServerName': sp_MSrecordsnapshotdeliveryprogress @snapshot_session_token = N'E:\Microsoft SQL Server\MSSQL.1\MSSQL\repldata\unc\PubServerName_UserDBName_MTOC_M\20120111115787\', @snapshot_progress_token = N'E:\Microsoft
    SQL Server\MSSQL.1\MSSQL\repldata\unc\PubServerName_UserDBName_MTOC_M\20120111115787\tblEmailMessages_2.sch'
    2012-01-11 12:05:52.841 OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:52.966 [6%] Percent Complete: 6
    2012-01-11 12:05:52.981 Applied script 'tblEmailMessages_2.sch'
    2012-01-11 12:05:52.981 Repl Agent Status: 3
    2012-01-11 12:05:52.981 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:53.153 OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:53.263 [6%] OLE DB Subscriber 'SubServerName': {call sys.sp_MSaddinitialarticle (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    ꜻä㹒 ꜐äB 11 12:05ä谼砗꜐ä镴ĀPercent Complete: 6
    2012-01-11 12:05:53.294 Preparing table 'tblEmailMessages' for merge replication
    2012-01-11 12:05:53.294 Repl Agent Status: 3
    2012-01-11 12:05:53.310 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:53.450 OLE DB Subscriber 'SubServerName': {call sp_MSupdatesysmergearticles (?,?,?,?,0)}
    2012-01-11 12:05:53.575 OLE DB Subscriber 'SubServerName': {call sys.sp_MSsetup_identity_range (?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:53.794 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.
    2012-01-11 12:05:53.825 OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:53.966 Percent Complete: 6
    2012-01-11 12:05:53.966 No subscription is on this publication or article.
    2012-01-11 12:05:53.997 Repl Agent Status: 6
    2012-01-11 12:05:54.013 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:54.216 Percent Complete: 0
    2012-01-11 12:05:54.231 Category:SQLSERVER
    Source: SubServerName
    Number: 14050
    Message: No subscription is on this publication or article.
    2012-01-11 12:05:54.247 Repl Agent Status: 3
    2012-01-11 12:05:54.372 Percent Complete: 0
    2012-01-11 12:05:54.372 Category:NULL
    Source: Merge Replication Provider
    Number: -2147201001
    Message: 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.
    2012-01-11 12:05:54.388 Repl Agent Status: 3
    2012-01-11 12:05:54.388 Disconnecting from OLE DB Subscriber 'SubServerName'
    2012-01-11 12:05:54.388 Disconnecting from OLE DB Subscriber 'SubServerName'
    2012-01-11 12:05:54.403 Disconnecting from OLE DB Subscriber 'SubServerName'
    2012-01-11 12:05:54.403 Disconnecting from OLE DB Subscriber 'SubServerName'
    2012-01-11 12:05:54.403 Disconnecting from OLE DB Publisher 'PubServerName'
    2012-01-11 12:05:54.419 Disconnecting from OLE DB Publisher 'PubServerName'
    2012-01-11 12:05:54.419 Disconnecting from OLE DB Publisher 'PubServerName'
    2012-01-11 12:05:54.419 Disconnecting from OLE DB Publisher 'PubServerName'
    2012-01-11 12:05:54.435 Disconnecting from OLE DB Distributor 'PubServerName'
    2012-01-11 12:05:54.435 Disconnecting from OLE DB Distributor 'PubServerName'
    2012-01-11 12:05:54.450 The merge process will restart after waiting 30 second(s)...
    Percent Complete: 0
    Any help would be much appreciated.
    Thanks
    Chris 

    The error happens on this table every time.
    The schema of the table is below;
    CREATE TABLE [dbo].[tblEmailMessages](
    [EmailMessageId] [bigint] IDENTITY(1,1) NOT FOR REPLICATION NOT NULL,
    [Guid] [nvarchar](32) NOT NULL,
    [Recipients] [varchar](8000) NOT NULL,
    [CcRecipients] [varchar](8000) NULL,
    [BccRecipients] [varchar](8000) NULL,
    [Sender] [varchar](8000) NOT NULL,
    [Subject] [nvarchar](4000) NOT NULL,
    [BodyText] [nvarchar](max) NULL,
    [BodyHTML] [nvarchar](max) NULL,
    [IsBodyEncrypted] [bit] NOT NULL CONSTRAINT [DF_tblEmailMessages_IsBodyEncrypted] DEFAULT ((0)),
    [Status] [tinyint] NOT NULL CONSTRAINT [DF_tblEmailMessages_Status] DEFAULT ((1)),
    [DateAdded] [datetime] NOT NULL CONSTRAINT [DR_tblEmailMessages_DateAdded] DEFAULT (getdate()),
    [rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT [MSmerge_df_rowguid_207F75F229994684BC3FAAE5BE4CD6EB] DEFAULT
    (newsequentialid())
    The table gets dropped and recreated each time i try to reinitialise the subscription.  I can't remove the article at the moment as two other servers subscribe to the publication.
    Thanks for your help
    Chris
    I am the master of my fate: I am the captain of my soul.

  • Merge replication - multi site, multi distributor, publisher, subscribers ...

    Hi,
    We have 2 sites at the moment. Each site has 2 servers. To reduce network load I was aiming at doing the following with a merge replication :
    * configure one server at each site to be distributor and publisher
    * configure the other server at each site to be a subscriber
    * configure the 2 publishers to also be subscribers to each other to sync the sites.
    Or even better:
    * have all the servers be distributors, publishers and subscribers, so that if one dies, who cares as they all have the same configuration.
    Also, I was thinking of:
    * having the distributor and publishers use a DFS share replicated on both sites (or maybe the same share on each sql server ? not sure what the best practice is on this one)
    However, I can't seem to find a good post / thread where it describes this kind of scenario in a step by step way nor what happens to the identity range management.
    If you could share any light on this or point me to the right English terms to describe the above scenario, thanks in advance.
    Olivier
    PS: We only have STD edition, so peer to peer and AG are not available to US. (which is why we are using merge)
    PS2: One way I could see this work is if I manually set the identity columns in the tables so that they won't overlap and make the range management manual. Then just setup publications / distributors and subscribers on each node. (But if I can dodge the
    manual management, it be great)

    Hi Brandon,
    Thx for the reply
    we are using web synchronization.
    According to the documentation ('The business logic handler you specify is executed for every row that is synchronized.') I would think this will do exactly the same as our trigger on the article.
    When we would use a business logic handler to update the record which is just uploaded to the Publisher I think we will end up with the same checksum error.
    We worked around the problem by not changing the status of orders once they are uploaded to the Publisher.
    For that part of the process we now have only 2 statusses anymore :
    - Not to be sent to central server
    - Upload(ed) to central server. 
    So an order is created at the subscriber and has the status 'not to be sent to central server'
    In a synchro-window the user can mark orders which must be uploaded to the central server.
    Only when the users clicks on the synchro button the orders which are marked (on screen) to be synchronised will get the status 'Upload(ed) to central server' and the pull subscriptions is started.
    On the central server we process only the articles with the status 'Upload(ed) to central server'.
    Before we had the statusses :
    - Not to be sent to central server
    - Upload to central server. 
    - Uploaded to central server.
    And we had our own trigger on the Publisher which updated the status of records from 'Upload to central server ' to 'uploaded to central server' which was not reliable because we often had checksum errors on that article.

  • Network Domain Migration - Merge Replication

    My company was recently acquired by a different Parent company. We are currently in the process of migrating from one Domain to the new one using a Microsoft tool called ADMT. I currently have Merge replication with pull subscriptions setup. These have been
    working for several years. The distributor is a SQL 2005 box and is on the old domain. I have several SQL 2005 express subscribers with Laptops and another full SQL 2005 box in another city connected over an MPLS line that is a pull subscriber as well.
    Has anyone migrated a distributor to a different Domain using ADMT before and had any problems? The SQL agent does not run under a domain account, but rather a standard Windows account using pass through authentication. I would hate to lose the Replication
    setup on the Distributor. I could reestablish / reinitialize each subscriber, if I had to.
    Any thoughts?
    Thanks,
    Steve

    Wrong forum. Sorry.

  • Recommended way to start a merge replication with big database

    Hi all
    I need to install a merge replication on 2 diferent stores with Sql 2012 server, that are connected via 2 mb vpn and the database is about 4gb. due to the fact we have 2mb for the initial sync and the database is big, What is the recommended way to do that
    without using the snapshop agent step? Can I take a backup of the db and restore it in the second server and setup the merge replication ? If so, where I tell the wizards that the databases are already there and do not use the snapshop agent and just start
    to replicate ?
    Thanks in advance.
    James

    Create the publication and snapshot. Zip up the snapshot and send it via FedEx to the subscriber. Apply the snapshot on the subscriber by pointing to the unzipped snapshot using the altSnapshotFolder parameter of the merge agent.
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • SQL Server Transacational Replication Issue while adding a new article

    I have a "PULL" transaction replication toplogy (SQL server 2008 R2 - publisher,subscriber & distributor) in place and is working fie. I added a new article (table) using sp_addarticle and it works fine. Then I tried to add subscription
    to the new article using sp_adddsubscrition SPROC from the publisher (details below)
    EXEC sp_addsubscription @publication = @pub_name, @article = @article_name, @subscriber = @sub_server, @destination_db   
    = @sub_dbname, @subscription_type = N'pull',@update_mode = N'read only', @sync_type = 'sutomatic', @status = 'active', 
    @reserved ='Internal'
    I tried with all combination of values in the @sync_type parametr,
    The above command fails with the following message:
    Msg 14100, Level 16, State 1, Procedure sp_MSrepl_addsubscription, Line 533;
    Specify all articles when subscribing to a publication using concurrent snapshot processing.
    The sync_type value parameter is "replication support type" when the subscrition was added orginally to the publication. This trsnslates into a value of 3 (CONCURRENT)  in sync_method
    column on the outpout of sp_helppublication SP execution.
    What am I doing wrong? Please advise. Your help is much appreciated.
    Thanks in advance
    Kirti

    Thanks for your reposne, Mr. Cottr.
    It was a type-oin the value for @sync_type parameter in the sp_addsubscription call when I posted this article originally. It was actually set to "automatic".  I have posted the scripts per your request. These scripts are executed in SQLCMD mode in
    SSMS query qindow. Since this is a PULL subscription, thre is another script for pP-addpullsubscription that is not incldued in this post. If you need that also, I will be glald to post that also. Thanks again for your help.
    -->>>>>sp_addpublication:
    USE [master]
    GO
                           SQL Server Transactional Replication Related Scripts
    Function: Configuring publication on the database at the publisher
    -- TO DO: Parameters to set before executing this TSQL batch script
    :SETVAR pub_dbname                TestDB
    :SETvar pub_name                  TestDB-TranPub01
    :SETVAR distributor               DISTRIBSVR
    :SETVAR repl_admin_account        <domain>\<account_name>
                                       --replication admin account for non-prod environment
    :SETVAR repl_admin_password       <pwd>
                                       --password for replication admin account
    USE [$(pub_dbname)]
    SET NOCOUNT ON
    IF db_name() IN ('master', 'model', 'msdb', 'tempdb', 'distribution', 'DBA')
    BEGIN
       RAISERROR('Please set the user database name properly and rerun the script', 15, 100)
       RETURN
    END
    DECLARE @dynsql                        sysname
           ,@repl_ddl                      int
           ,@allow_initialize_from_backup  varchar(5)
    SET @repl_ddl                     = 1       -- preferred value is 0 (replication of DDL statements prohibited; manually enabled
    when needed only)
    SET @allow_initialize_from_backup = 'true'  -- preferred /do not change this value
    -- Adding the transactional publication
    DECLARE @desc     varchar(255)
    SET @desc = 'Transactional replication of database ' + QUOTENAME('$(pub_dbname)') +
                ' from publisher ' + QUOTENAME(@@servername) + '; Publication: ' + QUOTENAME('$(pub_name)')
    PRINT '1. Configureing publication ' + QUOTENAME('$(pub_name)') + ' on database ' + QUOTENAME('$(pub_dbname)') + ' ...'
    EXEC sp_addpublication
         @publication                  = '$(pub_name)',
         @description                  = @desc,
         @retention                    = 0,
         @add_to_active_directory      = N'false',
         @allow_push                   = N'false',      -- push subscription disabled
         @allow_pull                   = N'true',       -- pull subscription enabled
         @allow_anonymous              = N'false',   
         @allow_sync_tran              = N'false',
         @allow_queued_tran            = N'false',
         @allow_dts                    = N'false',
         @allow_initialize_from_backup = @allow_initialize_from_backup,
         @allow_subscription_copy      = N'false',
         @compress_snapshot            = N'false',
         @enabled_for_internet         = N'false',    
         @enabled_for_p2p              = N'false',
         @independent_agent            = N'true',
         @immediate_sync               = N'false',     
         @repl_freq                    = N'continuous',
         @replicate_ddl                = @repl_ddl,
         @snapshot_in_defaultfolder    = N'true',
         @status                       = N'inactive',   -- initialy publication is inactive / activated later after articles
    are added to the pblication
         @sync_method                  = N'concurrent'  -- preferred
    IF @@ERROR <> 0 RETURN
    PRINT '2. Configureing publication ' + QUOTENAME('$(pub_name)') + ' on database ' + QUOTENAME('$(pub_dbname)') + ' ...'
    EXEC sp_addpublication_snapshot
          @publication                 = '$(pub_name)',
          @frequency_type              = 1,
          @frequency_interval          = 1,
          @frequency_relative_interval = 1,
          @frequency_recurrence_factor = 0,
          @frequency_subday            = 8,
          @frequency_subday_interval   = 1,
          @active_start_time_of_day    = 0,
          @active_end_time_of_day      = 235959,
          @active_start_date           = 0,
          @active_end_date             = 0,
          @job_login                   = '$(repl_admin_account)',
          @job_password                = '$(repl_admin_password)',
          @publisher_security_mode     = 1,             --Windows authentiction
          @publisher_login             = '$(repl_admin_account)',
          @publisher_password          = '$(repl_admin_password)'
    IF @@ERROR <> 0 RETURN
    PRINT 'Executing sp_helppublication for ' + QUOTENAME('$(pub_dbname)') + '.' + QUOTENAME('$(pub_name)') + ' ...'
    EXEC sp_helppublication @publication = '$(pub_name)'
    PRINT 'Executing sp_helppublication_snapshot for ' + QUOTENAME('$(pub_dbname)') + '.' + QUOTENAME('$(pub_name)') + ' ...'
    EXEC sp_helppublication_snapshot @publication = '$(pub_name)'
    --->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    -->>>>sp_addsubscription
    USE [master]
    GO
                           SQL Server Transactional Replication Related Scripts
    Function: Register the (pull) subscription at the subscriber
    -- TO DO: Parameters to set before executing this TSQL batch script
    :SETVAR publisher_dbname          TestDB
    :SETvar publication_name          TestDB-TranPub01
    :SETVAR subs_server               SUBSVR
    :SETVAR subs_dbname               TestDB
    :SETVAR distributor               DISTRIBSVR
    :SETVAR repl_admin_account        <domain>\<account_name
                                      --replication admin account for non-prod environment
    :SETVAR repl_admin_password      <pwd>
                                      --password for replication admin account
    USE [$(publisher_dbname)]
    SET NOCOUNT ON
    IF db_name() IN ('master', 'model', 'msdb', 'tempdb', 'distribution', 'DBA')
    BEGIN
       RAISERROR('Please set the user database name properly and rerun the script', 15, 100)
       RETURN
    END
    DECLARE @dynsql                        sysname
           ,@distibutor                    sysname
           ,@subscriber                    sysname
           ,@pub_dbname                    sysname
           ,@pub_name                      sysname
           ,@pub_login                     sysname
           ,@pub_password                  sysname
           ,@dest_dbname                   sysname
           ,@job_login                     sysname
           ,@job_password                  sysname
           ,@repl_ddl                      int
           ,@allow_initialize_from_backup  varchar(5)
    SET @pub_dbname                   = '$(publisher_dbname)'
    SET @pub_name                     = '$(publication_name)'
    SET @subscriber                   = '$(subs_server)'
    SET @dest_dbname                  = '$(subs_dbname)'
    SET @distibutor                   = '$(distributor)'
    SET @job_login                    = '$(repl_admin_account)'  
                                         -- used by replication agents to connect
    to publisher for queued updating subscriptions
                                         -- make sure account has DBO access on subscriber
    db
    SET @job_password                 = '$(repl_admin_password)'
    PRINT '1. Adding subscriber for pull subsctiption of publication ' + QUOTENAME(@pub_name) + ' on database ' + QUOTENAME(@pub_dbname) + ' ...'
    EXEC sp_addsubscription
         @publication       = @pub_name,
         @article           = 'all',
         @subscriber        = @subscriber,
         @destination_db    = @dest_dbname,
         @subscription_type = N'pull',
         @update_mode       = N'read only',
         @sync_type         = 'replication support only',
         @status            = 'active'
    IF @@ERROR <> 0 RETURN
    Execute sp_helpsubscription @publication = 'FTBTrade_TEST-TranPub01'
    --@pub_name

  • SQLSERVER Merge Replication Error: Command attempted: {call sp_MSreleasemakegenerationapplock}

    Dear Friends, I updated SQL SERVER 2k5 with SP4 and I am getting error while synchronizing merge replication.
    Here is the error in Replication Monitor:
    Command attempted:
    {call sp_MSreleasemakegenerationapplock}
    Error messages:
    The merge process was unable to create a new generation at the 'Subscriber'. Troubleshoot by restarting the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200994)
    Get help: http://help/MSSQL_REPL-2147200994
    Internal Query Processor Error: The query processor encountered an unexpected error during execution. (Source: MSSQLServer, Error number: 8630)
    Get help: http://help/8630
    I executed below statement in both Publisher and Subscriber, but didn't help.
    update sysmergepublications set [generation_leveling_threshold] = 0
    Some suggests that I should use SP2 Update Package, Though that is installed and I am using SP4 now.

    Hi arahmancsd,
    Hi arahmancsd,
    According to your error message, when you sync data in merge replication, check if you use a SELECT INTO query statement. If you run the same INTO query twice and separately or you perform an operation that causes SQL Server to recompile the second SELECT
    INTO query, they all return the error 8630 message.
    For more information, see:
    http://support.microsoft.com/kb/323586/en-us
    Since you have changed the generation_leveling_threshold to 0 in sysmergepublications table in publisher and in subscriber. Please do not update the system tables directly. You can follow the steps mentioned in workaround section of
    http://support.microsoft.com/kb/953568.
    Hope it can help you.
    Regards,
    Sofiya Li
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Merge replication is not happening in one way

    Hi ALl,
    We have merge replications setup. it is not working in one direction. I enabled the logging to output fine but no use i could not find anything. The pings are fine no drops. Telnet is working. no load on server. i contacted network teams there is no issues.
    What could be the issue?
    The merge process could not retrieve column information for table 'dbo.MAINT'. Verify that you have sufficient privileges on the database and retry the operation.The merge process could not enumerate changes at the 'Subscriber'. When troubleshooting, restart
    the synchronization with verbose history logging and specify an output file to which to write.
    But the agent subsystem account and replication has sysadmin permission no possibility of password issue.
    Snapshot folder and file not be used here. 
    Select * from MSmerge_history
    order by time Desc
    Query result is
    Uploading data changes to the Publisher. 
    after that there is no status
    Please help Its very urgent issue

    Hi Ashwin,
    Thanks for the reply.
    PFB verbose output. there are no blocking on both publisher and suscriber.
    2015-01-27 13:07:23.493 Microsoft SQL Server Merge Agent 10.50.1600.1
    2015-01-27 13:07:23.502 Copyright (c) 2008 Microsoft Corporation
    2015-01-27 13:07:23.513 Microsoft SQL Server Replication Agent: replmerg
    2015-01-27 13:07:23.519 
    2015-01-27 13:07:23.524 The timestamps prepended to the output lines are expressed in terms of UTC time.
    2015-01-27 13:07:23.529 User-specified agent parameter values:
    -Publisher Publisher
    -PublisherDB DODA_Prod
    -Publication DODA_PUB
    -Subscriber Subsciber
    -SubscriberDB DODA
    -Distributor Publisher
    -DistributorSecurityMode 1
    -HostName West Ariel
    -Continuous
    -output E:\VerboseData\WAL\Replout.txt
    -XJOBID 0x9BBE899CE4C3FF4DB358BEDD0F7E3970
    -XJOBNAME Publisher-DODA_Prod-DODA_PUB-Subsciber-92
    -XSTEPID 2
    -XSUBSYSTEM Merge
    -XSERVER Publisher
    -XCMDLINE 0
    -XCancelEventHandle 0000000000001A34
    -XParentProcessHandle 0000000000002708
    2015-01-27 13:07:23.619 Percent Complete: 0
    2015-01-27 13:07:23.623 Connecting to Distributor 'Publisher'
    2015-01-27 13:07:23.627 Connecting to OLE DB Distributor at datasource: 'Publisher', location: '', catalog: '', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:07:23.715 OLE DB Distributor: Publisher
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: 
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:07:23.722 OLE DB Distributor 'Publisher': {call sp_MSgetversion }
    2015-01-27 13:07:23.738 OLE DB Distributor 'Publisher': {call sp_helpdistpublisher (N'Publisher') }
    2015-01-27 13:07:23.755 OLE DB Distributor 'Publisher': {call sp_MShelp_repl_agent (N'Publisher', N'DODA_Prod', N'DODA_PUB', N'Subsciber', N'DODA', 1)}
    2015-01-27 13:07:23.776 OLE DB Distributor 'Publisher': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'Publisher')
    2015-01-27 13:07:23.781 OLE DB Distributor 'Publisher': {call sp_MShelp_merge_agentid (0,N'DODA_Prod',N'DODA_PUB',null,N'DODA',90,N'Subsciber')}
    2015-01-27 13:07:23.788 OLE DB Distributor 'Publisher': {call sp_MShelp_profile (92, 4, N'')}
    2015-01-27 13:07:23.794 Percent Complete: 0
    2015-01-27 13:07:23.794 Connecting to OLE DB Publisher at datasource: 'Publisher', location: '', catalog: 'DODA_Prod', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:07:23.796 Initializing
    2015-01-27 13:07:23.806 OLE DB Distributor 'Publisher': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:07:23.812 OLE DB Publisher: Publisher
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: DODA_Prod
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:07:23.817 Percent Complete: 0
    2015-01-27 13:07:23.818 OLE DB Publisher 'Publisher': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation,
    N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end
    as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
    2015-01-27 13:07:23.822 Connecting to Publisher 'Publisher'
    2015-01-27 13:07:23.832 OLE DB Publisher 'Publisher': {call sp_MSgetversion }
    2015-01-27 13:07:23.835 OLE DB Distributor 'Publisher': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:07:23.846 Connecting to OLE DB Publisher at datasource: 'Publisher', location: '', catalog: 'DODA_Prod', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:07:23.860 OLE DB Publisher: Publisher
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: DODA_Prod
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:07:23.870 OLE DB Distributor 'Publisher': {call sp_MShelp_repl_agent (N'Publisher', N'DODA_Prod', N'DODA_PUB', N'Subsciber', N'DODA', 1)}
    2015-01-27 13:07:23.878 Connecting to OLE DB Subscriber at datasource: 'Subsciber', location: '', catalog: 'DODA', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:07:29.240 OLE DB Subscriber: Subsciber
    DBMS: Microsoft SQL Server
    Version: 10.00.1600
    catalog name: DODA
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:07:32.330 OLE DB Subscriber 'Subsciber': {call sp_MSgetversion }
    2015-01-27 13:07:33.910 OLE DB Subscriber 'Subsciber': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation,
    N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end
    as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
    2015-01-27 13:07:34.687 Percent Complete: 0
    2015-01-27 13:07:34.687 OLE DB Subscriber 'Subsciber': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:07:34.690 Connecting to Subscriber 'Subsciber'
    2015-01-27 13:07:34.697 OLE DB Distributor 'Publisher': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:07:35.730 Percent Complete: 0
    2015-01-27 13:07:35.730 OLE DB Subscriber 'Subsciber': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:07:35.736 Retrieving publication information
    2015-01-27 13:07:35.744 OLE DB Distributor 'Publisher': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:07:36.475 Percent Complete: 0
    2015-01-27 13:07:36.484 Retrieving subscription information.
    2015-01-27 13:07:36.490 OLE DB Distributor 'Publisher': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:08:03.441 OLE DB Subscriber 'Subsciber': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:08:04.265 Percent Complete: 0
    2015-01-27 13:08:04.269 Uploading data changes to the Publisher
    2015-01-27 13:08:04.278 OLE DB Distributor 'Publisher': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:08:11.122 Connecting to OLE DB Subscriber at datasource: 'Subsciber', location: '', catalog: 'DODA', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:08:15.591 OLE DB Subscriber: Subsciber
    DBMS: Microsoft SQL Server
    Version: 10.00.1600
    catalog name: DODA
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:08:18.670 Connecting to OLE DB Publisher at datasource: 'Publisher', location: '', catalog: 'DODA_Prod', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:08:18.690 OLE DB Publisher: Publisher
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: DODA_Prod
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:08:18.697 Connecting to OLE DB Subscriber at datasource: 'Subsciber', location: '', catalog: 'DODA', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:08:23.111 OLE DB Subscriber: Subsciber
    DBMS: Microsoft SQL Server
    Version: 10.00.1600
    catalog name: DODA
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:08:26.124 Connecting to OLE DB Publisher at datasource: 'Publisher', location: '', catalog: 'DODA_Prod', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:08:26.141 OLE DB Publisher: Publisher
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: DODA_Prod
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:39:38.053 The merge process could not retrieve column information for table 'dbo.MAINT_STOCK_COSTS'. Verify that you have sufficient privileges on the database and retry the operation.The merge process could not enumerate changes at the 'Subscriber'.
    When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.
    2015-01-27 13:39:38.053 
    2015-01-27 13:39:38.078 OLE DB Subscriber 'Subsciber': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:39:39.119 Percent Complete: 0
    2015-01-27 13:39:39.133 No data needed to be merged.
    2015-01-27 13:39:39.138 The process was cancelled.
    2015-01-27 13:39:39.146 OLE DB Subscriber 'Subsciber': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:39:39.902 Percent Complete: 0
    2015-01-27 13:39:39.910 The process was successfully stopped.
    2015-01-27 13:39:39.915 The process was cancelled.
    2015-01-27 13:39:39.926 The Merge Agent was unable to update information about the last synchronization at the Subscriber. Ensure that the subscription exists at the Subscriber, and restart the Merge Agent. 
    2015-01-27 13:39:39.931 Percent Complete: 0
    2015-01-27 13:39:39.935 Category:NULL
    Source:  Merge Replication Provider
    Number:  -2147200999
    Message: The process was successfully stopped.
    2015-01-27 13:39:39.939 Percent Complete: 0
    2015-01-27 13:39:39.943 Category:NULL
    Source:  Merge Process
    Number:  -2147198718
    Message: The process was cancelled.
    2015-01-27 13:39:39.948 The Merge Agent was unable to update information about the last synchronization at the Subscriber. Ensure that the subscription exists at the Subscriber, and restart the Merge Agent. 
    2015-01-27 13:39:39.955 The merge process was unable to update last synchronization information at the Publisher.
    2015-01-27 13:39:39.962 OLE DB Subscriber 'Subsciber': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:39:40.738 [100%] Percent Complete: 100
    2015-01-27 13:39:40.744 The process was successfully stopped.
    2015-01-27 13:39:40.750 The process was cancelled.
    2015-01-27 13:39:40.756 Disconnecting from OLE DB Subscriber 'Subsciber'
    2015-01-27 13:39:40.762 Disconnecting from OLE DB Subscriber 'Subsciber'
    2015-01-27 13:39:40.768 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.773 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.778 Disconnecting from OLE DB Subscriber 'Subsciber'
    2015-01-27 13:39:40.783 Disconnecting from OLE DB Subscriber 'Subsciber'
    2015-01-27 13:39:40.787 Disconnecting from OLE DB Subscriber 'Subsciber'
    2015-01-27 13:39:40.791 Disconnecting from OLE DB Subscriber 'Subsciber'
    2015-01-27 13:39:40.795 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.799 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.805 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.810 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.814 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.819 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.823 Disconnecting from OLE DB Distributor 'Publisher'
    2015-01-27 13:39:40.829 Disconnecting from OLE DB Distributor 'Publisher'

Maybe you are looking for

  • Help urgent plz - lsmw retail material.

    hi all, i am posting my message again as this problem seems to have taken me too. i am new to lsmw and trying to create a retail material through lsmw. i chose business object method with business object as bus1001001.method is 'clone' everything has

  • My application doesn't start when I run the domain as windows service

    I am using weblogic 10.3.2 and i created a domain called rec_domain and i have AdminServer also i deployed application called myApplication to the rec_domain then i created windows service to run the server as a windows service The Script for Setting

  • How to give internet priority to one computer on a network?

    Hello, I have 2 computers on 1 modem/router. 1 is connected directly by Ethernet, second one via bridge AirPort. Is it posible that when in simultaneus transfers sitations 1 or the computers would have a priority to recieve data, and the other would

  • Overall release strategy in purchase requisition

    hi, how do i configure overall release in case of  purchase requisition. i have done item wise release in PR. but in case of overall release what field I should take in characteristics?  is their required two seperate classes for item and overall rel

  • Subcontract challan reconcillation problem

    Dear All, We are getting the following message while reconciling Subcontract challans  " Material XXXX is not assigned fully , short by X nos ".  Is it because  if we post a single GR referencing two Purchase orders for same vendor with two different