Mark Minasi's Tech Forum
Register Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
Pete

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 17
Reply with quote  #1 
Greetings -
I am running into an issue with error 1196 in the logs. I have followed an article regarding permissions. (option 1) https://blogs.msdn.microsoft.com/alwaysonpro/2014/03/25/create-listener-fails-with-message-the-wsfc-cluster-could-not-bring-the-network-name-resource-online/

 However the issue still remains.

Also attached a screen shot when attempting to create a listener.


Any hints, tips or thoughts?


Attached Images
jpeg 1196err.jpg (234.54 KB, 7 views)

0
cspanburgh

Avatar / Picture

Senior Member
Registered:
Posts: 219
Reply with quote  #2 
Ok, I've done a few SQL clusters before.  Is this all on physical machines or VMs?

Seems from the error you are not getting a response from the service that is bound to the other nodes IP address or it can't be resolved.  Perhaps because the SPN for service was not created within the LDAP Database.    Do you have some more configuration information you can share?

__________________
Curt Spanburgh
0
Pete

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 17
Reply with quote  #3 
Hi Curt,
yes these are VM's. What other information would you like?

I know that the DBA was setting these up (brand new) 2016 SQL. He wanted some assistance when he ran into that error. 
0
cspanburgh

Avatar / Picture

Senior Member
Registered:
Posts: 219
Reply with quote  #4 
Ok, I've done physical machines.  So VMs should be ok since I know Mark has set these up.   I think James Summerlin has done this too.   There has to be more than that SQL error.  It's seems like it's a symptom of something else.
__________________
Curt Spanburgh
0
Pete

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 17
Reply with quote  #5 
Agreed, but trying to figure out what that "something else" is. [wink]

0
cspanburgh

Avatar / Picture

Senior Member
Registered:
Posts: 219
Reply with quote  #6 
MSFT says to check DNS.      The error seems to say it can't resolve.

Resolve

Check DNS configuration

The Network Name resource could not register one or more Domain Name System (DNS) names. If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering." If the event contains an error code that you have not yet looked up, see "Finding more information about error codes that some event messages contain." After reviewing event messages, check the following:

  •  check out the URL.
https://technet.microsoft.com/en-us/library/cc773529(v=ws.10).aspx

Check that on the DNS server, the record for the Network Name resource still exists. If the record was accidentally deleted, or was scavenged by the DNS server, create it again, or arrange to have a network administrator create it.
  • Ensure that a valid, accessible DNS server has been specified for the indicated network adapter or adapters in the cluster.
  • Check the system event log for Netlogon or DNS events that occurred near the time of the failover cluster event. Troubleshooting these events might solve the problem that prevented the clustered Network Name resource from registering the DNS name.

To perform the following procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.

Opening Event Viewer and viewing events related to failover clustering

To open Event Viewer and view events related to failover clustering:

  1. If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
  3. To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources box, select FailoverClustering. Select other options as appropriate, and then click OK.
  4. To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.

Sometimes it's not the car................ It's the road.

__________________
Curt Spanburgh
0
Pete

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 17
Reply with quote  #7 
Bad Key??

Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason:
DNS bad key.
.

Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.

I also meant to add (probably important) is that we use blue cat as our DNS

0
donoli

Senior Member
Registered:
Posts: 533
Reply with quote  #8 
https://blogs.msdn.microsoft.com/alwaysonpro/2014/03/25/create-listener-fails-with-message-the-wsfc-cluster-could-not-bring-the-network-name-resource-online/

I hope that helps.
0
JamesNT

Senior Member
Registered:
Posts: 142
Reply with quote  #9 
Don't forget to check to make sure needed firewall ports are open.

JamesNT

__________________
I miss Windows NT 4.0 Service Pack 4.
0
cspanburgh

Avatar / Picture

Senior Member
Registered:
Posts: 219
Reply with quote  #10 
And network discovery as well.  common mistakes.
__________________
Curt Spanburgh
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.