Error fixEpicor KineticReporting / SSRS / Task Agent

Epicor Kinetic Print Preview Not Working

Error
epicor kinetic print preview not working

Also searched as

  • epicor print preview not working
  • epicor report preview blank
  • epicor report stuck in task agent

Short answer

Epicor Kinetic reports are generated by the task agent and rendered through the report server, so a preview that never appears usually means the job did not complete, the SSRS connection failed, or the browser blocked the result. Check System Monitor first, then the report server settings, then the client.

Applies to: Epicor Kinetic reports using SSRS report styles; the task agent and report server configuration are managed by the administrator

How to fix print preview in order

  1. 1Run the report and open System Monitor to see whether the task was created, ran, errored or is still queued.
  2. 2If the task is stuck or never starts, check that the task agent service is running and the agent is configured for the company.
  3. 3If the task errors, read the task log text, which usually names the failing step or the report server connection.
  4. 4Confirm the SSRS report server is reachable from the application server and the credentials used for rendering are valid.
  5. 5Check the report style assigned to the report and that it has not been broken by a customization.
  6. 6In the browser, allow popups and downloads for the Kinetic site and retry in a private window.
  7. 7Check that the user can print the report and has a valid printer or output setting on the report dialog.
  8. 8Try another report to see whether the problem is global or limited to one style.

The path a report takes

A report request becomes a task, the task agent builds the data, the report server applies the style, and the result is returned to the client for preview or print. A failure at any link looks like a missing preview, so start where the evidence is: System Monitor shows the task state and any message.

If tasks never run, the problem is the task agent. If they run and fail, read the error. If they succeed but nothing shows, suspect the client or the browser.

Report server and styles

Rendering depends on the SSRS service being reachable, on valid credentials, and on the report style being deployed. After an upgrade or server move, the report server URL and permissions are the common regression.

If only one report fails, compare its style to a working one. A customized style that references a missing field or data set will fail even though the server is healthy.

Client and browser issues

If System Monitor shows success, look at the browser: blocked popups, an extension, or a download policy. A different browser or a private window tells you quickly.

Also check the user's output settings. A user without a default printer or with restricted printing can see odd behaviour that an administrator does not.

Try it here, free

Epicor SSRS Report Template Checklist

Open full tool

A pre-release checklist for custom Epicor SSRS reports covering report style, data definition, layout, parameters, security and testing.

Common pitfalls

  • !Retrying repeatedly instead of reading the task log.
  • !Assuming the report server is fine after a server move.
  • !Editing a style in production without testing it.
  • !Ignoring a stopped task agent service.
  • !Testing only as an administrator.

How an ERP-grounded AI assistant handles this

An assistant with read access to your system logs and task history can summarize which reports failed and why, and group failures by style or time. That is useful for pattern spotting. Fixes to the report server or styles remain administrator tasks.

Frequently asked questions

Why is my Epicor report stuck in the task agent?

The task agent service may be stopped, misconfigured for the company, or blocked by a previous failing task. Check System Monitor and the service status on the server.

Why does the preview work for some reports only?

A specific report style is probably broken, often after a customization or upgrade. Compare it to a working style.

Does print preview need SSRS?

Reports that use SSRS styles need a reachable report server to render. Check its URL and credentials in your configuration.

Why does the report succeed but nothing shows?

Likely the browser blocked a popup or download. Allow them for the site or try a private window.

Related

How-to

How to Modify an SSRS Report in Epicor Kinetic

Never edit a standard Epicor report style in place. Download the RDL for the style, edit the copy in Microsoft Report Builder, upload it as a new custom report style with its own ID, then assign that style where the document prints. Keep the RDL in source control so you can reapply or compare it after an upgrade.

Error fix

Epicor Kinetic Export to Excel Not Working

When Export to Excel or Copy to Excel does nothing in Epicor Kinetic, the cause is usually on the client: a blocked download or popup in the browser, a missing or mismatched Office install for Copy to Excel on the desktop client, or a very large result set. Test with a small grid and a different browser first, then check security and the dashboard definition.

Error fix

Epicor Kinetic: Menu Item Missing or Access Denied for a User

When an Epicor Kinetic user cannot see a menu item or gets an access denied message, the cause is nearly always security: the user's security group lacks access to that menu or program, the user is not linked to the company, the license or module is not available, or a menu customization hides the item. Check each in that order.

How-to

Preserving Customizations When Upgrading to Epicor Kinetic

Epicor Kinetic's web UI does not simply inherit classic smart-client customizations - most need to go through the Update Customization / Application Studio conversion process, and some WinForms-specific customizations cannot convert directly and must be rebuilt in the Kinetic designer. Plan the upgrade as a customization inventory and rework project, not a single technical cutover step.

Error fix

Fixing Epicor BusinessObjectException: BPM Directive Errors

A BusinessObjectException that says "A Business Process Management (BPM) directive has raised the following error" means a directive on that business object stopped the transaction, either deliberately via a Raise Exception widget or accidentally via an unhandled .NET error in Custom Code. Expand the InnerException on the error dialog to see the real message and the directive name, then open BPM Designer for that object and method to find the widget that fired.

How-to

Fixing a Slow Epicor BAQ (Business Activity Query)

A slow BAQ in Epicor is usually caused by unindexed join columns, a subquery or calculated field forcing a table scan, or the BAQ pulling far more rows than the dashboard actually displays before filtering client-side. Fix it by reading the SQL Server execution plan Epicor generates, moving filters into the BAQ criteria instead of the dashboard filter panel, and replacing subqueries with joins where possible.

AI for ERP

AI for Epicor Kinetic, Beyond What Prism Covers

Add AI to Epicor Kinetic beyond Prism: private LLM over BAQs, BPM data, and REST v2, on-prem or private cloud, with honest guidance on when Prism already covers you.

AI for ERP

Private AI for Epicor Kinetic Cloud, Outside the Multi-Tenant Boundary

Run a private LLM on Epicor Kinetic private cloud or Kinetic Cloud data via BAQs, REST v2 and Data Fabric, keeping sensitive manufacturing data off shared AI.

Stuck on Epicor Kinetic?

Talk to engineers who work inside Epicor Kinetic every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Comparisons

Software