How to fix an Epicor Kinetic report stuck in ACTIVE (or finished with no PDF)

How the pieces fit

A report workflow can involve task submission, Task Agent processing, report data generation, SSRS rendering, file delivery, and finally the browser or local agent opening or printing the output. The exact workflow varies by report type, client, and deployment. Use the task status and logs to identify which stage failed rather than assuming every report uses the same path.

Step-by-step: Diagnose the stuck report

Work through the chain in sequence. In production, coordinate service restarts with your Epicor administrator and avoid disrupting users who are posting transactions.

1. Check System Monitor and the Task Details

• Open System Monitor and inspect the Active Tasks and History views.
• Record the task identifier (for example, TaskID or SysTaskNum if displayed), submitter, start time, report name, and parameters.
• If the task appears in History with an error, open its details and capture the complete message.
• Look for specific errors such as a timeout, invalid column, missing report data source, or file-access denial.
• Compare the task with other recent tasks. A single failing report points toward its query, report style, parameters, or output path; many tasks failing together may indicate a broader service or connectivity issue.
• A timeout message is evidence of a timeout, not proof of a Task Agent failure. Check the query, database blocking, SSRS logs, and relevant server logs before deciding which component to restart. If the error is a timeout, see our guide on fixing Epicor Kinetic BAQ and report timeouts.

2. Determine Whether the Issue Affects One Report or the Whole Environment

If permitted, submit a small, known-good report using a narrow parameter range and an immediate schedule.

• The test report completes: The Task Agent may be processing tasks normally. Focus on the original report's parameters, BAQ/RDD, SSRS dataset, subreports, and output settings.
• The test report also remains ACTIVE: Check whether tasks are accumulating, whether the Task Agent is connected and processing, and whether the AppServer, database, or SSRS is healthy.
• Only one user or workstation cannot preview or print: Check the browser session, permissions, pop-up settings, local Edge Agent, and printer configuration.
• Use a report that is safe to run and does not trigger posting or other business transactions.

3. Cancel the Task Through the Supported UI First

If a task is clearly stuck and your administrator has confirmed it is safe to stop:

1. In System Monitor, select the task.
2. Use Actions > Cancel Task if that action is available.
3. Refresh System Monitor and check whether the task changes state.
4. Confirm that no associated posting or other business transaction is still running before taking further action. If the cancelled task was an invoice posting or financial process, check the status of the related group or review journal before attempting to re-run it.

Do not start by editing or deleting rows in Ice.SysTask. The task can have related parameter, log, or other records, and a manual status change can make the database state inconsistent with the actual worker process. If cancellation fails, use the recovery procedure approved for your Epicor version or contact Epicor Support. On-premises administrators should not run ad hoc UPDATE or DELETE statements against task tables without an approved, task-specific recovery plan and a backup/rollback strategy. Cloud customers should use the supported UI or EpicCare Support.

For diagnosis, an authorized administrator may inspect task metadata using approved read-only tools. Do not expose sensitive task parameters or logs in public support posts.

4. Check the Task Agent Service (On-Premises)

If multiple tasks remain queued or the Task Agent appears not to be processing:

1. Open Windows Services (services.msc) on the server where the relevant agent is installed.
2. Identify the correct Epicor Task Agent service for that environment.
3. Check its status, startup configuration, recent service events, and the configured AppServer connection.
4. If a restart is approved, coordinate it with users and follow your organization's service-restart procedure.
5. After the restart, submit a small test report and verify that the queue begins processing.

A service showing "Running" does not by itself prove that it is connected to the correct AppServer or successfully polling tasks. Review agent logs and configuration. If the issue began after a server reboot, check service dependencies and startup ordering. Automatic (Delayed Start) may be appropriate in some on-premises configurations, but confirm this against the installed version and Epicor guidance rather than applying it universally.

For Kinetic Cloud, customers generally cannot restart the tenant's server-side Task Agent themselves. If tasks are stuck across multiple users and the supported UI cannot recover them, open an EpicCare ticket with task identifiers, timestamps, error details, and the scope of impact.

5. If the Task is COMPLETE but No PDF Appears, Check Output Configuration

A completed task does not always mean the client successfully opened or printed the output. Check:

• Report output and delivery settings: Confirm the report's selected output mode and destination.
• System Agent configuration: Verify the server and client file directories configured in System Agent Maintenance, where your deployment uses them.
• Network share permissions: For on-premises file shares, confirm that the actual service identity has the required permissions. A user being able to open a folder interactively does not prove that a Windows service can access it.
• UNC paths: For on-premises deployments where services access a network share, a UNC path such as \\ServerName\EpicorData\Reports is required. The Windows Task Agent service runs in non-interactive Session 0 and cannot access drive letters (such as Z:\) that exist only within an individual user's interactive logon session.
• SSRS endpoint and credentials: Where the report uses SSRS, confirm the Report Server URLs configured for the app server in the Epicor Administration Console, and test connectivity from the relevant server using an authorized account.
• SSRS logs: Look for rendering failures, data-source errors, permission problems, and execution timeouts.

Do not assume that every Kinetic report writes a PDF to a shared directory. Output handling differs by report type and client workflow; use the report's actual configuration and logs to establish where the file should be delivered.

6. Check the Local Edge Agent and Browser Behavior

For browser-based workflows that use the Epicor Edge Agent for local printing or other client-side actions:

1. Check whether the Edge Agent is installed and running on the workstation.
2. Confirm that the agent is listening on its local port (6071). If the agent reports "Required port already in use," another process on the workstation is holding that port.
3. If the diagnostic page (https://localhost:6071/#/home) does not load, check the local agent status, installation, endpoint-security rules, and whether another process is using the port.
4. Check the browser's site permissions and pop-up settings for your Kinetic URL. Allow only the permissions required by your organization's policy.
5. If appropriate, restart the local Edge Agent using the supported workstation procedure, then sign in again and test with a small report.

If the agent is not running, or cannot bind to its local port, Kinetic cannot hand print and file actions to the workstation. Do not assume every missing PDF is an Edge Agent problem: first confirm whether the report actually rendered and where its output was sent.

The trap: Rebooting or recycling everything

Restarting the AppServer, recycling an IIS application pool, or rebooting a server can interrupt unrelated users and may not stop a database query that is already executing. If the original cause is a slow BAQ/RDD, a blocking query, a broken report data source, or a local browser-agent issue, a broad restart may only hide the symptom temporarily.

Be especially careful when a report is associated with a posting routine or another business transaction. Before stopping services or changing task status, establish whether the task is a read-only report or part of a workflow that can affect transaction state. If uncertain, pause and involve your Epicor administrator or EpicCare Support.

Symptom → likely cause → Next check

Common Edge cases

• Edge Agent local port or loopback issue: The Edge Agent listens locally on port 6071. If Kinetic cannot communicate with the local agent, check whether the agent is running, whether another process holds the port, and whether endpoint security is blocking the loopback connection.
• Task Agent starts before the AppServer is ready: On some on-premises deployments, service startup order can affect the agent's initial connection after a reboot. Check logs and service dependencies before changing startup type. Delayed start can help in some configurations, but it is not a universal fix.
• Credentials or service identity changed: If the problem began after a password, certificate, or authentication change, verify the agent's configured credentials and permissions using the supported administration tools. Do not paste secrets into logs or support tickets.
• Tasks remain ACTIVE after cloud maintenance: If tasks appear orphaned after a cloud maintenance window, record the task identifiers and timestamps, try the supported cancellation action, and contact EpicCare if the task cannot be cleared. Cloud users should not attempt direct database updates.

FAQ

Why does my report stay in ACTIVE for hours?

Usually because its query is still running or is blocked in SQL Server, or because the Task Agent has stopped processing tasks. If other reports complete normally, look at that report's query and parameters. If every report is queuing, look at the Task Agent and the AppServer.

Can I delete tasks directly from Ice.SysTask in SQL?

No. Cancel the task in System Monitor. A SQL DELETE or status update leaves related task records behind and does not stop a worker that is still running. If the UI cannot cancel the task, use an Epicor-approved recovery procedure or open an EpicCare case.

What is the default Edge Agent port?

The Edge Agent listens locally on port 6071. If another process already holds that port, the agent reports "Required port already in use" and cannot start until the conflict is cleared.

Where are Epicor SSRS reports stored?

Report definitions (RDL files) live on the SSRS report server. Rendered output is delivered through the report's configured workflow, so check the report style and System Agent settings rather than looking for one fixed PDF folder.

References

Service names, menu locations and ports vary between Epicor releases. Confirm them against the documentation for your installed version, and prefer the supported UI and EpicCare guidance for any recovery step that changes task state or restarts services:

• Epicor Kinetic Help: System Monitor & Task Processing Overview
• Epicor Kinetic Help: System Agent Maintenance – Server and Client Directories
• Epicor Kinetic Help: Epicor Edge Agent Installation and Configuration
• Microsoft Documentation: Windows Services and Non-Interactive Session 0 Execution
• EpiUsers Community: Edge Agent Install – "Required Port in Use" Error (Port 6071)
• EpiUsers Community: Managing and Clearing Orphaned Tasks in Ice.SysTask