Post reply

Problem setting up log-shipping

  • January 1, 2008 at 3:05 pm

    #121525

    I'm trying to set up log shipping between 2 SQL Server 2005 servers. I have restored a full backup to the target server in 'Standby' mode, and am now setting about the task of making the source database the primary database. When I get right to the end of the process SQL Server complains that my server name does not exist.

    Below is the error report. Has anyone seen it? My Primary Server Name is N000S003, yet SQL Server complains about server name SERVER N000S003N

    Thanks in advance for any help...

    Neil Croft

    ***********************************

    Save Log Shipping Configuration

    - Saving secondary destination configuration [loytest].[Loyalty] (Success)

    - Saving primary backup setup (Error)

    Messages

    SQL Server Management Studio could not save the configuration of 'N000S003' as a Primary. (Microsoft SQL Server Management Studio)

    ------------------------------

    ADDITIONAL INFORMATION:

    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

    ------------------------------

    The specified @server_name ('N000S003N') does not exist.

    The specified @server_name ('N000S003N') does not exist. (Microsoft SQL Server, Error: 14262)

  • January 2, 2008 at 2:45 am

    #763943

    Neil,

    when you run SELECT @@Servername(), does it return your servers name or NULL? My guess would be NULL.

    Sometimes it happens that the entry for the local server in sysservers is missing and then the name would be unknown. To check run:

    Select * from sysservers where server_id = 0

    In case the previous query doesn't return a record you can add the local server using sp_addserver 'servername', local

    Be ware that you need to restart SQL Server before the change gets effective.

    [font="Verdana"]Markus Bohse[/font]

  • January 2, 2008 at 3:07 am

    #763950

    Can you run select @@servername and verify the name is correct on both servers (same as physical name of machine)

    I have a feeling that they are not the same.

  • January 2, 2008 at 7:44 pm

    #764239

    Markus, Belmukund,

    Thank-you for your replies. It transpires that this server (N000S003) replaced an old version of the same name prior to my commencement in this role. In order to have them both in the environment at the same time, the NEW one was called N000s003N. When testing was complete and the olld one was decommissioned, no-one bothered to rename the NEW SQL Server servername from N000s003N to N000S003.

    I have solved this by using:

    sp_dropserver N000S003N

    sp_addserver N000S003, local

    The creation of the LogShipping option against my chosen database now works.

    Regards, Neil

  • February 7, 2008 at 7:15 am

    #776002

    I was having the exact same problem. This fixed it. Thanks for posting your suggestions.

    Sherry

  • May 28, 2008 at 12:44 am

    #820997

    Thanks a lot, it really works fine 🙂

  • August 19, 2008 at 7:29 am

    #860007

    hello,

    I am getting the same error while trying to setup Log Shipping for 2 servers on my local machine.

    Can anyone tell me what should be the @@servername in case both instances of SQL Servers are on the same machine(just for testing purpose).

    Also, one of them is the default instance and the other one is named instance.

    thanks.

  • August 19, 2008 at 9:53 am

    #860111

    use the following

    select @@servername, serverproperty('servername')

    they should return the same name, if not use sp_dropserver and then sp_addserver

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • August 20, 2008 at 1:38 am

    #860453

    That works, Thanks!

  • September 17, 2009 at 5:20 pm

    #1055307

    I have the same problem, but my @@servername is set.

    Any other ideas?

    *****

    Give a man a fish, and you've given him a meal. Teach a man to fish and he'll ask to borrow your boat.:-P

  • September 17, 2009 at 11:19 pm

    #1055382

    Depending on whether you have changed the name of the server instance you will have to drop and add a new one.

    Remarks section here should be helpful to you.

  • September 18, 2009 at 4:58 am

    #1055492

    ;-):-)


    - Pradyothana     http://www.msqlserver.com

  • April 28, 2012 at 11:57 am

    #1480867

    Hi,

    Probably a bit late for you, but maybe not for others.

    Today we renamed a SQL 2008R2 server and tried to setup log shipping and got a similar error.

    We renamed the server using:

    sp_addserver servername, local

    The @@Servername was correct but the problem remained.

    We checked the log shipping tables and the were no entries for the old server name.

    We eventually started scanning the registry and found the following setting:

    HKLM\Software\Microsoft\Microsoft SQL Server\100\Machines\OriginalMachineName

    This had the old server name in it, correcting this seemed to allow log shipping to work.

    Bit odd, but saved us having to install SQL.

    Hope it helps someone...

    Graham

  • January 31, 2015 at 12:35 am

    #1774537

    Hi Everyone,

    Thank you for this subject really its usefully for me.

    once again thank you.

Viewing 14 posts - 1 through 13 (of 13 total)

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