35 EPMBPMUI-00101 to EPMBPMUI-01804

EPMBPMUI-00101: Initializing configuration factory

Cause: The application is initializing its configuration factory at application startup.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00102: Terminating configuration factory

Cause: The application is shutting down its configuration factory at application shutdown.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00201: Parameter "{0}" has value "{1}"

Cause: Reports the value of a configuration factory parameter during startup.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00204: Failed to initialize the class {0} with its default constructor.

Cause: The configuration factory could not create a configuration class.

Action: Consult the application configuration log for further details.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00205: Failed to instantiate the class {0}

Cause: The configuration factory could not create a configuration class.

Action: Consult the application configuration log for further details.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00206: Failed to initialize the configuration class.

Cause: The configuration factory could create, but could not initialize, a configuration class.

Action: Consult the application configuration log for further details.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00207: Failed to resolve the class {0}

Cause: The configuration factory could not find a named class definition to create.

Action: Consult the application configuration log for further details.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00208: Failed to initialize the configuration class.

Cause: The configuration factory could create, but could not initialize, a configuration class.

Action: Consult the application configuration log for further details.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00209: Configuration class application parameter "{0}" was not specified in web.xml

Cause: A required parameter for the configuration factory was not specified in the application configuration.

Action: Verify that the named parameter is present in the file web.xml, and that any customizations of this file did not remove it.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00210: The configuration Factory's configuration instance was null. There was an initialization error during application startup.

Cause: Due to previous errors, the configuration factory was not able to create a configuration instance.

Action: Consult the application configuration logs for previous errors.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00211: There was an error during configuration instance termination.

Cause: The configuration factory was unable to terminate a configuration instance.

Action: This error is not immediately fatal, but may result in a memory leak over time if repeated.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00212: The Configuration instance was not initialized. Ensure the context parameter "{0}" is set correctly, and check for errors during application startup.

Cause: The configuration factory could not initialize its configuration instance due to a missing parameter in web.xml.

Action: Verify that the named parameter is present in the file web.xml, and that any customizations of this file did not remove it.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00402: There was an error getting the context configuration parameter: {0}.

Cause: The application was unable to load the path to its context configuration from the configuration parameter BpmContextConfig.

Action: Verify that application configuration completed successfully, and that any customizations to this application did not remove this parameter.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00403: There was an error getting the common install version number.

Cause: The application was unable to determine the version number of the common installer.

Action: Verify that the file EPM_ORACLE_HOME/common/config/11.1.2.0/installer_version.xml exists, is accessible, and is a valid XML file.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00501: Failed to load and parse {0}

Cause: The configuration class failed to load the named file.

Action: Consult the application configuration log for further errors.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00502: Failed to initialize the authentication helper

Cause: The configuration class could not initialize the security system due to previous errors.

Action: Consult the application security log for previous errors.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00503: The property "{0}" has value "{1}"

Cause: Reports the named property and value.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00601: Loaded properties from {0}

Cause: Reports that the configuration class loaded its application properties from the named EPM Registry component.

Action: No action is requred.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00602: Failed to load properties from {0}

Cause: The configuration class could not load its configuration properties from the named EPM Registry component.

Action: Verify connection to the EPM Registry and EPM Registry contents.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00603: Loaded properties from {0}[{1}={2}]

Cause: Reports that the configuration class loaded its application properties from the named EPM Registry component.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00701: There was an error during authentication.

Cause: Reports a generic error during authentication. This message is a generic message for the user interface which obscured the actual security system error.

Action: Consult the application security log for the full error details.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00702: Intercepting request for authentication: {0}

Cause: The security system is intercepting the named request for an authentication check.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00703: Intercepting with static logon page: {0}

Cause: The security system is using the named logon page to prompt for user credentials.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00801: Redirecting request for authentication: {0}

Cause: The security system is redirecting the named request to the main application logon page.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00901: Logon bean class name was not specified in web.xml.

Cause: The name of a security class implementation was not found in the application configuration.

Action: This is not a fatal error; a default implementation will be used.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00902: Using the default logon bean implementation.

Cause: The security system will use a default security class implementation.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00903: There was an error instantiating the logon bean.

Cause: The security system was unable to instantiate the security class implementation.

Action: Consult the application security log for previous errors from the security API

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00904: The Logon bean class does not have a default public constructor.

Cause: The security class implementation does not have a required constructor.

Action: Verify that the application deployment is not damaged and that all service fixes were applied properly.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00905: Logon bean Java class is not resolvable.

Cause: The security system could not resolve the class name of the security class implementation.

Action: Verify that any customizations to web.xml did not remove or damage this parameter.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00906: Failed to initialize the logon bean.

Cause: The security system could not initialize the security class implementation.

Action: Consult the application security log for prior errors from the security API.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-00907: There was an error during logon bean initialization.

Cause: The security system could not initialize the security class implementation.

Action: Consult the application security log for prior errors from the security API.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01001: Blocking request: {0}

Cause: The named request has been blocked by the security system.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01201: The CSS mode is: {0}

Cause: Reports the deployment mode of the security system.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01202: Failed to determine CSS mode. Will use EPM mode.

Cause: Indicates that the security system could not determine its deployment mode and is using the default mode.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01203: Initializing security framework

Cause: Indicates that the security class is initializing the security API/

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01204: Security framework was initialized successfully.

Cause: Indicates that the security class initialized the security API without error.

Action: No action was required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01205: There was an error initializing security framework.

Cause: Indicates that the security class failed to initialize the security API.

Action: Consult the application security logs for prior error messages.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01207: This session will be invalidated.

Cause: Indicates that an already-extant session is being invalidated during logon to be replaced with a new session.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01208: Logging on user {0} at {1}

Cause: Records a successful user logon for the named user at the given time.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01210: There was an error determining if direct logon is permitted. Direct logons will be denied.

Cause: The security system was unable to determine if direct logons are permitted even if an SSO agent is enabled. Such logons will be disallowed.

Action: Verify that the application was deployed correctly and that any customization to its configuration did not remove any parameters.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01211: User's password is about to expire.

Cause: Informative message at logon indicating the the current user's password will soon expire.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01212: Failed to store user in session

Cause: The security system failed to create a session for an authenticated user.

Action: Consult the application security log for further details.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01213: Failed to retrieve user from session

Cause: The security system could not verify a user from an existing sesison.

Action: Consult the application security log for further details.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01214: Terminating session for user: {0}

Cause: Indicates that a user session is terminated.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01216: Session created at: {0}

Cause: Gives the creation time of a terminated user session.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01217: There was an error during Fusion logon:

Cause: Reports an error from the Fusion Middleware logon system.

Action: Consult the application security log for further details.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01301: Attempt to create a J2EE session on an unauthorized request path. The attempt was blocked. The request path was: {0}

Cause: An unauthorized request attempted to create an application session and was blocked in the attempt.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01501: read parameter name: {0} value: {1}

Cause: Indicates a preferences system configuration value read during startup.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01502: There was an error during preferences system initialization.

Cause: Reports an error during preferences initialization.

Action: Consult the application preferences log for further details.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01503: Preferences servlet initialized

Cause: Indicates that the preferences servlet is initialized.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01504: There was an error saving preferences.

Cause: Indicates an error saving preferences for a given user.

Action: Consult both the application security and applicaion preferences logs for more details.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01505: There was an error saving preferences for multiple users.

Cause: Indicates an error saving preferences for multiple users.

Action: Consult both the application security and applicaion preferences logs for more details.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01506: Ther was an error during preferences system shutdown.

Cause: Reports an error during preference system shutdown during application shutdown.

Action: The application has shut down, so no action is possible.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01801: There was an error checking the client debug setting: all requests blocked.

Cause: The security system was unable to determine if client debugging requests are permitted; these requests will be blocked by default.

Action: Verify that application configuration completed successfully, and that any customizations to this application did not remove this parameter.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01802: Permitting request: {0}

Cause: The security system is permitting the named client debugging request.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01803: Blocking request: {0}

Cause: The security system is blocking the named client debugging request.

Action: No action is required.

Level: 32

Type: ERROR

Impact:

EPMBPMUI-01804: You do not have access to see this page because client debugging is disabled. Contact your system administrator.

Cause: This message indicates that the request was blocked because client debugging is enabled. A system administrator must enable this setting for the application.

Action: Contact your system administrator.

Level: 32

Type: ERROR

Impact: