Page 1 of 1
Error: \"\"Cannot start setup - the setup file may be...\"
Posted: Wed Nov 18, 2009 7:44 am
by joltman
One of our customers report this error.
"Cannot start setup - the setup file may be corrupt, or you may have the
wrong password. If you downloaded the file, please download a fresh
copy. If the file is password protected, check your password and try again."
He has tried to donwload the installer again but the same error persists.
Please advice.
Posted: Sun Nov 22, 2009 5:17 pm
by neillans
Clear the browser (typically Internet Explorer) cache and try again.
90% of the time, this really is a corrupt download somewhere.
Tried MD5 checks to make sure the file is valid?
Re: Error: \"\"Cannot start setup - the setup file may be...
Posted: Wed Nov 24, 2010 2:03 pm
by afriesen3
Hoping that someone has another idea on this issue. We just hit this problem. It is not a download problem. MD5/SH1 checksums verified. On the systems where the problem occurs, the file properties on the msi file indicate "digital signature is invalid". signtool verify /pa setup.msi does not show a problem.
Any idea what to check?
Thanks,
Aaron
Re: Error: \"\"Cannot start setup - the setup file may be...
Posted: Fri Nov 26, 2010 4:36 pm
by mills
On what OS is the error being seen?
What version of InstallAware?
What kind of build are you using?
Does the message "digital signature is invalid" not appear on other system?
How are you getting the installer to the machine?
Re: Error: \"\"Cannot start setup - the setup file may be...
Posted: Mon Nov 29, 2010 11:31 am
by afriesen3
mills wrote:On what OS is the error being seen?
What version of InstallAware?
What kind of build are you using?
Does the message "digital signature is invalid" not appear on other system?
How are you getting the installer to the machine?
IA 9 (Moya.sp1.061309)
Single file build, with msi extraction, and the msi is signed with signtool.
This is happening on Server 2003 and XP SP3 at a single customer site. It happens downloading via http or ftp. MD5 checksums match, so the download should not be the issue.
I assume the problem is probably a configuration issue at this site, but I have no idea what to look for or suggest they change.