Error 21007

I can't configure my Sql Server 2000 Publisher, the Enterprise Manager
reports this error message: "Errore 21007. Cannot add the remote Distributor
when it tries to complete the operation. Make sure that the local server is
configured as a Publisher at a Distributor". What does it depends on? How can
I solve it?
Thanks.
Is this a local or remote distributor?
Its hard to fix these errors. IIRC I have been able to fix them by disabling
replication, un-registering SQL Server through EM, reregistering it as .,
bouncing the server, removing it from EM, registering it as the servername,
bounce, and trying again.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Ago" <Ago@.discussions.microsoft.com> wrote in message
news:ECC6DE78-1321-4BBD-BA7D-158639B07D3B@.microsoft.com...
> I can't configure my Sql Server 2000 Publisher, the Enterprise Manager
> reports this error message: "Errore 21007. Cannot add the remote
Distributor
> when it tries to complete the operation. Make sure that the local server
is
> configured as a Publisher at a Distributor". What does it depends on? How
can
> I solve it?
> Thanks.
|||It should be a local distributor.
I explain better my SQL server configuration.
I have a server named ITDEXANET001 and I have created a SQL server
registration with the server name ITDEXANET001, then I try to configure
ITDEXANET001 as Distributor and Publisher and I get this error message when
it is going to create the Distributor. I don't know if it is important but I
have also noticed that it adds an item in the Remote Servers folder named
LG696-EURO_J05 (that is the name of the domain), if I delete this Remote
server the installation of Replication fails with the error message 18482:
"Could not connect to server 'ITDEXANET001' because
'LG696_EURO_J05' is not configured as remote server", it is not clear to me
what it means.
"Hilary Cotter" wrote:

> Is this a local or remote distributor?
> Its hard to fix these errors. IIRC I have been able to fix them by disabling
> replication, un-registering SQL Server through EM, reregistering it as .,
> bouncing the server, removing it from EM, registering it as the servername,
> bounce, and trying again.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Ago" <Ago@.discussions.microsoft.com> wrote in message
> news:ECC6DE78-1321-4BBD-BA7D-158639B07D3B@.microsoft.com...
> Distributor
> is
> can
>
>