VS 2005 - Error logging in

bnott · Post by **bnott** » Tue Sep 04, 2007 2:43 pm

After using the VS.NET 2005 integration since it was released, I am now recieving the following error when opening a solution:

---------------------------
Login Failure
---------------------------
There was an error logging in. Please try again.
---------------------------
OK
---------------------------

The vault GUI client works fine, as well as the web interface. The only think I can think that changed recently is the installation of VS.PHP (http://www.jcxsoftware.com/), which also integrates with visual studio.

Thanks,

Brian

Beth · Post by **Beth** » Tue Sep 04, 2007 3:56 pm

Is Vault still your default source code control? Check to see if the setting in Tools - Options - Source Code Control has changed.

After looking at their forums, I think you have to set Vault as your default Source Code Control Provider (that's a setting in Vault Tools - Options).

Also, when they say they support other source code control providers, it looks like they all mean with the MCSCCI API. That would be what the VS 2003 Compatible Client is. The VS 2005 Client uses the VSIP API.

In one of their posts here, http://www.jcxsoftware.com/jcx/node/272, they say, "VS.Php installer is based on the MSI technology and follows the VS.Net's VSIP guidelines for third party products."

I'm still poking around, but I wonder if they are using that interface to and if they're assuming everyone else is using MCSCCI? You may wish to check exactly which API they are using.

bnott · Post by **bnott** » Wed Sep 05, 2007 7:17 am

Yes, vault is still the default source control provider.

I have also been using VS.PHP for a while now (with vault) and it has always worked fine. The recent install was a minor upgrade.

Vault has stopped working for all projects and solutions - even those that are only C# projects where the VS.PHP extension is not loaded.

Brian

Beth · Post by **Beth** » Fri Sep 07, 2007 9:49 am

Have you attempted to unbind and rebind your project?

bnott · Post by **bnott** » Fri Sep 07, 2007 11:05 am

No - the vault options on the menu had disappeared. I have:

- Uninstalled VS.PHP (no change)

- Uninstalled Vault
Reinstalled Vault (install failed)

- Reinstalled .NET 2.0
Installed Vault (install failed)

- Uninstalled .NET 2.0
- Uninstalled VS 2005
- Installed VS 2005
Installed Vault (install failed)

So thats where I am right now. A clean .NET 2.0 and VS 2005, and Vault will not install.

The error is:

Error 1722: There is a problem with this Windows Installer Package.

I have seen it before (http://support.sourcegear.com/viewtopic.php?t=7982). However this time I've gone to even greater lengths of uninstall\reinstall, and still the vault installer fails.

Please help me get vault installed.

Brian

Beth · Post by **Beth** » Fri Sep 07, 2007 12:04 pm

Can you send me an email at support at sourcegear.com (attn: Beth) with a link to this forum thread?

bnott · Post by **bnott** » Fri Sep 07, 2007 1:25 pm

OK - Finally working.

Unfortunately, I tried two things at once, so I'm not sure which did it.

1. Found a KB article somewhat related that said to Enable NetBIOS over TCP\IP. So I did that.
2. Installed VS05 SP1.

(Did _not_ reinstall VS.PHP, so I don't know if that was the actual cause or not)

Thanks,
Brian

bnott · Post by **bnott** » Tue Sep 11, 2007 10:13 am

I just took a chance an reinstalled VS.PHP, and it was definitely the problem. Is there any chance that its an issue in the vault client that has just now been uncovered? Any way we could debug exactly why vault is unable to log in?

Thanks,
Brian

Beth · Post by **Beth** » Tue Sep 11, 2007 10:45 am

The thing is that at this time, we don't support VS.PHP, which is a 3rd party add-on for Visual Studio. We haven't tested it. The only thought I'd have on this is that you could try the MCSCCI interface (VS 2003 compatible client) with that project since the VS.PHP seems to be using VSIP as well. The one thing to be aware of is that if one person switched to MCSCCI on that project or solution, then everyone has to. I've been searching for more information, but I'm not sure how that would work with multiple applications trying to use the same interface at the same time.

bnott · Post by **bnott** » Tue Sep 11, 2007 11:30 am

I really don't want to go back to MCSCCI. I understand you don't support VS.PHP, but you do support VS 2005. And I don't think it can be assumed that VS.PHP is doing anything wrong. It's possible that VS.PHP is behaving correctly, and that it utilizes an aspect of Visual Studio that exposes a bug in the vault visual studio add-in.

Would you be willing to dig into this enough to determine if the bug actually lies in vault?

Thanks,
Brian

ian_sg · Post by **ian_sg** » Tue Sep 11, 2007 12:09 pm

Brian,

I'm really glad to see that you like the 2005 client this much.

I'd very much like to drop what I'm doing to fix this immediately, but I'm unfortunately not in a position to do that at this moment.

Visual Studio has an extensible project architecture, meaning anyone with the aptitude and inclination can add a new project type. The fine folks who produced VS.PHP took advantage of this. Each of these project types is responsible for implementing a number of interfaces that may be used by a source control provider like Vault. The specs for this are complex enough that there's a fair amount of variation in how different project types handle different scenarios. This is true even with the built-in, Microsoft-built projects. One bug in our client was caused by behavioral differences between C# Console Application projects and C# Windows Application projects, for example.

All of this was a long-winded way of saying that we certainly do not assume that VS.PHP is doing anything wrong. It's doing something differently, and we haven't yet figured out what.

Testing the new client with VS.PHP and making sure it works well is on our list of things to do, but it's of somewhat lower priority because it's an add-on. We will get to it, but I can't yet say when. For what it's worth, your feedback has increased my personal desire to get it into the next release. If I can, I will.

Beth · Post by **Beth** » Tue Sep 11, 2007 12:21 pm

Brian, would you be willing to perform some logging for me so that I could see if there are any answers there?

Increase your Vault Server Logging to debug mode (this requires an iisreset). Then turn on Client Side Logging and IDE logging.

Then recreate the scenario. Zip up the logs and either attach them here or send them to support at sourcegear.com (attn: Beth) with a link to this forum post.

bnott · Post by **bnott** » Tue Sep 11, 2007 12:22 pm

Thanks for the reply Ian, I understand that this would be a lower priority.

For what its worth, maybe it will help you in your testing when it comes time: It's not just VS.PHP projects that are affected. The bigger problem for me is that even new or existing C# projects can no longer connect to vault.

Take your time. Anything's better than SourceSafe : )

Thanks,
Brian