I am editing a vendors msi package to include a .exe to add some addition files to the system and some registry keys. I put it in the Execute Defered to Execute Installed Program. I have added the file under the DefaultProgram (which is all the files) Feature. When I run the installation, it doesn't even install the file to the destination directory. I am not sure why this is happening. I have tried logging and there is no reference to the file I am installing anywhere in the log file. Is there something I am doing wrong here? Any advise is welcomed and appreciated.

John Summers
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
John :) This is Dave from NWA LOL!

Is it possible for you to simply populate the files and reg keys into the MSI directly?
Seems a lot simpler than what you're attempting..

Just a thought!

Cheers,

Dave
Answered 11/08/2004 by: daveinmn
Senior Yellow Belt

Please log in to comment
0
First, what are you using to edit the MSI? That will get you more specific help.

Second, if you know what the files & reg keys are, it may be a better option to add these via the File and Registry tables through a transform.

My guess is that the problem lies in the fact that you are trying to apply the .exe to the machine via the files table and then executing it. The sequence must be correct for it to work. Unless you want the .exe to remain on the machine, it may be better to put the .exe into the binary table and execute it from there. In Wise, that's the Execute Program from Installation custom action.
Answered 11/08/2004 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
Hello Dave. I hope things are going well.

I am using Wise Package Studio to edit the MSI. The issue is that I have tried to recapture the package but it won't work. If I use the SMS Installer package of the same capture, it works fine. I have tried converting the SMS install but the new MSI doesn't work. This is what I am doing.

1. Access a web that has a cab file it wants to push down to setup a dll and some registry keys to the winnt\Downloaded Program Files.
2. The program is called Bizflow. I don't know if anyone has had to work with it before but that is the app.
3. When you log in with a standard account, it can't load the cab file because the user doesn't have rights to HKLM.
4. If I capture this push down with SMS Installer, it will compile fine and then when I run it as an admin, then login as the restricted user, the web site will open correctly.
5. If I capture with WPS or conver the SMS Installer to a MSI, it will not work. I login as the restricted account and the web page reports errors.
6. So I decided to put the SMS Installer in the MSI to run to setup the files and it won't even install the file to the machine much less execute the exe. I put this file into the vendors MSI using a transform and directly into the MSI. Neither worked.

So that is my problem. I hope this helps. Thank ya'll for responding.

John Summers
jsummers@ingdirect.com
Answered 11/09/2004 by: johndsummers
Senior Yellow Belt

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