Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


This article lists the bugs that are fixed in Microsoft SQL Server 2012 Service Pack 1 (SP1).


  • Additional fixes that are not documented here may also be included in the service pack.

  • This list will be updated when more articles are released.

  • Mandatory SQL Server 2012 SP1 hotfix

    After you install SQL Server 2012 SP1, you may experience an issue in which Windows Installer starts repeatedly. This issue is described in the following article in the Microsoft Knowledge Base. This article includes a link to a downloadable hotfix that resolves the issue:

    Note It is mandatory that you install this hotfix after you install SQL Server 2012 SP1.

    2793634 Windows Installer starts repeatedly after you install SQL Server 2012 SP1 For more information about this issue, visit the following MSDN website:

    After applying Service Pack 1 for SQL Server 2012 you may encounter a known issue! Details inside…..

For more information about how to obtain SQL Server 2012 service packs, click the following article number to view the article in the Microsoft Knowledge Base:

2755533 How to obtain the latest service pack for SQL Server 2012

More Information

In addition to the fixes that are listed in this article, SQL Server 2012 SP1 includes Microsoft SQL Server 2012 Cumulative Update 1 (CU1) and Microsoft SQL Server 2012 Cumulative Update 2 (CU2). Therefore, SQL Server 2012 SP1 contains the hotfixes that were included in SQL Server 2012 CU1 and in SQL Server 2012 CU2.

For more information about the cumulative update packages that are available for SQL Server 2012, 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

Issues that are fixed in this service pack

For more information about the bugs that are fixed in SQL Server 2012 SP1, click the following article numbers to view the articles in the Microsoft Knowledge Base.

VSTS bug number

KB article number




FIX: Availability group failover takes a long time if a database in the availability group contains a FileTable in SQL Server 2012



FIX: New Availability Group Wizard-generated scripts skip the steps for joining a secondary database to an availability group in SQL Server 2012



FIX: You experience a deadlock condition when you run multiple SSIS packages in SQL Server 2012



FIX: SQL Server Data Quality Client is fr when you try to delete a data quality project after you install Cumulative Update 1 for SQL Server 2012



SQL Server 2012 DQS Export to 64-bit .xls Excel file fails with error



FIX: You cannot install a SQL Server 2012 cluster instance on a Server Core operating system that contains an existing cluster instance



FIX: Master Data Services Add-in for Excel cannot be installed on a computer that has Microsoft Office 2013 installed



FIX: An attribute in a change tracking group is reset and flagged as unchanged in SQL Server 2012 Master Data Services



FIX: "The client version is incompatible with the database version" error when you use MDS to create a web application after you install the cumulative update packages for SQL Server 2012



FIX: "Cannot write into file 'dqs_certificate.cer'" error when you install Data Quality Services on a different path than the instance of SQL Server 2012



FIX: Data Quality Services can be installed in the Standard edition of SQL Server 2012 unexpectedly



An update that improves the Data Quality Services (DQS) installation output log in SQL Server 2012 is available



FIX: Hierarchies are not alphabetically sorted when you explore them by using Master Data Services in SQL Server 2012



You experience slow synchronization between primary and secondary replicas in SQL Server 2012



FIX: Non-yielding scheduler error when outer joining DMVs with a mismatched ON clause in SQL Server 2008 R2 or SQL Server 2012

Resolutions to the following issues are also included in SQL Server 2012 SP1.

VSTS bug number



"View Sample Records" is disabled in the "discovery" process in SQL Server Data Quality Services (DQS).


Vertical scroll of Log Severity data grid is missing in DQS.


New clause is incorrectly added to a previous rule of the current or previous domain in DQS.


Empty "Name" column is not published as NULLin DQS.


A child domain of a composite domain is not formatted when the child domain has a specific formatting.


A read-only user who is in a group that has update permission can perform an update operation.


"IsolatedStorageException" exception when you try to access an entity in Master Data Services in InPrivate Browsing mode in Internet Explorer.


A date time column does not increase for every 20 rows that are updated to the Remote Date Services in SQL Server 2012.


No results are displayed when you search a value in a Hebrew string.


An unhandled exception occurs when you try to sign in to a Data Quality Project in DQS.


"File download failed, check that the export destination file does not already exist" error when you try to export to an Excel file in DQS.


"The given key was not present in the dictionary" error when you approve the changes in a newly-added term-based relation in DQS.


Explicit hierarchies are corrupted because of circular references in SQL Server 2012.


"Windows PowerShell is not installed on this server" error when you launch Configuration Manager.


Installation operation fails when you run the DQSInstaller.exe file to install DQS server if you specify the "&" character in the password for the database master key.


"Failed to save Configuration Name" error when a Windows user whose name has accented characters tries to open a data quality project by using Data Quality Client.


Updated knowledge bases cannot be used in an already-open cleansing project in DQS.


Incorrect error message is displayeds when you try to use Data Quality Client.

Note In this description, the word "displayeds" is a misspelling for the word "displayed."


The sort order is corrupted when you run the [mdm].[udpAttributeSave] stored procedure against an existing attribute in SQL Server 2012.


"Login failed for user '<Domain>\<User>'. Failed to open the explicitly specified database 'DQS_MAIN'. [CLIENT: <local machine>]" error in Master Data Services if DQS is not installed.


Cannot publish business rules when attributes contain "&" in the attribute name in Master Data Services.


An access violation occurs when executing a substring function together with an invalid offset by using remote procedure call (RPC).


"Date Postfix Argument Expected" error if you create a "has changed" business rule for an attribute of "DateTime" type in Master Data Services web UI.


"An unexpected error occurred during the last correction process" error when you try to run DQS data cleansing in SQL Server 2012.


DQS violation error message is hard to understand when you use the Master Data Services Add-in for Microsoft Excel or the Master Data Services web UI.


Cannot hard delete any soft-deleted members from the Master Data Services database.


Incorrect popup message when you create matching policy and then run a data matching project in DQS.


A .NET Framework 4.5-based application freezes instead of handling the exception when you use the Master Data Services Add-in for Excel.


"String or binary data would be truncated" error when the length of a SQL Server Integration Services (SSIS) DQS cleansing component name is longer than 32 characters.


"SQL46010: Incorrect syntax near SPARSE" error in a SQL Server Data Tools (SSDT) project.


The TSqlParser.ParseSubQueryExpressionWithOptionalCTE() method returns NULL for a SELECTstatement that contains a common table expression (CTE) and a pair of parentheses in an SSDT project.


You cannot publish a business rule when the rule contains a "Equals a Concatenated Value" or "Must be Unique" action, and the selected attribute name has more than 128 characters.


Msg 515, Level 16, State 2, Procedure udp_test_Leaf, Line 335 Cannot insert the value NULL into column 'Code', table 'MDS.mdm.tblStgErrorDetail'; column does not allow nulls. INSERT fails" error when you insert the NULL value into a column that allows for code in the tblStgErrorDetail table.


Relationship staging tables do not have an index in the BatchTag column. When there are many records in a batch staging table, a staging process experiences slow performance. SQL Server 2012 SP1 adds an index on the BatchTag column.


SQL Server 2012 SP1 now enables the String values to be converted to the Numeric values.

Resolutions to the following SQL Server deployment platform issues are also included in SQL Server 2012 SP1.

VSTS bug number



An error occurs, and you cannot find the SQL Server Reporting Services instance that you want to upgrade.


Setup program (uninstall or remove node) does not delete a service when the service is marked for deletion.


The 32-bit version of the SQL Server 2012 Express component is not updated when you install SQL Server support on 64-bit versions of Windows.


You cannot uninstall the localized shared feature in SQL Server Service Packs.


FIX: The value of UpdateDescription attribute is empty in the SQL Server 2012 SP1 Express edition slipstream package.


Shared features are not discovered in the feature selection page after you install SQL Server 2012 SP1.


"Try the installation again using a valid copy of the installation package 'sqlls.msi'." error when you try to repair SQL Server 2012.


Setup fails with a "path not found" error when you try to install the VSTA_DTLP30.msi file.


You cannot install SQL Server 2012 SP1 because another Windows Installer action is in progress.


The setup process randomly fails with an "access violation" error.


You cannot uninstall SQL Server 2012 SP1 on Windows 8 if you have not installed the Microsoft .NET Framework 3.5.


An unhandled exception occurs in the Microsoft .NET Framework when you install a second instance of SQL Server 2012.


A previously failed SQL Server installation prevents SQL Server Service Packs or Cumulative Updates from installing successfully.


Adds support for the retry logic in order to bring cluster resources online.


A missing IAcceptSqlServerLicenseTerms entry in the Summary log and an incorrect entry in the Settings.xml file indicate that you have rejected the Microsoft Software License Terms.


The /QS parameter in a command line does not overwrite /QUITESIMPLE =”False” in configuration file when you install SQL Server 2012.


The IP/subnet option is disabled on the Cluster Network Configuration page, and you cannot move to next step.


The setup UI is displayed left-to-right for Hebrew and Arabic languages when you run rsSharePoint.msi.


The Cluster Network Configuration page in the ADDNODE wizard does not show a selected instance's IP addresses if you go back and select a new instance of SQL Server.


The navigation pane is too wide in SQL Server Installation Center.


Adds a rule to warn you if the .NET Framework 3.5 is not installed and if the computer cannot access the Internet.


Setup process does not provide a summary that describes the next steps when you cannot update or remove an update.


You cannot install SQL Server updates through Windows Server Update Services or Microsoft Update on passive nodes of clustered instances.


Adds methods in Service Quality Monitoring (SQM) and in Watson to help you understand why the Setup program cannot install an MSI because of ERROR_PATH_NOT_FOUND code.


Setting validation does not report the correct setting that causes a failure in SQM and in Watson.


FIX: SQM is turned off in SQL Server 2012 Service Pack CTPs.


FIX: Fix the UserGroup.Exists() reporting method in SQM and Watson.


Setup account validation method throws an exception when the Active Directory server is down.


"There was a failure to call cluster code from a provider. Exception message: Generic failure. Status code: 997" error message when you upgrade from SQL Server 2008 R2 SP1 to SQL Server 2012.


"Incorrect SKUs supported" message when you try to install SQL Server in clustered environment.


FIX: Persistent state is set to 1 when an IP address is created in SQL Server Multi-Subnet Clustering.


You cannot upgrade from Microsoft SQL Server 2008 or SQL Server 2008 R2 to SQL Server 2012 on a Windows 8-based cluster.


You cannot uninstall SQL Server 2012 that has dependencies on multiple mount points.


You cannot use the SQL Server slipstream package to update the current feature to Service Pack 1 when you add a new feature at the same time.


The Install wizard freezes when it searches for product updates.


FIX: Master Data Services (MDS) feature is visible in the feature tree when you try to uninstall SQL Server 2012 SP1.


FIX: When you try to update the SQL Server Client Tools or SQL Server Full-Text Search feature by using a corrupted installer file, the feature does not display the correct error message.


Feature selection is unavailable when you install a security update for shared components when the instance component is at a different service pack level.


FIX: Updates SQM to report the service pack level as a number.


FIX: SQL Server service pack applies English to certain features even though these features are installed by using a localized language.


"Exit code:-2068578302" error message when you try to uninstall an instance of SQL Server 2012.


Reporting service is in a bad state after a SQL Server upgrade fails.


For more information about how to determine the current SQL Server version and edition, click the following article number to view the article in the Microsoft Knowledge Base:

321185 How to determine the version and edition of SQL Server and its components

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!