Re: The remote server is not defined as a subscription server.

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: danA (dea_at_deamon.com)
Date: 03/01/05 

Date: Tue, 1 Mar 2005 18:24:04 -0000

You mean create an alias with the same name as the instance? This results
in the famous error: "SQL Server does not exists or access denied" when
trying to register in EM on the same computer.

I have summarise the situation and started a new thread.

Many thanks,
Dan

"Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
news:115601c51d92$5d644410$a501280a@phx.gbl...
> Steen,
> as far as I understand, Dan has already registered the
> subscriber in EM, but using an alias. The alias was used
> because he doesn't want to use the default port (although
> setting this up directly in EM is possible AFAIR).
> I agree that aliases are not normally required, but they
> are mandatory over non-trusted networks (see
> http://support.microsoft.com/?id=321822). However to be
> honest I don't think this is relevant here. My suspicion
> is that the problem is due to the registration of the
> alias with a name other than the true instance name on
> the subscriber - I have seen this before. Dan - can you
> test this setup to see if this solves the issue?
> Rgds,
> Paul Ibison
>
>
>
>
>>-----Original Message-----
>>Hi
>>
>>You could also try to register your subscriber server in
> EM on the
>>Distributor server. If that works, then you should also
> be able to define
>>the subscriber when you set up the replication. If you
> can't get access to
>>the subscriber from EM though then you won't be able to
> get it working from
>>the replication setup.
>>Paul mentions that you should create an alias for the
> server rather than
>>using the IP adress, but I don't think that's
> neccessary - I'm almost
>>certain that you can get it working when using the IP
> adress.
>>As a check, you can try a Telnet to the server on the
> port it's using - that
>>will tell you if you can get in touch with the server.
> I'd also check
>>security. Does the account your are using on the
> distributor has proper
>>access to the subscribtion server?
>>
>>Regards
>>Steen
>>
>>
>>
>>danA wrote:
>>> The reason I am using aliases is that "Dynamically
> determine port"
>>> does not work (I assume because UDP port 1434 is
> Filtered and I
>>> couldn't determine why), TCP port 1433 is already
> used, thus the
>>> instance had to be assigned statically to another port
> (in this case
>>> 1500). This is true on both Publisher and Subscriber
> computers.
>>>
>>>
>>> "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in
> message
>>> news:OzCROZQHFHA.588@TK2MSFTNGP15.phx.gbl...
>>>> Dan,
>>>>
>>>> please try creating an alias on the publisher
> called 'P1234\EL3E1'.
>>>> Only do this if you are using IP addresses in the
> client network
>>>> utility, otherwise try creating the registration as
> per usual in EM
>>>> without any alias at all, and then register that name
> as a
>>>> subscriber.
>>>>
>>>> For trusted/non-trusted domains, I'm referring to
> authentication of
>>>> users - are the same windows users visible to both
>>>> publisher/distributer and subscriber computers? If
> not, then the
>>>> setup will be different and will involve mandatory
> use of the client
>>>> network utility and usually FTP for initialization.
> I'm not entirely
>>>> clear about your case, but I suspect that your
> network is not set up
>>>> like this.
>>>>
>>>> HTH,
>>>> Paul Ibison
>>>>
>>>>
>>>> "danA" <dea@deamon.com> wrote in message
>>>> news:OLwjFSPHFHA.2976@TK2MSFTNGP15.phx.gbl...
>>>>> Paul,
>>>>> Thank you very much for your reply.
>>>>>
>>>>> On the subscriber computer:
>>>>>> please check that the @@SERVERNAME global variable
> and
>>>>>> the SERVERPROPERTY('ServerName') function on the
>>>>>> subscriber return the same value.
>>>>> Yes, they return the same value, namely: P1234\EL3E1.
>>>>> This instance listens to TCP port 1500 under the
> alias EL3E11500.
>>>>> In Enterprise Manager the instance has two
> registrations:
>>>>> P1234\EL3E1 and EL3E11500
>>>>> The Publisher is registered in Enterprise Manager
> under an alias.
>>>>> The connection works fine.
>>>>>
>>>>> On the Publisher computer:
>>>>> The Subscriber instance is registered in Enterprise
> Manager under
>>>>> its alias EL3E11500. The connection works fine.
>>>>> The Publisher and Distributor (same SQL instance)
> know the
>>>>> Subscriber under its alias EL3E11500
>>>>>
>>>>>> Also, are you replicating across non-trusted
> domains?
>>>>> I don't think so. How can I check?
>>>>>
>>>>>> And are you using an IP address in Enterprise
> Manager?
>>>>>> If so, please create ...
>>>>> I'm not sure I understand this part of your
> message. It's not
>>>>> clear for me what should happen on the Publisher's
> computer and
>>>>> what on the Subscriber's.
>>>>>
>>>>> Again, thank you very much,
>>>>> Dan
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in
> message
>>>>> news:1d6901c51cb8$052aac10$a401280a@phx.gbl...
>>>>>> Dan,
>>>>>>
>>>>>> please check that the @@SERVERNAME global variable
> and
>>>>>> the SERVERPROPERTY('ServerName') function on the
>>>>>> subscriber return the same value. If not, then run
> this:
>>>>>>
>>>>>> Use Master
>>>>>> go
>>>>>> Sp_DropServer 'OldName'
>>>>>> GO
>>>>>> Sp_Addserver 'NewName', 'local'
>>>>>> GO
>>>>>> Stop and Start SQL Services
>>>>>>
>>>>>> Also, are you replicating across non-trusted
> domains?
>>>>>> And are you using an IP address in Enterprise
> Manager?
>>>>>> If so, please create an alias using the client
> network
>>>>>> utility on the publisher which has the exact same
> name as
>>>>>> the publisher, and maps to the IP address (ie a
> TCP/IP
>>>>>> alias). Register this alias in EM on the publisher
> and as
>>>>>> a subscriber.
>>>>>>
>>>>>> If none of this applies, then post back and I'll
> have
>>>>>> another think.
>>>>>>
>>>>>> HTH,
>>>>>> Paul Ibison SQL Server MVP,
> www.replicationanswers.com
>>>>>> (recommended sql server 2000 replication book:
>>>>>> http://www.nwsu.com/0974973602p.html)
>>
>>
>>.
>>

Quantcast