SourceGear Support

Vault 3.1.1 has got a fix for this.


Bye,
Herbert.

Here is the error in the server log: ----10.08.2005 14:39:22 --()-- A configuration error occurred reading [SMTPAuthPassWord] from vault.config. ConfigReader reported the following exception: Bad Data. For me it happened after upgrading from 3.1.0 to 3.1.1. However, I also had some beta versions of ...

Yeah, had the same problem.

Ciao,
Herbert.

To throw in my 2cents worth: We got a similar structure as you propose. What we do is we only branch on demand however. Meaning we label our releases and branch when we need to. The only time we do this is to create a Service pack of an older version. Sometimes our customers are not happy to update ...

Hi, Found out that it depends on the default user rights. If you switch them off, then only labels are shown in the history. So, if you want to test yourself, upgrade the DB to vault 3.1 (3476) - I think it was Beta 3. Then look at a user: e.g.: mdruml No checkin history is seen, but if default user...

@Jeff: Yes, we are running Beta3 but not even for a week yet so it is too early to tell.

Bye.

Hi, Ok we did some more tests. The problem is with the user and not with the computer. On one and the same computer, one user sees the complete history, the other only labels. Rights to the project are the same for both users. This problem has only appeared once we updated to Beta3. Before, everythi...

Hi,

using Beta 3: For some of our users, the show history command will only return label actions. No other actions (e.g.:checkin/out) are shown even though all actions are selected and no filters are applied.
For other users it works perfectly.

Thanks,
Herbert.

Hi,

Just tested this in Beta3, its not yet fixed. Any chance you can do this for 3.1 final?


Thanks,
Herbert.

Hi, we have similar problems and I have been in contact with sourcegear but were unable to get to the bottom of this so far. To get you up and running when it happens, you can however: 1. Close all clients 2. Delete all "CacheMember_CheckOutList" from your HD. I do it this way from the com...

Yes, but be careful to use this as certain features will not work anymore on that label e.g. pinning.

Check out the help files.

Hi,

Since there is no response to this, I guess it is not going to happen.

Different approach: Is there any way I can query the Vault server version through the SQL Server? We would then write a vault launcher, which first checks for correct version and then launches vault.


Thanks,
Herbert.

hmm, dont know how we could have missed that one , I apologize for wasting your time.


Thanks,
Herbert.

Hi Jeremy,

I see a few, but not all are there, e.g.: if "Get latest version" fails. There might be others as well....


Thanks,
Herbert.

Hi, Currently when an error occurs vault just writes an error into the Messages Panel. When an error occurs, it would be great if a popup lets the users know that something went wrong and to look in the message pane (after ending the transaction). We had cases when a get latest failed for some files...