Re: Snapshot or merge replcation propagation problem
- From: "Bernard Borsu" <bernard.borsu@xxxxxxxxxxxx>
- Date: Wed, 18 Jul 2007 11:53:24 +0200
It's already done. I use sa user account to connect to the subscriber.
The problem is always the same. Is it possible ISA Server stopped the
connection in one direction ? Which ports is used for a replication ?
"Hilary Cotter" <hilary.cotter@xxxxxxxxx> a écrit dans le message de news:
OrI8hwFyHHA.5276@xxxxxxxxxxxxxxxxxxxxxxx
Your publisher is unable to connect to your subscriber. Edit your
distribution agent and add a sql account which has dbo rights in the
subscription database.
It would look this this
-SubscriberSecurityMode -0 -SubscriberLogin
MySubscriberdboaccount -SubscriberPassword MySubscriberdbopassword
In SQL 2000 to make this change expand the replication folder, expand the
merge agents folder, locate your merge agent, right click on it select
agent properties, click on steps, click on Run Agent, click on Edit, and
at the end of the commands which appear in the text box hit space and then
paste in the above commands, click on Apply, Apply, right click on your
agent and restart it.
In SQL 2005 to make this change, connect to your publisher, expand the
replication folder, expand your publication, right click on the
subscription, select properties, and in the subscriber connection, click
on the three ellipses and select the SQL Authentication radio button and
enter the subscriber account that you wish to use and its password.
--
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Bernard Borsu" <bernard.borsu@xxxxxxxxxxxx> wrote in message
news:u2ePfGVxHHA.5068@xxxxxxxxxxxxxxxxxxxxxxx
Here is the log file
"Hilary Cotter" <hilary.cotter@xxxxxxxxx> a écrit dans le message de
news: %239qQXCUxHHA.736@xxxxxxxxxxxxxxxxxxxxxxx
Can you enable logging as per this kb article?
http://support.microsoft.com/kb/312292
--
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Bernard Borsu" <bernard.borsu@xxxxxxxxxxxx> wrote in message
news:u4H6xJTxHHA.1168@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for response.
I omit something. We have installed a ISA server between the 2 SQL
Servers. Before this installation, everything was fine. So, the
communication could perhaps be possible only in one direction. Which
tcp
or udp port is required for this kind of communicate ?
Here is the first item in the SQL log when I start the replication :
Date 13/07/2007 11:35:37
Log SQL Server (Current - 13/07/2007 5:01:00)
Source spid79
Message
Error: 14151, Severity: 18, State: 1.
Here is the second item :
Date 13/07/2007 11:35:37
Log SQL Server (Current - 13/07/2007 5:01:00)
Source spid79
Message
Replication-Replication Merge Subsystem: agent
SERVEUR2003\SERVEUR20-Enaos-TREnaos-T03-25 failed. The process could
not
connect to Subscriber 'T03'.
"Hilary Cotter" <hilary.cotter@xxxxxxxxx> a écrit dans le message de
news:
eLzVaXGxHHA.1164@xxxxxxxxxxxxxxxxxxxxxxx
Can you enable logging to see exactly where this is failing?
Another option is to set logintimeout to 300, in case this is the
problem. It also could be an authentication problem between the two
servers - check the accounts that your merge agent is connecting to
the
subscriber with. It should be in the pal in the publisher, dbo_role in
the distribution database, and dbo_role in the subscription database.
--
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Bernard Borsu" <bernard.borsu@xxxxxxxxxxxx> wrote in message
news:OZZmhwCxHHA.2432@xxxxxxxxxxxxxxxxxxxxxxx
Hi !
Each time i try to synchronis a snapshot replcation or a merge
replication, i receive these errors messages.
Error messages:
The process could not connect to Subscriber 'T03'. (Source:
MSSQL_REPL,
Error number: MSSQL_REPL0)
Get help: http://help/MSSQL_REPL0
TCP Provider: Une tentative de connexion a échoué car le parti
connecté
n'a pas répondu convenablement au-delà d'une certaine durée ou une
connexion établie a échoué car l'hôte de connexion n'a pas répondu.
(Source: MSSQLServer, Error number: 10060)
Get help: http://help/10060
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. (Source: MSSQLServer, Error number: 10060)
Get help: http://help/10060
Login timeout expired (Source: MSSQLServer, Error number: HYT00)
Get help: http://help/HYT00
I can't understand these problems because I start this
synchronisation
on the T03 windows 2003 server, which is the server the replication
can't connect to. T03 is connected to Serveur2003 through VPN
connection. In the SQL manager, i have no problem working on T03 or
Serveur 2003. I Have another merge replication whose working well
from
T03 to Serveur 2003 through the VPN. So, Why a merge replication from
Serveur2003 to T03 can't operate ?
--
Bernard
bernard.borsu@xxxxxxxxxxxx
.
- References:
- Snapshot or merge replcation propagation problem
- From: Bernard Borsu
- Re: Snapshot or merge replcation propagation problem
- From: Hilary Cotter
- Re: Snapshot or merge replcation propagation problem
- From: Bernard Borsu
- Re: Snapshot or merge replcation propagation problem
- From: Hilary Cotter
- Re: Snapshot or merge replcation propagation problem
- From: Bernard Borsu
- Re: Snapshot or merge replcation propagation problem
- From: Hilary Cotter
- Snapshot or merge replcation propagation problem
- Prev by Date: Re: Help please: wrong syntax near ...
- Next by Date: RE: Error 50007: xp_execresultset: unable to get a bound connection back to server
- Previous by thread: Re: Snapshot or merge replcation propagation problem
- Next by thread: Re: Disaster recovery in multiple publishers environment
- Index(es):