Unable to Generate the Validation Report

This article explains the common causes and resolutions for errors encountered when generating a Validation Report in Pulse.

What Is the Validation Report?

The Pulse Validation Report analyses the TM1 model and checks for common issues such as:

• Missing feeders

• Circular references in rules

• Unused dimensions

• Objects referencing non-existent elements

The report is accessed via Documentation → Validation Report in the Pulse web client.

Common Causes and Resolutions

Cause 1 — Documentation Has Not Been Run

The Validation Report depends on the Pulse documentation being up to date. If documentation has never been run or has failed, the report cannot be generated.

Resolution:

1. Go to Administration → Update Documentation.

2. Select the TM1 instance and click Document Selected Systems.

3. Wait for documentation to complete, then retry the Validation Report.

Cause 2 — Graphviz Is Not Installed or Not Configured

The Validation Report uses Graphviz to render relationship diagrams. If Graphviz is not installed or its path is not configured in Pulse.cfg, the report generation fails.

Resolution:

1. Verify Graphviz is installed on the Pulse server.

2. Check the path in Pulse.cfg under [Relationships]:

On Linux, verify the path in pulse.install.env:

3. Restart the Pulse Application Server after making changes.

Cause 3 — wkhtmltopdf Is Not Installed

PDF generation for the Validation Report requires wkhtmltopdf. If this library is missing, PDF export will fail.

Resolution:

Install wkhtmltopdf on the Pulse server. On Linux, it can be installed using the RPM included in the Pulse installer package:

Update the path in the Pulse configuration after installation.

Cause 4 — Insufficient Memory

Generating a Validation Report for a large TM1 model may cause the Pulse Application Server to run out of memory.

Resolution:

Increase the JVM maximum memory for the Pulse Application Server. See Update the Pulse Application Server JVM Maximum Memory for full steps.

Cause 5 — Permissions Issue

The Windows account running the Pulse Application Server service may not have write access to the temp folder used for report generation.

Resolution:

1. Check that the Pulse service account has write access to <Pulse Install Directory>\webapps\ROOT\WEB-INF\temp.

2. If the temp folder does not exist, create it manually.

3. Restart the Pulse Application Server service.

Checking Pulse Logs

If the cause is not immediately clear, check <Pulse Install Directory>\logs\pulse.log for error messages related to validation or report generation.