Problem compiling WSI to MSI
I created a package, Orgplus 6.0 with Wise Package Studio 6.01 version. When I tried to compile the WSI to change it to MSI, it went through and nothing happened -the file still remained WSI. I did it over and over again, same thing. There were two errors in the discription field at that bottom of the Installation Expert screen about 2 files (MSXML2r and MSXML2) that could not be compressed. I copied the files and placed them in the location that they were supposed be, still nothing happened.
Any thought? Please help.
Any thought? Please help.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
Thegunner
17 years ago
Are the files zero in size ? if so delete them from the WSI and trying recompliing.
Posted by:
sikkert
17 years ago
Are you sure that the 2 files exists where Wise is looking for them? To be sure, in Wise, right-click them and check their source. Also, when you compile a wsi, you will still have the wsi, you will just get an MSI as well.
Posted by:
wehttam
17 years ago
The two files were not existing at first but I copied them to those locations but still, no way. Here is the exact error below:
File with key x86_Microsoft.MSXML2R_6bd6b9abf345378f_4.1.0.0_xww_29c3ad6a
located at s:\projects\orgplus6\Windows\WinSxS\x86_Microsoft.MSXML2R_6bd6b9abf345378f_4.1.0.0_x-ww_29c3ad6a
could not be compressed. This may be a temporary file location.
Make sure file x86_Microsoft.MSXML2R_6bd6b9abf345378f_4.1.0.0_xww_29c3ad6a
has a source path.
File with key x86_Microsoft.MSXML2R_6bd6b9abf345378f_4.1.0.0_xww_29c3ad6a
located at s:\projects\orgplus6\Windows\WinSxS\x86_Microsoft.MSXML2R_6bd6b9abf345378f_4.1.0.0_x-ww_29c3ad6a
could not be compressed. This may be a temporary file location.
Make sure file x86_Microsoft.MSXML2R_6bd6b9abf345378f_4.1.0.0_xww_29c3ad6a
has a source path.
Posted by:
aogilmor
17 years ago
sounds like merge module source. delete and re-add them if you can.
Posted by:
sikkert
17 years ago
WinSxS is the Windows Side-by-Side directory, not a merge module source.
I have never used it myself, but it is one of those directories that can be a little tricky.
I don't think you can copy files to the WinSxS directory just like that, you somehow have to "install" them there (I think you use .NET somehow here, not quite sure). Have you tried NOT putting them into you installation, compiling it, then install the MSI to a new machine and see if the files appear there? Also, I think your installation must be set to mixed or .NET, not Win32.
I have never used it myself, but it is one of those directories that can be a little tricky.
I don't think you can copy files to the WinSxS directory just like that, you somehow have to "install" them there (I think you use .NET somehow here, not quite sure). Have you tried NOT putting them into you installation, compiling it, then install the MSI to a new machine and see if the files appear there? Also, I think your installation must be set to mixed or .NET, not Win32.
Posted by:
gizmolala
17 years ago
Y repackage OrgPlus? It normally comes wiv an msi. Try and locate the vendor msi and use transform for any changes u intend to make. Good luck
Giz
Giz
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.