I don't use the InstallShield source control integration at all - just the Vault Client. I get the following:
I tried with the command line client, too, and I got this:[7/16/2007 1:23:23 PM] An exception was encountered during the transaction. Exception: Server was unable to process request. ---> Error in the application. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultClientNetLib.ClientService.VaultService.BeginTx(Int32 nRepID, String strComment, VaultRequestItem[]& requests, String& strTxID)
at VaultClientNetLib.VaultConnection.BeginTx(Int32 nRepID, VaultRequestItem[]& requests, String& strTxID, String comment)
at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, String strChangeSetComment, Boolean keepCheckedOut, Boolean removeLocalCopy, CommitType committype, VaultDateTime dateImport, Int32 nUserIDImport, Int64& nRevID, Int32[]& retBegEndTx)
I've tried this on two PCs with the same result. I am able to work with other files - it's just our Installer projects that are causing the problem.Unhandled Exception: System.InvalidOperationException: Token StartElement in sta
te Error would result in an invalid XML document.
at System.Xml.XmlTextWriter.AutoComplete(Token token)
at System.Xml.XmlTextWriter.WriteStartElement(String prefix, String localName
, String ns)
at System.Xml.XmlWriter.WriteStartElement(String localName)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
It's been a couple of weeks since I last needed to make a change to one of these files, but we haven't done any vault upgrades or anything in the meantime.
Any ideas?