[wix-users] Extensive "MEF service broker" errors after installing WiX Toolset extension for VS 2022

Tue Jul 26 15:26:39 PDT 2022

Yeah, you're here now:

> Otherwise, you have to follow up with the Visual Studio team. They control the VSIX Installer.

The install worked for a couple hundred other people yesterday.

PS: Supporting VS Community does mean "VS Community and above".

From: William Rummler <wrummler at ara.com>
Sent: Tuesday, July 26, 2022 2:43 PM
To: Rob Mensching <rob at firegiant.com>; WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: Extensive "MEF service broker" errors after installing WiX Toolset extension for VS 2022

My IT folks had me install two certs, "NET Foundation Projects Code Signing CA.cer" and "WiX Toolset (.NET Foundation).cer", and the error still occurs.

In the log, the "Supported Products" section only lists VS Community (and amd64 product architecture), which made me think I need to try installing the extension into VS Community 2022 instead of Enterprise. Tried that, same error. This was a shot in the dark, since this metadata must not matter due to so many folks using the extension and not all of them using VS Community 2022.

For now, I'm out of ideas.

---

William Rummler (he/him)
Employee-owner, Senior Software Engineer

Applied Research Associates, Inc.
100 Trade Centre Dr., Suite 200
Champaign, IL 61820

T: 217.356.4500
F: 217.356.3088

www.ara.com<http://www.ara.com>
________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org<mailto:wix-users-bounces at lists.wixtoolset.org>> on behalf of William Rummler via wix-users <wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>>
Sent: Tuesday, July 26, 2022 12:21
To: Rob Mensching <rob at firegiant.com<mailto:rob at firegiant.com>>; WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>>
Cc: William Rummler <wrummler at ara.com<mailto:wrummler at ara.com>>
Subject: Re: [wix-users] Extensive "MEF service broker" errors after installing WiX Toolset extension for VS 2022

We're definitely connected to the internet, but it's inside a corporate network with managed IT policies on all machines, so could be some aggressive policies I guess.

I'm in touch with my IT now, and I think we can install the certs manually if we know which ones the WiX Toolset 2022 extensions are using. I'm trying to find out how to inspect the vsix for that info. If you know (or anyone on the list knows) how to do that, or just what certs are being used, that info would be appreciated.

Thanks again for your help!

---

William Rummler (he/him)
Employee-owner, Senior Software Engineer

Applied Research Associates, Inc.
100 Trade Centre Dr., Suite 200
Champaign, IL 61820

T: 217.356.4500
F: 217.356.3088

http://www.ara.com
________________________________
From: Rob Mensching <rob at firegiant.com<mailto:rob at firegiant.com>>
Sent: Tuesday, July 26, 2022 09:52
To: William Rummler <wrummler at ara.com<mailto:wrummler at ara.com>>; WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>>
Subject: RE: Extensive "MEF service broker" errors after installing WiX Toolset extension for VS 2022

I _think_ this is the issue:

7/25/2022 4:22:34 PM -                Extension is signed with an invalid certificate

7/25/2022 4:22:34 PM -                                (UntrustedRoot)     : A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.

7/25/2022 4:22:34 PM -                                (RevocationStatusUnknown): The revocation function was unable to check revocation for the certificate.

7/25/2022 4:22:34 PM -                                (OfflineRevocation) : The revocation function was unable to check revocation because the revocation server was offline.

That is known to happen with computers that are not connected to the internet and need their certificate store updated with the latest certs.

Otherwise, you have to follow up with the Visual Studio team. They control the VSIX Installer.

From: William Rummler <wrummler at ara.com<mailto:wrummler at ara.com>>
Sent: Monday, July 25, 2022 2:56 PM
To: Rob Mensching <rob at firegiant.com<mailto:rob at firegiant.com>>; WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>>
Subject: Re: Extensive "MEF service broker" errors after installing WiX Toolset extension for VS 2022

Thanks for the quick reply, Rob.

I uninstalled then reinstalled VS 2022, made sure it opened up without any errors, then tried to install with v1.0.0.20 of Votive2022.vsix from the project repo, but the extension installation terminated with an error. I've attached the log.

That error seemed to indicate installing the Schemas3.vsix might help, so I tried it. That installation also failed, strangely seeming to indicate no valid installation targets (e.g. VS 2022) were available. Log attached.

I then tried Schemas4.vsix to see if that did anything differently, and I got the same installation error. Log attached.

I then opened up VS 2022 to see if anything happened to it, and there were no errors. I double-checked the installed extensions list, and none of the three WiX Toolset extensions were listed.

Is there anything else I can try? Any other info I can provide that might help?

--William

---

William Rummler (he/him)
Employee-owner, Senior Software Engineer

Applied Research Associates, Inc.
100 Trade Centre Dr., Suite 200
Champaign, IL 61820

T: 217.356.4500
F: 217.356.3088

http://www.ara.com<http://www.ara.com>

________________________________

From: Rob Mensching <rob at firegiant.com<mailto:rob at firegiant.com<mailto:rob at firegiant.com%3cmailto:rob at firegiant.com>>>
Sent: Monday, July 25, 2022 12:35
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org%3cmailto:wix-users at lists.wixtoolset.org>>>
Cc: William Rummler <wrummler at ara.com<mailto:wrummler at ara.com<mailto:wrummler at ara.com%3cmailto:wrummler at ara.com>>>
Subject: RE: Extensive "MEF service broker" errors after installing WiX Toolset extension for VS 2022

Could you try Votive v1.0.0.20 from here: https://urldefense.com/v3/__https://github.com/wixtoolset/VisualStudioExtension/releases/tag/v1.0.0.20__;!!GxJN!ESPEf71ojvrp9aivhyJ7QEwGGMk6wMv3o0MnMLxeX65o-RJJXCGl-smSYD_XLWXOB4tMEH6u1w$<https://urldefense.com/v3/__https:/github.com/wixtoolset/VisualStudioExtension/releases/tag/v1.0.0.20__;!!GxJN!ESPEf71ojvrp9aivhyJ7QEwGGMk6wMv3o0MnMLxeX65o-RJJXCGl-smSYD_XLWXOB4tMEH6u1w$><https://urldefense.com/v3/__https:/github.com/wixtoolset/VisualStudioExtension/releases/tag/v1.0.0.20__;!!GxJN!ESPEf71ojvrp9aivhyJ7QEwGGMk6wMv3o0MnMLxeX65o-RJJXCGl-smSYD_XLWXOB4tMEH6u1w$%3chttps:/urldefense.com/v3/__https:/github.com/wixtoolset/VisualStudioExtension/releases/tag/v1.0.0.20__;!!GxJN!ESPEf71ojvrp9aivhyJ7QEwGGMk6wMv3o0MnMLxeX65o-RJJXCGl-smSYD_XLWXOB4tMEH6u1w$%3e>

There was a breaking change in VS2022 that they mitigated in recent VS2022 releases. This build _may_ work around that.

-----Original Message-----
From: wix-users <wix-users-bounces at lists.wixtoolset.org<mailto:wix-users-bounces at lists.wixtoolset.org<mailto:wix-users-bounces at lists.wixtoolset.org%3cmailto:wix-users-bounces at lists.wixtoolset.org>>> On Behalf Of William Rummler via wix-users
Sent: Monday, July 25, 2022 10:06 AM
To: wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org%3cmailto:wix-users at lists.wixtoolset.org>>
Cc: William Rummler <wrummler at ara.com<mailto:wrummler at ara.com<mailto:wrummler at ara.com%3cmailto:wrummler at ara.com>>>
Subject: [wix-users] Extensive "MEF service broker" errors after installing WiX Toolset extension for VS 2022

Hi all,

I installed the WiX Toolset build tools and the WiX Toolset extension in Visual Studio 2022 (via the Extensions UI in VS). The build tools seemed to install fine. After the installation of the extension, I started Visual Studio again and received several "MEF service broker package" errors on the VS splash screen. After clicking through those, I "continued without code" into the main VS UI and received dozens more of the same error before they stopped. At that point, the windows & panels in VS were unusable, only full of error stack traces instead of their normal content.

To try to eliminate the errors, I performed an installation repair (through the VS installer), which got VS working normally again (and removed the extension). I installed the extension again, and got the same behavior.

Then I tried a full uninstall and reinstall. Same thing, VS worked fine until I installed the extension, then the same errors.

Then I tried VS's "clean uninstall" tool followed by fresh installation of everything, including the VS installer. Same thing again.

(Machine restarts throughout each of these steps.)

I examined the log referenced by the error pop-up, and it included an "access denied" error on the path "C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\ENTERPRISE\COMMON7\IDE\EXTENSIONS\PHLCC4TT.1T0\extension.packcomponent".

(I also tried running VS as admin, and I encountered no errors at all during VS startup. Unfortunately, I can't run VS as admin day-to-day.)

I checked this access-denied path, and the final component of it doesn't exist. The parent folder does, and it has the following contents:

  *   "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\Extensions\phlcc4tt.1t0\catalog.json"
  *   "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\Extensions\phlcc4tt.1t0\CertificateInformation.dat"
  *   "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\Extensions\phlcc4tt.1t0\extension.vsixmanifest"
  *   "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\Extensions\phlcc4tt.1t0\manifest.json"
  *   "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\Extensions\phlcc4tt.1t0\WixLogo.png"

Has anyone else seen a problem like this? If so, any comment or help is appreciated. I can provide the log if that might clear anything up.

Also, my work colleague has experienced the same issue, and they resorted to using VS 2019 since the 2019 extension works fine for them there.

Thanks for reading,
William

---

William Rummler (he/him)
Employee-owner, Senior Software Engineer

Applied Research Associates, Inc.
100 Trade Centre Dr., Suite 200
Champaign, IL 61820

T: 217.356.4500
F: 217.356.3088

http://www.ara.com

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant https://urldefense.com/v3/__http://www.firegiant.com/__;!!GxJN!ESPEf71ojvrp9aivhyJ7QEwGGMk6wMv3o0MnMLxeX65o-RJJXCGl-smSYD_XLWXOB4tY539lrg$<https://urldefense.com/v3/__http:/www.firegiant.com/__;!!GxJN!ESPEf71ojvrp9aivhyJ7QEwGGMk6wMv3o0MnMLxeX65o-RJJXCGl-smSYD_XLWXOB4tY539lrg$><https://urldefense.com/v3/__http:/www.firegiant.com/__;!!GxJN!ESPEf71ojvrp9aivhyJ7QEwGGMk6wMv3o0MnMLxeX65o-RJJXCGl-smSYD_XLWXOB4tY539lrg$%3chttps:/urldefense.com/v3/__http:/www.firegiant.com/__;!!GxJN!ESPEf71ojvrp9aivhyJ7QEwGGMk6wMv3o0MnMLxeX65o-RJJXCGl-smSYD_XLWXOB4tY539lrg$%3e>

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant https://urldefense.com/v3/__http://www.firegiant.com/__;!!GxJN!G1g0LWcPeVihqEjc8aZNnDA3GlmoB0QTMZksCG8GjpI70QFafDSTdur_BQLnf0LQZ-Z-DAUg_mhXAlQSJK_oIzH9$<https://urldefense.com/v3/__http:/www.firegiant.com/__;!!GxJN!G1g0LWcPeVihqEjc8aZNnDA3GlmoB0QTMZksCG8GjpI70QFafDSTdur_BQLnf0LQZ-Z-DAUg_mhXAlQSJK_oIzH9$>