Select the product you need help with
Using SQL Server in Windows 8 and Windows Server 2012 environmentsArticle ID: 2681562 - View products that this article applies to. On This PageSummaryThis article contains guidance about using different versions of Microsoft SQL Server on a computer that is running Windows Server 2012 or Windows 8. The following topics are discussed in this article: Note For more information about a topic, click the link in the "More Information" section.
More informationMicrosoft SQL Server 2005 InformationCollapse this image  To resolve this issue, upgrade or remove the existing SQL Server 2005 instance. For information about how to upgrade SQL Server, visit the following MSDN website: http://msdn.microsoft.com/en-us/library/bb677622.aspx
(http://msdn.microsoft.com/en-us/library/bb677622.aspx )
Note This link points to SQL Server 2012. You can use the version picker tool at the top of the MSDN link (Other Versions) for information on other versions. For information about the Express editions of SQL Server, visit the following Microsoft websites: SQL Server 2012 Service Pack 1 (SP1) Express Edition
(http://www.microsoft.com/en-us/download/details.aspx?id=35579)
SQL Server 2008 R2 Service Pack 2 (SP2) Express Edition
(http://www.microsoft.com/en-us/download/details.aspx?id=30438)
SQL Server 2008 Express Edition
(http://www.microsoft.com/en-us/download/details.aspx?id=1695)
Note You must manually install Service Pack 3
(http://www.microsoft.com/en-us/download/details.aspx?id=27594)
after you install SQL Server 2008 Express Edition. For information about how to uninstall an existing instance of SQL Server 2005, click the article number to view the article in the Microsoft Knowledge Base: 909967 For more information about how to uninstall an existing instance of SQL Server 2005, visit the following MSDN website:
(http://support.microsoft.com/kb/909967/
)
How to manually uninstall an instance of SQL Server 2005 http://msdn.microsoft.com/en-us/library/ms143412(v=SQL.90).aspx
(http://msdn.microsoft.com/en-us/library/ms143412(v=SQL.90).aspx)
Collapse this image  Minimum SQL Server version requirements for Windows Server 2012 or for Windows 8Collapse this image Microsoft SQL Server 2012Collapse this image Note Please check known setup issues when you install SQL Server 2012 on Windows 8 or Windows Server 2012 Collapse this image Microsoft SQL Server 2008 R2Collapse this image Note The RTM installation of the product is supported. But you need to install the respective service packs after the initial Setup is complete. You will see the following message in the Solution Center page: Collapse this image  For more information, click the following article number to view the article in the Microsoft Knowledge Base: 2527041
(http://support.microsoft.com/kb/2527041/
)
How to obtain the latest service pack for SQL Server 2008 R2 Collapse this image Microsoft SQL Server 2008Collapse this image Note The RTM installation of the product is supported. But you need to install the respective service packs after the initial Setup is complete. Your SQL server 2008 installation is not supported unless you apply Service Pack 3 after you install the RTM edition. You will see the following message in the Solution Center page: Collapse this image  For more information, click the following article number to view the article in the Microsoft Knowledge Base: 968382
(http://support.microsoft.com/kb/968382/
)
How to obtain the latest service pack for SQL Server 2008Note The following dialog box appears in SQL Server 2008 R2 and SQL Server 2008 when you run the Setup program: Collapse this image  Collapse this image SQL Server Compact editionsCollapse this image
Collapse this image Collapse this image Support for switching modes in Windows Server 2012Collapse this image Windows Server 2012 has three feature states, or modes:
To switch from Full Server to Minimal Server Interface or Server Core when one or more instances of SQL Server 2012 are installed, you must uninstall SQL Server 2012, switch modes, and then reinstall SQL Server 2012. However, you can turn on SQL Server 2012 installation prerequisites in Full Server mode, switch to Server Core mode, and then install SQL Server 2012. Note Minimal Server is a Server Core installation that has Server Manager and other server tools installed. Therefore, the SQL Server Setup program performs the same installation steps in Windows Server 2012 Minimal Server Interface mode and Server Core mode. Additionally, you can switch between Server Core and Minimal Server when one or more instances of SQL Server 2012 is installed. This is a supported scenario. Note SQL Server Reporting Services 2012 is not supported on Windows Server 2012 Server Core or Windows 2012 Minimal Server Interface mode. You can install SQL Server Reporting Services 2012 on a server that is running Windows Server 2012 in Full Server mode and then switch to Windows Server 2012 Server Core mode. However, this configuration is not supported. Note We recommend that you uninstall all the SQL Server 2012 features that are not supported on a server that is running Windows Server 2012 in Server Core mode. For information about how to do this, visit the following MSDN website: http://msdn.microsoft.com/en-us/library/hh231669.aspx
(http://msdn.microsoft.com/en-us/library/hh231669.aspx)
Note This issue does not apply to SQL Server 2008 or SQL Server 2008 R2. SQL Server 2008 and SQL Server 2008 R2 are not supported in Minimal Server Interface or Server Core modes. For more information about the installation options that are available when you install Windows Server 2012, visit the following TechNet website: http://technet.microsoft.com/en-us/library/hh831786
(http://technet.microsoft.com/en-us/library/hh831786 )
Collapse this image Known SQL Server 2012 setup and migration issuesCollapse this image
http://blogs.msdn.com/b/jason_howell/archive/2012/08/28/how-to-patch-sql-server-2012-setup-with-an-updated-setup-package-using-updatesource-to-get-a-smart-setup.aspx
(http://blogs.msdn.com/b/jason_howell/archive/2012/08/28/how-to-patch-sql-server-2012-setup-with-an-updated-setup-package-using-updatesource-to-get-a-smart-setup.aspx )
Setup issues that can occur when the .Net Framework 3.5 is not enabledCollapse this image On servers where the .NET Framework 3.5 is not already installed or servers where Internet access is restricted, the SQL Server 2012 installation program does not install components that depend on the .NET Framework 3.5. Therefore, the SQL Server 2012 installation may be incomplete. Note For a list of SQL Server 2012 components that depend on the .NET Framework 3.5, see the "Known SQL Server 2012 setup and migration issues" topic. An error message that resembles the following may be displayed during SQL Server 2012 installation when the .NET Framework is not enabled: Collapse this image  Prevention To prevent this issue from occurring, enable the .NET Framework 3.5 on all nodes of the cluster or on the stand-alone server before you install SQL Server 2012. Resolution To resolve this issue on a stand-alone server, enable the .NET Framework 3.5, and then run Setup again to add the additional features. To resolve this issue in a clustered environment, uninstall the incomplete SQL Server 2012 instances, enable the .NET Framework 3.5, and then reinstall SQL Server 2012. Note In a clustered environment, you cannot add the features that were skipped by running SQL Server 2012 Setup again. To resolve this issue on a stand-alone server, enable the .NET Framework 3.5, and then run SQL Server Setup again. Issue 2 - Users are incorrectly prompted to download and install the .NET Framework 3.5 Users may be incorrectly prompted to download and install the .NET Framework 3.5 when they try to install CU1 or CU2. This issue can occur even though the installed components do not depend on the .NET Framework 3.5. Users may receive an error message that resembles the following: Collapse this image  Cause This is a known issue in CU1 and CU2. Note This issue is fixed in Cumulative Update 3 for SQL Server 2012 and later versions. Prevention To prevent this issue, we recommend that you do one of the following:
Issue 3 - Windows application compatibility mode alerts are displayed during a silent install In Windows 8 and Windows Server 2012, the .NET Framework is a Feature-On-Demand (FOD) component. Additionally, the Windows 8 system policy and the Windows Server 2012 system policy require that users be alerted when FOD components are enabled. Note By default, the .NET Framework 4.0 is enabled. However, the .NET Framework 3.5 is disabled. Therefore, a program compatibility mode alert that prompts users to download and install the .NET Framework 3.5 may be displayed during a silent install: Note These program compatibility alerts cannot be suppressed. Screenshots of alerts are shown here: Windows Server 2012 - Full Server Collapse this image  Windows Server 2012 - Server Core Collapse this image  To prevent this issue, the user can enable the .NET Framework 3.5 before they perform a silent installation. Collapse this image Additional SQL Server 2012 setup issuesCollapse this image Consider the following scenario:
An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly ‘System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=xxxxx’ or one of its dependencies.The system cannot find the file specified. (C:\Users\Administrator\AppData\Local\Microsoft_Corporation\LandingPage.exe_StrongName_ ryspccglaxmt4nhllj5z3thycltsvyyx\11.0.0.0\user.config) Collapse this image  This issue occurs because the .NET Framework 4.0 is enabled by default in Windows 8 and Windows Server 2012. Therefore, a .NET Framework 4.0 user configuration file is created when you install SQL Server 2012. Additionally, the .NET Framework 3.5 is enabled during the installation. When you try to install the second instance of SQL Server 2012, the installation defaults to the .NET Framework 2.0 because the .NET Framework 3.5 is already installed. This conflicts with the setting in the user configuration file and causes the unhandled exception. To prevent this issue, delete the User.config file in the following folder before you install the second instance of SQL Server 2012: %userprofile%\AppData\Local\Microsoft_Corporation\LandingPage.exe_StrongName_ryspccglaxmt4nhllj5z3thycltsvyyx\11.0.0.0 Note This issue is scheduled to be fixed in Microsoft SQL Server 2012 Service Pack 1 (SP1). Issue 2 - You cannot install a SQL Server 2012 Failover Cluster with the File Stream Share feature enabled on Windows Server 2012 You may receive an error message that resembles the following when you try to install a new SQL Server 2012 Failover Cluster with the FileStream Share feature enabled on Windows Server 2012: There was an error setting private property 'Security0x20Descriptor' to value 'System.Byte[]' for resource 'SQL Server Filestream share (FILESTREAM)'. Error: There was a failure to call cluster code from a provider. Exception message: Not found. Cause This issue occurs because support for the Security Descriptor property was dropped in Windows Server 2012. Prevention To prevent this issue, install the failover cluster without the FileStream Share feature enabled. After the installation is completed, enable the FileStream Share feature. Resolution To resolve this issue, uninstall the failed cluster instance by using Add/Remove Programs, and then install the failover cluster without the FileStream Share feature enabled. After the installation is completed, enable the FileStream Share feature. Issue 3 - Error during SQL Server 2012 installation: "An attempt was made to load a program with an incorrect format" Consider the following scenario:
Operation failed with 0x8007000B An attempt was made to load a program with an incorrect format Collapse this image  To prevent this issue, install the IIS ASP .NET 3.5 component by using Server Manager before you install SQL Server 2012. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 2748719
(http://support.microsoft.com/kb/2748719/
)
ASP.NET 2.0 and ASP.NET 3.5 do not work after you uninstall ASP.NET 4.5 in Windows 8 or Windows Server 2012Issue 4: You cannot install a SQL Server 2012 Enterprise Edition failover cluster instance Consider the following scenario:
Collapse this image  The details of the error resemble the following: Collapse this image  Cause This issue occurs because the DQ feature is implicitly selected together with the Engine component during the installation. Note The DQ feature is not supported in Server Core mode. Note The issue is fixed in SQL Server 2012 RTM CU3 and SQL Server 2012 Service Pack 1. Resolution To resolve this issue, do one of the following:
Issue 5: Error message when you try to upgrade the cluster node to SQL Server 2012: ”The common properties for resource 'SQL Network Name (<SQL Name>)' could not be saved" For more information about this issue and how to resolve it, click the article number to view the article in the Microsoft Knowledge Base: 2782511
(http://support.microsoft.com/kb/2782511/
)
"The common properties for resource 'SQL Network Name (<SQL Name>)' could not be saved" error when you try to upgrade the cluster node to SQL Server 2012 Collapse this image Collapse this image Known SQL Server 2008 R2 and SQL Server 2008 setup issuesCollapse this image Issue 1 - You cannot uninstall SQL Server 2008 Express Edition or SQL Server 2008 R2 Express Edition You may receive an error message that resembles the following when you try to uninstall SQL Server 2008 R2 or Microsoft SQL Server 2008 Express Edition: The following feature couldn’t be installed: .NET Framework 3.5 (includes .NET 2.0 and 3.0) Collapse this image  Cause This issue is still under investigation. Workaround To work around this issue, do one of the following:
Issue 2 - The "Cluster Service verification" rule fails when you try to install a SQL Server 2008 R2 failover cluster instance When you try to install a SQL Server 2008 R2 failover cluster instance, the installation fails at the "Cluster Service verification" Rule. When you view the details, you receive an error message that resembles the following: Collapse this image  Cause This issue occurs if the COM-based MSClus.dll library is not enabled. Note SQL Server 2008 and SQL Server 2008 R2 cluster Setup programs depend on the COM-based MSClus.dll library. If this library is not enabled on the cluster node, the Setup fails. Resolution To resolve this issue, do one of the following:
Collapse this image Collapse this image SQL Server support for new features in Windows 8 and Windows Server 2012Collapse this image Note Unless noted in the following table, all features of Windows Server 2012 are supported in all the supported versions of SQL server. Collapse this table
Collapse this image How to enable the .Net Framework 3.5 in Windows 8 and Windows Server 2012Collapse this image
How to enable the .NET Framework 3.5 by using Control Panel in Windows 8Collapse this image To enable the .NET Framework 3.5 in Windows 8, follow these steps:
Collapse this image  Collapse this image How to enable the .NET Framework 3.5 by using the Add Roles and Features Wizard in Windows Server 2012Collapse this image
Note If you are using Server Manager in Windows Server 2012 to add a role or feature to a remote server, the computer account on the remote server requires access to the alternate source file path because the deployment operation runs in the SYSTEM context on the target server. Collapse this image Collapse this image SharePoint Integrated Mode for SQL Server Reporting ServicesCollapse this image 2724471
(http://support.microsoft.com/kb/2724471/
)
Windows Server 2012 does not support SharePoint Server 2010 Collapse this image System Center Advisor rule informationCollapse this image Collapse this table
Collapse this image ReferencesFor more information about how to deploy the .NET Framework 3.5, visit the following MSDN website: http://msdn.microsoft.com/library/windows/hardware/hh975396
(http://msdn.microsoft.com/library/windows/hardware/hh975396)
For information about how to use ASP.NET 3.5 and ASP.NET 4.5 in IIS 8.0, visit the following IIS website: http://www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-using-aspnet-35-and-aspnet-45
(http://www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-using-aspnet-35-and-aspnet-45)
For information about issues that can occur after you install ASP.NET 4.5, click the following article number to view the article in the Microsoft Knowledge Base: 2748719
(http://support.microsoft.com/kb/2748719/
)
ASP.NET 2.0 and ASP.NET 3.5 do not work after you uninstall ASP.NET 4.5 in Windows 8 or Windows Server 2012 For more information about new features in Windows Server 2012, visit the following TechNet website: http://technet.microsoft.com/en-us/library/hh831769.aspx
(http://technet.microsoft.com/en-us/library/hh831769.aspx)
For more information about how to install fail over clustering in Windows Server 2012, see the following MSDN website: http://blogs.msdn.com/b/clustering/archive/2012/04/06/10291601.aspx
(http://blogs.msdn.com/b/clustering/archive/2012/04/06/10291601.aspx)
PropertiesArticle ID: 2681562 - Last Review: April 2, 2013 - Revision: 12.0 Applies to
| Article Translations
 |
Back to the top
