May 19, 2005 at 6:05 pm
I have a server on our domain called SERVER, which is a the publisher and distributor. I have created a merge publication on the server and I use the following statments to subscribe to it from another pc on the domain:
exec sp_addmergepullsubscription @publication = @PUB_NAME, @publisher = @SERVER_NAME, @publisher_db = @DB_NAME, @subscriber_type = N'anonymous', @subscription_priority = 0.000000, @sync_type = N'automatic', @description = N'Merge publication.'
exec sp_addmergepullsubscription_agent @publisher = @SERVER_NAME, @publisher_db = @DB_NAME, @publication = @PUB_NAME, @distributor = @SERVER_NAME, @subscriber_security_mode = 1, @publisher_security_mode = 0, @publisher_login = N'<username>', @publisher_password = N'<password>', @distributor_security_mode = 0, @distributor_login = N'<username>', @distributor_password = N'<password>', @frequency_type = 4, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 4, @frequency_subday_interval = 5, @active_start_date = 0, @active_end_date = 0, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @enabled_for_syncmgr = N'false', @use_ftp = N'true', @use_interactive_resolver = N'false', @offloadagent = N'false'
The SQL Server user account i'm using is set up correctly and so is FTP etc. When I set @SERVER_NAME as the internal name of the server 'SERVER', replication works perfectly, however, if I use the internal IP address, it fails. Also if I use the external IP address it fails and this is specifically what I want to do (to subscribe over the net).
I am also trying to use the instance name ontop of the ip address, ie 'xxx.xxx.xxx.xxx\<instance name>' and still no luck.
The firewall has the correct ports open. I am able to log onto Query analyser using the IP Address and the same username and password, and I am able to access the db.
Using the internal ip address '192.168.47.1':
"The remote server does not exist or has not been designated as a valid Publisher. The step failed."
Using '192.168.47.1\SERVER':
The process could not connect to Distributor '192.168.47.1\SERVER'. SQL Server does not exist or access denied.
The same as above happen when I use the external (internet side) ip address.
Any ideas why it would work using the server's computer name, but not the internal or external IP address?
Thanks,
Christopher.
May 20, 2005 at 5:12 am
When we first started using replication we had the same error. This is how it was resolved:
Set up a local alias on the publisher server. This alias should be the exact name of the subscriber. servername\instancename, which points to '192.168.47.1\SERVER'. Register this alias in enterprise manager.
The [srvname] in sysservers table must match the subscriber(s) server name in order for this to work because this is what replication uses to match up the Publisher and Subscribers.
May 22, 2005 at 6:43 pm
Hi SRB,
I can't set up an alias at the publisher server because the subscriptions are anonymous and I don't know the IP address, plus the IP address of the subscribers may change, even if I did know them, that's why they are anonymous.
I have tried however to create an alias at the subscriber which points to the publisher '192.168.47.1\SERVER' and registered this in enterprise manager. I can create a subscription now to that alias (in enterprise manager). When I look in the sysservers table, it has the alias, not the address of the publisher.
With all this said and done, the same errors occur, as above.
May 23, 2005 at 5:39 am
Does a PUSH subscription from the Publisher have the same error?
May 29, 2005 at 9:24 pm
Hi SRB,
I don't know if a push subscription would have the same error because the publisher does not know the address of the subscriber, as the ip address may constantly change etc. Plus the nature of the system is such that only a pull subscription is feasible.
I would assume it would have the same error as it comes down to one server simply not seeing the other correctly, even though they are being linked in enterprise manager and appears in the sysservers table.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply