SourceGear Support

Hi Linda, we've solved the issue. It hasn't been Vault Professional. Because our Firewall Admin forgot to change one thing, Vault Pro had been treated like a machine outside of our network. So the connection termination came from our firewall not from Vault Pro. Logfiles are always sooooo helpful. T...

Hi there, we've been using Fortress 2.0.2.187753 until yesterday and moved now to Vault Professional 5.1.2.19283. The whole migration process to a new W2K 2008R2 x64 server worked like a charm, but users are complaining about Vault client timeout issues. Every once a while (they say it takes anythin...

Any news on teh issue? Could you reproduce the problem or do you need a sample file?

Frank

Beth, get -workingfolder sets temporarily a working folder. Please compare your CLC documentation: -workingfolder [disk_path] Retrieve files to working folder specified by disk_path. The working folder specified is temporary, used only for this get request. This option cannot be specified with -nonw...

Using Vault 4.1 the command line client throws a VaultClientOperationsLib.WorkingFolderConflictException after retrieving two files one after each other using the get command with temporary working folders: get -workingfolder "F:/Vault_4.1/EWB_3.1" "$/Products/EngineeringWorkbench/tru...

Please add one more vote for the 'Rollback Changeset' feature request.

Beth wrote: Starting with version 3.5, setting multiple folders to the same working folder is no longer a feature. In the past there were issues that cropped up from that being allowed. One thing you can do is set the working folder of $ and check Force all subfolders to use inheirited working folde...

Please add my vote as well.

Thanks,

Frank Neumann

Eric,

what is the current result of your re-evaluations? Did the re-evalution lead to a concrete plan for the implementation of this feature?

Frank Neumann

Hi Eric, in the meantime we investigated the possible effort to adapt to the changed working folder policy (in 3.5) on our side. Unfortunately we will also have a substantial effort in order to change our repository and project layout. I could provide you offline with an estimate in man days for the...

OK - thanks for the update. I am waiting for your input.

Frank Neumann

After dealing with several webservice interoperablity issues between the Java and the .NET world and a new version of Fast Issue Track easing some of the interoperability issues, we managed to establish the integration between Vault and our enterprise wide bug tracking tool Fast Issue Track (http://...

We managed to integrate our bug tracking software (Fast Issue Track) via the Dragnet interface as discussed with Jeremy in March. Our Issue tracker uses the word "issue" for all managed requirements and bugs and also generates links when this word is found. Vault uses the words "item&...

Hi Jeff, Eric and Dan: I looked through the whole discussion thread again and got the impression, that your decision to disable the ability to set the same working folder for two repository folders without communicating that clearly to your customers was definitively not that what customers expected...

Hi Jeff, Eric, Dan and who else was involved with this topic meanwhile: I'm pretty shocked to read this (and especially the explanation in http://support.sourcegear.com/viewtopic.php?t=6483). Your ' Solution ' to disable the ability to set the same working folder for two repository folders is the wo...