SourceGear Support

Using it now - thanks, Linda!

Is there one?

Thanks,
Eric

We have several customers where our call to ServerOperations.Login() more than a minute to complete. Is there any way to improve on this?

Eric

A customer is running our client and we're not getting any results back from GetWorkingFolderAssignments. I've attached a Vault client api log that has some errors in it. Any idea what's going on? She also says, "The files you had me generate look like they are confirming my suspicion. I have a...

Jeremy, Thanks, I was able to get this to work. This is what I had to do: final ClientInstance ci = new ClientInstance(); ci.Init(VaultConnection.AccessLevelType.Client); ServerOperations.client.set_ClientInstance(ci); VaultLib.Brander.getInstance().setMode(connection.isFortressMode() ? Brander.Mode...

We can create multiple client instances, running ServerOperations.Login() after setting the client LoginOptions for each one. When we do, running ServerOperations.GetWorkingFolderAssignments() only returns folders corresponding to the first login session. I guess our second call to ServerOperations....

Oops. Got a "The extension log is not allowed" error attaching that file. Here it is. I'll check with the user about vault.exe

Can you take a look at this error? We're using the 4.1.4 Java client API release, and a customer is having problems using our integration to connect to his server. The client never appears to finish connecting, and gets these exceptions: 2/25/2009 1:25:52 PM <crypto>: Failed encryption. [System.Argu...

The Vault and Fortress client API's do not appear to be compatible. Trying to connect to Fortress with the 4.1.4 Vault client API gives a 'The server uses a protocol that is not supported by this client' error. If this is the case, is there any chance of getting a client API that works for both?

Same thing with 4.1.4.18419 - "vault.cmd listchangeset" shows all files modified. The Pending Change Set in the 4.1.2.18185 Vault Client shows just 3 files

Eric

Your latest Java CLC client (vaultJavaCLC_4_1_3_18336) reproduces this issue. With a 4.1.2 client installed, with files checked out from vaultdemo.sourcegear.com "Repository A", and with CVS-style checkouts selected, and "Detect modified files with CRCs" unselected, running the v...

Do you think (or know) that 4.1.4 has fixed this issue, or something related to it? This behavior has been around for almost a year (since the 4.0.5 client). Does the logging tell you anything?

Will the 4.1.4 client API work with the customer's 4.1.2 client?

This issue is still occurring with the latest 4.1.2 client API we're using (from viewtopic.php?f=32&t=10824), i.e., ProcessCommandListChangeset returns no files modified when there are modified files. At other times, it returns all files modified. This occurs on a customer's system who was the 4...

This issue is still occurring with the latest 4.1.2 client API we're using (from http://support.sourcegear.com/viewtopic.php?f=32&t=10824), i.e., ProcessCommandListChangeset returns all files modified (and in some cases returns no files modified), even when there are modified files. This occurs ...

Jeremy,

We do log in based on parameters given us by the user. I can get Rolland an updated version of our client, with debugging enabled if that will help - let me know how to do that.

Eric