SourceGear Support

I've used sgdm with TFS on an extremely limited basis, and it seemed to work fine. I can't really offer any advice about getting the most out of it, but it behaved fine in the (admittedly mostly trivial) tests I threw at it.

bfinney: > unresolved = completed ?? Why does unresolved mean completed? I can't get my mind around that at all. I'm not sure how to answer this apart from the stuff in the link above. Remember the different contexts: when a developer checks in code that he believes will fix a logged bug, his work ...

Only that we're having a helluva time getting mono to build on our Solaris machine.

Not given up, but the frustration level is high...

Sorry for the delay. If you're getting "Unable to get file by label" errors in the GUI client as well, the problem certainly lies on the server side. The first thing to do would be to run the VSS analyze utility on your database with the -f and -c switches. The SourceSafe automation compon...

Just the service would have to be restated - I can't think of any situation where a restart of the whole machine would be required.

The installer recommends a reboot, IIRC, but it's not actually necessary.

You've pretty well got it down pat: in this context open = open status; unresolved = completed status.

There's some additional detail about all this in this thread:

http://support.sourcegear.com/viewtopic.php?t=4371

Yeah, it does sound like the connection is being killed prematurely. If you can, please send us (or have a colleague send us) a copy of the SOS server log - it should contain some evidence if the killed connections are the cause and not the effect.

Most likely you need to refresh the project tree. This is a time consuming operation, so we don't invoke it automatically upon connection, but require a manual trigger.

You should select the root folder, then use the command View->Refresh Project tree.

Before I dig very deeply into this, could I get you to upgrade your CLC to 4.1.2? We made a ton of changes to the command line client for 4.1.2, and overall it's much more stable than 4.1.

Unfortunately, there isn't currenly any way to get more verbose info out of the CLC. It is logged as an enhancement, though.

Yuck. I guess I have no choice but to spend some quality time with our molasses-slow Sun machine.

Interesting. Have you tried this on the Windows CLC (or any other unix "flavor")?

I'll try to reproduce this here, but I won't be able to get to it until Monday.

We'll need to get some more info from you in order to diagnose what's going on. Specifically:

What version of vault are you running?

What error messages do the clients receive when the checkins fail?

Is there any relevent entries in the vault server log?

The -database parameter takes a path on the machine that hosts the server. If you're supplying the name listed in the GUI dropdown, substitute the -alias parameter for -database.

Otherwise, run a GetDatabases command to see the sever path to the database.

Honestly, -alias is probably much easier!

D'oh! That'll teach me to read too quickly. The home directory in 4.x versions of SOS is not within the install directory - by default it's in C:\Documents and Settings\<user>\Application Data\SourceGear\SOS. If you look in that path, you should see a <servername>.key file. This is the actual key - ...