Home › Forums › NodeXL Installation issues – first time install, moving NodeXL to a new machine and more › Error encountered after Windows 10 update
- This topic has 3 replies, 2 voices, and was last updated 4 years, 2 months ago by
CW.
- AuthorPosts
- September 18, 2019 at 6:17 pm #8605
CW
ParticipantI installed and used NodeXL Basic in my Windows 10 machine without any problem. Windows got an update to Version 1903 yesterday plus a cumulative update for .NET Framework 3.5 and 4.8. Since then I could not open NodeXL anymore. I tried uninstall and reinstall NodeXL but the problem remains unsolved. Below was the error message I got. I would be much grateful if anyone can give me a hand on this!
Updating Office Customization
There was an error during installation
The application binding data format is invalid. (Exception from HRESULT: 0x800736B2)Error Details:
Name: NodeXL Excel Template
From: http://www.nodexlgraphgallery.org/NodeXLBasicSetup/Smrf.NodeXL.ExcelTemplate.vsto************** Exception Text **************
System.Runtime.InteropServices.COMException (0x800736B2): The application binding data format is invalid. (Exception from HRESULT: 0x800736B2)
at System.Deployment.Internal.Isolation.IsolationInterop.CreateActContext(CreateActContextParameters& Params)
at System.Deployment.Internal.Isolation.IsolationInterop.CreateActContext(IDefinitionAppId AppId)
at System.ActivationContext.CreateFromName(ApplicationIdentity applicationIdentity)
at System.ActivationContext.CreatePartialActivationContext(ApplicationIdentity identity)
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn()************** Exception Text **************
System.Runtime.InteropServices.COMException (0x800736B2): The application binding data format is invalid. (Exception from HRESULT: 0x800736B2)
at System.Deployment.Internal.Isolation.IsolationInterop.CreateActContext(CreateActContextParameters& Params)
at System.Deployment.Internal.Isolation.IsolationInterop.CreateActContext(IDefinitionAppId AppId)
at System.ActivationContext.CreateFromName(ApplicationIdentity applicationIdentity)
at System.ActivationContext.CreatePartialActivationContext(ApplicationIdentity identity)
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn()************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4010.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
—————————————-
Microsoft.VisualStudio.Tools.Office.Runtime
Assembly Version: 10.0.0.0
Win32 Version: 10.0.60828.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Office.Runtime/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Office.Runtime.dll
—————————————-
Microsoft.VisualStudio.Tools.Applications.Hosting
Assembly Version: 10.0.0.0
Win32 Version: 10.0.60828.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.Hosting/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.Hosting.dll
—————————————-
Microsoft.VisualStudio.Tools.Applications.ServerDocument
Assembly Version: 10.0.0.0
Win32 Version: 10.0.60828.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.ServerDocument/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.ServerDocument.dll
—————————————-
Microsoft.Office.Tools
Assembly Version: 10.0.0.0
Win32 Version: 10.0.60828.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.Office.Tools/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.Office.Tools.dll
—————————————-
Microsoft.VisualStudio.Tools.Applications.Runtime
Assembly Version: 10.0.0.0
Win32 Version: 10.0.60828.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.Runtime/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.Runtime.dll
—————————————-
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
—————————————-
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
—————————————-
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
—————————————-
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
—————————————-
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
—————————————-
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
—————————————-
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
—————————————-
System.Deployment
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Deployment/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll
—————————————-CW
September 18, 2019 at 6:47 pm #8606CW
ParticipantSorry, I forgot to mention that I am using Office 365 ProPlus. My Excel is version 1908 (Build 11929.20300). Thank you.
CW
September 19, 2019 at 10:54 am #8607Arber Ceni
KeymasterHello,
It looks like the ClickOnce cache got corrupted due to the update.
To reset your ClickOnce cache and re-install NodeXL please follow these steps:
1. Uninstall NodeXl from Control Panel
2. Go to C:\Users\[user_profile_name]\AppData\Local\Apps\2.0
3. You should notice 2 folders: one is named “Data” and the other one has a strange name. The folder with the strange name used to have all the NodeXL files (now removed in step 1). Please try to delete that folder. If you are able to remove the folder, please try installing NodeXL again, otherwise continue in the next step
4. Open RegEdit and go to: [HKEY_LOCAL_MACHINE]\\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\
5. Under ProfileList find the profile that corresponds to your user. To do that click on the profile entry and check “ProfileImagePath” on the right side
6. After you have located your profile, add a new DWORD (32-bit) value entry name “RefCount” and set the Value to 0.(for more details you can check https://neosmart.net/wiki/corrupt-user-profile/)
7. Sign out from Windows (or restart)
8. Try installing NodeXL (it should work now!)
9. Open RegEdit again and remove the key (RefCount) you added in step 6-Arber
September 19, 2019 at 3:11 pm #8608CW
ParticipantYes, I confirm the above suggestions/steps solved my problem. Hope this is useful for others who encounter a similar issue. Thanks for the help Arber!
CW
- AuthorPosts
- You must be logged in to reply to this topic.