Skip to content
This repository has been archived by the owner on Jun 21, 2023. It is now read-only.

2.3.2.32 fails to install to VS 2017 with "A value for 'Component' needs to be specified in the catalog." #1213

Closed
BladeMF opened this issue Sep 1, 2017 · 27 comments

Comments

@BladeMF
Copy link

BladeMF commented Sep 1, 2017

Today an update showed up and it fails to update. Tried two times. My VS is version 15.3.3.

I have attached the install log.

VSIXInstaller_c5acfac7-b477-48c5-9952-7b0d7840945c.txt

@grokys
Copy link
Contributor

grokys commented Sep 1, 2017

Hi @BladeMF,

Unfortunately there is a known problem with the VSIX installer in Visual Studio 15.3, Microsoft are working on a fix, but in the meantime could you try the instructions they provided here? #1206 (comment)

You may also want to check out the issue on the VS developer community site: https://developercommunity.visualstudio.com/content/problem/102178/error-installing-github-extension.html

@BladeMF
Copy link
Author

BladeMF commented Sep 1, 2017

Hi @grokys,

I guess I can wait for a fix from MS, it's not that crucial yet. I just thought I'd let you know. I'm guessing you're positive that this is the same bug or not some incompatibility?

@grokys
Copy link
Contributor

grokys commented Sep 1, 2017

I'm not positive this is the same bug (@Michael-Eng does this look like the same problem to you?), however, I suspect that the fix/workaround will be the same.

@shana
Copy link
Contributor

shana commented Sep 1, 2017

This doesn't look like the same bug, it looks like a packaging issue. @BladeMF Which version of the extension do you currently have, and how did you install it originally? From the Extensions and Updates menu, or from the Visual Studio installer when you installed VS itself?

@shana
Copy link
Contributor

shana commented Sep 1, 2017

I've been trying to repro this but no luck so far. 😞

@BladeMF Uninstalling the extension manually might fix this problem. Could you try the following steps:

  1. Shutdown VS 2017
  2. Open a Developer Command Prompt for VS 2017 in administrator mode (right-click on the Start menu shortcut and Run as administrator)
  3. run vsixinstaller /uninstall:c3d3dc68-c977-411f-b3e8-03b0dccf7dfc to uninstall the currently installed extension

Hopefully that completes successfully and then you can install the latest version. 🤞

@BladeMF
Copy link
Author

BladeMF commented Sep 1, 2017

Maybe to repo this you need to install this on 15.3 and then upgrade to 15.3.3 and then upgrade the extension.

I wonder if I should wait for the fix for the other bug so we can all see if they are related. If you didn't miss anything in the package, maybe it is a bug.

BTW, I haven't tried uninstalling from the UI.

@vishnu4
Copy link

vishnu4 commented Sep 1, 2017

I have the same error
VSIXInstaller_5107ee1d-b3e9-4de3-92ad-1566cfdf8cf0.txt
and i tried the uninstall command and the #1206 (comment) above, and neither helped me.

@shana
Copy link
Contributor

shana commented Sep 1, 2017

@vishnu4 When you ran the uninstall command, did it also fail in the same way? Do you have the log for that?

@tinaschrepfer @Michael-Eng Could this be a side effect of setting the static install location of the extension in 2.3.2.32?

@shana
Copy link
Contributor

shana commented Sep 1, 2017

@BladeMF @vishnu4 We've had problems in the past related to bugs in the VS and VSIX installer which kinda have similar symptoms. #987 (comment) and #987 (comment) helped in the past, could you try those steps?

@Michael-Eng
Copy link

I installed the latest GitHub extension on the VS Marketplace this morning and it installed successfully.

I discussed this with Tina - We're wondering if this might be related to @BladeMF upgrading the GitHub extension.

@BladeMF, can you please run https://aka.ms/vscollect and then put the resulting zip file somewhere we can access it (it's large)

Thanks!

@vaindil
Copy link

vaindil commented Sep 1, 2017

Same issue here. Tried both of the workarounds above, neither worked. Install log is below, the error was the same both when upgrading and when running the vsixinstall command.

@tinaschrepfer
Copy link

@BladeMF , @vaindil, do you recall what your install order was for GitHub extension? Looking at the logs it seems like there was an attempt to upgrade from 2.3.0.24 to 2.3.1.30, which was successful, and then an attempt to upgrade from 2.3.1.30 to 2.3.2.32, which was unsuccessful. Did you do a system restore at any point between each install?

If you can, would you mind outputting all the directories and files under Common7\IDE\Extensions and upload that somewhere? We don't need the actual files, just the paths.

Thanks!

Tina

@BladeMF
Copy link
Author

BladeMF commented Sep 2, 2017

@tinaschrepfer My current version is indeed 2.3.1.30 (haven't had any problems before).

My files are:

01.09.2017 г. 09:43

.
01.09.2017 г. 09:43 ..
18.08.2017 г. 18:37 0jb0linh.k5j
28.08.2017 г. 14:57 1dpdmeqp.yfv
28.08.2017 г. 15:02 1zra3rwa.nr0
28.08.2017 г. 15:02 5gcenb00.exe
30.08.2017 г. 01:08 Application
28.08.2017 г. 15:02 bb3pjrtu.4hg
28.08.2017 г. 15:10 Community
28.08.2017 г. 14:49 854 DesignersCommonPackage_Registry_Common_x86.pkgdef
28.08.2017 г. 14:49 828 DesignersCommonPackage_Registry_x86.pkgdef
28.08.2017 г. 14:49 3 912 DSLTextTemplatingRegistry_x86.pkgdef
28.08.2017 г. 14:49 86 DSLTextTemplating_FileAssoc_Sxs.pkgdef
28.08.2017 г. 15:02 easce2x4.boy
28.08.2017 г. 15:05 ecazgoto.s4s
28.08.2017 г. 14:45 eils2yaz.zso
28.08.2017 г. 14:57 Enterprise
02.09.2017 г. 06:06 0 extensions.configurationchanged
28.08.2017 г. 15:06 eyxtamka.fb4
28.08.2017 г. 15:07 fmdmssq2.ckm
01.09.2017 г. 09:43 GitHub
28.08.2017 г. 15:02 i2gjzacw.dhn
28.08.2017 г. 15:02 jggihpoz.gdy
28.08.2017 г. 15:09 kb1u5q1t.yex
28.08.2017 г. 14:57 ksssvfur.xzw
28.08.2017 г. 14:49 9 174 LayerDesignerDslPackage_x86.pkgdef
06.04.2017 г. 01:44 Merq
28.08.2017 г. 15:10 Microsoft
28.08.2017 г. 14:49 229 ModelingProjectTargets_x86.pkgdef
28.08.2017 г. 14:49 87 ModelingProject_Registry_FileAssoc_SxS_x86.pkgdef
28.08.2017 г. 14:49 934 ModelingProject_Registry_Pkg_x86.pkgdef
28.08.2017 г. 15:10 Mono.Debugging
28.08.2017 г. 15:06 nxfodbrb.0f1
10.03.2017 г. 17:26 Professional
28.08.2017 г. 14:49 87 Progression_GraphDocument_FileAssoc_Sxs_x86.pkgdef
30.08.2017 г. 01:08 566 Progression_NativePackage_Component_x86.pkgdef
28.08.2017 г. 15:00 ProTools
30.08.2017 г. 01:06 pyrgfpsc.ea0
28.08.2017 г. 15:13 q2vm3w32.pmy
28.08.2017 г. 15:00 StaticAnalysis
28.08.2017 г. 15:02 TestPlatform
28.08.2017 г. 15:02 TestWindow.Dotnet
28.08.2017 г. 15:07 uant3xwi.dix
28.08.2017 г. 14:56 uhuqfcub.t3o
28.08.2017 г. 15:12 VSSDK
28.08.2017 г. 15:10 WorkflowDesigner
28.08.2017 г. 15:02 wx2hgjbe.s2d
28.08.2017 г. 15:11 Xamarin.Android.Sdk
28.08.2017 г. 15:11 Xamarin.Apple.Sdk
28.08.2017 г. 15:10 Xamarin.Forms
28.08.2017 г. 15:12 Xamarin.VisualStudio
28.08.2017 г. 15:06 xi44pjrj.t1t
28.08.2017 г. 15:02 y3kvx1nx.h3x

@jcansdale
Copy link
Collaborator

jcansdale commented Sep 4, 2017

To avoid cluttering this issue, I've moved this comment to #1217 (re: out of sync bindingRedirects).

@vaindil
Copy link

vaindil commented Sep 5, 2017

@tinaschrepfer Current version is also 2.3.1.30. The result of tree on Common7\IDE\Extensions is here.

@tinaschrepfer
Copy link

Regarding the original issue of not being able to upgrade to 2.3.32. We took a look at the logs you provided (thank you!) and from our analysis it looks like the following happened:

  • GitHub was upgraded from version 2.3.0.24 to 2.3.1.30, which was successful.
  • An attempt was then made to upgrade GitHub to 2.3.2.32, which was unsuccessful.

From the logs it looks like somewhere between 2.3.1.30 and the attempt to upgrade to 2.3.2.32, the setup engine somehow became unaware that 2.3.1.30 was installed. When the attempt to upgrade to 2.3.2.32 was made the engine still thinks that 2.3.0.24 is installed, so it tries to remove that instead of 2.3.1.30, but 2.3.0.24 is already gone. The engine did successfully install 2.3.2.32, but VSIXInstaller sees that 2.3.1.30 is still present, so it requests that 2.3.1.30 be uninstalled by calling the engine to uninstall it. However, because the engine has no idea 2.3.1.30 was ever installed, it doesn't know what to do and the exception you see is thrown.

Unfortunately, we don't have enough logging information to explain why the engine just forgot that 2.3.1.30 was installed. Did you run a system restore at some point or anything? We have an item on the backlog to provide more snapshot logging information so we can trace this better.

For now, to get around this, you can manually delete 2.3.1.30 by deleting everything under Common7\IDE\Extensions\pyrgfpsc.ea0 (perhaps copy the files somewhere else first as a backup), and then run devenv /updateconfiguration. That should load 2.3.2.32 properly.

Thanks!

Tina

@BladeMF
Copy link
Author

BladeMF commented Sep 5, 2017

Hi @tinaschrepfer

What happened was an upgrade to VS to 15.3.3 (even two upgrade). Maybe the mess happened then or earlier. Will try the delete trick and let you know.

@BladeMF
Copy link
Author

BladeMF commented Sep 5, 2017

I can confirm that after deleting the files and running /updateconfiguration, VS showed that I have 2.3.2.32 installed.

@vaindil
Copy link

vaindil commented Sep 5, 2017

@tinaschrepfer I also upgraded VS in between there, no system restore or anything else like that. Deleting the files and running devenv /updateconfiguration did indeed fix the problem. Thank you!

@vishnu4
Copy link

vishnu4 commented Sep 5, 2017

Works for me as well. thank you.

@tinaschrepfer
Copy link

Thanks for the confirmations. We are working on a fix internally to prevent this issue from occurring in the future. For now, please make sure that VS Installer is shut down before running VSIXInstaller. That should prevent this issue from occurring.

Thanks!

Tina

@shana
Copy link
Contributor

shana commented Sep 8, 2017

Awesome, thank you for all the help @tinaschrepfer!

@brwilkinson
Copy link

brwilkinson commented Sep 9, 2017

I currently have this issue, since the past 4 days on VS Enterprise 2017.

running GitHub.VisualStudio.vsix

9/8/2017 9:07:04 PM - Install Error : System.InvalidOperationException: A value for 'Component' needs to be specified in the catalog.

at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.PerformSetupEngineUnInstall(IInstalledExtension extension, Boolean downgrade)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.UninstallInternal(IInstalledExtension extension, Boolean forceDelete, Version targetedVSVersion, Boolean downgrade)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.CommitInstalledAndUninstalledExtensions(IEnumerable1 installedExtensions, IEnumerable1 uninstalledExtensions, IEnumerable`1 packComponentChanges, Version targetedVSVersion)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.BeginInstall(IInstallableExtension installableExtension, InstallFlags installFlags, AsyncOperation asyncOp, Version targetedVsVersion)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.InstallWorker(IInstallableExtension extension, InstallFlags installFlags, AsyncOperation asyncOp)

I removed the directory: extensions/pyrgfpsc.ea0 then ran: devenv /updateconfiguration

Then tried to install it again . . it said it was already installed. . .

I ran the command again: devenv /updateconfiguration

Opened up VS and things seem to be fine. . . I see the extension. . so not sure what the pyrgfpsc.ea0 was (I guess a new version of the extension), although I confirmed the directory was gone. There and no updates are showing in VS.

Extension version 2.3.2.32 shows as installed on 9/6/2017 (I guess this is a previous version.)

@jcansdale
Copy link
Collaborator

@brwilkinson, Thanks for the detailed information. Please let us know if you have any have any further issues updating the extension.

@BladeMF
Copy link
Author

BladeMF commented Sep 13, 2017

@shana shana added the bug label Oct 24, 2017
@grokys
Copy link
Contributor

grokys commented Dec 5, 2017

@BladeMF there have been numerous updates to the installer with 15.5 which was released yesterday, do they solve your problem? A user has also managed to fix the same problem here #1295 (comment) if the problem is still there.

@grokys
Copy link
Contributor

grokys commented Dec 12, 2017

Closing this as there's been no reply for 7 days. If you're still having the problem, please let us know and we'll reopen!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants