Article ID: 972387 - View products that this article applies to.
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
Consider the following scenario:
In this scenario, you expect that the SQL Server instance remains online on the active node. Instead, you find that the instance actually goes offline.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
To prevent this problem, use one of the following methods:
Note We recommend that you use this method if possible.
Schedule the password change during a maintenance window and change the password of the service accounts on each node of the failover cluster with the instance actively running on that node. The password must be changed through Configuration Manager as discussed in How to: Change the Password of the Accounts Used by SQL Server (SQL Server Configuration Manager).
Note When you change the password of the SQL Server service account by using the configuration manager on the active node, this does not change the password for the service account on the passive node. So if you do not change the password on each of the nodes as mentioned above, when a failover occurs, the service account uses the old password and the services using the account will fail to come online on that node with the following error message:
The SQL Server (MSSQLSERVER) service failed to start due to the following error:
The service did not start due to a logon failureThe MSSQLSERVER service was unable to log on as <Domain\ServiceAcct> with the currently configured password due to the following error:
Login failure: unknown user name or bad password.
Note You can use this method when you cannot afford downtime to make password changes.
If you change the password programmatically by using the WMI Provider for Configuration Manager, find the owner node and connect to it when you get the SQLService Class object.
Refer to the following example script if you use this method:
For more information, see the following:
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 972387 - Last Review: January 6, 2014 - Revision: 2.0