Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4689

Failover Cluster error - "Unable to get ip info for the provider resource"

$
0
0

Hi there.

I'm working my way through the training kit for exam 70-462 - SQL 2012 administration. I'm right at the end of the exercise on failover clustering. It says to do a manual failover from one node to the other, which works. But then you have to fail over back to the original node, and that's where it seems to go wrong for me.

My environment is 2 VMs running Windows Server 2012. The cluster error log seems to suggest there's an IP issue, but validation doesn't pick that up. And google has never even heard of this error! It all goes wrong after these lines:

      • 00000c04.00000700::2013/08/01-14:27:05.210 INFO  [RES] Network Name <SQL Network Name (SQL2012CLUSTER)>: Obtaining IP info for resource SQL IP Address 1 (SQL2012CLUSTER)
      • 00000c04.00000700::2013/08/01-14:27:05.211 INFO  [RES] Network Name <SQL Network Name (SQL2012CLUSTER)>: Using provider SQL IP Address 1 (SQL2012CLUSTER), ip address 10.0.0.120, mask 255.255.255.0, prefix length 24
      • 00000c04.00000700::2013/08/01-14:27:05.211 WARN  [RES] Network Name <SQL Network Name (SQL2012CLUSTER)>: Unable to get provider's transport name, status 2. Checking if the provider is online..
      • 00000c04.00000700::2013/08/01-14:27:05.212 ERR   [RES] Network Name <SQL Network Name (SQL2012CLUSTER)>: Unable to get ip info for the provider resource, status 2
      • 00000c04.00000700::2013/08/01-14:27:05.212 ERR   [RES] Network Name <SQL Network Name (SQL2012CLUSTER)>: Online thread Failed: (2)' because of 'Obtaining IP info for SQL Network Name (SQL2012CLUSTER) failed with error 2.'

      Validation report and cluster logs available here:

      https://skydrive.live.com/redir?resid=92C7C129B2F42162!490&authkey=!AANK8__jmpngy2Y

      Tried a few things that haven't helped:

  1. Restarting all nodes (and DC)
  2. Allow any authenticated user to update DNS records with the same owner name
  3. Change the preferred node so that SQL starts on SQL-D rather than SQL-C
  • Failover using GUI or powershell.

      Any ideas on further steps would be really appreciated.

      Thanks,

      Jon


    1. Viewing all articles
      Browse latest Browse all 4689

      Trending Articles



      <script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>