Receiving ”Manifest XML signature is not valid” error during installation of MS Excel add-in for 12.20 and later
Question ID: 107046

Does anyone have any ideas about this error?

We want to use this with QC12.53

Trying to install "Microsoft Excel Add-In, Version 12.01 (patch 03) and later" / v. 12.53.94

We want to use version of MS Office (and Excel) is 2010 64-bit.

We get an error and are directed to this file.
Here is the content of the file:


From: file:///C:/Users/JDOE/AppData/Local/Programs/Hewlett-Packard/Addins/HP.ALM.ExcelAddIn.vsto

************** Exception Text **************

System.Deployment.Application.InvalidDeploymentException: Exception reading manifest from file:///C:/Users/SHAWCW/AppData/Local/Programs/Hewlett-Packard/Addins/HP.ALM.ExcelAddIn.vsto: the manifest may not be valid or the file could not be opened. —> System.Deployment.Application.InvalidDeploymentException: Manifest XML signature is not valid. —> System.Security.Cryptography.CryptographicException: SignatureDescription could not be created for the signature algorithm supplied.
at System.Security.Cryptography.Xml.SignedXml.CheckSignedInfo(AsymmetricAlgorithm key)
at System.Security.Cryptography.Xml.SignedXml.CheckSignatureReturningKey(AsymmetricAlgorithm& signingKey)
at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags)
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
— End of inner exception stack trace —
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
— End of inner exception stack trace —
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.GetManifests(TimeSpan timeout)
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn()

Marked as spam
Posted by (Questions: 193, Answers: 14)
Asked on August 2, 2016 4:48 pm
Answers (3)
Private answer

This error seems to be the lack of the HPCodeSigning Certificate on the TrustedPublisher store on the local computer. It was found that the root cause could be related to restrictive settings which would not allow the certificate to be verified.

To solve this problem please perform the following steps:

1. Install MS Excel Add in v12.2x or 12.5x.
2. Browse to C:Program FilesHewlett-PackardAddins (default path).
3. Locate the HPCodeSignining.cer file.
4. Do right click and select ''Install Certificate''.
5. On the next screen select ''Local Machine''.
6. Select ''Place all certificates in the following store''.
7. Browse and select ''Trusted Publishers''.
8. Hit on Next and then on Finish.
9. Open Ms Excel. You would be prompted to install the certificate so please select ''Install'' on the dialog box.

Marked as spam
Posted by (Questions: 4, Answers: 509)
Answered on August 2, 2016 4:53 pm
Private answer

Still issues, even after upgrading to MS Excel 2016. Then tried again with steps provided for certificate.
Still not able to use.

Marked as spam
Posted by (Questions: 193, Answers: 14)
Answered on August 2, 2016 4:54 pm
Private answer

There have been some reported issues related with the newer ''Microsoft Excel Add-In, Version 12.01 (patch 03) and later''/12.53.94 add-in.

Let's try with the previous version ''Microsoft Excel Add-in version 12.20 and later''/12.21.1. You could download it from the link below.

It is compatible and normally works well with QC/ALM 12.53.

Some instructions to follow:

-Uninstall any previous versions of Excel Add-in.

When you perform this action please go to the Control Panel and make sure that the program have been uninstalled.

-Then, restart the machine and application, just to make sure Windows has refreshed the changes.

-After that, please reinstall this other one (Excel Add-in 12.20 and later), and you should now be able use it.

Marked as spam
Posted by (Questions: 4, Answers: 509)
Answered on August 2, 2016 4:59 pm
I installed the v12.20 and later as suggested. This solutions appears to be good. I tested the upload using our MS Excel 2016 and was successful.
( at August 2, 2016 5:01 pm)

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Scroll to Top