Cannot connect to to the other server when setting up replication in SQL 2005

Im trying to setup replication between two 2005 standard editions. They are on the same LAN and installed equally + SP1. They are installed as named instances (with the same instance name MSSQL01). Remote access is allowed and TCP/IP and shared memory and I can connect between them.

SQL1\MSSQL01 is configured as the publisher & distributor and the snapshot is done. When Im using the subscriber wizard from SQL1 to create the subscriptions and add SQL2\MSSQL01 as a subscriber the connection fails to the remote server.

The error message is:

TITLE: Connect to Server

Cannot connect to SQL2\MSSQL01.

ADDITIONAL INFORMATION:

Failed to connect to server SQL2\MSSQL01. (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: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

When I do a manual connection to SQL2 using the server managemnet studio on SQL1 I cannot connect using the instance name e.g. SQL2\MSSQL01, it works only when only using the server name e.g. SQL2. Then I have full access both when using a windows or SQL user.

When trying with using the server name only when setting up the subscription, I got a error saying that I need to use the full name.

TITLE: Connect to Server

Cannot connect to TFMHQARNDE07.

ADDITIONAL INFORMATION:

SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, ' SQL2\MSSQL01'. (Replication.Utilities)

I can also mention that theese servers are cloned from another server and I needed to drop the old servername and add the new servername (sp_addserver) on both servers to get the publisher to work.

When I try to setup the subscription from SQL2 and add SQL1 as a publisher I get the same error.

Any one have any idea what it can be?

I found the problem. I didnt have the SQL Browser service runnning which looks to be needed when using instances. After starting it, it works to connect.

Cannot connect to sql through asp app.

iis and sql on same box. asp lan app.
I can open the initial page but get this error when i try to look up a
customer or other db dependant actions.
Microsoft OLE DB Provider for SQL Server (0x80040e4d)
Login failed for user 'sa'
/ctservice/view_edit_service/getindex.asp, line 22
the code on line 21-22:
Set connEditService = Server.CreateObject("ADODB.Connection")
connEditService.Open conString
This started when i tried to change the sa password so that i could
access the db for a mail merge. I don't have the original sa password
and i don't know if i enabled it by accident. If so how do i remove it
or fix this error? thanks jho.
On Jan 13, 4:36Xpm, jho <jhogan0...@.yahoo.com> wrote:
> iis and sql on same box. asp lan app.
> I can open the initial page but get this error when i try to look up a
> customer or other db dependant actions.
> Microsoft OLE DB Provider for SQL Server (0x80040e4d)
> Login failed for user 'sa'
> /ctservice/view_edit_service/getindex.asp, line 22
> the code on line 21-22:
> Set connEditService = Server.CreateObject("ADODB.Connection")
> connEditService.Open conString
> This started when i tried to change the sa password so that i could
> access the db for a mail merge. I don't have the original sa password
> and i don't know if i enabled it by accident. If so how do i remove it
> or fix this error? thanks jho.
I found the password for sa after searching all of the pages in the
site for, you guessed it, password duh....

Cannot connect to sql through asp app.

iis and sql on same box. asp lan app.
I can open the initial page but get this error when i try to look up a
customer or other db dependant actions.
Microsoft OLE DB Provider for SQL Server (0x80040e4d)
Login failed for user 'sa'
/ctservice/view_edit_service/getindex.asp, line 22
the code on line 21-22:
Set connEditService = Server.CreateObject("ADODB.Connection")
connEditService.Open conString
This started when i tried to change the sa password so that i could
access the db for a mail merge. I don't have the original sa password
and i don't know if i enabled it by accident. If so how do i remove it
or fix this error? thanks jho.On Jan 13, 4:36=A0pm, jho <jhogan0...@.yahoo.com> wrote:
> iis and sql on same box. asp lan app.
> I can open the initial page but get this error when i try to look up a
> customer or other db dependant actions.
> Microsoft OLE DB Provider for SQL Server (0x80040e4d)
> Login failed for user 'sa'
> /ctservice/view_edit_service/getindex.asp, line 22
> the code on line 21-22:
> Set connEditService =3D Server.CreateObject("ADODB.Connection")
> connEditService.Open conString
> This started when i tried to change the sa password so that i could
> access the db for a mail merge. I don't have the original sa password
> and i don't know if i enabled it by accident. If so how do i remove it
> or fix this error? thanks jho.
I found the password for sa after searching all of the pages in the
site for, you guessed it, password duh....

Cannot connect to MSDE

Hello all,
I have two computers in LAN. Both computers are visible
one to another. First computer has MSDE installed on it.
Second cumputer runs application that needs to connect to
MSDE installed on the first computer. The problem is that
application installed on second computer cannot connect to
MSDE and i cant figure out why is that so.
The application running on first computer(the one that
has MSDE installed on it) can connect to MSDE without any
problems. MSDE is configured to use SQL Server
authentication. Can anyone help me please ?
Regards,
Tom
hi Tom,
Tom wrote:
> Hello all,
> I have two computers in LAN. Both computers are visible
> one to another. First computer has MSDE installed on it.
> Second cumputer runs application that needs to connect to
> MSDE installed on the first computer. The problem is that
> application installed on second computer cannot connect to
> MSDE and i cant figure out why is that so.
> The application running on first computer(the one that
> has MSDE installed on it) can connect to MSDE without any
> problems. MSDE is configured to use SQL Server
> authentication. Can anyone help me please ?
> Regards,
> Tom
MSDE installs by default disabling network protocols to prevent external
mailcius attacks...
you have to manually enable them, bot at install time providing the
DISABLENETWORKPROTOCOLS=0
parameter to setup.exe boostrap installer and/or later using the Server
Network Utility (svrnet.cn.exe) to enable the desired/required network
protocol (usually TCP/IP)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
I'm having the same problem. I am working in a peer-to-peer LAN (all XP
stations) and have all my tools installed on one station (MSDE, Visual
Studio, you great DbaMGR2k, Book Online, etc) and things are working
fine, but I can't access SQL from the other stations. All the stations
can see each others and share all other resources.
- I used svrnetcn.exe to make certain TCP/IP protocol was installed, it was
- I tried added named pipes too but it doesn't help
- I logged in as Administrator but still have the problem
Questions:
- Do I need to install MSDE on all the stations?
- Could Windows XP SP2 firewall be the problem?
Thanks
Richard
Andrea Montanari wrote:
> hi Tom,
> Tom wrote:
>
> MSDE installs by default disabling network protocols to prevent external
> mailcius attacks...
> you have to manually enable them, bot at install time providing the
> DISABLENETWORKPROTOCOLS=0
> parameter to setup.exe boostrap installer and/or later using the Server
> Network Utility (svrnet.cn.exe) to enable the desired/required network
> protocol (usually TCP/IP)
|||hi Richard,
Richard Fagen wrote:
> Hi Andrea,
> I'm having the same problem. I am working in a peer-to-peer LAN (all
> XP stations) and have all my tools installed on one station (MSDE,
> Visual Studio,
> you great DbaMGR2k
thank's :D

>, Book Online, etc) and things are
> working
> fine, but I can't access SQL from the other stations. All the
> stations can see each others and share all other resources.
> - I used svrnetcn.exe to make certain TCP/IP protocol was installed,
> it was
> - I tried added named pipes too but it doesn't help
> - I logged in as Administrator but still have the problem
> Questions:
> - Do I need to install MSDE on all the stations?
no, you don't
> - Could Windows XP SP2 firewall be the problem?
probably yes...
please have a look at http://support.microsoft.com/default.aspx?kbid=841249
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
personally I always solved my troubles adding an exception to the firewall
for the related TCP/IP port both specifying a subnet range and/or defined
pc's IP ... if you can restrict the IP list your server will appreciate it
:D
for named instance the UDP 1434 port must be opened as well, if you do not
specify an ALIAS on all remote clients pointing to a static defined (and not
dinamically assigned) port
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
Thanks for the links
> probably yes...
> please have a look at http://support.microsoft.com/default.aspx?kbid=841249
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
I tried what it said and I even tried disabling the XP SP2 firewall on
both PCs but the second PC (the one without MSDE installed) still can't
see the first PC (with MSDE and the databases).
I tried using your utility, DbaMGR2k, on the second PC but when I try to
connect, I get the error message, "429 - ActiveX component can't create
object"
I am new to MSDE and I am not sure if I need aliases, named pipes,
special libaries etc. What I do have configured is TCP/IP protocol and
I checked and it uses the default port 1433. I also only have one
instance, the default, created during installation.
I could try to install MSDE on a third PC with all the defaults and see
what happens, but I'm fairly certain I didn't change anything from the
recommended defaults during the initial installation.
Any ideas why the other stations still can't see MSDE?
Thanks.
Richard Fagen

> personally I always solved my troubles adding an exception to the firewall
> for the related TCP/IP port both specifying a subnet range and/or defined
> pc's IP ... if you can restrict the IP list your server will appreciate it
> :D
> for named instance the UDP 1434 port must be opened as well, if you do not
> specify an ALIAS on all remote clients pointing to a static defined (and not
> dinamically assigned) port
|||hi Richard,
Richard Fagen wrote:
> I tried what it said and I even tried disabling the XP SP2 firewall on
> both PCs but the second PC (the one without MSDE installed) still
> can't see the first PC (with MSDE and the databases).
can you reach the MSDE installed pc from the remote client for standard
sharing?
can you ping it?
can you telnet it, in the form
c:\..\>telnet ComputerName 1433;
if the screen becomes black you are in... then just type QUIT to exit..

> I tried using your utility, DbaMGR2k, on the second PC but when I try
> to connect, I get the error message, "429 - ActiveX component can't
> create object"
DbaMgr2k does not provide the SQL-DMO dependencies it relies on becouse of
the presence several international localizations and service pack level..
in the application folder you can find the Depend2k.txt file which lists, in
the SQL-DMO section, all the required files you can get from the MSDE
installed pc and copy on the destination pc.. please fullfill the indicated
hyerarchy and register via regsvr32 the required file (just 1)
please feel free to privately contact me for any question or concern about
the project, as long as for suggestions and feedback, as this is OT in this
public newsgroup...

> I am new to MSDE and I am not sure if I need aliases, named pipes,
> special libaries etc. What I do have configured is TCP/IP protocol
> and I checked and it uses the default port 1433. I also only have one
> instance, the default, created during installation.
that's ok.. the default instance listens on TCP/IP 1433 (if it has not been
changed) and does not require an ALIAS nor the UDP 1434 port for the SQL
Server Resolution Service to work as it is not needed..

> Any ideas why the other stations still can't see MSDE?
if all TCP/IP requirements and checks has been satisfied, I do think it's
just a network problem.. please verify your connectivity other then SQL
Server...
again... for my personal tests I just referenced
http://support.microsoft.com/default.aspx?kbid=841252 and worked like a
charm...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply