Iam working on a vendor msi. It has an msi and also the mst. I took that msi and mst from temp folder and when i tried to compile it iam getting the below mentioned error.
I have read this , but it says that the error is due to upgrading the wise. But i dint upgrade wise, so it is not helping me.

The vendor msi provided is empty , it contains just product code, product name etc but no files,reg,components,feauteres. All the data is in mst itself. I did not understand what is the reason behind it. I beleive that this is not the reason for the error but just wanted to let u know.

I have default type 51 custom action to set allusers profile and users profile in windows application and after compile i will get these in my msi/mst. I think this is the reason for the error. I have added custom actions to mst manually trough tables and tried to compile, even then I am getting the error.

Will any one please let me know how can i get on with this.
Thanks in Advance.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
0
Yes, I think the issue is with Wise upgrade only.

ORIGINAL: naveen.packager
I have added custom actions to mst manually trough tables and tried to compile, even then I am getting the error.


Why not try this step using ORCA? and once you see the install log, you can be sure that its related to Wise only.
Answered 07/19/2011 by: SandeepPanat
Orange Senior Belt

Please log in to comment
0
Hi Sandeep,

Thanks for your reply.
Yes, I think the issue is with Wise upgrade only.
But I did not upgrade WISE.

I have tried that in ORCA, but i could not get the save option(its grayed out) when i do some change to mst.

So I tried the changing the msi first(using ORCA) and saved it, then opened the mst then i can see the changes. It is not allowing to change the mst directly.

I have opened the msi in WPS and added the default custom actions, compiled it, and opened the mst with WPS and compiled the mst. Now it is getting compiled without error.

I don't understand this situation. Why it is not allowing to change the mst but allowing the msi. Is this what I am doing suggestable?

Thanks.
Answered 07/19/2011 by: naveen.packager
Green Belt

Please log in to comment
0
I have added custom actions to mst manually trough tables Do you think, maybe, that the two might be related? Why try and use the tables when your knowledge is presently quite limited? That's what the GUI is there for - to help you avoid using the tables!
Answered 07/19/2011 by: VBScab
Red Belt

Please log in to comment
0
VBScab,

First the reason why I have tried adding the custom actions to mst is thinking that the error is because the mst is not allowing to add the default custom actions which i have in widows application.
So First method I tried is adding the custom actions using GUI in custom actions tab, I am getting the Microsoft Error(Send Report Error).

So after that I tried adding the custom actions trough tables and tried to compile thinking that it should get compiled since the custom actions are already present in the mst, but even then I got the error.

Thanks.
Answered 07/19/2011 by: naveen.packager
Green Belt

Please log in to comment
0
Sounds like the MSI is ticked as blocked, check the properties on the file.

Do you get the same "error" if you try to create an MST on another MSI?
In that case the MSI could either be corrupt or has bad ICE errors that would be needed to solve first before creating the MST.
Answered 07/19/2011 by: AngelD
Red Belt

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