Upgraded from Vault 3.1 to 3.5 and getting errors now.
When trying to switch to a different server, the following error is displayed:
Specified cast is not valid.
Then if I try to click the File menu, I get:
Object reference not set to an instance of an object.
I had to kill it using Task Manager.
These errors smell like bugs to me. I hope this is not a bad omen as to the stability of 3.5; we never really had any problems with 3.1 and maybe I should have left well enough alone...?
Vault Errors
Moderator: SourceGear
Do you mean switching to a different Vault Server? Somethimes the error "Specified cast is not valid" means that SQL Server has run out of disk space.When trying to switch to a different server, the following error is displayed:
The first thing to check is the Vault Server log, sgvault in %windir%\temp\sgvault. Are there any errors corresponding to these client-side errors?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager