SourceGear Support

Completely reinstalling the machine has fixed the problem - I do reckon that it was a machine stability problem rather than a vault problem.

Thanks,

His account works fine on another machine and another users account dosn't work on his machine. A number of other applications such as IIS have stopped working as expected and are exhibiting strange errors also. We are going to have his machine rebuilt, afterwhich I expect his problems to go away. I...

Cool, I'll have a look at the log after the weekend and try points 1 and 2. We have already tried clearing out the cache and this hasn't changed anything.

Here goes a complete dump from the help-tech support window: Client Information Vault Client Version: 3.1.1.3506 .Net Framework Version: 1.1.4322.2032 Operating System: Microsoft Windows 2000 Professional Service Pack: 4.0 OS Version: 5.0.2195 Total Physical Memory: 494.73 MB Time Zone: (GMT+12:00) ...

One of my developers gets the following messages when trying to perform a get from the Vault Gui Client. Sometimes it works, but mostly not. * An exception was encountered during the get latest operation. Exception: Server was unable to read request. --> There is an error in XML document (1, 998). -...

The upgrade worked fine and took 40 minutes as oposed to the test upgrade on different hardware taking 2.5 minutes for our 22GB db. What I did discover during the actual upgrade was that our IIS server is actually running on a PIII which explained a number of speed issues. Strangly enough our proble...

Please add my vote to this also, if I've not previously voted for it that is. It drives us batty every now and again.

The upgraded backup reports 3.1.1.1 as the schemaversion - so it worked successfully. I noticed that our dual proc xeon P4 > 2ghz server holding our live vaultdb took 40 minutes to upgrade from 2.x to 3.0x compared to my test upgrade which was quicker than a click of my fingers on the AMD machine. C...

Please add my name to the feature request too.

Cheers,

A couple of my users have been getting exactly the same problem that has been described on this thread with respect to checkouts. I have found that it can be simply resolved (whenever it happens) by deleting their checkout list cache file and vola they see the file as checked out to themselves or so...

It turns out that someone scheduled a backup of our SQL Server machine while I was doing the branch and that killed things.

Ah, thats a helpful post I'd not found before - I'll follow the db maintance thru and see where that takes me. In terms of performance, it's generally just branching but we also get the occasional failed checkin. Apart from that it's slower during the day compared to 2am in the morning when I'm the ...

Ok the first point I should make is that we are not on the latest version of Vault - 2.06. Branching during working hours used to take 10-15 minutes, but recently it's ballooned out to a massive number of hours (9 so far) when run over night - this is a regular branch we do every two months as part ...

Just a thought, do you encase your paramaters in double quotes when they include spaces? eg VAULT.EXE COMMIT -user "user" -password "password" -host "host" -repository "repository" "$/Path/File" I don't know what error you would get if say the reposi...

Thanks for that, I might just try and find a spare machine without Vault on it.