Repackaging ABN AMRO OffeNet
Add your rating:
Hi,
I'm trying to repackage Officenet Extra 1.5, to deploy through Wininstall.
Software link:
Officenet 1.5 Extra
I download the software from the website, It is an .exe file.
When I run the .exe file, It unpacks an .msi in the temp folder.
When I try to run this MSI, I get an error:
"The installation can not run directly through the MSI package. Run Setup.exe (translated error from dutch)"
I can do an administrative install of the .exe (/v /a), I then have the same issue.
When I open the .msi in DA MSI Studio in the InstallExecuteSequence, there are a lot of checks done.
Also there is a big list of Custom Actions.
As I am new to .MSI packaging I an not sure what to do in order to create a deployable MSI package.
Any tips are welcome.
Thanks.
I'm trying to repackage Officenet Extra 1.5, to deploy through Wininstall.
Software link:
Officenet 1.5 Extra
I download the software from the website, It is an .exe file.
When I run the .exe file, It unpacks an .msi in the temp folder.
When I try to run this MSI, I get an error:
"The installation can not run directly through the MSI package. Run Setup.exe (translated error from dutch)"
I can do an administrative install of the .exe (/v /a), I then have the same issue.
When I open the .msi in DA MSI Studio in the InstallExecuteSequence, there are a lot of checks done.
Also there is a big list of Custom Actions.
As I am new to .MSI packaging I an not sure what to do in order to create a deployable MSI package.
Any tips are welcome.
Thanks.
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
spartacus
18 years ago
You should check out this article first to get around the problem that the MSI will not run directly.
Regards,
Spartacus
Regards,
Spartacus
Posted by:
Marz28
18 years ago
I edited the .msi with Orca to add the ISSETUPDRIVEN=1 option in Propert table.
The .msi does install now! thanks for that.
Only there is a problem. The original setup routine want's the installing person to set some options, like destination directory and a few more.
Since I set the ISSETUPDRIVEN option, these setup questions do not appear anymore.
Resulting that files are installed in the root of ..\program files\
I'd like to put these asnwers for setup in a MST, but that is not possible anymore.
Any ideas?
thanks
The .msi does install now! thanks for that.
Only there is a problem. The original setup routine want's the installing person to set some options, like destination directory and a few more.
Since I set the ISSETUPDRIVEN option, these setup questions do not appear anymore.
Resulting that files are installed in the root of ..\program files\
I'd like to put these asnwers for setup in a MST, but that is not possible anymore.
Any ideas?
thanks
Posted by:
spartacus
18 years ago
The installation folder can, if required, be specified on the command line thus :
msiexec /i <YourMSIName> INSTALLDIR=<Your Desired Installation Folder in quotes>
However, you mention some other settings though, so I think one approach would be to install the original setup.exe on a clean test machine having first set up verbose logging. The instructions for this can be found here.
This should give you a verbose log file in the %temp% folder on that particular machine.
On a second clean test machine, try installing the MSI you have developed - again with verbose logging enabled, which should give you a second verbose log.
You can now compare the two log files paying particular attention to the public properties that are listed at the end of each log file. Look for properties in the first log file that the original setup.exe sets which either are not set, or set to differently in the second log file.
It can be quite tedious to go through, but worth the effort ...
You can then, preferably via a transform, amend/add the properties in your MSI to match those that were set by the original setup.exe.
If there are only a few differences, you can set them via the command line - e.g.
msiexec /i <YourMSIName> INSTALLDIR=<Your Desired Installation Folder in quotes> NAMEOFPROPERTY1="Somevalue", NAMEOFPROPERTY2="Somevalue"
Regards,
Spartacus
msiexec /i <YourMSIName> INSTALLDIR=<Your Desired Installation Folder in quotes>
However, you mention some other settings though, so I think one approach would be to install the original setup.exe on a clean test machine having first set up verbose logging. The instructions for this can be found here.
This should give you a verbose log file in the %temp% folder on that particular machine.
On a second clean test machine, try installing the MSI you have developed - again with verbose logging enabled, which should give you a second verbose log.
You can now compare the two log files paying particular attention to the public properties that are listed at the end of each log file. Look for properties in the first log file that the original setup.exe sets which either are not set, or set to differently in the second log file.
It can be quite tedious to go through, but worth the effort ...
You can then, preferably via a transform, amend/add the properties in your MSI to match those that were set by the original setup.exe.
If there are only a few differences, you can set them via the command line - e.g.
msiexec /i <YourMSIName> INSTALLDIR=<Your Desired Installation Folder in quotes> NAMEOFPROPERTY1="Somevalue", NAMEOFPROPERTY2="Somevalue"
Regards,
Spartacus
Posted by:
Marz28
18 years ago
Hi Spartacus,
I enabled logging on the pc (v option only)
I took a clean pc and installed the app with the .exe and saved the logfiles.
On another clean pc I installed the .MSI with the ISSETUPDRIVEN=1 option set.
Saved the logfiles.
I then compared the logfiles using Deltaview software.
In a .MST i put some of the Property settings that were different between the logfiles.
When I now install the MSI with the MST it installs into the correct folder, but still I am missing some subfolders and I am missing shortcuts.
When I run the exe I get an error that it cannot find .ini files. So the app does not run.
When intalling the app. with the .exe It also asks me which parts of the App should be installed it has 4 options.
I cannot find the options in the logfile though. I also created logfiles with all options selected and with just one.
But i can't seem to find the difference in the logfiles.
You are right! it is a tedious job!
Any hints?
I enabled logging on the pc (v option only)
I took a clean pc and installed the app with the .exe and saved the logfiles.
On another clean pc I installed the .MSI with the ISSETUPDRIVEN=1 option set.
Saved the logfiles.
I then compared the logfiles using Deltaview software.
In a .MST i put some of the Property settings that were different between the logfiles.
When I now install the MSI with the MST it installs into the correct folder, but still I am missing some subfolders and I am missing shortcuts.
When I run the exe I get an error that it cannot find .ini files. So the app does not run.
When intalling the app. with the .exe It also asks me which parts of the App should be installed it has 4 options.
I cannot find the options in the logfile though. I also created logfiles with all options selected and with just one.
But i can't seem to find the difference in the logfiles.
You are right! it is a tedious job!
Any hints?
Posted by:
RobinV
18 years ago
Hi Marz28,
If I remember correctly, the dialog of OfficeNet is in the setup.exe and the answers are parsed to the msi in some way. I stopped looking in to it because I did not have more time and did a repackage. We use the program with a data folder on the network and the program on the workstation. The repackage will not take a lot of time.
Regards,
Robin
If I remember correctly, the dialog of OfficeNet is in the setup.exe and the answers are parsed to the msi in some way. I stopped looking in to it because I did not have more time and did a repackage. We use the program with a data folder on the network and the program on the workstation. The repackage will not take a lot of time.
Regards,
Robin
Posted by:
Marz28
18 years ago
Posted by:
RobinV
18 years ago
Posted by:
Cybermage
16 years ago
Hi everybody,
Better late then never :)
My Report for (re)repackaging ABN-AMRO officenet
-repackage the installation in a msi
-Give M rights to following maps/registry keys:
%ProgramFiles%\OfficeNet Extra
%windir% <- (not recomended)
HKLM\SOFTWARE\ABNAMRO
In september 2008 they had planned version 1.7 of ABN-AMRO officenet that wil work with vista.
http://www.abnamro.nl/nl/zakelijk/officenet_support/actueel.html
Better late then never :)
My Report for (re)repackaging ABN-AMRO officenet
-repackage the installation in a msi
-Give M rights to following maps/registry keys:
%ProgramFiles%\OfficeNet Extra
%windir% <- (not recomended)
HKLM\SOFTWARE\ABNAMRO
In september 2008 they had planned version 1.7 of ABN-AMRO officenet that wil work with vista.
http://www.abnamro.nl/nl/zakelijk/officenet_support/actueel.html

so that the conversation will remain readable.