|
MarcumLLP
Posts: 31
Joined: 2015-02-10
|
I have a very simple Addin Excel Project. I have all code commented out, so nothing custom is loading and the project builds without error.
However, in the registry my addin keeps resetting from 3 to 2 for LoadBehavior. I checked the adxloader.log file and it says "Hash verification failed".
Below I attached my adxloader.dll.manifest file. The problem I think started when I signed using "Signing Options". I do not have a version in source control because this is a new project I spent the day working on.
Below are the samples of the files. I have tried registering/unregistering multiple times with no success. I also tried removing the "Signing Option" and reregister and still no good.
Pleas help, thank you.
ADXLOADER.DLL.MANIFEST:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<assemblyIdentity name="K1.PlugIn.Excel, PublicKeyToken=7d1dbecfa86607fd" imageRuntimeVersion="v4.0.30319" hash="368DF3F6ADEC3CC12F1D87AD32CC3017" id="K1.PlugIn.Excel" />
<loaderSettings generateLogFile="true" shadowCopyEnabled="false" privileges="user" minOfficeVersionSupported="15" />
<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
<SignedInfo>
<CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315" />
<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />
<Reference URI="#K1.PlugIn.Excel">
<Transforms>
<Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" />
</Transforms>
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<DigestValue>s1WggmGG9THctSzKAm41Mz+Igu8=</DigestValue>
</Reference>
</SignedInfo>
<SignatureValue>R0q6WOZoLz6b9X1kZsmb0tbOIlaV0Lq2oySJc7ab/0dbj4PiXLOBLi6vNNkBoo4JSiSbrhd+oO7MS+pamGJ9xFGMoJeCXe8oz/H9H3FbG3NdoZIditKLKzsLSgI89ww8OyT7oS2DQcxoQJmVXtA+lLDIjOFo46ZDBBJkTpBrcCvYZYlEfwcpPvTuuQvrwqFTZXTcKRO82I+w1lNCnXSFWhuLGwArYb2yCuFP0w1lkhwn8xzSHWDcFMgOb2wQvS4tn1D6siSyErLzDduiivbmxGSVwHd/pRjdhmCLUIgjmSwJzmBpOmHZv/Zk+k/yqC10luzVgYgoztu97DaIcWpaOA==</SignatureValue>
<KeyInfo>
<KeyValue>
<RSAKeyValue>
<Modulus>ofs0gfXD2Svh6uBK5JACnH9IThYPbH7e8ECIeyl4jDzbIYv4LPSzRkBNa5CbLMzRqxDKHsTeZ7skvd9BP45n0GsuI0e4Xz1J6xgBIz9Dp2bt1N3mrivmqnayV0PZUxRmhDlGQuk6LKbUMZfO+h5AvVB9Tu3JpA18WkIMdKObQCFJrx073M+2u184tqoFPPr5BwblOTEFPFlCC8NChmvKOG2QwzRqOpOVbRgXdt6UKD/euKjcx5UOay2uMCPJ5KbJMtsGzLgc1XXP15F3KXB8OaMk+aL2iD2G2T7HW4Csz1sqdXz13So9C3uwRx1IbuGwEdhvyDfDDN+HXWOSOJlxgw==</Modulus>
<Exponent>AQAB</Exponent>
</RSAKeyValue>
</KeyValue>
</KeyInfo>
</Signature>
</configuration>
ADXLOADER.LOG
21:43:54:750 3204 19984 The configuration has been loaded successfully.
21:43:54:750 3204 19984 Runtime version: v4.0.30319.
21:43:54:750 3204 19984 Assembly name: K1.PlugIn.Excel, PublicKeyToken=7D1DBECFA86607FD.
21:43:54:750 3204 19984 Class name: K1_PlugIn_Excel.AddinModule.
21:43:54:750 3204 19984 Registry key: CLSID\{EF6BBE09-9E31-4586-83FB-E69C149DCD1D}.
21:43:54:750 3204 19984 Attempting to create a new instance of the managed add-in class: CLR - v4.0.30319
21:43:54:750 3204 19984 Loading CLR: v4.0.30319.
21:43:54:750 3204 19984 Calling CLRCreateInstance method.
21:43:54:750 3204 19984 Success.
21:43:54:750 3204 19984 Calling GetRuntime method.
21:43:54:750 3204 19984 Success.
21:43:54:750 3204 19984 Checking if the hosting API of .NET Framework v4.0 beta is installed.
21:43:54:750 3204 19984 The hosting API is up to date.
21:43:54:750 3204 19984 Calling GetInterface method for the CorRuntimeHost interface.
21:43:54:750 3204 19984 Success.
21:43:54:750 3204 19984 Starting CLR...
21:43:54:750 3204 19984 Success.
21:43:54:750 3204 19984 Getting the CLR version.
21:43:54:750 3204 19984 The CLR v4.0.30319 has been initialized successfully.
21:43:54:818 3204 19984 Hash verification failed |
|
|
Andrei Smolin
Add-in Express team
Posts: 18829
Joined: 2006-05-11
|
Hello,
Does building the project produce any warning?
Andrei Smolin
Add-in Express Team Leader |
|
|
MarcumLLP
Posts: 31
Joined: 2015-02-10
|
|
No, no warnings or errors. |
|
|
MarcumLLP
Posts: 31
Joined: 2015-02-10
|
Ok, it turns out I had my warnings disabled, I was looking at the build output which said no error. It turns out it looks like the manifest file in the bin directory was set to read-only because of our source control. This looks like it very well might be the cause of the problem, I will continue to trouble shoot and let you know.
Thanks. |
|
|
Sergey Grischenko
Add-in Express team
Posts: 7233
Joined: 2004-07-05
|
Hello,
Thank you for letting us know. |
|
Forums
Topics
Search
Help
Login
Register