Problem with Enhanced Client in VS2008

[fieldsms]

We have migrated the fortress to a new server and have been getting the following error when adding a new solution to fortress:

"There was an error generating the XML document."

The client seems to work with the solutions we added to the database before the migration to a new server. We are able to add solutions using the classic client without any problems.

[Beth]

What is the OS of the new server.

What version of Fortress are you using?

Were you using the Fortress Enhanced Client successfully prior to the move?

Can you either post your Fortress server log found at %windir%\temp\sgvault\sgvault.log or just the section that relates to your attempt to add from VS? If you prefer, you can email it to support at sourcegear.com with a link to this forum thread and attn: Beth in the subject line.

[fieldsms]

Ok, after turning on diagnostic logging in the client I was able to find the problem. I had an add-in called DocProject installed that was causing the error. After uninstalling it the errors went away, but there still is a compatibility issue, not sure if it is on the DocProject end or Fortress. Here is the output of the client log:

Code: Select all

9/13/2010 11:02:33 AM <generic>: [<No Name>:2152]     [System.IO.FileNotFoundException: Could not load file or assembly 'C:\SourceControl\Engineering_Tools\Libs\Source\TCOM_AerostatVisualizationLib\%DXROOT%\ProductionTools\BuildComponents.dll' or one of its dependencies. The system cannot find the file specified.
File name: 'C:\SourceControl\Engineering_Tools\Libs\Source\TCOM_AerostatVisualizationLib\%DXROOT%\ProductionTools\BuildComponents.dll'
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterVaultService.Write134_SetUserOptionsInHeaders(Object[] p)
   at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer72.Serialize(Object objectToSerialize, XmlSerializationWriter writer)
   at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
]Could not load file or assembly 'C:\SourceControl\Engineering_Tools\Libs\Source\TCOM_AerostatVisualizationLib\%DXROOT%\ProductionTools\BuildComponents.dll' or one of its dependencies. The system cannot find the file specified.
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterVaultService.Write134_SetUserOptionsInHeaders(Object[] p)
   at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer72.Serialize(Object objectToSerialize, XmlSerializationWriter writer)
   at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
[System.InvalidOperationException: There was an error generating the XML document. ---> System.IO.FileNotFoundException: Could not load file or assembly 'C:\SourceControl\Engineering_Tools\Libs\Source\TCOM_AerostatVisualizationLib\%DXROOT%\ProductionTools\BuildComponents.dll' or one of its dependencies. The system cannot find the file specified.
File name: 'C:\SourceControl\Engineering_Tools\Libs\Source\TCOM_AerostatVisualizationLib\%DXROOT%\ProductionTools\BuildComponents.dll'
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterVaultService.Write134_SetUserOptionsInHeaders(Object[] p)
   at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer72.Serialize(Object objectToSerialize, XmlSerializationWriter writer)
   at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

   --- End of inner exception stack trace ---
   at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
   at System.Web.Services.Protocols.SoapHeaderHandling.WriteHeaders(XmlWriter writer, XmlSerializer serializer, SoapHeaderCollection headers, SoapHeaderMapping[] mappings, SoapHeaderDirection direction, Boolean isEncoded, String defaultNS, Boolean serviceDefaultIsEncoded, String envelopeNS)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Serialize(SoapClientMessage message)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at VaultClientNetLib.ClientService.VaultService.SetUserOptions(Int32 nCategoryID, String[] names, String[] values)
   at VaultClientNetLib.VaultConnection.SetOptions(Int32 nCatID, String[] nameArray, String[] valueArray)
   at VaultClientOperationsLib.UserOptions.LoadFromServer()
   at VaultClientOperationsLib.ClientInstance.Login(String urlbase, String username, String password)
   at VaultClientPresentationLib.GUIClientInstance.ConnectToServer(String& outserverPath, Boolean forceDialogShow, String& outprofileName, String& outusername, Boolean& outbUseSSL, Boolean& outbAutoLogin)
   at SourceGearLLC.VaultVsipClient.Vault.LogIn(IntPtr mainWindowHandle)]There was an error generating the XML document.
   at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
   at System.Web.Services.Protocols.SoapHeaderHandling.WriteHeaders(XmlWriter writer, XmlSerializer serializer, SoapHeaderCollection headers, SoapHeaderMapping[] mappings, SoapHeaderDirection direction, Boolean isEncoded, String defaultNS, Boolean serviceDefaultIsEncoded, String envelopeNS)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Serialize(SoapClientMessage message)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at VaultClientNetLib.ClientService.VaultService.SetUserOptions(Int32 nCategoryID, String[] names, String[] values)
   at VaultClientNetLib.VaultConnection.SetOptions(Int32 nCatID, String[] nameArray, String[] valueArray)
   at VaultClientOperationsLib.UserOptions.LoadFromServer()
   at VaultClientOperationsLib.ClientInstance.Login(String urlbase, String username, String password)
   at VaultClientPresentationLib.GUIClientInstance.ConnectToServer(String& outserverPath, Boolean forceDialogShow, String& outprofileName, String& outusername, Boolean& outbUseSSL, Boolean& outbAutoLogin)
   at SourceGearLLC.VaultVsipClient.Vault.LogIn(IntPtr mainWindowHandle)

Stack Trace:
   at VaultClientPresentationLib.GUIClientInstance.ShowCommandException(Exception e, IWin32Window dialogOwner)
   at VaultClientPresentationLib.GUIClientInstance.ShowCommandException(Exception e)
   at SourceGearLLC.VaultVsipClient.Vault.LogIn(IntPtr mainWindowHandle)
   at SourceGearLLC.VaultVsipClient.VaultCommandAddSolution.PromptForRepositoryAddPath(WorkingFolderTree& workingFolderTree)
   at SourceGearLLC.VaultVsipClient.VaultCommandAddSolution.DoPerform()
   at SourceGearLLC.VaultVsipClient.VaultCommand.Perform()
   at SourceGearLLC.VaultVsipClient.VaultVsipClient.Exec_icmdAddSolutionToVault(Object sender, EventArgs e)
   at System.ComponentModel.Design.MenuCommand.Invoke()
   at System.ComponentModel.Design.MenuCommand.Invoke(Object arg)
   at Microsoft.VisualStudio.Shell.OleMenuCommandService.Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(Guid& guidGroup, UInt32 nCmdId, UInt32 nCmdExcept, IntPtr pIn, IntPtr vOut)
   at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(Guid& guidGroup, UInt32 nCmdId, UInt32 nCmdExcept, IntPtr pIn, IntPtr vOut)

Thanks for your help.

[Beth]

I can't find much information that relates that error to us. Was that file present before removing DocProject?

I ran a search on one of my machines that has VS 2008 and Vault and didn't find that dll at all.