Hi,
Sometimes I get a NullReferenceException when using Vault through the VS 2005 client. It seems to be mainly when a connection is first established.
For example, I created a new project, and checked the Add Solution to Source control option. VS attempted to do so after I selected the profile to use to logon, I got a NullReferenceExceception. After clicking OK, I again get the Logon dialog, select the profile again, and it works fine.
Also, using Vault as my SCC provider in HelpStudio 3.0.1 always gives me the same exception (which I am assuming has something to do with Vault at this point).
This started happening after I upgraded to Vault 3.5.2.
Any ideas?
NullReferenceException when using VS 2005 integration
Moderator: SourceGear
Are other users experiencing the same problem? Can you login with the same profile with the Vault GUI Client?
Is there anything in the Event Viewer on the client machine that corresponds to the error message?
Anything in the Vault Server log? It's sgvault.log in %windir%\temp\sgvault on the Vault Server machine.
Is there anything in the Event Viewer on the client machine that corresponds to the error message?
Anything in the Vault Server log? It's sgvault.log in %windir%\temp\sgvault on the Vault Server machine.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Unfortunately I am the only user. The Vault GUI Client works fine.lbauer wrote:Are other users experiencing the same problem? Can you login with the same profile with the Vault GUI Client?
Nope.lbauer wrote:Is there anything in the Event Viewer on the client machine that corresponds to the error message?
Nothing odd. Mostly SSL Enabled logins, and a few SSL Disabled ones.lbauer wrote:Anything in the Vault Server log? It's sgvault.log in %windir%\temp\sgvault on the Vault Server machine.
No, I just did an upgrade on the existing server.lbauer wrote:Did anything about the Server machine change -- location, IP address, etc?
This has also happened when I first attempted to add a solution to source control which was previously not bound.lbauer wrote:You might try unbinding and rebind the project. This is in Visual Studio under File->Change Source Control.