When I try to install SQL Server 2014 on Win Server 2012 R2 as soon as I open the setup.exe it gives an error stating ScenarioEngine.exe has stopped working. Also in the temp setup log I find the below message.

08/23/2015 23:58:21.753 Attempting to run workflow LANDINGPAGE
08/23/2015 23:58:21.753 Attempting to launch process D:\Download\x64\ScenarioEngine.exe
08/23/2015 23:58:41.863 Process returned exit code: 0xE0434F4D
08/23/2015 23:58:41.863 Workflow LANDINGPAGE returned exit code: 0xE0434F4D

Please help me understand what could be causing this issue.

Hi,

Did you read hardware and software requirement for installing SQl Server 2014

This seems issue with .net framework. Can you make sure you have installed all .net framework components. Make sure they are consistent and not corrupt

Hi Sajna,

According to your description, you are trying to install SQL Server 2014 on Windows server 2012 r2 with the error Workflow LANDINGPAGE returned exit code: 0xE0434F4D, right?

.NET 3.5 SP1 is a requirement for SQL Server 2014 when you select Database Engine, Reporting Services, Master Data Services, Data Quality Services, Replication, or SQL Server Management Studio, and it is no longer installed by SQL Server Setup. Based on my research, corrupted installer of .NET Framework will caused this issue. 

In your scenario, please uninstall .NET 3.5 sp1, .NET 3.0 and .NET 2.0 from your server. Verified that all the files were deleted and the registry entries were gone. Reinstall using the .NET 3.5 sp1 package from MS download site. And then check if this issue is persists or not.

Regards,

We do have .net 3.5 (includes 2.0 and 3.0) and 4.5 installed on the server.

Hi Charlie,

How do I check with the .net framework installed is corrupt? I dont find any related error on my event viewer.

I have tried running the .net framework repair tool but that came out with no errors on the server. Is there anything else that could be causing this issue?

http://www.microsoft.com/en-us/download/confirmation.aspx?id=30135

The issue is resolved......After going through all troubleshooting steps, the issue was the SQL Server setup was corrupt. Copying another set of the setup to the server fixed the issue.

• Marked as answer by SajnaAhamed 1 hour 15 minutes ago

The issue is resolved......After going through all troubleshooting steps, the issue was the SQL Server setup was corrupt. Copying another set of the setup to the server fixed the issue.

Thank you for posting the solution