Microsoft distributes Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release.
Symptoms
Issue 1
Consider the following scenario. You install a Microsoft SQL Server 2012 AlwaysOn failover cluster instance. Then, you click to select the Data Quality Services (DQS) check box under Database Engine Services on the Feature Selection page. In this scenario, you may encounter the following issues, although you do not receive an error message during the installation.
-
The Start menu shortcut icons for Data Quality Client and for Data Quality Server Installer are missing on the added cluster nodes.
-
Data Quality Services binaries are missing on the added node.
-
If you fail over the instance of SQL Server to the added cluster node and then connect from the Data Quality Client application to the instance, you may receive the following error message:
The Data Quality Services license has expired.Message ID: ServerLicenseExpired
Issue 2
When you try to install Data Quality Services (DQS) by running DQSInstaller.exe on the primary cluster node, the DQSInstaller does not connect to the SQL Server database engine instance to build the DQS catalogs. Additionally, you receive one or more error messages that resemble the following:Error message 1
System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Error message 2
System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Cause
Cause of issue 1
This issue occurs because of bug in the SQL Server Setup program.
Cause of issue 2
This issue occurs because DQSInstaller.exe cannot use the virtual name on the cluster.
Resolution
To resolve this issue, install the following cumulative update. This cumulative update enables support for DQS as part of a clustered SQL Server 2012 setup. DQS in SQL Server 2012 supports installation only in a cluster scenario, without any instance of SQL Server previously installed on the cluster node. To enable support, use one of the following methods:
-
If the failover cluster is already installed and the DQS feature is missing from added or secondary cluster nodes, the SQL Server 2012 installation has to be uninstalled (RemoveNode) and then reinstalled (AddNode) on those nodes by using CU1 update and by following the steps that are described later in this article. Before you uninstall the SQL Server 2012 clustered instance, make sure that you create backups of any user databases. See "Remove Node" details in the following Microsoft Books Online article:
http://msdn.microsoft.com/en-us/library/ms191545(SQL.110).aspx
-
If you do not have an instance of SQL Server 2012 installed, you still should follow the steps that are described later in this article in order to perform the installation and to apply cumulative update package 1 before you run any RTM setup. Then, the cumulative update will be included when you perform a fresh setup on the cluster.Note When you run the SQL Server 2012 setup, you are prompted to the "Scan for Product Updates" step. However, it can find and download only Microsoft General Distribution Release (GDR) and service pack updates. The cumulative update 1 package is not listed. To include cumulative update package 1, you can use the command line to point to the downloaded package for the latest update. To do this, follow these steps:
-
Download the cumulative update package into a local folder or UNC path. For example, download the cumulative update to the following folder:
C:\CU1Update
-
Use one of the following methods to run an .ini file to point the SQL Server 2012 Setup program to the folder in which the cumulative update package is saved:
-
To install SQL Server 2012 together with the DQS feature on the primary cluster node, follow these steps:
-
-
Open a command prompt as an administrator from a new server, and then run the following command:
Setup.exe /action=addnode /updatesource=<Folder path of update EXE>For example, run the following command:
Setup.exe /action=addnode /updatesource=c:\CU1Update
-
Complete the Setup wizard typically. To do this, follow these steps:
-
Click OK to set up support rules.
-
On the Product Updates page, verify that the hotfix package exists, and then click Next.
-
On the Install Setup Files page, click Install.
-
On the following pages, click Next:
-
Support Rules
-
Product Key
-
License Terms
-
Setup Role
-
-
Select Database Engine Services, Data Quality Services, and any other features that you may need,and then click Next.
-
On the Feature Rules page, click Next.
-
On the Instance Configuration page, type the SQL Server network name for the failover cluster, and then click Next.
-
On the Disk Space Requirement page, click Next.
-
On the Cluster Resource Group page, type the name of the SQL Server cluster resource group to which the failover cluster resources will be added, and then click Next.
-
On the Cluster Disk Selection page, select a disk, and click Next.
-
On the Cluster Network Configuration page, check the network settings, and then click Next.
-
On the Service Configuration page, enter service accounts information, and then click Next.
-
On the following pages, click Next:
-
Error Reporting
-
Cluster Installation Rules
-
Ready to Install
-
-
-
-
To install SQL Server 2012 together with the DQS feature on an additional or secondary cluster node, follow these steps:
-
Open a command prompt as an administrator from a new server, and then run the following command:
Setup.exe /action=addnode /updatesource=Folder path of update EXE>For example, run the following command:
setup.exe /action=addnode /updatesource=c:\CU1Update
-
Complete the setup wizard typically. To do this, follow these steps:
-
Click OK to set up support rules.
-
On the Product Updates page, verify that the hotfix pack exists, and then click Next.
-
On the Install Setup Files page, click Install.
-
On the following pages, click Next:
-
Setup Support Rules
-
Product Key
-
License Terms
-
-
On the Cluster Node Configuration page, type the SQL Server network name from the primary cluster node installation (see step 2B7 under the previous bullet point for name of the SQL Server instance), and then click Next.
-
On the following pages, click Next:
-
Error Reporting
-
Add Node Rules
-
Ready to Add Node
-
-
For more information about product updates in the SQL Server 2012 installation, visit the following Microsoft Developer Network (MSDN) website:
General information about product updates in the SQL Server 2012 installation
-
-
-
After the cluster setup has completed successfully (this includes cumulative update package 1) and any requested restarts are complete, you must run DQSInstaller.exe to complete the DQS installation. For more information, visit the following website:
Upgrade DQS: Installing Cumulative Updates or Hotfix Patches on Data Quality Services
-
If you have never run DQSInstaller.exe on the affected instance in the past to build the DQS catalogs, you must run DQSInstaller.exe from the active cluster node to perform the initial DQS configuration.On the active node of the cluster, run the DQSInstaller.exe from the Start Menu > All Programs > Microsoft SQL Server 2012 > Data Quality Services > Data Quality Server Installer. It will detect the virtual server name and configure the DQS catalogs and assemblies on that instance.
-
Or, if you ran the DQSInstaller before you installed cumulative update 1 on the added cluster nodes, you must use the command line to upgrade the DQS catalogs by using DQSInstaller.exe –upgrade switch.
-
You must be logged in as an account that is administrator, and the account must also be a member of the sysadmin role in the corresponding database engine instance of SQL Server 2012.
-
On systems on which UAC is enabled, open a command prompt as Administrator. Start Menu > cmd. Right-click the CMD.exe icon, and then select Run As Administrator.
-
Change the directory to the binn folder for the appropriate instance database engine program files location, such as the following: cd "C:\Program Files\Microsoft SQL Server\MSSQL11.InstanceName\MSSQL\Binn"
-
Run the DQSInstaller.exe upgrade command This command should detect the correct virtual name and instance name to upgrade. DQSInstaller.exe -upgrade
-
-
-
Cumulative update information
The fix for this issue was first released in Cumulative Update 1 for SQL Server 2012. For more information about how to obtain this cumulative update package for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
2679368 Cumulative update 1 for SQL Server 2012Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
DQSInstall.exe detection update
This update package includes the update of DQSInstaller.exe for the detection for clustered instances. After you apply this cumulative update, DQSInstaller.exe will detect the clustered instance based on the following steps:
-
DQSInstaller.exe locates the current instance identifier by using the registry values under the following registry key:
SOFTWARE\Microsoft\Microsoft SQL Server\Instance Name\SQL\
-
DQSInstaller.exe checks if that instance is clustered by using the registry values under the corresponding instance ID key:
SOFTWARE\Microsoft\Microsoft SQL Server\InstanceID\Cluster
-
Based on this key value, if the instance is clustered, the virtual name from this key is used in the SQL connection string. DQSInstaller.exe can use the virtual name to connect to the instance of SQL Server and then build the DQS catalogs. If the instance is not clustered, DQSInstaller.exe will build the SQL Server connection string, depending on the Windows machine name property for the current computer.
-
For named instances, the DQSInstaller.exe connection string is built by suffixing the virtual name or machine name with a backslash and the instance name. For example, machinename\instancename.Note The instance name can be overridden with the -instance command-line argument as a switch for DQSInstaller.exe if the wrong instance name is perceived.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Workaround
To work around these issues, install a SQL Server stand-alone instance on a cluster node, and then enable the DQS feature.
More Information
For more information about MDS support on a clustered installation of SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2683467 FIX: SQL Server 2012 Master Data Services is not supported on a clustered installation of SQL Server 2012For more information about AlwaysOn Failover Cluster instances, visit the following Microsoft Developer Network (MSDN) website:
