Using Version 4.0.6(15954)
On start up of client, getting this error:
Object reference not set to an instance of an object.
Any clues/fixes?
Thanks in advance
-franc
Problem with client on startup
Moderator: SourceGear
Problem w/login
After login, and NO it doesn't let me choose repository
yes it was working before.
There is another user that is having problems not being able to check-out items in visual studio.
thanks!
-f
yes it was working before.
There is another user that is having problems not being able to check-out items in visual studio.
thanks!
-f
I got this error too (with Client 4.1.1 and in Visual Studio 2008). It the error occurs while loading a Visual Studio project, a VAULT login dialog is shown after that. In other cases I am able to load a project, but the error occurs when I work on sourcecode files.
I assume the cause of the problem is a network/database/timeout problem since the error does not occur when our VAULT system is fast. I work over a VPN connection over the internet.
Our sgvault database is very large (4 GB). I assume the problems are based in the database size.
I assume the cause of the problem is a network/database/timeout problem since the error does not occur when our VAULT system is fast. I work over a VPN connection over the internet.
Our sgvault database is very large (4 GB). I assume the problems are based in the database size.
After restoring my OS system using an image I created a couple of days before, the NullReferenceException does not occur any longer. Since I work with absolutely the same working folders (which were not restored), that gives me the clue that the problem is caused in the VAULT client on the local machine.
pacout: Can I have you start up Client Side Logging? Recreate the scenario and then provide me both the Vault Server Log and that client log? You can either post them here or you can send an email to support at sourcegear.com (attn: Beth) with a link to this thread.