Information Server Web Console error: Failed to Save Report

-

Technote (troubleshooting)

Problem(Abstract)

When creating and saving a report the Information Server Web Console is returning the error message "Failed to Save Report"

Symptom

Review the System.out log to look for the message:

com.ascential.acs.reporting.ReportingEngineException: /tmp/informationServer/Reporting<machine_name>Node01server1/engine/JREPORT/realm/defaultRealm/dhtmlPreference.properties (No such file or directory)


Cause

The error occurs when the JReport workspace directory in the Information Server is deleted


Diagnosing the problem

Check to see if the JReport workspace exists

For Information Server 8.1 the default directory is located under /<InformationServer_Install_Dir>/ASBServer/apps/Reporting/engine/JREPORT

For Information Server 8.5 and later the default directory is located under /tmp/informationServer/Reporting<machine_name>Node01server1/engine/JREPORT


Resolving the problem

Restart WebSphere to have the JReport workspace created if the JReport workspace does not exist.

Steps to restart WebSphere:

Windows :
cd WAS_home\bin
stopServer.bat server_name [options]
startServer.bat server_name

Unix :
cd WAS_home/bin
./stopServer.sh server_name [options]
./startServer.sh server_name

Also, please refer to this link on How to change the default location of the Information Server Reporting workspace:

http://www.ibm.com/support/docview.wss?rs=14&uid=swg21317914

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more