locked
automatic failover not working RRS feed

  • Question

  • Hello,

     

    I've configured my two database instances for mirroring (confirmed by doing a manual failover in SQL 2008), and I set the failover partners for SP2010 through powershell using  .addFailoverServiceInstance(<servername>).  However, the failover doesn't seem to actually occur if I stop the principal server.  All I see in the logs are:

    SQL call failed (0x80004005: Unspecified error )                [atldbext.cxx:1290] d:\office\source\search\libs\utild\atldbext.cxx	 
    Application e493229d-92f3-4f5f-8b65-f8846ff94fb3-crawl-0, resource 2: pIDBInitialize->Initialize error. Failed to create a non fast load session. [resourcemanagerimpl.cpp:1070] d:\office\source\search\native\mssrch\resourcemanagerimpl.cpp	 
    CResourceManager::CreateSessionEx2 Error creating non fastload session 'Provider=SQLNCLI10;Extended Properties='Server=SQL\stage1;Database=Search Service Application 1;Trusted_Connection=yes;App=Microsoft SharePoint Foundation;Timeout=15;FailoverPartner=SQL\stage2';'. [resourcemanagerimpl.cpp:1124] d:\office\source\search\native\mssrch\resourcemanagerimpl.cpp	 
    SQL call failed (0x80004005: Unspecified error )                [atldbext.cxx:1290] d:\office\source\search\libs\utild\atldbext.cxx	 
    error 0: Login timeout expired (source Microsoft SQL Server Native Client 10.0, 0x80004005, code 0: Unspecified error ) [atldbext.cxx:1386] d:\office\source\search\libs\utild\atldbext.cxx	 
    error 1: Login failed for user 'CONTOSO\sharepoint'. (source Microsoft SQL Server Native Client 10.0, 0x80004005, code 18456: Unspecified error ) [atldbext.cxx:1386] d:\office\source\search\libs\utild\atldbext.cxx	 
    error 2: Cannot open database "Search Service Application 1" requested by the login. The login failed. (source Microsoft SQL Server Native Client 10.0, 0x80004005, code 4060: Unspecified error ) [atldbext.cxx:1386] d:\office\source\search\libs\utild\atldbext.cxx	 
    error 3: A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. (source Microsoft SQL Server Native Client 10.0, 0x80004005, code 2: Unspecified error ) [atldbext.cxx:1386] d:\office\source\search\libs\utild\atldbext.cxx	 
    error 4: Named Pipes Provider: Could not open a connection to SQL Server [2]. (source Microsoft SQL Server Native Client 10.0, 0x80004005, code 2: Unspecified error ) [atldbext.cxx:1386] d:\office\source\search\libs\utild\atldbext.cxx	  	
    [tripmain.cxx:4865] d:\office\source\search\native\ytrip\search\tripoliplugin\tripmain.cxx
    [tripmain.cxx:1991] d:\office\source\search\native\ytrip\search\tripoliplugin\tripmain.cxx
    I assume this is more an error message saying it can't connect to the principal server. As I said, manual failover works fine.  Any ideas what might be going wrong?

     

    Wednesday, May 12, 2010 7:55 PM

Answers

  • I forgot to allow the necessary login CONNECT permission to the endpoint.
    • Marked as answer by robdtec Thursday, May 13, 2010 2:27 PM
    Thursday, May 13, 2010 1:39 PM

All replies

  • I forgot to allow the necessary login CONNECT permission to the endpoint.
    • Marked as answer by robdtec Thursday, May 13, 2010 2:27 PM
    Thursday, May 13, 2010 1:39 PM
  • On one of our search servers we encounter this same error.

    What do you mean with "allow the necessary login CONNECT permission to the endpoint"?

    Friday, September 30, 2011 11:36 AM