Reporting Intelligence Error: "No handle of the given name exists" When Running in Background

Issue

A user receives the following error when attempting to run a Reporting Intelligence Report in the background by right-clicking the Excel file and selecting Run Reporting Intelligence Report:

An unexpected error has occurred:

No handle of the given name exists.

System.Threading.WaitHandleCannotBeOpenedException

at System.Threading.EventWaitHandle.OpenExisting(String name, EventWaitHandleRights rights)

at Jet.TrayApplication.Program.Run(String[] args)

Root Cause

This error typically occurs due to how Reporting Intelligence interacts with the file system and Windows background processes. It may be triggered by:

• File location (non-local directories)

• Windows File Explorer Preview Pane

• Reporting Intelligence background process limitations

Resolution Steps

1. Check file location

   Determine where the Excel file is stored:

   1. Local directory (For example, C:\Reports) – Recommended

   2. OneDrive, shared network drive, or mapped network drive – May cause issues

   Solution: Copy the Excel file to a local directory on the C:\ drive and try running the report again.

2. Try running via Reporting Intelligence ribbon

   Instead of using the right-click context menu:

   1. Open the Excel file.

   2. Go to the Reporting Intelligence ribbon in Excel.

   3. Select Run in Background.

   Check if the same error occurs. If it works here, the issue is likely tied to the context menu method.

3. Disable Windows File Explorer Preview pane

   If the Preview pane is enabled, it can interfere with the Reporting Intelligence background execution.

   

   To disable Windows File Explorer Preview pane, do the following:

   1. Open File Explorer.

   2. Go to the View tab.

   3. Clear Preview Pane.

   4. Then retry the Run Reporting Intelligence Report option.

Additional Notes

Ensure Reporting Intelligence is fully updated.

Confirm the user has appropriate permissions to run background tasks.

If the issue persists, consider reinstalling Reporting Intelligence or contacting Reporting Intelligence support.