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
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
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
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.
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.
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
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
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)?
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?!
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.
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.
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?
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?
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?
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?
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.
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)
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.
We are using a SQL Server 2000 Replication. I'm using the Merge Agent History Screen to retrive Informacion about replication sessions, is there any other screen to know exaclty which datawas replicated on each session?Or at least to know the script generated on each session?
I have a setup where I need to replicate the database which is actually subscribing from another database. The current setup is all in SQL Server 2000. I need to now setup a Distrbutor on a SQL server 2005 and publish the database using this distributor to another server on SQL server 2000.
Has anybody done this before. If yes what will I need to check. Can you please let me know :-
1) SQL Server 2000 which SP should be installed to support this enviroment.
2) SQL Server 2005 which SP should be installed to support this environment.
After extensive testing I have found that bcp's run almost twice as fast on my dedicated Distributor than on either the Publisher or Subscriber. I was wondering if there is a way to make the bcp's spawned by creating a Snapshot run on the distributor and not the Publisher.
For remote distributor (transactional replication,distribution database 50GB, 3 day retention), what is the most critical resource except disk ? Is it CPU intensive ? does it use lots of memory (i.e. would 4GB be enough) ?
I'm having a problem configuring one of my SQL servers as a distributor. I've done it successfully on another server, so I know that it's nothing procedural and there must be an issue with the way the server is set up. When I click 'finish' on the Configure Publication and Distribution Wizard, I get the following error message:
Enterprise Manager could not configure 'ABEL' as the distributor for 'ABEL'.
Error 20017: Cannot add the remote distributor at this time. Make sure that the local server is configured as a Distribution Publisher at the Distributor.
Can anyone point me in the right direction? I'm fairly new to SQL Server, so feel free to explain things in a condescending manner. ;-)
I'm reading the MS online docs about replication. there's something not so clear until so far.
I have one central server and 7 client servers. Sometimes new data is entered at one client server. This should be replicated (when client comes online) to the Central Server (merge replication).
Also, the other way, once the central server gets new data (that was replicated from a client), it should be again replicated to all 6 other clients (from the central server).
now, who should i configure as the distributor, publisher and subscriber?
Hi this is SQL 2000 but I couldn't see a forum for SQL 2000 replication.
I have set up merge replication. Between a server and an msde laptop.
The sync works fine within the network but when the user goes home and vpn's into the network and tries to replicate they get an error message that says:
"...server is not configured as a distributor" I find this strange because the replication definitely works within the network.
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.
I am trying to "Configure Distributor" prior to setting up the publications. When I go through the wizard, at the very last step I get the following error:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
Cannot find the principal 'sa', because it does not exist or you do not have permission. 'distribution' is not configured as a distribution database. Changed database context to 'master'. (Microsoft SQL Server, Error: 15151)
