czspc
Posts: 1
Joined: Tue Jul 18, 2017 9:05 am

Fatal Error when installing MS SQL Express as prerequisite

I want to install Microsoft SQL Server Express 2014 as prerequisite and configured it like you can see in attached image. When trying to install the installation fails with following error:

MSI (c) (E8:30) [12:21:07:480]: Connected to service for CA interface.
MSI (c) (E8!D4) [12:21:07:543]: PROPERTY CHANGE: Adding AI_SYSTEM_DPI property. Its value is '96'.
MSI (c) (E8!D4) [12:21:07:543]: PROPERTY CHANGE: Adding AI_SYSTEM_DPI_SCALE property. Its value is '100'.
Action ended 12:21:07: AI_DpiContentScale. Return value 1.
MSI (c) (E8:64) [12:21:07:543]: Doing action: FatalError
Action 12:21:07: FatalError.
Action start 12:21:07: FatalError.
Action ended 12:21:53: FatalError. Return value 1.
MSI (c) (E8:64) [12:21:53:812]: PROPERTY CHANGE: Deleting AI_BOOTSTRAPPER property. Its current value is '1'.
MSI (c) (E8:64) [12:21:53:812]: Doing action: AI_SHOW_LOG
Action 12:21:53: AI_SHOW_LOG.
Action start 12:21:53: AI_SHOW_LOG.
MSI (c) (E8:90) [12:21:53:812]: Invoking remote custom action. DLL: C:\Users\...\AppData\Local\Temp\MSI4C4F.tmp, Entrypoint: LaunchLogFile
Action ended 12:21:53: AI_SHOW_LOG. Return value 1.
MSI (c) (E8:64) [12:21:53:953]: Doing action: FatalError
Action 12:21:53: FatalError.
Action start 12:21:53: FatalError.


I have tried several command line options but the error still occurs. Any ideas?
Attachments
SQL Server Prerequisite.png
SQL Server Prerequisite.png (44.87 KiB) Viewed 13145 times
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Fatal Error when installing MS SQL Express as prerequisite

Hi and welcome to Advanced Installer forums.

I'm not sure why you encounter this problem. Can you please send me the .AIP (project file) and the full verbose log of the installation to support at advancedinstaller dot com, so I can investigate them?

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
theVman
Posts: 13
Joined: Wed Nov 05, 2014 8:02 am

Re: Fatal Error when installing MS SQL Express as prerequisite

Hi

I have found some issues installing "Microsoft SQL Server 2016 Express SP1" as a pre-install.

I have used the sample provided project to look at the mechanism but its not helping in this case as it is sql 2014 x86 installed as a feature.

Is there an update or solution to this issue that can be supplied to this thread please? It may help me trouble shoot my issue.


I have found that the "Install Command Lines" do not accept [variables] %variables% like [TempFolder] and %temp%. Hence the above [SETUPEXEDIR] in the "Install Command Lines" may not resolve for the location of the 'SQLSETUP.INI', which may or may not be related to the error posted.

BUG - Chicken or egg?
Futher to this, using default paths, the SQL Express 2016 'Pre-install' package is copied to the systems [TempFolder], likewise for any 'Additional files' like SQLSETUP.ini. Now these files get copied first before the SQL Express 2016 is invoked. You would think this is simple and straight foward, however the MS SQL Express 2016 pagkage extracts its files to [TempFolder]\SQLEXPR_x64_ENU. So the setup.exe in looking for the SQLSETUP.ini file in [TempFolder]\SQLEXPR_x64_ENU, buts it not there as it was copied by AI to [TempFolder]. SQL Express 2016 fails.
So the obvious solution may be to simply set the 'Additional files' to "SQLEXPR_x64_ENU\SQLSETUP.ini", NOPE, because it creates the folder and installs the file before the MS SQL Express 2016 is invoked and MS will no longer extract to that folder as it already exists. So it defaults to use an random created folder name on C:\9b7e5cbc1b59ad010d377144 and fails as it cant find the SQLSETUP.ini file relative to where its run from.

So what is the work around to get AI to either:
1. in the 'Additional files' section to invoke the SQL setup.exe with the appended folder name [TempFolder]\SQLEXPR_x64_ENU\SQLSETUP.ini
2. variables %variables% and [TempFolder]\SQLEXPR_x64_ENU to be resolved on the commandline
3. copy the 'Additional files' SQLSETUP.ini after invoking the SQL Express 2016 extraction so the [TempFolder]\SQLEXPR_x64_ENU already exists
4. other?



regards
V
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Fatal Error when installing MS SQL Express as prerequisite

Hi,

By default, the prerequisites are not extracted in the %temp% folder, they are extracted to the path specified in the "Download/extraction folder" field from the "Prerequisites" page, "Packages" tab.

So, you can point to the INI file also by using that path in the command line field (e.g. /ConfigurationFile=[AppDataFolder][Manufacturer]\[ProductName]\prerequisites\MyFile.ini - no | character at the beginning of the "[Manufacturer]" and "[ProductName]" properties). This is possible because some properties are resolved on the pre-install stage, too.

Please take a look on the "SQL Server Express Example Installer" thread which debates a similar problem.

Just let me know if you have other questions.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
theVman
Posts: 13
Joined: Wed Nov 05, 2014 8:02 am

Re: Fatal Error when installing MS SQL Express as prerequisite

Eusebiu wrote:Hi,

By default, the prerequisites are not extracted in the %temp% folder, they are extracted to the path specified in the "Download/extraction folder" field from the "Prerequisites" page, "Packages" tab.

So, you can point to the INI file also by using that path in the command line field (e.g. /ConfigurationFile=[AppDataFolder][Manufacturer]\[ProductName]\prerequisites\MyFile.ini - no | character at the beginning of the "[Manufacturer]" and "[ProductName]" properties). This is possible because some properties are resolved on the pre-install stage, too.

Please take a look on the "SQL Server Express Example Installer" thread which debates a similar problem.

Just let me know if you have other questions.

Best regards,
Eusebiu
Hi Eusebiu,

Yes, thats correct. However as stated above in the other thread "my project" uses "[TempFolder]" as the default 'Global Prerequisite Options' folder.
That means all 3 files are copied to "[TempFolder]":
1. no need to specify a 'Folder:' in the 'Main Setup File' option
2. 'Install Command Lines' for the config.ini is simply "/ConfigurationFile=config.ini"

What is the behaviour and outcome that you observe when testing this senario?

regards
V
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Fatal Error when installing MS SQL Express as prerequisite

Hi,

I'm afraid that using the "/ConfigurationFile=config.ini" is not possible because the "config.ini" file is copied before the SQL Bootstrapper extracts its files and the SQL Bootstrapper only allows the extraction in an empty folder.

The SQL Bootstrapper can be in the same folder with the "config.ini" file, but the setup package that it extracts will not be in the same folder so the "/ConfigurationFile=config.ini" command sent to it will not work.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
theVman
Posts: 13
Joined: Wed Nov 05, 2014 8:02 am

Re: Fatal Error when installing MS SQL Express as prerequisite

Eusebiu wrote:Hi,

I'm afraid that using the "/ConfigurationFile=config.ini" is not possible because the "config.ini" file is copied before the SQL Bootstrapper extracts its files and the SQL Bootstrapper only allows the extraction in an empty folder.

The SQL Bootstrapper can be in the same folder with the "config.ini" file, but the setup package that it extracts will not be in the same folder so the "/ConfigurationFile=config.ini" command sent to it will not work.

Best regards,
Eusebiu
Hi Eusebiu,

Yes thats exactly what I I stated above but is in slightly different words. Microsoft SQL Express 2014/2016/2017 ALL extract to "SQLEXPR_x64_ENU" a sub folder of the extraction path set in Advanced Installer. If you set the config.ini to install to "[TempFolder]\SQLEXPR_x64_ENU" then it kills the "Microsoft SQL Express" extraction because it only allows the extraction in an empty folder. Hence "Chicken or egg" comment, doesnt matter what comes first, it will still fail and be broken. Can Advanced Installer detect this known conflict and promt to say "Restricted path" the mutually exclusive path can not be used due to the MS SQL Express installation design.

However this is only half of the problem raised and described.

The second part of the issue is, if you simply set the path to the ini file on the command line to "/ConfigurationFile=[TempFolder]\config.ini", telling the MS SQL Express Setup.exe that the config file is a folder higher, then the command line set in advanced installer is NOT resolved. The path for the config file in the MS SQL Express "Detail_LandingPage" becomes e.g. "Validation for setting 'CONFIGURATIONFILE' failed. Error message: The configuration file 'C:\Users\User1\AppData\Local\Temp\SQLEXPR_x64_ENU\[TempFolder]\config.ini' does not exist. Specify a valid configuration file."
The reason for this is that Advanced Installer is NOT recognizing or passing variables in the commandline of "Pre-install" packages, however it does if it's a "Feature-based" prerequisite.

If I use "hard coded" paths e.g. C:\prerequisites as a "Pre-install' package it all works perfectly, however who in their right minds would ever use hard coded paths for obvious reasons!

Further to this, is your supplied sample project "Installing SQL as feature-based prerequisite with config file" fails to extract the MS SQL Express files with a MS SQL Express error stating that the path is too deep. You need to remove [manufacturer] from all path locations for this project to work correctly.

What is your advice going foward?

regards
V
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Fatal Error when installing MS SQL Express as prerequisite

Hi,

As I mentioned above, some properties are also resolved during the "pre-install" stage and the [TempFolder] is also resolved. I tested this and it worked as expected for me. Do you use the latest version of Advanced Installer? Can you send me your project, so I can take a look of its configurations?

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
theVman
Posts: 13
Joined: Wed Nov 05, 2014 8:02 am

Re: Fatal Error when installing MS SQL Express as prerequisite

Eusebiu wrote:Hi,

As I mentioned above, some properties are also resolved during the "pre-install" stage and the [TempFolder] is also resolved. I tested this and it worked as expected for me. Do you use the latest version of Advanced Installer? Can you send me your project, so I can take a look of its configurations?

Best regards,
Eusebiu

Hi Eusebiu,

I am using 13.1 evaluation on a new clean win8.1 x64 system straight out of the box.

Yes, I know you said that 'some' properties are also resolved during the "pre-install" stage, however [TempFolder] and %temp% are NOT. I have tested this and it is NOT working as expected for me as explained above.

When installing SQL Express as a "pre-install" the properties are not resolved.
When installing SQL Express as a "Feature-based" the properties are resolved.

To further support this the MS SQL Express installation logs even show and prove this to be the case.
When installing SQL Express as a "pre-install" the properties in the MS SQL Express installation log show the 'text' [TempFolder] in the path string. (fails)
When installing SQL Express as a "Feature-based" the properties in the MS SQL Express installation log show the 'Property value' "C:\Users\User1\AppData\Local\Temp" in the path string. (succeeds)

Another supporting factor is that Advanced Installer behaviour when adding 'properties' to the command Line field.
When installing SQL Express as a "Pre-install" the context sensitive properties in the command Line field are NOT triggered (no drop down selection box) and dont resolve to the [RED] colour.
When installing SQL Express as a "Feature-based" the context sensitive properties in the command Line field are triggered (show drop down selection box) and does resolve to the [RED] colour.
AI2.jpg
AI2.jpg (290.17 KiB) Viewed 13024 times
AI1.jpg
AI1.jpg (250.46 KiB) Viewed 13024 times
AI3.jpg
AI3.jpg (253.3 KiB) Viewed 13024 times
I will also email support the files.

regards
V
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Fatal Error when installing MS SQL Express as prerequisite

Hi,

I tested again and the "[TempFolder]" property and the %temp% environment variable work correct on my machine. Actually, the properties supported on the "pre-install" stage also reside on the Windows environment variables that are checked by Advanced Installer at the beginning of the installation, they are not Windows Installer properties. So, please make sure that the %temp% variable is defined on your machine.

I attached a project sample that you can extract to the "D:\" drive and see if it works for you.

Best regards,
Eusebiu
Attachments
Test pre-install.zip
(509.5 KiB) Downloaded 533 times
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
theVman
Posts: 13
Joined: Wed Nov 05, 2014 8:02 am

Re: Fatal Error when installing MS SQL Express as prerequisite

Eusebiu wrote:Hi,

I tested again and the "[TempFolder]" property and the %temp% environment variable work correct on my machine. Actually, the properties supported on the "pre-install" stage also resides on the Windows environment variables that are checked by Advanced Installer at the beginning of the installation, they are not Windows Installer properties. So, please make sure that the %temp% variable is defined on your machine.

I attached a project sample that you can extract to the "D:\" drive and see if it works for you.

Best regards,
Eusebiu

Hi Eusebiu,

I have downloaded your "Test pre-install.zip" project and opened it on my test pc with EXACTLY the same results as I have described above for the context sensitive variable properties.
In fact when I tested your "Test pre-install.zip" project, I simply draged and dropped the 'LaunchPaint' prerequesite from "Pre-install" to "Feature-based" and it all started working.

The other issue is that it displayed an error message and would not compile or run due to a missing "dictionary File' "C:\ProgramData\Caphyon\Advanced Installer\Repository\dictionaries\ui_en.ail"
I do not even have that specific folder on my system from the clean install of Advanced Installer. However I do have one in "C:\Program Files (x86)\Caphyon\Advanced Installer 13.5\dictionaries\ui_en.ail", so I copied the whole "dictionaries" folder to the "C:\ProgramData\Caphyon\Advanced Installer\Repository" and re run the project. Everything just worked. So your project command line "[TempFolder]Your Company\Your Application\prerequisites\TestPicture.png" MUST have resolved correctly.

This might be it, could it be so simple as this? So I immediately closed that project and opened my MS SQL Express project, double checked the command lines to be sure it was the same as your supplied project, and ran it expecting it to be all successful. NOPE it FAILD again with the MS SQL Express installation file log (Detail_LandingPage) showing it failed to find the config.ini file in the following path: "Validation for setting 'CONFIGURATIONFILE' failed. Error message: The configuration file 'C:\Users\User1\AppData\Local\Temp\prerequisites\SQLEXPR_x64_ENU\[TempFolder]\prerequisites\2017_SqlInstall_Server.ini' does not exist. Specify a valid configuration file."

I dont believe that running a bat file to launch mspaint and passing it the image to display via a commandline is emulating the same results as a MS SQL Express project. Sure MSPaint appears to accept the path passed but clearly the MS SQL "Setup.exe" (2017.140.1000.169 - Sql Server Setup Bootstrapper) does NOT.

New Clean install of Win8.1x64 pro from MSDN
New clean install of Advanced Installer 13.1 evaluation
Download MS SQL Express 2017 from Microsoft.
Add SQL Express 2017 as a prereq in Advanced Installer and set it as a "Pre-install" using [TempFolder]\prerequisites
Add the config file as a 'Additional file'
Set the 'install Command Line' to "[TempFolder]\prerequisites\config.ini"
Save>Build>Run

You need to compair "apples" with "apples", so I looked at what else I have on the commandline that may be affecting the passing of [TempFolder]. So I removed everything apart from JUST the command to pass the location of the config.ini file. It WORKED, the [TempFolder]\prerequisites\config.ini was resolved! So its something in the other commandlines that DO work with MS SQL Express (as its works with hard coded paths) but NOT in Advanced Installer.
The other commands are "/qs /SAPWD=tHi5$iS@nOt@mY@ReAl!Sa!Pa%%w0Rd!O.1.2.3"(no this is not my real sa password, just an example of the characters used).

Therefore a character in this string if placed BEFORE a Advanced Installer property eg. [TempFolder] is stopping Advanced Installer from resolving or passing the command line to the next process.
I have found this "http://www.advancedinstaller.com/forums ... hp?t=33417" but that appears to be specific to connecting to an existing SQL Server from AI not Installing and passing commandlines BUT I think they may be related.
If I move the order of the commandline in AI so that the [TempFolder]\prerequisites\config.ini is passed first then followed by the other commandlines it all WORKS as expected.

Is there a list of Reserved or Special characters for Advanced Installer and how or where they can affect the product?

AI4.jpg
AI4.jpg (148.54 KiB) Viewed 13015 times
AI5.jpg
AI5.jpg (78.54 KiB) Viewed 13015 times
AI6.jpg
AI6.jpg (154.3 KiB) Viewed 13015 times
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Fatal Error when installing MS SQL Express as prerequisite

Hi,

Sorry, the sample that I attached contained a repository dialog that is present on my machine, but you could get rid of that error by simply deleting it from the "Translations" page, "Dictionaries" tab. However, I modified it and re-uploaded it to the previous post.

Indeed, there seems to be an Advanced Installer limitation that prevents the expanding of the properties when some characters like "!" and "%" are used before them in the "Install Command Lines" fields of a "pre-install" prerequisite. As you mentioned, the workaround it to first set the path of the configuration file and set other properties that contain special characters at the end of the command line.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”