Error 2919 - replacing files
I'm new to packaging and have a question about editing an existing msi package.
I opened an existing msi package for editing with wise package studio - professional edition 6.0. in order to substitute two files. I replaced the two files in "Installation Expert" by deleting the old versions and adding the new versions. After that i compiled and saved the msi.
When i try to install the package i get "internal error 2919".
Any help will appreciated.
TIA
I opened an existing msi package for editing with wise package studio - professional edition 6.0. in order to substitute two files. I replaced the two files in "Installation Expert" by deleting the old versions and adding the new versions. After that i compiled and saved the msi.
When i try to install the package i get "internal error 2919".
Any help will appreciated.
TIA
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Your first lesson - never edit vendor-supplied MSIs. Always use a transform file (MST) to apply customisations. Revert to using the back-up you made [cough, cough...] and start the WPS tool called InstallTailor.
Next lesson - AppDeploy has a look-up page for WI errors here http://www.appdeploy.com/msierrors/
2919 means that the WI engine was unable to find the cabinet file for a compressed file.
Once you have your transform, created by InstallTailor, you can load it into WPS and then add your 2 files. Note that, when WPS compiles, it will create a companion cabinet file which you will need to distribute with the MSI and MST.
Next lesson - AppDeploy has a look-up page for WI errors here http://www.appdeploy.com/msierrors/
2919 means that the WI engine was unable to find the cabinet file for a compressed file.
Once you have your transform, created by InstallTailor, you can load it into WPS and then add your 2 files. Note that, when WPS compiles, it will create a companion cabinet file which you will need to distribute with the MSI and MST.
Posted by:
TalkingMarble
15 years ago
Thank you for your reply.
Sorry for not being clear, but with existing msi package i mean a custom-made msi not a vender-supplied msi.
Does a custom-made msi also require an mst file or is there an easier way to replace two files by a newer version?
Sorry for not being clear, but with existing msi package i mean a custom-made msi not a vender-supplied msi.
Does a custom-made msi also require an mst file or is there an easier way to replace two files by a newer version?
Posted by:
AngelD
15 years ago
As you're using WPS it sounds like you have the quick compile option turned on. Turn it off and re-compile or just delete the old file and compile (the .wsi file).
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.