VS2017/Vault not binding

[mmorris]

First noticed: 9/10/18 Monday. (>= 4 cases so far; everything has been working fine for the past several months; 2 independent confirmations that everything seemed fine on Friday 9/7/18).
Versions of VS2017 used: 15.8.2, 15.8.3, 15.7.5
Version of Vault Client: SourceGear Vault Standard 10.0.0 (736)
Version of Visual Studio 2017 Extension used: 10.0.1 (793) and 10.0.2 (936) (Edit: a.k.a. Enhanced)
OS: Windows 10 Enterprise; 64-bit
We do generally use SSDT, and I noticed on another thread that some Vault/SSDT/VS2017 issues had occurred:
viewtopic.php?f=5&t=23028&p=79279&hilit=VS2017#p79279

(As a side note, a large # of SSDT/VS2017 issues have occurred...
e.g. https://developercommunity.visualstudio ... -code.html)

FYI - VS2012, VS2015 (in our installs) do not have this issue.
Some images of the errors are attached.
This issue is most obvious when one tries to 'Open from Vault' (in VS2017)

I'm going to keep trying options (including one in the sourcegear thread above), and as I find additional data, I will add it here.
Thank you for your time and help. Please let us know of any questions.

We do have one apparent outlier: for a virtual machine with VS2017/Vault, no issue detected.
We tested on another virtual machine that my team has direct access on, and the issue was definitely present.

Sincerely,
Michael M.

[Tonya]

Hi Michael,

Thank you for the details! Following the advice given in the link you listed below would be my first suggestion.

Please keep us informed on the status. If the problem persists, please let us know which Vault plugin you have installed (classic or enhanced).

Thanks,

Tonya

[mmorris]

Edited above: Enhanced.
For some reason, your download page calls the Enchanced version the Extension... (image below).

I do (on my computer) have access to both Standard and Enhanced versions. The Standard doesn't work (of course)... though it will access Vault and try... but it pulls blank Projects back. The Enhanced version has the errors shown above... and will not access Vault at all.

Please note: I will be out of the office the remainder of this week, but someone else in my office will be watching this while I am out. Thank you!

[grandavenuesoftware]

We are also seeing this issue on multiple machines. Visuals Studio 2017 version is 15.8.3. Vault version is 10.0.1.793. We just noticed this behavior today. We will try the uninstall and re-install.

[grandavenuesoftware]

Reinstalling the extension appears to have fixed the issue.

[Tonya]

Glad to hear! Thank you for the update!!

Tonya

[adamsbrla]

This has also happened to me starting yesterday. It's as if the extension is disappearing from Visual Studio. Reinstalling does the trick, but it doesn't last beyond the next reboot of the machine

[Tonya]

Can you please try to reinstall the Vault extensions while running Visual Studio under an account with elevated "administrative" privileges?

Thanks,

Tonya

[Tonya]

A couple more questions:

1) What is set under Tools -> Options => Source Control?

2) What appears under Help -> About (should show the Vault Extensions that are installed)?

Tonya

[adamsbrla]

Had to reinstall again this morning. When opening VS, I get an error indicating that the source control provider could not be found. When going to Tools, Options, there is nothing set under Source Control. Under Help, About, the extension is not showing

Ive attached a zip file with screenshots of the various messages

[Tonya]

How are you installing the Vault Plugins? Are you using the classic or the VS 2017 extensions?

What version of Vault do you have installed? What version of Visual Studio are you using (along with the edition, pro, community, etc)?

In the screenshot labeled "SourceControl", does the drop down list Vault?

VSIX extension like Vault can be installed using VSIXInstaller.exe from the command line. This is found under your VS 2017-install-directory \<Edition>\Common7\IDE directory. Running this command line utility with the /? option will bring up a window with all of the options ( "VSIXInstaller.exe /?" ). You may want to give this a try.

Once an extension is installed, it will show up in the VS 2017-install-directory \<Edition>\Common7\IDE\Extensions\<some-nonsensical-hash-name> directory. Searching the VS 2017-install-directory \<Edition>\Common7\IDE\Extensions\** for VaultLib.dll should show. Please let us know if this disappears when you notice Vault being reset.

Thanks,

Tonya

[adamsbrla]

I had been installing the plugin just by double clicking on the vsix file I downloaded from this site.

Vault version is Standard Version 10.0.1
VS is 2017 Community, version 15.8

I ran Command Prompt as an administrator, and installed the plugin from the command line as you described. Opening Visual Studio shows everything working as expected. I'll update the thread if it reverts back again later after a reboot

[adamsbrla]

Failed again this morning. It's odd, it's almost like it happens every 24 hours. I shut down yesterday, restarted last night and worked without issue. When I open a project, the following appears

2018-09-13_8-39-15.png (36.82 KiB) Viewed 18949 times

[Tonya]

Before you reinstall, can you please confirm the following:

Once an extension is installed, it will show up in the VS 2017-install-directory \<Edition>\Common7\IDE\Extensions\<some-nonsensical-hash-name> directory. Searching the VS 2017-install-directory \<Edition>\Common7\IDE\Extensions\** for VaultLib.dll should show.

Is this information getting deleted from your system?

Thanks,

Tonya

[mmorris]

Back from vacation, and need to continue this.
Most of our issues were fixed with reinstalling, but 1-2 computers are still having issues.
For those computers which are fixed, there does not seem to be a problem with losing the info on reboots, but we will monitor.

In my case (in addition to the errors mentioned previously):
1) VaultLib.dll does not appear in VS 2017-install-directory \<Edition>\Common7\IDE\Extensions\**
2) When I try to install the Extension VSIX Installer, I get the following error:

Error3.PNG (5.57 KiB) Viewed 18869 times

3) I cannot uninstall the file in the Windows tool 'Change or Remove a Program'. When I look for the file, only the standard version appears (the following is sorted by Publisher).

UninstallPrograms.PNG (5.38 KiB) Viewed 18869 times

(I do use VS2012 on my computer also, so I do need the standard version....)
4) I was able to get the 'VSIXInstaller.exe /?' to work, and I see a bunch of options. I will start trying them, but do you have any recommendations (or additional examples)? I can only see about one page length of the options... so many of the arguments (and probably examples) are effective invisible. Generally i can also see down to '/culture'.
E.g.: /u requires the vsixID. What is the vsixID? I assumed it was '10.0.2.936', but that does not work. I tried the /f, but that requires the vsix_path... which I guess is the directory of VS2017? Could you confirm?
5) Tools->Options->SourceControl

SourceControl.png (4.55 KiB) Viewed 18869 times

6) Help->About

HelpAbout.PNG (35.69 KiB) Viewed 18869 times

So, diagnosis for my case: VS2017 and Vault think that the Extension version is installed... but, it is not 'successfully' installed... and cannot currently be uninstalled (though perhaps it can with the correct 'command prompt' statement). So somehow I need to successfully uninstall (or clean something up) before I can again install.

Thank you for your time and help.

Sincerely,
Michael M.