all groups > sql server replication > july 2007 >
You're in the

sql server replication

group:

Replication trouble between distant office ????


Replication trouble between distant office ???? calderara
7/5/2007 12:54:02 PM
sql server replication:
Dear all,

I am trying to set up a replication SQL server between 2 work office
connected over private lan. Both office use SQL server 2005.
Replication internal to each office works fine but when I try to setup
replication between connection to server fails.

After creating what to publish, I define a new subscriber from the publisher
which is also the distributor, then at the time to Add a new subscriber, I
need to enter the server name and authentication. From that office I am only
able to ping my server using IP adress or using the complete name as
<myServerName>.Mu1.grp

When doing so, I get an eror mesage saying that I cannot use IP adress,
alias for replication and connection fail of course. I then try to define an
Alias under SQL configuration , then I get an other eror saying that my
remote seerver refuse connection or is not access remote. Which is wrong
becasu it acept it.

IF I try to connect to my remote server using ODBC or osql utility, then I
connect without trouble. I am uisng TCP with default listen port 1433


What could be the problem that I can't set up the subsription ?

thnaks for help
regard
Re: Replication trouble between distant office ???? Paul Ibison
7/5/2007 10:18:01 PM
Here is an article that might help: http://support.microsoft.com/kb/328306
Silly question, but when you set up the alias, are you also using TCP/IP,
port 1433 like with the successful OSQL access?
Cheers,
Paul Ibison

Re: Replication trouble between distant office ???? calderara
7/5/2007 11:20:02 PM
Yes when I use the alias from the publisher site, I use same tcp port
Thats 's really strange..

I can not understand the difference between the fact of accessing it without
any trouble by using ODBC and not from Replication setup !!!

Any idea?

serge

[quoted text, click to view]
Re: Replication trouble between distant office ???? Paul Ibison
7/6/2007 1:20:03 AM
So does the alias work on its own, outside of the replication setup? You can
test this by connecting with the query designer or SSMS. Also, when you use
the alias and it fails, please can you post up the exact error message here.
Thanks,
Paul Ibison
Re: Replication trouble between distant office ???? calderara
7/6/2007 4:48:00 AM
hi paul.
Just to be sure that I have made things corrrcetly.
From Office A ( the publisherA ) to Office B (The subscriberB), I can ping
the server in office B from Office A by using either Ip adrress or the full
name as <Servername>.DomaineName. So for me it will be nomos-srvr.mu1.grp

If I use ither Ip adress or full name as server name from ODBC DSn setup, it
works all ok.

Then I was testing connection from Office A using the utility osql, works
all ok too

From New Subscription setup from SQL server 2005 of OfficeA , at the time I
Add a new subscriber, If I enter as Server name or IP adress in the form :

nomos-srvr.mu1.grp or Ip
--> error message saying :
"SQL server replication requires the actual server name to make a
connection to the server. Connections trhrough a server alias, ip adress, or
any other alternate name are not supported. Specify the actual server name
(Replication Utilities)"

Then on Publisher SQl server configuration manager I add an Alias with
entries:
- Alias Name : MyServer
- Tcp : 1433
- Server: nomos-srvr-mu1.grp ( or Ip adress)

Then I Add new subscriber from the previous setup of new subscription and
this time as a server name I enter myServer ( Aliasname)
----> Same error as before.
"SQL server replication requires the actual server name to make a
connection to the server. Connections trhrough a server alias, ip adress, or
any other alternate name are not supported. Specify the actual server name
(Replication Utilities)"


Then I add "\\" before the name of the server and I get an other error saying:

---->>>
Cannot connect to ECUSERVER.

------------------------------
ADDITIONAL INFORMATION:

Failed to connect to server ECUSERVER. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

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.(provider: SQL Network Interfaces, error: 25 - Connection string
is not valid)
Microsoft SQL Server, Error: 87)
<<<--------


What do you mean by testing the alias with Querry designer or SSMS ?

serge



[quoted text, click to view]
Re: Replication trouble between distant office ???? calderara
7/6/2007 5:14:01 AM
Some more information...
If from the publisher side I am clicking on the "new Query" , I am prompt
the server login. If I place as server name the ALIAS name that I define, I
get same error as in my previous message.

If I place my full computer name as : nomos-srvr.mu1.grp, I am able to
connect to my server and build a new querry. If I use this same name for
replication subscription setup, it fails...

I start to loose my hairs
serge

[quoted text, click to view]
Re: Replication trouble between distant office ???? Paul Ibison
7/6/2007 6:50:02 AM
OK - have a look here for the remote connections configuration:
http://support.microsoft.com/kb/914277
Can you also go to the subscriber, configure a TCP/IP alias there to the
publisher then set up a pull subscription there to the publication. Here are
more details: http://www.replicationanswers.com/InternetArticle.asp
HTH,
Paul Ibison
Re: Replication trouble between distant office ???? calderara
7/11/2007 3:06:02 AM
Hi paul,

Thnaks fro your links, I manage to get it working now.
I made different msitakes according to document link you send.

First of all in Alias name if I place as alias a string which is different
as the reel server name then it fails. my physical server name was NOMOS-SRVR
and as an Alias on the publisher side I was giving alias name myServer.

Second I was not defining any alias from subscriber side, but it seems it is
needed
Third, but not sure, SQl browser was not started from both side. is it
needed if I use standard tcp port 1433 ?

Could you light my light about this Alias naming, i am correct ?
That was the reason it fails I guess

regards
serge
[quoted text, click to view]
Re: Replication trouble between distant office ???? Paul Ibison
7/12/2007 1:26:01 AM
Yes - the alias problem is one I have seen before - the names need to be
identical. Pleased the article helped.
Cheers,
Paul Ibison
AddThis Social Bookmark Button