none
[UWP]Activation of app failed with error: The remote procedure call failed. RRS feed

  • Question

  • After upgrading to 15063, background tasks stops working. Event Viewer shows constant error like below:

    Activation of app net.neolib.BingDailyWallpaper_xctxhvdp4nrje!App failed with error: Unknown HResult Error code: 0x80131509 See the Microsoft-Windows-TWinUI/Operational log for additional information.
    
    Failed with 0x490 modifying AppModel Runtime status for package net.neolib.BgTaskTest_1.0.0.0_x64__xctxhvdp4nrje for user VM-W10\Edward (current status = 0x0, desired status = 0x20).
    
    Failed with 0x490 modifying AppModel Runtime status for package app.a435b0827.a67ad.a433a.aba66.aec2c4b63531c_1.0.0.0_x86_NorthAmerica_8wekyb3d8bbwe for user VM-W10\Edward (current status = 0x0, desired status = 0x20).
    
    Activation of app BgTastTest_xctxhvdp4nrje!App failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

    And there is a faulting error:

    Faulting application name: backgroundTaskHost.exe, version: 10.0.15063.0, time stamp: 0x0fa14906
    Faulting module name: twinapi.appcore.dll, version: 10.0.15063.332, time stamp: 0xf873d086
    Exception code: 0xc000027b
    Fault offset: 0x0000000000095a76
    Faulting process id: 0xf84
    Faulting application start time: 0x01d30ee93f387b8e
    Faulting application path: C:\WINDOWS\system32\backgroundTaskHost.exe
    Faulting module path: C:\Windows\System32\twinapi.appcore.dll
    Report Id: 9450df19-f205-4900-94f7-d4ce77bccb74
    Faulting package full name: BgTastTest_1.0.0.0_x64__xctxhvdp4nrje
    Faulting package-relative application ID: App
    App Container profile failed with error 0x800700B7 because it was unable to register the AppContainer SID.

    This is very confusing. The apps and background tasks had been working fine. Any suggestions?


    Ignorance is blissful


    • Edited by Neo the 1 Monday, August 7, 2017 7:07 AM
    • Changed type Neo the 1 Tuesday, August 8, 2017 6:39 AM
    • Changed type Neo the 1 Thursday, August 24, 2017 6:50 PM
    Monday, August 7, 2017 6:45 AM

Answers

  • After being pestered by this problem for over one month, I finally nailed down the bug with strong evidence. I hope this will help others having similar issues.

    My problem was caused  by Application Target setting. I reverted back to the original 14393 (Anniversary Edition) and my app works normally as before. The background tasks are getting triggered and scheduled correctly.

    One small interesting finding is that when I change Target Version, the list has different text labels for a same build. This can only be explain clearly by pictures:

    Anniversary Edition:

    Creators Update:


    Ignorance is blissful


    • Edited by Neo the 1 Wednesday, August 23, 2017 12:01 PM
    • Marked as answer by Neo the 1 Thursday, August 24, 2017 6:50 PM
    Wednesday, August 23, 2017 12:00 PM

All replies

  • Hi,

    Welcome to MSDN forum.

    >>After upgrading to 15063, background tasks stops working.

    The error message is more related to OS, I recommend you ask questions in windows forum.

    Best regards,

    Joyce


    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, August 8, 2017 6:19 AM
  • I think I find a very suspicious cause of the problem. One of my UWP app uses large image assets many of which exceed the (ridiculously small) limit (200k). I rebuilt the app with only small and wide tiles without file size warnings. Now it seems the two apps espcially the tasks are working and scheduled correctly.

    EDIT: It seems I was wrong. The problem struck again and my background task stops working again.

    I searched on the internet and there are tons of questions regarding this error. Even the builtin apps like Microsoft Weather and Maps suffer from this error.

    • Edited by Neo the 1 Sunday, August 13, 2017 8:22 AM
    Wednesday, August 9, 2017 3:47 PM
  • After being pestered by this problem for over one month, I finally nailed down the bug with strong evidence. I hope this will help others having similar issues.

    My problem was caused  by Application Target setting. I reverted back to the original 14393 (Anniversary Edition) and my app works normally as before. The background tasks are getting triggered and scheduled correctly.

    One small interesting finding is that when I change Target Version, the list has different text labels for a same build. This can only be explain clearly by pictures:

    Anniversary Edition:

    Creators Update:


    Ignorance is blissful


    • Edited by Neo the 1 Wednesday, August 23, 2017 12:01 PM
    • Marked as answer by Neo the 1 Thursday, August 24, 2017 6:50 PM
    Wednesday, August 23, 2017 12:00 PM
  • Hi,

    Thank you for sharing the workaround here, could you please mark your reply as an answer which will be helpful for those who has the similar issue with you?

    Best regards,

    Joyce 


    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, August 24, 2017 8:55 AM