Question 86928 in ASP.NET Question posted in
The official documentation can be found here.

Visual Studio 2022 error: Exception from HRESULT: 0x800300FA (STG_E_ABNORMALAPIEXIT) – Asp.net

I have an ASP.Net Web forms project in Visual Studio 2022. When I try to build it, an error message appears.

An API call exited abnormally. (Exception from HRESULT: 0x800300FA (STG_E_ABNORMALAPIEXIT))

This error also appears when I try to exit Visual Studio. I have to kill the process to proceed.

The same project works fine in Visual Studio 2019.

Any idea where to start? The error message is not very insightful.

I already tried setting the rights on the framework Temporary ASP.NET Files folder. I didn’t help.

The issue is also only with one project – other projects work fine.

Is there a way I can get a Visual Studio log. Any ideal where this is stored for Visual Studio 2022?

Tags:

4

Answers


  1. 0

    Vs22 is now x64 bits, and is the first such version to be so.
    This also means we see a lot more issues and errors in regards to running your application as any CPU as opposed to forcing the project bit size.
    It’s not clear if you always forced the bit size, or perhaps your project say references unmanaged code that’s say x32 bits.

    So I would force and change the project to run as x32 bits if that was the settings in the past.
    And in fact any CPU used to result in your application (f5) to run as x32 bits, now that default any CPU setting will result in a x64 but running and debug session.

    You don’t mention your current project settings, but I would try x32 bits, especially if you used any CPU in the past.

    Login or Signup to reply.
  2. 0

    I had a same issue after recent Visual Studio 2022 update. Was not able to build, run, publish solution at all. To resolve it I just pushed all my changes into repo and cloned it to new folder.

    Have no idea what was a root cause, but it helped…

    Login or Signup to reply.
  3. 0

    Try deleting the .vs folder at the root of your project that fixed it for me

    Login or Signup to reply.
  4. 0

    I was able to get rid of the issue through a combination of the following:

    • Closed Visual Studio
    • Removed **/bin/** **/obj/**
    • Updated Visual Studio to the latest version
    • Removed the component cache: %USERPROFILE%AppDataLocalMicrosoftVisualStudio1x.0ComponentModelCache
    • Removed all temporary files in %USERPROFILE%AppDataLocalTemp

    Those locations are also mentioned on the internets, but I didn’t touch them:

    %USERPROFILE%AppDataLocalMicrosoftTeam Foundation
    %USERPROFILE%AppDataLocalMicrosoftVisualStudio
    %USERPROFILE%AppDataLocalMicrosoftVSCommon

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search