November 9, 2014 at 8:44 pm
Hi ALL,
I am creating the replicaton between 2 servers . I have created the publication in the publisher and I tried to create the subcription ( it show up in the publisher --> so when i drill down the publication , i can see the subcription
that I made but when I checked into the subcriber , I can't find the subcription in LOCAL SUBCRIPTION folder ( Under REPLICATION) in SQL management Studio .
They can connect to each other ( I tried this using PING via Command Prompt)
I hv set up the permission for REPLSNAPAGENT , REPLMERGEAGENT and REPLDIStAGENT for both Publisher and Subcriber .
I just wonder why the subcription doesnt show up in the subcriber ??
Please kindly advice
Cheers
November 14, 2014 at 6:37 am
There are a few things you can check:
- what do you see under Replication Monitor? (Right-click on your publication and select Launch Replication Monitor). Any errors or activity? Where does it say the secondary is?
- Look in the SQL Agent jobs for the replication jobs. Any error messages there?
November 16, 2014 at 11:31 pm
Beatrix Kiddo (11/14/2014)
There are a few things you can check:- what do you see under Replication Monitor? (Right-click on your publication and select Launch Replication Monitor). Any errors or activity? Where does it say the secondary is?
- Look in the SQL Agent jobs for the replication jobs. Any error messages there?
this is the error that i got after running view syncronization status
The replication agent has not logged a progress message in 15 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active.
any idea ?
November 17, 2014 at 4:32 am
Are the SQL Agent jobs doing anything?
Would you consider ditching it and starting again from scratch?
November 17, 2014 at 4:46 pm
Beatrix Kiddo (11/17/2014)
Are the SQL Agent jobs doing anything?Would you consider ditching it and starting again from scratch?
So here is the message from SQL job :
Message
2014-11-17 06:04:02.828 Copyright (c) 2008 Microsoft Corporation
2014-11-17 06:04:02.828 Microsoft SQL Server Replication Agent: replmerg
2014-11-17 06:04:02.828
2014-11-17 06:04:02.828 The timestamps prepended to the output lines are expressed in terms of UTC time.
2014-11-17 06:04:02.828 User-specified agent parameter values:
-Publisher SERVER1
-PublisherDB MYDATABASE
-Publication Pub1
-Subscriber SERVER2
-SubscriberDB MYDATABASE
-Distributor SERVER1
-DistributorSecurityMode 1
-HostName Sydney Buses
-XJOBID 0xB2B9834A51451B438F2989FD977CDA39
-XJOBNAME SERVER1-MYDATABASE-DeviceCommsMergePubli-SERVER2-25
-XSTEPID 2
-XSUBSYSTEM Merge
-XSERVER SERVER1
-XCMDLINE 0
-XCancelEventHandle 0000000000000908
-XParentProcessHandle 0000000000000688
2014-11-17 06:04:03.085 Connecting to Distributor 'SERVER1'
2014-11-17 06:04:03.685 Initializing
2014-11-17 06:04:03.754 Connecting to Publisher 'SERVER1'
2014-11-17 06:04:28.077 The process could not connect to Subscriber 'SERVER2'.
2014-11-17 06:04:28.146 Connecting to Subscriber 'SERVER2'
2014-11-17 06:04:28.171 Category:AGENT
Source: SERVER2
Number: 20084
Message: The process could not connect to Subscriber 'SERVER2'.
2014-11-17 06:04:28.175 Category:SQLSERVER
Source: SERVER2
Number: 0
Message: Unable to complete login process due to delay in opening server connection
2014-11-17 06:04:28.180 Category:NULL
Source: Merge Process
Number: -2147201019
Message: The subscription to publication 'Pub1' could not be verified. Ensure that all Merge Agent command line parameters are specified correctly and that the subscription is correctly configured. If the Publisher no longer has information about this subscription, drop and recreate the subscription.
2014-11-17 06:04:28.188 The merge process will restart after waiting 30 second(s)...
Connecting to Distributor 'SERVER1'
2014-11-17 06:04:58.248 Initializing
2014-11-17 06:04:58.252 Connecting to Publisher 'SERVER1'
2014-11-17 06:05:21.725 The process could not connect to Subscriber 'SERVER2'.
2014-11-17 06:05:21.738 Category:AGENT
Source: SERVER2
Number: 20084
Message: The process could not connect to Subscriber 'SERVER2'.
2014-11-17 06:05:21.739 Connecting to Subscriber 'SERVER2'
2014-11-17 06:05:21.745 Category:SQLSERVER
Source: SERVER2
Number: 0
Message: Unable to complete login process due to delay in opening server connection
2014-11-17 06:05:21.746 Category:NULL
Source: Merge Process
Number: -2147201019
Message: The subscription to publication 'Pub1' could not be verified. Ensure that all Merge Agent command line parameters are specified correctly and that the subscription is correctly configured. If the Publisher no longer has information about this subscription, drop and recreate the subscription.
I have built the new one from the scratch but no luck 🙁
November 17, 2014 at 5:13 pm
This is your problem:
2014-11-17 06:04:28.077 The process could not connect to Subscriber 'SERVER2'.
2014-11-17 06:04:28.146 Connecting to Subscriber 'SERVER2'
2014-11-17 06:04:28.171 Category:AGENT
Source: SERVER2
Number: 20084
Message: The process could not connect to Subscriber 'SERVER2'.
2014-11-17 06:04:28.175 Category:SQLSERVER
Source: SERVER2
Number: 0
Message: Unable to complete login process due to delay in opening server connection
2014-11-17 06:04:28.180 Category:NULL
Have you tried to make a SQL connection to SERVER2 from the publisher?
November 17, 2014 at 5:16 pm
You may need to change the -LoginTimeout and -QueryTimeout parameters for the MergeAgent.
You can either change the profile or modify the Merge Agent job itself.
November 17, 2014 at 5:17 pm
arnipetursson (11/17/2014)
This is your problem:2014-11-17 06:04:28.077 The process could not connect to Subscriber 'SERVER2'.
2014-11-17 06:04:28.146 Connecting to Subscriber 'SERVER2'
2014-11-17 06:04:28.171 Category:AGENT
Source: SERVER2
Number: 20084
Message: The process could not connect to Subscriber 'SERVER2'.
2014-11-17 06:04:28.175 Category:SQLSERVER
Source: SERVER2
Number: 0
Message: Unable to complete login process due to delay in opening server connection
2014-11-17 06:04:28.180 Category:NULL
Have you tried to make a SQL connection to SERVER2 from the publisher?
How do I make the SQL Connection ? What i have done is ping the Server 2 from publisher ..it has the reply
November 18, 2014 at 9:39 am
You connect to the SQL Server instance on Server2 from the publisher using the credentials that the merge agent uses via either SSMS or SQLCMD.
November 19, 2014 at 11:09 pm
arnipetursson (11/18/2014)
You connect to the SQL Server instance on Server2 from the publisher using the credentials that the merge agent uses via either SSMS or SQLCMD.
ok . .I will try
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply