locked
wwahost.exe exits in release build with code -1073740767 (0xc0000421)

    Question

  • Thats the execption:

    Unhandled exception at 0x74891CDA (KernelBase.dll) in WWAHost.exe: 0x00000004: The system cannot open the file (parameters: 0x00000000, 0x80070005, 0x00000005).


    That is the stack trace:

    > KernelBase.dll!_DebugBreak@0() Unknown
    MrmCoreR.dll!Microsoft::Resources::ReportFatalException(unsigned long,unsigned long,unsigned long,enum Microsoft::Resources::MRT_ERROR_SCENARIO_TYPE) Unknown
    MrmCoreR.dll!Microsoft::Resources::HandleInternalFailure(unsigned long,unsigned long,enum Microsoft::Resources::MRT_ERROR_SCENARIO_TYPE) Unknown
    MrmCoreR.dll!6e8b0c98() Unknown
    combase.dll!CStaticMarshaler::QueryInterface(const _GUID & iid, void * * ppv) Line 212 C++
    MrmCoreR.dll!Microsoft::WRL::FtmBase::FtmBase() Unknown
    MrmCoreR.dll!6e8ef038() Unknown
    WWAHost.exe!MrtHostModule::InitializeResourceManagerCallback(struct _TP_CALLBACK_INSTANCE *,void *,struct _TP_WORK *) Unknown
    ntdll.dll!TppWorkpExecuteCallback() Unknown
    ntdll.dll!TppWorkerThread() Unknown
    kernel32.dll!@BaseThreadInitThunk@12() Unknown
    ntdll.dll!__RtlUserThreadStart() Unknown
    ntdll.dll!__RtlUserThreadStart@8() Unknown

    and then:

    First-chance exception at 0x6E8B0CA6 (MrmCoreR.dll) in WWAHost.exe: 0xC0000005: Access violation writing location 0x8D25E98E.

    > MrmCoreR.dll!6e8b0ca6() Unknown
      combase.dll!CStaticMarshaler::QueryInterface(const _GUID & iid, void * * ppv) Line 212 C++
      MrmCoreR.dll!Microsoft::WRL::FtmBase::FtmBase() Unknown
      MrmCoreR.dll!6e8ef038() Unknown
      WWAHost.exe!MrtHostModule::InitializeResourceManagerCallback(struct _TP_CALLBACK_INSTANCE *,void *,struct _TP_WORK *) Unknown
      ntdll.dll!TppWorkpExecuteCallback() Unknown
      ntdll.dll!TppWorkerThread() Unknown
      kernel32.dll!@BaseThreadInitThunk@12() Unknown
      ntdll.dll!__RtlUserThreadStart() Unknown
      ntdll.dll!__RtlUserThreadStart@8() Unknown

    The app runs fine in debug builds.

    Wednesday, December 10, 2014 3:20 AM

Answers

  • Thanks for your answer. I checked the other threads you mentioned but got it solved very easily by just uninstalling the app (that I deployed in Debug mode all the time before). That removed the local apps folder (including the AC folder where the PRI files are cached) and after deploying the app in release mode it worked.
    • Marked as answer by pkursawe Thursday, December 11, 2014 7:13 AM
    Thursday, December 11, 2014 7:13 AM

All replies

  • Hi Pkursawe,

    This error message is so broad, we should work together to narrow it down. Have you tried the system build-in metro style app, can they work? If not, I think it’s the problem about your operating system, you need to ask on consumer forum. I found similar questions may help.

    http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_store/cannot-connect-to-windows-8-store-wwahostexe/150de5e3-e8c3-4642-a009-82bddf6ae8e3.

    http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_store/most-windows-8-apps-crashing-the-remote-procedure/bd8e99df-ebe3-44bd-ae6d-c698b71f35a2.

    If the build-in app can work, then we can build a blank Javascript project to test in release mode to see if it can work. If it can that means there should be some code incorrect in your project. We can copy small code snippet to the blank project to find what’s wrong with the code.

    If the blank project cannot work either, that maybe something wrong with your development platform.

    Please try and let me know the result.

    Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate the survey.

    Thursday, December 11, 2014 5:41 AM
    Moderator
  • Thanks for your answer. I checked the other threads you mentioned but got it solved very easily by just uninstalling the app (that I deployed in Debug mode all the time before). That removed the local apps folder (including the AC folder where the PRI files are cached) and after deploying the app in release mode it worked.
    • Marked as answer by pkursawe Thursday, December 11, 2014 7:13 AM
    Thursday, December 11, 2014 7:13 AM