Transaction Exception (check-in): Response is not well-formed XML.

[LCI-Paul]

Hi. We have a number of files that are starting to receive errors when trying to check-in. We run Vault Standard 6.1.0.531 on SQL Server 2016 SP2 and all our clients are also 6.1.0.531. This is happening with specific files no matter the user. We have been running Vault without issue for years now. Very out of the blue. Any help would be very much appreciated!

Here is the full text of the error received:

Code: Select all

An exception was encountered during the transaction.  Exception: Response is not well-formed XML.   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)
InnerException: Unexpected end of file has occurred. The following elements are not closed: faultstring, soap:Fault, soap:Body, soap:Envelope. Line 1, position 65486.   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ThrowUnclosedElements()
   at System.Xml.XmlTextReaderImpl.ParseElementContent()
   at System.Xml.XmlReader.ReadString()
   at System.Xml.XmlReader.ReadElementString()
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadSoapException(XmlReader reader)
   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)

[Tonya]

Hello,

Can you please post your Vault Server log? The Vault Server log is in %windir%\temp\sgvault\sgvault.log on the server machine. This will likely give us more information in regards to the error.

Have you applied any changes to your network lately? Are the files that won't checkin large files? Do you see any similarities for the files that won't checkin?

Thanks,

Tonya

[LCI-Paul]

Hi Tonya. Thanks for the help. The log was very large, so I removed all entries before today and zipped it up to get it down to 2MB. (We made sure duplicate the issue at least once today so that it would be in the log.) I still wasn't able to attach it to this post, however. I'm getting "http error". Tried two different browsers. (I was able to attach a picture of that error, though.) I can host the file on google drive and send you a link via private message, maybe?

We've since come to realize that this issue is specific only to certain folders in our repository. And the error I detailed before is not limited to check-ins for files within these affected folders. We are unable to add files to these folders, as well. Same error. We have tried small and large files of various types. All are giving the same error as long as the operation is within one of these affected folders. We have also tried all of the same operations with various different users on different machines. All users get the same error but only within the affected folders. If we try adding the same files to a different folder, we have no issues.

There have also been no changes to our network or servers recently that we can think of.

[Tonya]

Hello again,

Please send your server log to support@sourcegear.com and refer to this forum post.

Thanks,

Tonya

[LCI-Paul]

Thanks, Tonya. Email is sent!