Adding New Files--FailExistingTx

mculbreth · Post by **mculbreth** » Tue Apr 05, 2005 9:05 am

Howdy,

I have a user who is using our Vault 3.0.5 and is getting this error thrown into the log:

----4/5/2005 10:59:23 AM mikec--atl01s31.intellinet.local(10.1.1.31)--SSL Disabled FailExistingTx

This happens when the user is trying to add a new file to a folder in the Repository from the Vault client.

Any idea here? It works for me when I login, and we have the same access. He is at a remote site and I am in the same building as the server.

Thanks,

Matt

Post by **jclausius** » Tue Apr 05, 2005 9:18 am

Matt:

Is there anything in the Vault Server's log file - ( by default in %windir%\temp\sgvault ), which may give some insight to the problem?

mculbreth · Post by **mculbreth** » Tue Apr 05, 2005 10:22 am

Thanks.

Here's what the developer is seeing:

[4/5/2005 12:21:00 PM] Preparing data to begin transaction

[4/5/2005 12:21:00 PM] Beginning transaction

[4/5/2005 12:21:00 PM] Add $/StreamlinedERP/StreamlinedERP Win/Trunk/Northwind.xml

[4/5/2005 12:21:00 PM] Upload for item $/StreamlinedERP/StreamlinedERP Win/Trunk/Northwind.xml failed, retrying...

[4/5/2005 12:21:00 PM] Upload for item $/StreamlinedERP/StreamlinedERP Win/Trunk/Northwind.xml failed, retrying...

[4/5/2005 12:21:01 PM] Upload for item $/StreamlinedERP/StreamlinedERP Win/Trunk/Northwind.xml failed, retrying...

[4/5/2005 12:21:01 PM] Upload for item $/StreamlinedERP/StreamlinedERP Win/Trunk/Northwind.xml failed too many times, aborting transaction.

Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.

The specific error was "The remote server returned an error: (400) Bad Request."

An exception was encountered during the transaction. Exception: The remote server returned an error: (400) Bad Request. at System.Net.HttpWebRequest.CheckFinalStatus()

at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)

at System.Net.HttpWebRequest.GetRequestStream()

at VaultClientOperationsLib.ClientInstance.UploadItem(ChangeSetItem item, String txID, Int64 totalBytes, Int64& bytesWritten, Byte[]& streamBuffer, Int32& bytesWrittenThisFile, Boolean bIsImport)

at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, Boolean keepCheckedOut, Boolean removeLocalCopy, Boolean bIsImport, DateTime dateImport, Int32 nUserIDImport, Int64& nRevID)

[4/5/2005 12:21:01 PM] Ending the transaction

[4/5/2005 12:21:01 PM] Server unavailable for transaction end

[4/5/2005 12:21:01 PM] An exception was encountered during the transaction. Exception: The Vault server could not be contacted to perform the operation. Your network connection to the server may have been interrupted. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.The underlying connection was closed: An unexpected error occurred on a send. at VaultClientNetLib.VaultConnection.EndTx(String strTxID, Int64& nNewRevision, VaultResponseItem[]& responses, Int32 nAction, DateTime& txBeginDate)

at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, Boolean keepCheckedOut, Boolean removeLocalCopy, Boolean bIsImport, DateTime dateImport, Int32 nUserIDImport, Int64& nRevID)

[4/5/2005 12:21:01 PM] Transaction failed

mculbreth · Post by **mculbreth** » Tue Apr 05, 2005 10:47 am

We figured it out.

If we uncheck "use chunked encoding" under the Tools/Options it seems to work.

Post by **jclausius** » Tue Apr 05, 2005 10:50 am

Something is interfering with IIS and the file transfer. This error is occurring even before the Vault server can be notified of the File upload.

Searching around for "Bad Request. at System.Net.HttpWebRequest.CheckFinalStatus()" has shown different responses to the problem:

1) Something misconfigured with SSL or the certificate

2) Going through a Firewall which does not support chunked encoding - You can disable chunked encoding for Vault 2.0.x clients - Unable to add or checkin files In Vault 3.0.x clients, there is an option to disable this within the Network settings option.

3) A timeout for the web request.

I'd have the end-user take a look at step 2 - since it is the easiest fix at this point in time. Please post back if this does the trick.

Post by **jclausius** » Tue Apr 05, 2005 10:54 am

mculbreth wrote:We figured it out.

Cool.