Replicatioin Configuration Problem

Question

Replicatioin Configuration Problem

SqlDeveloper2246

SSC Eights!

Points: 886
More actions
June 9, 2008 at 2:59 pm

#183317

I have Windows Vista installed on my PC.
I logged in to the database engine, but when i tried start configuring replication i got this message?
This is the default instance on my PC.
When i click on Configure Distribution, another login widow appears to me, i tried to login using the same credentials as i logged TO the database engine, but i got this message.
I tried this before on Windows XP and it succeeded.
so anyone can fix this?
TITLE: Configure Distribution Wizard
------------------------------
SQL Server is unable to connect to server 'FDARKAZANLY'.
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server+Management+Studio&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.UI.ConfigureWizardErrorSR&EvtID=CantConnect&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, 'FERASGER83-PC'. (Replication.Utilities)
------------------------------
BUTTONS:
OK
------------------------------

Viewing 5 posts - 1 through 4 (of 4 total)

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

happycat59 One Orange Chip Points: 29389 More actions · Answer 1

When using replication you can't use aliases for the servers - the name that you register in Management Studio must match the name for the instance of SQL 2005. It looks like "FDARKAZANLY" is an alias for the workstation name of your PC.

SqlDeveloper2246 SSC Eights! Points: 886 More actions · Answer 2

My PC name was FERASGER83-PC, i installed the default instance of SQL2005.

Then i changed my PC name to FDARKAZANLY.

I'm logging now to the database using FDARKAZANLY without specifying an instance name because it's the default instance.

So i don't know till now why it's refusing to login!

happycat59 One Orange Chip Points: 29389 More actions · Answer 3

I am wondering whether there was an issue introduced when the workstation was renamed. Prior to SQL 2005, you needed to use sp_dropserver to remove the old server name and then sp_addserver 'new name, 'LOCAL' with the new name.

I thought that this was not needed any more but I may be wrong.

What is the name of the server when you run

SELECT @@ServerName

I think that you will see the old name.

SqlDeveloper2246 SSC Eights! Points: 886 More actions · Answer 4

Dear HappyCat59

Really i appreciate your help, and you're right in your analysis.

The problem was that the server name did not changed when renaming the PC.

I did the following:

SELECT @@ServerName

i found that it was the old PC name.

Then i did the following:

sp_dropserver 'FERASGER83-PC'

sp_addserver 'FDARKAZANLY', 'LOCAL'

Then i restarted the server,and the problem was solved.

SELECT @@ServerName returned the new PC name, and the configuration dialog appeared successfully.

Best Regards.