Thursday, March 5, 2015

Installing a SQL Server 2008 Failover Cluster on Windows Server 2012: Three Additional Steps

There are three additional steps required when installing a SQL Server 2008 Failover Cluster on Windows Server 2012:




Once these additional items are addressed, the Failover Cluster can function as expected.





Bug: SQL Server 2008 Failover Cluster Setup does not show the option to use Service SID on the Cluster Security Policy screen when installing on Windows Server 2012

This bug during SQL 2008 Failover Cluster setup on Windows 2012 is documented here. With this bug, the radio button to choose "Use service SIDs" is completely missing.

The workaround is to continue forward with the setup dialogue without making any selections. This causes setup to default to using Service SIDs.

Thanks to Prashant Kumar for this solution. I have also verified this workaround is good.

There are three additional steps to perform when installing SQL Server 2008 on Windows Server 2012. Please see this post for all three additional steps.







Error: "Rule "Cluster service verification" failed." While installing SQL Server 2008 on Windows Server 2012

To resolve error: "Rule "Cluster service verification" failed." the Failover Cluster Automation Server feature must be installed on each node.

A screen shot showing the error message

In Server Manager, expand Remote Server Administration Tools, expand Feature Administration Tools, expand Failover Clustering Tools, and then click to select Failover Cluster Automation Server.

The screen shot for this step

Reference

There are three additional steps to perform when installing SQL Server 2008 on Windows Server 2012. Please see this post for all three additional steps.

Error: "Rule "Windows Server 2003 FILESTREAM Hotfix Check" failed." When installing a SQL Server 2008 R2 Failover Cluster on Windows Server 2012

This error is seen even if you are not attempting to install FILESTREAM support in your SQL Server Failover Cluster. This Hotfix KB937444 is not valid for Windows Server 2012.


To resolve you need to Slipstream the SQL Server service pack into your installation files.

There are three additional steps to perform when installing SQL Server 2008 on Windows Server 2012. Please see this post for all three additional steps.

Error: "The log for database "x" is not available. Check the event log for related error messages. Resolve any errors and restart the database."

The log for database "x" is not available. Check the event log for related error messages. Resolve any errors and restart the database.

To resolve, follow these steps:

  • Take the database offline.
  • Bring it back online.
  • Run DBCC checkdb to make sure everything is good.
  • Set Auto Close = False.

Friday, October 24, 2014

"An attempt was made to access a socket in a way forbidden by its access permissions" - Database Mail Failure

Database Mail fails with the following error:

"The mail could not be sent to the recipients because of the mail server failure. Exception Message: Could not connect to mail server. (An attempt was made to access a socket in a way forbidden by its access permissions (IP))."

Issue:

A recent McAfee Anti-Virus update began to block programs from sending mail unless they appear on a list of excluded programs. SQL Server Database Mail does not appear on that list by default.

You may see an error in the McAfee logs such as:

Date_Time - (Path)\MSSQL\Binn\DatabaseMail.exe Anti-virus Standard Protection:Prevent mass mailing worms from sending mail (IP)

Fix:

  • Go to the Access Protection Properties in the VirusScan console.
  • Select Anti-Virus Standard Protection.
  • Highlight mass mailing worms, and edit the property. 
  • Add DatabaseMail.exe to the list of excluded programs.

This was seen on SQL Server 2012, though it is relevant to all SQL Server versions using Database Mail and has to do with the McAfee configuration. 

Wednesday, January 22, 2014

Fix: "The specified credentials for the SQL Server service are not valid." error during cluster node installation

While trying to add a node to a SQL Server 2008 R2 cluster, I encountered a problem where the service account credentials were not being accepted during installation. These AD credentials were already in use on the active node.

These are the errors:

[Error Message]
The specified credentials for the SQL Server service are not valid. To continue, provide a valid account and password for the SQL Server service.

[Details]
Microsoft.SqlServer.Configuration.SqlEngine.ValidationException: The specified credentials for the SQL Server service are not valid. To continue, provide a valid account and password for the SQL Server service.
================================================================================

[Error Message]
The credentials you provided for the SQL Server Agent service are invalid. To continue, provide a valid account and password for the SQL Server Agent service.

[Details]
Microsoft.SqlServer.Configuration.Agent.InputValidationException: The credentials you provided for the SQL Server Agent service are invalid. To continue, provide a valid account and password for the SQL Server Agent service.
================================================================================

I knew the AD account credentials I was trying to use were correct. After searching and seeing numerous suggestions such as making sure you have entered the correct password, I decided to follow one of the suggestions: Reboot and try again!

Sure enough, after reboot, the install progressed past the credentials screen without difficulty and the node was added to the cluster.

Since I didn't see the error published along with a concise "do this to fix" response out there, and since several reports of this error were on versions older than SQL 2008 R2, I decided to publish this to hopefully save you some time. One note, make sure that your service account has local admin to the node, at minimum for the duration of the install.