Error HRESULT E_FAIL has been returned from a call to a COM component. vs 2022

CARLOS LUIS RICHARDSON MENDEZ 0

I'm trying to create a service application with WCF, when I get this error. User's image

I have tried multiple solutions that I saw online, such as adding this assembly gacutil -i Microsoft.VisualStudio.Shell.Interop.11.0.dll in the global assembly cache. I have reinstalled visual studio twice from 0. I have cleared the visual studio cache. I do not know what to do... I have attached the log file below. test04.xml

QiYou-MSFT 4,321 Reputation points Microsoft Vendor

2024-02-05T06:38:16.3433333+00:00

Hi @CARLOS LUIS RICHARDSON MENDEZ

Is this just the issue coming up with this project template? Also, I would like to ask which project template you used to create WCF services. Best Regards

Qi You
CARLOS LUIS RICHARDSON MENDEZ 0 Reputation points

2024-02-05T19:37:23.6+00:00

Hello @QiYou-MSFT I am using the default template offered by visual studio, below I will leave a series of images that show my steps when creating the project... 1

2- Here i Select WCF Service App.

3- This is where the error occurs, when creating the project.

This error occurs with the templates of that project, but knowing the nature of various projects in .net, the error may be present in other types of templates which may have some component or dependency on which they are used in this template and which fail giving the error in question
CARLOS LUIS RICHARDSON MENDEZ 0 Reputation points

2024-02-05T19:40:40.74+00:00

I also installed a .net run time that I saw in another post but it didn't work either. https://github.com/dotnet/core/blob/main/release-notes/download-archives/1.0.4-download.md

1 answer

QiYou-MSFT 4,321 Reputation points Microsoft Vendor

2024-02-08T07:42:58.97+00:00

Hi @CARLOS LUIS RICHARDSON MENDEZ

I searched a lot. Usually people who run into this problem are opening up other projects. If you're having trouble creating a project, it's possible that some of your files are corrupted or unregistered.

Try this solution:

Start —> Run —> regsvr32 %SystemRoot%\System32\msxml3.dll

Start —> Run —> regsvr32 %SystemRoot%\SysWOW64\msxml3.dll

Best Regards

Qi You

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
CARLOS LUIS RICHARDSON MENDEZ 0 Reputation points

2024-02-09T17:47:59.1066667+00:00

@QiYou-MSFT I really appreciate your effort, I have not stopped trying on my part either, I tried the proposed solution and there was no success... I also performed an SFC /scannow to verify the integrity of the operating system files but it says that they are at 100%. It should be noted that the number of errors in the log file has been greatly reduced, leaving us with the main culprit of everything

QiYou-MSFT 4,321 Reputation points Microsoft Vendor

2024-02-12T03:10:27.2266667+00:00

Hi @CARLOS LUIS RICHARDSON MENDEZ

I've done a lot of research, and I think the following methods might work:

1.Reset Visual Studio settings: Run devenv /ResetSettings in the developer command prompt in Visual Studio 2022.

2.Delete the Visual Studio cache: Navigate to C:\\Users\\<username>\\AppData\\Local\\Microsoft\\VisualStudio\\17.0_xxxxxxxx\\ComponentModelCache and delete all the "ComponentModelCache" folders.

Re-register Microsoft.VisualStudio.Shell.Interop.11.0.dll

Best Regard

Qi You

CARLOS LUIS RICHARDSON MENDEZ 0 Reputation points

2024-02-13T05:49:23.28+00:00

Hello @QiYou-MSFT , I have done everything indicated and we keep getting the same error. I greatly appreciate the efforts you put into helping me. I am here to share my latest discovery about this annoying problem. I decided to open the visual studio 2022 developer console as administrator and try visual studio safe mode using the devenv /safemode command. I ran the same steps and this time we got a different error, which could indicate being the trigger for the original error. The idea came to me when analyzing a certain line in a log file that I created while testing the solution that was provided to me.

I will continue investigating to find out what this new discovery concludes.

CARLOS LUIS RICHARDSON MENDEZ 0 Reputation points

2024-02-13T16:26:55.68+00:00

@QiYou-MSFT here is the log file safemodetest.xml

QiYou-MSFT 4,321 Reputation points Microsoft Vendor

2024-02-19T05:37:25.2566667+00:00

Hi @CARLOS LUIS RICHARDSON MENDEZ

I see that your file directory contains a BlazorApp1.sln. Did you create this on your current device? The scope of the problem needs to be identified at this time. You create a project with another folder and give it a try. Best Regards

Qi You
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Error HRESULT E_FAIL has been returned from a call to a COM component. vs 2022

1 answer

Your answer