Wise Package Studio 7.3.0.385 SP3
Hi Friends,
I am currently working on a a in-house customer software. The software is large one with many files and registries. All files compressed inside the MSI makes it a whopping 160 MB. I am using WPS 7.0 SP3 as the name of the topic indicates. The package is a simple on to create however compressing all resources within the msi file is a problem. Compilation was successfull but application fails to install.
' The installation package could not be opened. Contact the application vendor and confirm that this is a valid Windows Installer package.'
The same copy with external files or cabs outside options works perfectly.
Has anyone come across such a problem with WPS?
Any suggestions?
Note: Compressed inside is Customer standard [8|]
Cheers
I am currently working on a a in-house customer software. The software is large one with many files and registries. All files compressed inside the MSI makes it a whopping 160 MB. I am using WPS 7.0 SP3 as the name of the topic indicates. The package is a simple on to create however compressing all resources within the msi file is a problem. Compilation was successfull but application fails to install.
' The installation package could not be opened. Contact the application vendor and confirm that this is a valid Windows Installer package.'
The same copy with external files or cabs outside options works perfectly.
Has anyone come across such a problem with WPS?
Any suggestions?
Note: Compressed inside is Customer standard [8|]
Cheers
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
160Mb, whilst large, doesn't really qualify as whopping.
- What does a verbose log tell you?
- Does it fail at the same place each time, e.g. installing a particular file?
- Have you used ProcMon to try and tie down the actual error?
- What does a verbose log tell you?
- Does it fail at the same place each time, e.g. installing a particular file?
- Have you used ProcMon to try and tie down the actual error?
Compressed inside is Customer standardIt's part of your job to educate clients about such pathetically dogmatic decisions. Do they deploy MS Office with internal CABs? Thought not...
Posted by:
India_Repackaging
13 years ago
Hi Ian,
Thanks for your reply.
- The verbose logs tells me 'MainEngineThread is returning 1620'
- Yes, the installation fails on a clean machine without even the start UI.
I moved the compressed msi file to my vmware and it installs perfectly. It does not install from a network (previously I was trying to install it from my host machine).
Is this pertain to the Media settings or is there something else?
- I completely agree that its a part our job to educate customers, however sometimes you have to wait for correct opportunities, in spite of having a case. I have one this time.
Cheers
Thanks for your reply.
- The verbose logs tells me 'MainEngineThread is returning 1620'
- Yes, the installation fails on a clean machine without even the start UI.
I moved the compressed msi file to my vmware and it installs perfectly. It does not install from a network (previously I was trying to install it from my host machine).
Is this pertain to the Media settings or is there something else?
- I completely agree that its a part our job to educate customers, however sometimes you have to wait for correct opportunities, in spite of having a case. I have one this time.
Cheers
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.