Unable to setup Subscriber

Question

Unable to setup Subscriber

gfx99ne

SSChasing Mays

Points: 645
More actions
March 13, 2017 at 7:20 am

#328337

Hi,
I'm unable to connect to remove server without mention of port number, but when I do that when specifying Subscriber instance I also get an error
I'm posting both errors in screenshots below, with and without mention of port number.
Could someone please guide me how to achieve this?? I've spent extensive time googling and experimenting, but unsuccessful.
Thanks,
K

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

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

Sue_H SSC Guru Points: 90860 More actions · Answer 1

One possibility is that you can see this error if you have renamed the server and it's out of sync internally.
Run the following and see if the same names appear:
SELECT SERVERPROPERTY(N'YourServername') SELECT @@SERVERNAME

@@servername would have the old/original name of the server before the rename. If it's out of sync, it can be fixed with sp_addserver/sp_dropserver

Sue

gfx99ne SSChasing Mays Points: 645 More actions · Answer 2

Sue_H - Monday, March 13, 2017 8:56 AM
One possibility is that you can see this error if you have renamed the server and it's out of sync internally.
Run the following and see if the same names appear:
SELECT SERVERPROPERTY(N'YourServername') SELECT @@SERVERNAME
@@servername would have the old/original name of the server before the rename. If it's out of sync, it can be fixed with sp_addserver/sp_dropserver
Sue

Tried to do so, but still same 🙁

Sue_H SSC Guru Points: 90860 More actions · Answer 3

gfx99ne - Wednesday, March 15, 2017 7:16 AM
Sue_H - Monday, March 13, 2017 8:56 AM
One possibility is that you can see this error if you have renamed the server and it's out of sync internally.
Run the following and see if the same names appear:
SELECT SERVERPROPERTY(N'YourServername') SELECT @@SERVERNAME
@@servername would have the old/original name of the server before the rename. If it's out of sync, it can be fixed with sp_addserver/sp_dropserver
Sue
Tried to do so, but still same 🙁

Tried to do what? Did you rename the server?

Sue

gfx99ne SSChasing Mays Points: 645 More actions · Answer 4

Sue_H - Monday, March 13, 2017 8:56 AM
One possibility is that you can see this error if you have renamed the server and it's out of sync internally.
Run the following and see if the same names appear:
SELECT SERVERPROPERTY(N'YourServername') SELECT @@SERVERNAME
@@servername would have the old/original name of the server before the rename. If it's out of sync, it can be fixed with sp_addserver/sp_dropserver
Sue

Ok, works now. Browser service was not running, thanks for help.

gfx99ne SSChasing Mays Points: 645 More actions · Answer 5

gfx99ne - Wednesday, March 15, 2017 7:27 AM
Sue_H - Monday, March 13, 2017 8:56 AM
One possibility is that you can see this error if you have renamed the server and it's out of sync internally.
Run the following and see if the same names appear:
SELECT SERVERPROPERTY(N'YourServername') SELECT @@SERVERNAME
@@servername would have the old/original name of the server before the rename. If it's out of sync, it can be fixed with sp_addserver/sp_dropserver
Sue
Ok, works now. Browser service was not running, thanks for help.

Hi,
Why I'm getting below warning in Pull Seubscription, and how to fix it please??

Thanks,
K

Sue_H SSC Guru Points: 90860 More actions · Answer 6

gfx99ne - Thursday, March 16, 2017 5:06 AM
gfx99ne - Wednesday, March 15, 2017 7:27 AM
Sue_H - Monday, March 13, 2017 8:56 AM
One possibility is that you can see this error if you have renamed the server and it's out of sync internally.
Run the following and see if the same names appear:
SELECT SERVERPROPERTY(N'YourServername') SELECT @@SERVERNAME
@@servername would have the old/original name of the server before the rename. If it's out of sync, it can be fixed with sp_addserver/sp_dropserver
Sue
Ok, works now. Browser service was not running, thanks for help.
Hi,
Why I'm getting below warning in Pull Seubscription, and how to fix it please??
Thanks,
K

Was it every initialized? Depending on your environment and the subscription, you could just reinitialize by right clicking on the warning and select Reinitialize then it prompts you to use the current or new snapshot. Have no way of knowing any of the details but the safest would be a new snapshot. That can have impacts if it's a large subscription.

Sue

riverre SSC Enthusiast Points: 107 More actions · Answer 7

https://social.msdn.microsoft.com/Forums/en-US/0b5c2275-953b-48a2-8653-00ef3dfa7f26/unable-to-setup-subscriber?forum=sqlreplication

gfx99ne SSChasing Mays Points: 645 More actions · Answer 8

Sue_H - Thursday, March 16, 2017 7:52 AM
gfx99ne - Thursday, March 16, 2017 5:06 AM
gfx99ne - Wednesday, March 15, 2017 7:27 AM
Sue_H - Monday, March 13, 2017 8:56 AM
One possibility is that you can see this error if you have renamed the server and it's out of sync internally.
Run the following and see if the same names appear:
SELECT SERVERPROPERTY(N'YourServername') SELECT @@SERVERNAME
@@servername would have the old/original name of the server before the rename. If it's out of sync, it can be fixed with sp_addserver/sp_dropserver
Sue
Ok, works now. Browser service was not running, thanks for help.
Hi,
Why I'm getting below warning in Pull Seubscription, and how to fix it please??
Thanks,
K
Was it every initialized? Depending on your environment and the subscription, you could just reinitialize by right clicking on the warning and select Reinitialize then it prompts you to use the current or new snapshot. Have no way of knowing any of the details but the safest would be a new snapshot. That can have impacts if it's a large subscription.
Sue

Reinitialize is not making a difference. Is there any specific log that i could check please?

Sue_H SSC Guru Points: 90860 More actions · Answer 9

gfx99ne - Friday, March 17, 2017 5:08 AM
Sue_H - Thursday, March 16, 2017 7:52 AM
gfx99ne - Thursday, March 16, 2017 5:06 AM
Hi,
Why I'm getting below warning in Pull Seubscription, and how to fix it please??
Thanks,
K
Was it every initialized? Depending on your environment and the subscription, you could just reinitialize by right clicking on the warning and select Reinitialize then it prompts you to use the current or new snapshot. Have no way of knowing any of the details but the safest would be a new snapshot. That can have impacts if it's a large subscription.
Sue
Reinitialize is not making a difference. Is there any specific log that i could check please?

If you double click on that Uninitialized subscription, it will open another window that shows the commands each direction.
But from that window shown above, click on the Agent tab. Check the Job named Snapshot Agent. You'd want to start the agent if the status is not completed - right click and start agent. If it says completed, right click and select View Details and you can view the history from there.

Sue

Beatrix Kiddo SSC-Dedicated Points: 32407 More actions · Answer 10

Isn't the pull subscription attempting to run from a SQL Express instance?

https://technet.microsoft.com/en-us/library/ms165686(v=sql.105).aspx

SQL Server Express does not include the SQL Server Agent, which is typically used to run replication agents. If you use push subscription, replication agents run at the Distributor, which will be an instance of SQL Server, so there are options for synchronizing. But if you use a pull subscription, in which agents run at the Subscriber, you must synchronize the subscription by using Windows Synchronization Manager or RMO.