none
[sqrvres] CheckAndChangeVirtualServerName: Could not obtain the Virtual Server Name (status 138f)

    Question

  •  

    We're doing some re-configuration on our storage area network, and when we tried bringing our SQL Server 2005 servers back online (in a clustered environment), we're getting the following errors:

     

     

    Event Type: Error
    Event Source: MSSQL$SQLvs02b
    Event Category: (3)
    Event ID: 19019
    Date:  12/7/2008
    Time:  8:32:42 PM
    User:  N/A
    Computer: MLBN-SQLN01
    Description:
    [sqsrvres] CheckAndChangeVirtualServerName: Could not obtain the Virtual Server Name (status 138f)


    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 4b 4a 00 40 01 00 00 00   KJ.@....
    0008: 09 00 00 00 53 00 51 00   ....S.Q.
    0010: 4c 00 76 00 73 00 30 00   L.v.s.0.
    0018: 32 00 62 00 00 00 00 00   2.b.....
    0020: 00 00                     ..     

    Event Type: Error
    Event Source: MSSQL$SQLvs02b
    Event Category: (3)
    Event ID: 19019
    Date:  12/7/2008
    Time:  8:32:42 PM
    User:  N/A
    Computer: MLBN-SQLN01
    Description:
    [sqsrvres] GetVirtualServerName, Unable to obtain next Resource from Cluster Resource Enumerator. Error: 3f0.


    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 4b 4a 00 40 01 00 00 00   KJ.@....
    0008: 09 00 00 00 53 00 51 00   ....S.Q.
    0010: 4c 00 76 00 73 00 30 00   L.v.s.0.
    0018: 32 00 62 00 00 00 00 00   2.b.....
    0020: 00 00                     ..     

     

    I can find nothing online about "GetVirtualServerName Error 3f0" or "CheckAndChangeVirtualServerName: Could not obtain the Virtual Server Name (status 138f)"

     

    HELP!

     

    Monday, December 08, 2008 1:52 AM

Answers

  • Check your cluster resource groups in windows and make sure that your quorum drives are all available.  I am not a cluster guru, but I will ping someone with this post link who is, and he will reply to it as well.

    Monday, December 08, 2008 4:28 AM
    Moderator
  • Looks like something is missing from the resource group for SQL.

     

    I would bring the cluster group online, leave everything else offline.  Test failover with the cluster group only. 

     

    If that works, bring the individual resources online except the SQL Service and SQL Agent resources. 

     

    Somewhere along this path, you will find which exact resource failed.  My guess is that the LUN zoning got blasted and that one or more hosts cannot see the LUNs.  Usually this is seen by one host seeing the drives and another one not seeing them.

     

    If this is the case, you may need to reboot one or more hosts after fixing the LUN presentation problem.

     

    Feel free to post back with more details.

     

    --GNH

    Monday, December 08, 2008 2:33 PM
    Moderator

All replies

  • Check your cluster resource groups in windows and make sure that your quorum drives are all available.  I am not a cluster guru, but I will ping someone with this post link who is, and he will reply to it as well.

    Monday, December 08, 2008 4:28 AM
    Moderator
  • Looks like something is missing from the resource group for SQL.

     

    I would bring the cluster group online, leave everything else offline.  Test failover with the cluster group only. 

     

    If that works, bring the individual resources online except the SQL Service and SQL Agent resources. 

     

    Somewhere along this path, you will find which exact resource failed.  My guess is that the LUN zoning got blasted and that one or more hosts cannot see the LUNs.  Usually this is seen by one host seeing the drives and another one not seeing them.

     

    If this is the case, you may need to reboot one or more hosts after fixing the LUN presentation problem.

     

    Feel free to post back with more details.

     

    --GNH

    Monday, December 08, 2008 2:33 PM
    Moderator
  •  

    It was an issue with resources (Server Name, IP Address, etc) being removed as dependencies of the SQL Server service.  Once we added them as dependencies in Cluster Administrator, everything came back up.

     

    Thanks for your answers!

     

    Regards,

     

    Marc Jellinek

    • Proposed as answer by RTTAdmin Thursday, March 24, 2011 8:20 AM
    Monday, December 08, 2008 3:37 PM
  • Thanks Marc, it was a dependancy issue aswell on my side once I changed it to the actual cluster name it brought both the sql server & agent back online
    Thursday, March 24, 2011 8:22 AM