Problem while installing on client PC

[convay89]

Hi there,

I run into a problem when installing our application on the clients PC. On every machine I tried to run the installer (VM and also several notebooks of the company), it works like a charm, but when the installer will be executed on the client PC, the installation fails every time.
During the installation, SQL Server Express 2014 is installed silently and also a custom instance is created. So far so good. When the installation of SQL Server is complete, the installer shall also run a SQL Script on the previously installed instance. According to the verbose log, that is the point, where the installer stops.
I could really need a helping hand.

I attached the verbose log of the client. Maybe you can shed some light.

Regards
Convay89

[Daniel]

Hello and welcome to our forums,

Accordingly to the MSI install log there was an issue with establishing the ODBC connection with the SQL server. Could you please manually test the ODBC connection parameters (Server, username, password, database name, etc) and make sure the ODBC parameters are correctly set? For instance, please make sure that during prerequisite installation the SQL Server was not configure to listen on a different port than the default one (1433).

Also, could you please enable the "Connection and all its scripts are verbose" and "Log errors to file" option fro your SQL Connection within "SQL Databses" page, rebuild your setup project, test it again on your customer's machine and send us the "AI_SQLScripts.log" file by email to support at advancedinstaller dot com so we can further investigate this?

All the best,
Daniel

[convay89]

Hi Daniel,

thanks for your reply. We were able to circle the problem. Actually, there was an error during "SQL Server Express 2014" install. From the "Details.txt" of the installation Log.

Code: Select all

(01) 2019-07-04 07:50:24 Slp: ----------------------------------------------------------------------
(01) 2019-07-04 07:50:24 Slp: Running Action: MsiTimingAction
(01) 2019-07-04 07:50:24 Slp: ----------------------------------------------------------------------
(01) 2019-07-04 07:50:24 Slp: Running Action: Install_msodbcsql_Cpu64_Action
(01) 2019-07-04 07:50:24 Slp: SetFeaturePropsModifyInstallAction for msodbcsql_Cpu64 
(01) 2019-07-04 07:50:24 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2019-07-04 07:50:24 Slp: Sco: Attempting to open registry subkey 
(01) 2019-07-04 07:50:24 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\RefCount\MSODBCSQL11
(01) 2019-07-04 07:50:24 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2019-07-04 07:50:24 Slp: Sco: Attempting to open registry subkey 
(01) 2019-07-04 07:50:24 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\10.0
(01) 2019-07-04 07:50:24 Slp: Sco: Attempting to get registry value InstallDir
(01) 2019-07-04 07:50:24 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\11.0
(01) 2019-07-04 07:50:24 Slp: Sco: Attempting to get registry value InstallDir
(01) 2019-07-04 07:50:24 Slp: Checkpoint: PREINSTALL_MSODBCSQL_CPU64_ACTION
(01) 2019-07-04 07:50:24 Slp: Not waiting for Windows installer service
(01) 2019-07-04 07:50:24 Slp: Target package: "{A22EED3F-6DB6-4987-8023-6C6B7030E554}"
(01) 2019-07-04 07:50:24 Slp: MSI Error: 1706 An installation package for the product Microsoft ODBC Driver 11 for SQL Server cannot be found. Try the installation again using a valid copy of the installation package 'msodbcsql.msi'.
(01) 2019-07-04 07:50:24 Slp: InstallPackage: MsiInstallProduct returned the result code 1603.
(01) 2019-07-04 07:50:24 Slp: Using MSI error code to detect the retry option: 1706

The driver was not installed and therefore no instance on which the connection should be established. The final result of the Clients PC is still pending. I added the driver as prerequisite and hopefully the installer will now do the trick.

Another question, the mentioned "AI_SQLScripts.log" will be created beneath "%temp%"?

Regards
Convay 89

[Daniel]

Hello,

I am glad you sorted this out.

Yes the "AI_SQLScripts.log" should be created beneath "%temp%" folder location of current Windows account running the installation.

All the best,
Daniel

[convay89]

Hi Daniel,

thanks for your reply, unfortunately the problem still exists.

During installation, the SQL Server 2014 will extract all installation files to a specific user folder "C:\Users\USER\AppData\Roaming\..\..\prerequisites\SQL Server Express 2014\SQLEXPR_x64_ENU". But the problem seems to be, that the file "MSODBCSQL.MSI" won't be extracted.
Manually starting the setup routine, independent of "my" installer, doesn't work either.
SQL Server tries to open the mentioned file and afterwards asking for the location. Manually selecting another Microsoft® ODBC Driver 11 for SQL Server® from "https://www.microsoft.com/en-us/downloa ... x?id=36434" doesn't work either.
The machine responds with the problem, that a newer version of ODBC Driver 11 for SQL Server is already installed and I should deinstall other versions of the driver first. But that won't be a desired option to be honest.
Installing ODBC Driver 13 doesn't do the trick either.
Currently I'm completly clueless, how to perform the installation on the clients PC flawless..
I'm open for any advise.

Regards
Convay89

[convay89]

Hi,

After some troubleshooting and consultation with two system administrators who were also completely unaware, the customer removed each piece of MS-SQL from his machine and restarted the installation. It works flawlessly.
So there was no problem with the installer himself, it was just a problem on the customer's machine.

Greetings
Convay89

[Catalin]

Hello Convay,

Thank you for your followup on this.

We are glad you solved the issue encountered by your customer.

Best regards,
Catalin