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
Wrong addin version loaded #10
Comments
The VBS and .EXE installer make the 32-bit / 64-bit determination based upon the following documentation provided by Microsoft: Can you verify the output that is generated from running the following VBA Macro within Excel:
|
I don't seem to be able to open VBA Editor in that Excel - the button is greyed out. However, the product code I gave you comes directly from the installer script - I added a print statement within it. Running your macro in another version of Excel 2016 gives |
The GUID you have supplied appears show up in the registry (on my machine, at least) as the value: for the following key: Having only brief exposure to the MS Office Click-to-Run feature my suspicions are that the machine in question has not performed a full install of Excel, but rather currently has a partial install, with specific features such as VBA automation missing. |
A proper reinstall fixed the issue, so you were probably correct. Thanks! |
One of our test Excel versions is:
The installation of the addin fails with the following error:
Looking at the old VBScript installer, it seems that the 64 bit version is being incorrectly chosen. The logic is this:
I assume it's similar in the EXE installer. However, our
excel.ProductCode
is{9AC08E99-230B-47e8-9721-4577B7F124EA}
, so 64 bit is chosen, even though the Excel is 32 bit.The text was updated successfully, but these errors were encountered: