Not able to connect to Remote Distributor from Publisher using Administrative Link Password

January 28, 2008, 9:45 pm

≫ Next: Distribution Agent Running Slow or Not at All

≪ Previous: SQL2014 Transactional replication for Availability Group (Named Instance)

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.

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=Microsoft.SqlServer.Management.UI.ReplUtilitiesErrorSR&EvtID=CantConnectAdminPassword&LinkId=20476

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

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

------------------------------
BUTTONS:

OK
------------------------------

↧

Distribution Agent Running Slow or Not at All

October 13, 2015, 4:14 am

≫ Next: Merge Replication : Failing to create subscription for one node but working for other nodes.

≪ Previous: Not able to connect to Remote Distributor from Publisher using Administrative Link Password

Last week, I ran into a situation where one of my subscribers started running really-really slow.

We have two SQL Server instances (Server-1 and Server-2). Server-1 hosts a high volume database (Pub) with multiple publications. Server-2 hosts a reporting database (Sub), which subscribes to the publications from database Pub. The publication uses a remote distributor. Server-1 is a part of an AG group (1). Server-2 is a part of a separate AG group (2). For those not familiar with replication and AG, don't get distracted by the AG's. Here is a quick snapshot:

Server-1 (in AG 1)
|-Database-Pub
   |-Publication-1
   |-Publication-2
   |-Publication-3

Server-2 (in AG 2)
|-Database-Sub
   |-Subscription to Publication 1 (Push)
   |-Subscription to Publication 2 (Push)
   |-Subscription to Publication 3 (Push)

Server-3
|-Database-Distributor

Last week, I ran into a situation where publication #2 began running really-really slow. We engaged support services, but they weren't sure what was happening either. To help troubleshoot the issue, I broke publication 2 into smaller publications. My hope was to find the article that was the root of my problem. Today, we found that one of the new publications (one of the guys formed from publication #2) was really-really slow. The publication contained one big table. For some reason, this bastard just won't update.

Some additional information about the issue:

No errors in the error log on the publisher's instance
No errors in the error log on the subscriber's instance
In a healthy distributor, you'll see "# transaction(s) with # command(s) were delivered" on the "Distributor to Subscriber History" tab. Right now all I see is "Delivering replicated transactions".
Distributor of interest is using the default profile
No error appears in distributor agent's job history
No error appears in log reader agent's job history
All other subscriptions in this database and on this instance appear healthy and current
This issue was not preceded by a code change
Publsher database sits on a SQL Server 2014 Enterprise 64-bit SP1 instance
Subscriber database sits on a SQL Server 2014 Enterprise 64-bit SP1 instance
Distributor database sits on a SQL Server 2014 Standard 64-bit SP1 instance
The distributor database and machine do not appear to be under any resource pressure
We have re-indexing and statistics update jobs on the subscriber
The subscribing article is indexed differently that the publisher

Any suggestions are appreciated.

Adam

↧

Merge Replication : Failing to create subscription for one node but working for other nodes.

October 12, 2015, 9:34 am

≫ Next: Syncing of database from local host database to online database automatically after some interval

≪ Previous: Distribution Agent Running Slow or Not at All

Hi All,

Merge replication fails on one node with error :

Error messages:
The merge process could not update the list of subscriptions. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201010)
Cannot insert duplicate key row in object 'dbo.sysmergepublications' with unique index 'nc1sysmergepublications'. The duplicate key value is . (Source: MSSQLServer, Error number: 2601)
The subscription could not be created. (Source: MSSQLServer, Error number: 14057)

works fine on other subscribers.

--Hunt

↧

Syncing of database from local host database to online database automatically after some interval

October 13, 2015, 11:33 pm

≫ Next: replicating data from sql server to hadoop

≪ Previous: Merge Replication : Failing to create subscription for one node but working for other nodes.

I have database on localhost and i want to show this data on my website. I want to create a database online and want to sync with Local Host. Can it be possible syncing data automatically after some interval? (I am .NET developer)

↧

replicating data from sql server to hadoop

October 14, 2015, 7:14 pm

≫ Next: Remove Seondary available replica from SQL 2012

≪ Previous: Syncing of database from local host database to online database automatically after some interval

hi all,

we have our transnational data in sql server but we keep our analytical data in hadoop.

1. is there anything built in sql server to replicate data to hadoop ?

2. can following connector ("SQL Server-Hadoop Connector") be used for this ? with this connector , can sql server push data (similar to replication) or hadoop has to periodically pull data ?

http://www.microsoft.com/en-us/download/details.aspx?id=27584

thanks

siddharth

↧

Remove Seondary available replica from SQL 2012

October 14, 2015, 4:13 pm

≫ Next: multiple publishers and one subscriber setup

≪ Previous: replicating data from sql server to hadoop

Environment:-

Windows 2012 R2,

SQL 2012 (Primary Replica)

SQL 2012 (Seondary Replica)

SQL 2012 (Secondary Replica over WAN site)

There are database replicating on three SQL servers. WAN line is having performance issue because of limited bandwidth

I have to remove SQL secondary replica over WAN site temporarily and add it again later when the WAN line is upgraded with between bandwidth

What is the best practice to remove secondary replica and replicating database and add later from SQL management studio without interruptions on databases please?

Muhammad Mehdi

↧

multiple publishers and one subscriber setup

October 15, 2015, 8:33 am

≫ Next: Queue Reader Agent - Login failed for user...

≪ Previous: Remove Seondary available replica from SQL 2012

Hello,

Is it possible to replicate data from 3 publishers to a single/central subscriber transactionally? In other words I have Server A, Server B, Server C with databases A,B,C respectively. I need to replicate 2 articles from A,2 from B and 2 from C to a central Server D that hosts database D. D will have only 6 articles. The replication is Transactional Replication.

If it is possible what will be the drawbacks of such implementation? (if one server goes down will the whole replication break?) If not possible then what is the best way of implementing this?

Thanks

↧

Queue Reader Agent - Login failed for user...

October 15, 2015, 8:51 am

≫ Next: spAddMergeSubscription fails with subscription already exists

≪ Previous: multiple publishers and one subscriber setup

Hi,

So on sql server 2012, trying to setup updatable transactional replication (I know next versions won't have it). After going through DTC configuration, opening the firewall ports, etc... I get the following error:

The Queue Reader Agent has encountered the error ''Login failed for user ''Domain\User''.'' when connecting to ''DB'' on ''REMOTE DB SERVER''. Ensure that the publication and subscription are defined properly and that both servers are running.

The domain\user that is used is the sql agent user. And that user does not have access to the database on the remote server. Where do I change the user used to login to the remote server ? Or do I need to give access to the sql agent user to the remote database ?

Thanks

Olivier

↧

spAddMergeSubscription fails with subscription already exists

November 12, 2013, 2:20 am

≫ Next: Msg 18752, Level 16, State 1, Procedure sp_repldone, Line 1 Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds)

≪ Previous: Queue Reader Agent - Login failed for user...

When executing sp_addMergeSubscription it fails with the error

    exec sp_addmergesubscription @publication = 'ArizonaCASH_Pub'
	    , @subscriber = 'BALE-S1'
	    , @subscriber_db = 'ArizonaCASH'
	    , @subscription_type = N'Push'
	    , @sync_type = N'None'
	    , @subscriber_type = N'local'
	    , @subscription_priority = 75
	    , @description = null
	    , @use_interactive_resolver = N'False'
	    , @hostname = 'some_guid'
	    ;

Msg 14058, Level 16, State 1, Procedure sp_addmergesubscription, Line 381
Cannot create the subscription because the subscription already exists in the subscription database. Only one subscription to the same publication is allowed in each subscription database. Drop the subscription and add it again if necessary. If the problem persists, replication metadata might be incorrect; see Books Online for troubleshooting information.

Tried to run sp_dropmergesubscription with the proper parameters (tried ignoredistributor = 1 ), it completes instantly without error.

exec dbo.sp_dropmergesubscription
	  @publication = 'ArizonaCASH_Pub'
	, @subscriber = 'BALE-S1'
	, @subscriber_db = 'ArizonaCASH'
	, @subscription_type = 'All'
	, @ignore_distributor = 1

At the subscriber I already ran sp_removeDbReplication in the subscriber database, there appear to be no replication objects left there. A select from sysobjects returns nothing like msmerge%

At the publisher, the failed attempt at sp_addMergeSubscription appears to write lines in sysmergesubscriptions (for this subscriber). I removed those lines manually and retried to add the subscription with the same result.

Any ideas why this is happenning ? This is a prod box, of course none of this garbage ever happenned in test :(

The ultimate solution for me would be to drop all subscribers, nuke the publication, recreate it and re-add all the subscribers. I know there is powershell for that but if it can be avoided...

Forgot to mention both publisher and subscriber are 2008R2, Enterprise for the Publisher, Workgroup for the subscriber.

↧

Msg 18752, Level 16, State 1, Procedure sp_repldone, Line 1 Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds)

October 16, 2015, 10:49 am

≫ Next: MSRepl_Commands table is huge - 456Gb

≪ Previous: spAddMergeSubscription fails with subscription already exists

I have configured database mirroring and replication, the log file not getting shrink ,so i try to reduce log many ways but could not reduce the log size , I use the following script

EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1

Once i excute i truncate the log file using DBCC SHRINK FILE

after that i start the Log reader It shows

Error messages:
The process could not execute 'sp_repldone/sp_replcounters' on 'HDB'.
(Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help: http://help/MSSQL_REPL20011
Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds)
can connect to a database at a time.
If you executed a log-related procedure, drop the connection over which the procedure was executed
or execute sp_replflush over that connection before starting the Log Reader Agent or
executing another log-related procedure. (Source: MSSQLServer, Error number: 18752)
Get help: http://help/18752
The process could not set the last distributed transaction. (Source: MSSQL_REPL, Error number: MSSQL_REPL22017)
Get help: http://help/MSSQL_REPL22017
The process could not execute 'sp_repldone/sp_replcounters' on 'HDB'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)

Please help me to solve the problem

when i try to remove replication and decide to configure new replication ,the following error i received,

Please help me ,I am using SQL server 2012

Msg 18752, Level 16, State 1, Procedure sp_repldone, Line 1Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds)
can connect to a database at a time. If you executed a log-related procedure,
drop the connection over which the procedure was
executed or execute sp_replflush over that connection before
starting the Log Reader Agent or executing another log-related procedure.

Thanks & Regards Manoj

↧

MSRepl_Commands table is huge - 456Gb

October 25, 2011, 3:48 am

≫ Next: SQL Server 2012 Error 3989 Message: New request is not allowed to start because it should come with valid transaction descriptor.

≪ Previous: Msg 18752, Level 16, State 1, Procedure sp_repldone, Line 1 Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds)

I have a "MSRepl_Commands" table which has grown up to 456Gb in size. It keeps growing everyday. Can someone help me finding a fix or remedy to purge this table, please?

Work done so far:

Updated the sys.publications to set immediate_sync & allow_anonymous properties to FALSE and also set theSubscriptions Expire retention to48hrs.

Ensured that the delete procs "sp_MSdelete_publisherdb_trans" and "sp_MSdelete_dodelete" are altered as ‘Delete Top 100000’.
Ensured that the "Distribution cleanup" and "Agent history cleanup" jobs are running properly.

Any assistance and / guidance here is highly solicited and will be appreciated.

↧

SQL Server 2012 Error 3989 Message: New request is not allowed to start because it should come with valid transaction descriptor.

October 18, 2015, 10:27 am

≫ Next: Replication Over Internet without VPN

≪ Previous: MSRepl_Commands table is huge - 456Gb

As it is always when it comes to replication, the circular problems and suposedly resolved in previous versions rear their head again and again. The title issue was supposedly resolved in SQL server 2005 and 2008. Yet it is again an issue in 2012, there was some indication that it was resolved in SP2, SQL 2012. Yet, it continues to be an issue even after applying the update. The even bigger problem is that the error is so generic that there is not even a place to start troubleshooting. Leave it to Microsoft!!! Maybe a support call will give me an answer. In the mean time, is there anybody out there that can give me a hint on where to start trouble shooting this issue?

↧

Replication Over Internet without VPN

October 20, 2015, 2:01 am

≫ Next: Error while synchronizing data with Head Office server

≪ Previous: SQL Server 2012 Error 3989 Message: New request is not allowed to start because it should come with valid transaction descriptor.

Hello Experts,

I want to setup transactional replication over the internet and WITHOUT VPN. I think it is possible, but i'm worried about security of data when it travels through internet.

I heard data security can be achieved by using encrypted connection.

Please let me know how can I achieve this and is there any step-by-step guide on the pre-requisite and how to setup replication without VPN.

Thank you !!!

Malkesh Sheth

↧

Error while synchronizing data with Head Office server

October 19, 2015, 12:48 am

≫ Next: The Merge Agent could not connect to the URL during Web synchronization

≪ Previous: Replication Over Internet without VPN

Execute at Shop: Exception Type:System.Data.SqlClient.SqlException Error! Please Contact Lumensoft Technologies Pvt.Ltd.Error Detail:Tale'tblPhysicalInventoryItems' does not have the identity property,cannot perform SET Operation.Statment Ref: Seq No[792961],Statment ID [371916]

Transfered to HO:Succesfully;

↧

The Merge Agent could not connect to the URL during Web synchronization

September 19, 2008, 10:24 pm

≫ Next: SQL Server 2012 - Updateable transac replication - failing on first command

≪ Previous: Error while synchronizing data with Head Office server

This error when I try to syncrhonize using Windows Sync Manger:

The Merge Agent could not connect to the URL https://mywebserver/Sync_Test/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable.

I tried accessing the dll on a browser and it shows a 'Security Alert' saying that

"The security certificate was issued by a company you have not chosen to trust. View the certificate to determine whether you want to trust the certifying authority."

I just proceeded with the alert and then a login window appears and I provided username/password credentials and the dll shows successfully. I think it has something to do with the certificate I used but I do no what...

I installed Windows Server 2003 CA then made a request using IIS > Default WebSite > Properties > Directory Security > Server Certificate > Complete the request wizard.

I submit the new request using Administrative Tools > Certification Authority > CA Server > All Tasks > Submit new request

I issued the pending request using Administrative Tools > Certification Authority > Pending Requests > All Tasks > Issue.

I checked on the Issued Certificates and it is there. I returned to IIS > Default WebSite > Properties > Directory Security > Server Certificate > Process the pending request and install certificate > Finish the wizard.

Here's the setup:
Publisher/Distributor - Windows Server 2003 SP1, IIS 6.0, SQL Server 2005 Enterprise, Stand-Alone CA
Subscriber - XP SP2, SQL Server 2005 Express

Any tip is very much appreciated.. Thanks! Smile

↧

SQL Server 2012 - Updateable transac replication - failing on first command

October 21, 2015, 6:49 am

≫ Next: SQL Server 2012 - Updatable transactional replication - No data initialization ?

≪ Previous: The Merge Agent could not connect to the URL during Web synchronization

Hi,

So I setup an updateable transact replication between 2 SQL server 2012 servers. When I try to start using the application supported by the DB, the first command immediately fails with the error:

* Error converting data type nvarchar to int

Now when I look at the command that is failing and the table related to it, the number of parameters passed to it is not equal to the number of columns in the table and not equal to the number of parameters of the stored procedure. The identity column value is actually missing.

And since the first parameter expected by the stored procedure is an int but is actually getting an nvarchar... well it fails.

So what did I miss in the configuration of the transact replication for it to work with identity columns ?

Thanks

Edit: even worse, 2 commands calling the same SP are sending completely different sets of parameters. The first command gives 24 out of 25 params and the second call sends 14 out of 25...

↧

SQL Server 2012 - Updatable transactional replication - No data initialization ?

October 21, 2015, 10:55 am

≫ Next: subscription already deleted but still visible in sync manager

≪ Previous: SQL Server 2012 - Updateable transac replication - failing on first command

Hi,

Is it possible to configure updatable transactional replication to initialize the schemas and everything but ignore the data ?

In the current case, the transactional part of the DB is huge and contains only live data that are deleted anyway after a few weeks. If one of the DB server fails we don't really care about that live data, thus spending a huge amount of time transferring the DB backup/snapshot (or the data part of the initialization) from a site to another would take a few weeks and then we would still have to synch the delta between current and backup.

So overall, by the time the new server is in synch again, the data that was loaded initially is gone or will be soon purged.

Thus importing the data on initialization is wasted time and resources.

Thanks

↧

subscription already deleted but still visible in sync manager

September 3, 2008, 6:10 pm

≫ Next: replicate ddl setting is not working if multiple subscribers are used

≪ Previous: SQL Server 2012 - Updatable transactional replication - No data initialization ?

I have deleted a subscription from my Subscriber database but when I open the Synchronization Manager it is still there with other subcriptions though the name of the deleted subscription is "()" and when I click the button 'Properties' it won't open. Also when I run sync other subscriptions it would says sync is complete but the status is pending and data were not actually sync... I am about to unisntall the SQL Server to try it but if any tip would be very much appreciated...

Thanks...

↧

replicate ddl setting is not working if multiple subscribers are used

October 21, 2015, 5:45 pm

≫ Next: SQL Server 2012 - Updateable transactional replication - The subscription is uninitialized or unavailable for immediate updating as it is marked for reinitialization

≪ Previous: subscription already deleted but still visible in sync manager

replicate ddl setting is not working if multiple subscribers are used

Thanks

↧

SQL Server 2012 - Updateable transactional replication - The subscription is uninitialized or unavailable for immediate updating as it is marked for reinitialization

October 22, 2015, 5:18 am

≫ Next: sql server 2012 - bidirectional transactional replication - first trigger already present

≪ Previous: replicate ddl setting is not working if multiple subscribers are used

Hi,

Like a lot of people, when I try to update at the subscriber, I end up with: The subscription is uninitialized or unavailable for immediate updating as it is marked for reinitialization.

All I could find from the threads at the moment is that the Queue Reader Agent might have an expired password. Except that when I right click the agent and select properties it tells me the job does not exists...

How do I go about making that updateable transactional replication work :) ?

Thanks

Edit: At the moment this is what I have configured for the publication

exec sp_addpublication @publication = N'PUB', @description = N'Transactional publication of database ''DB'' from Publisher ''SRV''.', @sync_method = N'concurrent', @retention = 0, @allow_push = N'true', @allow_pull = N'true', @allow_anonymous = N'true', @enabled_for_internet = N'false', @snapshot_in_defaultfolder = N'true', @compress_snapshot = N'false', @ftp_port = 21, @allow_subscription_copy = N'false', @add_to_active_directory = N'false', @repl_freq = N'continuous', @status = N'active', @independent_agent = N'true', @immediate_sync = N'true', @allow_sync_tran = N'true', @allow_queued_tran = N'true', @allow_dts = N'false', @replicate_ddl = 1, @allow_initialize_from_backup = N'false', @enabled_for_p2p = N'false', @enabled_for_het_sub = N'false'
GO

↧

Latest Images