When you try to update Microsoft SQL Server 2008 to SQL Server 2008 Service Pack 2 (SP2) on a computer that only has the Microsoft .NET Framework 4 Client Profile installed, the service pack installation fails, and you receive the following error message:
SQL Server 2008 Setup requires Microsoft .NET Framework 4.0 to be installed. Download and install .NET Framework from http://www.microsoft.com/net and then rerun Setup.
The error message resembles the following:
Error messages in SQL Server Setup log files When you examine the Sqlsetup.log that is located in the temporary files folder (%temp%), you see entries that resemble the following:
01/21/2011 11:01:37.415 Checking to see if we need to install .Net version 4.0 01/21/2011 11:01:37.427 Determining the cluster status of the local machine. 01/21/2011 11:01:37.442 The local machine is not configured as a cluster node. 01/21/2011 11:01:37.455 Attempting to find media for .Net version 4.0 01/21/2011 11:01:38.020 .Net version 4.0 needs to be installed from media: c:\2fbc8508d49676c919cb309810466807\ 01/21/2011 11:01:38.032 Error: Unable to find media for .Net version 4.0 01/21/2011 11:12:31.114 Setup closed with exit code: 0x84C40007
Note The Microsoft .NET Framework 4.0 is made up of the .NET Framework 4 Client Profile and the .NET Framework 4 Extended components. These components exist separately in the Programs and Features item in Control Panel or in the Add or Remove Programs item in Control Panel in earlier versions of Windows.
To resolve this problem, obtain the latest service pack for SQL Server 2008. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
968382 How to obtain the latest service pack for SQL Server 2008
This error occurs when the SQL Server Setup program detects that the .NET Framework 4.0 client is installed on the system, and redirects the CLR to load some .NET Framework 4.0 libraries that are only present in the full version of the .NET Framework 4.0.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Microsoft SQL Server 2008 Service Pack 3.