Can't Open from Source Control in VS2003 with Vault 4.1.3

[DHall]

I have been using Vault Client 4.1.1 with VS2003 on XP (with all the latest service packs) for some time. Our Vault server was recently upgraded to 4.1.3 a couple weeks ago and I upgraded the client to 4.1.3 at the same time.

Today is the first time since the upgrade that I tried to open a solution from Source Control within the VS2003 IDE and it's not working for me.

WhenI first select the "Open from Source Control" menu option, I am prompted for my login and then to choose one of two repositories. I choose the repository I have always used, and then nothing more happens. No errors, nothing. I have waited for over 5 minutes... Then I try a second time to "Open from Source Control". Again I am prompted for login and repository. I make the same choice, and this time, I immediately get the following exception:

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at VaultClientPresentationLib.FormIDEViewRepository.FormIDEViewRepository_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I click Continue, and the "Create Local project from Vault" is shown, but there is nothng shown in the repository tree view. Clicking on "Refresh Tree" has no effect.

Since I can't see the repository tree, I have been unable to open any projects from source control within the VS2003 IDE.

I can see the full repository from within the Vault Client.

Any ideas where to look or what to do next?

[Beth]

Was the solution you performed an "Open from Source Control" on an older solution that was used in Vault 4.1.1 or is it a brand new one?

What happens if you try the Recent Projects/Solutions quick link to open one that you were working on in Vault 4.1.1?

Does this happen on just one client or all clients?

Could you post screenshots of the values under these registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders

[DHall]

I never got to the point of selecting ANY solution (new or old) to "Open from Source Control" because as I said in the original post, no solutions show up for me to choose from. I have not tried adding any new solutions to Vault from VS2003 since the upgrade, but all of my development machines with VS2005 on them seem to be working fine even after the upgrade to 4.1.3.

Since my original posting, I uninstalled the Vault client and made sure the cache was cleared and then reinstalled 4.1.3 and the symptom is still identical.

If I try to open an existing recent project in VS2003 that was working before the upgrade, It immediately brings up the "Change Source Control" dialog and the only way out is to work disconnected or to fully disconnect the project from source control. If I disconnect the bindings then reconnect, then click Browse, I get exactly the same exception as I originally reported, with exactly the same call stack.

On a number of different machines with only VS2005 installed, everything seems to be workng OK since the upgrade. As fas as I can tell, the only problem I have is on this one machine which has only VS2003. I don't have any other VS2003 machines to try with upgrade. This is the only one I use for VS2003 projects. The stand-alone Vault client is able to see the full repository structure with no problem.

I've attached the two screen shots of the registry that you requested.

Registry Screen Shot 1

RegistryScreenShot1.JPG (28.99 KiB) Viewed 3831 times

Registry Screen Shot 2

RegistryScreenShot2.JPG (30.84 KiB) Viewed 3831 times

[uros377]

Same issue here. I upgraded from Vault 4.1.2 to 4.1.3, and opening from Source Control stopped working. Stack trace is the same as above, so I won't repeat it. Requested registry entries are as follows:

2008-10-11_142647.jpg (63.63 KiB) Viewed 3785 times

and

2008-10-11_143059.jpg (59.75 KiB) Viewed 3785 times

This worked OK with previous version of Vault (4.1.2), and I confirmed that Vault is default SCC provider. I even tried clean installing, with fresh database (empty), but no luck, so it should not be upgrade issue.

After second try (as in previous post, after first nothing happens), and after choosing to continue on unhandled exception window, form for choosing solution appears, but looks like this:

2008-10-11_144006.jpg (29.99 KiB) Viewed 3784 times

. None of buttons are working on this form.

I confirmed that this happens on Windows XP as well as Vista x32. From Vault client, everything is OK, as in previous post. After returning to Vault 4.1.2, everything is back to normal.

I am interested in your opinion, how long will it take to investigate and fix this, and should I return to 4.1.2 and wait for next version where hopefully, this will be resolved?

In case you need some more information about my configuration, or anything, I am willing to help in resolving this.

[uros377]

And I found what was causing this object reference exception. I had to set working folder for root of respository tree (it was empty). After defining working folder for root, everything started working OK. Even after this, when I removed working folder association (from GUI client), it continued working OK. It was just that, after creating new respository, you have to set working folder for root of the respository.

This is definitely bug, since you cannot create new respository and add solution to it until you set working folder.

Hope this helpes to other people havving same issue

[kha]

Uros377,
Can you please be more specific on how to create working directory for root repository? I'm confused
Will client 4.1.2 work with Vault 4.1.3? I've upgraded vault server 4.1.3 and don't want to change it.

Thanks!

[Beth]

kha: I see where I have received an email on this issue, so I will take this offline to look at it.

uros377: Thanks for the update. I had one other user that setting a working folder worked for as well, but it doesn't have to be set at root. As long as the projects and solutions line up with what VS has set, then it's ok.

DHall: Could you try setting a working folder in Vault for your solution that you are having problems with? It must match exactly where VS places the files. Does that fix it for you?

[jeremy_sg]

We've discovered the cause of this bug. A fix will be included in 4.1.4. A workaround would be to log in to the repository using the Vault GUI client as the same Vault user before trying the operation in VS 2003 . If you would like a prerelease build of 4.1.4, please email support at sourcegear.com ATTN: jeremy with a link to this thread.