Oracle® Hyperion Financial Reporting

Error Message Reference

Release 11.1.2.4


Copyright © 2015, Oracle and/or its affiliates. All rights reserved.

Authors: EPM Information Development Team

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS:

Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.


EPMFR-00001: Duplicate arc exists in the linkbase. From: ({0}) to: ({1})

Cause: Duplicate arc nodes were provided for a linkbase.
Action: Ensure that the taxonomy does not use duplicate arc nodes.
Level: 1
Type: ERROR

EPMFR-00002: Error while trying to get content at URL: ({0}). Trying path: ({1}) instead.

Cause: The taxonomy's relative path was used instead of the URL location.
Action: Ensure that the taxonomy's URL location is properly formed.
Level: 1
Type: WARNING

EPMFR-00003: URL: ({0}) missing

Cause: The URL for the taxonomy was not found.
Action: Ensure that the taxonomy exists at the given location. Also ensure that the given taxonomy's URL is properly formed.
Level: 1
Type: WARNING

EPMFR-00004: {0} <element> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized taxonomy element attribute was found by the taxonomy parser. It will be ignored.
Action: Ensure that the taxonomy being parsed does not use unrecognized element attributes.
Level: 1
Type: ERROR

EPMFR-00005: {0} <schema> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized schema attribute was found by the taxonomy parser. It will be ignored.
Action: Ensure that the taxonomy being parsed does not use unrecognized schema attributes.
Level: 1
Type: WARNING

EPMFR-00006: Linkbase:{0} <linkbaseRef> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized linkbase attribute was found by the taxonomy parser. It will be ignored.
Action: Ensure that the taxonomy being parsed does not use unrecognized linkbase attributes.
Level: 1
Type: WARNING

EPMFR-00007: processImportAttributes:{0} <import> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized import attribute was found by the taxonomy parser. It will be ignored.
Action: Ensure that the taxonomy being parsed does not use unrecognized import attributes.
Level: 1
Type: WARNING

EPMFR-00008: {0} <include> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized include attribute was found by the taxonomy parser. It will be ignored.
Action: Ensure that the taxonomy being parsed does not use unrecognized include attributes.
Level: 1
Type: WARNING

EPMFR-00009: Error writing binary data to file: ({0})

Cause: Write permissions to the file may be denied due to user permission settings or disk space limitations.
Action: Ensure that the user has write permissions to the file and that there is enough disk space.
Level: 1
Type: ERROR

EPMFR-00010: Error reading binary data from file: ({0})

Cause: File is missing or not accessible at this time.
Action: Verify that the file exists and is available, or try later.
Level: 1
Type: ERROR

EPMFR-00011: Cannot load bursting file: {0}. Internal unique identifier of this file is: [{1}].

Cause: The file that was accessed does not exist.
Action: Select a file that exists and rerun.
Level: 1
Type: ERROR

EPMFR-00012: Cannot load bursting file: {0}. Internal unique identifier of this file is: [{1}].

Cause: The file that was accessed does not exist.
Action: Select a file that exists and rerun.
Level: 1
Type: ERROR

EPMFR-00013: GIF no longer supported

Cause: An unsupported Graphic Interchange Format (GIF) file was encountered as a report image.
Action: Convert the GIF file to a Bitmap (BMP) file and reload.
Level: 1
Type: WARNING

EPMFR-00014: GIF no longer supported

Cause: An unsupported Graphic Interchange Format (GIF) file was encountered as a report image.
Action: Convert the GIF file to a Bitmap (BMP) file and reload.
Level: 1
Type: WARNING

EPMFR-00015: GIF no longer supported

Cause: An unsupported Graphic Interchange Format (GIF) file was encountered as a report image.
Action: Convert the GIF file to a Bitmap (BMP) file and reload.
Level: 1
Type: WARNING

EPMFR-00016: Batches run successfully will be cleaned up after {0} milliseconds.

Cause: The batches were run successfully and will be cleaned up.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00017: The thread which cleans up scheduled batches will wake up every {0} milliseconds.

Cause: The thread that cleaned the scheduled batches occurs every number of milliseconds.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00019: Cannot not find binary file: {0}

Cause: The reported file could not be found and may result in missing data, text, or images.
Action: Ensure that the selected .BES file is correct and corresponds to the loaded .DES file.
Level: 1
Type: ERROR

EPMFR-00021: Attempted to cancel job, but could not find JobId: {0}

Cause: The selected job no longer exists.
Action: Check if the job already completed or was removed by another user.
Level: 1
Type: ERROR

EPMFR-00022: Unable to open connection to data source. Failure result: {0}.

Cause: Either a connection to the data source was not established, or the user credentials for the data source were incorrect.
Action: Verify that the connectivity to the data source and that the user credentials for the data source are accurate.
Level: 1
Type: ERROR

EPMFR-00023: Cannot find job definition {0}

Cause: The selected batch job was not found.
Action: Refresh the display and verify that the requested batch exists, then try again.
Level: 1
Type: WARNING

EPMFR-00026: Key '{0}' already exists for {1}

Cause: The given extended link was not added to the element because it already exists.
Action: Ensure that the taxonomy does not attempt to add duplicate extended links to the same element.
Level: 1
Type: WARNING

EPMFR-00027: Unable to load error message for key: {0}

Cause: The resource for the error message was not found.
Action: An error message or translated message is missing from the resource file. Contact Oracle Support Services.
Level: 1
Type: ERROR

EPMFR-00028: Unable to load error message for key: {0}

Cause: The resource for the error message was not found.
Action: An error message or translated message is missing from the resource file. Contact Oracle Support Services.
Level: 1
Type: ERROR

EPMFR-00029: Unable to load error message for key: {0}

Cause: The resource for the error message was not found.
Action: An error message or translated message is missing from the resource file. Contact Oracle Support Services.
Level: 1
Type: ERROR

EPMFR-00030: Unable to load error message for key: {0}

Cause: The resource for the error message was not found.
Action: An error message or translated message is missing from the resource file. Contact Oracle Support Services.
Level: 1
Type: ERROR

EPMFR-00031: Class '{0}' must extend from the ReportAddOn class

Cause: This is custom code in which the AddOn class did not extend the ReportAddOn class.
Action: The Java class in the Reports AddOn needs to extend the ReportAddOn class.
Level: 1
Type: ERROR

EPMFR-00032: Error executing batch: {0}

Cause: The Reports Web Server was not available, the report to be run was not located, or there were no correct user credentials supplied for the batch routine.
Action: Verify the availability of the Reports Web Server, that the report in the batch exists, and that the user credentials for the batch routine are correct.
Level: 1
Type: ERROR

EPMFR-00033: Type {0} of a service on {1} is shutting down.

Cause: A service on the noted server was shut down and removed from the registry.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00034: Type {0} of a service on {1} is started.

Cause: A service on the noted server was started and added to the registry.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00035: Initializing Financial Reporting Analytic Data Model Service

Cause: The Financial Reporting Analytic Data Model Service was about to initialize.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00036: Failure to initialize Financial Reporting Analytic Data Model Service

Cause: There was most likely an installation or configuration error that caused the initialization error.
Action: Check the installation and configuration logs for more information.
Level: 1
Type: ERROR

EPMFR-00037: Stopping Financial Reporting Analytic Data Model Service

Cause: The Financial Reporting Analytic Data Model Service was stopping.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00038: Failure to stop Financial Reporting Analytic Data Model service

Cause: There most likely was a memory issue on the system.
Action: Check the system hardware for memory usage issues.
Level: 1
Type: ERROR

EPMFR-00039: Initializing Financial Reporting Printing Service

Cause: The Financial Reporting Printing Service was initializing.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00040: Failure to start Financial Reporting Printing Service

Cause: The Financial Reporting Printing Service failed to initialize.
Action: Look at the installation and configuration logs for possible errors; check the system for memory errors, disk space, or other system related issues.
Level: 1
Type: ERROR

EPMFR-00041: Stopping Financial Reporting Printing Service

Cause: The Financial Reporting Printing Service stopped.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00042: Failure to stop Financial Reporting Printing Service

Cause: The Financial Reporting Printing Service failed to stop.
Action: Check the logs for print jobs running. Also, check the system for memory errors or other system-related issues.
Level: 1
Type: ERROR

EPMFR-00043: Initializing and starting Financial Reporting Service

Cause: The Financial Reporting Service initialized.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00044: Failure to start Financial Reporting Service

Cause: The Financial Reporting Service failed to initialize.
Action: Check the installation and configuration logs for possible errors, and check the system for memory errors, disk space, or other system related issues.
Level: 1
Type: ERROR

EPMFR-00045: Stopping Financial Reporting Service

Cause: The Financial Reporting Service stopped.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00046: Failure to stop Financial Reporting Service

Cause: The Financial Reporting Service failed to stop.
Action: Check the logs for running reports, batch jobs, or any other running report process. Also, check the system for memory errors or other system-related issues.
Level: 1
Type: ERROR

EPMFR-00047: Financial Reporting Scheduler Service initialized

Cause: The Financial Reporting Scheduler Service was initializing.
Action: No action is required
Level: 1
Type: NOTIFICATION

EPMFR-00048: Failure to start Financial Reporting Scheduler Service

Cause: The Financial Reporting Scheduler Service failed to initialize.
Action: Look at the installation and configuration logs for possible errors; check the system for memory errors, disk space, or other system-related issues.
Level: 1
Type: ERROR

EPMFR-00049: The Financial Reporting Scheduler Service stopped

Cause: The Financial Reporting Scheduler Service stopped.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00050: Failure to stop Financial Reporting Scheduler Service

Cause: The Financial Reporting Scheduler Service failed to initialize.
Action: Check the logs for scheduled jobs that may have failed. Also, check the system for memory errors or other system-related issues.
Level: 1
Type: ERROR

EPMFR-00051: Returning HsServer from machine {0}

Cause: The Reports server was successfully selected from the registry.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00052: Cannot get Report Server object

Cause: Failed to get the Report Server object from the registry. There may be an access or connectivity issue.
Action: Verify that the registry, RMI, and Reports Servers are all operational and that there are no network issues. Also verify all user credentials. Contact Oracle Support Services if this issue cannot be resolved.
Level: 1
Type: ERROR

EPMFR-00053: Unable to find Print Server

Cause: Failed to get the print server object from the registry; possible access or connectivity issue.
Action: Verify that the registry, RMI, and Reports Servers are all operational and that there are no network issues. Also verify all user credentials. Contact Oracle Support Services if this issue cannot be resolved.
Level: 1
Type: ERROR

EPMFR-00054: Cannot connect to server on {0}

Cause: Failure to connect to the specified server is most likely due to an RMI (Remote Method Invocation) issue.
Action: Verify that the RMI (Remote Method Invocation) service is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 1
Type: NOTIFICATION

EPMFR-00055: Could not connect to server on {0}

Cause: Failed to connect to the specified server most likely due to an RMI issue.
Action: Verify the RMI (Remote Method Invocation) service is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 1
Type: NOTIFICATION

EPMFR-00056: Cannot obtain report server list from server

Cause: Failed to get a report server list because the Hyperion Registry is not accessible.
Action: Verify that the Hyperion Registry is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 1
Type: ERROR

EPMFR-00057: Cannot obtain print server list from server

Cause: Failed to get a print server list because the Hyperion Registry is not accessible.
Action: Verify that the Hyperion Registry is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 1
Type: ERROR

EPMFR-00058: Cannot obtain scheduler server from server

Cause: Failed to get a scheduler server list because the Hyperion Registry is not accessible.
Action: Verify that the Hyperion Registry is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 1
Type: ERROR

EPMFR-00059: Invalid login: ({0})

Cause: The login security credentials for a given data source were invalid.
Action: Provide data source credentials to view the portlet content.
Level: 1
Type: ERROR

EPMFR-00060: Invalid report: ({0})

Cause: The portlet failed to generate the specified Financial Reports report.
Action: Ensure that the specified report exists or can be run using the Financial Reports Web preview.
Level: 1
Type: ERROR

EPMFR-00061: Cannot retrieve Row & Column Template [{0}] into Grid '{1}'. The template may have been moved, renamed or deleted from the repository.

Cause: A reference to a Row and Column template was not found in the repository.
Action: Ensure that the template exists in the expected folder within the repository. It could have been renamed, moved, or deleted. But it needs to exist in the specified path.
Level: 1
Type: ERROR

EPMFR-00062: Error adding incompatible Row & Column template [{0}] to Grid '{1}'. The template and/or grid may have been modified such that they are no longer compatible. The insert error code is {2}.

Cause: Dimensions on the row or column have changed, thus making the Row & Column template invalid for the grid.
Action: No action is required. The invalid Row & Column template was removed.
Level: 1
Type: ERROR

EPMFR-00063: The maximum calculation limit of {0} has been reached. Further processing of this cell calculation will not occur.

Cause: The report contained unevaluated cells due to reaching the maximum calculations limit.
Action: Update the MaximumCalculationIterations setting. Refer to the documentation for instructions.
Level: 1
Type: ERROR

EPMFR-00064: Error while opening connection for user: {0} to the data source: {1}:{2}

Cause: An error occurred when attempting to establish a connection with a selected data source.
Action: Ensure that the data source exists and is available. Also, verify that user credentials to the selected data source are accurate.
Level: 1
Type: ERROR

EPMFR-00065: Financial Management server {0} is not responding

Cause: A connection could not be made to the Financial Management server. The Financial Management server is either offline or has been reconfigured.
Action: Verify the Financial Management connection information and ensure that the server or cluster is online.
Level: 1
Type: ERROR

EPMFR-00066: Attempting to cancel Essbase report script for ID: {0}

Cause: A user issued a cancel request for the Essbase report script.
Action: No action is required. The Essbase report script will be canceled if possible.
Level: 1
Type: NOTIFICATION

EPMFR-00067: Canceling run for job with instanceId: {0}

Cause: The job with the associated ID was canceled.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00068: Invalid attempt to access controlled file: {0}

Cause: The file path was incorrect.
Action: Enter the correct file location and try again.
Level: 1
Type: ERROR

EPMFR-00069: START: JobId: {0}; User: {1}; Name: {2}

Cause: The START time of the associated job with the given ID was marked.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00070: END: JobId: {0}

Cause: The END time of the associated job with the given ID was marked.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00071: Custom Socket Factories loaded successfully

Cause: The sockets connecting to the RMI server were successfully established.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00072: Unable to establish port within established range

Cause: The established range of ports selected to access the RMI server were unavailable.
Action: Either reestablish a different range with available ports, or, stop nonessential processes that are occupying the port range, and then retry.
Level: 1
Type: INCIDENT_ERROR

EPMFR-00073: User preferences or ReportServer object are not properly initialized. Unable to save User Preferences.

Cause: The connection to the server was disrupted.
Action: Log out and try again.
Level: 1
Type: ERROR

EPMFR-00074: User preferences or ReportServer object are not properly initialized. Unable to save user preferences.

Cause: The connection to the server possibly was disrupted.
Action: Log out and try again.
Level: 1
Type: ERROR

EPMFR-00075: Cannot connect to Related Content destination. status = {0}.

Cause: The Related Content destination was not available.
Action: Verify that the Related Content destination exists and that the calling object has it set correctly.
Level: 1
Type: ERROR

EPMFR-00076: Substituting related content attributes. Reference String is: [{0}]

Cause: The related content attributes were substituted.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00077: Error exporting file: {0}

Cause: The file may have been deleted.
Action: Refresh the browser and try the operation again.
Level: 1
Type: ERROR

EPMFR-00078: Error exporting file: {0}

Cause: The file may have been deleted.
Action: Refresh the browser and try the operation again.
Level: 1
Type: ERROR

EPMFR-00079: Error getting folder: {0}

Cause: The folder may have been deleted.
Action: Refresh the browser and retry the operation.
Level: 1
Type: ERROR

EPMFR-00080: Error retrieving report or snapshot: {0}

Cause: The book contains a report or snapshot that was not found.
Action: Ensure that the report or snapshot exists in the book.
Level: 1
Type: ERROR

EPMFR-00081: Connected to server: {0}

Cause: A successful connection was made to the Report Server.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00082: Unable to stop job {0}

Cause: The selected data source did not respond to the cancel request.
Action: Verify that the selected data source is accessible and operating. Check the data source logs for any other issues.
Level: 1
Type: ERROR

EPMFR-00083: Unable to delete job: {0}

Cause: The Report Server could not be accessed.
Action: Verify that the Report Server is running and verify that the user has permissions to delete the scheduled job.
Level: 1
Type: ERROR

EPMFR-00084: Error executing member selection: [{0}]

Cause: Either the member selection was not valid or the data source connection failed.
Action: Check connection to the data source.
Level: 1
Type: ERROR

EPMFR-00085: Error executing member selection: [{0}]

Cause: Either the member selection was not valid or the data source connection failed.
Action: Check the connection to the data source.
Level: 1
Type: ERROR

EPMFR-00086: Hyperion Financial Management indicates that either data or metadata has changed.

Cause: Hyperion Financial Management indicates that either data or metadata had changed.
Action: Discard the current connection, then acquire a new connection, and then rerun the book or report.
Level: 1
Type: WARNING

EPMFR-00087: Error in setting up the 'Org By Period Filter'

Cause: Either the member selection was not valid or the data source connection failed.
Action: Check connection to the data source.
Level: 1
Type: ERROR

EPMFR-00088: External authentication successful for user: [{0}] succeeded in {1} ms.

Cause: The user logon was successful in the associated time in milliseconds.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00089: User [{0}] has no access to Financial Reporting.

Cause: A user without any Financial Reporting roles tried to access Financial Reporting.
Action: Review the user's credentials for security purposes.
Level: 1
Type: NOTIFICATION

EPMFR-00090: Failure to initialize ADM

Cause: The Financial Reporting Server did not initialize the ADM component for data source communication.
Action: A configuration issue is the likely cause, so verify that the ADM is specified within the classpath or path.
Level: 1
Type: ERROR

EPMFR-00091: Starting Report Server and modules

Cause: The Report Server and associated modules were started.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00092: Error starting Report Server

Cause: The report server did not start.
Action: Check for port conflicts or other configuration issues, whether the system hostname is correctly configured, and if the RMI registry is available.
Level: 1
Type: ERROR

EPMFR-00093: Successful start for Financial Reporting Authentication, Repository and Reports modules.

Cause: The Financial Reporting Authentication, Repository and Reports modules started successfully.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00094: Error during data source connection cleanup

Cause: Another request to close the datasource connections may have been issued previous to the current request.
Action: Check the list of active sessions and retry, closing any existing sessions.
Level: 1
Type: ERROR

EPMFR-00095: Invalid command line parameters

Cause: The number of command line parameters was incorrect.
Action: Ensure that the correct number of parameters are entered when starting from the command line.
Level: 1
Type: NOTIFICATION

EPMFR-00096: Error while writing the binary data of the report object to file: ({0})

Cause: An error occurred while writing the binary data of the report object to the specified file.
Action: Verify that the user has permission to write to the file and ensure that there is enough disk space.
Level: 1
Type: ERROR

EPMFR-00097: Removing annotation on existing snapshot as duplicate annotation is generated: {0}

Cause: The annotation on the existing snapshot was a duplicate and was removed.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00098: Retrieving annotations from repository: {0}

Cause: Annotations were retrieved from the repository
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00099: In method Instance.createDuplicateAnnotationsForSnapshot() annotation count: {0}

Cause: In method Instance.createDuplicateAnnotationsForSnapshot() annotation count: {0}
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00100: Creation of duplicate annotations for snapshot successful: {0}

Cause: Duplicate annotations for snapshot were completed: {0}
Action: No Action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00101: Not expecting Context Value; Finding: {0}; Expected: {1}

Cause: An invalid Context Value was received and might not exist in the repository.
Action: Verify that the instance exists in the repository.
Level: 1
Type: ERROR

EPMFR-00102: Error in sending e-mail: {0}

Cause: An error occurred while sending an e-mail. This can happen due to network issues or invalid information.
Action: Verify the e-mail address, and check if the mail server is available.
Level: 1
Type: ERROR

EPMFR-00103: Error while getting dimension: {0}

Cause: The datasource connection was either lost or not established. Otherwise an internal error in the data source occurred.
Action: Verify that the data source is running and accessible, and then retry. Otherwise, check the data source logs for any data access issues.
Level: 1
Type: ERROR

EPMFR-00104: Error while getting dimension: {0}

Cause: The datasource connection was either lost or not established. Otherwise an internal error in the data source occurred.
Action: Verify that the data source is running and accessible, and then retry. Otherwise check the datasource logs for any data access issues.
Level: 1
Type: ERROR

EPMFR-00105: Error while getting member selections

Cause: The datasource connection was either lost or not established. Otherwise an internal error in the data source occurred.
Action: Verify that the data source is running and accessible, and then retry. Otherwise check the datasource logs for any data access issues.
Level: 1
Type: ERROR

EPMFR-00106: Failure in exporting user session for use in static HTML generation

Cause: Access to the Report Server connection might have been lost.
Action: Verify the Remote Method Invocation (RMI) service is operational and the same with the Report Server. Ensure that all communication routes between the services are also available. Contact Oracle Support Services if all services and communication routes are operational.
Level: 1
Type: ERROR

EPMFR-00107: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored. This may happen because the central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.
Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file to be saved has a valid file name.
Level: 1
Type: ERROR

EPMFR-00108: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored. This may happen because the central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.
Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file to be saved has a valid file name.
Level: 1
Type: ERROR

EPMFR-00109: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored. This may happen because the central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.
Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file to be saved has a valid file name.
Level: 1
Type: ERROR

EPMFR-00110: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored. This may happen because the central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.
Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file to be saved has a valid file name.
Level: 1
Type: ERROR

EPMFR-00111: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored. This may happen because the central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.
Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file to be saved has a valid file name.
Level: 1
Type: ERROR

EPMFR-00112: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored. This may happen because the central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.
Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file to be saved has a valid file name.
Level: 1
Type: ERROR

EPMFR-00113: Cannot find the static book template root directory

Cause: The static book template root directory within the scheduler properties was not found.
Action: Check if there are any product configuration issues within the config logs. Check if the SchedulerTemplate is defined in fr_scheduler.properties.
Level: 1
Type: ERROR

EPMFR-00114: Error creating zip file. File does not exist: {0}.

Cause: The specified file and path did not exist.
Action: Verify that the file and path specified exist.
Level: 1
Type: WARNING

EPMFR-00115: Data source names to validate: {0}

Cause: A status message lists the data sources that were validated.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00116: Data source names to validate: {0}

Cause: A status message that lists the data sources that were validated.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00117: Connecting to Report Server: {0}

Cause: The Report Server was connected for validation.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00118: Users to validate: {0}

Cause: Users were validated.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00119: Users to validate: {0}

Cause: User were validated.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00120: Finding {0} match(es).

Cause: A status message was provided with the data source information from the user's point of view.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00121: This action will delete {0} POVs

Cause: A status message was provided that stated the number of POVs that were deleted.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00122: Not finding POVs

Cause: A status message was provided that stated that no POVs were found.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00123: User POV import LoginID = {0}

Cause: A status message was provided that listed the user ID while importing a user POV.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00124: Not finding user: {0}

Cause: There was an unforseen condition where user information could not be extracted from security.
Action: Generally this error should not happen. An extreme condition where this may occur is if security were to intermittently fail. Check the foundation services and the network for possible issues. Contact Oracle Support Services if unable to be resolved.
Level: 1
Type: WARNING

EPMFR-00125: Member missing: {0}

Cause: The member name was not found within the data source because it either did not exist or could not be seen by the current user. It will not be imported.
Action: By default, the member name is skipped. However, if the member name is needed, then it must be made available either by adjusting the data source security access for the user, or by entering the member name into the data source.
Level: 1
Type: WARNING

EPMFR-00126: No DATASOURCE_NAME in XML file

Cause: The XML file being imported for user POV information was missing a datasource name.
Action: Supply a valid datasource name in the XML file.
Level: 1
Type: ERROR

EPMFR-00127: Error loading config file: {0}

Cause: The specified configuration file did not exist or was not accessible.
Action: Supply a valid and accessible file name as a parameter.
Level: 1
Type: ERROR

EPMFR-00128: Missing AdminUser

Cause: The configuration file did not have an administrative user (AdminUser) specified.
Action: In the configuration file, specify a user (AdminUser) with Administrator access.
Level: 1
Type: ERROR

EPMFR-00129: No AdminPassword

Cause: The configuration file did not have an administrator password (AdminPassword) specified.
Action: In the configuration file, specify an administrator password (AdminPassword) for the user.
Level: 1
Type: ERROR

EPMFR-00130: No ImportFileName

Cause: The configuration file did not have a user POV import file name (ImportFileName).
Action: Specify a valid import file name (ImportFileName) when running in import mode.
Level: 1
Type: ERROR

EPMFR-00131: ImportFileName missing: {0}

Cause: The specified user POV import file name (ImportFileName) was invalid.
Action: Specify a valid import file name (ImportFileName)when running in import mode.
Level: 1
Type: ERROR

EPMFR-00132: Error while reading the ImportFile

Cause: An error occurred while reading the import file. This could be caused by a file access issue or any other error while processing the import file.
Action: Verify that the file is still accessible and readable to the user. Look for other issues within both the Report Server and connecting data sources for other possible causes. Contact Oracle Support Services for additional assistance.
Level: 1
Type: ERROR

EPMFR-00133: Error while reading the ImportFile

Cause: An error occurred while reading the import file. This could be caused by a file access issue or any other error while processing the import file.
Action: Verify that the file is still accessible and readable to the user. Look for other issues within both the Report Server and connecting data sources for other possible causes. Contact Oracle Support Services for additional assistance.
Level: 1
Type: ERROR

EPMFR-00134: No ExportFileName

Cause: The user POV export file name (ExportFileName) was not specified.
Action: Specify a valid user POV export file name (ExportFileName).
Level: 1
Type: ERROR

EPMFR-00135: No ReportServer

Cause: A valid and working Report Server (ReportServer) was not specified.
Action: Specify a valid and working Report Server (ReportServer).
Level: 1
Type: ERROR

EPMFR-00136: Starting Hyperion Financial Reporting ManageUserPOV Utility at: {0}

Cause: The ManageUserPOV utility started and is accompanied by a time stamp to monitor the time lapse.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00137: Ending Hyperion Financial Reporting ManageUserPOV Utility at: {0}

Cause: The ManageUserPOV utility ended and is accompanied by a time stamp to mark the end of the time lapse.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00138: Usage: ManageUserPov Mode ConfigFile\n\tMode = import | export | delete\n\tConfigFile = configuration file name such as ManageUserPov.properties

Cause: An instruction about how to use the ManageUserPov utility was provided.
Action: Follow the instructions of the message.
Level: 1
Type: ERROR

EPMFR-00139: Data source does not exist: {0}, A new one will be created.

Cause: The data source was not previously configured, but the utility attempted to create a connection with the specified data source automatically.
Action: No action is required unless a new data source cannot be created automatically.
Level: 1
Type: WARNING

EPMFR-00140: Creating data source: {0}

Cause: The data source was created successfully.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00141: Exception: {0} in loading locale strings for locale: {1}

Cause: The file that contains the translated messages either was not found or the file contained errors.
Action: Look at the installation and configuration logs for possible errors. Contact Oracle Support Services for additional assistance.
Level: 1
Type: ERROR

EPMFR-00142: Error while storing PDF

Cause: The PDF file was not stored. This may happen because the central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.
Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file to be saved has a valid file name.
Level: 1
Type: ERROR

EPMFR-00143: Error while storing PDF

Cause: The PDF file was not stored. This may happen because the central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.
Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file to be saved has a valid file name.
Level: 1
Type: ERROR

EPMFR-00144: Error while storing PDF

Cause: The PDF file was not stored. This may happen because the central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.
Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file to be saved has a valid file name.
Level: 1
Type: ERROR

EPMFR-00145: Error while storing PDF

Cause: The PDF file was not stored. This may happen because the central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.
Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file to be saved has a valid file name.
Level: 1
Type: ERROR

EPMFR-00146: Error storing PDF

Cause: The PDF file was not stored. This may happen because the central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.
Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file to be saved has a valid file name.
Level: 1
Type: ERROR

EPMFR-00147: Error storing PDF

Cause: The PDF file was not stored. This may happen because the central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.
Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file to be saved has a valid file name.
Level: 1
Type: ERROR

EPMFR-00148: Start of print server job

Cause: The print server job started.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00149: Completed printing of book or report

Cause: The book or report printing was completed.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00150: Cannot get page number count for instance '{0}'. Continuous page numbers may not be correct.

Cause: There was no page count for instance '{0}'. Continuous page numbers may be applied incorrectly.
Action: Verify that the print server is installed correctly.
Level: 1
Type: ERROR

EPMFR-00152: Cannot find BookTOCPrintTemplate {0} entry in properties file. Cannot generate Book TOC.

Cause: The specified BookTOCPrintTemplate entry was not found in the properties file. The Book TOC was not generated.
Action: Verify that the print server is installed correctly.
Level: 1
Type: ERROR

EPMFR-00153: Cannot print report '{0}' within Book '{1}'

Cause: The specified report was not printed within the specified book.
Action: Ensure that all external object links in the book are correct, that the book is valid, and that the report exists in the repository.
Level: 1
Type: ERROR

EPMFR-00160: Cannot retrieve the document file: '{0}'

Cause: The specified document file was not retrieved.
Action: Verify that the PDF output location is correct in the property file.
Level: 1
Type: ERROR

EPMFR-00161: Error generating print for report instance '{0}'. Return code: {1}

Cause: There was an error when trying to print the specified report instance.
Action: Verify that the instance runs correctly in HTML, and if it has attachments, that the links are valid.
Level: 1
Type: ERROR

EPMFR-00162: Start of run for {0} job {1}

Cause: The specified print job started.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00163: End of run for {0} end

Cause: The specified print job ended.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00164: Cannot print using printer '{0}'. The printer is either not available to the Print Server or not configured for the host computer's services.

Cause: The specified printer was not used because either it was not available to the print server, or it was not configured for the host computer's services.
Action: Ensure that the print server is installed correctly.
Level: 1
Type: ERROR

EPMFR-00165: Error when printing an instance

Cause: An error occurred when the instance was printing.
Action: Verify that the instance runs correctly in HTML, and if it has attachments, that the links are valid.
Level: 1
Type: ERROR

EPMFR-00166: No page count for the table of contents in book '{0}'

Cause: The page count for the table of contents in the specified book was not obtained.
Action: Verify that all external object links in the book are correct and that the book is valid.
Level: 1
Type: ERROR

EPMFR-00167: No table of contents in book '{0}'

Cause: The table of contents in the book was not produced.
Action: Verify that all external object links in the book are correct and that the book is valid.
Level: 1
Type: ERROR

EPMFR-00168: Cannot merge PDF file '{0}'. The file does not exist.

Cause: The specified PDF file was not merged because the file did not exist.
Action: Verify that the print server is installed correctly and Ghostscript is there.
Level: 1
Type: ERROR

EPMFR-00169: Error in merging PDF file ({0})

Cause: The attempt to merge the specified PDF file generated an error.
Action: Verify that the print server is installed correctly and that Ghostscript is there.
Level: 1
Type: ERROR

EPMFR-00170: Cannot get page number count for instance '{0}'. Continuous page numbers may not be correct.

Cause: There was no page count or continuous page numbers because the print server might be installed incorrectly.
Action: Verify that all external object links in the book are correct and that the book is valid.
Level: 1
Type: ERROR

EPMFR-00171: Cannot print instance: '{0}'. The PostScript file for the instance does not exist.

Cause: The specified instance was not printed. The PostScript file for the instance does not exist.
Action: Ensure that Ghostscript is installed.
Level: 1
Type: ERROR

EPMFR-00172: Cannot print instance: '{0}'. The PostScript file for the instance does not exist.

Cause: The specified instance was not printed. The PostScript file for the instance did not exist.
Action: Ensure that Ghostscript is installed.
Level: 1
Type: ERROR

EPMFR-00173: Error generating the bookmark outline for '{0}'

Cause: The bookmark outline for the specified PDF file generated an error.
Action: Ensure that the iText version is correct.
Level: 1
Type: ERROR

EPMFR-00174: Error generating the book table of contents for '{0}'

Cause: The book table of contents for the specified PDF file generated an error.
Action: Verify that the iText version is correct.
Level: 1
Type: ERROR

EPMFR-00175: Cannot print document file: '{0}' \n\tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.
Action: Verify that the external document link is correct.
Level: 1
Type: ERROR

EPMFR-00176: Cannot print document file: '{0}' \n\tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.
Action: Verify that the external document link is correct.
Level: 1
Type: ERROR

EPMFR-00177: Cannot obtain page count from file '{0}'. The file type is not supported for printing.

Cause: The page count was not obtained from the specified file. The file type is not supported for printing.
Action: Ensure that the file type is supported by the print server.
Level: 1
Type: ERROR

EPMFR-00178: Error writing external file '{0}'. It will not be included in the PDF output.

Cause: There was an error when writing the specified external file.
Action: Verify that the PDF output location is correct in the property file.
Level: 1
Type: ERROR

EPMFR-00179: Error reading external PDF file '{0}'. It will not be included in the PDF output.

Cause: There was an error when reading the specified external PDF file.
Action: Verify that iText has the correct version.
Level: 1
Type: ERROR

EPMFR-00180: Cannot retrieve the document file: '{0}' The returned error code is: {1}, Last error: {2}

Cause: The specified document files was not retrieved.
Action: Verify that the external object's link is correct.
Level: 1
Type: ERROR

EPMFR-00181: Cannot produce the PDF output for the external document '{0}'

Cause: The specified external document file did not produce PDF output.
Action: Verify that external link in the print object is correct.
Level: 1
Type: ERROR

EPMFR-00182: Cannot produce the PDF output for the book or instance '{0}'. The returned error code is: {1}, Last error: {2}

Cause: The specified book or instance did not produce PDF output.
Action: Ensure that the HRDocumentPrinting.dll file is installed correctly.
Level: 1
Type: ERROR

EPMFR-00183: Cannot print instance or book: '{0}'. The print file is not produced.

Cause: The specified instance or book was not printed. The print file was not produced.
Action: Verify that Ghostscript is installed correctly.
Level: 1
Type: ERROR

EPMFR-00184: Cannot send output to the system printer. No printer specification.

Cause: Because no printer was specified, the output was not sent to the system printer.
Action: Verify that the physical printer is correct.
Level: 1
Type: ERROR

EPMFR-00185: Cannot send instance output to the system printer ('{0}'). No instance retrieval.

Cause: The instance was not retrieved because the instance output was not sent to the system printer.
Action: Ensure that the server which has the repository is up and the object is running.
Level: 1
Type: ERROR

EPMFR-00186: Cannot send book output to the system printer ('{0}'). No book retrieval.

Cause: The book was not retrieved because the book output was not sent to the system printer.
Action: Ensure that the server that has the repository is up and the book is running.
Level: 1
Type: ERROR

EPMFR-00187: Invalid object type '{0}'. Cannot send output to system printer('{1}')

Cause: Due to an invalid file type, the output was not sent to the specified system printer.
Action: Verify that the file type is supported by the print server.
Level: 1
Type: ERROR

EPMFR-00188: Successful printing '{0}' on system printer '{1}'

Cause: The specified document was successfully printed on the specified system printer.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00189: FRExecute has invalid cell reference '{0}'

Cause: FRExecute referenced an invalid cell.
Action: Verify that the FRExecute function's parameters are valid.
Level: 1
Type: ERROR

EPMFR-00190: FRExecute cannot generate an image for component '{0}'

Cause: FRExecute could not generate an image for the specified component.
Action: Verify that the FRExecute function's parameters are valid.
Level: 1
Type: ERROR

EPMFR-00191: Cannot replace FRExecute function with the result.

Cause: The FRExecute function could not be replaced with the result.
Action: Verify that Microsoft Word is installed on the machine where the print server is located.
Level: 1
Type: ERROR

EPMFR-00192: Cannot load Ghostscript or Distiller.

Cause: Ghostscript or Distiller could not be loaded.
Action: Ensure that a supported version of Ghostscript or Distiller is properly installed on the print server.
Level: 1
Type: ERROR

EPMFR-00193: Ghostscript error in converting to PostScript.

Cause: A supported version of Ghostscipt may not be installed on the print server.
Action: Ensure that a supported version of Ghostscript is installed on the print server. If the problem persists, please contact Oracle Support Services.
Level: 1
Type: ERROR

EPMFR-00194: PDF root directory is {0}

Cause: The cited directory name was the root directory of the PDF file.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00195: The report: [{0}] not cancelling

Cause: The specified report failed to cancel.
Action: Verify that the Print Server or Network is not down.
Level: 1
Type: ERROR

EPMFR-00196: Printer {0} not accessible on print server: {1}

Cause: Printer {{0}} was not accessible on print server: {1}.
Action: Verify that the print server is running and that the printer is available.
Level: 1
Type: NOTIFICATION

EPMFR-00198: Duplicate member in a prompt. Duplicate member will be removed.

Cause: A duplicate member was found during member selection from the data source.
Action: No action is required. A duplicate member was removed from the member selection display.
Level: 1
Type: ERROR

EPMFR-00199: Over 50 dimensions in the data source. Removing the following dimensions which are set to the default member:

Cause: An SAP data source with more then 50 dimensions was found. The SAP BAPI driver does not support accessing a data source with more then 50 dimensions.
Action: Reduce the number of dimensions in the data source or use a different data source.
Level: 1
Type: ERROR

EPMFR-00200: Error while setting POV:

Cause: There was probably a connection error with the data source while setting the POV.
Action: Verify that the selected data source is available, access credentials are correct, or review the logs from the data source for other possible issues.
Level: 1
Type: WARNING

EPMFR-00201: Exception while getting dimension {0}

Cause: There were data source access issues or an internal error in the data source.
Action: Verify that the selected data source is available, access credentials are correct, or review the logs from the data source for other possible issues.
Level: 1
Type: ERROR

EPMFR-00202: Exception while getting dimension {0}

Cause: There were data source access issues or an internal error in the data source.
Action: Verify that the selected data source is available, access credentials are correct, or review the logs from the data source for other possible issues.
Level: 1
Type: ERROR

EPMFR-00203: Using Enterprise Scheduling Services for scheduling

Cause: The Enterprise Scheduling Service was used.
Action: No is action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00205: Scheduler not ready to publish itself. Retry in {0} minutes.

Cause: No Report servers were running.
Action: Ensure that the Report Server is running. Retry in the specified minutes.
Level: 1
Type: WARNING

EPMFR-00206: Successful start of Scheduler Server

Cause: The Scheduler Server was started successfully.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00207: Scheduler cannot contact any Report Server. Exiting.

Cause: The Scheduler did not start because it did not contact any Report Server.
Action: Check on the availability of configured Reports Servers.
Level: 1
Type: NOTIFICATION

EPMFR-00208: Cannot start scheduler service:

Cause: An unexpected error occurred while the Scheduler Service was binding to the Report Server.
Action: Contact Oracle Support Services for assistance.
Level: 1
Type: ERROR

EPMFR-00210: Scheduler Server stopped

Cause: The Scheduler Server was stopped.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00213: Batch Job file: {0} not found. Error reported:

Cause: The specified scheduled batch job file was not found. The file may have been deleted or moved to another location.
Action: Verify that the specified file exists in the expected location and rerun the job.
Level: 1
Type: ERROR

EPMFR-00215: Schema '{0}' missing. Attempting to create a new one.

Cause: The schema was not previously loaded. An attempt to load it occurred.
Action: Ensure that the schema is valid and can be loaded. Look for additional warnings.
Level: 1
Type: WARNING

EPMFR-00216: Error while parsing a new schema:\n{0}

Cause: The error was produced while attempting to parse a schema.
Action: Ensure that the schema is valid and complies with the XBRL 2.1 specification.
Level: 1
Type: ERROR

EPMFR-00217: Schema: '{0}' missing. Cannot delete it.

Cause: The schema was not found.
Action: Ensure that the schema exists and can be removed from the file system.
Level: 1
Type: WARNING

EPMFR-00218: Schema: '{0}' missing. Cannot delete it.

Cause: The schema was not found.
Action: Ensure that the schema exists and can be removed from the file system.
Level: 1
Type: WARNING

EPMFR-00219: Error during the auto-update of Schemas:\n{0}

Cause: The error occurred while attempting to auto-update the schemas in the file system.
Action: Ensure that the schema exists, is valid and complies to the XBRL 2.1 specification.
Level: 1
Type: ERROR

EPMFR-00220: Error attempting to create a row and column template

Cause: An unexpected error occurred while attempting to add a row and column template into a grid.
Action: Review the Report Server log file for details on the error.
Level: 1
Type: ERROR

EPMFR-00221: Error attempting to add a row or column from a template.

Cause: An unexpected error occurred while attempting to add a row or column from a template into a grid.
Action: Review the Report Server log file for details on the error.
Level: 1
Type: ERROR

EPMFR-00233: Error while getting content at: ({0}). Trying ({1}/{2}) instead.

Cause: The path for the taxonomy was not found.
Action: Ensure that the taxonomy exists for the given path.
Level: 1
Type: WARNING

EPMFR-00234: Unknown linkbase role: {0} found. Linkbase will not be included.

Cause: The linkbase could not be added as a reference from a taxonomy.
Action: Ensure that the linkbase is valid and can be added as a reference to a taxonomy.
Level: 1
Type: ERROR

EPMFR-00235: The presentation linkbase '{0}' is empty. A flat taxonomy tree may display.

Cause: The taxonomy's presentation linkbase was empty, which typically causes a flat taxonomy tree to be rendered.
Action: Provide a presentation linkbase for the given taxonomy.
Level: 1
Type: WARNING

EPMFR-00236: TaxonomyElement: {0} not found.

Cause: The presentation linkbase had a reference to a taxonomy element that could not be found.
Action: Ensure that the presentation linkbase has references to valid taxonomy elements.
Level: 1
Type: WARNING

EPMFR-00237: Taxonomy Element Node: {0} not found

Cause: A taxonomy element node referenced by the given element ID could not be obtained.
Action: Ensure that the taxonomy element exists with the taxonomy.
Level: 1
Type: WARNING

EPMFR-00238: Taxonomy element '{0}' already exists.

Cause: The taxonomy element has already been processed. The taxonomy seems to have a duplicate element declaration.
Action: Ensure that the taxonomy does not contain duplicate taxonomy element declarations.
Level: 1
Type: WARNING

EPMFR-00239: The taxonomy element {0} was not mapped, as it is an abstract type.

Cause: The given element could not exist within an instance document. Typically, this is because an abstract element was mapped.
Action: Ensure that only mappable taxonomy elements are mapped within a report. Do not map abstract elements.
Level: 1
Type: WARNING

EPMFR-00240: Element specified in the locator: {0} {1} not found

Cause: The taxonomy element could not be found from the locator.
Action: Ensure that the taxonomy's locators have valid references to taxonomy elements.
Level: 1
Type: WARNING

EPMFR-00241: Element specified in the locator: {0} {1} not found

Cause: The taxonomy element could not be located from the locator.
Action: Ensure that the taxonomy's locators have valid references to taxonomy elements.
Level: 1
Type: WARNING

EPMFR-00242: Error in TextCell {0} Col {1} Row {2} Formula: '{3}'\n\t Error: {4}

Cause: There was a syntax error in the function.
Action: Fix the syntax error that is described in the error message.
Level: 1
Type: ERROR

EPMFR-00243: Error in TextObject Formula: '{0}'\n\t Error: {1}

Cause: There was a syntax error in the function.
Action: Fix the syntax error that is described in the error message.
Level: 1
Type: ERROR

EPMFR-00244: Report Server Initializing

Cause: The Report Server initialized.
Action: No action is required
Level: 1
Type: NOTIFICATION

EPMFR-00245: Report Server started

Cause: The Report Server initialized and started successfully.
Action: No action is required
Level: 1
Type: NOTIFICATION

EPMFR-00246: Error while starting the Report Server

Cause: The Report Server failed to initialize.
Action: Check a variety of possible failures including: Port conflicts or other configuration issues, incorrect system hostname configuration, and availability of the Remote Method Invocation (RM0).
Level: 1
Type: ERROR

EPMFR-00247: Hyperion Financial Management reports that either metadata or data has changed. Discarding the current connection and reconnecting.

Cause: Possible metadata or data load was performed on the Hyperion Financial Management server.
Action: Rerun the book or report.
Level: 1
Type: WARNING

EPMFR-00248: Book contains reports not found: {0}

Cause: The book contained reports which could not be found.
Action: Ensure that the contained report(s) exists.
Level: 1
Type: ERROR

EPMFR-00249: Cannot find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: WARNING

EPMFR-00250: Could not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source name.
Action: Verify that data source is started or restored, and the credentials are correct.
Level: 1
Type: WARNING

EPMFR-00251: Cannot not find data source ID: {0} {1}. Failed to create a new data source for it.

Cause: A connection to the data source could not be made by using the stored data source ID or name; as a result, a new data source was not created.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: ERROR

EPMFR-00252: Cannot find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: ERROR

EPMFR-00253: Cannot find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made using the stored data source ID.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: ERROR

EPMFR-00254: Cannot not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source name.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: ERROR

EPMFR-00255: Cannot find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source name.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: ERROR

EPMFR-00256: Cannot find data source ID: {0} {1}. Failed to create a new data source for it.

Cause: Could not make a connection to the data source using the stored data source ID or name; as a result, a new data source was not created.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: ERROR

EPMFR-00257: Could not find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: ERROR

EPMFR-00258: Could not find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: WARNING

EPMFR-00259: Could not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source ID.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: ERROR

EPMFR-00260: Could not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source ID.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: WARNING

EPMFR-00261: Could not find data source ID: {0} {1}. Failed to create a new data source for it.

Cause: A connection to the data source could not be made by using the stored data source ID or name; as a result, a new data source was not created.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: ERROR

EPMFR-00262: Schema '{0}' not found. Attempting to create a new one.

Cause: The schema was not previously loaded. An attempt to load it occurred.
Action: Ensure that the schema is valid and can be loaded. Look for additional warnings.
Level: 1
Type: WARNING

EPMFR-00263: XBRL Schema Manager not properly initialized

Cause: The XBRL Schema Manager was not properly configured.
Action: Reconfigure the XBRL Schema Manager.
Level: 1
Type: ERROR

EPMFR-00264: XBRL Schema Manager not properly initialized

Cause: The XBRL Schema Manager was not properly configured.
Action: Reconfigure the XBRL Schema Manager.
Level: 1
Type: ERROR

EPMFR-00265: Schema {0} was not found. Attempting to create a new one

Cause: The schema was not previously loaded. An attempt to load it occurred.
Action: Make sure the schema is valid and can be loaded. Look for warnings.
Level: 1
Type: WARNING

EPMFR-00266: Taxonomy '{0}' does not have any namespace

Cause: The taxonomy did not declare a namespace and was not processed.
Action: Ensure that the taxonomy declares a valid namespace.
Level: 1
Type: WARNING

EPMFR-00267: Taxonomy '{0}' does not have any namespace

Cause: The given taxonomy did not declare a namespace and was not processed.
Action: Ensure that the given taxonomy declares a valid namespace.
Level: 1
Type: ERROR

EPMFR-00268: Error while creating directories for emails:

Cause: The Schedule Server attempted to create a directory for e-mails but failed, most likely due to a system disk access issue.
Action: Verify that the disk is not full and that the user has both read and write access to the drive.
Level: 1
Type: ERROR

EPMFR-00269: XBRL Footnote error retrieving report value. Report: {0}. Invalid Row ({1}) and Column ({2})

Cause: An error occurred while retrieving the report value. Invalid row and/or column reference were given.
Action: Ensure that the mapped footnote has valid row and column references to a grid.
Level: 1
Type: ERROR

EPMFR-00270: XBRL No language definition in footnote

Cause: A footnote in the report did not provide a valid language definition.
Action: Assign a language to every footnote.
Level: 1
Type: ERROR

EPMFR-00271: An unsupported version of XBRL was used. XBRL data is ignored.

Cause: The report had embedded XBRL data. However the version was unrecognized and could not be processed.
Action: Ensure that the XBRL data in the report definition is saved with the proper Financial Reports version.
Level: 1
Type: ERROR

EPMFR-00272: Instance generation failed. File name specified: {0} is invalid.

Cause: The specified filename for the instance report was null or invalid. The instance document was not generated.
Action: Provide a valid file name for the instance document.
Level: 1
Type: ERROR

EPMFR-00273: XBRL Footnote for '{0}' not properly set up

Cause: The XBRL footnote had a reference to an invalid report object.
Action: Ensure that all XBRL footnotes have valid references to a report object (grid or text).
Level: 1
Type: ERROR

EPMFR-00274: Taxonomy element '{0}' is linked to an unregistered taxonomy '{1}'

Cause: The given taxonomy element belongs to an unregistered taxonomy.
Action: Ensure that the taxonomy used within a report is registered in the taxonomy repository.
Level: 1
Type: ERROR

EPMFR-00275: Taxonomy element '{0}' has no context defined. It will not be persisted in the instance document.

Cause: A taxonomy element was mapped to data in a report, but there was no XBRL context associated with it. The element was ignored and not added to the instance document.
Action: Ensure that all mapped taxonomy elements in a report have a corresponding mapped context.
Level: 1
Type: ERROR

EPMFR-00276: Taxonomy element '{0}' has no associated report object. It will not be persisted in the instance document.

Cause: A mapped taxonomy element was mapped to an invalid report object (grid or text).
Action: Ensure that all taxonomy elements are mapped to a valid report object.
Level: 1
Type: ERROR

EPMFR-00277: Taxonomy element '{0}' has an unregistered taxonomy ('{1}'). It will not be persisted in the instance document.

Cause: A mapped taxonomy element belonged to an unregistered taxonomy. The element was ignored and not added to the instance document.
Action: Ensure that all mapped taxonomy elements in a report belong to a taxonomy that is registered in the Financial Reports system.
Level: 1
Type: ERROR

EPMFR-00278: Cannot connect to server on {0}

Cause: Connection to the specified server failed, most likely due to a Remote Method Invocation (RMI) issue.
Action: Verify that the Remote Method Invocation (RMI) service is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 1
Type: ERROR

EPMFR-00279: Unable to find appropriate Service at {0}

Cause: Connection to the specified server failed, most likely due to a Remote Method Invocation (RMI) issue.
Action: Verify that the Remote Method Invocation (RMI) service is running without errors. Also look for possible network issues. Contact Oracle Service Support if additional assistance is needed.
Level: 1
Type: ERROR

EPMFR-00280: Large imported file denied by the annotation UI

Cause: A file exceeding the AttachedFileMaxSize property limit was loaded.
Action: Reduce the file size or increase the AttachedFileMaxSize property.
Level: 1
Type: ERROR

EPMFR-00281: Cannot create a Remote Method Invocation (RMI) registry on port: {0}

Cause: Another Remote Method Invocation (RMI) registry was running at the specified port number.
Action: Verify the configuration for the Remote Method Invocation (RMI) registry to avoid conflicts.
Level: 1
Type: ERROR

EPMFR-00282: RMI (Remote Method Invocation) registry created on port: {0}

Cause: The Remote Method Invocation (RMI) registry was created on the specified port.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00283: Unable to create registry

Cause: An error occurred while attempting to establish a connection with the Remote Method Invocation (RMI) registry.
Action: Verify the configuration of the Remote Method Invocation (RMI) registry and ensure that it is running without errors.
Level: 1
Type: ERROR

EPMFR-00284: Financial Reporting Print Server started

Cause: The print server started successfully.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00285: Print server not started

Cause: An error occurred while attempting to establish a connection with the Remote Method Invocation (RMI) registry.
Action: Verify the configuration of the Remote Method Invocation (RMI) registry and ensure that it is running without errors.
Level: 1
Type: ERROR

EPMFR-00292: Element specified in the locator: {0} {1} not found.

Cause: The given taxonomy element could not be located from the given locator.
Action: Ensure that the taxonomy's locators have valid references to taxonomy elements.
Level: 1
Type: WARNING

EPMFR-00293: Cannot initialize XBRL Schema Collection

Cause: Most likely, there were no schemas in the specified XBRL Location.
Action: This message is harmless if you do not intend to use XBRL. If you do, ensure that you have created the appropriate schemas in the specified location.
Level: 1
Type: WARNING

EPMFR-00294: Invalid attempt accessing server controlled properties

Cause: The client side code tried to access a server-only controlled property.
Action: No action needed.
Level: 1
Type: ERROR

EPMFR-00295: Unable to extract OBIEE session

Cause: Attempt to get administration level session failed.
Action: Verify the administrator user configuration in OBIEE.
Level: 1
Type: ERROR

EPMFR-00297: Initialization of CredentialStore failed

Cause: The credential store could not be located or could not be initialized.
Action: Ensure that the credential store is properly configured.
Level: 1
Type: ERROR

EPMFR-00298: Failed obtaining credentials from security store for {0}

Cause: Expected credentials could not be retrieved from credential store.
Action: Verify the credentials stored in credential store.
Level: 1
Type: ERROR

EPMFR-00299: Failed obtaining credentials from security store for {0}

Cause: Expected credentials could not be retrieved from credential store.
Action: Verify credentials stored in credential store.
Level: 1
Type: ERROR

EPMFR-00301: Attempt to get undefined configuration property ({0})

Cause: A property was not defined or set. A default property was not available.
Action: Contact Oracle Support Services to obtain the correct default property value and instructions to configure it.
Level: 1
Type: ERROR

EPMFR-00303: Invalid attempt to authenticate with elevated user credentials

Cause: The configured elevated user credentials caused an exception when trying to authenticate.
Action: Check the configured elevated user credentials.
Level: 1
Type: ERROR

EPMFR-00304: Error while setting the POV for data source ID: {0}

Cause: There was a problem storing the current POV.
Action: Verify access to the repository.
Level: 1
Type: ERROR

EPMFR-00305: PDFRootDirectory {0} not created. PDFs not generated.

Cause: The folder required to create the PDF files could not be created.
Action: Create the required folder on the Print Server.
Level: 1
Type: INCIDENT_ERROR

EPMFR-00306: getObjectsById:Objects requested={0}, but objects returned is {1}

Cause: Some of the objects were not accessible.
Action: No action is required.
Level: 1
Type: WARNING

EPMFR-00307: Cannot print using printer '{0}'. The printer is either not available to the Print Server or not configured for the host computer's services.

Cause: The specified printer was not used because either it was not available to the print server, or it was not configured for the host computer's services.
Action: Ensure that the print server is installed correctly.
Level: 1
Type: ERROR

EPMFR-00308: Cannot print document file: '{0}' \n\tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.
Action: Verify that the external document link is correct.
Level: 1
Type: ERROR

EPMFR-00309: Cannot print document file: '{0}' \n\tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.
Action: Verify that the external document link is correct.
Level: 1
Type: ERROR

EPMFR-00310: Error writing external file '{0}'. It will not be included in the PDF output.

Cause: There was an error when writing the specified external file.
Action: Verify that the PDF output location is correct in the property file.
Level: 1
Type: ERROR

EPMFR-00312: Invalid attempt accessing server controlled properties

Cause: The client side code tried to access a server-only controlled property.
Action: No action needed.
Level: 1
Type: ERROR

EPMFR-00313: Invalid attempt to authenticate with elevated user credentials

Cause: The configured elevated user credentials caused exception when trying to authenticate.
Action: Check the configured elevated user credentials.
Level: 1
Type: ERROR

EPMFR-00315: Invalid user defined preferred date format ({1})

Cause: User defined date format contains invalid date format characters
Action: Update user preferences with valid a date format
Level: 1
Type: ERROR

EPMFR-00316: Custom Socket Factories loaded successfully

Cause: A status message stating that the sockets connecting to the RMI Server has successfully been established.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00317: Unable to establish port within established range

Cause: The established range of ports selected to access the RMI server are all unavailable.
Action: Either reestablish a different range with available ports, or, stop nonessential processes that are occupying the port range and then retry.
Level: 1
Type: INCIDENT_ERROR

EPMFR-00318: Custom Socket Factories could not be loaded

Cause: The configured socket factory classes could not be loaded.
Action: Check the configuration for the socket classes, and ensure that the entries are correct.
Level: 1
Type: INCIDENT_ERROR

EPMFR-00319: Book contains reports not found: {0}

Cause: Book contains reports which could not be found.
Action: Ensure that the contained report(s) exists.
Level: 1
Type: ERROR

EPMFR-00323: FRExecute has invalid cell reference '{0}'

Cause: FRExecute referenced an invalid cell.
Action: Verify that the FRExecute function's parameters are valid.
Level: 1
Type: ERROR

EPMFR-00324: FRExecute cannot generate an image for component '{0}'

Cause: FRExecute could not generate an image for the specified component.
Action: Verify that the FRExecute function's parameters are valid.
Level: 1
Type: ERROR

EPMFR-00325: FRExecute cannot generate an image for component '{0}'

Cause: FRExecute could not generate an image for the specified component.
Action: Verify that the FRExecute function's parameters are valid.
Level: 1
Type: ERROR

EPMFR-00326: FRExecute cannot generate an image for component '{0}'

Cause: FRExecute could not generate an image for the specified component.
Action: Verify that the FRExecute function's parameters are valid.
Level: 1
Type: ERROR

EPMFR-00327: Cannot replace FRExecute function with the result.

Cause: The FRExecute function could not be replaced with the result.
Action: Verify that Microsoft Word is installed on the machine where the print server is located.
Level: 1
Type: ERROR

EPMFR-00329: Error writing external file '{0}'. It will not be included in the PDF output.

Cause: There was an error when writing the specified external file.
Action: Verify that the PDF output location is correct in the property file.
Level: 1
Type: ERROR

EPMFR-00330: Error writing external file '{0}'. It will not be included in the PDF output.

Cause: Error writing the specified external file. It will not be included in the PDF output.
Action: Verify that the PDF output location is correct in property file.
Level: 1
Type: ERROR

EPMFR-00331: Cannot print document file: '{0}' \n\tError code: {1}, Last Error was: {2}

Cause: The specified document file was not printed.
Action: Verify that the external document link is correct.
Level: 1
Type: ERROR

EPMFR-00332: Cannot print document file: '{0}' \n\tError code: {1}, Last Error was: {2}

Cause: The specified document file was not printed.
Action: Verify that the external document link is correct.
Level: 1
Type: ERROR

EPMFR-00334: Cannot print report '{0}' within Book '{1}'. Make sure the report exists in the repository.

Cause: The specified report was not printed within the specified book..
Action: Ensure that all external object links in book are correct, that the book is valid, and that the report exists in the repository.
Level: 1
Type: ERROR

EPMFR-00336: Could not find data source ID: {0} {1}. Attempting to find a data source with the same name.

Cause: A connection to the data source could not be made by using the stored data source ID.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: WARNING

EPMFR-00337: Could not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source ID.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: WARNING

EPMFR-00338: Could not find data source ID: {0} {1}. Failed to create a new data source for it.

Cause: A connection to the data source could not be made by using the stored data source ID or name; as a result, a new data source was not created.
Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 1
Type: ERROR

EPMFR-00339: Usage: ManageUserPov Mode ConfigFile\n\tMode = import | export | delete\n\tConfigFile = configuration file name such as ManageUserPov.properties

Cause: An instruction about how to use the ManageUserPov utility was provided.
Action: Follow the instructions of the message.
Level: 1
Type: ERROR

EPMFR-00340: Error loading config file: {0}

Cause: The specified configuration file did not exist or was not accessible.
Action: Supply a valid and accessible file name as a parameter.
Level: 1
Type: ERROR

EPMFR-00341: Missing AdminUser

Cause: The configuration file did not have an administrative user (AdminUser) specified.
Action: In the configuration file, specify a user (AdminUser) with Administrator access.
Level: 1
Type: ERROR

EPMFR-00342: Cannot print document file: '{0}' \n\tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.
Action: Verify that the external document link is correct.
Level: 1
Type: ERROR

EPMFR-00344: Setting BaseWebApp in HIT registry to: "

Cause:
Action:
Level: 1
Type: NOTIFICATION

EPMFR-00345: Setting BaseWebApp in HIT registry to: "

Cause:
Action:
Level: 1
Type: NOTIFICATION

EPMFR-00346: Could not get version information from the file system

Cause: The version.xml file could not be loaded, or there was an error parsing the file.
Action: Make sure version.xml exists under common/epmstatic/wspace/SmartView/ on the server.
Level: 1
Type: NOTIFICATION

EPMFR-00347: The system cannot access the Print Server at this time. Try again later or confirm the Print Server name.

Cause: The specified Print Server is not accessible.
Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 1
Type: WARNING

EPMFR-00348: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible
Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 1
Type: WARNING

EPMFR-00349: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible
Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 1
Type: WARNING

EPMFR-00350: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible
Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 1
Type: WARNING

EPMFR-00351: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible
Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 1
Type: WARNING

EPMFR-00352: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible
Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 1
Type: WARNING

EPMFR-00353: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible
Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 1
Type: WARNING

EPMFR-00354: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible
Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 1
Type: WARNING

EPMFR-00355: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible
Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 1
Type: WARNING

EPMFR-00356: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible
Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 1
Type: WARNING

EPMFR-00357: The generated output PDF file is not accessible.

Cause: The generated output PDF file may not exist due to product configuration or system access issues.
Action: Verify product configuration and that the PDF output file and path are correct. Verify that access to the output destination is available.
Level: 1
Type: ERROR

EPMFR-00358: A property did not initialize due to a missing resource.

Cause: The system is initializing and some resources do not exist at this stage of initialization
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00359: Unable to get Base WebApp from the registry

Cause: The Registry may not be available.
Action: Check the logs and the availability of the Registry server.
Level: 1
Type: NOTIFICATION

EPMFR-00360: Unable to authenticate user.

Cause: User ID or password are incorrect, user session may have expired, or security provider is unavailable.
Action: The user needs to verify username and password. If the user session expired, have the user log off and re-authenticate. If user information is valid, the administrators should verify that all systems are running and accessible.
Level: 1
Type: WARNING

EPMFR-00361: Unable to authenticate user.

Cause: User ID or password are incorrect, user session may have expired, or security provider is unavailable.
Action: The user needs to verify username and password. If the user session expired, have the user log off and re-authenticate. If user information is valid, the administrators should verify that all systems are running and accessible.
Level: 1
Type: WARNING

EPMFR-00362: Unable to authenticate user.

Cause: User ID or password are incorrect, user session may have expired, or security provider is unavailable.
Action: The user needs to verify username and password. If the user session expired, have the user log off and re-authenticate. If user information is valid, the administrators should verify that all systems are running and accessible.
Level: 1
Type: WARNING

EPMFR-00363: Unable to authenticate user.

Cause: An error occurred within the security service provider.
Action: Review logs for Shared Services and security providers for the cause of the exception.
Level: 1
Type: WARNING

EPMFR-00364: User authentication failed. Unable to connect to data source.

Cause: User information is invalid, user session expired, user account status is not current, or data source is not available.
Action: User must resubmit correct authentication information or repair account status. Also verify that all data sources are available.
Level: 1
Type: WARNING

EPMFR-00365: User authentication information is invalid. Unable to connect to data source.

Cause: User information is invalid or user account status is not current.
Action: User must resubmit correct authentication information or repair account status.
Level: 1
Type: WARNING

EPMFR-00366: Unable to connect to data source or remote server.

Cause: An error has occurred due to the availability of a remote service or data source.
Action: Verify that all connections are available and that all remote services and data sources are available.
Level: 1
Type: ERROR

EPMFR-00367: No applications were found in {0}.

Cause: The data source that the user accessed does not return a list of applications.
Action: Verify that the accessed data source is operational and contains applications accessible to the user.
Level: 1
Type: ERROR

EPMFR-00368: Unable to connect to the data source {0}: {1}

Cause: An error occurred while connecting to the data source.
Action: Verify that the data source is available and that the user has access. Check the logs of the data source provider.
Level: 1
Type: ERROR

EPMFR-00369: Unable to connect to data source. {0}: {1}

Cause: An error occurred while connecting to the data source.
Action: Verify that the data source is available and that the user has access. Check the logs of the data source provider.
Level: 1
Type: ERROR

EPMFR-00370: An error occurred while adjusting member selections via a data source connection.

Cause: An error occurred while adjusting member selections via a data source connection.
Action: Verify that the data source is available and that the user has valid authorization and rights. View the logs of the data source for additional information.
Level: 1
Type: ERROR

EPMFR-00371: An object could not be retrieved from the repository.

Cause: The likely cause of an object not being retrieved may be due to a user who has not yet used a user POV for the given data source.
Action: User Point of View must be established for the data source. Review the logs and accessibility of the Shared Services provider
Level: 1
Type: NOTIFICATION

EPMFR-00372: An error occurred while setting the property {0} with the value set to {1}

Cause: The error is likely to have occurred while accessing Shared Services due to permissions, authentication, or connection issues.
Action: Review the logs for Shared Services and verify that all systems are operational and accessible.
Level: 1
Type: ERROR

EPMFR-00373: An error occurred while attempting to create a session with the repository.

Cause: An error occurred with the system repository
Action: Verify that all systems are running and available. Check the logs for errors.
Level: 1
Type: ERROR

EPMFR-00374: An unexpected error occurred.

Cause: An unexpected error occurred and requires further evaluation.
Action: Verify that all systems are operational. Gather logs from all systems and contact Support for further assistance.
Level: 1
Type: INCIDENT_ERROR

EPMFR-00375: An exception occurred in the Repository with the message: {0}

Cause: An error occurred in the Repository.
Action: Verify that all systems are running and accessible. Check the logs for errors connecting to the repository and with the repository related logs.
Level: 1
Type: ERROR

EPMFR-00376: An error occurred while attempting to access the prompts from the design manager.

Cause: The error is likely due to a connection issue with the data source.
Action: Verify that all data sources accessed by the report are available to the user.
Level: 1
Type: ERROR

EPMFR-00377: An error occurred while attempting to access the Repository.

Cause: The most plausible cause of the error is likely due to an access issue with the Repository.
Action: Verify that the Repository is available to the Report Server.
Level: 1
Type: ERROR

EPMFR-00378: An error occurred while building the user POV.

Cause: The cause of the error is likely due to a connection issue.
Action: Verify that all the data sources are available to the user and that all other systems are running and available.
Level: 1
Type: ERROR

EPMFR-00379: An error occurred while accessing the Report Server or one of the supporting systems.

Cause: An error occurred while accessing the Report Server or one of the supporting systems.
Action: Review the server side logs and verify that all systems are running and accessible.
Level: 1
Type: ERROR

EPMFR-00380: An error occurred while attempting to get the book's user POV.

Cause: The error is likely due to a connection issue with the data source.
Action: Review all system logs and verify that all data sources accessed by the POV are available to the user.
Level: 1
Type: ERROR

EPMFR-00381: Failed Authentication via Security Agents

Cause: Authentication information passed from the Security Agent failed to authorize.
Action: Verify configuration with Security Agent, Shared Services, and Financial Reporting.
Level: 1
Type: WARNING

EPMFR-00382: User successfully authenticated via Security Agent.

Cause: A successful logon occurred via a configured Security Agent.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00383: An error occurred while accessing an annotation attachment.

Cause: An error will occur when the attachment doesn't exist or is not accessible.
Action: Verify that the attachments exist within the report and that all systems are operational and accessible.
Level: 1
Type: ERROR

EPMFR-00384: An issue occurred while refreshing the data sources via the Data Source Connection Manager.

Cause: The data source stored in the Data Source Connection Manager is invalid, does not exist, or is not accessible.
Action: Verify the list of data sources from the Data Source Connection Manager and ensure all data sources are accessible to the user.
Level: 1
Type: WARNING

EPMFR-00385: The following error occurred while accessing the book objects: {0}

Cause: The object requested is not accessible or does not exist in the repository.
Action: Verify that all objects in the book are available and accessible to the user.
Level: 1
Type: ERROR

EPMFR-00386: An error occurred while saving the new annotation.

Cause: An error occurred while saving the new annotation during snapshot creation.
Action: There was an issue retrieving the existing annotation for duplication during snapshot creation. Refer to the annotation logs for additional information.
Level: 1
Type: ERROR

EPMFR-00387: An error occurred while marshalling the annotation xml.

Cause: An error occurred while marshalling the annotation xml.
Action: Refer to the annotation logs for additional information.
Level: 1
Type: ERROR

EPMFR-00388: An error occurred while updating the annotation.

Cause: An error occurred while updating the annotation.
Action: There was an issue updating the existing annotation. Refer to the annotation logs for additional information.
Level: 1
Type: ERROR

EPMFR-00389: An issue occurred while connecting to the data source. {0}: {1}

Cause: A connection to the data source was unsuccessful and may have been caused by incorrect user credentials, an invalid data source name, or a connection issue to the specified data source.
Action: Verify that all systems are running and that the credentials for connecting to the data source are correct.
Level: 1
Type: WARNING

EPMFR-00390: An error occurred while connecting to the data source. {0}: {1}

Cause: A connection to the data source was unsuccessful and may have been caused by incorrect user credentials, an invalid data source name, a connection issue to the specified data source, or an unexpected error.
Action: Verify that all systems are running and that the credentials for connecting to the data source are correct.
Level: 1
Type: ERROR

EPMFR-00391: An error occurred while connecting to the data source. {0}: {1}

Cause: A connection to the data source was unsuccessful and may have been caused by incorrect user credentials, an invalid data source name, a connection issue to the specified data source, or an unexpected error.
Action: Verify that all systems are running and that the credentials for connecting to the data source are correct.
Level: 1
Type: ERROR

EPMFR-00392: User successfully authenticated via Oracle Access Manager.

Cause: A successful logon occurred via the Oracle Access Manager.
Action: No action is required.
Level: 1
Type: NOTIFICATION

EPMFR-00393: The following message occurred while performing a batch operation: {0}

Cause: Review the complete log message statement to determine the cause of this message.
Action: Review the complete log message statement to determine the cause of the message and further action. Review other log messages for potential issues and actions to take.
Level: 1
Type: WARNING

EPMFR-00394: The following message occurred while performing a batch operation: {0}

Cause: Review the complete log message statement to determine the cause of this message.
Action: Review the complete log message statement to determine the cause of the message and further action. Review other log messages for potential issues and actions to take.
Level: 1
Type: WARNING

EPMFR-00395: An error occurred while accessing object information for Application Name, {0), and Data Source Type, {1} from the repository.

Cause: The input parameters may be invalid or do not exist when called from the repository. Also access to the repository may not be available.
Action: Verify the input parameters are correct and that all systems are operational and available.
Level: 1
Type: ERROR

EPMFR-00396: An error occurred while retrieving the chart image with the file name, {0}

Cause: The specified chart image was not obtained from the server for reasons that may include file access or the file name and type were not specified.
Action: Verify that file access is available on the system drive and that the file name and type are valid.
Level: 1
Type: ERROR

EPMFR-00397: An error occurred while closing a dialog window. View the systems logs for more information.

Cause: To determine the cause of the error review the log files for other errors and events leading to this error.
Action: Contact support for assistance in determining the cause of the error as it may be related to another system issue.
Level: 1
Type: ERROR

EPMFR-00398: ReportServer object is not properly initialized. Unable to check access to a report.

Cause: The connection to the server was disrupted.
Action: Log out and try again.
Level: 1
Type: ERROR

EPMFR-00399: Could not get version information from the file system

Cause: The version.xml file could not be loaded, or there was an error parsing the file.
Action: Make sure version.xml exists under common/epmstatic/wspace/SmartView/ on the server.
Level: 1
Type: NOTIFICATION