no NodeXL tab or document actions

Mar 29, 2014 at 6:38 AM
Hello, I was very excited to discover NodeXL, but have just spent all night installing, disinstalling and reinstalling it, as well as reading your forums, in order to get the NodeXL tab and document actions window customization to appear. Given the message below, I thought I might need Visual Studios, since it didn't show up in a search of my computer, but when I tried to install it, I got only repair or disinstall options. It repaired successfully, but didn't help with installing NodeXL. I'm not a techy, and am at a loss. Below is (most of) the message I receive. Part of it is in French, but I think you'll get the gist of it. I'd really appreciate any help. I'm running Office 10 on Windows 7.

Microsoft.VisualStudio.Tools.Applications.Runtime.CannotCreateCustomizationDomainException: La personnalisation n'a pas pu être chargée, car le domaine d'application n'a pas pu être créé. ---> System.InvalidOperationException: The Add-in store is corrupt. Please use AddInUtil and rebuild this store: C:\Program Files (x86)\Common Files\Microsoft Shared\VSTA\Pipeline.v10.0\PipelineSegments.store ---> System.Runtime.Serialization.SerializationException: Le flux binaire '0' ne contient pas de BinaryHeader valide. Les raisons possibles sont un flux non valide ou une modification de la version de l'objet entre la sérialisation et la désérialisation.
à System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
à System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
à System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
à System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream)
à System.AddIn.Hosting.AddInStore.ReadCache[T](String storeFileName, Boolean mustExist)
--- Fin de la trace de la pile d'exception interne ---
à System.AddIn.Hosting.AddInStore.ReadCache[T](String storeFileName, Boolean mustExist)
à System.AddIn.Hosting.AddInStore.PipelineStateReader(String path, String fileName)
à System.AddIn.Hosting.AddInStore.GetDeploymentState(String path, String storeFileName, Reader reader, Builder stateBuilder)
à System.AddIn.Hosting.AddInStore.GetPipelineDeploymentState(String pipelineRoot)
à System.AddIn.Hosting.AddInStore.FindAddIn(Type hostViewOfAddIn, String pipelineRootFolderPath, String addInFilePath, String addInTypeName)
à Microsoft.VisualStudio.Tools.Applications.AddInStoreExtensions.FindAddIn(AddInInformation addInInformation, String pipelinePath, Type hostAddInView, SegmentConstraints[] segmentConstraints)
à Microsoft.VisualStudio.Tools.Applications.AddInStoreExtensions.FindAddIn(AddInInformation addInInformation, String pipelinePath, Type hostAddInView)
à Microsoft.VisualStudio.Tools.Office.Runtime.DomainCreator.LoadMafPipeline(AppDomain newDomain, IntPtr hostServiceProvider, AddInInformation info, EntryPoints requestedEntryPoints, OfficeApp officeApplication, OfficeVersion officeVersion, IntPtr& executor)
à Microsoft.VisualStudio.Tools.Office.Runtime.DomainCreator.CreateCustomizationDomainInternal(String solutionLocation, String manifestName, String documentName, Boolean showUIDuringDeployment, IntPtr hostServiceProvider, IntPtr& executor)
--- Fin de la trace de la pile d'exception interne ---


************** Assemblys chargés **************
mscorlib
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.5477 (Win7SP1GDR.050727-5400)

CodeBase : file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

Microsoft.VisualStudio.Tools.Office.Runtime.v10.0
Version de l'assembly : 10.0.0.0
Version Win32 : 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

System
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.5467 (Win7SP1GDR.050727-5400)

CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

System.Core
Version de l'assembly : 3.5.0.0
Version Win32 : 3.5.30729.5420 built by: Win7SP1

CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll

System.AddIn
Version de l'assembly : 3.5.0.0
Version Win32 : 3.5.30729.5446 built by: Win7SP1GDR

CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.AddIn/3.5.0.0__b77a5c561934e089/System.AddIn.dll

Microsoft.VisualStudio.Tools.Applications.Hosting.v10.0
Version de l'assembly : 10.0.0.0
Version Win32 : 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

Microsoft.VisualStudio.Tools.Applications.Runtime.v10.0
Version de l'assembly : 10.0.0.0
Version Win32 : 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.ServerDocument.v10.0
Version de l'assembly : 10.0.0.0
Version Win32 : 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.v9.0
Version de l'assembly : 9.0.0.0
Version Win32 : 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
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.5468 (Win7SP1GDR.050727-5400)

CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System.Drawing
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.5467 (Win7SP1GDR.050727-5400)

CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

Microsoft.VisualStudio.Tools.Office.Runtime.v10.0.resources
Version de l'assembly : 10.0.0.0
Version Win32 : 10.0.40305.0

CodeBase : file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Office.Runtime.v10.0.resources/10.0.0.0_fr_b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Office.Runtime.v10.0.resources.dll

System.Deployment
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.5420 (Win7SP1.050727-5400)

CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.Deployment/2.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll

System.Configuration
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.5476 (Win7SP1GDR.050727-5400)

CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Xml
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.5476 (Win7SP1GDR.050727-5400)

CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

System.Security
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.5475 (Win7SP1GDR.050727-5400)

CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.Security/2.0.0.0__b03f5f7f11d50a3a/System.Security.dll

mscorlib.resources
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.5477 (Win7SP1GDR.050727-5400)

CodeBase : file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

System.Deployment.resources
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.Deployment.resources/2.0.0.0_fr_b03f5f7f11d50a3a/System.Deployment.resources.dll

System.Xml.Linq
Version de l'assembly : 3.5.0.0
Version Win32 : 3.5.30729.5420 built by: Win7SP1

CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.Xml.Linq/3.5.0.0__b77a5c561934e089/System.Xml.Linq.dll

System.AddIn.Contract
Version de l'assembly : 2.0.0.0
Version Win32 : 3.5.30729.5420 built by: Win7SP1

CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.AddIn.Contract/2.0.0.0__b03f5f7f11d50a3a/System.AddIn.Contract.dll

Microsoft.VisualStudio.Tools.Applications.Runtime.v9.0.resources
Version de l'assembly : 9.0.0.0
Version Win32 : 9.0.30729.5806

CodeBase : file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.Runtime.v9.0.resources/9.0.0.0_fr_b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.Runtime.v9.0.resources.dll

Microsoft.VisualStudio.Tools.Applications.ServerDocument.v10.0.resources
Version de l'assembly : 10.0.0.0
Version Win32 : 10.0.40305.0
C
Coordinator
Mar 29, 2014 at 6:47 AM
Hello!

Sorry to hear you have had many problems installing NodeXL.

Our technical staff will have a look at your error message soon.

In the mean time do you have another machine you can try to install on? Or, perhaps a virtual machine in Amazon could be a temporary alternative?

Regards,
Marc

Mar 29, 2014 at 8:02 AM
Hi Marc, thanks for your quick response. I'll be buying a desktop computer soon, but I'm just so anxious to dive into your terrific program, I can hardly wait! I look forward to hearing back from the technical staff. In the meantime, I'll look into a virtual machine. Thanks for the suggestion.
Cheers, Letitia
Mar 29, 2014 at 8:14 PM
Edited Mar 30, 2014 at 7:56 PM
Hello, Letitia:

I am the aforementioned technical staff.

The message is saying that a piece of Microsoft software that NodeXL makes use of (the "add-in pipeline") has somehow been corrupted on your computer, and that prevents NodeXL from running. I have no idea how that happened--perhaps another add-in you used in the past didn't behave itself.

There is a Microsoft tool that can be used to repair the corruption. I've never used it before and I am therefore reluctant to recommend it, but if you want to try it (or better yet, if you have an IT department that will do this for you), it's called AddInUtil.exe and it can be found in this folder:

C:\Windows\Microsoft.NET\Framework\v3.5

It has to be run from a command line. If you run "AddInUtil.exe /?" it will show instructions on how it is supposed to be run. There are further instructions at "How to fix corrupt add-in store", which can be found here:

http://social.msdn.microsoft.com/Forums/vstudio/en-US/ccccfd29-ce29-4aaa-8d89-56c88a1a8dd4/how-to-fix-corrupt-addin-store?forum=vsto

In your case, I think the required command line would look like this:

AddinUtil -PipelineRoot:"C:\Program Files (x86)\Common Files\microsoft shared\VSTA\Pipeline.v10.0" -Rebuild

-- Tony