Check in not checking in

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Locked
Scott
Posts: 2
Joined: Tue Aug 09, 2005 9:07 am

Check in not checking in

Post by Scott » Tue Aug 09, 2005 9:13 am

We use version 3.0.7 (2863). I checked out three files, made changes, and checked in. What happened was that vault determined that no changes were made, did not check in, and reloaded my client (visual studio.net) with the previous unchanged code. If it weren't for the _sgbak subdirectory and my noticing that suddenly my changes were gone I would have lost around 6 hours of code changes. Is there something we can do to keep this from happening in the future?

Also, for some files I try to check out and vault tells me that I already have it checked out, does the checkout, tells me that it couldn't check out but the vault client then shows that I checked it out. Has anybody seen this behavior before?
Scott

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Tue Aug 09, 2005 10:00 am

Are you using folder security?

Have other Vault users in your organization experienced this type of problem?
Linda Bauer
SourceGear
Technical Support Manager

Scott
Posts: 2
Joined: Tue Aug 09, 2005 9:07 am

Post by Scott » Tue Aug 09, 2005 12:30 pm

Yes we are using folder security and we use it to assign rights. And yes there are others experiencing the same problems. We have approximately 60 developers working all at the same time.
Scott

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Tue Aug 09, 2005 12:37 pm

We've had a few similar reports when users were using folder security and had a large number of checkouts.

I'd suggest upgrading to Vault 3.1.1. We made some changes to checkouts/checkins that could help with the behavior you're seeing.

http://support.sourcegear.com/viewtopic.php?t=4397
Linda Bauer
SourceGear
Technical Support Manager

shenderson
Posts: 14
Joined: Wed Jun 23, 2004 9:36 am
Contact:

don't like this answer

Post by shenderson » Thu Aug 11, 2005 10:43 am

Not sure if I like this answer. Can you:

a) confirm that what Scott is saying is a bug
b) confirm that this is definitely fixed in 3.1.1

I have at least 30 of our developers that have approached me since we upgraded from 2.0 to 3.0.7 with this problem. I think we have lost weeks (collectively) of work because of this MAJOR bug. You guys should probably give me a call ASAP.

Oh, and the original poster of this thread, Scott, works with me at Match.com.

Thanks,
_________________________
Shane Henderson, MCAD
Technical Architect
Match.com
shane.henderson@match.com

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Thu Aug 11, 2005 7:51 pm

Can you:

a) confirm that what Scott is saying is a bug
b) confirm that this is definitely fixed in 3.1.1
We'd need more information before we could determine what the problem is. We can call you -- send me your phone number via the email link below or email Linda @sourcegear.com.
Linda Bauer
SourceGear
Technical Support Manager

Locked