SQL Server installation error: Could not start the local ScenarioEngine.exe file

I’ve been trying to install SQL Server 2012 Developer Edition for quite some time now. I always get stuck in the installation files, the installation wizard just hides,

Now I looked at the installation log file, which is: SqlSetup_1

I found these errors there

Attempting to start the (null) SQLServer2012 \ x86 \ ScenarioEngine.exe process
Error: failed to start the process
Error: Could not start the local ScenarioEngine.exe file: 0x80070003

Full SqlSetup_1 log:

http://pastebin.com/Ehvi1Nvm

any suggestions?

+6
source share
6 answers

Go to “Uninstall a program” in CP and restore “Configure SQL Server 2012”.

+2
source

I fixed it by going to "Control Panel" → "Programs and Features" → "Local Microsoft SQL Server 2014 Database" → "Restore"

+2
source

I had the same problem after I manually cleared the wild mix of SQL Server versions and instances from my development machine. Actually, I was stuck on this until I found this MSDN blog , which helped me get back on track.

This is what I did.

Add to registry:

[HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Microsoft SQL Server \ 110 \ Bootstrap] "BootstrapDir" = "C: \ Program Files \ Microsoft SQL Server \ 110 \ Setup Bootstrap \"

[HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Microsoft SQL Server \ 110 \ Bootstrap \ Setup] "Patch numbers" = "11.00.2100.60"

Then copy the following files / folder from the media / temp directory to the C folder: \ Program Files \ Microsoft SQL Server \ 110 \ Setup Bootstrap \ SQLServer2012

folder

x64, resources folder, setup.exe.

Change to x86 if necessary.

Cheers, Dennis

0
source

I also had this problem, but I did not see a solution anywhere, so I thought I would contribute. I installed SQL Server in the evaluation version of Windows Server 2012 R2 in hyper v. The server evaluation version lasts 180 days, but it still needs to be activated. If you do not activate it, after 10 days it will restart every hour (I believe that this happens after 180 days). Activation occurs automatically after the computer is connected to the Internet.

What I did was to allow this 10-day period, and I did not connect the machine to the Internet. Then I tried installing SQL Server and got this error. The key was activated by the Windows server. After I activated it, I was able to install SQL Server without any problems.

Please note that the fix above also worked for me. I was able to install SQL Server on Windows Server 2012 R2, which was not activated and took more than 10 days.

Just try something else!

0
source

In my case, this happened because something in C: \ Windows \ Microsoft.NET \ Framework64 \ v2.0.50727 \ CONFIG \ machine.config was corrupted. By attaching the debugger to ScenarioEngine.exe after its failure and looking at the .NET exception, the message was that the configuration section was not understood. I deleted the section containing the line that indicates the exception from both the Framework versions and the Framework64 machine.config, and this fixed the installation.

0
source

I apparently had a hidden unsuccessful installation of SQL 2012, I saw that I had "SQL 2012 Setup" as a program in my installed programs. I uninstalled it and then sql 2014 express installed without problems.

0
source

All Articles