I need to make a simple property change in my .msi i.e. REBOOT=ReallySuppress.I am creating an .mst for this and once I validate this, it gives error : Could not write row in Table "Feature".I have no idea baout this error.When I try to install this .mst file, it gives error : An unexpected error : 2235

Please suggest...

Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

  • This content is currently hidden from public view.
    Reason: Member has been banned from the site
    For more information, visit our FAQ's.
Please log in to comment

Answers

0

You can run a verbose logging during installs to see the actual error and also see this link - http://kb.flexerasoftware.com/selfservice/viewContent.do?externalID=Q107132

On the other hand, I remember encountering a vendor MSI which I had an error also when I tried adding an MST with it despite adding only a few properties in the table. In the end, I was not able to find the reason why and just settled those properties in the command line.

If that REBOOT=ReallySuppress is the only one that you need to add then add it thru command line without creating an MST for that MSI.

Hope this help.

Answered 05/08/2013 by: dj_xest
Fifth Degree Black Belt

  • For a single Public Property change the suggested use of command line is a nice workaround but I guess you have trouble with more transforms? Could you tell us what tool you are using to generate the Transform?
  • hey...i guess it worked now....it was throwing this error while using Wise..I did it via ORCA and it works fine...though didnt understand what the reason could be???
  • Check the one you created in Wise with Orca, I bet it added a lot more that just the REBOOT Public Property - Wise likes to add its own tables and properties that could be causing the issue.
    • Yes...there were lots of things added......most of the times its Orca that does the trick :)
  • This content is currently hidden from public view.
    Reason: Member has been banned from the site
    For more information, visit our FAQ's.
Please log in to comment
Answer this question or Comment on this question for clarity