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

Post New Web Links

Replication Monitor Problem

Posted By:      Posted Date: October 06, 2010    Points: 0   Category :Sql Server

I tried to monitor the replication by running the query.



* FROM [distribution].dbo.MSreplication_monitordata

Now, one distribution agent is failed; however the status returned by the query doesn't show that. It is idle instead of failed. Do you know why this happens? What's the best way to monitor automatically?


View Complete Post

More Related Resource Links

Wickedly Strange .Net WPF Performance Problem Dissapeers with Windows 7 Performance Monitor Open

Hello Everyone, I have been developing one large and complex WPF application for 13 months now, all is going well and especially tonight as I now have some sort of clue or hint to what I have been seing now for quite some time.  Here is the rundown. 1) Running on i5 processor with 4GB RAM and Windows 7 2) The application was developed all in .Net 4.0, WPF C#. 3) It is heavily GUI intensive and also uses Entity Framework Detached for Database Access. 4) Is multi-threaded / multi-tasking. I am a nutcase when it comes to testing.  Since my graphical application heavily depends upon performance and determinsm (please somebody don't start with the C++ vs .Net on here) and has been performing great FOR THE MOST PART.  Every once in a while, I see that the application runs into the weeds for 5 or 6 seconds and the interface is unresponsive.  I have this thing tuned finely too.  Well now toward the end of development I have finally had to face that bug so to speak.  I can force it by clicking spastically on my buttons causing an event storm and making the system update the GUI.  SO!  Great start, I can now cause the problem on a regular basis (for you youngsters that is actually a good thing)!  Alright, so I start with the easiest investigative tool, CNTRL - ALT - DEL into Windows 7 Performance Monitor.  As you can tell from

Merge Replication and "Field size too large" problem

Hi,I have a single table database for tests configured on my server, I create another database using the same script that I use on my server on another server. I made a several inserts on the first database and I configure a merge replication between the two server and on the table article configure 2 integer columns to not be replicated and configure @pre_creation_cmd to none, because if I use another configuration on @pre_creation_cmd , when the snapshot applied it must recreated my table without the columns and I need then on another server. When I set @pre_creation_cmd  to none I need to create a rowguid column on the another server. My server is the Publisher and my another server is the publisher. I create the snapshot and when I sinconize the databases, the sinconization return that error:=================================================================================================The process could not bulk copy into table '"dbo"."CONSTS"'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20037)Get help: http://help/MSSQL_REPL20037 Field size too large (Source: MSSQLServer, Error number: 0)Get help: http://help/0 To obtain an error file with details on the errors encountered when initializing the subscribing table, execute the bcp command that appears below.  Consult the BOL for more information on the bcp utility and its supported options. (Source:

Give non-SA Access to Replication Monitor - SQL 2008

I need to give a user access to Replication Monitor in SQL 2008. How can I do this without giving them SA access ?  

Replication Monitor - Friendly Name

Anyone know how to get this field to populate from a given subscription in Merge replication?

SQL 2005 Standard - problem with ORACLE replication


Hello All

Windows 2003 SP2  x64 + SQL 2005 Standard 32bit + Oracle ODBC Driver 10.2.01

Replication between SQL servers works FINE, bit I'm not able to replicate betwen MS SQL and ORACLE server.

Any ideas ?


Replication monitor could not conenct to distributor



In our environment we are maintaining Transactional replication between 2 servers.

Both  servers are sql server 2005 with standard edittion.

By  launching replication monitor in  server 1  we can see both the servers publisher status.

But i found that server 2 publisher  is not able  to connect with distributor.I tried to connect to distributor.Here i am getting error like

Replication monitor could not connect to distributor of server 2.

Failed to connect to server 2 (Microsoft .Sqlserver.Conenctioninfo)

Login failed for user " .The user is not associated with a trusted sql server conenction .(Microsoft sql server ,error :18452)

Kindly help me to find out the exact rootcause.



Latency on Replication Monitor(Transactional Replication)


Latency shows around 18 hrs today on the replication monitor and status shows Performance critical.Is that mean the subscriber is 18 hrs latency when compared to the publisher?Will it catch up eventually?

Thanks In advance.

Cannot open replication monitor in a distributed scenario



I have created a replication topology on 2 servers. The distributor is located on the subscriber in order to reduce server load on the publisher. The publisher is a Sql Server 2005, the subscriber & distributor is Sql Server 2008.

When I want to examine the replication with replication monitor, I have to do this at the publisher. If I try to view synchronization status at the subscriber it throws the exception 'You must manage this subscription from the publisher because it shares a distribution agent with subscriptions to other publications from the same publication database.' Also I don't even have the option to call the replication monitor at the subscriber. But when I try to open a replication monitor at the publisher, it isn't able to connect to the distributor because it is Sql Server 2008.

Is there any way I can use the replication monitor in my deployment scenario?

Greets, Stefan

replication problem in MSSQL2008



I have a two servers both of them have installed SQL Server 2008 Enterprise, also each of them have DB called MCG, same amount of data and tables.

Which type of replication is better to use and how to setup it.

I tried to create transcation replication,

but when it starts it creates on second server all tables again (creates some kind of *.pre and *.sch files)  and tries to populate data that already exists there.

After creating those tables again and initialize populating data from 1st to 2nd and gives an error.

I need to replicate data is only changed on first server  and this changes should immediately appear on second server.

Your help is really appreciated.



Merge replication nested view problem

Using SQL 2005 as pub and SQL EXPRESS as sub using Merge replication. Got the following error message

The schema script 'CD_InTransit_v_153.sch' could not be propagated to the subscriber.
Error Detail:
The schema script 'CD_InTransit_v_153.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001
Unable to replicate a view or function because the referenced objects or columns are not present on the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL20164)
Get help: http://help/MSSQL_REPL20164
Invalid object name 'dbo.Debit_v'. (Source: MSSQLServer, Error number: 208)
Get help: http://help/208

According to error message, it seems that debit_v is missing. However, I cannot control the sequence of view to replicate.  How can I solve this problem

Replication Monitor: Publication Node will not expand



I'm using SQL Server 2005 Replication Monitor to monitor a number of Publications.

One Publication node, will not expand however, that is to say that when clicked it's label changes to expanding and then never actually completes in order to provide details of the Publications at the Publisher. This means that I cannot highlight a specific Publication at the Publisher for further investigation and instead have to review all Subscriptions in the subscription watch list, which is cumbersome.

I have tried removing the Publication and adding it back to Replication Monitor without success, the issue persists. I have also tried creating a SQL Server Login with SYSDBA rights in order to connect to the remote distributor in order to rule out a permissions issue.

Has anyone else come across this issue before or can perhaps provide further suggestions in order to troubleshoot?

John Sansom | SQL Server Database Administrator

Replication Monitor losing connection to distributor


We are having an issue with our replicaiton monitor.  Upon opening the monitor it shows the publisher with a red x next to it.  After right clicking and connecting to the distributor it shows the publications in the tree view, but not in the publications tab.  Of course, after the refresh (default 5 seconds) it loses its connection again.  If I change the default refresh time, it stays connected and I can browse some of the data.  But the publications are still not listed when the publisher is selected in the tree view.  Any thoughts on why it would do this and what we can do to resolve the issue?



Replication Monitor shows old publication


So, I am using Replication monitor, and under one of my publisher nodes, I still see an old publication, which I do not see in SSMS Object explorer.  This publication shows a red 'x', and I can't view the properties.  I've tried using 'sp_droppublication' at the publisher, 'sp_dropsubscription' at the publisher, 'sp_droppullsubscription' at the subscriber, and 'sp_subscription_cleanup' at the subscriber.

Any ideas on how to get rid of this?  It's making the publisher node show a red 'x' also, which is misleading.  Thanks!


TSQL to know there is an error in replication monitor (red X)


In SQL 2005 and SQL 2008, in the Replication Monitor it will show a red X if any of the subscriptions have an error. Is there a TSQL statement i can run to see that without having to go into the Replication Monitor?

i am trying to come up with some way to see that information and present it to our customer from our application without them having to connect to SSMS and look at the replication monitor.

thanks for you help.


Merge Replication Infinite Loop & Time Problem


Hi all,

We have merge replication system between Sql Server 2008 R2 64bit Enterprise Edition (As a Publisher&Distributor) and Sql Server 2008 R2 Express Edition (As 800+ Subscribers). We use only "https " method as transfer method. We have 30 tables and we have Joins & Filters. Our system work normally for 5-6 months.

But for last 10 days, sometimes (generally initial snapshot being downloaded), it takes over 14 hours to replicate!! I think an infinite loop is being occured during the process. I trace the publication server with Sql Server Profiler 2008 and here is the trace file.

Lots of times, i see this line "exec sp_MSmergeupdatelastsyncinfo '8C01EA1F-153D-47BC-ACD3-F8439ACB7B76',2,N'Merge completed with no data changes processed .'" (and also other lines which repeat similar to this one) with same/different  Session ID's. And when i first see this line is after 3 seconds the start time of the Process!! And after , 6 seconds again same line, and after 13 seconds again same line and it goes on like this. I think, in fact synchronization process is finished after 5-6 seconds (normally because there is no any data change in fact!) but for some reason, it continues to same process over and over.

Is this a bug or anything else, h

Transactional Replication's Problem




I have two servers. I want to make replication between SQL 2005 and SQL 2008 R2.

SQL 2005 is distributor and SQL 2008 R2 is subscriber. I have already  done everything for replication but i got following error during synchronization:

"The process could not connect to Subscriber 'SQl 2008 R2 Server's name '."


Error messages:

The process could not connect to Subscriber 'Ql 2008 R2 Server's name'. (Source: MSSQL_REPL, Error number: MSSQL_REPL0)

Get help: http://help/MSSQL_REPL0

SQL Network Interfaces: Error getting enabled protocols list from registry [xFFFFFFFF].  (Source: MSSQLServer, Error number: -1)

Get help: http://help/-1

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (Source: MSSQLServer, Error number: -1)

Get help: http://help/-1

Login timeout expired (Source: MSSQLServer, Error number: HYT00)


Replication Monitor Error



after updating a SQL Server 2008 (German) installation to SQL Server 2008 R2 (English), I get an error when I connect to the distributor by using the replication monitor on the same machine. I deinstalled the old version and made a complete new installation.

the error message is: "an error occurd while retrieving the puplisher data" and "Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt"

The last massage is in german, which means translated: "Object reference not set to an instance of an object"

When I open the distributor on this machine from an other machine everthing is fine.

I believe, there is somewhere a library which is still from the previous installation. But where?

Thats how it look like: http://ausgelesenes.de/rm_error.jpg

Server Info ===========================

Microsoft SQL Server Management Studio                        10.50.1600.1
Microsoft Analysis Services Client Tools                        10.50.1600.1
Microsoft Data Access Components (MDAC)                        3.86.3959

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