SQL Server Runtim Fail

sryan10 · Postby **sryan10** » Thu Sep 10, 2015 9:42 am

I am trying to evaluate InstallAware during the free trial period. So I am new to this program. I am attempting to use the Studio edition to set up an install.

For this project I selected the "SQL Server 2012 sp2 Express (x86 and x64 WOW)" Runtime to be a prereq. I first built the install as compressed and it would not run at all. It gave me an error stating that the installer exe was corrupt. I then attempted an uncompressed version (suggested by a thread in the forums) and the installer exe ran without a problem. However, while trying to install the SQL Server prereq it failed. A message box popped up stating that the SQL Server installation failed and should be instead installed by Windows Update.

Is there something I missed in my configuration of the install? As I said, I am new to your program so any guidance would be appreciated.

I am coming from an older version of Installshield. It didn't have SQL 2012 as a prereq option (that came in a later version that we couldn't justify paying the upgrade fee for) so we were forced to install it manually. We got what we needed out of it but it wasn't clean.

Postby **FrancescoT** » Fri Sep 11, 2015 12:45 pm

Dear Sryan,

for what concerns the "SQL Server 2012 sp2 Express" issue, on which OS did you test the generated setup package?
It may be possible that a required pre-requisite is already included with the OS (e.g. latest systems already include Net Framework Runtime) and that probably, such pre-requisite must be activated via "Install-Remove Windows features" and not installed.

- https://support.microsoft.com/en-us/kb/2681562

Regarding the error you had while running the compressed package, this may be caused by an active Anti Virus application.
Please note that a setup package should be digitally signed, in order to skip possible AV problems.

Regards

PLEASE NOTE!
This topic has been moved to the more appropriate "Technical Support" forum.

sryan10 · Postby **sryan10** » Mon Sep 14, 2015 6:22 am

I tried installing it on a Windows 7 32-bit OS. So, no windows features were required (like the ones win8 requires). It also does not have any anti-virus software on it. It's a clean system that we use for testing. It was restored to a basic win 7 OS (with latest windows updates) before I started my testing.

Postby **FrancescoT** » Tue Sep 15, 2015 11:15 am

Dear Sryan10,

the problem you reported has been fixed.
Please download and install the latest trial available (X3 20.04.1).

This update doesn't require personal license file re-generation.

Hope this helps you.

Regards

sryan10 · Postby **sryan10** » Mon Sep 21, 2015 9:23 am

Using the new version you suggested I can build an uncompressed install which no longer has an error. However, the compressed install (which is really what I would want) still gives me an error. The error states: "Cannot start setup - the setup file may be corrupt, or you may have the wrong password. If you downloaded this file please download a fresh copy. If the file is password protected, check your password."

The only difference between the two builds is that I'm changing the Build Type from Uncompressed to Compressed Single EXE. Is there something other option I also need to be selecting?

Postby **FrancescoT** » Mon Sep 21, 2015 12:09 pm

Dear Sryan10,

what you are reporting seems a classic Anti Virus issue.

did you digitally sign the package?

Regards

sryan10 · Postby **sryan10** » Mon Sep 21, 2015 12:14 pm

1) As I mentioned earlier, I'm installing this on a clean system where there is no anti-virus software.
2) Even if this was an anti-virus issue, why wouldn't I get the same error when installing the uncompressed version?
3) As I mentioned earlier I am a complete noob to InstallAware (I am running the trial version). So how would I know if it's "digitally signed". As far as I am aware that is not something I set up. All I have done with this installer so far is try to attach the files and exes I need to install. As I said, it seems to work as long as I build it "uncompressed", but I would rather build it "compressed".

Postby **FrancescoT** » Mon Sep 21, 2015 12:48 pm

Dear Sryan10,

when a compressed package gets executed, its content is first decompressed and extracted to the local temporary folder. So it could happen, that an active security policy or an AV app, alters such target files. With an Uncompressed layout instead, all the required files are already available within the same "setup.exe" path.

A digital signature can be applied to a file (any file) in order to certify its origin. Generally this technique is able to skip possible AV interferences, due the fact that the AV application recognizes the file authenticity from its signature (...however not always). Anyway this is not your case, because I understand that you don't have any signing certificates ( ... which have to be issued from a certificate authority).

BTW, all I have mentioned seems to be not your case ... but it remains the fact that the setup files extracted to the local temporary folder get damaged.

For test purpose, did you try to run the package on a different machine?

Regards

sryan10 · Postby **sryan10** » Mon Sep 21, 2015 1:07 pm

I've tried it on both a Win7 32-bit and a Win7 64-bit. I've tried it on my Virtual PC as well as a brand new out-of-the-box PC. I get the same message whenever I run the compressed exe.

Whenever I run it I verify I am the Administrator and that the UAC is off.

Postby **FrancescoT** » Mon Sep 21, 2015 1:59 pm

Dear Sryan10,

could you please contact me at; support@installaware.com

Regards

sryan10 · Postby **sryan10** » Fri Sep 25, 2015 8:28 am

Turns out the random ico file was the problem. Guess I should have been more careful even though I'm just playing around right now. Thanks for all the help though.