Remote Procedure Call Failed (HRESULT: 0x800706BE)

Question

Remote Procedure Call Failed (HRESULT: 0x800706BE)

Xie Steven 831

The application uses diagnostic APIs to prevent it from starting repeatedly. However, it crashes on startup, and the following exception information is logged:

Remote procedure call failed.  (Exception from HRESULT: 0x800706BE)
   at System.Runtime.InteropServices.McgMarshal.ThrowOnExternalCallFailed(Int32, RuntimeTypeHandle) + 0x21
   at __Interop.ComCallHelpers.Call(__ComObject, RuntimeTypeHandle, Int32, Void*) + 0xbe
   at __Interop.ForwardComStubs.Stub_16[TThis](__ComObject, Int32) + 0x2e
   at Windows.System.Diagnostics.ProcessDiagnosticInfo.get_IsPackaged() + 0x18
   at cherApp.App.DetectDuplicateApp() + 0xdf
   at cherApp.App.<OnLaunched>d__19.MoveNext() + 0x2ce
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__7_0(Object) + 0x1e
   at System.Action`1.Invoke(T) + 0x28
   at System.Threading.WinRTSynchronizationContext.Invoker.InvokeCore() + 0x33
Cannot use RPC server.
   at System.Runtime.InteropServices.McgMarshal.ThrowOnExternalCallFailed(Int32, RuntimeTypeHandle) + 0x21
   at __Interop.ComCallHelpers.Call(__ComObject, RuntimeTypeHandle, Int32, Void*) + 0xbe
   at __Interop.ForwardComStubs.Stub_3[TThis, TResult](__ComObject, Int32) + 0x37
   at cherApp.App.DetectDuplicateApp() + 0x7d
   at cherApp.App.<OnLaunched>d__19.MoveNext() + 0x2ce
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__7_0(Object) + 0x1e
   at System.Action`1.Invoke(T) + 0x28
   at System.Threading.WinRTSynchronizationContext.Invoker.InvokeCore() + 0x33

What issues could cause this problem?

The code sample:

private bool DetectDuplicateApp()
{
    List<string> processNameCollection = new List<string>();
    IReadOnlyList<ProcessDiagnosticInfo> processes = new ProcessDiagnosticInfo.GetForProcesses();
    foreach(ProcessDiagnosticInfo process in processed)
    {
        if(process.IsPackaged)
       {
           processNameCollection .Add(process.ExecutableFileName);
       }
    }
    var count = processNameCollection .Where(item => item == "cherApp.exe");
    if(count > 1)
    {
          return false;   
    }
    return true;
}

Junjie Zhu - MSFT 21,651

Hello @Xie Steven ,

Welcome to Microsoft Q&A!

Your code needs to be modified. This is my test code, and there is no error. You can try this.

  private bool DetectDuplicateApp()
  {       
      List<string> processNameCollection = new List<string>();
      List<ProcessDiagnosticInfo> processes = ProcessDiagnosticInfo.GetForProcesses().ToList();
      foreach (ProcessDiagnosticInfo process in processes)
      {
          if (process.IsPackaged)
          {
              processNameCollection.Add(process.ExecutableFileName);
          }
      }
      var count = processNameCollection.Where(item => item == "cherApp.exe");
    
      if (count.Count() > 1)
      {
          return false;
      }
      return true;
  }

Thank you.

Xie Steven 831 Reputation points

2024-11-21T01:24:28.35+00:00

@Junjie Zhu - MSFT This problem doesn't occur every time. I want to know what issues could cause this problem?
Junjie Zhu - MSFT 21,651 Reputation points

2024-11-21T01:50:58.1333333+00:00

Hello @Xie Steven ,

The document says that a possible cause is that some catalog files, manifest files, or MUM files on the computer are corrupted. You can try the solution in the documentation.

Thank you.

1 answer

Your answer

Junjie Zhu - MSFT 21,651 Reputation points

2024-11-20T08:44:36.32+00:00

Hello @Xie Steven ,

Welcome to Microsoft Q&A!

Your code needs to be modified. This is my test code, and there is no error. You can try this.

private bool DetectDuplicateApp() { List<string> processNameCollection = new List<string>(); List<ProcessDiagnosticInfo> processes = ProcessDiagnosticInfo.GetForProcesses().ToList(); foreach (ProcessDiagnosticInfo process in processes) { if (process.IsPackaged) { processNameCollection.Add(process.ExecutableFileName); } } var count = processNameCollection.Where(item => item == "cherApp.exe"); if (count.Count() > 1) { return false; } return true; }

Thank you.
Xie Steven 831 Reputation points

2024-11-21T01:24:28.35+00:00

@Junjie Zhu - MSFT This problem doesn't occur every time. I want to know what issues could cause this problem?
Junjie Zhu - MSFT 21,651 Reputation points

2024-11-21T01:50:58.1333333+00:00

Hello @Xie Steven ,

The document says that a possible cause is that some catalog files, manifest files, or MUM files on the computer are corrupted. You can try the solution in the documentation.

Thank you.

Answer 1

Hi @Xie Steven ,

The error HRESULT: 0x800706BE indicates that the RPC communication has failed, meaning the call between your program and the RPC server could not be completed successfully.

What issues could cause this problem?

UWP apps run in a sandboxed environment with limited access to system-level resources. Some processes may restrict access to their diagnostic metadata due to security permissions, causing RPC failures when queried.
Frequently starting and stopping processes may not exist at the time of query, leading to RPC errors because the process is no longer valid.
Temporary unavailability or overload of the RPC server may lead to communication failures.
Using ProcessDiagnosticInfo.GetForProcesses() queries all processes, including those that are restricted or inaccessible, which can trigger errors.

This problem doesn't occur every time. I want to know what issues could cause this problem?

These might be the reasons:

The error only affects certain processes that are restricted, transient, or inaccessible. If these processes are not included in the diagnostic query, the error may not occur.
Transient processes may appear and disappear quickly. If a process terminates or is being created/destroyed during the query, it can trigger the error.
The diagnostic APIs may internally retry or handle edge cases differently, resulting in inconsistent or intermittent failures.

If you have any questions, feel free to ask! Thank you!

Harry Vo (WICLOUD CORPORATION) 405 Reputation points Microsoft External Staff

2025-07-22T03:43:03.24+00:00

Hi @Xie Steven , if you have any questions, feel free to ask! Thank you!
Harry Vo (WICLOUD CORPORATION) 405 Reputation points Microsoft External Staff

2025-07-31T06:25:01.0433333+00:00

Hi @Xie Steven , I'm willing to help if you still have any question! Thank you!

Share via

Remote Procedure Call Failed (HRESULT: 0x800706BE)

1 answer

Your answer