Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version !bind + InstanceTransforms = MSI error 2229 #4675

Open
wixbot opened this issue Feb 17, 2015 · 5 comments
Open

Version !bind + InstanceTransforms = MSI error 2229 #4675

wixbot opened this issue Feb 17, 2015 · 5 comments
Milestone

Comments

@wixbot
Copy link

wixbot commented Feb 17, 2015

Binding the Product/Version to an assembly + using InstanceTransforms with UpgradeCode in my installer source.
When I run the installer with MSINEWINSTANCE=1 TRANSFORMS=":i1" to install a new instance,
the windows installer throws a meesage:
DEBUG: Error 2229: Database: . Could not load table 'Upgrade' in SQL query: SELECT UpgradeCode,VersionMin,VersionMax,Language,Attributes,ActionProperty FROM Upgrade

Originally opened by gbignozzivsn

@wixbot
Copy link
Author

wixbot commented Feb 17, 2015

Release changed from v3.8 to v3.x

@wixbot
Copy link
Author

wixbot commented Feb 17, 2015

Bind-time variables are resolved after link time, which is when instance transforms are generated.

@wixbot
Copy link
Author

wixbot commented Jun 29, 2015

I'm also affected by this bug

  1. calculating $(var.MyVersion) using (!bind.FileVersion.MyDllFileID)
  2. applying this $(var.MyVersion) to:
  3. Product/Version attribute
  4. Registry
  5. installdir path

The reason for this is that I need to allow the user to run multiple instances of multiple versions at the same time.

Then when I run the installer to upgrade any of my instances to newer version with the same options as described in bug description, I get exactly the same error.

The only solution for me now is to hardcode the $(var.MyVersion).

Originally posted by michalpenka

@wixbot wixbot added this to the v3.x milestone Dec 20, 2015
@robdalsanto
Copy link

I've hit this in WiX v3.11, so it clearly still is an issue. I found the stackoverflow post that noted it was related to the presence of the MajorUpgrade element in the Product element. I may experiment with using the Upgrade and UpgradeVersion elements, but I suspect the transform is the real issue.

@EricGriffith
Copy link

This is still an issue in WIX 3.11. Not sure about 4.x.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants