Replication Monitor Could Not Connect To Distributor
Jun 25, 2007
Hello Guys,
I have the following scenario:
PC1 : located in Dubai representing my laptop
PC2: located in Denver ,
Both pcs are connected to each other via the internet as i am using Aliases ,they can both access and see each other using SQL Auth.
I want to implement Merge Replication to Synchronize TestDB ,
I have NO DOMAIN connnecting them.
I Created a new publication ,under security i asked the agent to use the Sa account to connect
When launching the rep monitor i get the following error:
"Replication Monitor could not connect to Distributor 'laptop'."
"Login failed for user ''. The user is not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider)"
Both Publisher and Distributer are on my Laptop ,why cant they connect to each other?
Another Question : could i implement Traditional Merge replication to synchronize my DBs or do i need to configure Web Synch in Merge rep to enable connecting via the internet?!
Thanks Guys!
Moodi
View 4 Replies
ADVERTISEMENT
Jan 29, 2008
I am not able to connect to Remote Distributor from Publisher using Administrative Link Password. I have configured the Distributor on 1 m/c and Publisher on another m/c. When i use the wizard to configure the publisher using remote distributor. I have also specified the same Admin Password link (distributor_admin) in the distributor m/c.
I am getting the following message:
TITLE: New Publication Wizard------------------------------
SQL Server could not connect to the Distributor using the specified password.
[URL]
------------------------------ADDITIONAL INFORMATION:
Connection to server [SANMENON] failed.OLE DB provider "SQLNCLI" for linked server "D956CF83-AE2E-4FC5-83DD-BE90D84A3950" returned message "Login timeout expired".OLE DB provider "SQLNCLI" for linked server "D956CF83-AE2E-4FC5-83DD-BE90D84A3950" returned message "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.". (Microsoft SQL Server, Error: 21670)
[URL]
------------------------------BUTTONS:
OK------------------------------
View 12 Replies
View Related
Feb 8, 2006
Precedents
Windows 2000 Server
1 SERVERNAME
SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003 16:08:15
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
1 SERVERNAMEINSTANCE
SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
IIS 5.0
SQL Server CE 2.0 (sp3a)
Merge replication previously working fine.
The problem
After migrating MSDE from sp3a to sp4 (in order to fix CE replication bug) I can't sync to MSDE.
I got the following error code: [29045]->[Initializing SQL Server Reconciler has failed.] so I've looked into SQL Server CE log file and I've found the following error message:
2006/02/07 19:44:23 Thread=9A8 RSCB=4 Command=SYNC Hr=00000000
The process could not connect to Distributor 'Distributor-name'. 20084
2006/02/07 19:44:23 Thread=9A8 RSCB=4 Command=SYNC Hr=00000000
Data source name not found and no default driver specified
I've already tried without success
Uninstalling all SQL Server 2000 (EE) instances (except for the "no instance")
Unistalling and re-install MSDE (sp4)
Re-registering sscerp20.dll.
Rebooting server.
Restarting IIS.
Any ideas?
Sebastian
View 3 Replies
View Related
Jan 30, 2007
I have setup transactional replication everything on one box. later(two or three weeks later), Replication monitor is show red X Under my publishers (publications is disconnected). this is SQL2005.
Everyone known how to fix this problem?
Thanks,
Frank
View 1 Replies
View Related
Aug 19, 2015
If I'm on a remote machine, meaning a computer not in the WSFC cluster, and I open SSMS 2014, point it to a SQL Instance, and open activity monitor:
1. I get all the panes and charts except % Processor Time.
2. Then, if I authenticate to the cluster's domain by mapping a drive with valid domain credentials, I'm free to put performance counters in the Perfmon - - - but SQL Activity Monitor shuts down with“The Activity Monitor is unable to execute queries against server SQL-V01INSTANCE1..Activity monitor for this instance will be placed into a paused state.Use the context menu in the overview pane to resume the activity monitor.
Additional information: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))(Mscorlib)”
3. Of course, the Activity monitor can't be resumed via the context menu. Removing counters and closing the perfmon do not work. I dropped the mapped drive and rebooted the machine. That brought back 95% of the information in the Activity monitor.
4. Further experimentation showed that any mapping of drive shares present on the SQL Server to the computer running SSMS cut off functionality of the 'overview' pane in the remote machine's SQL Activity monitor -- the monitor that had been trying to watch the server offering the shares.
View 4 Replies
View Related
Feb 6, 2008
I have publisher and distributor, both on SQL 2005. I need to re configure replication. When I try to create publisher, the wizard gives me an option to give password to connect to Distributor. Even after resetting this password on the distributor server, publisher still gives me the following error.
SQL Server could not connect to the Distributor with the specified password. SQL Server Error 21670.
Need urgent help. Thank you!
View 1 Replies
View Related
Sep 1, 2006
hi friends
i am creating the Merge Replication between two server(both SQLServer-2005, on XP).
Server names are as
1. HB5B
2. VSNET1
i) On server HB5B, i had created the Publication with name 'hb_pub'.
(publisher & Distributer on HB5B server)
ii) On server VSNET1, i had created the Pull Subscription, for the publication name hb_pub( form the server HB5B), this starts fine.
iii) When i went to Viwe Synchroniztion status, it says
The process could not connect to Distributor 'HB5B'
iv) i too check the Distributor properties, its seems fine for me.
v) On server VSNET1, if creats the Push Subscription, for the publication name hb_pub( form the server HB5B), this starts fine.
vi) When i went to Viwe Synchroniztion status, it says
The server 'VSNET1' is not a Subscriber. (.Net SqlClient Data Provider)
vii) if i try again the Start button on the Viwe Synchroniztion status, it says the job is already running (with job name), Change the database context to 'HBmyDB' ( this is my database name).
the check list i made is
i) I had log on as service(SQL Server Agent (MSSQLSERVER) & SQL Server (MSSQLSERVER) ) as Administrator at server VSNET1(i mean it had the administrative right) & restarted them.
ii) I do have the administrative rights on the both of the machines.
iii) both Server have same 'sa' passwords.
please help me
any solution, hint or idea.
Regards
Thanks
Gurpreet S. Gill
View 16 Replies
View Related
Nov 28, 2006
I have a small problem, I get this following error when trying to start the snapshot agent "The process could not connect to the distributor 'distributor name'. NOTE: The step was retried the requested number of times [10] without succeeding. The step failed.
I thought it was related to users or rights but i am using the same user than in previous replication with the server and the rights haven't been altered. I don't know if someone has some knowledge of what to do or a workaround solution, any help would be greatly appreciated.
Thank you in advance.
View 6 Replies
View Related
Jan 23, 2007
I am setting up my 2005 Replication system...
publisher = 2005 sp1
Subscriber = 2005 sp1
I created a publication for a single table. Then I created the subscription to another 2005 server. Had to add it as a subscriber in the wizard. Told it to do the snapshot right away.
Everything seems fine right up to the point where it tries to connect to the subscriber... I get a cannot connect error. I have tried all kinds of security context and accounts for the sql agent to run under but nothing seems to work. I cannot even get a linked server to work. I have the subscriber setup to accept remote connections.
I am not sure where to look at next... I never had this issue in 2000.
View 14 Replies
View Related
Oct 13, 2006
Hey guys. I am creating an app that uses the RMO Merge Replication objects.
So far it can subscribe and unsubscribe just fine but when it comes to the syncing process it gets a little weird, here's why.
- If I run the SQL GUI Sync tool, it sinks fine. So that setup is working.
- When I run the C# App it blows up witht the error: "Process cannot connect to Distributor"
- Here's the weird part: When I set a breakpoint on my custom method SyncData (this method sets up the connection info and properties and then calls Syncronize( ) ) and step through the code when it gets to Syncronize( ) it runs perfectly fine, no execeptions.
I thought that maybe the Syncronize( ) method was being called too fast before the connection properties got to fully setup and connect, so I added a Thread.Sleep( ) method for 10 secs after each connection call and just before calling Syncronize( ). It still didn't work. My class is a static class by design, however, I changed it into an ordinary class and then placed the connection info in the constructor hoping it would do it's connection when the object gets initialized, that didn't work either.
If someone could please help me out with this I would greatly appreciate it.
Here's my code:
using System;using System.Collections.Generic;using System.Text;using Microsoft.SqlServer.Replication;using Microsoft.SqlServer.Replication.BusinessLogicSupport;using Microsoft.SqlServer.Management.Common;using System.Windows.Forms;using System.Threading;namespace Emds.Briefcase.BriefcaseSubscriber.BLL{ public class SyncDataClass { #region Members private static string m_statusMessage = string.Empty; private static byte m_percentComplete; public delegate void StatusTextChangeHandler(int percent, string status); public static event StatusTextChangeHandler OnStatusChange; #endregion Members #region Methods public static string SyncData() { //Delay(); // Define the server, publication, and database names. string publicationName = "Chart"; string publisherName = @"JSMITHSQL2005"; string subscriberName = @"JDOESQL2005"; string subscriptionDbName = "DataSubscriber"; string publicationDbName = "DataPublisher"; string message = string.Empty; // Create a connection to the Subscriber. ServerConnection conn = new ServerConnection(subscriberName); MergePullSubscription subscription; try { // Connect to the Subscriber. conn.Connect(); // Delay(); // Define the pull subscription. subscription = new MergePullSubscription(); subscription.ConnectionContext = conn; //Delay(); subscription.DistributorSecurity.WindowsAuthentication = false; subscription.DistributorSecurity.SqlStandardLogin = "sa"; subscription.DistributorSecurity.SqlStandardPassword = "russell"; // Delay(); subscription.PublisherName = publisherName; subscription.PublicationDBName = publicationDbName; subscription.PublicationName = publicationName; subscription.PublisherSecurity.SecurityMode = ReplicationSecurityMode.SqlStandard; subscription.PublisherSecurity.SqlStandardLogin = "sa"; subscription.PublisherSecurity.SqlStandardPassword = "russell"; // Delay(); subscription.DatabaseName = subscriptionDbName; subscription.SubscriberSecurity.WindowsAuthentication = false; subscription.SubscriberSecurity.SqlStandardLogin = "sa"; subscription.SubscriberSecurity.SqlStandardPassword = "russell"; // Delay(); // If the pull subscription exists, then start the synchronization. if (subscription.LoadProperties()) { // Check that we have enough metadata to start the agent. if (subscription.PublisherSecurity != null || subscription.DistributorSecurity != null) { // Synchronously start the Merge Agent for the subscription. subscription.SynchronizationAgent.Status += new AgentCore.StatusEventHandler(SynchronizationAgent_Status); // Delay(); subscription.SynchronizationAgent.Synchronize(); message = "Data Syncronization is a success!"; } else { throw new ApplicationException("There is insufficent metadata to " + "synchronize the subscription. Recreate the subscription with " + "the agent job or supply the required agent properties at run time."); } } else { // Do something here if the pull subscription does not exist. throw new ApplicationException(String.Format( "A subscription to '{0}' does not exist on {1}", publicationName, subscriberName)); } } catch (Exception ex) { // Implement appropriate error handling here. throw new ApplicationException("The subscription could not be " + "synchronized. Verify that the subscription has " + "been defined correctly.", ex); } finally { conn.Disconnect(); } return message; } static void SynchronizationAgent_Status(object sender, StatusEventArgs e) { m_percentComplete = e.PercentCompleted; m_statusMessage = e.Message; //Fire custom event if (OnStatusChange != null) { OnStatusChange(m_percentComplete, m_statusMessage); } } #endregion Methods }}
View 7 Replies
View Related
Apr 24, 2006
I'm trying to set up merge replication between SqlServer 2000 and SqlMobile 2005. When I create the publication, I select merge replication for SqlServer CE. When I view the status of the snapshot agent, the error message is "the process could not connect to Distributor. The step failed".
I've verified both SqlServer and SqlServer Agent are running under the same domain account (with admin access to the server). This domain account has full access to the snapshot shared folder. I've also run "exec sp_helpserver", which gives me the server name for both the name and network_name fields where id=0.
I'm able to successfully set up merge replication between SqlServer 2005 and SqlMobile 2005, but my production servers are sql 2000.
View 2 Replies
View Related
Aug 3, 2005
I was wondering if you could set up multiple distributors for one database?For example:Server A needs to publish data to server B so I set up server A's distributor as server B. Later Server A needs to publish data to server C so I want to set up the distributor for this replication to use server C.I don't think this is possible as you need to set up the distributor for the entire DB when its created not for each individual replication job.Any help is appreciated.Nick
View 1 Replies
View Related
Apr 3, 2002
I am having problem creating a distributor on my sever, when i do it thru the enterprise manager it defaults to another sever's path and when i put the severs path it dosen't find it.
and when i do it thru query analzer this is what i get
sp_adddistributor @distributor = 'vivian'
,@heartbeat_interval = 10
, @password = 'grants831'
-- , @from_scripting = from_scripting
The error message that we get is,
Server: Msg 6, Level 16, State 1, Procedure sp_adddistributor, Line 147
Specified SQL server not found.
Remote logins for remote server 'repl_distributor' have been dropped.
Server dropped.
Server added.
Server network name set.
and for this it is going to another server
sp_adddistributor @distributor = '158.72.80.48'
,@heartbeat_interval = 10
, @password = 'grants831'
-- , @from_scripting = from_scripting
error message
Server: Msg 18482, Level 14, State 1, Procedure sp_adddistributor, Line 147
Could not connect to server 'GEMS' because 'vivian' is not defined as a remote server.
Remote logins for remote server 'repl_distributor' have been dropped.
Server dropped.
Server added.
Server network name set.
View 1 Replies
View Related
May 30, 2001
Completed SQL 2000 Transactional Replication from distributor/publisher to Subscriber. (with identity problem solved)
NOW wizard disallows set up subscriber to publish back to the Distributor/Publisher. "Distributor not known" message on Subscriber server when we open configure Publisher-Subscriber tool.
Any experience using this wizard to set this up would be appreciated.
View 2 Replies
View Related
Mar 8, 2007
I have 2 servers: #1 -- SQL 2005 SP1 publisher ; #2 -- SQL 2005 SP2 subscriber
originally I had #1 as pub and dist but dist but killing my CPU so I was in the process of moving the dist to #2... Got it all configured and when I tried to add #2 as a dist for #1 it fails when I get to the administrative password screen... It give me an error about how it cannot connect with the given password but under that is says linked server failed.
Since it mentioned linked server I tried to connect via the previous linked server to #2 and it failed... I cannot connect to #2 anymore from #1. I can login directly to #2 and I can use osql to connect to #2 but linked server does not work. I tried all drivers and many configurations...
Any ideas??
View 1 Replies
View Related
Apr 24, 2002
Hello, I have 3 servers sql 7 sp3, 1 editor, a distributor and an subscriber. the base on the editor is removed, how to make to remove all traces of replication on the distributor and the subscriber.
thank you. Pascal
View 1 Replies
View Related
Jul 20, 2005
Hello,I'm trying to set up transactional replication on two SQL2k Servers.Unfortunately I stuck on the following problem:I use 'Configure Publishing and Distribution Wizard' , I make one of theservers (publisher) its own distributor, then I set all the paths .Afterpressing 'Finish' button, the wizard tries to perform next step i.e.'Configuring Distributor' and I get the error:"Error 14114: '(null)' is not configured as a Distributor". Does anyone haveidea what I should do in order to solve the problem?I tried to run procedures manually, and I get exactly the same error when Itry to execute sp_adddistributondbThanks,Piotrek
View 1 Replies
View Related
Sep 14, 2007
What is the minimum SQL Server version I can use on my replication distributor server? My publisher and subscriber(s) will all be Enterprise Edition (64 bit). However, it seems awefully wasteful to put Enterprise Edition on a box that is just used for distribution. That's another $15K for a server that doesn't do much. Can I use a lower version (Express, Developer, Standard)?
Thank you,
Ben Wolf
View 3 Replies
View Related
Jan 24, 2007
Sorry for the odd format but that is what happens when you paste here! This is data from our Job History for a "Replication Distributor" Job Step Type. Here is how I interprete it: The job step started on the 19th. It restarted itself twice on the 20th. Then it restarted itself twice on the 21st. Then it restarted itself 3 times on the 22nd. And finally it restarted itself on the 23rd. Notice the progression of Retries_Attempted. When Retries_Attempted exceeds 10, the step will fail and the service will shut-down, which is what I have seen in the past. I conclude the Advanced Settings of Retry Attempts is not per "Event" but "total tries no matter how many successful retries are encountered." I thought a successful retry would reset the Retries_Attempted. But it does not. Is this correct? This implies that to keep the distributor up, we should set the Retry Attempts" setting to its max!
Status Run_Date Run_Time Run_Duration Retries_attempted
1
1/19/2007
44025
0
0
2
1/20/2007
31200
1429
1
2
1/20/2007
32729
234250
2
2
1/21/2007
31119
1558
3
2
1/21/2007
32817
234225
4
2
1/22/2007
31142
1513
5
2
1/22/2007
32755
508
6
2
1/22/2007
33403
233615
7
2
1/23/2007
31118
1503
8
2
1/23/2007
32721
501
9
View 1 Replies
View Related
Jul 16, 2015
I am setting up transaction replication in SQL Server 2012 with three individual servers for Distributor, Publisher, Subscriber, But I want to know how to set the folder for Snapshot agent like whether the folder should be a network shared folder or normal local folder.
View 4 Replies
View Related
Aug 25, 2004
What happens when Network Connectivity between Distributor & Subscriber
fails in Transactional Replication ??
Thanks,
John
View 2 Replies
View Related
Dec 4, 2004
We have a setup with one Publisher Server and 15 Subscribers with merge replication configured for all subscribers. The current Database size is approximately 3 GB expected to grow to 10 GB in next 1 year. We wanted to know what benefits would we incur if we add an additional seperate distributor server (hardware box). Also, what is the approx. size of a database where a seperate distributor server (hardware box) is recommended.
Thanks in advance
View 4 Replies
View Related
Mar 15, 2004
What I would like to do is set up transactional replication from server1 (Publisher) to server2 (Subscriber), with server2 acting as the (Distributor).
I am successful on server2 in allowing server2 as a distributor for server1. When I try to configure replication on server1 to use server2 as a distributor and subscriber I get this message once
"
SQL Server Enterprise Manager could not enable 'server2' as a Subscriber.
Error 14071: Could not find the Distributor or the distribution database fom the local server. The Distributor may not be installed, or the local server may not be configured as a Publisher at the Distributor.
"
and this mesage for each database I enable for subscription, I get this message.
"
SQL Server Enterprise Manager could not enable database 'x' for snapshot or transactional replications.
Error 20028: The Distributor has not been correctly installed. Could not enable database for publishing. The replication 'publish' of database 'x' has been set to false.
"
The last message I get is
"
SQL Server Enterprise Manager successfully enabled 'server2' as the Distributor for 'server1'.
"
This message is apparently false.
When I try to Configure Publishing, Subscribers and Distributing... on server1, I get the message
"
SQL Server Enterprise Manager could not retrieve information about the Distributor or the distribution database.
"
In an attempt to fix this I:
1. disable publishing on server1,
2. disable publising and distribution on server2.
3. enable publishing and distribution on server2.
4. enable publishing on server1 using server2 as distributor.
Again I get errors on step 4.
I have even tried re-installing SQL Server 2000 on server2 with no improvement.
Can some one please shed some light on this problem?
Thanks in advance.
View 2 Replies
View Related
Jul 22, 2015
We have inherited a remote distribution db where the password has been lost. I would like to confirm that if you change the password in the distributor properties-->publishers--> administrative link password that the password will be changed on all publishers without having to resnap the publications?
View 3 Replies
View Related
Jul 31, 2015
We are going away from a 2003 Windows Server OS with SQL Server 2008 R2 to a 2012 Windows Server with 2012 SQL Server. Both the distributor and subscriber resides on 2003 Windows Server and the focus will be to migrate those databases to the 2012 SQL Server.
We would also like to avoid sending down a new snapshot due to logic in the replication process (major headache to clean up data). what's the best approach in moving the distributor and subscriber databases without having to run a snapshot?
In theory and needs testing:
1. Work with business users to get downtime
2. Stop sql apply so no new changes are going to the Oracle publisher database
3. Remove subscription, publication and distributor from current replication
4. Oracle DBA to clear out replication related objects - fresh clean slate
5. Use log shipping to apply last t-log and restore db with Keep_Replication
6. Set up new distribution, publication (keep existing object unchanged), and subscriber (without initialization) Will this work?
View 3 Replies
View Related
Jun 26, 2007
Hello,
Are there any requirements that dictate the SQL Server version for the distribution agent for a SQL 2000 publisher with a transactional push subscription to a SQL 2005 subscriber?
Thanks in advance,
John
View 3 Replies
View Related
Jul 17, 2007
Hello
I have server "123456" SQL 2005 On clustered environment. I added permissions to snapshot folder, it is on sharing for both nodes.
I got error during the set up as:
Microsoft.SqlServer.ConnectionInfo
Additional Information:
An exception occurred while executing a TSQL or Batch(
Microsoft.SqlServer.ConnectionInfo)
An error occurred during the execution of xp_cmdshell. A call to "Create Process" failed with error code 5
Destination path d:Microsoft SQL ServerMSSQL.1MSSQLData is not Valid. Unable to list directory contents. Specify a valid destination path
Changed database context to 'master' (Microsoft SQL Server, Error 15121)
The datafolder exists, sql cluster service account from domain added in to snapshot folder, administrators access also on this folder.
Please advice how to troubleshoot this issues. Thanks, Jay
View 1 Replies
View Related
Jul 23, 2005
I'm experiencing some very odd behavior in Enterprise Manager.I have a process that performs the following:1.) Restores a published database from Server A onto Server B. Thedatabasesare identical and they are both published.2.) I run a script that then deletes the subscriptions to thepublication onServer B. I do this via SP_DROPSUBSCRIPTION.3.) I run a script that then deletes the publication. I do this viaSP_DROPPUBLICATION.4.) Deletes the distribution database.5.) Deletes the old jobs.6.) Creates the publication from pregenerated scripts.7.) Adds the subscriber.8.) Adds the subscription.9.) Generates the snapshot and applies it.What's happening is that I'm seeing the job name that's assigned to thedistribution job increment by 1 each time this process is run. Also,I'mseeing ten instances of the publication showing up in the tree view.Everything appears to be rtunning just fine, transactions beingreplicated,etc. I'm just wondering is there something I'm missing in my steps.Plus,after two or three months of this, might not look so good having 90publications showing up in the tree view.Thanks!
View 1 Replies
View Related
May 30, 2007
There seems to be a problem with the replication monitor correctly telling you the progress of applying database schema.
Here is my setup:
Running SQL 2005 SP2. Publishing with merge replication (push) via a VPN. Approx 100 tables with lots of filtering, using data partitions filtered on host_name()
When you create and initialize a new subscription if you go to the Replication Monitor and open the Sync History window for that new subscription. You will see that it is setting up the schema in the subscriber but it does not update the status at the bottom of the window it just continually says:
Applying Database Schema - 0% complete (approzimately 00:00:00 remaining)
If it helps you can see an image of this below you will notice that it is already 15 minutes into a process that will probibly take 2 hours but it still says 0% complete.
If you require any further info or have any suggestions as to why this is not a bug (just me being dumb) please let me know.
You can see an image of this problem here: https://applications.ccusa.com/2/images/snychistory.jpg
Thanks In Advance.
Martin
View 1 Replies
View Related
Jun 3, 2004
I have to write a little vb6 app to monitor sql 2000 replication. The app must run on the same desktop as the subscriber.
I've tried the samples that comes with sql (replsampl) but that is to do the replication, I need to just monitor replication that was set up in sql 2000.
With monitor I mean to show a red light when replication is busy, so that the user doesn't disconnect from the network while replication is in progress.
Any ideas?
View 1 Replies
View Related
Aug 16, 2006
I have developed a smart device application using SqlServerCE that replicates data to the backend server. I need to provide to the user a status of this replication process. I read about the "MergeSubscriberMonitor" in SQL Server but can't find it in SqlServerCe. Is this possible? Can someone please point me in the right direction?
View 6 Replies
View Related
Aug 25, 2006
Hello,
We have some mobile devices that are setup to replicate with our sql 2005 server via web sync. It seems that the devices are added multiple times within replication monitor. Is there a way to purge the bogus items. For example we have a mobile unit labeled as Device12 we have it listed under the subscriptions 5x. I would like to purge four of them as they are not currently being the replicated one.
Device12-A6EE69A0944 is the valid subscription
Device12-EE44D1EF3E24 is an invalid one.
Thanks in advance.
John
View 1 Replies
View Related
May 8, 2006
When Replication monitor shows an error icon, I removed all the publication jobs completedly. After I reconfigured publishing, subscriber,Distribution, why the replication monitor still shows an error icon even though there is no replication job scheduled?
Thank you!
View 3 Replies
View Related
