Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Donate Today!

Do you enjoy these
technical forums?
Donate Today! Click Here

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

TysonLPrice (Programmer)
20 Oct 11 11:35
I'm posting this for a fellow worker.

Upgrading Server Hardware and changing from Default Instance of SQL Server 2005 Standard 32bit on Windows 2003 32 bit to New Server Hardware with Named Instance of SQL Server 2005 Standard 64bit on Windows 2008 R2 .

I built the new server, created the named instance, restored the system DBs, and restored the user DBs.

My problem: Now I can't drop, rebuild, configure, or do anything with my transactional replication.

I receive the following error message:

An error occurred connecting to Publisher 'NewServer\Instance'
Additional Information: SQL Server requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternative name are not supported. Specify the actual server name, 'OldServerName'. (Replication.Utilities)

Where is this former server name stored? How do I wipe out everything in replication related to old server so I can start from scratch and use my modified replication scripts from the old server to rebuild replication? I would think there is a simple script that would clean up all this old information so you can rebuild replication on your new server.

Additional info: I've already followed the steps outlined in the following article which did not solve my problem.

http://msdn.microsoft.com/en-us/library/ms147921(v=SQL.90).aspx
How to: Disable Publishing and Distribution (Replication Transact-SQL Programming)

sp_dropsubscriber 'servername', @Ignore_distributor =1
sp_removedbreplication
use [master]
exec sp_dropdistributor @no_checks = 1, @Ignore_distributor =1

All commands ran successfully but I still receive same error when I try to configure publishing

Thanks in advance to anyone that can help!
 
Helpful Member!  mrdenny (Programmer)
20 Oct 11 20:08
You need to tell the master database what the new server name is.

CODE

exec sp_dropserver 'OldServerName'
go
exec sp_appserver 'NewServerName\NewInstance'
go

Then you'll need to restart the SQL Instance.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)
MCM (SQL 2008)
MVP

My Site

TysonLPrice (Programmer)
21 Oct 11 6:15
mrdenny to the rescue...

I passed that on to him and he will be in soon (7:00 AM EST).

Thanks!
TysonLPrice (Programmer)
21 Oct 11 7:37
mrdenny you sure put a smile on his face smile

That worked!
 

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close