Computer name conflict

I have ServerA and ServerB. I configured ServerB as distributor and allowed
ServerA as a publisher for it. Then I started to configure ServerAs publisher
using ServerB as distributor but the process failed with error stating
SeverA0 is not enabled as publisher for distributor ServerB ... eventhough
the NetBIOS name of ServerA is really ServerA and not ServerA0. If I enable
ServerA0 as publisher for distributor on ServerB I can finallize the
replication setup. But the finall reasult is that (for Trans replication)
Snapshot agent on ServerB reports failure: Cannot connect to ServerA0.
It seems that SQL server on ServerA calls it self a little bit different
then what is his NetBIOS name.
Is this really possible? How can I recover from this?
Thanks a lot for any help.
Tom Hagen
Some of this may be related to differences between servername (NETBIOS) and
the name registered in sysservers for the local system. It's possible you
didn't run sp_dropserver, sp_addserver with the local switch?
Just so I can understand the issues a bit more can I just confirm some
things?
Initially: ServerB - distributor, ServerA - Publisher
Next step: rename ServerA as ServerA0? However you mention that the NETBIOS
name was still ServerA so where did ServerA0 come from? Perhaps this is an
alias or it is sp_addserver?
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Just to clarify: I'm not the owner of ServerA nor I was installing it. So I
know a few about it.
No, I never run sp_addserver nor sp_dropserver directly. I was just
configuring the replication using Enterprise Manager from ServerB.
To your questions:
Exactly: ServerB is a Distributor; ServerA is a Publisher.
I didn't rename the servers during the configuration. So ServerA was named
ServerA before and is still. What I know is that ServerA was not fully
installed from scratch, instead it was somehow "cloned". I think that the
original server from which it was cloned was named ServerA0. But this name I
cannot find either in linked server nor remote servers on ServerA. Nor I can
find ServerA name in there. Can this be the problem? Shall I add ServerA to
Remote servers on ServerA?
Thanks in advance
Tom Hagen
|||Tom,
I'm beginning to get the picture. an you run select @.@.servername,
SERVERPROPERTY('ServerName') on ServerA and post back the results.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Great,
@.@.SERVERNAME returns 'ServerA0',
'SERVERPROPERTY' is not a recognized function name.
Tom Hagen
|||Tom,
is this sql server 7.0? Anyway, running
Use Master
go
Sp_DropServer 'OldName'
GO
Use Master
go
Sp_Addserver 'NewName', 'local'
GO
Stop and Start SQL Services
should help.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks a lot Paul,
In the mean while I tested to add ServerA0 to the Remote Servers on ServerA
and it helped. The replication runs good.
But in any case, I'll synchronize the names to be correct using your
suggestion. But as it needs restart I have to plan it.
Thank you again.
Tom Hagen

compatibility question

just a question....

my web project is using SQL Express2005 and ASP.NET and C#.
my web hosting company only have MSsql2000. would there be any conflict with regards to my database? im sorry if i sound dumb. im a newbie to this.

thanks a lot!
There will not be a conflict but you may have to make code changes, there are a fair number of features in SQL Express that will not work with SQL 2000. I suggest downloading a copy of MSDE for yourself(which is free) so you can test before going live with the hoster.|||i am only using one mdf file and my asp.net program just deals with the common add, edit, delete transactions. would these transactions differ from version to version of MSSQL?

honestly i did not think there would be a problem coz these transactions are very common. pls correct me if i am wrong.
|||

It depends. Are you using user instances(its in the connection string)? are you using varchar(max), xml types? Are you using the new security features?

Any of the above will prevent the app from working on a sql server 200 machine.

|||

Euan Garden wrote:

It depends. Are you using user instances(its in the connection string)? are you using varchar(max), xml types? Are you using the new security features?

Any of the above will prevent the app from working on a sql server 200 machine.

this is my connection string:
<add name="conn_name" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\dbase_name.mdf;Integrated Security=True;User Instance=True" providerName="System.Data.SqlClient"/>

sql2000 doesnt support user instance, does it?

__
i just installed MSDE to make a test. i tried attaching my mdf file (created by SQL Express) to the MSDE but i got this error message:

"An error occured when attaching the database"

i attached that mdf file to the SQL Express and i encountered no problem at all. do you think i will encounter the same problem with my hosting company?

thanks for your time Euan.|||

2 issues here;

1/ MSDE does NOT support user instances so you need to change your conection string to a regular one.

2/ You are trying to attach a SQL2005 db to a SQL2000 machine, this will not work, you will need to move the data and schema onto a SQL Server 2000 implementation.

|||can I implement the membership control (provided by ASP.NET) on MSDE? i can try migrating from SQLEXxpress to MSDE but im not sure if membership control works on that MSDE. sorry if i really sound dumb. im a newbie.|||There is a tool that comes with ASP.Net that supports installation of the databases, aspnet_regsql.exe is its name, check and see if it can install the tables for membership control, I believe it supports SQL 2000 ie MSDE.|||

Euan Garden wrote:

There is a tool that comes with ASP.Net that supports installation of the databases, aspnet_regsql.exe is its name, check and see if it can install the tables for membership control, I believe it supports SQL 2000 ie MSDE.

i just tried it and it installed all the membership tables using this MSDE.
thanks for the help Euan Garden.