.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

Can't replicate few tables in Snapshot replication SQL 2005 in two different domain

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

I am not able to replicate few tables of a database using snapshot replication.Both publisher and subscriber are in different network and domain.Although I am able to replicate 950 tables but facing problem in some 30 tables.I am using push replication and I can telnet 1433 port from A server to B server but vice versa not happening.When I am replicating few records of that few tables it is replicating properly but not able to replicate complete table. I tried Verbose history too but I didn't get complete error.

Please help me out.....

View Complete Post

More Related Resource Links

Snapshot Replication between MSQL 2005 SP3 and MSQL 2008 R2; cannot create subscription


I tried to setup a snapshot replication between 2 servers, running different MSQL versions

The distribution database is set up on subscriber side and the publisher use this Distribuitor. The creation of  snapshot works fine on publisher without errors.

But, when i try to create the subscription on Subscriber i got this message:

The article '(null)' does not exist.
Could not update the distribution database subscription table. The subscription status could not be changed.
The subscription could not be created.
The subscription could not be found.
Changed database context to 'DMC'. (.Net SqlClient Data Provider)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.4035&EvtSrc=MSSQLServer&EvtID=20027&LinkId=20476

Server Name: hpserver\erp <--this is the publisher
Error Number: 20027
Severity: 11
State: 1
Procedure: sp_MSadd_subscription
Line Number: 223



sql 2005 merge replication replicate 65 GB binary and cause "MSSQL_REPL20216 due to OS error 2"



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

SQL Server 2005 SP4 Install Fails - error log references replication system tables


The OS is Windows Server 2003 R2 SP2 (32 bit).  Trying to install SQL Server 2005 SP4 (current version is 9.00.4035).  All SQL products update without error, except for the Database engine.  The error listed in the summary.txt file in C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix is:

Product                   : Database Services (MSSQLSERVER)
Product Version (Previous): 5000
Product Version (Final)   :
Status                    : Failure
Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2463332_sqlrun_sql.msp.log
Error Number              : 29537
Error Description         : MSP Error: 29537  SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Update or insert of view or function 'dbo.syspublications' failed because it contains a derived or constant field.. To continue, correct the problem, and then run SQL Serv

Locking published tables while generating the snapshot infinite (Transactional replication)


I set up a transactional replication, publisher 2005 SP2 to a subscriber SQL 2008r2. The database is about 90 GB. When I want to create a Snapshot, the snapshot agent is running to 96% and then give a error. I have set up some logging, here is the tail of it:


2011-05-16 20:16:15.32 [96%] Inserted stored proc to disable constraint/triggers article 'WGF B.V.$XBRLAutorisatieRegister' during concurrent snapshot into the distribution database.
2011-05-16 20:16:15.32 [96%] Inserted stored proc to disable constraint/triggers article 'WGF B.V.$XBRLBericht' during concurrent snapshot into the distribution database.
2011-05-16 20:16:15.33 [96%] Inserted stored proc to disable constraint/triggers article 'WGF B.V.$XBRLBerichttype' during concurrent snapshot into the distribution database.
2011-05-16 20:16:15.33 [96%] Inserted stored proc to disable constraint/triggers article 'WGF B.V.$XBRLFault' during concurrent snapshot into the distribution database.
2011-05-16 20:16:15.33 [96%] Inserted stored proc to disable constraint/triggers article 'WGF B.V.$Ziekmeldingsregistratie' during concurrent snapshot into the distribution database.
2011-05-16 20:16:15.33 [96%] Inserted stored proc to disable constraint/triggers article 'WGF B.V.$Ziekte Bijzonderheden' during concurrent snapshot into the distribution database

merge replication system tables fragmentation issue

I have Merge replication going on in my environment. The problem is that system tables like MSmerge_content, MS merge _tombstone and MSmerge_genhistory are getting fragmented. We are rebuilding indexes time to time daily. But we want some good fix. Just send some good idea guys?

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. regards Vijay  

transactional replication and sp_MSupd tables

Hi thre, My target server keeps running sp_MSupd sp for different values in profiler and synch status shows "delivering replication commands" I keep waiting but this never ends. and ultimately we run a snapshot and it can't be applied. So recreate the whole replication again. It runs fine for a while but again, the sp_MSupd sp starts running on the target server and the replication goes down again. I don't know how to fix this. any advices?   Regards

SQL Server 2005 Merge Replication

We did the following: We setup a database with all of standard tables, views, etc. We then put in place merge replication for a few of the tables within this database, including a tables called "Areas". We can execute SQL statements to insert rows into this table fine. We then applied an update script for this database to change a few tables by adding fields and changing indexes, etc.  We didn't change the "Areas" table though. After the update to the database structure, we get an error when trying to insert into this "Areas" table. The error message was the following: The insert failed. It conflicted with an identity range check constraint in database 'AETest', replicated table 'dbo.Areas', column 'AREPrimaryId'. If the identity column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent.  The statement has been terminated.   What would cause such a problem and how do we resolve it?  The structure of the "Areas" table before and after the update is the following: USE   [AETest] GO /****** Object: Table [dbo].[Areas] Script Date: 08/24/2010 17:42:36 ******/ SET   ANSI_NULLS ON GO SET   QUOTED_IDENTIFIER ON GO SET   ANSI_PADDING ON

Merge Replication: How to give read access on snapshot share to a sql account

Hello All, I want to give read access to an sql account(not windows account). Can it be given or not. Someone please tell. Thanks saandii777

Replication between SQL Server 2005 and SQL Server 2008

Hi,    We were using SQL Server Transactional Replication between two SQL Server 2005 servers. Now we are going to upgrade the Publisher server to SQL Server 2008, Distributor Server remains as SQL Server 2005.     Can anyone let me know what is the challenges we need to face when configuring Replication between SQL Server 2005 and SQL Server 2008. Replication Method - Transactional Replication Distributor/Subscriber - SQL Server 2005 Publisher     -  SQL Server 208 Regards, Fazlu.

How to let a non admin business user run a replication snapshot job?

According to the msdn library, I would have to give the non admin user (User1) SQLAgentUserRole privileges. But it also says that it has to be a local job and not a multi server job. Is the snapshot agent job a local or multi server job? Considering the snapshot agent is a local job and i make USER1 the owner of that job. He should be able to run the job rite? I need to give USER1 the ability to run sp_start_job to start the snapshot agent ONLY! (and not any other jobs). So what are the steps to do this? I also read that the only way to achieve this is by creating a proxy account? Is there an article somewhere that best describes this?  

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.

Issue with transactional replication on SQL 2005 SP3 using row filters with bit columns

We recently upgraded from SQL 2000 to SQL 2005 SP3 and I am noticing something that I think is a bug with replication from a publication that has an article in it with row filters.  It seems to be that if the row filter has columns that are bit datatype and that column is updated on the publisher to cause the row filter to exclude it, it is not removed from the subscriber.  If you update a column that is part of the row filter that is not a bit datatype it works as expected.  I can reproduce this in a test environment with a small base table.  In production this is resulting in an occasional 20598 error "The row was not found at the Subscriber when applying the replicated command". Is anyone aware of a hotfix that addresses this? I can think of a few work arounds but the table is rather large and I really would like to avoid having to pull replication, re-snap or changing datatypes on the base table etc. Any suggestions are greatly appreciated.  Thanks!

How to replicate for 2008 to 2005?

Hello, I would like to replicate (one way) a database from sql 2008 to sql 2005. Between 2005's I a backup log database, etc. a) Is the above way feasible for my problem? b) What would be the easiest way, since they are in different domains with firewalls between? Thank youChristos

Using SQL Server Replication for SQL Server 2005 and 2008

I have an ASP.NET application that uses replication, and uses the RMO DLLs to do this. I initially built the application against the 2005 version of the DLLs and have it running successfully against SQL Server 2005. However, when I try running it against SQL Server 2008 it doesn't work. Initially I didn't deploy the Microsoft.SqlServer.* DLLs with my app - instead relying on them being in place on the server on which it was installed. However, when trying to make it work against SQL Server 2008 it was looking for the 2005 version DLLs which it wasn't able to locate. Following some other advice I read online I have now swapped out the 2005 DLLs and referenced the 2008 assemblies in my .NET project. In my MSI I now also deploy (i.e. redistribute) the SQL Server 2008 DLLs to the bin folder of my ASP.NET project. Now, when I try to run the application against SQL Server 2005 it fails to load the Microsoft.SqlServer.Replication assembly. I run depends.exe against this and find that it's dependent on SQLNCLI10.DLL which is missing on my machine with only SQL Server 2005 on it. So, what am I to do? Is this possible? How do I get around this?

A query in Snapshot replication ---- Please help !!!!!

Hi,     I have a SQL Database with different roles and users,depends upon their roles,permissions,they can see some table,views and etc.     Now,I am going to replicate (Snapshot) the same Database into different server.    My query is, in the source database incase if they do some changes in the roles,permissions,adding roles/updation of users happens, the same will be replicated in the  destination databsase as well? One of my friend told that ,snapshot replication just deals with records inside the Database and does not deal with users/roles/permissions...Is that so?

Replication on SQL 2005

I am trying to configure replication on an sql server 2005. It gives me an error message that I should enable the server to be a distributor first. The wizard doesn't go forward. It ends there and I can't continue
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