SQL Server 2014 Express

[sayed98]

Yes. If you build a native 64-bit setup, this action will read the 64-bit registry. If you build a 32-bit setup, Registry.DoesKeyExist() will read in the 32-bit registry. If you use a 32-bit setup to install a 64-bit application, the registry keys of that application cannot be found without help using the 32-bit function.



In this case, the registry keys read by will be found at HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\ Microsoft SQL Server.



Not a native speaker myself, so no worries at all.

Ulrich
Please Help I want yor help

[Ulrich]

Is that the function Registry.DoesKeyExist, check in different registry depending on whether the operating system is 32 bits or 64 bits?

Yes. If you build a native 64-bit setup, this action will read the 64-bit registry. If you build a 32-bit setup, Registry.DoesKeyExist() will read in the 32-bit registry. If you use a 32-bit setup to install a 64-bit application, the registry keys of that application cannot be found without help using the 32-bit function.

I'm trying to install 32-bit SQL on a 64-bit Windows Server 2016.
The first time it installs well, but then it does not detect that it is already installed.

In this case, the registry keys read by will be found at HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\ Microsoft SQL Server.

Forgive my English, and I hope you understand my query

Not a native speaker myself, so no worries at all.

[stiton]

Is that the function Registry.DoesKeyExist, check in different registry depending on whether the operating system is 32 bits or 64 bits?

I'm trying to install 32-bit SQL on a 64-bit Windows Server 2016.

The first time it installs well, but then it does not detect that it is already installed.

Forgive my English, and I hope you understand my query

[Ulrich]

Did you deploy a 32-bit or 64-bit server? If you installed a 64-bit version of SQL Server, then you most likely need to use Wow64 plugin in order to query the 64-bit registry keys, or your Registry.DoesKeyExist() will actually check the 32-bit registry, where the keys were not created.

Ulrich

[stiton]

Hello, I am looking for a solution to this problem. If I try to reinstall sql the statement

if (not Registry.DoesKeyExist (HKEY_LOCAL_MACHINE, "SOFTWARE \\ Microsoft \\ Microsoft SQL Server")) then
SetupData.WriteToLogFile ("Info \ tMicrosoft SQL Server 2005 Express Edition Module: Main SQL Server key not found. \ R \ n", true);
return false; end

It does not recognize the registry key that already exists.
Please, someone guides me how to continue.
Thank you

[jdege]

I'm trying to install the 64-bit version of Sql Server 2014 Express:


My virtual is running Windows 10:


Before I run the installer, I have no DB packages installed:


After I run the installer, I have a pile full of DB packages installed, from 2008 to 2014:


If I run the installer again, it reinstalls Sql Server 2014 Express.

And when I look at the installer log, to see why, I see this:


It looks, to me, as if it doesn't find the MSSQL12.SQLEXPRESS key in the registry, so it runs the install again.

The thing is, I do see the following key in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL12.SQLEXPRESS

[Ulrich]

I tested both the x86 and the x64 demo project outputs, and won't get an error with either, on Windows 10 x64 Pro. On the second installation, the SQL Server 2014 Express deployment is skipped as expected, in both cases. Which version of SQL Express are you installing, for what target platform, and using a 32 or 64-bit installer?

Ulrich

[jdege]

Looking the log, I see:

[04/04/2016 17:19:59] Info Microsoft SQL Server 2014 Express Module: Detection script started.
[04/04/2016 17:19:59] Info Microsoft SQL Server 2014 Express Edition Module: MSSQL12.SQLEXPRESS key not found in the registry.

[jdege]

One more thing - the check to see whether Sql Server 2014 is already installed seems not to be working. If I rerun the installer, it runs through the Sql Server 2014 installation again.

[Ulrich]

Thanks for the info. You will find the sample project I mentioned in your Setup Factory 9 projects folder.

Ulrich

[jdege]

I ran the install I downloaded from your site, and it loaded the 2012 project I described.

[Ulrich]

The demo project you mention is not for SQL Server 2014 as the name indicates, and is not included in this package. The demo project for the SQL Server 2014 dependency is named "SQLServer2014Express-DBOnly-TestInstaller.suf" and allows to build both x86 and x64 setups.

Ulrich

[jdege]

I have revised the SQL Server 2014 Express dependency, and it is now compatible with Windows 10. Please download the current version, install it and allow it to download the current installer packages, then build the included demo project.

I was confused, a bit. The sample project that opened was SQL2012_Test.suf, which contained as dependencies Sql Server 2012 SP1 Express edition:



This confused me, but I tried to build it. I got "Error 2090: Dependency file not found N:\CONSULTING\Depen..."

Giving up on the sample project, I added the new dependencies to my project. And everything worked fine.

Thanks.

[Ulrich]

I have revised the SQL Server 2014 Express dependency, and it is now compatible with Windows 10. Please download the current version, install it and allow it to download the current installer packages, then build the included demo project.

I started with removing all existing support for .NET 3.5 from Windows features before running the setup:

As expected, this was shown once the setup was started:

Select to Download and install the feature and continue. After the installation, a reboot of the computer is required:

Perform the reboot and the setup will resume. Microsoft SQL Server Express will be extracted:

After the extraction, the installer will show the installation progress, which will take some time. Eventually the installation of SQL Server 2014 Express will finish and the target system is ready.

I may revise the SQL Server 2012 Express dependency as well eventually, but as only one person ever made a donation for this module, I am not in a hurry to spend my free time on this.

Ulrich

[jdege]

And if I try to install it despite the warning, I'm back to the

You do not have the Microsoft.NET 3.5 SP1 or greater installed on your system.