Replication Problem where Distributor & Subcriber on same machine

What I would like to do is set up transactional replication from server1 (Publisher) to server2 (Subscriber), with server2 acting as the (Distributor).

I am successful on server2 in allowing server2 as a distributor for server1. When I try to configure replication on server1 to use server2 as a distributor and subscriber I get this message once

"
SQL Server Enterprise Manager could not enable 'server2' as a Subscriber.

Error 14071: Could not find the Distributor or the distribution database fom the local server. The Distributor may not be installed, or the local server may not be configured as a Publisher at the Distributor.
"

and this mesage for each database I enable for subscription, I get this message.

"
SQL Server Enterprise Manager could not enable database 'x' for snapshot or transactional replications.

Error 20028: The Distributor has not been correctly installed. Could not enable database for publishing. The replication 'publish' of database 'x' has been set to false.
"

The last message I get is

"
SQL Server Enterprise Manager successfully enabled 'server2' as the Distributor for 'server1'.
"

This message is apparently false.

When I try to Configure Publishing, Subscribers and Distributing... on server1, I get the message

"
SQL Server Enterprise Manager could not retrieve information about the Distributor or the distribution database.
"

In an attempt to fix this I:
1. disable publishing on server1,
2. disable publising and distribution on server2.
3. enable publishing and distribution on server2.
4. enable publishing on server1 using server2 as distributor.

Again I get errors on step 4.

I have even tried re-installing SQL Server 2000 on server2 with no improvement.

Can some one please shed some light on this problem?

Thanks in advance.Connect to the SQL Server using Query Analyzer and run the following query: select @.@.servername.

If it returns NULL you will need to run the sp_addserver procedure to get
the internal server name correct. You may need to run sp_dropserver as
well. These are documented in Books on Line.

A NULL server name can cause wierd behavior with replication.|||I do have a NULL server name problem. I have run the sp_dropserver, sp_addserver and have retarted SQL Server.

I have tried again to create the replication & it now WORKS!

Satya, thanks soooo much for you help!

Replication problem

Hi,
I have two different servers Server1 and Server2. I had a database DB1 on Server1 which I restored onto the server Server2 with the same name DB1. Then I deleted the database DB1 from the server Server1. Now when I try to establish snapshot replication of DB1 from Server2 onto the Server1, I'm getting the following error.

"A connection could not be established to Server1 - Cannot open default database '<ID>'. Using master database instead.
Please verify SQL server running and check your SQL server registration properties (by right-clicking on the Server1 node) and try again."
DB1 was the default database on Server1 which I deleted after restoring the same onto Server2.
Now I'm not even able to connect to server1.

I'm using the user SA.

Thanks in advance.
Regards,
P.C. VaidyanathanYou must remember that when you copy a database from one server to another while users UIDs may be copied across inside the databse, they have the same name in the database and on the new server .....BUT...... the user ids are a match in name ONLY!!

Each user ID has an SUID ( 24 bit hex value I think ) that is unique for each UID on the server and in the copied over database. So, to make the UIDs line up in the databse with UIDs already defined on the new server, you need to run a special stored procedure called sp_change_users_login ( see books on line (BOL)) to map the UIDs so at they match on the UIDs. This maps the SUIDs such that UID "testuser" on your server matches UID "testuser" in the copied over database.

I have done this serveral times with minimal hassles.

Try this first, & see how you go. Post back if problems.

Cheers

J.