SQL Server Setup Failed with Error 0x80070002

SQLServerF1

SQL Server Installation most often or not completes smoothly without any problems, but there are many occasions too where it fails and it is not easy to understand the cause and fixing the problem. Below is one such error which causes the SQL Server Setup from not getting installed.

When you run the SQL Server setup install an MS-Dos window may popup and disappears and nothing else happens. Even if you wait for 10 or 15 minutes no further setup wizard would be launched. Generally when the setup has problems at the very initial stage, we will not even be able to find the SQL Server setup logs, but we will find couple of logs and one of it may have some error messages about the cause of the error. You can find the log file by typing the command %temp%/SqlSetup.log from Run window. You may notice an error similar to below.

.Net security policy file does not exist
Attempting to create .Net security policy file
Error: InitializeSqlSetupCodeGroupCore(32bit) failed
Error: InitializeSqlSetupCodeGroup failed: 0x80070002
Setup closed with exit code: 0x80070002

Above error occurs mostly due to problems with the .net framework which may be corrupted. So, to resolve this issue we will have to try fixing the .net framework problems.

Article explains the process about on how to manually remove and then reinstall the.NET Framework. Writing down the steps here as well, so try to follow the steps to fix the issue.

– Click Start, click Run, type installer in the Open box, and then click OK.
– On the View menu in Windows Installer, click Details, right-click the Name column header, and then click Comment.
– Right-click the cached Windows Installer file that has the Microsoft .NET Framework 2.0 RTL x86 enu comment, and then click Repair.
– After the repair process has completed, quit Windows Installer.

Next run the below below steps

– Open a command prompt by choosing Rus-as-Administrator”
– Change the directory to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
– Type below command.
caspol.exe -machine -reset

After following the above steps the issue must have been resolved.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

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

 

Leave a Reply

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