I am trying to repackage an installation, (the software is X1). I made a capture with Wise, and this msi seems to install, appears the shortcut in the desktop and in Start-Programs , but when you try to launch the program appears the following messegge error:

X1 is not properly installed. Please re - install X1 and run again.

Any idea?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Jesica,

I'm not familiar with the software but the error you're getting appears not be a Windows Installer error, but an error from the application you've captured.

Try snapshotting an installation of the software (manual install) over the top of your installed MSI, and then see what the manual install has that your MSI doesn't.

I suspect that something has been missed in the snapshot and when running the program executable it is checking for the existance of registry keys or files that are missing.
*Using ProcMon when launching X1 will tell you which file/registry reads fail with file/key not found*

Hope this points you in the right direction,

Dunnpy
Answered 09/29/2008 by: dunnpy
Red Belt

Please log in to comment
0
ORIGINAL: dunnpy
Try snapshotting an installation of the software (manual install) over the top of your installed MSI, and then see what the manual install has that your MSI doesn't.
This should be part of the packaging process. In time, you'll learn that vendors are essentially bone-idle and will retain functionality in their set-up EXEs which really belongs in the MSI. The only practical way you'll know that is by running the original install over the top of your MSI.. If the vendor's stub extracts and runs an MSI, remember that you'll need to hide the 'Uninstall\[ProductCode]' registry key before re-running the stub, or you'll only ever be prompted for a Modify/repair/Remove'.
Answered 09/30/2008 by: VBScab
Red Belt

Please log in to comment
0
jesica,

Run filemon and regmon tools and exclude all the other process and then try to launch the shortcut you may find to which file or registry is trying to access.Then you can try giving permission to those file or registry and try it out.If this is not working then

using Picture taker tool capture the changes occurs while launching the particular shortcut and find out which files and registries it captured.Then try adding those files and registries to the msi and try it out.Hope this will definitely work.

Karthik
Answered 10/06/2008 by: ak1984
Yellow Belt

Please log in to comment
0
ORIGINAL: ak1984
Run filemon and regmon tools and exclude all the other process
I *hate* to keep banging this drum but ProcMon (from the same author as FileMon and RegMon ) is so far ahead of FM/RM in functionality that the switch to using it is a no-brainer. Not the least of the changes is the removal of the 256-character limit on processes you can add to the Exclude or Include lists. Additionally, you can save the configuration which gets stored in the registry. Once you have a set of exclusions, it's a snap to export the reg key to a .REG and import that into your packaging machines/VMs.
Answered 10/07/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity