Upload fail - no errors reported

[david.swanson]

Client - 4.1.4.18402 on XP Pro SP3
Server - 4.1.4.18402 on Server 2003 SE SP1

I have a problem with checking in a new version of one particular file. Vault doesn't complete the commit but doesn't show any errors.
The file "Fulmar.ctz" from 18/06/2008 checks out as normal. When I replace it in the working folder, the client displays it as Size Unchanged and Modified. Despite over a year between the versions and many changes, the files are exactly the same size - 4,813 KB (4,927,858 bytes).
When I select check in, that dialogue also reports Size Unchanged and Modified. I click OK, the check out details disappear and the version doesn't change. In the working directory is a file called "Fulmar.ctz" with the current date and time from when I click OK and a hidden folder "_sgbak" which contains a file "Fulmar.ctz.4977.4.2009-08-03.10-20-15.3750" I can't find any errors or any sign that I ever attempted to update the file.

We have a test repository so I've loaded the same 2008 file into it and attempted to update with the 2009 file. I get exactly the same result. I guess this is somehow related to the file size being un-changed. How do I get Vault to recognise this?

David Swanson

[Beth]

You might try using CRCs to check for changes. If you open your Vault GUI client, go to Tools - Options - Local Files, there will be an option at the bottom of that window to use CRCs. If your file is over 10 mb in size, you will want to adjust the size of the files that it checks as well. After that is set, try again and let me know your results.

[david.swanson]

That resolved the problem, but probably not in the way expected.
With the CRC setting, the new file said "Unmodified". Realising that wasn't possible for an archive file, when I had added a file and completely populated a field in several database tables, further investigation showed this was an archive (which I don't recall creating) of the system before this year's modifications so should be the same as the one from after the previous modifications. I have now found the new one in the wrong folder on the memory stick.

[Beth]

I'm happy to hear that you were able to resolve what was happening.