List of Bugs Fixed in SQL Server 2012 SP1 – Part 7

SQLServerF1

With every release of SQL Server product or subsequent service packs or Cumulative updates, new bugs are encountered or discovered. Below are some of the bugs which were fixed with the release of SQL Server 2012 Service Pack 1 (SP 1) for Microsoft SQL Server 2012.

SQL Server MSDN Bug Number 1025500
Shared features are not discovered in the feature selection page after you install SQL Server 2012 SP1.
SQL Server MSDN Bug Number 918421
“Try the installation again using a valid copy of the installation package ‘sqlls.msi’.” error when you try to repair SQL Server 2012.
SQL Server MSDN Bug Number 923970
Setup fails with a “path not found” error when you try to install the VSTA_DTLP30.msi file.

SQL Server MSDN Bug Number 931703
You cannot install SQL Server 2012 SP1 because another Windows Installer action is in progress.
SQL Server MSDN Bug Number 967159
The setup process randomly fails with an “access violation” error.
SQL Server MSDN Bug Number 1030137
You cannot uninstall SQL Server 2012 SP1 on Windows 8 if you have not installed the Microsoft .NET Framework 3.5.

SQL Server MSDN Bug Number 959184
An unhandled exception occurs in the Microsoft .NET Framework when you install a second instance of SQL Server 2012.
SQL Server MSDN Bug Number 887176
A previously failed SQL Server installation prevents SQL Server Service Packs or Cumulative Updates from installing successfully.
SQL Server MSDN Bug Number 880222
Adds support for the retry logic in order to bring cluster resources online.
SQL Server MSDN Bug Number 863805
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.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2014

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

Leave a Reply

Your email address will not be published. Required fields are marked *