Display problem with history Explorer

brewer531 · Post by **brewer531** » Wed Oct 17, 2007 6:18 pm

I attached a screenshot of a minor display problem with the history explorer window. The name column appears to be chopped off even though there is plenty of room for the name in the column. I just wanted to report this in case it wasn't already noticed.

lbauer · Post by **lbauer** » Wed Oct 17, 2007 8:16 pm

We've had reports of this before but have never been able to reproduce it. In one case, we had the user's database in-house, but the display was fine on our system. The user reported this eventually resolved itself as they used history.

Are you seeing it on a database that was upgraded from a previous version?

brewer531 · Post by **brewer531** » Thu Oct 18, 2007 1:29 pm

Yes. It has been upgraded from version 2 originally but was last upgraded from 3.5.1 to 4.0.4. You happen to have a copy of our db right now doing analysis for a branching problem so it would be interesting to see if you see that on our database (Beth is helping us with the branching issue). You can see the issue if you do a history query on $/Webpayroll (it seems to just always chop off all but the last character and the / of the folder you are querying history on).

lbauer · Post by **lbauer** » Thu Oct 18, 2007 3:46 pm

OK, we'll try that.

janeriko · Post by **janeriko** » Thu Feb 14, 2008 4:35 am

We also have this problem.

Some additional info:
1. We have recently upgraded from 3.5.0 to 4.0.6 and I believe that the problem wasn’t there before the upgrade.
2. We have three repositories but the problem is seen only on one of them.
3. The root folder’s name is truncated to the last character, but only for items included because of a recursive search.
4. It is more than a display problem - if I attempt to get such an object I’ll get an error message "The requested version (2) of $/... can not be found in the current repository", with an incorrect path stated due to the truncation.

lbauer · Post by **lbauer** » Thu Feb 14, 2008 11:25 am

If the server is using $/... in the message, then it appears to have the full path. But it doesn't seem to be getting to the client.

Could you reproduce the error and send me a copy of the Vault serve log? Email it to support at sourcegear.com, ATTN Linda.

Would it be possible for you to run a packet sniffer between the Vault client and server to see what data is actually being passed?

lbauer · Post by **lbauer** » Thu Feb 14, 2008 5:07 pm

Another question: What OS is Vault installed on?

What edition and version of SQL Server are you using?

janeriko · Post by **janeriko** » Tue Mar 11, 2008 8:55 am

I have been informed that you have a solution for this problem.
Is it fixed in version 4.1.0?

lbauer · Post by **lbauer** » Tue Mar 11, 2008 9:31 pm

This will be fixed in Vault 4.1.1.

We have a pre-release fix for the truncated history. We've sent it to a couple of uses with good results. If you'd like it, email support@sourcegar.com ATTN: Linda