Error occurs in VSTO 4.0 add-in while using Office 2010 products

To utilize .NET framework 4.5 in Visual Studio 2012, it can be directed towards. NET framework 4.5. The assembly version is 9.0.0.0 with a Win32 version of 9.0.30729.4130. The codebase can be found at file:///C:/Windows/assembly/GAC_MSIL/Microsoft.

Question:

We are facing issues with a 3rd party Office add-in and have consulted the creators of the add-in, who are unable to identify the problem. Our systems have roaming profiles on Window 7 (x64) with Office 2010 (v14.0.6029.1000) installed. The add-ins load successfully the first time, but appear disabled on subsequent startups of most Office products. Despite checking the event logs, we are currently stuck and unsure of what to do next.

Under the Application log, an error with Event ID 4096 and no assigned Task Category occurred on 10/22/2012 at 08:18:25 AM. The error, which was classified as Classic and had no associated user, took place on the computer xxxx.xxxxx.xxx. The error description indicated that the Customization URI was file:///C:/Program Files (x86)/Common Files/Microsoft Shared/VSTA/Pipeline.v10.0/PipelineSegments.store. However, the manifest from the same file location (file:///C:/Program%20Files%20(x86)/Common%20Files/Microsoft%20Shared/VSTA/Pipeline.v10.0/PipelineSegments.store) may be invalid or could not be opened.

The system encountered an exception while attempting to open the
Exception reading
manifest from file:///C:/Program%20Files%20(x86)/Common%20Files/Microsoft%20Shared/VSTA/Pipeline.v10.0/PipelineSegments.store. This may be due to the manifest being invalid or the file being inaccessible. An
invalid character
was encountered in the manifest at line 1, position 1, causing a System.Xml.XmlException. The manifest was read using various classes, including XmlTextReader, XmlCharCheckingReader, and XsdValidatingReader. The error stack trace indicates that the exception occurred in the ManifestReader.FromDocument method, which was called with the localPath, manifestType, and sourceUri parameters. The ClickOnceAddInDeploymentManager class was used to install the add-in, and the GetManifests method was used to retrieve the manifests, which timed out after a specified amount of time.

The loaded assemblies include mscorlib
Assembly Version
version 2.0.0.0 with Win32 version 2.0.50727.5456 (Win7SP1GDR.050727-5400) and codebase at file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll. Additionally, the Microsoft.VisualStudio.Tools.Office.Runtime.v10.0 assembly has version 10.0.0.0 and Win32 version 10.0.31119.0, with codebase at 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. Other loaded assemblies include System, with version 2.0.0.0 and Win32 version 2.0.50727.5456 (Win7SP1GDR.050727-5400), and System.Core with version 3.5.0.0 and Win32 version 3.5.30729.5420 built by Win7SP1. Lastly, the Microsoft.VisualStudio.Tools.Applications.Hosting.v10.0 assembly has version 10.0.0.0, Win32 version 10.0.31119.0, and codebase at 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.

The following are the details of various assemblies:
– System.AddInAssembly Version: 3.5.0.0Win32 Version: 3.5.30729.5446 built by: Win7SP1GDRCodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.AddIn/3.5.0.0__b77a5c561934e089/System.AddIn.dll
– Microsoft.Office.Tools.Outlook.v9.0Assembly Version: 9.0.0.0Win32 Version: 9.0.30729.4130CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/Microsoft.Office.Tools.Outlook.v9.0/9.0.0.0__b03f5f7f11d50a3a/Microsoft.Office.Tools.Outlook.v9.0.dll
– Microsoft.VisualStudio.Tools.Applications.Runtime.v10.0Assembly Version: 10.0.0.0Win32 Version: 10.0.31119.0CodeBase:
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
– System.Windows.FormsAssembly Version: 2.0.0.0Win32 Version: 2.0.50727.5460 (Win7SP1GDR.050727-5400)CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
– System.DrawingAssembly Version: 2.0.0.0Win32 Version: 2.0.50727.5462 (Win7SP1GDR.050727-5400)CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/
system.drawing.dll

The Event Xml contains information about an event that occurred. It includes details such as the provider name, event ID, level, task, keywords, time created, event record ID, channel, computer, and security. The EventData section provides further data about the event, including the customization URI and the exception that occurred while reading the manifest from the PipelineSegments.store file located at the specified file path. The exception message indicates that the manifest may not be valid or the file could not be opened.

The system encountered an exception while attempting to read the manifest from the specified file location. The manifest may not be valid or the file could not be opened, resulting in an InvalidDeploymentException. The root cause of this issue is an invalid character (”, hexadecimal value 0x01) located at position 1 of line 1 in the XML document. The system attempted to parse the document, but was unable to do so due to the invalid character. The exception stack trace shows that the system encountered this issue while attempting to retrieve the manifest from the specified location using the ClickOnceAddInDeploymentManager. The system was unable to retrieve the manifest within the specified timeout period.

The loaded assemblies include mscorlib with assembly version 2.0.0.0 and Win32 version 2.0.50727.5456 (Win7SP1GDR.050727-5400), located at file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll. Additionally, Microsoft.VisualStudio.Tools.Office.Runtime.v10.0 has assembly version 10.0.0.0 and Win32 version 10.0.31119.0, located at 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. The system assembly has version 2.0.0.0 and Win32 version 2.0.50727.5456 (Win7SP1GDR.050727-5400), located at file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll, while System.Core has version 3.5.0.0 and Win32 version 3.5.30729.5420 built by: Win7SP1, located at file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll. Finally, Microsoft.VisualStudio.Tools.Applications.Hosting.v10.0 has assembly version 10.0.0.0 and Win32 version 10.0.31119.0, located at 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.

The following assemblies have been added to the system:
– System.AddInAssembly Version: 3.5.0.0 Win32 Version: 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.Office.Tools.Outlook.v9.0 Assembly Version: 9.0.0.0 Win32 Version: 9.0.30729.4130 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.Office.Tools.Outlook.v9.0/9.0.0.0__b03f5f7f11d50a3a/Microsoft.Office.Tools.Outlook.v9.0.dll
– Microsoft.VisualStudio.Tools.Applications.Runtime.v10.0 Assembly Version: 10.0.0.0 Win32 Version: 10.0.31119.0 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
– System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5460 (Win7SP1GDR.050727-5400) 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.5462 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

The closing tags for the “Data”, “EventData”, and “Event” elements are included as follows: </Data></EventData></Event>.


Solution:

Navigate to the add-in registry located at HKCUSoftwareMicrosoftOffice followed by the name of the specific application and then proceed to the Addins folder where you will locate the add-in ID.

Removing the Warmup located under the addin ought to solve the issue.


Providing feedback to the manager, Forrest Guo from MSDN Community Support.

Frequently Asked Questions

Posted in Uncategorized