Trouble with adding a certificate

Aug 11, 2011 at 5:07 AM

I am currently operating NodeXL on a Mac operating parallels, using windows 7 and office 2010. I am unable to add a certificate to trust publisher. I can access the template but there is no functionality or NodeXL menu.I am a newbie to windows OS but have figured out how to get into change the certificate, but unable to get this to work?

I have added the error code below;

************** Exception Text **************
System.Security.SecurityException: The solution cannot be installed because it is signed by a publisher whom you have not yet chosen to trust. If you trust the publisher, add the certificate to the Trusted Publisher list.
   at Microsoft.VisualStudio.Tools.Office.Runtime.OfficeAddInDeploymentManager.VerifyAddInTrust(ClickOnceAddInTrustEvidence evidence)
   at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.VerifySecurity(ActivationContext context, Uri manifest, AddInInstallationStatus installState)
   at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn()
The Zone of the assembly that failed was:
MyComputer


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4961 (win7RTMGDR.050727-4900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Microsoft.VisualStudio.Tools.Office.Runtime.v10.0
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.21022.1
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Office.Runtime.v10.0/10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Office.Runtime.v10.0.dll
----------------------------------------
Microsoft.VisualStudio.Tools.Applications.Hosting.v10.0
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.21022.1
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.Hosting.v10.0/10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.Hosting.v10.0.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4962 (win7RTMGDR.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Microsoft.VisualStudio.Tools.Applications.ServerDocument.v10.0
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.21022.1
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.ServerDocument.v10.0/10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.ServerDocument.v10.0.dll
----------------------------------------
Microsoft.VisualStudio.Tools.Applications.Runtime.v10.0
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.21022.1
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.Runtime.v10.0/10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.Runtime.v10.0.dll
----------------------------------------
Microsoft.VisualStudio.Tools.Applications.Runtime.v9.0
    Assembly Version: 9.0.0.0
    Win32 Version: 9.0.30729.4130
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.Runtime.v9.0/9.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.Runtime.v9.0.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4961 (win7RTMGDR.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.4926 built by: NetFXw7
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Deployment
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Deployment/2.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Security
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4951 (win7RTMGDR.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Security/2.0.0.0__b03f5f7f11d50a3a/System.Security.dll
----------------------------------------
System.Xml.Linq
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.4926 built by: NetFXw7
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml.Linq/3.5.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------


Aug 11, 2011 at 3:59 PM

Kevin:

You shouldn't have to know anything about "certificates" to use NodeXL, so something has clearly gone wrong here.

You didn't say if the NodeXL setup program ran without a hitch, but I'm guessing that there was an error message from the setup program, too.  The message you posted indicates that you don't have adequate permission to install software, or at least to install NodeXL.  Are you an administrator on Windows?

Please try this:

1. In Windows Explorer, navigate to the NodeXL program folder.  That will be either "C:\Program Files (x86)\Microsoft Research\Microsoft NodeXL Excel Template" or "C:\Program Files\Microsoft Research\Microsoft NodeXL Excel Template".

2. Double-click this file: "Microsoft.NodeXL.ExcelTemplate.vsto".  What happens?

-- Tony

Aug 12, 2011 at 4:45 PM

As far as I know I am an administrator, when I installed originally there was a brief error 1001(I think)  but for some reason the install continued and prompted that it worked, I did uninstall and reinstall the program twice and both times

it said the install was good. The prompt box did come up with the "Do you want to trust this publisher" and one of them I accidentally pressed no, the others I said to trust. A this point I am unable to delete all of the instances from the computer 

so that I might be able to start over, which does not work, the installer just asks if I want to  repair. I am at a loss...

 

So I went in and opened the file as asked: 

2. Double-click this file: "Microsoft.NodeXL.ExcelTemplate.vsto".  What happens? 

Custumization Installer pop up box opened with:

 "The latest version of this customization is already installed." 

Name: Microsoft.NodeXL.ExcelTemplate

From: Root File location of the VSTO file

Aug 12, 2011 at 6:22 PM
Edited Aug 12, 2011 at 7:13 PM

When you told the setup program that you didn't trust NodeXL, it listened to you.  Unfortunately, it didn't make it easy to recover from a simple mistake.

I'm not sure what state things are in right now, so let's start by getting the program uninstalled.  Please do this:

1. In Windows Explorer, right-click the Setup.exe file and select "Run as administrator."

2. When you are asked whether you want to uninstall or repair the program, say uninstall.

3. In the Windows Start Menu, enter "Programs and Features" in the "Search programs and files" box.

4. In the Programs and Features window, enter "NodeXL" in the "Search Programs and Features" box at the upper-right corner of the window.  If the search results in any NodeXL items, select each of them and click Uninstall.  (There may not be any such items.)

If an error message appears during any of these steps, stop and send me the error message.  If all steps succeed, run the NodeXL Setup.exe program again, this time answering "yes" to all security questions.  You don't have to use the "Run as administrator" right-click option this time.

-- Tony

Aug 12, 2011 at 9:56 PM

I uninstalled form my Mac and also from Windows 7 as you stated and there was no change, I received the same error message as if nothing was uninstalled, should I also uninstall Visual studio? Is there a way to cache the system?  I am at a loss...

Aug 12, 2011 at 10:08 PM

Sorry just to be clear the error message:

************** Exception Text **************
System.Security.SecurityException: The solution cannot be installed because it is signed by a publisher whom you have not yet chosen to trust. If you trust the publisher, add the certificate to the Trusted Publisher list.
   at Microsoft.VisualStudio.Tools.Office.Runtime.OfficeAddInDeploymentManager.VerifyAddInTrust(ClickOnceAddInTrustEvidence evidence)
   at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.VerifySecurity(ActivationContext context, Uri manifest, AddInInstallationStatus installState)
   at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn()
The Zone of the assembly that failed was:
MyComputer

Aug 13, 2011 at 3:48 AM

I don't understand.  Please tell me the following:

1.  Did the uninstall work successfully, without any error messages popping up?

2.  If so, did the setup program run successfully, without any error messages popping up?

3.  If so, may I assume that the error message you just posted pops up when you attempt to run NodeXL from the Windows Start menu?

You should definitely NOT uninstall Visual Studio.

-- Tony

Aug 20, 2011 at 12:29 AM

Both the uninstall and install were successful without any error messages. You're correct that the message posted above comes up  when  I load it from the windows start menu.  Thank  you.

Aug 22, 2011 at 1:16 AM

Kevin:

It looks like your computer is configured to not allow external software like NodeXL to run within Office.  Is this a company or school computer that is maintained by an IT department?

-- Tony

Sep 1, 2011 at 8:39 PM

No it is a personal mac running parallels with the  Windows 7 OS. I would need to alter the configurations myself most likely.  It would have worked if I did not just trust it form the beginning. Would just need to know how to alter any configurations that would allow for the exception for node XL.

Sep 6, 2011 at 11:40 PM
Edited Sep 8, 2011 at 12:20 AM

Kevin:

I don't know what happened.  If you accidentally answer the security question with "no," the setup program is just supposed to stop; it's not supposed to prevent the program from ever being installed again.

But let's check something.  Please look at the "security certificates" on your computer by following these steps:

1. Click the Windows Start button.

2. Type "certmgr.msc" into the Search box, then press Enter.  (More complete instructions are at http://windows.microsoft.com/en-US/windows-vista/View-or-manage-your-certificates.)

3. In the certmgr window, open the Untrusted Certificates\Certificates folder.

4. Do the words "NodeXL" or "Tony" appear anywhere in the list of untrusted certificates?

-- Tony

Sep 22, 2011 at 5:00 PM

So neither "NodeXL" or "Tony"were in the "untrusted Certificates" > Certificates folder. I did attempt a while back to try to add a new certificate for NodeXL, but not sure I attempted correctly. I could attempt again to establish a new certificate. My previous attempts were based on this error message:

Microsoft.VisualStudio.Tools.Office.Runtime.OfficeAddInDeploymentManager.VerifyAddInTrust(ClickOnceAddInTrustEvidence evidence)

Not NodeXL itself. I figured I needed to verify trust for Visual Studio Tools because this is not in the 'Root Certification Folder.'  Initially I wondered if there was an issue with parallels but it is trusted. Would it be easier to take windows OS off my computer and begin again?

 

Kevin

Sep 23, 2011 at 3:36 PM

Kevin:

That seems pretty extreme just to get one program to work, but if you're willing to do that, it's the only solution I know of at this point.

-- Tony