# Delete Package Failed to Be Processed (Conscom Not Processed)

> Fix a Conscom not processed replicator event reported when a package deletion fails.

Source: https://docs.capaone.com/capainstaller/troubleshooting/delete-package-failed-to-be-processed-conscom-not-processed/  
Product: CapaInstaller — a separate CapaSystems product; do not apply this page to any other.

## Problem

In System Administration, the System Notification History shows a **Conscom not processed** event with type **Replicator**, and a description similar to:

```
Delete Package '', failed to be processed. Attempts: 'N'.
```

The attempt count keeps climbing on every retry, and the **Subsequent issues** list fills up with the same error for the same server, package, and event.

## Solution - Close programs that hold a package file open

The Replicator can't delete a package's folder while another program on the server still has one of its files open. A text editor, an archive tool, or even a File Explorer preview pane left open on a file inside the package is enough to block the delete, so every retry fails with the same "failed to be processed" error.

1. On the server that's running the Replicator job (in the notification's **Server** field, for example `CAPA3SRV`), close any editor, archive tool, or other application that has a file from the package open.
2. Close any File Explorer window browsing the package's folder — a preview pane can hold a lock even if no file is explicitly open.
3. Wait for the Replicator's next scheduled attempt, or trigger it manually, and check System Notification History again. The delete completes once nothing on the server has a lock on the package's files.

:::tip
If you can't tell which program is holding a file, use a locking tool such as Sysinternals **Process Explorer** or **handle.exe** to search for the package's file path and identify the process to close.
:::