Because the only documentation I've found regarding this error applies to Windows 2008, I figured I'd post this up in hopes it'll help someone else in the future. If you ever run into the following error(s) when attempting to start a SQL 2008 instance on a Windows 2003 failover cluster, this solution may help you out:
Event Type: Error
Event Source: ClusSvc
Event Category: Network Name Resource
Event ID: 1207
Description:
The computer account for Cluster resource 'SQL Network Name (SQLINSTANCENAME)' in domain domainname.com could not be configured for the following reason:
Unable to update password for computer account
The text for the associated error code is: Access is denied.
The Cluster Service Account may lack the proper access rights to Active Directory. The domain administrator should be contacted to assist with resolving this issue.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-- or --
Description:
The computer account for Cluster resource 'SQL Network Name (SQLINSTANCENAME)' in domain domainname.com could not be configured for the following reason:
Unable to find computer account on DC where it was created
The text for the associated error code is: Directory object not found.
The Cluster Service Account may lack the proper access rights to Active Directory. The domain administrator should be contacted to assist with resolving this issue.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
A resolution that worked for me is either of the following (in order of preference and ease):
- Using a Domain Admin account, find the troublesome computer in "Active Directory Computers and Users", right click the computer name, and choose the option "Enable Account". Bring the SQL Network Name online (if this doesn't work, chances are option 2 will not work for you either, sorry), bring the rest of the SQL Services online.
- If option 1 is not viable (e.g. the computer doesn't show up in "Active Directory Computers and Users"), using Cluster Administrator, right-click the troublesome SQL Network Name resource, click properties, select the Parameters Tab, uncheck "Enable Kerberos Authentication", choose Yes on the prompt, press Ok. Bring the SQL Network Name online (if it doesn't come online at this point, this "fix" doesn't apply to you, sorry). Bring the SQL Network Name offline. Right-Click the SQL Network Name resource, click properties, select the Parameters Tab, check "Enable Kerberos Authentication" option. Click Ok. Bring the SQL Network Name online again. Verify in "Active Direcotry Computers and Users" that the computer name now shows up and bring the rest of SQL Services online through Cluster Administrator.
I believe the cause of my issue was our ill-fated attempt to upgrade a Windows 2003 cluster to a Windows 2008 cluster using the Cluster Migration Wizard. We obviously performed one of the steps in the process incorrectly and this issue happened. At any rate, hopefully someone finds this useful going forward.
- John