Check In Fail

middlik · Post by **middlik** » Mon Apr 24, 2006 5:37 am

Good Day!

All files successfully Checked In, but on one single file i have this problem:

[24.04.2006 15:19:51] Preparing data to begin transaction
[24.04.2006 15:19:51] Beginning transaction
[24.04.2006 15:19:51] Check in $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm
[24.04.2006 15:19:51] Upload for item $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm failed, retrying...
[24.04.2006 15:19:51] Upload for item $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm failed, retrying...
[24.04.2006 15:19:51] Upload for item $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm failed, retrying...
[24.04.2006 15:19:51] Ending the transaction
[24.04.2006 15:19:51] Upload for item $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm 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 server returned an unknown error header: VaultFileUpload.aspx encountered: FailFileInvalidCheckSum"
An exception was encountered during the transaction. Exception: The server returned an unknown error header: VaultFileUpload.aspx encountered: FailFileInvalidCheckSum at VaultClientOperationsLib.ClientInstance.UploadItem(ChangeSetItem item, String txID, Byte[]& streamBuffer, Int32& bytesWrittenThisFile, Boolean bIsImport)
at VaultClientOperationsLib.UploadThread.ProcessCommand(UploadThreadCommand command, UploadThreadCommandResult& outputResult)
[24.04.2006 15:19:51] Transaction failed

Any ideas?

VI:
[24.04.2006 10:53:14] Version Check: This Vault client is version 3.1.8.3771
[24.04.2006 10:53:15] Version Check: Your Vault server is version 3.1.8.3771

lbauer · Post by **lbauer** » Mon Apr 24, 2006 8:23 am

What does the Vault server log say for the same time period? It's sgvault.log in the %windir%\temp\sgvault directory on the Vault Server machine.

middlik · Post by **middlik** » Mon Apr 24, 2006 8:50 am

~30 line with info:

----24.04.2006 15:19:05 admin--yut(10.1.5.247)--SSL Disabled VaultFileUpload.aspx encountered: FailFileInvalidCheckSum

but 20 min earlier I can see this:

----24.04.2006 15:04:31 admin--yut(10.1.5.247)--SSL Disabled VaultFileUpload.aspx encountered: an error looking up the session's intermediate transaction object: FailFileTokenError

middlik · Post by **middlik** » Mon Apr 24, 2006 9:05 am

hmm: very interesting sequel

)

On this file I do "Undo CheckOut", after that i have been changed working folder and try to CheckOut again... and what do you think?

Right! Error:
[24.04.2006 18:50:51] Checking out file $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm
[24.04.2006 18:50:51] An error was found with the baseline file for $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm. Refetching baseline and retrying get operation...

After that the IIS Service on Server was restarted. No way.... the same error was occur.

I can tell wat I do, and what for I do it. Now our Company in process to chose a replacement for VSS. On first site your product is very good. But the main problem with VSS is performance. Before making a decision on transition to a new product, we all over again wish we shall not be convinced of that what to have the same problems with productivity. And now I just make the Vault DB same size as our main VSS DB.

This is the first serious problem.
Please help us to make right ) decision

))

lbauer · Post by **lbauer** » Mon Apr 24, 2006 9:41 am

This could be --
1) a problem with the baseline file being out of sync.

Or

2) a problem with the particular file.

Let's first try to fix 1):

Backup the file that won't check in (testGetDoc_G_AccName_DM.dfm ).

Change working directories. Do a get latest on the new working directory.
You should then have testGetDoc_G_AccName_DM.dfm in the directory. Check it out, and replace the file with the modified file you backed up.

Now try to checkin testGetDoc_G_AccName_DM.dfm.

middlik · Post by **middlik** » Mon Apr 24, 2006 9:54 am

Thank you for the fast reply.

Backup the file that won't check in (testGetDoc_G_AccName_DM.dfm ).

done !

Change working directories.

done!

Do a get latest on the new working directory.

Error message box: Object reference not set to an instance of an object.
In message list:
[24.04.2006 19:49:55] Getting latest version of $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm
[24.04.2006 19:49:55] An error was found with the baseline file for $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm. Refetching baseline and retrying get operation...

Server log: nothing.

Add info: when i try GetLatest on all folder, all the files in folder successfully processed, but this one is failed.

No file in new working directory.

lbauer · Post by **lbauer** » Mon Apr 24, 2006 10:19 am

When you did this, did you use a new, never used before, empty working directory? If not, try again with a working directory you have just created.

middlik · Post by **middlik** » Mon Apr 24, 2006 11:00 am

My operations:

1. Create folder on local disk: D:\TEMP\TEST
(ok!)
2. Set working folder to this directory
(ok!)
3. Get latest version on single file
(error!) Object reference not set to an instance of an object.

End of path...

Can I help you with any additional debug info ?

P.S.
Another path to another error (may be help you to guess a riddle )...

1. Set working folder to original place by choose "Use inherited working folder (D:\ ... etc)"
(ok!)
2. Clear this local folder.
(ok!)
3. Get latest version on single file
(ok! file on my local disk!)
4. CheckOut file
(ok!)
5. Change file on local disk
(ok! may editor is still working :)))) )
6. CheckIn file
(error!)

Full log for this path:

[24.04.2006 20:47:11] Getting latest version of $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm
[24.04.2006 20:47:11] Fetched $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm
[24.04.2006 20:47:11] Finished get latest of $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm
[24.04.2006 20:57:27] Checking out file $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm
[24.04.2006 20:57:27] Fetched $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm
[24.04.2006 20:57:27] Checked out file $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm
[24.04.2006 20:58:24] Preparing data to begin transaction
[24.04.2006 20:58:24] Beginning transaction
[24.04.2006 20:58:24] Check in $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm
[24.04.2006 20:58:24] Upload for item $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm failed, retrying...
[24.04.2006 20:58:24] Upload for item $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm failed, retrying...
[24.04.2006 20:58:24] Upload for item $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm failed, retrying...
[24.04.2006 20:58:25] Ending the transaction
[24.04.2006 20:58:24] Upload for item $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm 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 server returned an unknown error header: VaultFileUpload.aspx encountered: FailFileInvalidCheckSum"
An exception was encountered during the transaction. Exception: The server returned an unknown error header: VaultFileUpload.aspx encountered: FailFileInvalidCheckSum at VaultClientOperationsLib.ClientInstance.UploadItem(ChangeSetItem item, String txID, Byte[]& streamBuffer, Int32& bytesWrittenThisFile, Boolean bIsImport)
at VaultClientOperationsLib.UploadThread.ProcessCommand(UploadThreadCommand command, UploadThreadCommandResult& outputResult)
[24.04.2006 20:58:25] Transaction failed
[24.04.2006 20:58:25] Transaction failed

sgvault.log on server
----24.04.2006 20:57:38 admin--yut(10.1.5.247)--SSL Disabled VaultFileUpload.aspx encountered: FailFileInvalidCheckSum
----24.04.2006 20:57:38 admin--yut(10.1.5.247)--SSL Disabled VaultFileUpload.aspx encountered: FailFileInvalidCheckSum
----24.04.2006 20:57:38 admin--yut(10.1.5.247)--SSL Disabled VaultFileUpload.aspx encountered: FailFileInvalidCheckSum

lbauer · Post by **lbauer** » Tue Apr 25, 2006 8:50 am

Let's see if I can summarize:

1 -- you cannot get the file to a new working directory
2 -- you cannot checkin the modified file
3 --you can get to an inherited directory where the file was previously retrieved.

It's possible the get in #3 worked because you already had a baseline of that file on your machine.

This could be some type of network issue.

Do other Vault users have a problem getting or checking in this file?

Is this a large file?

If you create a test directory in Vault, can you upload this file to the new directory?

Could a firewall or anti-virus program on the client or server machine be blocking the upload or get?

middlik · Post by **middlik** » Wed Apr 26, 2006 9:24 am

Hello Linda.

Sorry for timeout.

It's possible the get in #3 worked because you already had a baseline of that file on your machine.

Sorry, I can't understand it. What does it means?

Do other Vault users have a problem getting or checking in this file?

Now we have trial version with only 'admin' user. On another host I have same error. I cant checkout this file by 'admin' vault user.

Is this a large file?

18423 bytes

If you create a test directory in Vault, can you upload this file to the new directory?

YES!!! Just do this. In some existing folder Add this file, set working folder, check out, edit and succesfully check in this file

Could a firewall or anti-virus program on the client or server machine be blocking the upload or get?

No! Especially for this test I put down all anti-virus, firewalls and other "bad" applications.

May by problem with Vault DB (MS SQL DB) ?

lbauer · Post by **lbauer** » Wed Apr 26, 2006 2:47 pm

Sorry, I can't understand it. What does it means?

In order to improve performance, Vault sends only the changes in a file rather than the whole file. However, the Vault client must first download baseline files to the _sgvault (baseline) directory. In some cases, if the baseline file is the same as the latest version, the Vault client will get a file from this directory rather than from the server.

YES!!! Just do this. In some existing folder Add this file, set working folder, check out, edit and succesfully check in this file

This means there probably is not a problem with the type of file or size. It could be that the client-side cache files have gotten out of sync. I suggest deleting the client-side cache files.

First, I'd suggest checking in or backing up any modified files in the working directories. Close any open Vault clients on the machine.

Then delete the entire cache file. It's called Vault_1 and by default is in C:\Documents and Settings\yourprofile\Local Settings\Application Data\SourceGear. If you store the _sgvault folders in the working directories, delete those, too.

The cache file will be rebuilt when you connect to the Vault Server again, but you will need to reset your working directories. File status will be Unknown, and a get latest will restore the proper status.

Details on cache files here:
http://support.sourcegear.com/viewtopic.php?t=6

middlik · Post by **middlik** » Thu Apr 27, 2006 1:27 am

What I have done:
Close all Vault Client on machine.
Delete all in working folder, delete all in "D:\Documents and Settings\ %accountname%\Local Settings\Application Data\SourceGear"

Run Vault client
Set Working Folder and try check out. Fail....Same Error...There are no any files in working folder, but vault set "CheckedOut" status in Vault Client.

Error log:
[27.04.2006 10:57:21] Checking out file $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm
[27.04.2006 10:57:23] An error was found with the baseline file for $/DiasoftDealing5NT/Âåðñèÿ 3.6/Release/3.6.1/Client/Test/ESec/testGetDoc_G_AccName_DM.dfm. Refetching baseline and retrying get operation...

And new interesting. After that I try Undo CheckOut and have this error in message box:
A database error has occured (FailDBFault). Another file in same vault folder succesfully checked out, edited, and checked in after this error.

Please give attention on this fact (see on previos post): on other machine I also can't check out this file.

It seems to me that this magic file corrupted in Vault DB.

middlik · Post by **middlik** » Thu Apr 27, 2006 1:39 am

Additional info for your mind:

1. Share this file on folder higher. Successfully.
2. Try to check out. Error. Absolutely the same: messasge box : Object reference not set to an instance of an object.