Announcement

Collapse
No announcement yet.

SQL Server 2014 Express

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • SQL Server 2014 Express

    I have an application that has been using Sql Server Express 2008R2.

    I'm trying to it working on Windows 10, which means moving to a more recent version of Sql Server Express (2008 won't run on Windows 10).

    The application works just fine using Sql Server Express 2014, so now it's just a matter of building an installer that will install Sql Server Express 2014.

    SUF doesn't install a SQLExpress 2014 dependency, out of the box, so I went looking, and found this:

    http://www.mindquake.com.br/en/dependencies/sql2014

    The problem? It won't install on Windows 10. Its installer requires .NET 3.5 SP1, and I've not been able to get that to install on Windows 10.

    If I include just the SQLExpress 2014 dependency, when I try to install it I get an error:
    You do not have the Microsoft.NET 3.5 SP1 or greater installed on your system.
    If I include the .NET 3.5.1 dependency, I still get the same error:

    You do not have the Microsoft.NET 3.5 SP1 or greater installed on your system.
    Any ideas what might be going wrong?

    Can anyone point me to a Sql Server Express 2014 dependency package that actually works?

  • #2
    I decided to try the Sql Server 2012 dependency, and gave that a try.

    Now I'm getting an error:

    .NET 3.5 SP1 cannot be installed on this operating system. Requires Windows XP SP2, Windows Server 2003 SP1, Windows XP Professional 64 SP1, Windows Server 2008, or Windows Vista.

    Comment


    • #3
      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.

      Comment


      • #4
        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:

        Click image for larger version

Name:	SCRN-2016-04-02-01.png
Views:	1
Size:	17.3 KB
ID:	284393

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

        Click image for larger version

Name:	SCRN-2016-04-02-02.png
Views:	1
Size:	13.4 KB
ID:	284394

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

        Click image for larger version

Name:	SCRN-2016-04-02-03.png
Views:	1
Size:	5.1 KB
ID:	284395

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

        Click image for larger version

Name:	SCRN-2016-04-02-04.png
Views:	1
Size:	4.0 KB
ID:	284396

        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

        Comment


        • #5
          Originally posted by Ulrich View Post
          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:

          Click image for larger version

Name:	Capture2.PNG
Views:	1
Size:	40.1 KB
ID:	284397

          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.

          Comment


          • #6
            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

            Comment


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

              Comment


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

                Ulrich

                Comment


                • #9
                  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.

                  Comment


                  • #10
                    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.

                    Comment


                    • #11
                      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

                      Comment


                      • #12
                        I'm trying to install the 64-bit version of Sql Server 2014 Express:
                        Click image for larger version

Name:	Capture.PNG
Views:	1
Size:	22.6 KB
ID:	284398

                        My virtual is running Windows 10:
                        Click image for larger version

Name:	Capture1.PNG
Views:	1
Size:	17.0 KB
ID:	284399

                        Before I run the installer, I have no DB packages installed:
                        Click image for larger version

Name:	Capture2.PNG
Views:	1
Size:	10.3 KB
ID:	284400

                        After I run the installer, I have a pile full of DB packages installed, from 2008 to 2014:
                        Click image for larger version

Name:	Capture3.PNG
Views:	1
Size:	30.1 KB
ID:	284401

                        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:
                        Click image for larger version

Name:	Capture4.PNG
Views:	1
Size:	26.3 KB
ID:	284402

                        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

                        Comment


                        • #13

                          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

                          Comment


                          • #14
                            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

                            Comment


                            • #15

                              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

                              Comment

                              Working...
                              X