error setting up a new subscription

Question

Post reply

error setting up a new subscription

purplebirky

SSC-Addicted

Points: 461
More actions
March 26, 2009 at 10:25 am

#202768

this is the error msg i get:
TITLE: Connect to Server
------------------------------
Cannot connect to loaner7.
------------------------------
ADDITIONAL INFORMATION:
Failed to connect to server loaner7. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. 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: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
-----------------------------------------------------------------------------------------
I know my password is correct to that computer... I know the named pipes are open...
not sure what else to check.
--thanks
[font="Comic Sans MS"]Being "normal" is not necessarily a virtue; it rather denotes a lack of courage.
-Practical Magic[/font]

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

Roy Ernest SSC-Dedicated Points: 38780 More actions · Answer 1

Do you have any firewall/acls set up that blocks UDP Port 1434??

Just a shot in the dark. Also check what account the services are running under.

-Roy

purplebirky SSC-Addicted Points: 461 More actions · Answer 2

No i do not think that it's a firewall problem because we (me and IT) dropped the firewall for a while during some testing. I'll look into the account question and get back with an answer.

thanks for the suggestion.

[font="Comic Sans MS"]Being "normal" is not necessarily a virtue; it rather denotes a lack of courage.
-Practical Magic[/font]

Roy Ernest SSC-Dedicated Points: 38780 More actions · Answer 3

Also check if SQLBrowser service is up and running.

-Roy

purplebirky SSC-Addicted Points: 461 More actions · Answer 4

i find that in the surface area config right?

if so then yes it's up and running.

[font="Comic Sans MS"]Being "normal" is not necessarily a virtue; it rather denotes a lack of courage.
-Practical Magic[/font]

Roy Ernest SSC-Dedicated Points: 38780 More actions · Answer 5

Thats the end of my knowledge base... Sorry. 🙂

-Roy

Kendal Van Dyke SSCertifiable Points: 5972 More actions · Answer 6

Is this a push subscription or a pull subscription? At what step in trying to create the subscription does the error occur? Have you tried scripting out the new subscription and running it on a query window?

Kendal Van Dyke
http://kendalvandyke.blogspot.com/[/url]

purplebirky SSC-Addicted Points: 461 More actions · Answer 7

Well at some point I will need it to push or pull as needed but at the moment we are just trying to set up a push subscription.

I go to the database that is set as the publisher, right click on it to add a subscription, select the current database as the publisher, then is asks for the subscriber database, enter the name and password for that second database... that’s when I get the error that I posted before... I can't get past that point.

[font="Comic Sans MS"]Being "normal" is not necessarily a virtue; it rather denotes a lack of courage.
-Practical Magic[/font]

Kendal Van Dyke SSCertifiable Points: 5972 More actions · Answer 8

That sounds like an issue between your machine and the subscriber. Are you using your desktop\laptop to set up the subscription, and if so can you open a new query to the subscriber in SSMS?

Kendal Van Dyke
http://kendalvandyke.blogspot.com/[/url]

purplebirky SSC-Addicted Points: 461 More actions · Answer 9

Well the Publisher is on a desktop, i have one database (a hopefull subscriber) on a laptop and another one on a desktop (was in a process of elimatation to see if it was just the laptop that was causeing the problem) same error message each time.

I tried this morning to go to the hopefull subcriber and set up a push subscribtion and i got to the end of the wizard (silly me i thought i had own the battle) so i tell the server to sync up and then i get errors...

the error msgs are way too long to post here but the one that stands out is this:

-The job failed. The Job was invoked by User sa. The last step to run was step 3 (Detect nonlogged agent shutdown.).

-Detect nonlogged agent shutdown.,,Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.

-The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information. The step failed.

these are listed in order as listed in my error logs.

[font="Comic Sans MS"]Being "normal" is not necessarily a virtue; it rather denotes a lack of courage.
-Practical Magic[/font]

Kendal Van Dyke SSCertifiable Points: 5972 More actions · Answer 10

Make sure that the account you've set your distribution agents to run as has the necessary rights to both the publisher and subscriber. Are the publisher and subscriber in the same domain?

Kendal Van Dyke
http://kendalvandyke.blogspot.com/[/url]

purplebirky SSC-Addicted Points: 461 More actions · Answer 11

I know if can work because my tower has a subscription to the that publisher... i just can't get it to work anywhere else. Yep, i checked the setting on all computers, i can't find anything diffrent. One of my IT staff think that there is a communactation error between the computers, so we are gonna test that thery this afternoon.

[font="Comic Sans MS"]Being "normal" is not necessarily a virtue; it rather denotes a lack of courage.
-Practical Magic[/font]