EJPFD: com.ibm.wps.services.resources.ServicesMessages

EJPFD0001E

Attempt to read object after end of input ({0}).

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0002E

An object of type {0} cannot be constructed from {1}.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0005E

RequestDispatcher not found for {0}.

Explanation

An internal error occurred. The RequestDispatcher which is required to include JSP's is not available.

User response

See the log file for more details.

EJPFD0006E

Cannot find object {0} in JNDI context {1}.

Explanation

The object was not found in the context of the Java Naming and Directory Interface (JNDI) of the WebSphere Application server instance. The error can be caused by a incorrectly specified JNDI context, an incorrect JNDI context configuration of the object, or a previous error that prevented a successful JNDI registration.

User response

Verify the JNDI name provided and the JNDI resource environment configuration of the application in the administrative console of WebSphere Application Server. Check the SystemOut.log or SystemErr.log for additional information about the error. If the SystemOut.log or SystemErr.log contains entries indicating a timestamped FFDC log entry was generated, also review that FFDC log entry (there may be more than one).

EJPFD0007E

Failed to initialize JNDI context {0}.

Explanation

The context of the Java Naming and Directory Interface could not be initialized successfully.

User response

Verify the context root specification and see the explanation of the NamingException for more details.

EJPFD0008W

Context parameter {0} ignored.

Explanation

The specified context parameter was incorrect and will be ignored.

User response

Verify and correct the context parameter (key) in the property file of the naming service.

EJPFD0009E

NavigatorService is unable to load supported markups.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0010E

An unexpected exception occurred.

Explanation

An unexpected internal error occurred.

User response

See the log file for more details.

EJPFD0011E

Error loading filter {0}.

Explanation

The specified filter service could not be initialized successfully.

User response

Verify and correct the content of the property file for the portal filter service.

EJPFD0012E

Error loading filter list. Filter not found: {0}.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0015E

RegistryService is unable to initialize Bucket {0} with class {1} Stack trace follows .....

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0016E

Initialization of service failed.

Explanation

A service was requested to be initialized and the operation failed.

User response

See the log file for more details.

EJPFD0017E

Could not initialize engine: {0}.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0018E

Invalid property format: {0}.

Explanation

The property file for the specified service has an invalid format.

User response

Correct the format of the property file for the specified service and repeat the action.

EJPFD0019E

Could not send Event PORTLET_SETTINGS_EVENT.

Explanation

The portlet container could not send the PORTLET_SETTINGS_EVENT to a portlet successfully.

User response

See the log file for more details.

EJPFD0020E

Error while invoking a system event handler.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0021E

Error while invoking an event handler.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0022W

Unable to initialize cluster aware cache.

Explanation

This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.

User response

Correction of the condition is recommended.

EJPFD0023W

Unable to instantiate an event handler.

Explanation

This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.

User response

Correction of the condition is recommended.

EJPFD0024W

The value for property key ''{0}'' is not a number. Using default value of ''{1}'' instead.

Explanation

The value for the property key has to be a numeric value.

User response

If the default value meets your requirement, no further action needs to be taken. Otherwise correct the property value and retry your action.

EJPFD0025W

The value ''{0}'' for property key ''{1}'' is not valid. Using default value ''{2}'' instead.

Explanation

A property key has an invalid value. A default value will be used instead.

User response

If the default value meets your requirement, no further action needs to be taken. Otherwise correct the property value and retry your action.

EJPFD0026E

Virtual Portal mapping service was unable to retrieve cache ''{0}''.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0027E

Virtual Portal mapping service was unable to get the Virtual Portal mapping information for ''{0}'' from the database.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0028E

Virtual Portal mapping service was unable to retrieve a UserWorkArea instance using a JNDI lookup.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0029E

Unable to set Virtual Portal ID in current context.

Explanation

An exception occurred while setting the Virtual Portal ID in the current UserWorkArea.

User response

See the log file for more details.

EJPFD0031E

An error has occurred in the AsynchBeans layer of WebSphere Application Server.

Explanation

An unexpected internal error occurred in the AsynchBeans layer of the WebSphere Business Integration Server Foundation component.

User response

Please check the nested exception.

EJPFD0032E

Error executing a job object in the WorkManager.

Explanation

An error has occurred while executing a job object in the Thread-based WorkManager implementation.

User response

See the log file for more details.

EJPFD0033I

Exception was thrown from the AsynchBeans layer of WebSphere Application Server.

Explanation

A nested exception was received from the AsynchBeans layer of WebSphere Application Server.

User response

See the log file for more details.

EJPFD0034W

Error while creating WorkManager ''{0}''. Skipping this WorkManager.

Explanation

This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.

User response

Correction of the condition is recommended.

EJPFD0035E

Error while creating WorkArea Partition with name ''{0}''.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0036E

The default WorkManager could not be created. Service initialization failed.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0037W

WorkManager ''{0}'' has been requested, but could not be found. Using default WorkManager instead.

Explanation

The WorkManager was not found in the context of the JNDI directory.

User response

If the default WorkManager configuration meets your requirement, no further action needs to be taken. Otherwise verify and correct the Portal WorkManager configuration service properties file and WebSphere Application Server WorkManager configuration.

EJPFD0038E

RegistryService configuration invalid: No class defined for bucket {0}.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0039E

Configuration parameter {0} is missing in properties file.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0040E

Factory {0} is not defined in properties file.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0041E

Initialization of CacheManagerService failed.

Explanation

This is an error message. The portal system cannot handle this condition without failing.

User response

Correction of the condition is required.

EJPFD0042W

Class {0} did not return a valid CacheFactory. Entry is being ignored.

Explanation

This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.

User response

Correction of the condition is recommended.

EJPFD0043W

System returned {0} while trying to instantiate CacheFactory {1}. The configuration entry is being ignored.

Explanation

This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.

User response

Correction of the condition is recommended.

EJPFD0045W

Object name {0} is already defined. System is returning a default Cache implementation.

Explanation

This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.

User response

Correction of the condition is recommended.

EJPFD0047E

The object supplied is no valid object ID [{0}].

Explanation

This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.

User response

Correction of the condition is recommended.

EJPFD0048E

Transient object IDs cannot be serialized for a global scope.

Explanation

This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.

User response

Correction of the condition is recommended.

EJPFD0049W

Portal home directory was not specified, no information about interim fixes and fix packs is available!

Explanation

The configuration parameter 'wps.home' could not be resolved. This parameter is necessary to load information about Portal.

User response

Make sure that this parameter is configured in Portal Configuration Service.

EJPFD0050W

An exception occurred while checking installation history, no information about interim fixes and fix packs is available!

Explanation

This is a warning message. An abnormal condition has been detected. The portal system is able to handle this condition without failing.

User response

See the nested exception for more details on this problem and how to resolve it.

EJPFD0051I

The following fix packs have been installed: {0}

Explanation

This is an informational message listing the fix packs that have been applied after initial installation of the product.

User response

No action needs to be taken.

EJPFD0052I

No fix packs have been installed.

Explanation

This is an informational message indicating that no fix packs have been applied after initial installation of the product.

User response

No action needs to be taken.

EJPFD0053I

The following interim fixes have been installed: {0}

Explanation

This is an informational message listing the interim fixes that have been applied after initial installation of the product.

User response

No action needs to be taken.

EJPFD0054I

No interim fixes have been installed.

Explanation

This is an informational message indicating that no interim fixes have been applied after initial installation of the product.

User response

No action needs to be taken.

EJPFD0055E

Unable to access traceService MBean.

Explanation

A problem occurred when accessing the traceService MBean of Application Server.

User response

See the log file for more details.

EJPFD0056W

The file {0} could not be created.

Explanation

The file given in the message could not be created in the local file system.

User response

See the nested exception for more details on this problem and how to resolve it.

EJPFD0057E

Unique name {0} is already defined in a different Virtual Portal. The ID of that Virtual Portal is {1}.

Explanation

Unique names share the same Virtual Portal scope as their corresponding resources. Also unique names must be unique within their scope. In this case the unique name was supposed to be assigned to a resource that is shared across Virtual Portal boundaries. However the very same unique name already exists in the Virtual Portal that is specified in the error message. To learn more about the Virtual Portal scope of resources refer to the WebSphere Portal Information Center.

User response

A different unique name should be chosen.

EJPFD0058E

The new object type [{1}] that is supposed to be created, cannot be registered, because a different object type [{2}] for the same name or ordinal [{0}] already exists.

Explanation

The new object type cannot be registered, because this type would clash with an existing object type.

User response

A different pair of ordinal value and object type name should be used.

EJPFD0059E

An unknown error occurred when reading the JNDI name mapping.

Explanation

During the initialization of the JNDI name mapping for public portal services an error occurred.

User response

See the log file for more details.

EJPFD0060E

The distributed cache {0} could not be invalidated.

Explanation

The distributed cache name given in the message could not be invalidated.

User response

See the nested exception for more details on this problem and how to resolve it.

EJPFD0061E

The distributed cache {0} could not be cleared.

Explanation

The distributed cache name given in the message could not be cleared.

User response

See the nested exception for more details on this problem and how to resolve it.

EJPFD0062I

The following fixes have been installed: {0}

Explanation

This is an informational message listing the interim fixes that have been applied after initial installation of the product.

User response

No action needs to be taken.

EJPFD0063E

Initialization of cache {0} failed.

Explanation

The cache mentioned in the error message cannot be initialized due to an error condition.

User response

See the log file for nested exceptions with more details on the error condition.

EJPFD0064E

Initialization of a service (implementation name: {0}) failed.

Explanation

The service was requested to be initialized and the initialization failed due to an error condition that is reported in the log file.

User response

Check the SystemOut.log or SystemErr.log for additional information about the error. If the SystemOut.log or SystemErr.log contains entries indicating a timestamped FFDC log entry was generated, also review that FFDC log entry (there may be more than one). Please note that the filenames listed above for the log files are the defaults. Your deployment may have configured these to be different than the defaults, or to be in non-default folders in the filesystem.

EJPFD0065E

SiteAnalyzer logger {0} cannot be initialized.

Explanation

An attempt to initialize the SiteAnalyzer logger failed due to an error condition that is reported in the log files.

User response

See the log file for more details on the nested error condition.

EJPFD0066E

The dispatcher call to template {0} failed.

Explanation

The web request cannot be dispatched to the mentioned template due to an error condition that is reported in the log files.

User response

Check the SystemOut.log or SystemErr.log for additional information about the error. If the SystemOut.log or SystemErr.log contains entries indicating a timestamped FFDC log entry was generated, also review that FFDC log entry (there may be more than one). Please note that the filenames listed above for the log files are the defaults. Your deployment may have configured these to be different than the defaults, or to be in non-default folders in the filesystem.

EJPFD0067I

The following feature packs have been installed: {0}

Explanation

This is an informational message listing the feature packs that have been installed.

User response

No action needs to be taken.

EJPFD0068I

No feature packs have been installed.

Explanation

This is an informational message indicating that no feature packs have been installed.

User response

No action needs to be taken.

EJPFD0069E

Unable to get ContentMappingHome interface of service.

Explanation

The back-end database is unavailable.

User response

Make sure back-end database is up and running.

EJPFD0070E

Initialisation of ContentMappingInfoHome interface failed.

Explanation

Service maybe unavailable.

User response

See the log file for more details.

EJPFD0071E

Clearing content mapping of resource {0} failed.

Explanation

There could be several reasons like missing content mapping or missing access rights for content mapping.

User response

None. Leave clearing the content mapping to the clean up daemon.

EJPFD0072E

Service lookup of service {0} failed.

Explanation

Service is unavailable.

User response

Make sure that the service is running.

EJPFD0073W

Getting a content mapping for path {0} failed.

Explanation

There could be several reasons like missing content mapping or missing access rights for content mapping.

User response

See the log file for more details.

EJPFD0074E

Resolving an ambiguous longest path match for a given content resource failed.

Explanation

A ModelException occurred when trying to resolve an ambiguous longest path match for a given content resource.

User response

See the log file for more details.

EJPFD0075W

Cannot retrieve provider for content resource topology.

Explanation

An exception occurred when trying to get a provider for content resource topology.

User response

See the log file for more details.

EJPFD0076E

{0} occurred when migrating content mappings.

Explanation

An exception occurred when trying to migrate content mappings.

User response

See the log file for more details.

EJPFD0077E

{0} occurred when reporting content mapping creation during migration.

Explanation

An exception occurred when trying to create a content mapping during migration.

User response

See the log file for more details.

EJPFD0078E

Object with resource id {0} was already committed.

Explanation

Object was already committed.

User response

See the log file for more details.

EJPFD0079I

Asynchronous page layout refresh started for page layout template "{0}".

Explanation

An asynchronous task has been started reloading the page layout information for all pages associated with the given page layout template.

User response

The completion of this task will be indicated by an "Asynchronous page layout refresh completed" message.

EJPFD0080I

Asynchronous page layout refresh completed for page layout template "{0}".

Explanation

The asynchronous task reloading the page layout information for all pages associated with the given page layout template has completed.

User response

None.

EJPFD0081E

Asynchronous page layout refresh failed for page layout template "{0}".

Explanation

The asynchronous task reloading the page layout information for all pages associated with the given page layout template has completed.

User response

See the logs for details.

EJPFD0082I

Asynchronous IWidget Definition refresh started.

Explanation

An asynchronous task has been started reloading IWdiget Definition information.

User response

The completion of this task will be indicated by an "Asynchronous IWidget Definition refresh completed" message.

EJPFD0083I

Asynchronous IWidget Definition refresh completed.

Explanation

The asynchronous task reloading IWdiget Definition information has completed.

User response

None.

EJPFD0084E

Asynchronous IWidget Definition refresh failed.

Explanation

The asynchronous task reloading IWdiget Definition information has completed.

User response

See the logs for details.

EJPFD0085I

Report started at {0}.

Explanation

An asynchronous execution report was started.

User response

None.

EJPFD0086I

Report completetd at {0}.

Explanation

An asynchronous execution report was completed.

User response

None.

EJPFD0087I

Object {0} processed successfully.

Explanation

The given object was processed successfully.

User response

None.

EJPFD0088E

The initialization of the asynchronous refresh page layout task failed.

Explanation

This task reloads the page layout information for all pages associated with the given page layout template.

User response

See the log for more details.

EJPFD0089E

The initialization of the asynchronous refresh iwidget definitions task failed.

Explanation

This task reloads IWdiget Definition information.

User response

See the log for more details.

EJPFD0090I

Number of processed items: {0}.

Explanation

Number of items processed while executing an asynchronous task.

User response

None.

EJPFD0091I

The following IWidgets URLs have been registered: {0}.

Explanation

The given iWidgets URLs have been registered. Corresponding IWidget Wrapper portlet clones have been created.

User response

None.

EJPFD0092W

The execution of an asynchronous page layout template refresh operation for page {0} failed due to: {1}.

Explanation

The asynchronous task skipped the given page. The page has not been modified.

User response

See the log for more details.

EJPFD0093W

The execution of an asynchronous iwidget refresh operation for IWidget {0} failed due to: {1}.

Explanation

The asynchronous task skipped the given IWidget Wrapper portlet. The IWidget Wrapper portlet has not been modified.

User response

See the log for more details.

EJPFD0094W

The mandatory task invocation parameter {0} is missing.

Explanation

The task was called without specifying the required parameters.

User response

See the InfoCenter for details on required parameters for the given task.

EJPFD0095W

{0} is not a valid value for parameter {1}.

Explanation

The task was called with an invalid parameter value.

User response

See the InfoCenter for details on supported task parameter values.

EJPFD0096E

Object with resource id {0} cannot be removed, since it is a system content mapping.

Explanation

System content mappings cannot be deleted manually as they are maintained by the system as long as the given page is managed in WCM.

User response

See the log file for more details.

EJPFD0097E

No theme was found to render the page. Navigate to Administration and assign a working theme to restore full function to your site.

Explanation

The theme assigned to this page either does not exist or is not started up. The theme currently showing is a fallback.

User response

Make sure the theme exists and is activated. Or navigate to Administration and assign a working theme to the affected pages.

EJPFD0098E

The content mapping information could not be updated.

Explanation

The given object was not processed successfully. All updates have been rolled back.

User response

None.

EJPFD0099E

The content mapping information could not be updated due to repeated usage of resource path {0}

Explanation

The given object was not processed successfully. All updates have been rolled back.

User response

None.

EJPFD0100E

The content mapping information could not be updated due to repeated usage of resource ID {0}

Explanation

The given object was not processed successfully. All updates have been rolled back.

User response

None.

EJPFD0101E

The content mapping information could not be updated due to multiple default mappings being used.

Explanation

The given object was not processed successfully. All updates have been rolled back.

User response

None.

EJPFD0102E

The content mapping information could not be updated due to multiple default mappings being used.

Explanation

The given object was not processed successfully. All updates have been rolled back.

User response

None.

EJPFD0103E

The given content path was not found in the current content mapping information.

Explanation

The given content path was not found in the current content mapping information.

User response

None.

EJPFD0104E

The given content ID was not found in the current content mapping information.

Explanation

The given content ID was not found in the current content mapping information.

User response

None.

EJPFD0105E

The content mapping information could not be updated due to missing access rights.

Explanation

The current user has not been granted enough privileges to execute the given operation.

User response

None.

EJPFD0106E

The specified content path is no valid content path.

Explanation

The syntax of the given content path is incorrect.

User response

None.

EJPFD0107E

The hostname [{0}] cannot not be resolved to a virtual portal.

Explanation

The specified hostname is not associated with a virtual portal.

User response

Ensure that the specified hostname is associated with a virtual portal. Repeat the task with a corrected hostname or after creating a virtual portal for the specified hostname.

EJPFD0108E

The mapping URL context [{0}] cannot not be resolved to a virtual portal.

Explanation

The specified mapping URL context is not associated with a virtual portal.

User response

Ensure that the specified mapping URL context is associated with a virtual portal. Repeat the task with a corrected mapping URL context or after creating a virtual portal for the mapping URL context.

EJPFD0109E

Content mapping information has not been propgated to child pages of page {0}, because the page has too many child pages.

Explanation

The child pages of the given page have not been modified.

User response

Child pages need to be updated individually or the content mapping propagation configuration needs to be adjusted to tolerate a higher number of child resouce update operations.

EJPFD0110E

The page with ObjectID {0} could not be found.

Explanation

The given page was not found in the portal database.

User response

None.