blind install is not possible ???

  • Thread starter Thread starter barabba
  • Start date Start date
B

barabba

Hi all,

I need to deploy a package to a couple hundreds of computers. I
received the MSI from the vendor. I customized it and ran it.
everything was fine. When I deployed it to a test computer using GP
software installation hang. To troubleshoot, I tried to install it via
commandline using the msiexec /qn switch. I get an installshield error
"blind install is not possible". So do I need to install it manually
on all computers ? has anybody seen this error before ? I haven't...

Thanks
Bar
 
I haven't seen this error message before and I suspect that the setup author
has put it in to prevent silent installation. I'm pretty sure it's not a
general InstallShield issue, but something specific to that package. Maybe
you can contact the author of the package.

--
Stefan Krueger
Microsoft Windows Installer MVP

Please post your questions in the newsgroup or vist one of these web sites:

Windows Installer FAQ
http://www.msifaq.com - http://www.msifaq.de

InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)
 
I agree. This sounds like a message I've seen before. The vendor ha
done things to attempt to prevent silent installations. You may wan
to try runing it with a reduced UI /qr and see if you get the sam
results. If you do, contact the vendor. What app is it by the way?

*Hi all,

I need to deploy a package to a couple hundreds of computers. I
received the MSI from the vendor. I customized it and ran it.
everything was fine. When I deployed it to a test computer using GP
software installation hang. To troubleshoot, I tried to install i
via
commandline using the msiexec /qn switch. I get an installshiel
error
"blind install is not possible". So do I need to install it manually
on all computers ? has anybody seen this error before ? I haven't...

Thanks
Bar
Click to expand...


-
Brady
 
Oh, wait if you're using GP to install you don't have that option. I
would contact the vendor. They may have something they want to run
during the UI sequence. And while on hold, run the MSI quietly and
generate a verbose log to locate the offending action.
 
Like stefan has said it is specific to the installation
and not to the fact that the package is from install
shield. If you have an msi editor then you could open the
msi in it and then check for the custom action that is
causing this and then work around it.

And have u tried other switches like /qb-! for instance.
Most likely this should also not work, but just in case.

The reason the author of the package might have done this
is because there are some information that needs to be
entered compulsarily into the UI, based on which some
decison regarding the installation is taken.

Regards
Suraj
 
Back
Top