Bernard,
IIRC, you've been told to turn on the logging on the MSI package installation which you have problems with. Did you do that?
The log would show you more info on what's is going on with the install.
It is most likely that some of the binary files from the package (Dll's, Exe's, etc.) do not have all their dependencies presented
in the image and thus failed to be registered.
So, the point is that you should analyze the dependencies of all the files from the package first, make sure they are in the image
and then only try to install it at run time.
(because of all this work it sometimes makes a good sense to componentize application instead of installing it at run time)
--
Regards,
KM
> Sorry, but I failed in using the following command line: msiexec...
> Additional information to the problem previously expained:
>
> 1/ The component "windows installer service" had been added in the basis
> configuration of *.slx to enable the use of Wizad Installer.
> 2/ When loading the installing program through its setup.exe, the sequences
> are exactly appearing as follows:
> - windows installer
> - installshield Wizard
> - customer information
> - ready to install the program
> - installing software
> - genering script
> - copying new files
> - .... (many other sequences)
> - registering product
> when this sequence is carrying out the following error message is displayed:
>
> "Internal error 2203 E:\windows\installer\98fb.msi,-2137287037".
>
> As a result, the program is uninstalling.
>
> What is the missing componant that drives the "registering product" sequence?
>
> Looking forward to receive a solution to solve this problem
> Thank you for your assitance
>
> Best rgds
> Bernard
|
Similar Threads
