I am having trouble adding a particular file to a vault repository. I have disabled chunked encoding and made sure that the server allows anonymous access, and, in any case, have not had the same problem with any other files. It is an unremarkable 12k text file. When I try to add the file I get the popup error message "The underlying connection was closed. An unexpected error occurred on a receive." And in the message I get the "failed too many times, aborting transaction" error. In the sgvault log, though, there are no errors; it says "VaultServiceBase.VaultRequestAddFile returned: Success".
Any ideas?
Problem adding a file
Moderator: SourceGear
Try setting your server's logging mode to debug. I'm assuming that the line simmediately before "VaultServiceBase.VaultRequestAddFile returned: Success". indicated that it was in BeginTx. There are three steps in any Vault transaction
1. BeginTx. This determines if the request is legal, checks permissions etc.
2. VaultFileUpload -- This is called by IIS after IIS has received the entire file from the client. This is where we store a temp copy of the delta.
3. EndTx. This is where we actually put the file in the database.
My hypothesis is that in debug mode, you will see a log entry for begintx, but no more. This would indicate that IIS is not receiving the file properly.
Things to try.
1. Does the file uplad work if you're on the server machine and logged in to localhost?
2. Are you over a VPN? Try lowering your MTU setting as described http://support.sourcegear.com/viewtopic ... hlight=mtu and http://support.sourcegear.com/viewtopic ... hlight=mtu
1. BeginTx. This determines if the request is legal, checks permissions etc.
2. VaultFileUpload -- This is called by IIS after IIS has received the entire file from the client. This is where we store a temp copy of the delta.
3. EndTx. This is where we actually put the file in the database.
My hypothesis is that in debug mode, you will see a log entry for begintx, but no more. This would indicate that IIS is not receiving the file properly.
Things to try.
1. Does the file uplad work if you're on the server machine and logged in to localhost?
2. Are you over a VPN? Try lowering your MTU setting as described http://support.sourcegear.com/viewtopic ... hlight=mtu and http://support.sourcegear.com/viewtopic ... hlight=mtu
The log was in debug mode, and it doesn't show anything of interest (at least nothing resembling an error):
----4/9/2004 1:05:31 PM dhammond--******--SSL Disabled
BeginTx beginning transaction
----4/9/2004 1:05:31 PM dhammond--******--SSL Disabled
BeginTx returned: Success
----4/9/2004 1:05:31 PM dhammond--******--SSL Disabled
VaultServiceBase.VaultRequestAddFile returned: Success
----4/9/2004 1:05:33 PM dhammond--******--SSL Disabled
Ending transaction
----4/9/2004 1:05:33 PM dhammond--******--SSL Disabled
EndTxSuccess
As you suggested, I tried ftping the file to the server and adding the file from a client directly on the server, and that worked. I was then able to check out the file on my local machine and check it in. If I remove the file from the repository and try to add it from my local machine again (using the file that had been checked out) it gives me the same error.
I'm not using VPN.
This is the second glitch since installing the trial version of Vault yesterday, and I have to say that I'm not inspired with confidence. The first problem I had was when I tried to add a large directory of files. It inexplicably told me that it couldn't connect to the server for that transaction. I solved that problem by adding files in smaller chunks. I wonder if the two problems I've had are related.
----4/9/2004 1:05:31 PM dhammond--******--SSL Disabled
BeginTx beginning transaction
----4/9/2004 1:05:31 PM dhammond--******--SSL Disabled
BeginTx returned: Success
----4/9/2004 1:05:31 PM dhammond--******--SSL Disabled
VaultServiceBase.VaultRequestAddFile returned: Success
----4/9/2004 1:05:33 PM dhammond--******--SSL Disabled
Ending transaction
----4/9/2004 1:05:33 PM dhammond--******--SSL Disabled
EndTxSuccess
As you suggested, I tried ftping the file to the server and adding the file from a client directly on the server, and that worked. I was then able to check out the file on my local machine and check it in. If I remove the file from the repository and try to add it from my local machine again (using the file that had been checked out) it gives me the same error.
I'm not using VPN.
This is the second glitch since installing the trial version of Vault yesterday, and I have to say that I'm not inspired with confidence. The first problem I had was when I tried to add a large directory of files. It inexplicably told me that it couldn't connect to the server for that transaction. I solved that problem by adding files in smaller chunks. I wonder if the two problems I've had are related.
It definitely sounds like there is a network issue here. I would recommend setting the MTU value on the client machine as a first step. You can see that because VaultFileUpload was never logged, IIS never got the file, and so never gave the file to Vault.
It makes sense that you were able to edit the file after you added it, because in Vault, only the changed bytes are sent up to the server, so the checkin was much less than 12k.
It makes sense that you were able to edit the file after you added it, because in Vault, only the changed bytes are sent up to the server, so the checkin was much less than 12k.
