Windows Installer package error

I'm trying to install driver software for my high speed camera (lab-material)
but I receive the following error:
"error 1722: there is a problem with this windows installer package. A
program run as part of the setup did not finish as expected. Contact your
support personnel or package vendor"
I'm now using Vista (new pc), is it possible that the company that provided
the driver for the camera still delivers a driver for windows XP. Could it
make a difference? Yet, i downloaded the latest driver possible

Thanks!

benjamin

Hi,

Yes, it's possible. Right click the setup file, use 'run as administrator'
and see if that helps.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"Benjamin" <> wrote in message
news:A8B20E61-D02B-410B-8104-...
> I'm trying to install driver software for my high speed camera
> (lab-material)
> but I receive the following error:
> "error 1722: there is a problem with this windows installer package. A
> program run as part of the setup did not finish as expected. Contact your
> support personnel or package vendor"
> I'm now using Vista (new pc), is it possible that the company that
> provided
> the driver for the camera still delivers a driver for windows XP. Could it
> make a difference? Yet, i downloaded the latest driver possible
>
> Thanks!
>
> benjamin

"Benjamin" <> wrote ...
> I'm trying to install driver software for my high speed camera
> (lab-material)
> but I receive the following error:
> "error 1722: there is a problem with this windows installer package. A
> program run as part of the setup did not finish as expected. Contact your

Hi Benjamin,

The error 1722 is a standard Windows Installer error message; but the
underlying cause will be highly specific to the MSI package you are trying
to install. The vendor has written the package in such a way that it runs an
external program as part of the installation procedure; but the external
program cannot start, for some reason (hence the error).

If the driver is in the form of an MSI file, you may be able to get
additional information by turning on logging. Open a command prompt as
administrator, cd to the directory containing the MSI file, and run this
command:

C:\FOO>msiexec /i <filename>.msi /l*vx logfile.log

This will create a text file called logfile.log in the current directory,
with a very detailed, blow-by-blow description of what the installer is
doing as it runs. After teh error appears, you can examine this file using
Notepad or any other text editor.

If the driver has been packaged as an EXE file, then it's a bit harder. The
EXE may have command line parameters to turn on logging, or else options to
unpack the MSI from the EXE file, so that you can run the MSI on its own (we
know that the core package is an MSI file, because that's why you get a
"1722" error. If it was a different kind of installer you'd get a different
error message).

Even once you've got a log of the problem, you may still need to contact the
vendor of the driver, to confirm their software works on Vista. But the log
will help you understand exactly why it is failing.

Hope it helps,
--
Andrew McLaren
amclar (at) optusnet dot com dot au

Benjamin wrote:
> I'm trying to install driver software for my high speed camera
> (lab-material) but I receive the following error:
> "error 1722: there is a problem with this windows installer package. A
> program run as part of the setup did not finish as expected. Contact
> your support personnel or package vendor"
> I'm now using Vista (new pc), is it possible that the company that
> provided the driver for the camera still delivers a driver for
> windows XP. Could it make a difference? Yet, i downloaded the latest
> driver possible
>
> Thanks!
>

Google lists about a google instances of this error. The error comes from
InstallShield and the cause is not specified. All manner of work-arounds are
provided - depending on what's being installed. Some suggestions/causes
include:

* Specifying a different install directory
* Installation folder with funny characters
* Uninstall previous versions
* .NET is screwed
* JAVA Runtime Environmnet (JRE) error