Results 1 to 4 of 4
  1. #1
    Join Date
    Dec 2007
    Posts
    3

    Unanswered: Log Shipping errors

    I am trying to set up log shipping in SQL 2005.
    The transaction log copy job is failing with the following error.

    2007-12-19 11:33:33.93 *** Error: Could not retrieve copy settings for secondary ID 'd8d9b7cf-0f36-4446-bdbb-488dfdc1f6fe'.(Microsoft.SqlServer.Management.LogS hipping) ***
    2007-12-19 11:33:33.95 *** Error: Failed to connect to server SCDSSLSQL2.(Microsoft.SqlServer.ConnectionInfo) ***
    2007-12-19 11:33:33.95 *** Error: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)(.Net SqlClient Data Provider) ***

    Any help would be appreciated.

    vkumar

  2. #2
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    Can you connect to the secondary server from the primary server using the SQL Service service credentials?

  3. #3
    Join Date
    Jan 2004
    Location
    In a large office with bad lighting
    Posts
    1,040
    Take a look at this too: http://support.microsoft.com/kb/328306

    -- This is all just a Figment of my Imagination --

  4. #4
    Join Date
    Dec 2007
    Posts
    3
    Thanks I got that resolved. Changed the services to use a common domain user account and enabled the Named Pipe protocol using the ' SQL Server Configuration Manager' Looks like it is working now.

    vkumar

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •