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

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Replication monitor could not conenct to distributor

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


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.



View Complete Post

More Related Resource Links

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?



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?

Replication Monitor Problem


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?


Setting Publisher as distributor also in Transactional replication from SQL 2008 to SQL 2008


Can some one please tell how will the performance of the Publisher be affected if I use the same server as the distributor ? How can i get the best performance from Publisher in case i use this as distributor as well ?


any ideas or links  would be appreciated 




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


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

Toolbox: Easy File Backup, Exploring Files And Folders Inside Visual Studio, Multiple Monitor Softwa


If the responsibility for creating, managing, and executing routine backups is yours, these tools will make it easier. Also see how you can browse folders and files from inside Visual Studio.

Scott Mitchell

MSDN Magazine May 2009

.NET Matters: Deadlock monitor


This month Stephen Toub discusses deadlocks that can occur when synchronizing threads.

Stephen Toub

MSDN Magazine October 2007

Advanced Basics: Monitor Your Apps with System.Diagnostics


It never fails. The application you just deployed ran great on your development machine-but stumbles in production. The problem might show up right away or maybe it creeps up over time. Now what?

Brad McCabe

MSDN Magazine July 2006

Toolbox: Generate Office Documents, Monitor Event Logs, and More


Most data-driven Web sites are used as interfaces to collect, process, and summarize information. Reports that summarize the data can be presented to the user in a variety of formats-the most common way is to display the report directly in a Web page.

Scott Mitchell

MSDN Magazine June 2006

Call MOM: Instrument and Monitor Your ASP.NET Apps Using WMI and MOM 2005


The current version of Windows Management Instrumentation (WMI) satisfies many current and future manageability requirements. In this article Michael Jurek demonstrates how WMI provides important system management capabilities and develops a WMI-aware monitoring solution you can use to instrument your ASP.NET applications. He then introduces the capabilities of MOM 2005 that allow you to monitor these instrumented applications.

Michael Jurek

MSDN Magazine September 2005

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