45 WCS-03051 to WCS-90200

WCS-03051: No event is selected.
Cause: There was invalid or missing information in the connection.xml or adf-config.xml file.
Action: Verify that the connections.xml and adf-config.xml file contains a valid entry with the correct connection information.

Level: 1

Type: WARNING

Impact: Other

WCS-03052: event date validation error
Cause: An invalid date or time was selected for the event.
Action: Verify the date and time.

Level: 1

Type: ERROR

Impact: Other

WCS-03053: No upcoming events were found.
Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the adapter was not defined.
Action: Verify that the connections.xml file contains a valid connection for the Portal Events service, and the Portal Events server is running

Level: 1

Type: WARNING

Impact: Other

WCS-03101: The Events service is not able to acquire an adapter from the server.
Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the adapter was not defined.
Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the specified adapter is defined.

Level: 1

Type: ERROR

Impact: Other

WCS-03102: The Events service is unavailable.
Cause: The connections.xml file either did not contain a valid connection entry for the Personal Events service, or it was missing the entry for Personal Events with the state attribute set to default.
Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03103: Data query in Personal Events service failed
Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03104: Create event in Personal Events service failed
Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03105: Update event in Personal Events service failed
Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03106: Delete event in Personal Events service failed
Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03107: failure to send event mail in Personal Events service
Cause: Either the connections.xml file did not contain a valid connection for the Mail service, or the Mail server was down.
Action: Verify that the connections.xml file contains a valid connection for the Mail service, and that the Mail server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03108: failure to retrieve online meeting
Cause: Either the connections.xml file did not contain a valid connection entry for the Conference service, or the Conference server was down.
Action: Verify that the connections.xml file contains a valid connection for the Conference service, and the Conference server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03109: failure to retrieve personal event list
Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03110: failure to retrieve personal event detail
Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03111: The Personal Events service credential is not configured properly.
Cause: The Personal Events service credential was not configured properly.
Action: Verify that the Personal Events service credential is correct, and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-03112: The Personal Events service is not properly configured.
Cause: The Personal Events service was not properly configured in connections.xml.
Action: Verify that the connections.xml file contains a valid entry for the Personal Events service.

Level: 1

Type: ERROR

Impact: Other

WCS-03113: The Personal Events server is not available.
Cause: The Personal Events server was not available.
Action: Verify that the connections.xml file contains a valid entry for the Personal Events service, and the Personal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03114: failure to send personal event
Cause: Either the connections.xml file did not contain a valid connection for the Mail service, or the Mail server was down.
Action: Verify that the connections.xml file contains a valid connection for the Mail service, and the Mail server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03117: Failed to login to the exchange server.
Cause: The credential for the Personal Events service is not configured properly or the exchange server is not running.
Action: Verify that the credential for the Personal Events service is correct, and the exchange server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03118: Failed to login to the exchange server.
Cause: The credential for the Personal Events service credential is not configured properly.
Action: Verify that the credential for the Personal Events service is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-03201: The Events service is not able to acquire an adapter for an Events server.
Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service.
Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service.

Level: 1

Type: ERROR

Impact: Other

WCS-03202: The Events service is unavailable.
Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03203: Data query in Events service failed
Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03204: Create event in Events service failed
Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03205: Update event in Events service failed
Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03206: Delete event in Events service failed
Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03207: Send event mail in Events service failed
Cause: Either the connections.xml file did not contain a valid connection for the Mail service, or the Mail server was down.
Action: Verify that the connections.xml file contains a valid connection for the Mail service, and Mail server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03208: The changes to the event cannot be saved.
Cause: The event was modified or deleted by another user after the event was retrieved.
Action: Refresh the Events task flow to view changes, and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-03209: Cannot create the category
Cause: The category could not be created because a category of the same name already exists.
Action: Select the existing category.

Level: 1

Type: ERROR

Impact: Other

WCS-03210: cannot add the portal event to the personal calendar
Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03211: cannot add the portal event to the personal calendar
Cause: The Personal Events service was not configured properly in connections.xml or the Personal Events service is down.
Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03212: cannot add the portal event to the personal calendar
Cause: The credential for the Personal Events service was not configured properly.
Action: Verify that the credential for the Personal Events service is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-03213: Failure to create category
Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03214: failure to retrieve categories
Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03215: failure to retrieve portal event list
Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03216: failure to retrieve portal event detail
Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.
Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03217: failure to check the relationship for the event
Cause: Either the connections.xml file did not contain a valid connection entry for the Relationship service,or the Relationship service was down.
Action: Verify that the connections.xml file contains a valid entry for the Relationship service, the Relationship service is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03218: failure to save the display mode preference
Cause: Either the connections.xml file did not contain a valid connection entry for the Preferences service, or the Preferences service was down.
Action: Verify that the connections.xml file contains a valid entry for the Preferences service, and the Preferences service is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03219: failure to change the repeat attributes
Cause: Either the connections.xml file did not contain a valid connection entry for the Events service, or the Events service was down.
Action: Verify that the connections.xml file contains a valid entry for the Events service, and the Events service is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03220: The event was deleted by another user after you retrieved it. Refresh the Events task flow to see the changes if necessary.
Cause: The event was deleted by another user after you retrieved it.
Action: Refresh the Events task flow to view changes, and try again.

Level: 1

Type: WARNING

Impact: Other

WCS-03221: The event was updated by another user after you retrieved it. Refresh the Events task flow to see the changes if necessary.
Cause: The event was updated by another user after you retrieved it.
Action: Refresh the Events task flow to view changes, and try again.

Level: 1

Type: WARNING

Impact: Other

WCS-03222: You do not have permission to update this event or your permission to update this event is revoked. Refresh the Events task flow to see the changes if necessary.
Cause: You do not have permission to update this event or your permission to update this event is revoked.
Action: Refresh the Events task flow to view changes, and try again.

Level: 1

Type: WARNING

Impact: Other

WCS-03223: You do not have permission to view this event or your permission to view this event is revoked. Refresh the Events task flow to see the changes if necessary.
Cause: You do not have permission to view this event or your permission to view this event is revoked.
Action: Refresh the Events task flow to view changes, and try again.

Level: 1

Type: WARNING

Impact: Other

WCS-03224: You do not have permission to create the event or your permission to create the event is revoked. Refresh the Events task flow to see the changes if necessary.
Cause: You do not have permission to create this event or your permission to create this event is revoked.
Action: Refresh the Events task flow to view changes, and try again.

Level: 1

Type: WARNING

Impact: Other

WCS-03225: You do not have permission to delete the event or your permission to delete the event is revoked. Refresh the Events task flow to see the changes if necessary.
Cause: You do not have permission to delete this event or your permission to delete this event is revoked.
Action: Refresh the Events task flow to view changes, and try again.

Level: 1

Type: WARNING

Impact: Other

WCS-03226: You do not have permission to manage the event or your permission to manage the event is revoked. Refresh the Events task flow to see the changes if necessary.
Cause: You do not have permission to manage this event or your permission to manage this event is revoked.
Action: Refresh the Events task flow to view changes, and try again.

Level: 1

Type: WARNING

Impact: Other

WCS-03227: Event not found.
Cause: The event doesn't exist or was deleted.
Action: Refresh the Events task flow to view changes, and try again.

Level: 1

Type: WARNING

Impact: Other

WCS-03228: The Events service is currently disabled, preventing you from performing this operation. Contact your administrator.
Cause: The Events service is currently disabled.
Action: Contact your administrator. Enable the Events service.

Level: 1

Type: WARNING

Impact: Other

WCS-03301: The Web Conference service is unavailable.
Cause: Either the connections.xml file did not contain a valid connection entry, or the adapter was not defined in the adf-config.xml file.
Action: Verify that the connections.xml file contains a valid connection entry, and the specified adapter is defined in the adf-config.xml file.

Level: 1

Type: ERROR

Impact: Other

WCS-03302: The Web Conference service is unavailable.
Cause: The connections.xml file either did not contain a valid connection entry or the entry for conference service with the state attribute set to default was missing.
Action: Verify that the connections.xml file contains a valid connection entry and that the conference server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03303: failure to query data in WebCenter Conference service
Cause: There was an issue with the connections.xml file, or the Conference server was down.
Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03304: failure to create conference in WebCenter Conference service
Cause: There was an issue with the connections.xml file, or the Conference server was down.
Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03305: failure to update conference in WebCenter Conference service
Cause: There was an issue with the connections.xml file, or the Conference server was down.
Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03306: failure to delete conference in WebCenter Conference service
Cause: There was an issue with the connections.xml file, or the Conference server was down.
Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03307: failure to retrieve personal meetings
Cause: There was an issue with the connections.xml file, or the Conference server was down.
Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.

Level: 1

Type: ERROR

Impact: Other

WCS-03308: The Conference service is not properly configured.
Cause: The Conference service was not properly configured in connections.xml.
Action: Verify that the connections.xml file contains a valid entry for the Conference service.

Level: 1

Type: ERROR

Impact: Other

WCS-03309: The Conference service is properly not configured.
Cause: The Conference service was not configured in connections.xml.
Action: Verify that the connections.xml file contains a valid entry for the Conference service.

Level: 1

Type: WARNING

Impact: Other

WCS-03310: The Conference service is not properly configured.
Cause: The ambiguous connections of Conference service were found in connections.xml.
Action: Verify that the connections.xml file contains a valid entry for the Conference service.

Level: 1

Type: ERROR

Impact: Other

WCS-04001: unable to resolve the name {0}
Cause: The object with the given name could not be found.
Action: Check the JNDI configuration or the context passed.

Level: 1

Type: ERROR

Impact: Other

WCS-04002: ADFConfig does not contain adf-collaboration-config details with namespace: {0}.
Cause: The collaboration configuration tag 'adf-collaboration-config' might have been missing in ADFConfig.
Action: Ensure that the adf-config.xml file contains the adf-collaboration-config tag.

Level: 1

Type: ERROR

Impact: Other

WCS-04003: No adapter found for service {0}
Cause: No adapter configuration found or the implementation class could not be loaded.
Action: Ensure adapter is configured properly or change the SessionFactory to override the default behavior.

Level: 1

Type: ERROR

Impact: Other

WCS-04004: unable to load the class {0}
Cause: The class named in the error message was not available in the class path.
Action: Check the class path and ensure this class is available.

Level: 1

Type: ERROR

Impact: Other

WCS-04005: unable to load the class {0}, due to: {1}
Cause: Either the class named in the error message was not available in the class path or it could not be instantiated.
Action: Check the logs for more details. Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-04006: ADFConfig {0} {1} does not contain the required attribute {1}.
Cause: The required attribute was missing from the configuration.
Action: Ensure that the required attribute is added to the configuration.

Level: 1

Type: ERROR

Impact: Other

WCS-04007: The attachment size is too large to be consumed.
Cause: The storage quota was exceeded.
Action: Select a different attachment with a smaller size.

Level: 1

Type: WARNING

Impact: Other

WCS-04008: The attachment type is not supported.
Cause: The attachment type was not supported.
Action: Try with a different MIME type.

Level: 1

Type: WARNING

Impact: Other

WCS-04009: The attachment cannot be found.
Cause: The attachment was not readable.
Action: Try a different attachment.

Level: 1

Type: WARNING

Impact: Other

WCS-04010: failure to create, update, or fetch the service configuration file {0}, due to: {1}
Cause: One of the following was the cause: There was a concurrent modification by another user; there was an MDS I/O exception; the metadata was not found; a validation error occurred; or the update was not supported.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-04011: unable to find the service configuration file {0}, due to: {1}
Cause: The service was not provisioned for this portal.
Action: Provision this service or contact the system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-04012: unable to find the credentials for user {0}
Cause: The credentials were either not supplied, or were invalid.
Action: Supply credentials using the External Application configured for the service.

Level: 1

Type: WARNING

Impact: Other

WCS-04013: failure to authenticate the user {0}, due to: {1}
Cause: There was a failure while connecting to server, or the credentials were invalid.
Action: Ensure the credentials are supplied and are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-04014: no connections available for: {0}
Cause: There are no connections defined for this connection type.
Action: At least one connection must be defined for this connection type.

Level: 1

Type: WARNING

Impact: Other

WCS-04015: There are multiple connections defined for the connection type {0}, but no default connection is specified.
Cause: Multiple connections of this type were defined, but the default connection was not specified.
Action: Select the appropriate connection for this type and mark it as the default.

Level: 1

Type: ERROR

Impact: Other

WCS-04016: unable to look up connection with name {0}
Cause: Either the connection name was wrong or the connection was deleted.
Action: Verify the name of the connection supplied and also ensure that the connection with this name is available.

Level: 1

Type: ERROR

Impact: Other

WCS-04017: failure to create session instance for: {0}
Cause: An instantiation exception occurred for the session class. Either this class was not a valid class or it could not be loaded from the class path.
Action: Verify that the session class supplied is a valid class, and that it is available in the class path.

Level: 1

Type: ERROR

Impact: Other

WCS-04018: failure to create session for {0}, due to: {1}
Cause: Either the required configuration was missing or class was not found.
Action: Verify that the session class supplied is a valid class, and that it is available in the class path.

Level: 1

Type: ERROR

Impact: Other

WCS-04019: There are multiple adapters for the session {0}, but the default adapter is not specified.
Cause: Multiple adapters were defined for this session type, but the default adapter was not specified in the connection.
Action: Update the connection and ensure that the adapter name is specified (ensure that the "adapter.name" property exists).

Level: 1

Type: ERROR

Impact: Other

WCS-04020: No adapter found with name {0}.
Cause: Adapter not found with the given name.
Action: Ensure the adapter with this name configured in the adf-config.xml file.

Level: 1

Type: ERROR

Impact: Other

WCS-04021: Not an instance of {1} : {0}
Cause: Supplied class is not an instance of SessionManager class.
Action: Check the service configuration property "session.manager.class".

Level: 1

Type: ERROR

Impact: Other

WCS-04022: The service is unavailable.
Cause: Cannot establish connection to the server, either the server is down or the connect details are wrong.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-04023: Cache not available.
Cause: Cache is not initialized.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-04024: unable to find object {0} in the cache
Cause: The object was either not cached or it had expired.
Action: Ensure that the object is cached.

Level: 1

Type: WARNING

Impact: Other

WCS-04025: Session not initialized {0}.
Cause: Either initialize method on the session is not invoked or initialization has failed.
Action: Check logs for more details or Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-04026: session instance acquired is null from SessionFactory: {0}
Cause: SessionFactory returned null session instance. Wrong factory implementation.
Action: Check the SessionFactory implementation for more details or contact the system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-04027: Session Factory class not defined.
Cause: Either the service-config for the session is missing or "session.factory.class" property is missing.
Action: Check the service-config.xml for the given session type exists and "session.factory.class" property is defined with a qualified class name that is available in the classpath. Contact system administrator for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-04030: System user session is requested from session {0}, but administrator user name is not defined in the connection nor in adf-config.
Cause: Missing "admin.user" property from connection and/or adf-config.xml.
Action: Ensure that either the connection or ADF service-config contains a property called "admin.user" with a valid administrator user.

Level: 1

Type: WARNING

Impact: Other

WCS-04031: Unexpected error occurred, due to : {0}
Cause: An unexpected server exception occurred.
Action: Contact the system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-04032: Could not get access to cache object.
Cause: API should be invoked only for getting access to the root cache.
Action: Try using correct API.

Level: 1

Type: WARNING

Impact: Other

WCS-04033: Invalid cache name: {0}.
Cause: Cache name supplied is either empty or null.
Action: Supply valid name for the cache.

Level: 1

Type: WARNING

Impact: Other

WCS-04034: Not able to fetch data due to {0}.
Cause: Might be because the backend system is not reachable.
Action: Try after sometime.

Level: 1

Type: WARNING

Impact: Other

WCS-04035: Session Type for Session instance {0} is null.
Cause: Session Factory does not set the SessionType on the Session instance created.
Action: Check the session factory implementation.

Level: 1

Type: WARNING

Impact: Other

WCS-04036: User not found: {0}.
Cause: Unable to find the user with the supplied name in the user repository.
Action: Check user with the given identity exists in the user repository.

Level: 1

Type: WARNING

Impact: Other

WCS-04037: Supplied class {0} is not an instance of {1}.
Cause: Supplied class is not an instance of SessionFactory class.
Action: Check the adf-config.xml or service-config.xml configuration property "session.factory.class".

Level: 1

Type: ERROR

Impact: Other

WCS-04039: Session Manager instance creation failed for {0}
Cause: Either the required configuration is missing or class is not found..
Action: Check the class supplied is a valid class and its available in the classpath.

Level: 1

Type: ERROR

Impact: Other

WCS-04040: CacheFactory not specified.
Cause: CacheFactory instance is not found.
Action: Set appropriate CacheFactory instance on the Cache class.

Level: 1

Type: ERROR

Impact: Other

WCS-04041: No default or active connection available for: {0}
Cause: There is no default or active connection defined for this connection type.
Action: At least one connection must be defined default or active for this connection type.

Level: 1

Type: WARNING

Impact: Other

WCS-04042: Enterprise role not found: {0}.
Cause: Unable to find the enterprise role with the supplied name in the backend server.
Action: Check group with the given identity exists in the backend server.

Level: 1

Type: WARNING

Impact: Other

WCS-04043: Service is disabled for the current Portal: {0}.
Cause: Service is disabled for the current Portal.
Action: Enable this service or contact the Portal Moderator.

Level: 1

Type: WARNING

Impact: Other

WCS-04201: Error loading relationship service implementation
Cause: The relationship service encountered a problem while loading a relationship service implementation.
Action: Check the stack trace for more information

Level: 1

Type: ERROR

Impact: Other

WCS-04206: Error checking create permission
Cause: There was an error loading the relationship security provider.
Action: Check to make sure that the relationship security provider is properly configured.

Level: 1

Type: ERROR

Impact: Other

WCS-04207: Could not instantiate relationship repository
Cause: The relationship service encountered a problem while instantiating the repository.
Action: Check the stack trace for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-04208: jdbc/WebCenterDS data source not found: {0}
Cause: The jdbc/WebCenterDS data source could not be found.
Action: Ensure that the jdbc/WebCenterDS data source is created.

Level: 1

Type: WARNING

Impact: Other

WCS-04301: Relationship repository is not available.
Cause: An error was encountered while checking if the relationship repository was available.
Action: Check the log for errors that may have caused this.

Level: 1

Type: ERROR

Impact: Other

WCS-04302: Relationship already exists between [sourceApplicationId={0} sourceResourceId={1}] and [targetApplicationId={2} targetResourceId{3}].
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-04303: Resource does not exist [applicationId={0} resourceId={1}].
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-04304: Target resource was not found [targetApplicationId={0} targetResourceId={1}].
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-04305: Relationship was marked as a bi-directional relationship, however no target to source back relationship was found for target [targetApplicationId={0} targetResourceId={1}].
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-04306: Source object was not found [sourceApplicationId={0} sourceResourceId={1}].
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-04401: Exception during event or action
Cause: The relationship service encountered a problem while performing an event or action
Action: Check the application log for more information on the cause

Level: 1

Type: ERROR

Impact: Other

WCS-04403: Could not find relationship service {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-04404: Service {0} threw exception for getViewObject() on RelatedObject {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-04405: linksDetailedPanelWindow is null: cannot add partial target to RequestContext.
Cause: The relationship popup task flow is not included in the page.
Action: Check to make sure the relationship popup task flow is included in the page.

Level: 1

Type: WARNING

Impact: Other

WCS-04406: Cannot get current RichLinksDetailButtonRow. FacesContext.getCurrentInstance().getRenderKit() returned null for component: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-04407: Exception while checking for existing links
Cause: An error was encountered while checking for existing links.
Action: Check the application log for more information on the cause.

Level: 1

Type: ERROR

Impact: Other

WCS-04408: Error instantiating RichLinksDetailButtonRow
Cause: The relationship service encountered a problem while instantiating a custom component.
Action: Check the relationship links button component for valid attributes.

Level: 1

Type: ERROR

Impact: Other

WCS-04409: Error instantiating RichLinskDetailMenuItem
Cause: The relationship service encountered a problem while instantiating a custom component.
Action: Check the relationship links menu component for valid attributes.

Level: 1

Type: ERROR

Impact: Other

WCS-04410: Could not find Links Detail Popup in the LinksDetailBean bean
Cause: The relationship service encountered a problem while encoding the popup.
Action: Make sure the links popup task flow is included in the page.

Level: 1

Type: ERROR

Impact: Other

WCS-04412: Attribute value is null for component: {0}
Cause: A required attribute value is bound to a null value.
Action: Make sure the required attributes of this component are bound to non-null values.

Level: 1

Type: WARNING

Impact: Other

WCS-04413: An exception occurred while parsing parameter
Cause: A number format exception was encountered while parsing a parameter.
Action: Make sure the window width/height parameters for launching relationship views are valid numbers.

Level: 1

Type: WARNING

Impact: Other

WCS-04414: Got null from registry for service ID {0}, including all target services: {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-04415: Service {0} returned null for target view object with objectId: {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-04417: Could not find {0} parameter for the Links Detail taskflow.
Cause: The parameter is required for processing links-detail task flow.
Action: Make sure the parameter is bound to a non-null value.

Level: 1

Type: ERROR

Impact: Other

WCS-04418: User principal is null.
Cause: The user principal returned by the security context was null.
Action: Make sure security is property configured for the application.

Level: 1

Type: WARNING

Impact: Other

WCS-04419: Links components cannot render
Cause: The links-detail-popup task flow panelWindow was not found.
Action: Make sure the view includes the links-detail-popup task flow.

Level: 1

Type: WARNING

Impact: Other

WCS-04420: The image file {0} you tried to select was invalid. Provide a valid image file.
Cause: Unable to embed the image as the file is null or invalid.
Action: Select a valid image file

Level: 1

Type: ERROR

Impact: Other

WCS-04421: The taskflow id {0} was invalid. Provide a valid taskflow id.
Cause: Unable to retrieve the taskflow as the id is null or invalid.
Action: Specify a valid taskflow Id.

Level: 1

Type: ERROR

Impact: Other

WCS-04422: The NewRelatedObject returned from the service {0} was invalid.
Cause: Unable to process the returned object.
Action: Return a valid object for linking.

Level: 1

Type: ERROR

Impact: Other

WCS-04601: unexpected error
Cause: An unexpected error occurred for the RTC service.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-04602: Unable to load RTC configuration
Cause: Connections context could not be acquired.
Action: Ensure that the connections.xml file is available and valid.

Level: 1

Type: WARNING

Impact: Other

WCS-04603: Unable to load RTC configuration
Cause: No RTC (Real-Time Communication) connection was specified.
Action: Ensure that the property 'selected.connection' for the RTC service's 'service-config' element within the application's adf-config.xml file is available with a valid RTC connection name value.

Level: 1

Type: WARNING

Impact: Other

WCS-04604: Unable to lookup RTC connection {0}
Cause: The specified connection name either did not exist or did not resolve to a valid RTC connection.
Action: Ensure that the property 'selected.connection' for the RTC service's 'service-config' element within the application's adf-config.xml file contains a valid RTC connection name (as defined in the application's connections.xml file).

Level: 1

Type: WARNING

Impact: Other

WCS-04605: Unable to load RTC adapter {0}
Cause: The specified RTC adapter name was invalid.
Action: Ensure that the property 'adapter.name' of the RTC connection is valid and the corresponding adapter definition is available within the RTC 'service-config' element in the application's adf-config.xml file.

Level: 1

Type: WARNING

Impact: Other

WCS-04606: Unable to load RTC adapter {0}
Cause: The specified RTC adapter class does not extend from IMPConnection class.
Action: Ensure that the RTC adapter class extends IMPConnection class and follows its contract.

Level: 1

Type: WARNING

Impact: Other

WCS-04607: Unable to load RTC adapter {0}
Cause: The specified RTC adapter class could not be instantiated.
Action: Ensure that the RTC adapter class extends IMPConnection class and follows its contract.

Level: 1

Type: WARNING

Impact: Other

WCS-04608: Unable to load RTC adapter {0}
Cause: The RTC configuration object was null or invalid.
Action: Ensure that the RTC configuration is valid.

Level: 1

Type: WARNING

Impact: Other

WCS-04610: Unable to create instance of the UserManager implementation class {0}.
Cause: The specified user manager class could not be instantiated.
Action: Ensure that the class exists and can be instantiated with a default constructor.

Level: 1

Type: WARNING

Impact: Other

WCS-04611: Unable to find a valid RTC connection.
Cause: No RTC connections were found within the application's connections.xml file.
Action: Ensure that there is a valid RTC connection defined in the application's connections.xml file.

Level: 1

Type: WARNING

Impact: Other

WCS-04612: Invalid RTC address resolver specified: {0}
Cause: Specified address resolver was invalid.
Action: Ensure that the resolver type is one of DEFAULT, PROFILE_ATTRIBUTE, or CUSTOM.

Level: 1

Type: WARNING

Impact: Other

WCS-04614: Invalid attribute specified for PROFILE address resolver: {0}
Cause: The specified profile attribute for the address resolver was invalid.
Action: Ensure that the 'rtc.address.resolver.mapping' attribute is not null and contains a valid profile attribute.

Level: 1

Type: WARNING

Impact: Other

WCS-04615: Unable to load custom RTC address resolver: {0}
Cause: The custom class could not be initialized.
Action: Ensure that the custom class extends RtcAddressResolver and follows the contract specified by it.

Level: 1

Type: WARNING

Impact: Other

WCS-04616: Unable to load custom RTC address resolver: {0}
Cause: No custom class was specified for the CUSTOM type RTC address resolver.
Action: Ensure that the 'rtc.address.resolver.mapping' attribute is not null and contains a fully qualified and valid class name that extends from the RtcAddressResolver class.

Level: 1

Type: WARNING

Impact: Other

WCS-04619: The RTC address resolver supplied is invalid or null.
Cause: The RTC address resolver supplied was invalid or null.
Action: Ensure that 'rtc.address.resolver.mapping' attribute is not null.

Level: 1

Type: WARNING

Impact: Other

WCS-04620: The domain supplied is invalid or null.
Cause: The domain supplied was invalid or null.
Action: Ensure that the 'domain' attribute is not null or invalid.

Level: 1

Type: WARNING

Impact: Other

WCS-04621: Invalid timeout value specified: {0} Defaulting to {1}
Cause: The presence cache timeout value was either null or not a valid number.
Action: Ensure that the 'rtc.cache.time' attribute is not null and contains a valid number.

Level: 1

Type: WARNING

Impact: Other

WCS-04625: Failed to instantiate IMPSession for the logged-in user.
Cause: The adapter class could not be instantiated.
Action: Ensure that the property 'adapter-class' has been defined for the adapter in the adf-config.xml and is valid.

Level: 1

Type: WARNING

Impact: Other

WCS-04801: Invalid timeout value specified: {0} Defaulting to {1}
Cause: The presence cache timeout value was either null or not a valid number.
Action: Ensure that the 'rtc.cache.time' attribute is not null and contains a valid number.

Level: 1

Type: WARNING

Impact: Other

WCS-04804: Unable to acquire RTC connection for user {0}. RTCService running in dummy mode.
Cause: Exception caught while initializing IMPConnection.
Action: Check the log file for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-04805: Unable to acquire associated external application details.
Cause: The external application ID could not be loaded from the RTC connection configuration.
Action: Ensure that the 'ext.app.id' attribute is not null and refers to a valid external application ID.

Level: 1

Type: ERROR

Impact: Other

WCS-04806: Unable to acquire associated external application details.
Cause: The external application was not found for the external application ID.
Action: Ensure that external application ID refers to a valid external application.

Level: 1

Type: ERROR

Impact: Other

WCS-04851: Failed to generate endpoint to talk to OCS WebService.
Cause: The webservice is unreachable.
Action: Ensure that the OCS connection entry contains the 'base.connection.url' property and points to a valid URL.

Level: 1

Type: ERROR

Impact: Other

WCS-04852: Unable to perform operation {0}
Cause: Failed to perform the operation on remote Web service.
Action: Ensure that the RTC configuration is correct, the remote system is available, and the errors generated in the remote system's logs have been fixed.

Level: 1

Type: ERROR

Impact: Other

WCS-04853: Exception caught while fetching buddy list for user {0}
Cause: Failed to retrieve buddy list from the Remote Service.
Action: Ensure that valid OCS connection entries have been supplied and the server is up.

Level: 1

Type: WARNING

Impact: Other

WCS-04854: Exception caught while fetching presence information using user account {0}
Cause: Failed to fetch presence information from the remote service.
Action: Ensure that valid OCS connection entries have been supplied and the server is up.

Level: 1

Type: WARNING

Impact: Other

WCS-04855: Account field missing from user credentials
Cause: Cannot login to server without the account information.
Action: Ensure that a valid sip address value is supplied as the Account in credentials.

Level: 1

Type: WARNING

Impact: Other

WCS-04856: Connection not defined
Cause: Connection is not defined.
Action: Ensure that the connection is defined.

Level: 1

Type: WARNING

Impact: Other

WCS-04857: External application ID not defined.
Cause: The required configuration parameter External Application ID was not found.
Action: Contact your system Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-04901: Not initializing RtcAction {0} as it does not extend from RtcAction
Cause: Specified class does not extend from RtcAction.
Action: Ensure that the specified class is a proper subclass of RtcAction.

Level: 1

Type: WARNING

Impact: Other

WCS-04902: Failed to initialize RtcAction {0}
Cause: Unable to instantiate the supplied RtcAction subclass.
Action: Ensure that the specified class is a proper subclass of RtcAction, and provides a default constructor.

Level: 1

Type: WARNING

Impact: Other

WCS-04903: ADFConfig does not contain rtc-config details with namespace : {0}.
Cause: The RTC actions tag 'rtcC:actions' might be missing in ADFConfig.
Action: Ensure adf-config.xml file contains rtcC:actions tag.

Level: 1

Type: WARNING

Impact: Other

WCS-04904: Cannot process call request : User Profile for user {0} not found
Cause: User has selected PSTN call method but its profile cannot be found for the user to read the contact number.
Action: Ensure that the user profile exists in the system.

Level: 1

Type: WARNING

Impact: Other

WCS-04905: Cannot process call request : Contact information for user {0} not found
Cause: User has selected PSTN call method but has not supplied the correct ldap attribute to read the contact information.
Action: Ensure that correct ldap attribute has been supplied in connection/adf-config and its value has been set in the profile.

Level: 1

Type: WARNING

Impact: Other

WCS-04906: Cannot process call request : Incorrect call method supplied
Cause: User has supplied an incorrect call method.
Action: Ensure that correct call method is supplied. Refer to the documentation to find the supported call methods.

Level: 1

Type: WARNING

Impact: Other

WCS-04907: Cannot process call request : Call domain not specified in connection.
Cause: User has selected PSTN call method but has not supplied the call.domain property.
Action: Ensure that correct call.domain has been supplied in connection/adf-config.

Level: 1

Type: WARNING

Impact: Other

WCS-04908: Cannot process call request : User name is missing or not provided.
Cause: User name is missing or it has not been provided.
Action: Ensure that correct user name is provided, contact administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-05001: Cannot retrieve the metadata for a portal
Cause: Unable to fetch the portal metadata due to an internal error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05002: An error occurred while trying to get the ScopeAPI implementation for the service {0}.
Cause: Service {0} does not support provisioning.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05003: The service object passed to the wrapper is null.
Cause: A null service object was retrieved from the service registry.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05004: A portal template named {0} already exists.
Cause: Name specified for the portal template was not unique. A template with the same name already exists.
Action: Provide a unique name for the portal template.

Level: 1

Type: ERROR

Impact: Other

WCS-05005: Cannot create portal template
Cause: No name was provided for the portal template.
Action: Provide a unique name for the portal template.

Level: 1

Type: ERROR

Impact: Other

WCS-05006: Unable to retrieve information about {0}.
Cause: No portal template was found with the name specified.
Action: Provide the name of an existing portal template.

Level: 1

Type: ERROR

Impact: Other

WCS-05007: The reference to the portal template metadata {0} is invalid.
Cause: No portal template was found with the name specified.
Action: Provide the name of an existing portal template.

Level: 1

Type: ERROR

Impact: Other

WCS-05008: Unable to get mutable metadata for the portal template {0}
Cause: Some portion of the portal template metadata has already been modified.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05009: Metadata for the portal template {0} is invalid.
Cause: MDS reported a metadata validation error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05010: An error occurred reading or writing metadata of portal template {0}.
Cause: MDS reported an IO error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05011: The commit operation failed due to a concurrent metadata change for portal template {0}.
Cause: MDS reported a concurrent metadata change error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05012: Couldn''t retrieve the portal members email ids for {0} due to {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-05013: Unable to execute portal related operation on {0}
Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05014: Unable to get metadata for portal {0}.
Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05015: Cannot create metadata for portal {0}
Cause: Metadata for the specified portal already exists.
Action: Provide a different name.

Level: 1

Type: ERROR

Impact: Other

WCS-05018: The reference to the metadata of portal {0} is invalid.
Cause: The metadata reference was invalid.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05019: Unable to get mutable metadata for portal {0}
Cause: Some portion of the portal metadata has already been modified.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05020: Metadata of portal {0} is invalid.
Cause: MDS reported a metadata validation error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05021: An error occurred reading or writing metadata of portal {0}.
Cause: MDS reported an IO error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05022: The commit operation failed due to a concurrent metadata change for portal {0}.
Cause: MDS reported a concurrent metadata change error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05023: Cannot retrieve a list of members for the current portal.
Cause: An error occurred trying to access the specified portal.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05025: Could not create portal {0} from portal template {1}.
Cause: An internal error occurred.
Action: Contact Administrator.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05026: Could not create portal template {1} from portal {0}.
Cause: Either the specified portal template already exists or the name was invalid.
Action: Provide a valid,unique name for the portal template.

Level: 1

Type: ERROR

Impact: Other

WCS-05027: Unable to get preference metadata for portal {0}
Cause: Either the metadata does not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has changed.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05035: Unexpected error in renaming portal from {0} to {1}. Contact administrator or try again after some time.
Cause: An invalid character was found in the name.
Action: Remove the invalid character(s) from the name and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-05036: A portal with the URL {0} already exists.
Cause: A portal with the specified URL exists.
Action: Specify a unique name for the portal.

Level: 1

Type: ERROR

Impact: Other

WCS-05037: The portal template name contains an invalid character {0}.
Cause: An invalid character was found in the portal template name.
Action: Remove the invalid character(s) from the portal template name and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-05038: A portal template named {0} already exists.
Cause: A portal template with the specified name already exists.
Action: Specify a unique name for the portal template.

Level: 1

Type: ERROR

Impact: Other

WCS-05039: An error occurred attempting to save this portal as a portal template.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05040: The portal name contains one or more blank space characters.
Cause: A blank was found in the portal name. Blank spaces are not allowed.
Action: Remove all blank spaces from the portal name and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-05041: The portal template name contains one or more blank space characters.
Cause: A blank space was found in the name of the portal template. Blank spaces are not allowed.
Action: Remove all blank spaces from the portal template name and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-05042: Unable to get metadata {1} for portal {0}.
Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05043: A portal with title {0} already exists. While the portal may not be available to you, another portal has that title. Choose a different title for your portal.
Cause: A portal with the specified display name exists.
Action: Specify a unique display name for the portal.

Level: 1

Type: ERROR

Impact: Other

WCS-05047: Sending invitation to user(s) failed. The reason is : {0}.
Cause: Connection details for the BPEL server providing portal invitation services were not available.
Action: Ask your administrator to configure a connection to the BPEL server providing portal invitation services.

Level: 1

Type: ERROR

Impact: Other

WCS-05048: Unexpected error occurred while trying to invite user(s) to portal {0}
Cause: The BPEL server that provides the portal invitation service might have been down.
Action: Ask your administrator to restart the BPEL server, and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-05058: Cannot create policy store metadata for portal {0}
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05059: Cannot save the changes
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05063: Cannot delete portal {0} due to unknown errors.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05065: Cannot not get the list of available services
Cause: No services were available in the service registry.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05066: An error occurred while attempting to unsubscribe a user from portal {0}.
Cause: The BPEL server supporting portal unsubscription may be down
Action: Ask your administrator to restart the BPEL server and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-05067: Unable to send unsubscription request to Portal Manager(s). The reason is : {0}.
Cause: Connection details for the BPEL server providing portal unsubscription services were not available.
Action: Ask your administrator to configure a connection to the BPEL server providing portal unsubscription services.

Level: 1

Type: ERROR

Impact: Other

WCS-05068: An error occurred attempting to unsubscribe user from portal {0}: {1}.
Cause: Connection details for the BPEL server providing portal unsubscription services were not available.
Action: Ask your administrator to configure a connection to the BPEL server providing portal unsubscription services.

Level: 1

Type: ERROR

Impact: Other

WCS-05069: Unable to send subscription notification to Portal Manager(s). The reason is : {0}.
Cause: The BPEL URL has not been configured yet.
Action: Notify your administrator that the BPEL service supporting portal subscription is not configured

Level: 1

Type: ERROR

Impact: Other

WCS-05070: An error occurred attempting to subscribe a user to portal{0}.
Cause: The BPEL server providing the portal subscription service may be down.
Action: Ask your administrator to restart the BPEL server, and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-05071: An error occurred attempting to subscribe user to portal {0}: {1}.
Cause: The BPEL server providing the portal subscription service may be down.
Action: Ask your administrator to restart the BPEL server, and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-05072: Error occurred while navigating to portal {0}.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05073: Could not create portal with name {0}
Cause: The portal name provided could not be created.
Action: Please contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05074: An error occurred attempting to access a page of the renamed portal.
Cause: The portal rename operation was not successful.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05075: An error occurred attempting to rename a portal.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05077: Could not retrieve portal workflow configuration. Please contact administrator.
Cause: An error occurred attempting to retrieve the BPEL Several URL configured in connections.xml
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05078: Cannot delete workflow approval metadata from the portal
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-05079: Cannot get the security handler for portal template {0}
Cause: The policy store metadata was not available for portal template security initialization.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05080: Cannot create the portal template {0}
Cause: The portal template was not created due to an error reported by the metadata store.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05081: Unable to retrieve metadata object for portal {0}
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05082: Adding workflow approval metadata to the portal failed
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-05083: An error occurred attempting to rename portal {0} to {1}.
Cause: The portal rename operation was successful.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05084: An unexpected error occurred attempting to delete portal {0}.
Cause: The portal delete operation was unsuccessful.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05085: Portal name cannot be null
Cause: Portal name was blank.
Action: Enter a valid alphanumeric name for the portal

Level: 1

Type: ERROR

Impact: Other

WCS-05086: Portal name is a reserved keyword.
Cause: The portal name specified was a reserved keyword.
Action: Specify a valid alphanumeric name for the portal which excludes the following reserved keywords: webcenter, pages, page, spaces, space, group, groups, space, spaces, webcenter space, webcenter spaces, webcenter Portal, WebCenter Portal, WebCenter Portal spaces, portal, webcenter administration, my spaces, admin, last, system.

Level: 1

Type: ERROR

Impact: Other

WCS-05087: The portal name contains invalid characters. Only alphanumeric and space characters are allowed.
Cause: Portal name contained non-alphanumeric/space characters.
Action: Specify a valid alphanumeric name for the portal that only contains a-z, A-Z, 0-9, _, or a space character

Level: 1

Type: ERROR

Impact: Other

WCS-05088: Cannot delete the seeded portal template {0}
Cause: An attempt was made to delete a seeded portal template.
Action: Do not try to delete a seeded portal template.

Level: 1

Type: ERROR

Impact: Other

WCS-05089: Connection details for the BPEL server providing portal notification services are not available. Unable to send add or delete notifications to members of portal{0}
Cause: Connection details for the BPEL server providing portal invitation services were not available or configured incorrectly.
Action: Ask your administrator to configure a connection to the BPEL server providing portal notification services.

Level: 1

Type: ERROR

Impact: Other

WCS-05090: An error occurred attempting to send a notification to a member added to or deleted from portal {0}
Cause: An error occurred attempting to send a portal notification.
Action: Contact Oracle Support.

Level: 1

Type: ERROR

Impact: Other

WCS-05091: Connection details for the BPEL server providing notification services in WebCenter Portal not found.
Cause: Connection details for the BPEL server providing notification services in WebCenter Portal were not available.
Action: Ask the administrator to configure a connection to the BPEL server providing notification services in WebCenter Portal.

Level: 1

Type: ERROR

Impact: Other

WCS-05092: One of the arguments passed to API call {0} is null
Cause: A null argument was passed to an API call
Action: Invoke the API with non-null arguments

Level: 1

Type: ERROR

Impact: Other

WCS-05093: Portal template name cannot be null
Cause: No name was specified for the portal template.
Action: Specify a valid alphanumeric name for portal template.

Level: 1

Type: ERROR

Impact: Other

WCS-05094: Portal template name is a reserved keyword.
Cause: The template name specified was a reserved keyword.
Action: Specify a valid alphanumeric name for the template which excludes the following reserved keywords: admin, builder, group, groups, home, last, page, pages, my portals, my spaces, portal, portals, spaces, space, system, webcenter, webcenter administration, webcenter portal, webcenter portals, webcenter space, webcenter spaces.

Level: 1

Type: ERROR

Impact: Other

WCS-05095: Template name contains invalid characters. Only alphanumeric and space characters are allowed.
Cause: Template name contains non-alphanumeric or space characters
Action: Specify a valid alphanumeric name for the template that only contains:a-z, A-Z, 0-9, _, or a space character

Level: 1

Type: ERROR

Impact: Other

WCS-05096: A portal template with name {0} already exists.
Cause: A portal template with the specified name exists.
Action: Specify a unique name.

Level: 1

Type: ERROR

Impact: Other

WCS-05097: Cannot upload portal icon
Cause: An error occurred while attempting to upload the file to WebCenter Portal
Action: Try again or contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

WCS-05098: Cannot upload a portal logo
Cause: An error occurred attempting to upload the file to WebCenter Portal
Action: Try again or contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

WCS-05099: Unable to set lock on portal {0}
Cause: A lock could not be acquired for this portal.
Action: Try again later.

Level: 1

Type: ERROR

Impact: Other

WCS-05100: Unable to execute operation on portal {0}
Cause: Portal {0} was locked by some other operation.
Action: Wait for the first operation to complete and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-05101: Unable to execute portal operation
Cause: The portal was locked by some other operation.
Action: Wait for the first operation to complete and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-05102: Error creating portal {0} from portal template {1}
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-05103: Errors while renaming portal {0}
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-05104: Unexpected error while trying to request change membership to portal {0}
Cause: The BPEL server might have been down.
Action: Ensure BPEL server is up and retry. Contact the portal manager for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-05105: Unexpected error while trying to send notification to user {0}
Cause: The BPEL server might have been down.
Action: Ensure BPEL server is up and retry. Contact the portal manager for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-05106: Unexpected error creating region in cache
Cause: An attempt to create a region in the JOC (Java Object Cache) failed.
Action: Ensure that the JOC configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05107: Unexpected error getting object {0} from region {1} in cache
Cause: An attempt to retrieve an object from the cache failed.
Action: Ensure that the JOC configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05108: Search {0} for portal returned more than {2} results.
Cause: Search matched {1} results for portal template. The maximum number of result records allowed for this report is {1}.
Action: Restrict your query further, or use a different query.

Level: 1

Type: ERROR

Impact: Other

WCS-05109: Portal operation resulted in unexpected exception.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-05111: Creating template resulted in unexpected exception.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-05112: Fetching portal member count resulted in unexpected exception.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-05113: An error occurred while trying to provision the service {0}. The service did not get provisioned.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05114: An error occurred while trying to unprovision the service {0}. The service did not get unprovisioned.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05115: An error occurred while trying to determine the selected service.
Cause: An unexpected error occurred.
Action: Reload the browser page, and if problem persists, contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05116: An error occurred while trying to process the service that was selected.
Cause: An unexpected error occurred.
Action: Reload the browser page, and if problem persists, contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05117: An error occurred while trying to load the configuration screen for the selected service.
Cause: An unexpected error occurred.
Action: Reload the browser page, and if problem persists, contact the administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-05118: Failed to delete portal {0} security metadata
Cause: Deletion of portal security metadata failed
Action: An unexpected error occurred while trying to deleting portal {0}. Please contact administrator for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-05119: An unexpected error occurred while trying to provision/unprovision services.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05120: An unexpected error occurred while trying to save the configuration for the service {0}.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05121: An unexpected error occurred while trying to upload an image for portal {0}.
Cause: An unexpected error occurred during image upload.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05122: There was an error while fetching the GUID for portal {0}.
Cause: An unexpected error occurred while fetching the GUID for portal {0}.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05123: Metadata Not Found Exception occurred while fetching the service config metadata for a portal {0}.
Cause: An unexpected error occurred while fetching the service config metadata for portal {0}
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05124: An exception occurred while fetching the Portal Manager for portal {0}.
Cause: An unexpected error occurred while fetching the Portal Manager for portal {0}.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05125: An exception occurred while fetching the Portal Manager for portal {0}.
Cause: An unexpected error occurred while fetching the Portal Manager for portal {0}.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05126: An exception occurred while fetching the GUID for portal {0}.
Cause: An unexpected error occurred while fetching the GUID for portal {0}.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05127: An exception occurred while fetching the contacts list for portal {0}.
Cause: An unexpected error occurred fetching the contacts list for portal {0}.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05128: An exception occurred while fetching the GUID for portal {0}.
Cause: An unexpected error occurred while fetching the GUID for portal {0}.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05129: Error occurred while launching the delete role confirmation.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05130: Error occurred while launching add/invite members table.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05131: Error occurred while getting the message for inviting non-members.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05132: Error occurred while performing operations on roles.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05133: Error occurred while adding custom attributes name={0} and value={1}.
Cause: An unexpected error occurred while adding the custom attributes.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05134: Error occurred while deleting the name={0} custom attribute
Cause: An unexpected error occurred while deleting the custom attribute.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05135: Error occurred while editing the custom attribute name={0} and value={1}.
Cause: An unexpected error occurred while editing the custom attribute.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05136: Error occurred while fetching the custom attributes for portal {0}.
Cause: An unexpected error occurred while fetching the custom attribute.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05137: No Such Attribute exists.
Cause: Unable to find the custom attributes
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05138: Unexpected error in getting the list of portals. You can try again later or contact Administrator.
Cause: Unexpected error in getting portals.
Action: Please contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05139: Unexpected error in retrieving portal {0}.
Cause: Unexpected error in retrieving the portal.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05140: Unexpected error while rolling back the service {0}
Cause: Error in rolling back the service.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05141: Unknown errors creating portal. Please contact Administrator.
Cause: Post creating the portal, there were errors.
Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05142: Portal was created successfully but refreshing the portal list failed. You may try to refresh the portal list manually.
Cause: List refresh failed after creating portal.
Action: Manually refresh the portal list.

Level: 1

Type: ERROR

Impact: Other

WCS-05143: Errors were encountered in creating portal. The main error is - {0}. You may want to delete the current portal if it is visible in your lists. Contact the administrator if the problem persists.
Cause: Errors were seen in post-processing the create portal.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05144: Errors were encountered while creating the portal. The main error is - {0}. Rollback of the creation also failed. You may want to clean the current portal if it is visible in your lists. You may want to try to create the portal again later or contact the administrator.
Cause: Error in post-processing the portal.
Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05145: Portal created with the following warning(s) : {0}
Cause: Portal was created with warnings.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05146: Unexpected errors in deleting the portal. Contact Administrator.
Cause: Unexpected error in deleting the portal.
Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05147: Deletion of the portal resulted in errors. The main error is - {0}. You may want to try deleting the portal again later. If the error persists, contact the administrator.
Cause: Delete of the portal resulted in error.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05148: Deletion of portal resulted in errors. The main error is - {0}. Rollback of the deletion failed as well. You may want to try deleting the portal again later. If the error persists, contact the administrator.
Cause: Delete of the portal resulted in error.
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05149: Portal was deleted successfully but refreshing the portal list failed. You may try to refresh the portal list manually.
Cause: List refresh failed after deleting portal.
Action: You can refresh the portal list manually.

Level: 1

Type: ERROR

Impact: Other

WCS-05150: Unexpected errors in renaming the portal. Contact Administrator.
Cause: Unknown errors in renaming the portal.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05151: Rename of the portal resulted in errors. The main error is - {0}. You may want to try to rename the portal again later. If the error persists, contact the administrator.
Cause: Rename of the portal resulted in error.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05152: Rename of the portal resulted in errors. The main error is - {0}. Rollback of renaming also failed. You may want to try to rename the portal again later or contact the administrator.
Cause: Portal was renamed but there were errors in processing.
Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05153: Portal was renamed successfully but refreshing the portal list failed. You may try to refresh the portal list manually.
Cause: Refreshing the list after renaming the portal failed.
Action: Manually refresh the list of portals.

Level: 1

Type: ERROR

Impact: Other

WCS-05154: Portal was renamed with warnings. These are some of the warnings - {0}.
Cause: Portal was renamed with warnings.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05155: Unexpected error in retrieving the portal list.
Cause: Unexpected error in retrieving the portal list.
Action: Try again after some time. If problem persist, contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05156: Unexpected error while provisioning some optional services in the portal. You may want to provision them again by going to portal Administration.
Cause: Unexpected error while provisioning some optional services in the portal.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05157: Provisioning some optional services {0} in the portal did not go through successfully. You may want to provision them again by going to portal Administration.
Cause: Provisioning some optional services in the portal did not go through successfully.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05158: Unexpected error while unprovisioning the services.
Cause: Unexpected error in unprovisioning the services.
Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05159: Portal was deleted with warnings. These are some of the warnings - {0}.
Cause: Portal was renamed with warnings.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05160: Unexpected errors while granting user access on new portal {0}. Please contact Administrator.
Cause: Unexpected errors while granting access on new portal {0}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05161: Unexpected errors while removing access on new portal {0}. Please contact Administrator.
Cause: Unexpected errors while removing access on new portal {0}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05162: Unknown error while removing access for portal {0}
Cause: Unexpected errors while removing access on portal {0}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05163: Unknown error while mapping access for the new portal {0}
Cause: Unexpected errors while mapping access on portal {0}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05164: Unexpected errors in provisioning services for new portal {0}
Cause: Unexpected errors in provisioning services for new portal {0}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05165: Unknown error while reprovisioning services since delete failed for portal {0}
Cause: Unexpected errors while reprovisioning services on portal {0}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05166: Unknown error while creating metadata for new template {0}
Cause: Unexpected errors while copying metadata from portal {0} to template {1}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05167: Unknown error in creating metadata for the new portal {0}
Cause: Unexpected errors while creating metadata for portal {0}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05168: Unknown error in renaming the portal.
Cause: Unexpected errors in renaming the portal.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05169: Unknown error in renaming services from portal {0} to portal {1}.
Cause: Unexpected errors in renaming the services.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05170: Updates or deletes are being performed on portal {0} by another Portal Manager. Please try again after some time.
Cause: Portal {0} is already being deleted.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05171: Error occurred while trying to determine if service {0} is provisioned in the current portal.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05172: The role {0} does not exist and hence could not be assigned to the user {1}.
Cause: Role {0} may have already been deleted .
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05173: Error occurred while trying to modify the role for user {0}.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05174: Error occurred while accessing footer information.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05175: Portal {0} already exists.
Cause: Name specified for the portal was not unique. A portal with the same name already exists.
Action: Provide a unique name for the portal.

Level: 1

Type: ERROR

Impact: Other

WCS-05176: Portal name must contain at least one alphanumeric character
Cause: Portal name did not contain any alphanumeric characters
Action: Provide at least one alphanumeric character for portal name.

Level: 1

Type: ERROR

Impact: Other

WCS-05177: Unable to perform the operation on the selected portal(s) due to unknown errors
Cause: Selection of portal(s) failed
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05178: Failed to refresh the portal list due to unknown errors
Cause: Unknown error occurred while trying to refresh the portal list
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05179: Unable to perform the operation on the selected portal template(s) due to unavoidable errors
Cause: Selection of portal template(s) failed
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05180: An error occurred while trying to delete the portal template(s).
Cause: Selection of portal template(s) failed
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05181: Error while creating portal
Cause: Error occurred during portal creation
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05182: Error in closing the Create Portal dialog.
Cause: Error occurred while closing the Create Portal dialog
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05183: Another user is modifying the settings. Please try after some time.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05184: Unable to delete selected portal(s).
Cause: Selection of portal(s) failed
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05185: Unable to export selected portal(s) due to unknown errors
Cause: Selection of portal(s) failed
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05186: Error occurred while checking existing status of portal {0}.
Cause: An unexpected error occurred while checking existing status of the portal.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05187: Error occurred while retrieving portal {0} creation date
Cause: An unexpected error occurred while retrieving the portal creation date.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05188: Error occurred while retrieving portal {0} status changed date.
Cause: An unexpected error occurred while retrieving the portal status changed date.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05189: Failed to validate the name/display name
Cause: Failed to validate the name/display name
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05190: An error occurred in post-processing the invite for {0} in portal {1}. Please contact Administrator.
Cause: Unable to cleanup invited status metadata
Action: Please contact Administrator for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-05191: Unexpected error occurred while saving the portal changes.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05192: Unexpected error occurred while making portal public.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05193: Unexpected error retrieving data for the Portal Switcher.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05194: Portal template {0} based on portal {1} created successfully with the errors.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05195: Portal template {0} deletion failed due to concurrent operation performed on the same resource by some other user.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05197: Portal mail ID is not available because the Mail service is not configured.
Cause: Portal mail ID is not available because the Mail service is not configured.
Action: Contact the administrator to configure the Mail service.

Level: 1

Type: ERROR

Impact: Other

WCS-05198: Failed to initialize cache for portal template {0}.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05200: Failed to update cache for portal template {0}.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05201: Unknown error occurred while processing the templates.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05202: User was added but could not be notified due to some errors.
Cause: The BPEL server may be down.
Action: Ensure BPEL server is up and retry.

Level: 1

Type: ERROR

Impact: Other

WCS-05203: Template name must contain at least one alphanumeric character
Cause: Template name did not contain any alphanumeric characters
Action: Provide at least one alphanumeric character for template name.

Level: 1

Type: ERROR

Impact: Other

WCS-05204: Portal display name cannot be null.
Cause: Portal display name was blank.
Action: Enter a valid alphanumeric name for the portal display name

Level: 1

Type: ERROR

Impact: Other

WCS-05205: Portal display name is a reserved keyword. One of: {0}
Cause: The portal display name specified was a reserved keyword
Action: Specify a valid alphanumeric name for the portal display name which excludes the following reserved keywords: admin, builder, group, groups, home, last, page, pages, my portals, my spaces, portal, portals, spaces, space, system, webcenter, webcenter administration, webcenter portal,webcenter portals, webcenter space, webcenter spaces.

Level: 1

Type: ERROR

Impact: Other

WCS-05206: The portal name contains invalid characters.
Cause: Portal display name contained non-alphanumeric/space characters.
Action: Specify a valid alphanumeric name for the portal display name that only contains a-z, A-Z, 0-9, _, or a space character

Level: 1

Type: ERROR

Impact: Other

WCS-05207: The portal name must contain at least one letter or number.
Cause: Portal display name did not contain any alphanumeric characters
Action: Provide at least one alphanumeric character for portal display name.

Level: 1

Type: ERROR

Impact: Other

WCS-05208: Select at least one portal to change state/status of portal.
Cause: No portal has been selected or changing the state.
Action: Select at least one portal.

Level: 1

Type: ERROR

Impact: Other

WCS-05209: There are no templates available for creating the portal(s). You should refresh the list of templates by going to the Portal Templates page or create new templates or publish available templates if any to continue creating portal(s). If the problem persists, contact system administrator
Cause: No templates available for creating portal.
Action: Create new templates or publish existing templates if any.

Level: 1

Type: ERROR

Impact: Other

WCS-05210: Unknown error occurred while initiating creation of a portal.
Cause: Unable to launch the Create Portal dialog.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05211: Unknown error occurred while retrieving the list of templates.
Cause: Unknown error occurred while retrieving the list of templates.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05212: User {0} not authorized to perform the operation {1}:{2}
Cause: User {0} not authorized to perform the operation {1}:{2}
Action: User {0} not authorized to perform the operation {1}:{2}

Level: 1

Type: ERROR

Impact: Other

WCS-05213: Unexpected Error occurred while performing the method {0}. Contact system administrator.
Cause: Unexpected Error occurred while performing the method {0}.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05214: Unable to retrieve information about {0} as another user is modifying the {0}. Please try again after some time.
Cause: Cannot retrieve metadata for portal {0} as another user is modifying the settings. Please try after some time.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05215: User(s) added successfully, but sending notification to the user(s) failed
Cause: The BPEL server may be down.
Action: Ensure BPEL server is up and retry.

Level: 1

Type: ERROR

Impact: Other

WCS-05216: User was removed successfully, but sending notification to the user failed
Cause: The BPEL server may be down.
Action: Ensure BPEL server is up and retry.

Level: 1

Type: ERROR

Impact: Other

WCS-05217: User role was modified successfully, but sending notification to the user failed
Cause: The BPEL server may be down.
Action: Ensure BPEL server is up and retry.

Level: 1

Type: ERROR

Impact: Other

WCS-05218: Unknown error occurred while navigating to portal {0}.
Cause: Unable to navigate to the portal.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05219: Try accessing the portal from the Portal Switcher menu or the Portal page if the portal creation resulted in warnings. If the portal is not listed, refresh the list. If the portal is still not visible, report the error to your administrator. If the portal creation resulted in error, try deleting the portal if it is visible or else request the administrator to delete the portal
Cause: You can try accessing the portal from the Portal Switcher menu or the Portal page. If the portal is not listed, try refreshing the listing on the Portal page.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05220: Deletion or Rename is being performed on portal {0} by another Portal Manager. Refresh the list of portals and try again after some time.
Cause: Portal {0} is already being deleted or renamed.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05221: An unexpected error occurred while trying to delete portal template. Try again after some time. If the problem persists, contact administrator.
Cause: An unexpected error occurred while trying to delete portal template.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05222: Some optional services in the portal could not be provisioned as they were disabled. You may want to provision them again by going to portal Administration.
Cause: Unexpected error while provisioning some optional services in the portal.
Action: Contact Administrator and look in the logs for information about the specific service that has been disabled.

Level: 1

Type: ERROR

Impact: Other

WCS-05223: Admin Role does not exist in the policy store for portal {0}, so creating it
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-05224: Unexpected error occurred while revoking portal public status.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05225: Cannot retrieve the portal distribution list for {0} due to {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-05226: Cannot retrieve the portal managers list for {0} due to {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-05227: Cannot retrieve the Webcenter Portal administrators list due to {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-05228: Unable to send change membership notification. The reason is : {0}.
Cause: The BPEL URL has not been configured yet.
Action: Notify your administrator that the BPEL service supporting portal subscription is not configured

Level: 1

Type: ERROR

Impact: Other

WCS-05229: Cannot retrieve portal workflow configuration. Please contact your administrator.
Cause: The BPEL URL has not been configured yet.
Action: Notify your administrator that the BPEL service supporting portal subscription is not configured

Level: 1

Type: ERROR

Impact: Other

WCS-05230: An error occurred while searching invited user {0} in portal {1}. Contact your administrator.
Cause: Unable to search invited status metadata
Action: Contact your administrator for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-05231: Cannot retrieve user {0} email ID in portal {1} due to {2}
Cause: Failed to retrieve email id due to {2}
Action: Contact your administrator for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-05232: Template publishing role does not exist in the policy store for portal {0}, so creating it
Cause: Copy of the role failed, now trying to sanitize the portal security data
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-05233: Sanitizing template {0} failed unable to copy the publish data
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-05234: WebCenter Portal is not configured with BPEL server information.
Cause: BPEL server is not configured.
Action: Contact your administrator for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-05235: WebCenter Portal is not properly configured with the required BPEL server information.
Cause: BPEL server information is not correct.
Action: Contact your administrator for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-05236: BPEL server is either down or not properly configured.
Cause: Either the BPEL server is down or the portal workflows are not configured properly
Action: Contact your administrator for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-05237: Unexpected error occurred rebuilding the user portals list.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05238: Unexpected error occurred rebuilding the public portals list.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05239: Unable to retrieve portal tags.
Cause: An error occurred while trying to retrieve the tags for portal.
Action: Please contact Administrator for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-05240: Unable to create portal tags.
Cause: An error occurred while trying to create the tags for portal.
Action: Please contact Administrator for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-05241: Error occurred while getting portal activity streaming preferences.
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-05242: Error occurred while fetching the portal members information.
Cause: Error occurred while fetching the portal members information.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-05243: Unexpected error deriving {0} list.
Cause: An unexpected error occurred.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05244: The member's current role is selected. If you want to change this member's role, choose another role from the list.
Cause: The new role is same as the old role.
Action: Select new role.

Level: 1

Type: ERROR

Impact: Other

WCS-05246: Unexpected error persisting portal information to tables
Cause: Error saving portal information to the database
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-05247: Unable to retrieve mail ID for the portal.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05248: Unable to find security policy store metadata while creating portal template {0}
Cause: An error was detected in the application's configuration.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05249: Unexpected error occurred fetching ratings table from repository.
Cause: An unexpected error occurred fetching the bulk ratings table from the repository.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05250: Unable to delete portal {0} as either it is being exported or imported. Please refresh the list portals list and try again later.
Cause: Attempt to delete portal {0} when the portal is being exported/imported.
Action: Try delete after sometime. Contact the administrator if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05251: Unable to delete the portal template {0} as either it is being exported or imported. Please refresh the portal templates list and try again later.
Cause: Attempt to delete portal template {0} when the portal is being exported/imported.
Action: Try delete after sometime. Contact the administrator if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05252: Unexpected error in getting information from users table
Cause: Error in getting information from the database
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-05253: Role {1} of a user {0} is changed successfully to Role {2}, with failures in some of the services {3}
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05254: Unexpected error occurred while refreshing the portal cache
Cause: Unexpected error occurred while refreshing the portal cache
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-05255: Unexpected error occurred while cleaning up some of the permissions
Cause: Failed to clean up the policies post portal creation due to unexpected error
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-05256: Error while deleting security metadata for portal {0}.
Cause: An unexpected error occurred while deleting security metadata for portal. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-05267: Error while deleting security metadata for portal template {0}.
Cause: An unexpected error occurred while deleting security metadata for portal template. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-05268: Error occurred while fetching the portal data.
Cause: Error occurred while fetching the portal data.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05269: Error occurred while fetching the portal template data.
Cause: Error occurred while fetching the portal template data.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05270: You can add only a total of {0} items including subportals to the selected set. Remove items from selected set and try to add again.
Cause: Limit of selected set exceeded.
Action: Remove items from selected set and add again.

Level: 1

Type: ERROR

Impact: Other

WCS-05271: Please select one or more row to add.
Cause: No rows selected to add.
Action: Select one or more rows and add again.

Level: 1

Type: ERROR

Impact: Other

WCS-05272: Unexpected errors while granting user access on new portal template {0}. Please contact Administrator.
Cause: Unexpected errors while granting access on new group template : {0}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05273: Unknown error in removing access for the portal template {0}
Cause: Unexpected errors while removing access on portal template {0}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05274: Unable to find the security management lock for template {0}
Cause: Unable to find the security management lock for template {0}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05275: Unexpected errors in provisioning services for new portal template {0}
Cause: Unexpected errors in provisioning services for new portal template {0}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05276: Unknown error in reprovisioning services since delete failed for portal template {0}
Cause: Unexpected errors while reprovisioning services on portal template {0}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05277: Unknown error in mapping access for the new portal template {0}
Cause: Unexpected errors while mapping access on portal template {0}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05278: Portal template {0} already exists.
Cause: Name specified for the portal template was not unique. A portal template with the same name already exists.
Action: Provide a unique name for the portal template.

Level: 1

Type: ERROR

Impact: Other

WCS-05279: Unexpected error while rolling back the template during {0}
Cause: Error in rolling back the plugin.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05280: Creation of portal template resulted in error. Rollback of the create template failed as well. The main error is - {0}. You may delete the template if it is available in the list as this template is in unusable state.
Cause: Error in rolling back the plugin.
Action: Try deleting this template if it is available on the Portale Templates page.

Level: 1

Type: ERROR

Impact: Other

WCS-05281: Rollback of portal template metadata also resulted in error. The main error is - {0}. Try deleting the template from the Portal Templates page if it is available as this template is in unusable state.
Cause: Error in deleting the template metadata.
Action: Try deleting this template if it is available on the Portal Templates page.

Level: 1

Type: ERROR

Impact: Other

WCS-05282: Unexpected errors in deleting the portal template. Contact Administrator.
Cause: Unexpected error in deleting the portal template.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05283: Deletion of the portal template resulted in errors. The main error is - {0}. You may want to try again later. If the error persists, contact the administrator.
Cause: Delete of the portal template resulted in error.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05284: Deletion of portal template resulted in errors. Rollback of the deletion failed as well. The main error is -{0}. You may want to try again later. If the error persists, contact the administrator.
Cause: Delete of the portal template resulted in error.
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05285: Portal template was deleted successfully but refreshing the portal template list failed. You may try to refresh the portal template list manually.
Cause: List refresh failed after deleting portal template.
Action: You can refresh the portal template list manually.

Level: 1

Type: ERROR

Impact: Other

WCS-05286: Updates or deletes are being performed on portal template {0} by another Portal Manager. Please try again after some time.
Cause: Portal template {0} is already being deleted.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05287: Unexpected errors occurred while creating template {0}.
Cause: Unexpected errors occurred while creating template.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05288: Creation of template resulted in errors. The main error is - {0}. Try again after some time or contact administrator
Cause: Template creation resulted in errors.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05289: Unexpected error occurred while executing pre portal template creation due to {0}.
Cause: Unexpected error occurred while executing pre portal template creation due to {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05290: Base portal name cannot be null
Cause: Base portal name cannot be null
Action: Enter a value for base portal.

Level: 1

Type: ERROR

Impact: Other

WCS-05291: Error occurred while executing custom pre portal creation code due to {0}.
Cause: Error occurred while executing custom pre portal creation due to {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05292: Error occurred while executing custom post portal creation code due to {0}.
Cause: Error occurred while executing custom post portal creation due to {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05293: Error occurred while executing custom pre portal deletion code due to {0}.
Cause: Error occurred while executing custom pre portal deletion due to {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05294: Error occurred while executing custom post portal deletion code due to {0}.
Cause: Error occurred while executing custom post portal deletion due to {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05295: Error occurred while executing custom pre portal rename code due to {0}.
Cause: Error occurred while executing custom pre portal rename due to {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05296: Error occurred while executing custom post portal rename code due to {0}.
Cause: Error occurred while executing custom post portal rename due to {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05297: Error occurred while executing custom pre portal template creation code due to {0}.
Cause: Error occurred while executing custom pre portal template creation due to {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05298: Error occurred while executing custom post portal template creation code due to {0}.
Cause: Error occurred while executing custom post portal template creation due to {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05299: Portal template created with the following warning(s) : {0}
Cause: Portal was created with warnings.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05300: Error occurred while executing custom pre portal template deletion code due to {0}.
Cause: Error occurred while executing custom pre portal template deletion due to {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05301: Error occurred while executing custom post portal template deletion code due to {0}.
Cause: Error occurred while executing custom post portal template deletion due to {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05302: Unexpected error occurred while executing pre portal creation due to {0}.
Cause: Unexpected error occurred while executing pre portal creation due to {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05303: Unable to add {0} as it conflicts with another portal on target application.
Cause: Conflict cannot be imported.
Action: Deselect the conflict row and add again.

Level: 1

Type: ERROR

Impact: Other

WCS-05309: Unexpected error occurred during updating template {0}
Cause: Unexpected error occurred during updating template {0}
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05310: Template Display Name is null
Cause: Template Display Name is null.
Action: Enter valid values.

Level: 1

Type: ERROR

Impact: Other

WCS-05311: Template display name is a reserved keyword. One of: {0}
Cause: The template display name specified was a reserved keyword
Action: Specify a valid alphanumeric name for the template display name which excludes the following reserved keywords: webcenter, pages, page, Spaces, Space, group, groups, Space, Spaces, webcenter Space, webcenter Spaces, webcenter Portal, WebCenter Portal, WebCenter Portal Spaces, portal, webcenter administration, my Spaces, admin, last.

Level: 1

Type: ERROR

Impact: Other

WCS-05312: The template display name contains invalid characters. Only alphanumeric and space characters are allowed.
Cause: Template display name contained non-alphanumeric/space characters.
Action: Specify a valid alphanumeric name for the template display name that only contains a-z, A-Z, 0-9, _, or a space character

Level: 1

Type: ERROR

Impact: Other

WCS-05313: Portal display name must contain at least one alphanumeric character
Cause: Portal display name did not contain any alphanumeric characters
Action: Provide at least one alphanumeric character for portal display name.

Level: 1

Type: ERROR

Impact: Other

WCS-05314: Portal template with display name {0} already exists.
Cause: Portal template with display name {0} already exists.
Action: Enter another display Name.

Level: 1

Type: ERROR

Impact: Other

WCS-05315: Unexpected error occurred while fetching template displayName {0}.
Cause: Template with display name {0} already exists.
Action: Enter another display Name.

Level: 1

Type: ERROR

Impact: Other

WCS-05316: Unexpected error occurred while creating role {0} for template {1}
Cause: Unexpected error occurred while creating role {0} for template {1}.
Action: Try again after some time or Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05317: Unexpected error occurred while saving members data from portal {0} to template {1}
Cause: Unexpected error occurred while saving members data from portal {0} to template {1}.
Action: Try again after some time or contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05318: Unexpected error occurred while copying member from template {0} to portal {1}
Cause: Unexpected error occurred while copying member {0} whose role {1} due to {3}.
Action: Try again after some time or Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05325: Parent portal cannot be null
Cause: Parent portal was null.
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05326: Failed to set parent portal
Cause: Error in setting parent portal
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05327: Unexpected error occurred while making the template {0} public.
Cause: Unexpected error occurred while making the template {0} public.
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05328: Unexpected error occurred while fetching the templates.
Cause: UUnexpected error occurred while fetching the templates.
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05329: Unexpected error occurred while deleting the template during overriding the template {0}.
Cause: Unexpected error occurred while deleting the template while overriding the template.
Action: Contact Administrator or Try again after some time

Level: 1

Type: ERROR

Impact: Other

WCS-05330: Unexpected error occurred while overriding the template {0}.
Cause: Unexpected error occurred while overriding the template.
Action: Contact Administrator or Try again after some time

Level: 1

Type: ERROR

Impact: Other

WCS-05331: Unexpected error occurred while saving the template permissions.
Cause: Unexpected error occurred while saving the template permissions.
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05332: Unexpected error occurred while fetching the supported languages for this portal.
Cause: Unexpected error occurred while fetching the supported languages.
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05333: Unexpected error occurred while launching the portal in edit mode.
Cause: Unexpected error occurred while launching the portal in edit mode.
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05334: This operation is not possible on multiple portals. Select one portal to proceed with the operation.
Cause: Unable to perform the operation on multiple portals.
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05335: Unexpected error occurred while launching the About Portal dialog.
Cause: Unexpected error occurred while launching the About Portal dialog.
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05336: Portal not specified
Cause: The supplied portal name was null or blank.
Action: Specify a valid portal name that is not null or blank.

Level: 1

Type: ERROR

Impact: Other

WCS-05337: Membership not changed for user {0}. You cannot manage your own membership.
Cause: Changing one's own membership in a portal is not allowed.
Action: Select users other than the current user to change their membership.

Level: 1

Type: WARNING

Impact: Other

WCS-05338: Unexpected error occurred while publishing portal template(s)
Cause: Unexpected error occurred while publishing portal template(s)
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05339: Unable to create portal as the template name is not specified.
Cause: Template is not selected.
Action: Select at least one template to create portal.

Level: 1

Type: ERROR

Impact: Other

WCS-05340: Unknown errors occurred while saving the cache for portal {0}, try setting the values again in the portal administration settings.
Cause: Error while saving cache.
Action: Retry again from Settings screen.

Level: 1

Type: ERROR

Impact: Other

WCS-05341: Portal display name must be less than 200 characters.
Cause: Portal display name exceeded 200 characters.
Action: Specify portal display name less than 200 characters.

Level: 1

Type: ERROR

Impact: Other

WCS-05342: Portal name must be less than 200 characters.
Cause: Portal name exceeded 200 characters.
Action: Specify portal name less than 200 characters.

Level: 1

Type: ERROR

Impact: Other

WCS-05343: Portal template display name must be less than 200 characters.
Cause: Portal template display name exceeded 200 characters.
Action: Specify portal template display name less than 200 characters.

Level: 1

Type: ERROR

Impact: Other

WCS-05344: Portal template name must be less than 200 characters.
Cause: Portal template name exceeded 200 characters.
Action: Specify portal template name less than 200 characters.

Level: 1

Type: ERROR

Impact: Other

WCS-05345: Keywords must be less than 4000 characters.
Cause: Keywords exceeded 4000 characters.
Action: Specify keywords less than 4000 characters.

Level: 1

Type: ERROR

Impact: Other

WCS-05346: Description must be less than 4000 characters.
Cause: Description exceeded 4000 characters.
Action: Specify description less than 4000 characters.

Level: 1

Type: ERROR

Impact: Other

WCS-05347: Select at least one portal to continue the operation.
Cause: Select at least one portal to continue.
Action: Select at least one portal to continue.

Level: 1

Type: ERROR

Impact: Other

WCS-05348: Unexpected error occurred while publishing following portal template(s) {0}
Cause: Unexpected error occurred while publishing following portal template(s) {0}
Action: Contact Administrator or try again after some time.

Level: 1

Type: ERROR

Impact: Other

WCS-05349: Unexpected error occurred while launching Rename dialog
Cause: Unexpected error occurred while launching Rename dialog
Action: Contact Administrator or try again after some time.

Level: 1

Type: ERROR

Impact: Other

WCS-05350: Unexpected error occurred while launching Set Access dialog
Cause: Unexpected error occurred while launching Set Access dialog
Action: Contact Administrator or try again after some time.

Level: 1

Type: ERROR

Impact: Other

WCS-05351: Unexpected error occurred while unpublishing portal template(s)
Cause: Unexpected error occurred while unpublishing portal template(s)
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05352: Unexpected error occurred while unpublishing following portal template(s) {0}
Cause: Unexpected error occurred while unpublishing following portal template(s) {0}
Action: Contact Administrator or try again after some time.

Level: 1

Type: ERROR

Impact: Other

WCS-05353: Select at least one portal to copy data to template.
Cause: Select at least one portal to copy data to template.
Action: Select at least one portal to copy data to template.

Level: 1

Type: ERROR

Impact: Other

WCS-05354: Portal template metadata {0} not found.
Cause: Portal template metadata not found.
Action: Portal template metadata not found.

Level: 1

Type: ERROR

Impact: Other

WCS-05355: Unable to set parent for one or more selected portal(s).
Cause: Failed to set parent for selected portal(s)
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05356: The new parent {0} specified cannot be a child portal in the hierarchy of {1}.
Cause: The new parent {0} is a child portal in the hierarchy of {1}.
Action: Choose a different parent portal

Level: 1

Type: ERROR

Impact: Other

WCS-05357: The new parent is one of the selected portals for reparenting. Choose a different parent
Cause: The new parent {0} is one of the selected portal for reparenting.
Action: Choose a different parent portal

Level: 1

Type: ERROR

Impact: Other

WCS-05358: The new parent and child portal cannot be same
Cause: The new parent and child portal specified are same.
Action: Choose a different parent portal

Level: 1

Type: ERROR

Impact: Other

WCS-05359: The URL contains invalid characters
Cause: Value entered in the url is not proper
Action: Only the following characters are allowed: A-Z, a-z, 0-9, _

Level: 1

Type: ERROR

Impact: Other

WCS-05360: The URL contains non-English characters
Cause: Non-ascii, multibyte characters entered in the pretty URL
Action: Only English names and ascii characters are supported

Level: 1

Type: ERROR

Impact: Other

WCS-05361: Error occurred while fetching the custom attributes
Cause: An unexpected error occurred while fetching the custom attribute.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05362: The archive that you are trying to import is not a valid {0} archive. Refer to the Spaces diagnostic log file for more information or contact your system administrator.
Cause: The supplied file to import was not a valid archive.
Action: Retry the import operation with a valid archive.

Level: 1

Type: ERROR

Impact: Other

WCS-05363: The URL contains invalid characters. Permitted characters: A-Z, a-z, 0-9, _
Cause: Value entered in the url is not proper
Action: Only the following characters are allowed: A-Z, a-z, 0-9, _

Level: 1

Type: ERROR

Impact: Other

WCS-05364: The portal template name contains non-English characters
Cause: Non-ascii, multibyte characters entered in the pretty URL
Action: Only English names and ascii characters are supported

Level: 1

Type: ERROR

Impact: Other

WCS-05365: Membership not changed for group {0}. You cannot manage the membership of this group because your own membership is granted through this group. Only direct members who have manage permission can manage the membership of groups.
Cause: Changing one's own membership in a portal is not allowed.
Action: Select users other than the current user to change their membership.

Level: 1

Type: WARNING

Impact: Other

WCS-05366: Unexpected error occurred while fetching list of all portals
Cause: Unexpected error occurred while fetching list of all portals
Action: Unexpected error occurred while fetching list of all portals

Level: 1

Type: ERROR

Impact: Other

WCS-05367: Unable to display the list of portals you have access on due to unexpected errors. Try again after some time or contact administrator if the problem persists.
Cause: Unexpected error occurred while fetching list of all portals
Action: Unexpected error occurred while fetching list of all portals

Level: 1

Type: ERROR

Impact: Other

WCS-05368: Portal GUID not specified
Cause: The supplied portal GUID was null or blank.
Action: Specify a valid portal GUID that is not null or blank.

Level: 1

Type: ERROR

Impact: Other

WCS-05369: Portal not found
Cause: The system could not find the specified portal.
Action: Specify a valid portal.

Level: 1

Type: ERROR

Impact: Other

WCS-05370: Internal handler error
Cause: The internal handler for portal {0} failed.
Action: Refer to logs for more information and contact the administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05371: The list of portal name passed was null
Cause: The list of portal names passed to fetch the metadata was empty.
Action: Pass a valid list of values.

Level: 1

Type: ERROR

Impact: Other

WCS-05372: The customizations available in portal template {1} were not copied to portal {0} since that process was interrupted.
Cause: Thread executing the customization document copy has been cancelled.
Action: Retry this option using mds export/import wlst commands.

Level: 1

Type: ERROR

Impact: Other

WCS-05373: The customizations available in portal template {1} were not copied to portal {0} since that process has timed-out.
Cause: Thread executing the customization document copy has been timed out
Action: Retry this option using mds export/import wlst commands.

Level: 1

Type: ERROR

Impact: Other

WCS-05374: The customizations available in portal template {1} were not copied to portal {0} due to unexpected errors.
Cause: Thread executing the customization document copy has failed to unexpected errors
Action: Retry this option using mds export/import wlst commands.

Level: 1

Type: ERROR

Impact: Other

WCS-05375: The customizations available in portal {1} were not copied to portal template {0} since that process was interrupted.
Cause: Thread executing the customization document copy has been cancelled.
Action: Retry this option using mds export/import wlst commands.

Level: 1

Type: ERROR

Impact: Other

WCS-05376: The customizations available in portal {1} were not copied to portal template {0} since that process has timed-out.
Cause: Thread executing the customization document copy has been timed out
Action: Retry this option using mds export/import wlst commands.

Level: 1

Type: ERROR

Impact: Other

WCS-05377: The customizations available in portal {1} were not copied to portal template {0} due to unexpected.
Cause: Thread executing the customization document copy has failed to unexpected errors
Action: Retry this option using mds export/import wlst commands.

Level: 1

Type: ERROR

Impact: Other

WCS-05378: Unable to launch About Portal Template dialog.
Cause: Unable to launch About Portal Template dialog.
Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

WCS-05379: Unable to perform the operation on multiple portal templates.
Cause: Unable to perform the operation on multiple portal templates.
Action: Select a single portal template only and retry the operation

Level: 1

Type: ERROR

Impact: Other

WCS-05380: Select at least one portal template to continue the operation.
Cause: Select at least one portal template to continue.
Action: Select at least one portal template to continue.

Level: 1

Type: ERROR

Impact: Other

WCS-05381: User {0} does not have permission to view portal {1}.
Cause: User {0} does not have permission to view portal {1}.
Action: User {0} does not have permission to view portal {1}.

Level: 1

Type: ERROR

Impact: Other

WCS-05382: User {0} does not have permission to manage portal {1}.
Cause: User {0} does not have permission to manage portal {1}.
Action: User {0} does not have permission to manage portal {1}.

Level: 1

Type: ERROR

Impact: Other

WCS-05383: User {0} does not have the permission to create portal {1}.
Cause: User {0} does not have the permission to create the portal.
Action: User {0} does not have the permission to create the portal.

Level: 1

Type: ERROR

Impact: Other

WCS-05384: User {0} does not have the permission to view the portal template {1}.
Cause: User {0} does not have the permission to view the portal template {1}.
Action: User {0} does not have the permission to view the portal template {1}.

Level: 1

Type: ERROR

Impact: Other

WCS-05385: User {0} does not have permission to create portal template.
Cause: User {0} does not have permission to create portal template.
Action: User {0} does not have permission to create portal template.

Level: 1

Type: ERROR

Impact: Other

WCS-05386: User {0} does not have permission to manage portal template {1}.
Cause: User {0} does not have permission to manage portal template {1}.
Action: User {0} does not have permission to manage portal template {1}.

Level: 1

Type: ERROR

Impact: Other

WCS-05387: User {0} does not have permission to edit portal {1}.
Cause: User {0} does not have permission to edit portal {1}.
Action: User {0} does not have permission to edit portal {1}.

Level: 1

Type: ERROR

Impact: Other

WCS-05388: Unexpected error occurred while creating portal {0} from portal template {1}. Try again after some time. If the problem persists, contact Administrator
Cause: Unexpected error occurred while creating portal {0} from portal template {1}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05389: User {0} does not have permission to manage security of portal {1}.
Cause: User {0} does not have permission to manage security of portal {1}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05390: Unexpected error occurred while deleting portal {0}. Try again after some time. If the problem persists, contact Administrator.
Cause: Unexpected error occurred while deleting portal {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05391: Unexpected error occurred while creating portal template {1} from portal {0}. Try again after some time. If the problem persists, contact Administrator.
Cause: Unexpected error occurred while creating portal template {1} from portal {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05392: Unexpected error occurred while deleting portal template {0}. Try again after some time. If the problem persists, contact Administrator.
Cause: An unexpected error occurred while deleting portal template {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05393: User {0} is not authorized to refresh Portal cache.
Cause: User {0} is not authorized to refresh Portal cache.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05394: An unexpected error occurred while creating portal preference metadata.
Cause: An unexpected while creating portal preference metadata.
Action: Contact the administrator or try again later.

Level: 1

Type: ERROR

Impact: Other

WCS-05395: User {0} does not have permission to view portal {0}, the portal is not discoverable, and self-subscription is not enabled.
Cause: User {0} does not have permission to view portal {0}, the portal is not discoverable, and self-subscription is not enabled.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05396: An unexpected error occurred while trying to drop the role {0} in portal {1}.
Cause: An unexpected error occurred while trying to drop the role {0} in portal {1}.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05397: An unexpected error occurred while trying to set welcome message {0} for invited non-member in portal {1}.
Cause: An unexpected error occurred while trying to set welcome message {0} for invited non-member in portal {1}.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05398: An unexpected error occurred while trying to set welcome message {0} for invited member in portal {1}.
Cause: An unexpected error occurred while trying to set welcome message {0} for invited member in portal {1}.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05399: An unexpected error occurred while trying to set add member message {0} in portal {1}.
Cause: An unexpected error occurred while trying to set add member message {0} in portal {1}.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05400: An unexpected error occurred while trying to get portal members.
Cause: An unexpected error occurred while trying to get portal members.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05401: Changing role for invited members, is not supported.
Cause: Changing role for invited members, is not supported.
Action: For changing the role of Invited Members, delete the existing invite for the member and invite the member again with the new role.

Level: 1

Type: WARNING

Impact: Other

WCS-05402: Unexpected error occurred while deleting the customization documents for portal {0}.
Cause: Unexpected error occurred while deleting the customization documents for portal {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05403: Unexpected error occurred while getting Parent Display Name for portal {0} due to {1}.
Cause: Unexpected error occurred while getting Parent Display Name for portal {0} due to {1}.
Action: Contact Administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-05404: Unexpected error occurred while getting URL of parent portal for portal {0} due to {1}.
Cause: Unexpected error occurred while getting URL of parent portal for portal {0} due to {1}.
Action: Contact Administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-05405: Unexpected error occurred while deleting the package containing assets for portal {0}.
Cause: Unexpected error occurred while deleting the package containing generic-site-resources documents for portal {0}.
Action: Contact Administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-05406: Unable to create portal as a portal with the URL or display name {0} already exists.
Cause: A portal with the specified URL or display name already exists.
Action: Specify a unique UURL or display name for the portal.

Level: 1

Type: WARNING

Impact: Other

WCS-05407: Unable to create portal as portal name is a reserved keyword. One of: {0}
Cause: The portal name specified was a reserved keyword.
Action: Specify a valid alphanumeric name for the portal which excludes the following reserved keywords: webcenter, pages, page, Spaces, Space, group, groups, Space, Spaces, webcenter Space, webcenter Spaces, webcenter Portal, WebCenter Portal, WebCenter Portal Spaces, portal, webcenter administration, my Spaces, admin, last.

Level: 1

Type: ERROR

Impact: Other

WCS-05408: Unable to create portal as portal display name is a reserved keyword. One of: {0}
Cause: The portal display name specified was a reserved keyword
Action: Specify a valid alphanumeric name for the portal display name which excludes the following reserved keywords: webcenter, pages, page, Spaces, Space, group, groups, Space, Spaces, webcenter Space, webcenter Spaces, webcenter Portal, WebCenter Portal, WebCenter Portal Spaces, portal, webcenter administration, my Spaces, admin, last.

Level: 1

Type: ERROR

Impact: Other

WCS-05409: Simulated error condition during creation of portal {0} for internal test purposes.
Cause: Simulated error condition during creation of portal {0} for internal test purposes.
Action: This is just for negative tests.

Level: 1

Type: ERROR

Impact: Other

WCS-05410: Unexpected error occurred while deleting the portal template(s) {0}
Cause: Unexpected error occurred while deleting following portal template(s) {0}
Action: Contact Administrator or try again after some time.

Level: 1

Type: ERROR

Impact: Other

WCS-05411: Couldn''t get the first accessible page for portal {0} due to {1}.
Cause: Error in getting the first accessible page for the portal.
Action: Contact the application administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-05412: Unexpected error occurred in setting {0} as parent of portal {1} due to {2}.
Cause: Error in setting the parent portal.
Action: Contact the application administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05413: Unexpected error while setting the parent to {0} due to {1}.
Cause: Error in setting the parent and security parent for the scope
Action: Contact the application administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05414: User {0} is not authorized to generate site maps for this site.
Cause: User {0} is not authorized to generate site maps for this site.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05415: Unexpected error while getting the site map index.
Cause: Error in getting the site map index.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05416: Unexpected error while getting the site map for portal {0}.
Cause: Error in getting the portal site map.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05417: Unexpected error while generating the site map.
Cause: Error while generating the site map.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05418: Unexpected error while generating the site map for portal {0}.
Cause: Error while generating the portal site map.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05419: Unexpected error while updating the site map for portal {0}.
Cause: Error while updating the site map.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05420: Unexpected error occurred while deleting the portal entry from default portal metadata due to {0}.
Cause: Error while deleting the portal from default portal metadta.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05421: Unexpected error occurred while renaming the portal entry from default portal metadata due to {0}.
Cause: Error while renaming the portal from default portal metadta.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05422: Error fetching parent space for space {0} due to {1}
Cause: Error occurred while fetching parent space.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05423: Unexpected error occurred while fetching the Portal Manager list for space{0} due to {1}
Cause: Error occurred while fetching the list of Portal Managers.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05424: Attribute value not specified
Cause: Attribute value cannot be null or blank.
Action: Please enter a valid value.

Level: 1

Type: WARNING

Impact: Other

WCS-05425: Attribute name not specified
Cause: Attribute name cannot be null or blank.
Action: Please enter a valid name.

Level: 1

Type: WARNING

Impact: Other

WCS-05426: Failed to update last active time for user guid {0} with exception {1}.
Cause: Unexpected error while updating last active time for user guid {0} due to exception {1}.
Action: Contact the application administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-05427: Exceptions occurred while revoking role {1} for user {0} due to failures in some of the services {2}
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05428: Unexpected error occurred while revoking roles for member {0}. Refer to the diagnostic WebCenter Portal log file for more information or contact your system administrator.
Cause: Unexpected error occurred while deleting role(s).
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05429: User {0} cannot be removed from portal {1} because {0} is the only member assigned to the Portal Manager role in the portal.
Cause: You cannot remove a member from a portal if that member is the sole Portal Manager of the portal.
Action: Assign another member as the portal manager, then proceed to remove the current user.

Level: 1

Type: WARNING

Impact: Other

WCS-05430: Cannot delete portal {0} as the Portal API cannot find this portal.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05431: Cannot create portal {0} due to error encountered when creating Portal object.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05432: Cannot create portal {0} due to error encountered when updating Portal object.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05433: Cannot create portal {0} due to error encountered when updating Portal object - {0}.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05434: User {0} does not have the privileges required for deployment operation on Portals. Verify that the user has ''Create Portal'' permission while performing the deployment operation.
Cause: Verify that the user has Create Portal permission while performing the deployment operation.
Action: Try performing the operation as an administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05435: User {0} does not have the privileges required for deployment operation on portal {1}. Verify that the user has ''Manage Portal'' permission while performing the deployment operation.
Cause: Verify that the user has Manage Portal permission while performing the deployment operation.
Action: Try performing the operation as an administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05436: User {0} does not have the privileges required for deployment operation on Portals. Verify that the user has ''Deploy'' permission while performing the deployment operation.
Cause: Verify that the user has Deploy permission while performing the deployment operation.
Action: Try performing the operation as an administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05437: User {0} does not have the privileges required for propagation operation on portal {1}. Verify that the user has ''Manage Portal'' permission while performing the propagation operation.
Cause: Verify that the user has Manage Portal permission while performing the propagation operation.
Action: Try performing the operation as an administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05438: User {0} does not have the privileges required for propagation operation on Portals. Verify that the user has ''Deploy'' permission while performing the propagation operation.
Cause: Verify that the user has Deploy permission while performing the propagation operation.
Action: Try performing the operation as an administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05439: User {0} does not have the privileges required for import operation on Portals. Verify that the user has ''Create Portal'' permission while performing the import operation.
Cause: Verify that the user has Create Portal permission while performing the import operation.
Action: Try performing the operation as an administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05440: User {0} does not have the privileges required for import operation on Portals. Verify that the user has ''Deploy'' permission while performing the import operation to be able to import the shared assets.
Cause: Verify that the user has Deploy permission while performing the import operation to be able to import the shared assets.
Action: Try performing the operation as an administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05441: User {0} does not have the privileges required for this operation on portal {1}. Verify that the user has ''Manage Portal'' permission while performing the export, deployment or propagation operation.
Cause: Verify that the user has Manage Portal permission while performing the export, deployment or propagation operation.
Action: Try performing the operation as an administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05442: User {0} does not have the privileges required for this operation on Portals. Verify that the user has ''Deploy'' permission while performing the deployment or propagation operation to be able to export the shared assets.
Cause: Verify that the user has Deploy permission while performing the deployment or propagation operation to be able to export the shared assets.
Action: Try performing the operation as an administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05443: User {0} does not have the privileges required for this operation on Portal Templates.
Cause: Check if the user has required permission on Portal Templates for performing lifecycle operations.
Action: Try performing the operation as an administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05444: User {0} does not have the privileges required for this operation on the WebCenter Portal Server application.
Cause: Check if the user has required permission on WebCenter Portal Server application for performing lifecycle operations.
Action: Try performing the operation as an administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05445: User {0} does not have the privileges required for import operation on portal {1}. Verify that the user has ''Manage Portal'' permission while performing the import operation.
Cause: Verify that the user has Manage Portal permission while performing the import operation.
Action: Try performing the operation as an administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-05446: List of Members cannot be empty
Cause: Members List passed is empty.
Action: Please enter a valid value.

Level: 1

Type: WARNING

Impact: Other

WCS-05447: Role Name cannot be empty
Cause: Role Name is empty.
Action: Please enter a valid Role Name.

Level: 1

Type: WARNING

Impact: Other

WCS-05448: Base Role Name cannot be empty
Cause: Base Role Name is empty.
Action: Please enter a valid Base Role Name.

Level: 1

Type: WARNING

Impact: Other

WCS-05449: Portal Image URL cannot be empty
Cause: Portal Image URL is empty.
Action: Please enter a valid Image URL.

Level: 1

Type: WARNING

Impact: Other

WCS-05450: Attribute type not specified
Cause: Attribute type cannot be null or blank.
Action: Please enter a valid type.

Level: 1

Type: WARNING

Impact: Other

WCS-05451: New Portal name for rename not specified
Cause: New Portal Name cannot be null or blank.
Action: Please enter a valid Portal name.

Level: 1

Type: WARNING

Impact: Other

WCS-05452: Unexpected error occurred while performing the method {0}. Contact Administrator and check the logs for more details
Cause: Runtime error occurred while performing method {0}.
Action: Contact Administrator and check logs.

Level: 1

Type: WARNING

Impact: Other

WCS-05453: Unexpected error finding portal.
Cause: An error occuring when trying to retrieve a Portal object by its identifier.
Action: Check underlying exception for cause.

Level: 1

Type: WARNING

Impact: Other

WCS-05454: Unexpected error while trying to change membership of portal {0} due to {1}
Cause: The user roles may be invalid.
Action: Contact the portal manager for assistance and check logs.

Level: 1

Type: ERROR

Impact: Other

WCS-05455: Unexpected error while trying to subscribe a user to portal{0} due to {1}
Cause: The user roles may be invalid.
Action: Contact the portal manager for assistance and check logs.

Level: 1

Type: ERROR

Impact: Other

WCS-05701: Deleting portal {0} failed
Cause: WebService API failed to execute deleting web service call.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05702: Creating portal {0} failed
Cause: WebService API failed to execute create web service call.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05703: An error occurred while revoking the roles {1} for users in portal {0}
Cause: WebService API failed to execute revoke role web service call.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05704: An error occurred while granting roles for {1} users in portal {0}
Cause: WebService API failed to execute grant role web service call.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05705: Getting portal template {0} metadata failed
Cause: WebService API failed to execute get portal template metadata web service call.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05706: Getting portal metadata {0} failed
Cause: WebService API failed to execute get portal metadata web service call.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05707: Getting portals for search string {0} failed
Cause: WebService API failed to execute get spaces web service call.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05708: Getting portal templates for search string {0} failed
Cause: WebService API failed to execute get template web service call.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05709: Setting the Custom Attributes for scope {0} failed
Cause: WebService API failed to execute Custom Attributes.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05710: An error occurred while attempting to retrieve spaces web service endpoint configured in connections.xml of caller application
Cause: Unable to retrieve spaces web service endpoint configured in caller applications connections.xml
Action: Please check spaces web service endpoint configured in connections.xml

Level: 1

Type: ERROR

Impact: Other

WCS-05711: One of the arguments passed to API call {0} is null
Cause: A null argument was passed to an API call
Action: Ensure to invoke the API with non-null arguments

Level: 1

Type: ERROR

Impact: Other

WCS-05712: No portal name is provided
Cause: Portal name is not provided
Action: Ensure to invoke the API with non-null arguments

Level: 1

Type: ERROR

Impact: Other

WCS-05713: No portal template name is provided
Cause: Portal template name is not provided
Action: Ensure to invoke the API with non-null arguments

Level: 1

Type: ERROR

Impact: Other

WCS-05714: No portal user name is provided
Cause: Portal user name is not provided
Action: Ensure to invoke the API with non-null arguments

Level: 1

Type: ERROR

Impact: Other

WCS-05715: No portal role name is provided
Cause: Portal role name is not provided
Action: Ensure to invoke the API with non-null arguments

Level: 1

Type: ERROR

Impact: Other

WCS-05716: No portal custom attribute name is provided
Cause: Portal custom attribute name is not provided
Action: Ensure to invoke the API with non-null arguments

Level: 1

Type: ERROR

Impact: Other

WCS-05717: No portal custom attribute value is provided
Cause: Portal custom attribute value is not provided
Action: Ensure to invoke the API with non-null arguments

Level: 1

Type: ERROR

Impact: Other

WCS-05718: Error while setting the new end point for the space web services
Cause: Portal web services client already has an endpoint {0}
Action: It cannot be overridden at the runtime. Try setting it in connections.xml and restarting the application

Level: 1

Type: ERROR

Impact: Other

WCS-05719: Portal web service client is null
Cause: Portal web service client is null
Action: You need to set the context for the client and then initialize it

Level: 1

Type: ERROR

Impact: Other

WCS-05720: An unexpected error occurred while instantiating space web services client
Cause: Unable to create an instance of GroupSpaceWSClient
Action: Please verify the context parameters or contact administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05721: An error occurred when user {0} tried to accept invite for portal {2} with role {1}
Cause: Failed to execute acceptance of portal invite
Action: Check the parameters being passed to the acceptInvite API or contact administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05722: An error occurred when user {0} tried to reject the invite for portal {1}
Cause: Failed to execute rejection of portal invite
Action: Check the parameters being passed to the rejectInvite API or contact administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05723: An error occurred while fetching the roles for portal {0}
Cause: An error occurred while fetching the roles for portal {0}
Action: Contact administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05724: An error occurred while inviting {0} members to portal {1}
Cause: An error occurred while inviting the members to portal {1}
Action: Contact administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05725: An error occurred while creating the portal template {0} based on portal {1}
Cause: An error occurred while creating the portal template {0}
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05726: An error occurred while fetching the roles for portal template {0}
Cause: An error occurred while fetching the roles for portal template {0}
Action: Contact administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05727: The Service ID {0}, is invalid.
Cause: An error occurred while fetching the RSS Feed URL for the Service ID, {0}.
Action: Contact administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05728: An error occurred while checking if a login user {0} is a member of portal {1}
Cause: An error occurred while checking if a login user {1} is a member of portal {0}
Action: Contact administrator

Level: 1

Type: ERROR

Impact: Other

WCS-05729: Deleting portal template {0} failed
Cause: WebService API failed to execute deleting web service call.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05730: Search on portals for search string {0} failed
Cause: WebService API failed to execute search for portals.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05731: Creation of role {0} failed in portal {1}
Cause: WebService API failed to execute create role for portals.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05732: Dropping of role {0} failed in portal {1}
Cause: WebService API failed to execute drop role for portals.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05733: Failed to get role information for identity {0} in portal {1}
Cause: WebService API failed to get role information.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05734: Failed to get member information for portal {0}
Cause: WebService API failed to get member information.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05735: Search on portal templates for search string {0} failed
Cause: WebService API failed to execute search for portal template.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05736: No image URL is provided
Cause: Image URL is not provided
Action: Ensure to invoke the API with non-null arguments

Level: 1

Type: ERROR

Impact: Other

WCS-05737: Unexpected error occurred in preparing image URL {0}
Cause: An error occurred in preparing image URL
Action: Make sure that the URL passed is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05738: Failed to grant role for some members in portal {0}.
Cause: WebService API failed to execute grant role web service call for some or all members. This may be because these members already have provided role grants.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: WARNING

Impact: Other

WCS-05739: An error occurred while revoking roles for some users in portal {0}.
Cause: WebService API failed to execute revoke role web service call for some members.
Action: Check the web service parameters, make sure the configuration is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-05900: Unexpected error occurred while performing operation.
Cause: Error occurred due to unknown cause
Action: Try the operation again or contact oracle support

Level: 1

Type: ERROR

Impact: Other

WCS-06001: JCR session leak: leaked {0} sessions during {1} request to URI {2}.
Cause: JCR sessions have not been returned to the pool after the request ended.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-06002: Connection "{0}" is not a content repository connection.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-06004: Error getting default IdcContext for connection "{0}": {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-06005: Error getting admin IdcContext for connection "{0}": {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-06006: Error getting IdcClient for connection "{0}": {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-06007: Invalid maximum binary cache entry size: {0}. The value must be a number.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-06008: The connection "{0}" is not an Oracle Content Server connection.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-06009: There was an error looking up connection {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-06902: Incomplete repository connection, cannot login.
Cause: The repository configuration details are not valid and a classpath issue prevented the loading of the underlying JCR repository.
Action: Verify that all the configuration parameters are correct and check the message from the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-06905: Credentials for connection {0} not found using External Application Identifier {1}.
Cause: An attempt to fetch user credentials failed. User credentials may not have been provisioned or the external application configuration may be incorrect.
Action: Verify the external application configuration. If necessary, provision credentials for the user.

Level: 1

Type: WARNING

Impact: Other

WCS-06906: invalid credentials for connection {0} using External Application Identifier {1}
Cause: An attempt to log in using the provisioned credentials failed. The user's credentials for this connection might have been changed or the external application configuration might have been incorrect.
Action: If the provisioned credentials for the given user are not valid, then those credentials must be provisioned again. It might also be necessary to verify the external application configuration.

Level: 1

Type: WARNING

Impact: Other

WCS-06908: JCR Repository creation failure.{0}
Cause: A JCR repository instance could not be created from the parameters provided.
Action: Check the configuration parameters, and retry.

Level: 1

Type: WARNING

Impact: Other

WCS-06910: External Application Definition not found using External Application Identifier {0}
Cause: An attempt to fetch user credentials failed. The External Application ID is incorrect.
Action: Verify that the External Application definition has been created for this connection.

Level: 1

Type: WARNING

Impact: Other

WCS-06911: There is no authenticated user and PUBLIC credentials are not supported for External Application ID {0}.
Cause: An attempt to fetch credentials failed because there is not currently an authenticated user and the External Application ID does not support PUBLIC credentials.
Action: Use an External Application ID that supports PUBLIC credentials or authenticate so that no attempt to use PUBLIC credentials will occur.

Level: 1

Type: WARNING

Impact: Other

WCS-06912: There is no authenticated user and the PUBLIC credentials provisioned for External Application ID {0} are not valid.
Cause: An attempt to login using PUBLIC credentials failed because the provisioned PUBLIC credentials are not valid.
Action: Contact your system administrator and inform them that the PUBLIC credentials need to be updated or authenticate so that no attempt to utilize the PUBLIC credentials will occur.

Level: 1

Type: WARNING

Impact: Other

WCS-06913: The SHARED credentials provisioned for External Application ID {0} are not valid.
Cause: An attempt to login using SHARED credentials failed because the provisioned SHARED credentials are not valid.
Action: Contact your system administrator and inform them that the SHARED credentials need to be updated.

Level: 1

Type: WARNING

Impact: Other

WCS-07001: severe internal error
Cause: An irrecoverable internal error has occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-07002: error obtaining Documents service ADF configuration
Cause: An error occurred while obtaining or interpreting the DocLib section of ADF configuration.
Action: Verify that the Documents service section of the ADF configuration is present, complete, and contains valid data.

Level: 1

Type: WARNING

Impact: Other

WCS-07003: error obtaining content repository connection
Cause: A JNDI Naming Exception occurred while attempting to obtain the content repository connection.
Action: Verify that connections.xml contains a valid entry for the content repository connection.

Level: 1

Type: WARNING

Impact: Other

WCS-07004: content repository login failure
Cause: The attempt to log on to the content repository failed.
Action: Make sure the credentials used are valid.

Level: 1

Type: WARNING

Impact: Other

WCS-07005: JCR error connecting to content repository
Cause: A JCR repository exception (other than login) occurred.
Action: Use the associated JCR exception text to diagnose the problem.

Level: 1

Type: WARNING

Impact: Other

WCS-07006: runtime error obtaining content repository
Cause: An unexpected runtime exception occurred.
Action: Use the associated runtime exception text to diagnose the problem.

Level: 1

Type: WARNING

Impact: Other

WCS-07007: cannot list items in directory {0}
Cause: An error occurred while trying to list the items in the specified folder.
Action: Make sure that the content repository connection is accessible and that the specified folder exists.

Level: 1

Type: WARNING

Impact: Other

WCS-07008: cannot get breadcrumbs for directory {0}
Cause: An error occurred while trying to list the breadcrumbs items for the specified folder.
Action: Make sure that the content repository connection is accessible and that the specified folder exists.

Level: 1

Type: WARNING

Impact: Other

WCS-07010: error listing folder {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07011: The Rich Text Editor could not load the target document, it may have been deleted.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07012: The Rich Text Editor could not load the destination folder, it may have been deleted.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07013: No content repository connection with the name "{0}" can be found.
Cause: A JNDI Name Not Found Exception occurred while attempting to obtain the content repository connection.
Action: Verify connections.xml contains an entry for the specified content repository connection name.

Level: 1

Type: WARNING

Impact: Other

WCS-07014: An attempt to log on to the content repository did not complete within the allotted time.
Cause: The content repository may have been slowed by heavy loads or network congestion.
Action: Wait a while, and then retry. Optionally, ask the system administrator to allocate more resources for the content repository or to lengthen the timeout period.

Level: 1

Type: WARNING

Impact: Other

WCS-07015: An attempt to log on to the content repository did not succeed because the Documents service is disabled.
Cause: Login failed because the Documents service was disabled. Another login was still executing, exceeding its allotted timeout period.
Action: Wait a while, and then retry. Optionally, ask the system administrator to allocate more resources for the content repository or to lengthen the timeout period.

Level: 1

Type: WARNING

Impact: Other

WCS-07016: Cannot get the user name for the selected user.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07017: The target Content Server does not support the following query used to retrieve recent documents: {0}.
Cause: Required components may not have been installed or properly configured.
Action: Check the Content Server installation guide for WebCenter for details on required components and their configuration.

Level: 1

Type: ERROR

Impact: Other

WCS-07018: An error occurred while trying to convert the following object from {0} to {1}: {2}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07019: Cannot create folder "{0}" in "{1}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07020: Error refreshing the JCR session.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07021: The transferable object contains no usable data.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07022: After fail-over, failed to get the item {0} from the repository.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07023: Please refresh to see the latest content (View > Refresh Content).
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07024: Please refresh to see the latest content (View > Refresh Content). You may need to navigate up the folder hierarchy before refreshing.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07025: Unable to rename the selected document.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07026: Unable to perform the operation. The document or folder may have been deleted or you do not have permission.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07027: An error occurred performing post operation refreshing. The current document or folder may have been deleted or you do not have permission.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07028: The folder being renamed no longer exists.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07029: Unable to checkout {0}. This document is already checked out.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07030: Unable to perform the current operation.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07031: Unable to delete selected documents or folders.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07032: Unable to rename the selected folder.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07033: Unable to create folder.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07034: Unable to display folder properties.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07035: Unable to create new HTML document.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07036: Unable to upload the document.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07037: Unable to edit the HTML document.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07038: Unable to display document properties.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07039: Unable to display folder properties.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07040: Unable to save folder properties.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07041: Unable to check in the document.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07042: Unable to check out the document.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07043: Unable to cancel the document check-out.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07044: Unable to view version history for the document.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07045: Unable to copy selected documents or folders.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07046: Unable to paste selected documents or folders.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07047: A document or folder with the same name exists in this folder.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07048: A document or folder with the same name exists in this folder.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07049: You do not have permission.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07050: The folder no longer exists.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07051: The selected documents or folders no longer exist.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07052: The document no longer exists.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07053: The parent folder no longer exists.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07054: The document or folder being copied/moved no longer exists or the target folder no longer exists.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07055: The parent folder is currently unavailable.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07056: One or more of the selected documents or folders no longer exists.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07057: The document being renamed no longer exists.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07058: The document or folder no longer exists.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07059: The maximum number of folders stored within a folder has been reached. Contact your systems administrator.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07060: The maximum number of documents stored within a folder has been reached. Contact your systems administrator.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07061: The document is checked out by another user.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07062: The document is checked out by user {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07063: The document is not checked out.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07064: An unknown error occurred in the Oracle Content Server.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07065: The selected document or folder or its parent folder may have been deleted or your permissions may have been revoked.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07066: Unable to move selected documents or folders.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07067: A document or folder with the same name exists in this folder.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07068: A document or folder with the same name exists in this folder.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07069: The folder name contains an invalid character.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07070: The folder name is too long.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07071: Unable to save document properties.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07072: The destination cannot be a child folder of the source folder.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07073: Unable to display item properties.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07074: Unable to save item properties.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07075: No transfer data found for data flavor {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07076: No value found for task flow parameter {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07077: An error occurred while adding the content presenter task flow to the page.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07078: The class method ''{0}.{1}'' cannot be called with a null or empty argument ''{2}''.
Cause: The specified method call cannot be called with the specified argument with value of null.
Action: Ensure the specified argument has a non-null value.

Level: 1

Type: ERROR

Impact: Other

WCS-07079: Datasource type ''{0}'' was expected but found ''{1}''.
Cause: The configured datasource type did not match the expected datasource type.
Action: Correct the presenter configuration to the expected datasource type.

Level: 1

Type: ERROR

Impact: Other

WCS-07080: Error retrieving node(s).
Cause: An error was encountered retrieving node(s).
Action: Please contact a system administrator for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-07081: Error saving Content Presenter Configuration.
Cause: An error was encountered saving the specified configuration document.
Action: Please contact a system administrator for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-07082: Query expression must be a valid, non-empty expression.
Cause: The specified query expression was invalid.
Action: Review the specified query expression and correct it.

Level: 1

Type: ERROR

Impact: Other

WCS-07083: The datasource type ''{0}'' requires ''{1}'' to be set.
Cause: The specified datasource type is not consistent with the datasource state.
Action: Specific datasource types require different parameters to be set. Please resolve this situation.

Level: 1

Type: ERROR

Impact: Other

WCS-07084: Invalid datasource type ''{0}''. Valid datasource types:{1}.
Cause: The specified datasource type was invalid.
Action: Correct the specified datasource type to one of the examples provided in the error message.

Level: 1

Type: ERROR

Impact: Other

WCS-07085: The configuration {0} is required.
Cause: You have not specified the mentioned configuration item.
Action: Make sure the mentioned configuration item is provided for this presenter instance.

Level: 1

Type: ERROR

Impact: Other

WCS-07086: Both page size and maximum results are required and must be a positive integer (pageSize:{0}, maxResults:{1}).
Cause: You have not specified the page size and maximum results.
Action: Correct the page size and maximum results.

Level: 1

Type: ERROR

Impact: Other

WCS-07087: Error loading task-flow instance configuration
Cause: An error occurred while loading the task-flow instance configuration.
Action: Check the base exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-07088: Error saving task-flow instance configuration
Cause: An error occurred while saving the task-flow instance configuration.
Action: Check the base exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-07089: Unable to save Content Presenter configuration data.
Cause: An error occurred while saving the presenter configuration data.
Action: Check the base exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-07090: Unable to retrieve presenter configuration data.
Cause: An error occurred while retrieving the presenter configuration data.
Action: Check the base exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-07091: Unable to retrieve presenter template data.
Cause: An error occurred while retrieving the presenter template data.
Action: Check the base exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-07092: An error occurred while running the query.
Cause: An error occurred while previewing the query.
Action: Check the base exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-07093: An error occurred while retrieving the node.
Cause: An error occurred while retrieving the node.
Action: Check the base exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-07094: Maximum results (current:{0}) must be an integer between {1} and {2}.
Cause: The value you have specified for maximum results must inclusively be between the range specified.
Action: Correct the maximum results to be inclusively be between the specified range.

Level: 1

Type: ERROR

Impact: Other

WCS-07095: An error occurred while running the query.
Cause: A general repository exception has occurred.
Action: Check the base exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-07096: Unable to retrieve properties for the specified item.
Cause: An error occurred while retrieving properties for the specified item.
Action: Check the base exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-07097: Unable to retrieve markup for the specified item: {0}
Cause: An error occurred while retrieving markup for the specified item.
Action: Check the base exception for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-07098: Unable to delete the selected version.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07099: Unable to retrieve workflow approvers for the specified item: {0}
Cause: An error occurred while retrieving workstate approvers for the specified item.
Action: Check the base exception for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-07100: Oracle Content Server error: {0}
Cause: An unexpected error occurred in the Oracle Content Server.
Action: Check the Oracle Content Server logs for details on this exception.

Level: 1

Type: WARNING

Impact: Other

WCS-07101: Repository error: {0}
Cause: An unexpected error occurred in the content repository.
Action: Check the base exception and repository's log for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-07102: Repository error
Cause: An unexpected error occurred in the content repository.
Action: Check the base exception and repository's log for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-07103: Unsupported repository operation
Cause: The Documents service tried to invoke an operation that is not supported by the underlying document repository.
Action: Avoid this operation with this repository.

Level: 1

Type: WARNING

Impact: Other

WCS-07104: Access Denied
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07105: Versioning is not supported on this repository.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07106: Locking is not supported on this repository.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07107: The recent documents query is not supported on this repository.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07108: Repository error: {0}
Cause: An unexpected error occurred in the content repository.
Action: Check the base exception and repository's log for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-07109: Unable to save Content Presenter configuration data because no content item was selected. Select a content item before proceeding further.
Cause: An error occurred while saving the presenter configuration data without a content item.
Action: Check the base exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-07201: Unable to approve the selected document.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07202: Unable to reject the selected document.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07203: Error initializing the user security cache.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07204: Unable to create new wiki page.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07205: Unable to find parent folder.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07206: parent folder is not set.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07207: Could not retrieve links count for resource {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07208: Could not retrieve tags count for resource {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07209: Could not retrieve comments count for resource {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07210: Could not retrieve likes count for resource {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07211: Could not retrieve likes/comments count for resource {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07212: Error trying to retrieve spaces page for resource {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07213: Could not set the security on the folder or document.
Cause: An error occurred while trying to update the item's security.
Action: Review the associated error messages.

Level: 1

Type: WARNING

Impact: Other

WCS-07214: The Scenario datasource was not constructed correctly
Cause: Either the conductor or the scenario have not be set correctly.
Action: Review the specified conductor service and scenario configurations to make sure they are correct.

Level: 1

Type: ERROR

Impact: Other

WCS-07215: Failed to get UCM configuration settings.
Cause: An error occurred while getting configuration information from the Content Server.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07216: The workflow settings could not be saved as there are too many approvers. Please reduce the number of approvers.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07217: Unable to add the following approvers to the workflow, the approvers username limit has been reached.{0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07218: Unknown error while retrieving recent documents
Cause: An unknown error occurred while querying for recent documents.
Action: Check the underlying exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-07219: Invalid parameter combination: the connection name specified by resourceId = {0} is not the same as specified in parameter connectionName = {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07220: Invalid parameter combination: the item identified by resourceId = {0} is not a child of startFolderPath = {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07221: {0} is not a valid resource identifier.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07222: The item with resourceId = {0} does not exist or is not accessible.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07223: Invalid content id ''{0}'' for datasource type ''{1}''.
Cause: The specified content id was invalid.
Action: Correct the specified content id to a valid id.

Level: 1

Type: ERROR

Impact: Other

WCS-07225: The object is not a Document Library resource.
Cause: An unexpected condition has occurred.
Action: Contact your Oracle support representative.

Level: 1

Type: ERROR

Impact: Other

WCS-07226: Failed to set ACL on content item as item ACL has been changed concurrently.
Cause: The attempt to change the security settings has failed because the settings have already been changed by another user.
Action: Re-try the operation against the refreshed view of the item's security policy.

Level: 1

Type: ERROR

Impact: Other

WCS-07227: Modifications to an item's security policy are not supported.
Cause: An attempt has been made to modify an item's security policy.
Action: An item's security policy must be updated entirely and not partially.

Level: 1

Type: ERROR

Impact: Other

WCS-07228: Failed to set ACL on content item {0}.
Cause: The attempt to set ACL security on an Oracle Content Server repository item has failed.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07229: Failed to restore content item {0} for security settings.
Cause: The attempt to restore a content item from its identifier has failed.
Action: Retry the security settings operation.

Level: 1

Type: ERROR

Impact: Other

WCS-07230: Determining if Content Server is configured to support item level security failed.
Cause: An error occurred while getting configuration information from the Content Server.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07231: Determining if Content Server is configured to support Slide Previewer failed.
Cause: An error occurred while getting configuration information from the Content Server.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07232: Error discovering if user has admin access to file or folder.
Cause: An error occurred when trying to discover if the current user has admin capabilities for the file or folder.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07233: Cannot perform action, item is in a workflow.
Cause: An action is being attempted on a document which is in a workflow.
Action: Retry the action, when the workflow is complete.

Level: 1

Type: WARNING

Impact: Other

WCS-07234: Fetching Workflow data from Content Server failed.
Cause: An error occurred while getting workflow information from the Content Server.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07235: No connection specified for Documents to use.
Cause: An attempt was made to use Documents without explicitly specifying a connection or configuring a primary connection.
Action: Either explicitly supply Documents with a connection or specify a primary connection in the ADF configuration.

Level: 1

Type: ERROR

Impact: Other

WCS-07237: Determining if Content Server is configured with AutoVue failed.
Cause: An error occurred while getting configuration information from the Content Server.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07238: Unexpected exception: {0}
Cause: An unexpected exception occurred.
Action: Check the server logs for details on this exception.

Level: 1

Type: WARNING

Impact: Other

WCS-07239: Unexpected error
Cause: An unexpected error occurred.
Action: Check the server logs for details on this error.

Level: 1

Type: ERROR

Impact: Other

WCS-07240: Unsupported resource type
Cause: The Documents service tried to perform an operation on a resource but failed to do so because the resource type was not recognized.
Action: Avoid this operation with this particular type of resource.

Level: 1

Type: WARNING

Impact: Other

WCS-07241: Renaming the root folder is not allowed.
Cause: An attempt was made to rename the root folder.
Action: Avoid the rename operation with the root folder.

Level: 1

Type: WARNING

Impact: Other

WCS-07242: Error reading the document's content.
Cause: The document's content could not be accessed.
Action: Verify that the document is available.

Level: 1

Type: WARNING

Impact: Other

WCS-07243: Error performing paste.
Cause: An error prevented the items from being pasted at the destination folder.
Action: Verify that the destination folder still exists, is writable, and no items with the same names exist there.

Level: 1

Type: ERROR

Impact: Other

WCS-07244: When searching between dates, if the dates are not specified in ascending order, the search may not return any results.
Cause: The begin and end dates have been specified in the wrong order.
Action: Specify the dates in ascending order.

Level: 1

Type: WARNING

Impact: Other

WCS-07245: Operation not allowed on Public folders.
Cause: An attempt has been made to perform an illegal operation on a Public folder.
Action: Do not select a Public folder when performing operations such as delete and rename. If performing a copy or move operation then select item(s) inside the Public folder, not the Public folder itself.

Level: 1

Type: ERROR

Impact: Other

WCS-07246: Approver list is too large for current workflow.
Cause: Unable to save the set of approvers for the workflow as the usernames exceed the 255 character limit.
Action: Reduce the approvers for the workflow.

Level: 1

Type: ERROR

Impact: Other

WCS-07247: Could not list the items in a folder;
Cause: An error occurred while trying to list the items in a folder.
Action: Make sure that the content repository connection is accessible and that the folder exists. Navigate to another folder in the hierarchy.

Level: 1

Type: WARNING

Impact: Other

WCS-07248: Unable to open the editor.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07249: Could not connect to the content repository.
Cause: A error occurred while trying to connect to the content repository.
Action: Make sure that the content repository is running and accessible.

Level: 1

Type: ERROR

Impact: Other

WCS-07250: Provisioning of the Documents service failed.
Cause: An error occurred while trying to provision the Documents service.
Action: Make sure that the content repository connection is accessible. Check the Oracle Content Server logs for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07251: The item may have been deleted or has already been approved or rejected.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07252: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07253: Unexpected error evaluating property ''{0}'' of base {1}
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-07254: Click the blog name in the banner to refresh with the latest content.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07255: Typical causes are that you do not have permission or one or more child items are currently in an active workflow.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07256: Error while showing configure content manager pop up.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07257: Error while saving wcc pin to page definition file.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07258: Cannot find region with id {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07259: Cannot find rich popup with id {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07260: Error while viewing the document. Document identifier: {0}, revision identifier: {1} and document account: {2}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07261: Error while viewing the contents of folder. Folder identifier: {0} and folder account: {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07262: An error occurred while checking permission on content.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07263: Please refresh to see the latest content.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07264: An error occurred while viewing or downloading the content.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07265: An error occurred while invoking the WCC filter.
Cause: An error occurred while invoking the WCC filter
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-07501: There is no role matching the given ID: {0}.
Cause: The application attempted to look up a service role with an invalid role ID.
Action: Ensure that your application uses a valid service role ID.

Level: 1

Type: ERROR

Impact: Other

WCS-07502: Cannot grant super administrator role for scope {1}.
Cause: Could not grant the super administrator role to the scope. The super administrator role can only be granted to the default scope; other roles must be granted on a portal scope.
Action: Verify that the role mapping is correctly defined.

Level: 1

Type: ERROR

Impact: Other

WCS-07503: Cannot log on to the content repository.
Cause: The username and password used for the current login were not correct.
Action: Check the username and password.

Level: 1

Type: WARNING

Impact: Other

WCS-07504: There was an unknown content repository exception.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07505: The repository login was interrupted.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07601: Unable to read document metadata (''{0}'',''{1}'').
Cause: Generally caused by a malformed xml document.
Action: Check the specified xml document for errors.

Level: 1

Type: ERROR

Impact: Other

WCS-07602: Document metadata (''{0}'',''{1}'') is expected to be of type ''{2}'', but found ''{3}''.
Cause: Generally caused by a malformed xml document with an incorrect namespace.
Action: Check the specified xml document and make sure the xmlns attribute is set to 'http://xmlns.oracle.com/webcenter/content/templates/registry'.

Level: 1

Type: ERROR

Impact: Other

WCS-07603: No content list template or content template found in registry(''{0}'',''{1}'').
Cause: Generally caused by an empty display template descriptor.
Action: Check the specified xml document and make sure that either content-templates or content-list-templates are defined.

Level: 1

Type: ERROR

Impact: Other

WCS-07604: Default template view named ''{0}'' not found for content type ''{1}''.
Cause: A content type has been configured in the template registry with a default template that has not been found.
Action: Check the specified xml document and make sure a template view exists with the id of the defaultView specified on the content type.

Level: 1

Type: ERROR

Impact: Other

WCS-07605: There are duplicate template categories with id ''{0}''.
Cause: There are duplicate template categories that are defined with the specified id.
Action: Check the template registry document and make sure and change the name of the specified template category.

Level: 1

Type: ERROR

Impact: Other

WCS-07606: There are duplicate content types by name ''{0}''.
Cause: There are duplicate content types that are defined with the specified name.
Action: Check the template registry document and make sure and change the name of the specified content type.

Level: 1

Type: ERROR

Impact: Other

WCS-07607: There are duplicate content repositories by name ''{0}'' and type ''{1}''.
Cause: There are duplicate content repositories that are defined with the specified name.
Action: Check the template registry document and make sure and change the name of the specified content repository.

Level: 1

Type: ERROR

Impact: Other

WCS-07608: There are duplicate template views by id ''{0}''.
Cause: There are duplicate template views that are defined with the specified id.
Action: Check the template registry document and make sure and change the id of the specified template view.

Level: 1

Type: ERROR

Impact: Other

WCS-07609: The class method ''{0}.{1}'' cannot be called with a null argument ''{2}''.
Cause: The specified method call cannot be called with the specified argument with value of null.
Action: Ensure the specified argument has a non-null value.

Level: 1

Type: ERROR

Impact: Other

WCS-07610: Unable to locate resource key ''{0}'' in bundle ''{1}''.
Cause: The display template registry is configured with a resource bundle and key that is unable to be found.
Action: Check the specified resource bundle and ensure that the specified key exists.

Level: 1

Type: WARNING

Impact: Other

WCS-07611: No template category defined by id ''{0}''.
Cause: The display template registry does not contain a category configuration by the specified id.
Action: Add the specified category id to the template registry.

Level: 1

Type: WARNING

Impact: Other

WCS-07612: No template view defined by id ''{0}''.
Cause: The display template registry does not contain a template configuration by the specified id.
Action: Add the specified template id to the template registry.

Level: 1

Type: WARNING

Impact: Other

WCS-07613: No template registry found in application.
Cause: The display template registry does not exist or cannot be found.
Action: Check application configuration and ensure registry is properly configured.

Level: 1

Type: WARNING

Impact: Other

WCS-07614: Default template view named ''{0}'' not found in template category ''{1}''.
Cause: A category has been configured in the template registry with a default template view that has not been found.
Action: Check the specified xml document and make sure a template view exists with the id of the defaultView specified on the category.

Level: 1

Type: ERROR

Impact: Other

WCS-07615: Default category named ''{0}'' not found in the registry.
Cause: A default category has been configured in the template registry that has not been found.
Action: Check the specified xml document and make sure a the default category has been defined.

Level: 1

Type: ERROR

Impact: Other

WCS-07616: No template view defined by id ''{0}'' and category ''{1}''.
Cause: The display template registry does not contain a template configuration by the specified category and view.
Action: Add the specified template id to the template registry.

Level: 1

Type: WARNING

Impact: Other

WCS-07617: A general display template error has occurred.
Cause: An unexpected exception has occurred processing the display template registry.
Action: Review the original stacktrace cause for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07618: No default template view specified for category id ''{0}''. Returning the default view for the default category.
Cause: The specified category in the template registry is not configured with a default view, but has been referenced using the default behavior.
Action: Update the specified category in the template registry to configure a default view.

Level: 1

Type: WARNING

Impact: Other

WCS-07619: Invalid configuration for category id ''{0}''. Could not find view defined for view id ''{1}''.
Cause: The specified category in the template registry is configured with no default templates.
Action: Update the registry to only include a single default template for the category.

Level: 1

Type: WARNING

Impact: Other

WCS-07620: Invalid configuration for category id ''{0}''. Multiple templates found for view id ''{1}''.
Cause: The specified category in the template registry is configured with multiple templates.
Action: Update the registry to only include a single template for the category and view id combination.

Level: 1

Type: WARNING

Impact: Other

WCS-07621: Invalid configuration for content type name ''{0}'' in repository name ''{1}'' configuration.
Cause: The specified category in the template registry is configured with no default templates.
Action: Update the registry to only include a single default template for the category.

Level: 1

Type: WARNING

Impact: Other

WCS-07622: Invalid configuration for content type name ''{0}'' in repository ''{1}''. Multiple default templates found.
Cause: The specified category in the template registry is configured with multiple templates.
Action: Update the registry to only include a single template for the category and view id combination.

Level: 1

Type: WARNING

Impact: Other

WCS-07701: severe internal error while getting the template view ID
Cause: An irrecoverable internal error has occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-07702: Error while getting the template view ID
Cause: An error occurred while determining the template for a node.
Action: Check the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-07703: No request dispatcher for template viewID {0} located at {1}
Cause: An error occurred while trying to dispatch the request to the template. The target template may not exist.
Action: Check that the target template exists.

Level: 1

Type: ERROR

Impact: Other

WCS-07704: Error processing the display template include for template viewID {0} located at {1}
Cause: An error occurred while processing the template include. This may result from a syntax or logic error in the template code.
Action: Check the underlying exception for the details of the error.

Level: 1

Type: ERROR

Impact: Other

WCS-07710: Error while getting the template view ID because of null node or view, node: {0}, view: {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07712: Error setting up context for template. {0}
Cause: An error occurred while trying to setup the context for the template.
Action: Check the underlying error.

Level: 1

Type: ERROR

Impact: Other

WCS-07713: Internal error: illegal reentrant use of template context.
Cause: An internal error was detected, attempted reentrant use of template context.
Action: Contact your Oracle Support representative.

Level: 1

Type: ERROR

Impact: Other

WCS-07714: Error tearing down context for template. {0}
Cause: An error occurred while trying to teardown the context for the template.
Action: Check the underlying error.

Level: 1

Type: WARNING

Impact: Other

WCS-07715: Error popping context, found another template context. {0}. {1}.
Cause: An error occurred while trying to pop the context, found another template context.
Action: Contact your Orale support representative.

Level: 1

Type: ERROR

Impact: Other

WCS-07716: Error popping context, found another context. {0}.
Cause: An error occurred while trying to pop the context, found another context.
Action: Contact your Oracle support representative.

Level: 1

Type: ERROR

Impact: Other

WCS-07717: Error while invoking component.
Cause: An error occurred while invoking the template component.
Action: Check the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-07718: Error when resuming context: no queued context to resume.
Cause: Template context cannot be resumed, as context queue is empty.
Action: Contact your Oracle support representative.

Level: 1

Type: ERROR

Impact: Other

WCS-07719: Error when resuming context: no context to resume.
Cause: Template context cannot be resumed, as there is no context to resume.
Action: Contact your Oracle support representative.

Level: 1

Type: ERROR

Impact: Other

WCS-07720: Error retrieving Region Template from WebCenter Content.
Cause: An error occurred retrieving the Region Template from the WebCenter Content server.
Action: Check the exception for the underlying cause.

Level: 1

Type: ERROR

Impact: Other

WCS-07801: Cannot seed the WebCenter data into the content repository.
Cause: An error occurred while seeding data for the Documents service in the content repository.
Action: Check the underlying exception and content repository log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07802: Cannot find the adf-config.xml file.
Cause: Could not find an adf-config.xml document in the classpath.
Action: To enable the Documents service in WebCenter, ensure adf-config.xml and connections.xml containing Documents service information are on the classpath.

Level: 1

Type: ERROR

Impact: Other

WCS-07803: Cannot open a connection to the Oracle Content Server.
Cause: The application failed to open a connection to the Oracle Content Server.
Action: Check that the Oracle Content Server connection is properly configured and that the server is available.

Level: 1

Type: ERROR

Impact: Other

WCS-07804: Cannot create the Security Group, {0}, in the Oracle Content Server.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07805: Cannot create the seeded role, {0}, in the Oracle Content Server.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07806: Cannot create the folder, {0}, in the folder, {1}, in the Oracle Content Server.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07807: Cannot rename the folder, {0}, to {1}, in the Oracle Content Server.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07808: Cannot delete the folder, {0}, in the Oracle Content Server.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07809: Cannot get folder with the path, {0}, from the Oracle Content Server.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07810: Error obtaining the content repository connection "{0}".
Cause: A JNDI Naming Exception occurred while attempting to obtain the content repository connection.
Action: Verify that connections.xml contains a valid content repository connection.

Level: 1

Type: ERROR

Impact: Other

WCS-07811: Unsupported repository connection "{0}" for the Documents service.
Cause: The specified content repository is not currently supported for Documents service WebCenter Portal integration. The supported content repository types is Oracle Content Server.
Action: Verify that adf-config.xml and connections.xml contain a valid entry for the Documents service repository.

Level: 1

Type: ERROR

Impact: Other

WCS-07812: Cannot remove permissions, {0}, for user/group, {1}, to the account for the folder, {2}.
Cause: The application failed to remove permissions for the user/group on the folder.
Action: Check that the permissions and user/group are valid and that the folder exists.

Level: 1

Type: ERROR

Impact: Other

WCS-07813: Cannot grant permissions, {0}, for user, {1}, to the account for the folder, {2}.
Cause: The application failed to grant permissions for the user on the folder.
Action: Check that the permissions and user are valid and that the folder exists.

Level: 1

Type: ERROR

Impact: Other

WCS-07814: Error while removing an account from all users credentials.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07816: Unable to seed the WebCenter data in the Oracle Content Server repository.
Cause: A Content Server error occurred while seeding the WebCenter data in the repository.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07817: Unable to seed the Personal Folder data in the Oracle Content Server repository.
Cause: A Content Server error occurred while seeding the Personal Folder data in the repository.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07818: Cannot find the WebCenter administrators to seed in the Document Library repository.
Cause: The application failed to determine the list of WebCenter administrators.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07819: Cannot release the session pool.
Cause: Failed to release the session pool for the content repository administrative connection.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07820: Cannot create a search result row from the JCR node.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07821: Error while calling the EC_SET_PROPERTY service with dECPropType = {0}, dECPropKey = {1}, dECPropSubKey = {2}, dECPropValue = {3}.
Cause: A call to the Oracle Content Server EC_SET_PROPERTY service during repository setup failed to complete.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07822: Cannot get the WebCenter URL.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07823: Cannot grant the account, {0}, to all users.
Cause: An error occurred while trying to grant the account to all users.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07824: Unable to get the admin session to the Oracle Content Server repository.
Cause: An error occurred while trying to obtain an admin session to the Oracle Content Server repository.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07825: Cannot remove role, {0}, for user/group, {1}.
Cause: The application failed to remove the specified role from the user/group.
Action: Check the role and user/group are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-07826: Cannot remove role {0} and permissions, {1}, to the account for the folder, {2} for the user/group {3}.
Cause: The application failed to remove the role and permissions on the folder for the user/group.
Action: Check that the permissions and user/group are valid and that the folder exists.

Level: 1

Type: ERROR

Impact: Other

WCS-07827: Cannot add role, {0}, for user/group, {1}.
Cause: The application failed to add the specified role to the user/group.
Action: Check the role and user/group are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-07828: Cannot add role {0} and permissions, {1}, to the account for the folder, {2} for the user/group {3}.
Cause: The application failed to add the role and permissions on the folder for the user/group.
Action: Check that the permissions and user/group are valid and that the folder exists.

Level: 1

Type: ERROR

Impact: Other

WCS-07829: Cannot update the account for the portal {0}, with permission, {1}, for all users.
Cause: An error occurred while trying to update the portal account for all users.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07830: Cannot set default attributes, {0}, for the key, {1}
Cause: An error occurred while trying to set default attributes for the specified key.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07831: Cannot delete default attributes for the key, {0}.
Cause: An error occurred while trying to delete default attributes for the specified key.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07832: Cannot determine account and permission from the default attributes for the portal, {0}.
Cause: An error occurred while trying to determine the account and permission from the default attributes for the portal. The default attributes are not in the correct format.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07833: The Java Object Cache is not available.
Cause: An error occurred while trying to retrieve the cache.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07834: A Java Object Cache operation timed out. Distributed caches may be inconsistent.
Cause: A cache operation timed out.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07835: Java Object Cache, Put operation failed.
Cause: A cache put operation failed.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07836: Java Object Cache, Destroy operation failed.
Cause: A cache destroy operation failed.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07837: Java Object Cache, Get operation failed.
Cause: A cache get operation failed.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07838: Java Object Cache, release ownership failed.
Cause: A cache unlock operation on a cached object failed.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07839: Invalid document service ADF configuration.
Cause: The documents services configuration in adf-config.xml is invalid.
Action: Verify that the documents services configuration in adf-config.xml conforms to the documents service configuration data schema.

Level: 1

Type: ERROR

Impact: Other

WCS-07840: Cannot get folder with the GUID, {0}, from the Oracle Content Server.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07845: Error loading Site Studio content.
Cause: An error occurred while loading data for Site Studio into the content repository.
Action: Check the underlying exception and content repository log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07846: Error checking Site Studio content into Content Server.
Cause: An error occurred while checking in Site Studio content into the content repository.
Action: Check the underlying exception and content repository log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07847: Error checking installation of SiteStudio on Content Server.
Cause: An error occurred while checking the installation of the Site Studio in the content repository.
Action: Check the underlying exception and content repository log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07848: Error creating temporary directory to extract SiteStudio content to.
Cause: An error occurred while creating the directory to extract the Site Studio content to.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07850: Failed to destroy Java Object Cache region, {0}.
Cause: An error occurred while trying to destroy the Doclib Java Object Cache region.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07857: Cannot get the version for the {0} component from the Oracle Content Server.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07863: Cannot determine if Document Library supports Enterprise Roles.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07864: Cannot enable the workflow {0}.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07865: Cannot create the workflow with the name {0}.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07866: Cannot create the workflow step {0} for the workflow {1}.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07867: Cannot get the portal account from the GUID {0}.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07868: Cannot propagate account for the portal folder {0} to its contents.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07870: Security settings are only supported for Oracle Content Server.
Cause: An attempt has been made to set security for a non Oracle Content Server repository.
Action: To enable security, use Oracle Content Server.

Level: 1

Type: ERROR

Impact: Other

WCS-07871: Cannot set default attributes, for the key, {1}
Cause: An error occurred while trying to get default attributes for the specified key.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07872: Unable to upgrade the WebCenter data in the Oracle Content Server repository.
Cause: A Content Server error occurred while upgrading the WebCenter data in the repository.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07873: Cannot get the workflow {0}.
Cause: A Content Server error occurred while getting the workflow.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07874: The documents services configuration in adf-config.xml is invalid, one of the settings is being used in another Webcenter's configuration.
Cause: Either the portal root or application name in the Document Properties is the same as another WebCenter instance using the same Content Server.
Action: Ensure the portal root and application are both unique and not being used in another WebCenter's configuration using the same Content Server.

Level: 1

Type: ERROR

Impact: Other

WCS-07875: Can not get the folder metadata for the scope, {0}.
Cause: A Content Server error occurred while getting the scope's folder metadata.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07877: Error invalidating the VCR cache entry for {0}.
Cause: An error happened while trying to remove an item from the VCR cache.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07878: Error determining if a scope in the export set has document library provisioned.
Cause: An error happened while trying to determine if the scope is provisioned.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07879: Error while writing doclib provisioned scope to export file.
Cause: An error happened while trying to output the scopes which have document library provisioned.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07880: Error while writing the doclib export document to MDS for portal(s) {0}.
Cause: An error happened while trying to write the document containing the document library export data to MDS.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07884: Error while reading the set of doclib provisioned scopes from the export file.
Cause: An error happened while trying to read the scopes which have document library provisioned from the export file.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07885: Error while reading the doclib export document from MDS for portals{0} .
Cause: An error happened while trying to read the document containing the document library export data from MDS.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07886: Error provisioning document library for a scope in the import set.
Cause: An error happened while trying to provisioning document library during import.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07887: No document library export data found for import in MDS under path {0} for portal(s) {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07888: Invalid datasource type ''{0}''. Valid datasource types:{1}.
Cause: The specified datasource type was invalid.
Action: Correct the specified datasource type to one of the examples provided in the error message.

Level: 1

Type: ERROR

Impact: Other

WCS-07889: Query expression must be a valid, non-empty expression.
Cause: The specified query expression was invalid.
Action: Review the specified query expression and correct it.

Level: 1

Type: ERROR

Impact: Other

WCS-07890: The Scenario datasource was not constructed correctly
Cause: Either the conductor or the scenario have not be set correctly.
Action: Review the specified conductor service and scenario configurations to make sure they are correct.

Level: 1

Type: ERROR

Impact: Other

WCS-07891: Failed to get UCM configuration settings.
Cause: An error occurred while getting configuration information from the Content Server.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07892: Invalid content id ''{0}'' for datasource type ''{1}''.
Cause: The specified content id was invalid.
Action: Correct the specified content id to a valid id.

Level: 1

Type: ERROR

Impact: Other

WCS-07893: The datasource type ''{0}'' requires ''{1}'' to be set.
Cause: The specified datasource type is not consistent with the datasource state.
Action: Specific datasource types require different parameters to be set. Please resolve this situation.

Level: 1

Type: ERROR

Impact: Other

WCS-07894: Both page size and maximum results are required and must be a positive integer (pageSize:{0}, maxResults:{1}).
Cause: You have not specified the page size and maximum results.
Action: Correct the page size and maximum results.

Level: 1

Type: ERROR

Impact: Other

WCS-07895: Maximum results (current:{0}) must be an integer between {1} and {2}.
Cause: The value you have specified for maximum results must inclusively be between the range specified.
Action: Correct the maximum results to be inclusively be between the specified range.

Level: 1

Type: ERROR

Impact: Other

WCS-07896: An error occurred while retrieving the node.
Cause: An error occurred while retrieving the node.
Action: Check the base exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-07897: Error retrieving node(s).
Cause: An error was encountered retrieving node(s).
Action: Please contact a system administrator for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-07898: The datasource type ''{0}'' is currently not supported for custom folder.
Cause: The specified datasource type is not supported for ContentListFactory custom folder.
Action: Only specific datasource types are supported. Please resolve this situation.

Level: 1

Type: ERROR

Impact: Other

WCS-07899: Cannot update the seeded role, {0}, in the Oracle Content Server.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07900: Can not perform document library role mapping, role mapper is not initialized.
Cause: A Content Server error occurred while executing the operation.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07901: Can not perform document library role mapping, role mapper was initialized with a different scope to that being processed. Initialized with scope {0} and processing with scope {1}.
Cause: The document library role mapper can only process actions for the scope with which it was initialized. A request has been made to process role mapping for a different scope which is not permitted.
Action: Check the underlying exception and Oracle Content Server log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07902: Can not perform document library role mapping, the scope does not have Document Library provisioned.
Cause: The document library role mapper can only map roles for a scope which has document library provisioned.
Action: Check the scope has document library provisioned.

Level: 1

Type: ERROR

Impact: Other

WCS-07903: Invalid repository name {0}.
Cause: An invalid repository was specified.
Action: Verify that a valid repository is specified.

Level: 1

Type: ERROR

Impact: Other

WCS-07904: Error while exporting the documents content.
Cause: An error happened while trying to export the documents content of the scopes being exported.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07905: Error while getting the documents contents of the source scope.
Cause: An error happened while trying to get the documents of the source scope from the Content Server.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07906: No scopes have been specified for export.
Cause: No portals have been specified to be exported.
Action: Specify scopes to be exported.

Level: 1

Type: WARNING

Impact: Other

WCS-07907: Error while importing the documents content.
Cause: An error happened while trying to import the documents content of the scopes being imported.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07908: Group Space folder does not exist in target instance can not proceed with import.
Cause: The scope has not been provisioned in the target instance, can not proceed to import data into the target instance.
Action: Ensure WebCenter Export Import has completed successfully and the Scope is provisioned in the target instance.

Level: 1

Type: ERROR

Impact: Other

WCS-07909: The import archive {0} was not found, no document data will be imported.
Cause: The archive containing the documents data was not found. Import of documents content will not occur.
Action: Ensure WebCenter Export included the exporting of documents content..

Level: 1

Type: WARNING

Impact: Other

WCS-07910: Unable to delete data in the target scope prior to import.
Cause: An error happened while trying to delete existing data in the target scope before import commences.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07911: Unable to create document in target scope.
Cause: An error happened while trying to create a document in the target scope.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07916: The following documents were not imported {0}.
Cause: The documents in the list could not be imported into the target UCM.
Action: Check the logs for more information.

Level: 1

Type: WARNING

Impact: Other

WCS-07917: Error creating content URL.
Cause: An error occurred creating a content URL.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07918: The content item {0} was not imported. An item with the filename {1} already exists in the folder.
Cause: Oracle Content Server does not permit multiple content items with the same filename to be checked into the same folder. The content item being imported has the same filename as an existing content item in the same folder. The duplicate document has not been imported.
Action: Check the source UCM instance and either remove the duplicate content items, or ensure the import has imported the correct version of the content item.

Level: 1

Type: WARNING

Impact: Other

WCS-07919: The content item {0} was not imported. The filename {1} contains an invalid characters.
Cause: The filename of the file being imported contains invalid characters, the document can not be checked in.
Action: Check the logs for more information.

Level: 1

Type: WARNING

Impact: Other

WCS-07920: An error occurred loading the names of additional content attributes.
Cause: An error occurred loading the names of additional content attributes.
Action: Check the underlying exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07923: No primary content repository connection.
Cause: There is no content repository connection name set as the primary connection.
Action: Set a content repository connection as the primary connection.

Level: 1

Type: ERROR

Impact: Other

WCS-07924: Error checking foldering service (Framework Folders/folders_g) of content server.
Cause: An error occurred while checking doclib foldering service implementation of content server.
Action: Check the underlying exception and content repository log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07925: Foldering service from content server {0} and Portal Server Configuration {1} do not match.
Cause: Value stored in WC_PORTAL_PROPERTIES table and response from content server is not same.
Action: Contact System Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-07926: Framework Folders version on Oracle WebCenter Content Server is not supported for Oracle WebCenter Portal. The supported versions are {0} and later.
Cause: Framework Folders version on Oracle WebCenter Content Server is not supported for Oracle WebCenter Portal. The supported versions are 2.1 and later.
Action: Contact System Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-07927: Error creating system library list.
Cause: An error occurred while creating system library list from Oracle WebCenter Content Server.
Action: Check the underlying exception in WebCenter Portal and Content Server logs for additional information.

Level: 1

Type: ERROR

Impact: Other

WCS-07928: Failed to get document rules from Oracle WebCenter Content Server.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07929: Failed to add document rule {0} to Oracle WebCenter Content Server.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07930: An error occurred while redirecting to resource using url:{0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07931: An error occurred while importing portal content. Ensure that Oracle WebCenter Content Server is up and running.
Cause: An error occurred while importing portal content from Oracle WebCenter Content Server.
Action: Check the underlying exception in WebCenter Portal and Content Server logs for additional information.

Level: 1

Type: ERROR

Impact: Other

WCS-07932: No file exists with the file name: {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-07933: Error checking desktop tag component in content server.
Cause: An error occurred while checking doclib desktop tag component status in content server.
Action: Check the underlying exception and content repository log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-07934: Error seeding data for SESCrawlerExport component.
Cause: An error occurred while seeding data for SESCrawlerExport component into the content repository.
Action: Check the underlying exception and content repository log for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-08001: Supplied class {0} is not an instance of {1}.
Cause: Forum service adapter details were not configured properly in the adf-config.xml file or the adapter implementation class was not correct.
Action: Check that the adapter class name in the adf-config file is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-08002: Not able to invoke constructor of class {0} through Constructor.newInstance() call.
Cause: Application tried to instantiate a class through Constructor.newInstance().
Action: Check that the adapter class name in the adf-config file is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-08003: Not able to find the method "{0}" in the class "{1}".
Cause: Matching constructor was not found in the adapter implementation class.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-08004: Not able to resolve the name {0}
Cause: Not able to acquire Context to look up.
Action: Check for JNDI configuration.

Level: 1

Type: ERROR

Impact: Other

WCS-08005: User "{0}" is not authorized.
Cause: Contact your administrator for access to discussions forum.
Action: Provide valid user credentials, or check if user exists or has appropriate permissions.

Level: 1

Type: WARNING

Impact: Other

WCS-08006: User "{0}" not logged on.
Cause: User might not have logged on to the system.
Action: Try logging on using correct user credentials.

Level: 1

Type: WARNING

Impact: Other

WCS-08007: User "{0}" not found
Cause: User might not have been created, or user might have been deleted from the back-end application.
Action: Contact your administrator or try different user credentials.

Level: 1

Type: ERROR

Impact: Other

WCS-08008: Service "{0}" is not a valid service or it is not supported by the "{1}" adapter implementation.
Cause: Adapter implementation does not recognize this service type.
Action: Read the documentation for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-08009: Discussion forum Category with name "{0}" already exists.
Cause: Category with the given name already exists.
Action: Try with a different category name.

Level: 1

Type: WARNING

Impact: Other

WCS-08010: Category not found.
Cause: Category does not exists or user is not authorized to access it.
Action: Provide a valid category ID.

Level: 1

Type: WARNING

Impact: Other

WCS-08011: Discussion forum object Forum with name "{0}" already exists.
Cause: Discussion forum object Forum with the given name already exists.
Action: Try with a different forum name.

Level: 1

Type: WARNING

Impact: Other

WCS-08012: No forums were found.
Cause: Forum does not exists or user is not authorized to access it.
Action: Provide a valid forum ID.

Level: 1

Type: WARNING

Impact: Other

WCS-08013: Topic not found.
Cause: Topic does not exists or user is not authorized to access it.
Action: Provide a valid topic ID.

Level: 1

Type: WARNING

Impact: Other

WCS-08014: Message not found.
Cause: Message does not exists or user is not authorized to access it.
Action: Provide a valid message ID.

Level: 1

Type: WARNING

Impact: Other

WCS-08015: There is a problem with the supplied attachments.
Cause: Possible causes: attachment was larger than expected, it was not readable or available, or it was not a supported mime type.
Action: Try with a different attachment or contact your system administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-08016: Unable to look up the forum connection with name "{0}".
Cause: Either the forum connection name is not valid or corresponding connection details are deleted from the connection store.
Action: Check the default connection name in adf-config and connection details in connection store for discussion forum service or contact your system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-08017: Ambiguous forum connection definitions found in the connection store.
Cause: More than 1 connection type found for discussion forum service. Unable to decide which one to use.
Action: Configure the appropriate connection name as the default connection to use from the management console or contact your system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-08018: Discussion forum object Message with subject "{0}" is prevented from being posted.
Cause: Discussion forum object Message is rejected because of any one of the following reasons: 1) blocking a set of users from posting, 2) preventing a user from posting more than once every X seconds, 3) rejecting any messages that contain profanity from the back-end application.
Action: If you are authorized to post messages and your text has valid language, then try again after some time.

Level: 1

Type: WARNING

Impact: Other

WCS-08019: Host address "{0}" configured in connection store is not correct.
Cause: IP address of the host configured in connection store could not be determined.
Action: Configure the correct host name in connection store or contact your system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-08020: Unable to connect to discussion server.
Cause: Possible reasons: The IP address of the host configured in the connection store could not be determined, or the connection was refused by the host.
Action: Configure the correct host name in connection store or contact your system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-08021: Forum connection details are not available in the connection store.
Cause: Forum connection details were not available in the connection store.
Action: Configure discussion forum service connection details in connection store or contact your system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-08022: Unable to create discussion forum object Forum with name "{0}".
Cause: Unable to create discussion forum object Forum with the supplied name and description.
Action: Contact your administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-08023: Not able to reach service endpoint port type due to {0}.
Cause: Service end point is not reachable.
Action: Contact your administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-08024: Input parameter value "{0}" supplied is invalid.
Cause: Invalid input parameter value is supplied.
Action: Provide valid values for the input parameters.

Level: 1

Type: ERROR

Impact: Other

WCS-08025: You do not have permission to see forums for this portal.
Cause: User is not authorized to access the forum.
Action: Contact your administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-08026: You do not have permission to see recent topics for this portal.
Cause: User is not authorized to access the recent topics.
Action: Contact your administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-08027: You do not have permission to see popular topics for this portal.
Cause: User is not authorized to access the popular topics.
Action: Contact your administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-08028: {0} not accessible.
Cause: Contact your administrator for access.
Action: Check if data exist or check for appropriate permissions.

Level: 1

Type: WARNING

Impact: Other

WCS-08029: Could not connect to the configured discussions server.
Cause: Configured discussion server is not reachable.
Action: Check if server details are correct or contact your administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-08201: Not able to create forum configuration file for community "{0}" due to : {1}.
Cause: Possible failure creating the category or forum, or an issue with the MDS write operation.
Action: Contact your system administrator or read the discussion forum service configuration documentation for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-08202: Failed to flush changes into preference store due to {0}.
Cause: Possible failure in the backing store, or a failure to contact the backing store.
Action: Contact system administrator

Level: 1

Type: ERROR

Impact: Other

WCS-09001: The IMAP host cannot be null or an empty string.
Cause: The IMAP server host address was not specified.
Action: Configure Mail Service connection.

Level: 1

Type: ERROR

Impact: Other

WCS-09002: The SMTP host cannot be null or an empty string.
Cause: The SMTP server host address was not specified.
Action: Configure Mail Service connection.

Level: 1

Type: WARNING

Impact: Other

WCS-09003: Anonymous user access is not permitted on the mail service. Users must log on to the application.
Cause: User was not logged on to the application. ADF security context was not set to authenticated user.
Action: Log on to the application using the ADF authentication mechanism.

Level: 1

Type: WARNING

Impact: Other

WCS-09004: User credentials not found in the credential store for user "{0}" with external application ID: {1}.
Cause: Mapped user credentials for the current logged on user were not found in the credential store.
Action: Supply valid credentials.

Level: 1

Type: WARNING

Impact: Other

WCS-09005: Multiple connection definitions found for mail service.
Cause: Multiple connection definitions were defined in the registry; could not identify the default connection to use.
Action: Specify the default connection to be used in adf-config.xml. For more details, refer to the Mail Service documentation for creating connections.

Level: 1

Type: WARNING

Impact: Other

WCS-09006: Lookup for connection "{0}" failed.
Cause: Failed to get the JNDI context, or the mail connection with the given name was not available.
Action: Supply proper connection name, and ensure that the entry exists in the connection repository.

Level: 1

Type: ERROR

Impact: Other

WCS-09007: ADF connections context could not be acquired. Failed to find mail connection.
Cause: Failed to get the JNDI context for the connection repository.
Action: ADF connection context details were missing from the adf-config.xml file. For more information, refer to the ADF Developer's Guide.

Level: 1

Type: ERROR

Impact: Other

WCS-09008: Failed to create mail session due to: {0}
Cause: Unexpected failure: either the IMAP/SMTP server did not respond, it failed to understand the request, or it was not configured properly.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-09009: Failed to connect to the mail server. Connection timed out.
Cause: Could not connect to the mail server in the given time.
Action: Confirm that the IMAP/SMTP servers are running or increase the timeout value.

Level: 1

Type: WARNING

Impact: Other

WCS-09010: Failed to read messages from the folder "{0}". Further information: {1}
Cause: Either the IMAP folder had issues or the search term was not supported by the server.
Action: Contact your system administrator to check the issues in the log file.

Level: 1

Type: WARNING

Impact: Other

WCS-09011: Failed to get message with ID "{0}" from the folder "{1}". Further information: {2}.
Cause: Either the IMAP folder had issues or the search term was not supported by the server.
Action: Contact your system administrator to check the issues in the log file.

Level: 1

Type: WARNING

Impact: Other

WCS-09012: Failed to send the message with subject "{0}". Further information: {1}
Cause: Either the SMTP server did not respond or the message was corrupted.
Action: Contact your system administrator to check the issues in the log file.

Level: 1

Type: ERROR

Impact: Other

WCS-09013: Message with ID "{0}" has been permanently removed from the "{1}" folder.
Cause: Either this message did not exist on the IMAP folder or it was been deleted via expunge on the folder.
Action: The IMAP folder has been expunged to permanently delete all messages. The message cannot be recovered.

Level: 1

Type: WARNING

Impact: Other

WCS-09014: Unable to find the "{0}" folder.
Cause: Either the folder with this name did not exist on the IMAP server or the mail server did not support folders.
Action: Ensure that the folder with the given name exists and that the IMAP server is properly configured.

Level: 1

Type: WARNING

Impact: Other

WCS-09015: Failed to perform the {0} operation due to: {1}.
Cause: Either the mail server was down or it did not support this operation.
Action: Ensure that the IMAP and SMTP servers are properly configured and available.

Level: 1

Type: ERROR

Impact: Other

WCS-09016: Logon failed: unknown user name or incorrect password
Cause: The user credentials acquired from the credential store were incorrect.
Action: Ensure that the user credentials supplied for logon are correct.

Level: 1

Type: WARNING

Impact: Other

WCS-09017: Could not make an attachment: not a valid body part for creating an attachment.
Cause: Either the body part was not recognized, it could not be attached to the message, or the body part could not be processed.
Action: Contact your system Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-09018: No recipients for the mail specified.
Cause: No recipients for the mail specified.
Action: At least one recipient must be specified for the mail to be delivered.

Level: 1

Type: ERROR

Impact: Other

WCS-09019: No mail connection found.
Cause: No mail connection was specified.
Action: The mail connection is not available in the connection repository. Ensure that a connection to the mail server is defined.

Level: 1

Type: ERROR

Impact: Other

WCS-09020: Connection to the server failed.
Cause: Connection to the server failed: either the host or port information was wrong or the server was down.
Action: Check the mail server connection details and ensure that the mail server is up and running.

Level: 1

Type: ERROR

Impact: Other

WCS-09021: User name to connect to the mail server for Email Gateway is not supplied.
Cause: Connection to the server failed: mail user account was not complete.
Action: User account details are required to connect to the mail server.

Level: 1

Type: ERROR

Impact: Other

WCS-09022: User password to connect to the mail server for Email Gateway is not supplied.
Cause: Connection to the server failed: mail user account is not complete.
Action: User account details are required to connect to the mail server.

Level: 1

Type: ERROR

Impact: Other

WCS-09023: Cannot attach file. Either the file exceeds the maximum allowed file size or it is empty(zero bytes). Attached files must be less than 2 MB.
Cause: Either the attachment size is 0(zero) or greater than 2 MB.
Action: Attach a file within in the expected size limit.

Level: 1

Type: ERROR

Impact: Other

WCS-09025: Message delivery failure: The message could not be sent because connecting to the SMTP mail server failed. The server may be unavailable. If the problem persists, report the error to your administrator.
Cause: Connection to the server failed: either the host or port information was wrong or the server was down.
Action: Check the mail server connection details and ensure that the mail server is up and running.

Level: 1

Type: ERROR

Impact: Other

WCS-09026: Error processing the message.
Cause: The message might have been sent with improper encoding.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-09027: The number of recipients for the mail:{0} has exceeded the maximum limit:{1} set by the space administrator.
Cause: The number of recipients for the mail has exceeded the maximum limit set by the space administrator.
Action: Reduce the number of recipients or contact the space administrator to change the maximum limit

Level: 1

Type: ERROR

Impact: Other

WCS-09201: Distribution list "{0}" already exists.
Cause: A distribution list with the supplied name already exists.
Action: Create the distribution list with a different name.

Level: 1

Type: ERROR

Impact: Other

WCS-09202: Distribution list "{0}" is not available.
Cause: A distribution list with the supplied name does not exist.
Action: Verify the supplied name and ensure that the list exists on the mail server.

Level: 1

Type: ERROR

Impact: Other

WCS-09203: Mandatory connection property "{0}" missing from the directory connection.
Cause: The mandatory connection property required to establish directory connection was not supplied.
Action: Verify the supplied directory connection details, and ensure that the required details are supplied.

Level: 1

Type: ERROR

Impact: Other

WCS-09204: Filter criteria not defined for the directory search: {0}.
Cause: Filter criteria was not defined for the directory search.
Action: Search criteria should contain filter details.

Level: 1

Type: ERROR

Impact: Other

WCS-09205: Incorrect format for the schema attribute. Value retrieved is: {0}.
Cause: The schema was not specified properly.
Action: Check the base DN for the schema details and supply the complete base DN.

Level: 1

Type: ERROR

Impact: Other

WCS-09214: Failed to acquire the initial directory context for name: {0}, due to : {1}
Cause: Failed to acquire the connection either the connection details are wrong or server is not reachable.
Action: Ensure proper configuration is provided or Contact your administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-09215: Unable to create the distribution list: {0}, Mandatory attributes missing. Further information: {1}
Cause: Mandatory attributes to create a group are missing.
Action: Contact System Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-09216: Unexpected error occurred. Further info: {0}
Cause: Unexpected error occurred contact system administrator.
Action: Contact Oracle Support

Level: 1

Type: ERROR

Impact: Other

WCS-09217: Unable to lookup the context name: {0}, due to : {1}
Cause: Unable to find the context.
Action: Contact System Administrator

Level: 1

Type: WARNING

Impact: Other

WCS-09218: Unable to destroy the context name: {0}, due to : {1}
Cause: Either context does not exists or its not a proper context name.
Action: Contact System Administrator

Level: 1

Type: WARNING

Impact: Other

WCS-09219: Unable to modify attributes for the context name: {0}, due to : {1}
Cause: Either context does not exists or its not a proper context name.
Action: Contact System Administrator

Level: 1

Type: WARNING

Impact: Other

WCS-09220: Unable to find the attribute: {0} under context {1}, due to {2}
Cause: Required attribute not found in the context object.
Action: Ensure the required attribute is available in the context object.

Level: 1

Type: WARNING

Impact: Other

WCS-09251: Failed to make attachment, due to: {0}.
Cause: Either the file size was too large or the selected file was not readable. Check the server settings.
Action: Ensure that the file is available and readable. Also ensure that the file is not too large. If the problem persists, then contact your system administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-09252: Failed to remove attachment due to: {0}.
Cause: Either this attachment did not exist or it failed to read the message. See the error log for more details.
Action: Contact your system administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-09253: Failed to send message, due to: {0}.
Cause: Either the mail session was expired or the user was not logged in.
Action: Contact your system Administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-09254: Failed to read attachments, due to: {0}.
Cause: Either the mail session is expired or the user is not logged-in.
Action: Contact your system Administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-09255: External application ID not defined.
Cause: The required configuration parameter External Application ID was not found.
Action: Contact your system Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-09256: This message has been deleted.
Cause: This message had been deleted.
Action: Only non-deleted mails can be viewed.

Level: 1

Type: WARNING

Impact: Other

WCS-09257: No compose message object found.
Cause: User may not be in the compose mode or the state is lost.
Action: Ensure the user is in compose message view.

Level: 1

Type: WARNING

Impact: Other

WCS-09258: Unable to find the attachment table component.
Cause: Unable to find the table component in the current view.
Action: Ensure the table component id name is not changed.

Level: 1

Type: WARNING

Impact: Other

WCS-09259: Unable to find the backing bean by name {0}.
Cause: Either the backing bean is removed or the name is changed.
Action: Ensure the backing bean names are intact.

Level: 1

Type: WARNING

Impact: Other

WCS-09501: An unexpected error occurred.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-09502: Supplied class {0} is not an instance of {1}.
Cause: Announcement service adapter details might not have been configured properly in the adf-config.xml file or adapter implementation class was not proper.
Action: Check that the adapter class name in the adf-config file is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-09503: Not able to invoke constructor of class {0} through Constructor.newInstance() call.
Cause: Application is trying to instantiate a class through Constructor.newInstance().
Action: Check that the adapter class name in the adf-config file is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-09504: Not able to find the method "{0}" in the class "{1}".
Cause: Matching constructor might not be found the adapter implementation class.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-09505: User "{0}" is not authorized.
Cause: Contact your administrator for access to announcements.
Action: Provide valid user credentials, or check if user exists or has appropriate permissions.

Level: 1

Type: WARNING

Impact: Other

WCS-09506: User "{0}" not logged on.
Cause: User might not have logged on to the system.
Action: Try logging on using correct user credentials.

Level: 1

Type: WARNING

Impact: Other

WCS-09507: User "{0}" is not found.
Cause: User might not have been created, or user might have been deleted from the back-end application.
Action: Contact your administrator or try different user credentials.

Level: 1

Type: WARNING

Impact: Other

WCS-09508: Announcement configuration file for community "{0}" not found or details such as category ID and announcement ID are not available.
Cause: There was a failure in creating the announcement configuration or an issue with the MDS read or write operation.
Action: Contact your system administrator or read the announcement service configuration documentation for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-09509: Announcement not found.
Cause: Announcement object with the supplied announcement ID was not available or it was not accessible.
Action: Provide a valid announcement ID.

Level: 1

Type: WARNING

Impact: Other

WCS-09510: Announcement parent not found.
Cause: Announcement parent object with the supplied ID was not available or it was not accessible.
Action: Provide a valid accessible parent ID.

Level: 1

Type: WARNING

Impact: Other

WCS-09511: Announcement parent not found.
Cause: Announcement parent object is not accessible from discussion forum.
Action: Check if discussion service is configured properly.

Level: 1

Type: WARNING

Impact: Other

WCS-09512: Unable to lookup the announcement connection with name "{0}".
Cause: Either the announcement connection name is not valid or corresponding connection details are deleted from the connection store.
Action: Check the default connection name in adf-config for discussion announcement service or contact your system administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-09513: Ambiguous announcement connection definitions found in the connection store.
Cause: More than 1 connection type found for discussion announcement service. Unable to decide which one to use.
Action: Configure the appropriate connection name as the default connection to use from the management console or contact your system administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-09516: Announcement service configuration not found
Cause: service configuration details are missing
Action: Ensure service config details are either loadable from classpath or from adf-config.

Level: 1

Type: WARNING

Impact: Other

WCS-09517: Announcement service configuration not correct.
Cause: service configuration details are not provided as expected.
Action: Correct the service configuration details.

Level: 1

Type: WARNING

Impact: Other

WCS-09518: Host address "{0}" configured in connection store is not correct.
Cause: IP address of the host configured in connection store could not be determined.
Action: Configure the correct host name in connection store or contact your system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-09519: Not able to log on to the back-end system with host address "{0}".
Cause: Possible reasons: The IP address of the host configured in the connection store could not be determined, or the connection was refused by the host.
Action: Configure the correct host name in connection store or contact your system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-09520: Expiry date cannot be earlier than start date.
Cause: Expiry date is specified to be earlier than start date.
Action: Specify expiry date to be later than start date.

Level: 1

Type: WARNING

Impact: Other

WCS-09521: Not able to query data from SQL Connection.
Cause: Possible reasons: The database is down or invalid SQL Connection configuration in the DataSource.
Action: Configure the correct SQL Connection in the DataSource.

Level: 1

Type: ERROR

Impact: Other

WCS-09522: Announcement parent not accessible.
Cause: Contact your administrator for access to announcements.
Action: Check if announcements parent exists or user has permissions to access announcements.

Level: 1

Type: WARNING

Impact: Other

WCS-09523: Could not connect to the configured discussions server.
Cause: Configured discussion server is not reachable.
Action: Check if server details are correct or contact your administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-09601: Not able to create announcement configuration file for community {0} due to : {1}.
Cause: Possible failure creating category or announcement or an issue with the MDS write operation.
Action: Contact your system administrator or read the announcement service configuration documentation for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-09602: Failed to flush changes into preference store due to {0}.
Cause: Possible failure in the backing store, or failure to contact the backing store.
Action: Contact system administrator

Level: 1

Type: ERROR

Impact: Other

WCS-11001: Error on content write: {0}
Cause: The content write operation failed for the given reason.
Action: Investigate the reason for the failure.

Level: 1

Type: ERROR

Impact: Other

WCS-11002: Internal server error: {0}
Cause: An unexpected internal error has occurred.
Action: Contact your Oracle Support representative.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-11003: Invalid Request
Cause: The client has submitted an invalid HTTP request.
Action: Re-send the corrected request.

Level: 1

Type: WARNING

Impact: Other

WCS-11004: Path not found: {0}
Cause: The requested path has not been found on the server.
Action: Correct the path on the client and re-send the request.

Level: 1

Type: WARNING

Impact: Other

WCS-11005: Not an ISO8601 date: {0}
Cause: The client supplied a date which is not in ISO8601 format.
Action: Correct the date format on the client and re-send the request.

Level: 1

Type: WARNING

Impact: Other

WCS-11006: Not an HTTP date: {0}
Cause: The client supplied a date which is not in HTTP date format.
Action: Correct the date format on the client and re-send the request.

Level: 1

Type: WARNING

Impact: Other

WCS-11007: Namespace not supported: {0}
Cause: The repository does not support the given namespace.
Action: Specify a valid namespace.

Level: 1

Type: WARNING

Impact: Other

WCS-11008: Bad request
Cause: The client submitted a request that could not be understood by the server.
Action: Correct the syntax and resubmit the request.

Level: 1

Type: WARNING

Impact: Other

WCS-11009: Not modified
Cause: The client has performed a conditional GET request, access is allowed but the document has not changed.
Action: No action required as resource has not been modified and hence it is not returned.

Level: 1

Type: ERROR

Impact: Other

WCS-11010: Not acceptable
Cause: The requested resource could not generate an entity with an acceptable media-type for the client.
Action: If applicable, resubmit the request with a broader acceptance criteria.

Level: 1

Type: ERROR

Impact: Other

WCS-11011: Precondition failed
Cause: A request precondition has failed.
Action: If applicable, resubmit the request with different preconditions.

Level: 1

Type: ERROR

Impact: Other

WCS-11012: The Java virtual machine does not support the UTF-8 character set.
Cause: The UTF-8 character set is not supported by the Java virtual machine.
Action: Contact your Oracle Support Representative.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-11013: No DAV dead property name matches the JCR property name {0}.
Cause: A unexpected JCR property name has been found that does not correspond to a DAV dead property name.
Action: Contact your Oracle Support Representative.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-11014: Cannot close the servlet output stream.
Cause: There was an error closing the servlet output stream.
Action: Review the server logs for possible cause of failure.

Level: 1

Type: ERROR

Impact: Other

WCS-11015: Cannot close content input stream.
Cause: There was an error closing the content input stream.
Action: Review the server logs for possible cause of failure.

Level: 1

Type: ERROR

Impact: Other

WCS-11016: Invalid resource name: {0}
Cause: The given name is not a valid resource name.
Action: The client should resubmit the request with a corrected URL.

Level: 1

Type: ERROR

Impact: Other

WCS-11017: Invalid resource name; illegal escape sequence in path: {0}
Cause: The given name was not a valid resource name as it contains an illegal escape sequence.
Action: The client should resubmit the request with a corrected URL.

Level: 1

Type: WARNING

Impact: Other

WCS-11018: Forbidden request method: {0}
Cause: The requested HTTP method was not completed as the server forbids the execution of this type of method.
Action: Compatible clients should not use the specified HTTP method.

Level: 1

Type: ERROR

Impact: Other

WCS-11019: Folder listing is disabled.
Cause: Folder listing has been disabled.
Action: Folder listing must be explicitly enabled in the application's web.xml.

Level: 1

Type: WARNING

Impact: Other

WCS-11020: Error storing uploaded file content.
Cause: Uploaded file could not be stored.
Action: Check other errors for cause.

Level: 1

Type: WARNING

Impact: Other

WCS-11021: Error verifying CSRF token: ADF session scope token null.
Cause: CSRF could not be verified as session CSRF null.
Action: Contact your Oracle Support representative.

Level: 1

Type: WARNING

Impact: Other

WCS-11022: CSRF token check fail, session and request token mis-match.
Cause: CSRF verification failed as request and session tokens do not match.
Action: Contact your Oracle Support representative.

Level: 1

Type: WARNING

Impact: Other

WCS-11023: CSRF token check fail, session and multi-part form token mis-match. Form: {0} Session {1}
Cause: CSRF verification failed as session and multipart form tokens do not match.
Action: Contact your Oracle Support representative.

Level: 1

Type: WARNING

Impact: Other

WCS-11024: Cannot write file as CSRF not verified.
Cause: File write prohibitied as CSRF not verified.
Action: Contact your Oracle Support representative.

Level: 1

Type: WARNING

Impact: Other

WCS-11025: Error while writing response..
Cause: An error occured on sending upload response.
Action: Check other errors for cause.

Level: 1

Type: WARNING

Impact: Other

WCS-12001: Following services are not configured: {0}. Configure these services and retry the operation.
Cause: Portals imported requires some services that are not configured in the instance.
Action: Ensure that the specified services are included and configured in the application and restart the import process.

Level: 1

Type: ERROR

Impact: Other

WCS-12002: The handler found in the classpath at run time cannot process the data or metadata of the archive: {0}.
Cause: Handlers enable services to manage their data and metadata in the manner best suited to each service. The version of the handler used during import was not compatible with the version of the handler used while creating the data or metadata on export.
Action: Include compatible versions of handlers in the application and restart the import process.

Level: 1

Type: ERROR

Impact: Other

WCS-12003: The required handlers are not found: {0}.
Cause: Handlers enable services to manage their data and metadata in the manner best suited to each service. Not all handlers that were used while creating this archive could be found during the import.
Action: Ensure that the specified services are included and configured in the application and restart the import process.

Level: 1

Type: ERROR

Impact: Other

WCS-12004: Unable to retrieve the JAXB bean for the export/import document in MDS.
Cause: An error occurred in the MDS configuration of the application.
Action: Check the MDS configuration files of the application.

Level: 1

Type: ERROR

Impact: Other

WCS-12006: The export archive does not contain any scope metadata.
Cause: An error occurred during the export process, or the exported archive was damaged.
Action: Reattempt import with a different export file.

Level: 1

Type: ERROR

Impact: Other

WCS-12007: Scope with name {0} already exists in the import destination and it does not match with the scope being imported.
Cause: A scope with the specified name already exists for the current application instance. This caused a conflict between the source and target instances.
Action: Delete the scope from the current application instance and reattempt the import.

Level: 1

Type: ERROR

Impact: Other

WCS-12008: The export archive is from an older version of WebCenter Portal and is not compatible with the current version.
Cause: The export archive is created using an older version. This archive cannot be imported into the current version of WebCenter Portal.
Action: Reattempt import with a newer export archive.

Level: 1

Type: ERROR

Impact: Other

WCS-12009: The Lifecycle Manager MBean cannot be deregistered.
Cause: There are numerous possible reasons for this failure.
Action: For information, review other messages in the log file and the reported exception stacks.

Level: 1

Type: WARNING

Impact: Other

WCS-12009: The Lifecycle Manager MBean cannot be deregistered.
Cause: There are numerous possible reasons for this failure.
Action: For information, review other messages in the log file and the reported exception stacks.

Level: 1

Type: WARNING

Impact: Other

WCS-12010: The Lifecycle Manager MBean cannot be created and registered. This problem will not prevent the application from running. However, the Lifecycle Manager will be unavailable.
Cause: There are numerous possible reasons for this failure.
Action: For information, review other messages in the log file and the reported exception stacks.

Level: 1

Type: WARNING

Impact: Other

WCS-12010: The Lifecycle Manager MBean cannot be created and registered. This problem will not prevent the application from running. However, the Lifecycle Manager will be unavailable.
Cause: There are numerous possible reasons for this failure.
Action: For information, review other messages in the log file and the reported exception stacks.

Level: 1

Type: WARNING

Impact: Other

WCS-12012: Information related to run time MBeans cannot be saved in the ADFContext application scope.
Cause: The system failed to store data in the ADFContext application scope. Lifecycle functions may not be available.
Action: Review the log files to see if there are any other problems which may have resulted in the ADFContext object becoming unusable.

Level: 1

Type: WARNING

Impact: Other

WCS-12012: Information related to run time MBeans cannot be saved in the ADFContext application scope.
Cause: The system failed to store data in the ADFContext application scope. Lifecycle functions may not be available.
Action: Review the log files to see if there are any other problems which may have resulted in the ADFContext object becoming unusable.

Level: 1

Type: WARNING

Impact: Other

WCS-12013: An internal class cast error has occurred. Actual class: {0}, cast-to class: {1}.
Cause: The possible errors could be in the code or application configuration.
Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12014: The activity {0} has ended but completed less child activities ({1}) than the expected ({2}).
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12015: The activity {0} has ended but completed more child activities ({1}) than the expected ({2}).
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12016: The activity {0} has completed more child activities ({1}) than the expected ({2}).
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12017: The export/import listener {0} has thrown an exception, which is being ignored.
Cause: A class listening to export/import progress events has thrown an exception.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: WARNING

Impact: Other

WCS-12018: The resource {0} for lifecycle operation cannot be found on the classpath.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12019: The connection {0} cannot be exported because it is not a Reference or Referenceable.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12020: An error has occurred while exporting the connection {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12021: The output stream for table {0} failed to close. The exception {1} will not be thrown.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12022: A SQL exception was thrown while closing the connection. This exception will be ignored.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12023: An error has occurred while closing the output stream to which the XML was being written. The export process will not be aborted.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12024: Value of the SQL type is not recognized, attempting to use the CHAR handler.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12025: Value of the SQL type is not recognized.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12026: A SQL exception {0} was caught while rolling back in response to an earlier exception {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12027: A SQL exception {0} was caught while closing the statement {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12028: A SQL exception {0} was caught while closing the connection {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12029: An error {1} has occurred while creating a DocumentName for table {0}. The import will not be aborted.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12030: An error {1} has occurred while retrieving input stream from MDS for {0}. The import will not be aborted.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12031: An error {1} has occurred while deleting the table export document {0} from MDS. The import will not be aborted.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12032: The Queue Callback handler was interrupted while waiting for child threads to complete.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12033: Exception occurred in child thread: {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12034: The Queue Consumer with name {0} was interrupted while taking an object from the queue. The Queue Consumer will continue and ignore the exception: {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12038: IOException while creating stage directory for export
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12038: IOException while creating stage directory for export
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12039: IOException while creating temporary directory to extract the import archive to
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12039: IOException while creating temporary directory to extract the import archive to
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12040: IOException extracting import archive
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12040: IOException extracting import archive
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12041: Input archive path not set on context.
Cause: The possible errors could be in the code or application configuration.
Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12041: Input archive path not set on context.
Cause: The possible errors could be in the code or application configuration.
Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12042: Input archive does not exist.
Cause: The possible errors could be in the code or application configuration.
Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12042: Input archive does not exist.
Cause: The possible errors could be in the code or application configuration.
Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12043: MDSConfigurationException constructing source instance for MDS transfer.
Cause: The possible errors could be in the code or application configuration.
Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12043: MDSConfigurationException constructing source instance for MDS transfer.
Cause: The possible errors could be in the code or application configuration.
Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12044: An unanticipated exception {0} has occurred while generating the oracle-archive.xml deployment descriptor of the export archive.
Cause: Cause is dependent upon the type and details of the exception being processed.
Action: Review the exception being processed for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-12045: Operation aborted because of an exception thrown by subunit ({0})
Cause: The cause of the exception that was thrown is dependent upon the type and details of the exception.
Action: Review the exception thrown for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-12046: MDSException while creating lifecycle document in MDS transfer source
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12047: The import archive file does not contain a metadata archive.
Cause: The supplied file to import was not a valid export archive.
Action: Retry the import operation with a valid export archive.

Level: 1

Type: ERROR

Impact: Other

WCS-12047: The import archive file does not contain a metadata archive.
Cause: The supplied file to import was not a valid export archive.
Action: Retry the import operation with a valid export archive.

Level: 1

Type: ERROR

Impact: Other

WCS-12048: FileNotFoundException extracting metadata transport archive
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Resolve any hardware or file system errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12048: FileNotFoundException extracting metadata transport archive
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Resolve any hardware or file system errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12049: IOException while extracting metadata transport archive
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12049: IOException while extracting metadata transport archive
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12050: IOException while creating metadata transport archive
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12050: IOException while creating metadata transport archive
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12051: Output path has not been set on operation context.
Cause: The possible errors could be in the code or application configuration.
Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12051: Output path has not been set on operation context.
Cause: The possible errors could be in the code or application configuration.
Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12052: MDSException constructing transfer list for MDS transfer.
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12053: MDSException performing MDS transfer.
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12053: MDSException performing MDS transfer.
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12054: MDSException deleting existing metadata.
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12055: An exception has occurred while creating the transformer factory to write lifecycle information document.
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12056: IOException occurred creating lifecycle information document
Cause: An error occurred writing to the file system while creating the lifecycle information document. The possible causes could be application configuration, or hardware errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12057: TransformerException while writing lifecycle information document
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12058: Input path has not been set on operation context.
Cause: The possible errors could be in the code or application configuration.
Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12059: IOException while creating oracle-archive.xml
Cause: An error occurred while writing the oracle-archive.xml file to the file system. The possible causes could be application configuration, or hardware errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12060: IOException while creating transport archive
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12060: IOException while creating transport archive
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12061: Output archive path has not been set on operation context.
Cause: The possible errors could be in the code or application configuration.
Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12061: Output archive path has not been set on operation context.
Cause: The possible errors could be in the code or application configuration.
Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12062: An unexpected exception occurred while removing lock {0}:{1}
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12063: MDSException occurred while removing lock {0}:{1}
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12064: A lock is blocking application import.
Cause: Another operation was being performed that prevented the import.
Action: Retry the import operation after the other operation is complete.

Level: 1

Type: ERROR

Impact: Other

WCS-12065: A lock is blocking application import.
Cause: Another operation was being performed that prevented the import.
Action: Retry the import operation after the other operation is complete

Level: 1

Type: ERROR

Impact: Other

WCS-12066: MDSException while creating application import lock
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12067: A lock is blocking the import of scope {0}.
Cause: Another operation was being performed that prevented the import.
Action: Retry the import operation after the other operation is complete

Level: 1

Type: ERROR

Impact: Other

WCS-12068: A lock exists that prevents the import of scope {0}.
Cause: An import of the specified scope was being performed that prevented this import.
Action: Retry the import operation after the other operation is complete

Level: 1

Type: ERROR

Impact: Other

WCS-12069: MDSException while creating scope import lock
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12070: A lock exists that blocks the export set import.
Cause: Another operation was being performed that prevented the export set import.
Action: Retry the import operation after the other operation is complete

Level: 1

Type: ERROR

Impact: Other

WCS-12071: A lock exists that prevents the export set import.
Cause: An export set import was already being performed preventing this import.
Action: Retry the import operation after the other operation is complete

Level: 1

Type: ERROR

Impact: Other

WCS-12072: MDSException while creating an export set import lock
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12073: MDSException while obtaining the Lifecycle bean from the MDS session
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12074: ID of export set in MDS does not match that of the application. MDS ID: {0}, Application ID: {1}.
Cause: An export set was imported from an incompatible source and has been ignored.
Action: Import an export set from a compatible instance.

Level: 1

Type: ERROR

Impact: Other

WCS-12076: NamingException while binding connection {0} to the export connections.xml
Cause: The possible causes could be coding or application configuration errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12077: NamingException while getting environment for exporting the ADF credential store
Cause: The possible causes could be coding or application configuration errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12078: IOException while exporting ADF credential store
Cause: The possible causes could be coding, hardware, or file system errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12079: JPSException while exporting JPS credential store
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12080: MDSException while creating lifecycle information metadata in transport set
Cause: An existing document with the same name as the lifecycle information document was found in the transport set being constructed.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12081: ReferenceException while creating lifecycle information metadata in transport set
Cause: An unexpected exception occurred while creating the lifecycle document in transport set.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12082: UnsupportedUpdateException while creating lifecycle information metadata in transport set
Cause: An unexpected exception occurred while creating the lifecycle document in the transport set.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12083: MDSException while building transfer list for lifecycle metadata
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12084: MDSException while constructing metadata store for MDS transfer
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12084: MDSException while constructing metadata store for MDS transfer
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12085: ParserConfigurationException while creating lifecycle information document
Cause: An unexpected exception occurred while creating the lifecycle document in the transport set.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12086: SAXException while creating lifecycle information document
Cause: An unexpected exception occurred while creating the lifecycle document in the transport set.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12087: ServiceException while getting registered services
Cause: There was an error in the application's configuration.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12088: Cannot find lifecycle service extension registry
Cause: An error in the application's configuration.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12089: Destination path specified to create the temporary directory is not a directory.
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Resolve any application configuration or hardware errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12089: Destination path specified to create the temporary directory is not a directory.
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Resolve any application configuration or hardware errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12090: The source path specified to archive does not exist
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Resolve any application configuration or hardware errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12090: The source path specified to archive does not exist
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Resolve any application configuration or hardware errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12091: The source path specified to archive is not a directory
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Resolve any application configuration or hardware errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12091: The source path specified to archive is not a directory
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Resolve any application configuration or hardware errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12092: A file already exists with the same name as the destination folder.
Cause: A call was made to extract an archive to a destination directory with the same name as an existing file.
Action: Retry the operation that caused this error.

Level: 1

Type: ERROR

Impact: Other

WCS-12092: A file already exists with the same name as the destination folder.
Cause: A call was made to extract an archive to a destination directory with the same name as an existing file.
Action: Retry the operation that caused this error.

Level: 1

Type: ERROR

Impact: Other

WCS-12093: {0} is an invalid value for the maximum number of steps. The maximum number of steps must be a least 1.
Cause: The probable cause is a coding error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12094: MDSException while constructing metadata store for MDS transfer
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12094: MDSException while constructing metadata store for MDS transfer
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12095: Import archive file does not exist or could not be read.
Cause: The specified file could not be found either because it does not exist or does not have the correct access permissions.
Action: Check that the path is correct, the file exists and has the appropriate access permissions.

Level: 1

Type: ERROR

Impact: Other

WCS-12095: Import archive file does not exist or could not be read.
Cause: The specified file could not be found either because it does not exist or does not have the correct access permissions.
Action: Check that the path is correct, the file exists and has the appropriate access permissions.

Level: 1

Type: ERROR

Impact: Other

WCS-12096: A lock is blocking application export.
Cause: Another operation was being performed that prevented the export.
Action: Retry the export operation after the other operation is complete.

Level: 1

Type: ERROR

Impact: Other

WCS-12097: A lock is blocking application export.
Cause: Another operation was being performed that prevented the export.
Action: Retry the export operation after the other operation is complete

Level: 1

Type: ERROR

Impact: Other

WCS-12098: MDSException while creating application export lock
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12099: An unexpected exception occurred while refreshing lock {0}:{1}
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: WARNING

Impact: Other

WCS-12100: MDSException occurred while refreshing lock {0}:{1}
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: WARNING

Impact: Other

WCS-12101: Unable to find data source
Cause: The data source hasn't been configured
Action: Configure the data source

Level: 1

Type: ERROR

Impact: Other

WCS-12102: An exception occurred while refreshing lock {0}:{1}
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12103: Unexpected RuntimeException performing MDS transfer.
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12103: Unexpected RuntimeException performing MDS transfer.
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12104: Unexpected exception occurred while exporting portlet producer information. The producer may be down or unavailable.
Cause: The possible causes could be the portlet producer is down or unavailable, errors from the portlet producer, or application configuration.
Action: Check that the portlet producers are available, and then retry the export. Review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12104: Unexpected exception occurred while exporting portlet producer information. The producer may be down or unavailable.
Cause: The possible causes could be the portlet producer is down or unavailable, errors from the portlet producer, or application configuration.
Action: Check that the portlet producers are available, and then retry the export. Review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12106: Document {0} has been excluded from the export set.
Cause: The path of the document exceeds file system constraints and therefore cannot be exported.
Action: None

Level: 1

Type: ERROR

Impact: Other

WCS-12107: InvalidReferenceException constructing MDS rename plan for upgrade.
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12108: MDSException performing MDS rename for upgrade.
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12109: MDSException while committing metadata changes for upgrade.
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12110: Unable to import Scope {0} under Scope {0}
Cause: Unable to import scope under itself
Action: Import the scope either as a root level scope or specify a different parent for the scope.

Level: 1

Type: ERROR

Impact: Other

WCS-12111: Unable to import {0} as a root level scope as it inherits security.
Cause: Unable to import scope as a root level scope as it inherits security.
Action: Import the scope as a subscope and not as a root level scope.

Level: 1

Type: ERROR

Impact: Other

WCS-12112: The parent scope {0} does not exist
Cause: Unable to import as the parent scope does not exist
Action: Import the scope either as a root level scope or specify a different parent for the scope.

Level: 1

Type: ERROR

Impact: Other

WCS-12113: Export operation aborted due to the following reasons. {0}
Cause: Export operation aborted
Action: Retry the operation fixing the cause of failure

Level: 1

Type: ERROR

Impact: Other

WCS-12114: Failed to fetch the handler due to invalid resource type - {0}
Cause: Invalid Resource type is passed during import.
Action: Retry the operation with the correct resource type.

Level: 1

Type: ERROR

Impact: Other

WCS-12115: Portal Export operation aborted due to the following reasons. {0}
Cause: Backup operation aborted
Action: Retry the operation fixing the cause of failure

Level: 1

Type: ERROR

Impact: Other

WCS-12116: Exception while creating the export label
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12117: Portal {0} already exists. If you want to overwrite the portal use the ''overwrite'' option.
Cause: Portal already exists.
Action: If you want to overwrite the existing portal, use the ''overwrite'' option.

Level: 1

Type: ERROR

Impact: Other

WCS-12118: A SQL exception {0} was caught while closing the resultset.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12119: Unable to upload as the archive does not contain a shared asset.
Cause: The asset you are trying to upload belongs to a specific portal, it is not a shared asset.
Action: Verify which portal owns the asset and then upload the asset to that portal.

Level: 1

Type: ERROR

Impact: Other

WCS-12120: Unable to upload the asset as the archive does not contain an asset that belongs to this portal.
Cause: The asset you are trying to upload belongs to a different portal.
Action: Verify which portal owns the asset and then upload the asset to that portal.

Level: 1

Type: ERROR

Impact: Other

WCS-12121: A lock is blocking the deployment of portal: {0}.
Cause: Another operation was being performed that prevented the deployment.
Action: Retry the deployment operation after the other operation is complete

Level: 1

Type: ERROR

Impact: Other

WCS-12122: A lock is blocking the propagation of portal: {0}.
Cause: Another operation was being performed that prevented the propagation.
Action: Retry the propagation operation after the other operation is complete

Level: 1

Type: ERROR

Impact: Other

WCS-12123: Unable to deploy the portal "{0}" because this portal is currently being deployed to the target "{1}" by "{2}". Try again later.
Cause: Deployment of the specified portal to the specific target portal server was being performed that prevented this current deployment operation.
Action: Retry the deployment operation after the other operation is complete

Level: 1

Type: ERROR

Impact: Other

WCS-12124: Unable to deploy the portal "{0}" because changes for this portal are currently being propagated to the target "{1}" by "{2}". Try again later.
Cause: Propagation of the specified portal to the specific target portal server was being performed that prevented this current deployment operation.
Action: Retry the deployment operation after the other operation is complete

Level: 1

Type: ERROR

Impact: Other

WCS-12125: Changes for portal "{0}" cannot be propagated because this portal is currently being deployed to the target "{1}" by "{2}". Try again later.
Cause: Deployment of the specified portal to the specific target portal server was being performed that prevented this current propagation operation.
Action: Retry the propagation operation after the other operation is complete

Level: 1

Type: ERROR

Impact: Other

WCS-12126: Changes for portal "{0}" cannot be propagated because changes for this portal are currently being propagated to the target "{1}" by "{2}". Try again later.
Cause: Propagation of the specified portal to the specific target portal server was being performed that prevented this current propagation operation.
Action: Retry the propagation operation after the other operation is complete

Level: 1

Type: ERROR

Impact: Other

WCS-12127: MDSException while creating portal deployment lock
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12128: An internal error occurred while exporting portal data. Refer to the WebCenter Portal Server log for more information.
Cause: An exception was thrown while exporting the persistence data for the portal.
Action: Retry the operation. If the exception occurs again, review the full exception stack for details.

Level: 1

Type: ERROR

Impact: Other

WCS-12129: An internal error occurred while importing portal data. Refer to the WebCenter Portal Server log for more information.
Cause: An exception was thrown while importing the persistence data for the portal.
Action: Retry the operation. If the exception occurs again, review the full exception stack for details.

Level: 1

Type: ERROR

Impact: Other

WCS-12130: No user created assets of type "{0}" exist in the portal "{1}" for export.
Cause: No user created assets of the specified type exist in the portal for export.
Action: Refresh the list of assets to see if the assets you are attempting to still exist.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12131: No user created global assets of type "{0}" exist for export.
Cause: No user created global assets of the specified type exist for export.
Action: Refresh the list of assets to see if the assets you are attempting to still exist.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12132: Changes for portal "{0}" cannot be propagated because Oracle WebCenter Content Server is not configured properly.
Cause: Propagation of the specified portal failed because Oracle WebCenter Content Server has not been configured properly.
Action: Retry the propagation operation after fixing the Oracle WebCenter Content Server configuration on the Oracle WebCenter Portal Server instance.

Level: 1

Type: ERROR

Impact: Other

WCS-12133: Specify a valid name for the asset archive. Usage of special character / or \ is not allowed.
Cause: Usage of special character / or \ is not allowed.
Action: Specify a valid name for the asset archive.

Level: 1

Type: ERROR

Impact: Other

WCS-12134: Invalid asset archive extension provided: {0}. Specify a valid name for the asset archive using the file extension {1}.
Cause: Invalid asset archive extension specified.
Action: Specify a valid name for the asset archive using the file extension ''.aar''.

Level: 1

Type: ERROR

Impact: Other

WCS-12135: Specify a valid name for the asset archive using the file extension {0}.
Cause: Invalid file extension specified.
Action: Specify a valid name for the asset archive using the file extension ''.aar''.

Level: 1

Type: ERROR

Impact: Other

WCS-12136: An exception occurred while finding the conflicting assets.
Cause: An exception was thrown while finding the conflicting assets.
Action: Retry the operation. If the exception occurs again, review the full exception stack for details.

Level: 1

Type: ERROR

Impact: Other

WCS-12137: The archive specified is corrupted. Specify a valid archive, and try again.
Cause: The specified archive is corrupted and could not be imported.
Action: Ensure the export archive is valid and retry the import operation.

Level: 1

Type: ERROR

Impact: Other

WCS-12138: Operation aborted because of an exception thrown due to missing configuration mandated for secured lifecycle operations. Fix the configuration issues, and try again.
Cause: Operation aborted because of an exception thrown due to missing configuration mandated for secured lifecycle operations.
Action: Retry the operation after fixing the configuration mandated for secured lifecycle operations on the Oracle WebCenter Portal Server instance.

Level: 1

Type: ERROR

Impact: Other

WCS-12139: An exception occurred while calculating the checksum for the contents.
Cause: An exception occurred while calculating the checksum for the contents.
Action: Retry the operation and review the full exception stack for details of the exception should it recur.

Level: 1

Type: ERROR

Impact: Other

WCS-12140: Import and upload operations have reached the maximum number of concurrent operations allowed. Try again later.
Cause: Import and upload operations have reached the maximum number of concurrent operations allowed.
Action: Retry the operation after any one of the concurrent operations has completed.

Level: 1

Type: ERROR

Impact: Other

WCS-12141: An error occurred while deleting the portal deployment records.
Cause: The possible causes could be application configuration or hardware issues.
Action: Retry the operation. If the error persists, review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12900: Invalid portal template archive extension provided: {0}. Specify a valid name for the portal template archive and use the file extension {1}.
Cause: Invalid portal template archive extension specified.
Action: Specify a valid name for the portal template archive and use the file extension '.par'

Level: 1

Type: ERROR

Impact: Other

WCS-12901: An unexpected error has occurred, unable to save the archive: {0}
Cause: Unexpected erro occurred while saving the archive.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-12902: Specify an archive that exists on the server.
Cause: Unable to locate archive for import.
Action: Specify a valid archive that exists on the server and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-12903: An unexpected error has occurred, unable to complete the import process.
Cause: Unable to complete the import process.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-12904: Unable to upload archive from the local file system.
Cause: Unable to upload the archive from the local file system.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-12905: Cannot save the export archive to the local file system because the file size exceeds the maximum value allowed.
Cause: Cannot save the export archive to the local file system because the file size exceeds the maximum value allowed.
Action: Save the archive to a server and then transfer the file separately.

Level: 1

Type: ERROR

Impact: Other

WCS-12906: The portal archive specified is invalid. Specify a valid archive with file extension ''{0}'', and try again.
Cause: Invalid portal archive extension specified.
Action: Specify a valid name for the portal archive with the file extension '.par'

Level: 1

Type: ERROR

Impact: Other

WCS-12920: A problem was encountered when invoking a method on a remote mBean ({0}) which has caused the local operation to fail.
Cause: In order for the local operation to be performed a method on a remote mBean has to be invoked - there are numerous reasons why the remote method invocation could fail ranging from connection problems between servers to the remote object simply not existing
Action: Review the log files for a record of this error in order to ascertain the primary cause.

Level: 1

Type: ERROR

Impact: Other

WCS-12950: The required customization class is not found: {0}
Cause: To export the specified customization class, first an instance of the class must be created. An instance of this class could not be created because the class was not included in the classpath.
Action: Include the customization class in the classpath of the application and restart the application.

Level: 1

Type: ERROR

Impact: Other

WCS-12951: The required customization class cannot be instantiated: {0}
Cause: To export the specified customization class, first an instance of the class must be created. An instance of this class could not be created because it is an interface or abstract class.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12952: The required customization class cannot be instantiated: {0}
Cause: To export the specified customization class, first an instance of the class must be created. An instance of this class could not be created because the current method was unable to access it.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12953: A listener cannot be registered to generate notification about the progress of the export. The export will continue but notification will not be generated on its progress.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12955: The notification arrived out of sequence. Latest sequence:{0}; sequence of this notification:{1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-12957: Exception occurred while importing data. No data imported.
Cause: The issue may be due to a hardware error or an application configuration error.
Action: Review other messages in the log file and the reported exception stacks for additional information. Resolve any application configuration or hardware errors.

Level: 1

Type: WARNING

Impact: Other

WCS-12958: Import failed with errors.
Cause: The issue may be due to a hardware error or an application configuration error.
Action: Review other messages in the log file and the reported exception stacks for additional information. Resolve any application configuration or hardware errors.

Level: 1

Type: ERROR

Impact: Other

WCS-12959: Export failed with errors.
Cause: The issue may be due to a hardware error or an application configuration error.
Action: Review other messages in the log file and the reported exception stacks for additional information. Resolve any application configuration or hardware errors.

Level: 1

Type: ERROR

Impact: Other

WCS-12980: Service {0} has not been provisioned for Scope {1}.
Cause: The Service has not been provisioned for the specified Scope.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12981: Service {0} has already been provisioned for Scope {1}.
Cause: The Service has already been provisioned for the specified Scope.
Action: Do not provision the Service for a Scope it is already provisioned for or unprovision the Service first.

Level: 1

Type: ERROR

Impact: Other

WCS-12982: Scope {0} is not known.
Cause: A Scope with the specified name has not been created.
Action: Create a Scope with the specified name using the createScope method on the ServiceContext.

Level: 1

Type: ERROR

Impact: Other

WCS-12983: Service {0} has not been configured for the application.
Cause: The Service has not been configured for the application.
Action: Configure the Service and try the operation again.

Level: 1

Type: ERROR

Impact: Other

WCS-12984: An error occurred removing the security policies for service {0}.
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-12985: An error occurred invoking isProvisioned for service {0}.
Cause: The possible causes could be coding, application configuration, or hardware errors.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: WARNING

Impact: Other

WCS-12986: An error occurred invoking isEnabled for service {0}.
Cause: The possible causes could be coding or application configuration.
Action: Review the full exception stack for details of the exception.

Level: 1

Type: WARNING

Impact: Other

WCS-12990: Specified key does not match that of the lock with type ''{0}'' and name ''{1}''.
Cause: The application attempted to manipulate a lock with an incorrect lock key.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12991: Lock with type ''{0}'' and name ''{1}'' already exists.
Cause: A lock with the specified type and name already exists.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12992: Lock with type ''{0}'' and name ''{1}'' does not exist.
Cause: The application attempted to manipulate a lock that no longer exists.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12993: Lock with type ''{0}'' and name ''{1}'' could not be created as a lock with type ''{2}'' exists.
Cause: A lock with a type that prevents locks with the specified type being created exists.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14001: An unexpected error occurred.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14002: An object of type {0} with this id ({1}) already exits.
Cause: An attempt was made to create an object with an id that is already in use.
Action: Specify a unique id.

Level: 1

Type: ERROR

Impact: Other

WCS-14004: The name ({0}) is not valid.
Cause: The specified name is not valid.
Action: Specify a valid name.

Level: 1

Type: ERROR

Impact: Other

WCS-14005: The specified list type could not be found.
Cause: The specified list type could not be found. This may be due to the list type being deleted by another user.
Action: Try reloading to see if the list has been deleted.

Level: 1

Type: ERROR

Impact: Other

WCS-14006: Object has been changed by another user.
Cause: The object has been changed by another user.
Action: Reload the object and try the operation again.

Level: 1

Type: ERROR

Impact: Other

WCS-14007: An Object of type {0} with id={1} could not be found.
Cause: The specified object could not be found. This may be due to the list being deleted by another user.
Action: Specify a valid id.

Level: 1

Type: ERROR

Impact: Other

WCS-14008: Object ({0}) is immutable.
Cause: An attempt to change this object was made, but this object is currently immutable.
Action: Retrieve mutable object to make changes.

Level: 1

Type: ERROR

Impact: Other

WCS-14010: {0} is not a valid reference name to MDS.
Cause: The name is not a valid MDS reference name.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14011: The MDS session does not support updates.
Cause: MDS was not configured correctly to support updates.
Action: Configure the MDS store to support updates.

Level: 1

Type: ERROR

Impact: Other

WCS-14012: An IO error occurred when accessing metadata.
Cause: An IO error occurred in MDS.
Action: See the log for more details on the specific IO error to correct the problem.

Level: 1

Type: ERROR

Impact: Other

WCS-14013: The object is not valid.
Cause: The metadata for the object does not pass validation.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14014: Failed to construct attribute set for list [{0}].
Cause: Failed to construct attribute set for list.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14015: Failed to add data flavor to ListTransferable. List=[{0}] DataFlavor=[{1}]
Cause: Failed to add data flavor to ListTransferable.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14016: The query attribute predicate {0}{1}{2} was ignored because the column does not exist or the comparator is not supported.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-14017: An error occurred when deleting metadata.
Cause: An error occurred in MDS while deleting metadata.
Action: See the log for more details on the specific error to correct the problem.

Level: 1

Type: ERROR

Impact: Other

WCS-14018: A column with the name ({0}) already exists.
Cause: A column was created or renamed with the name of an existing column in the list.
Action: Specify a unique column name within the list.

Level: 1

Type: ERROR

Impact: Other

WCS-14019: A list with the name ({0}) already exists.
Cause: A list was created or renamed with the name of an existing list.
Action: Specify a unique list name.

Level: 1

Type: ERROR

Impact: Other

WCS-14020: The maximum number of columns for this list has been exceeded.
Cause: A list was created or modified with more than 30 columns.
Action: Do not add more than 30 columns to a list.

Level: 1

Type: ERROR

Impact: Other

WCS-14021: User does not have permission to perform {0} operation for {1}.
Cause: User does not have permission to perform the specified operation.
Action: Grant the user permission to perform the specified operation.

Level: 1

Type: ERROR

Impact: Other

WCS-14022: The Lists service is not provisioned for scope {0}.
Cause: The Lists service is not provisioned for the specified scope.
Action: Provision the Lists service for the specified scope.

Level: 1

Type: ERROR

Impact: Other

WCS-14023: The value is the wrong data type. The data type expected is {0}.
Cause: The value is the wrong data type.
Action: Use the value with the correct data type.

Level: 1

Type: ERROR

Impact: Other

WCS-14024: The WebCenter repository is not available.
Cause: An error occurred accessing the repository.
Action: Contact your system administrator. Check the log for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-14025: An error occurred accessing the WebCenter metadata repository.
Cause: An error occurred accessing the repository.
Action: Contact your system administrator. Check the log for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-14026: List column values were converted or deleted based on list column changes during import: scope={0}, list={1}, column={2}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-14027: List are not enabled for this portal or a parent portal.
Cause: Lists are not enabled in this portal.
Action: Enable lists if required by this portal.

Level: 1

Type: WARNING

Impact: Other

WCS-14028: Enabling lists failed.
Cause: An error occurred enabling lists.
Action: Contact your system administrator. Check the log for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-14029: Lists not enabled for portal {0}.
Cause: Lists not enabled for the specified portal.
Action: Enable lists for the specified portal.

Level: 1

Type: ERROR

Impact: Other

WCS-14501: The list was not found.
Cause: The list could not be found.
Action: Remove the list view for the invalid list from the page.

Level: 1

Type: ERROR

Impact: Other

WCS-14502: Another user deleted the row while you modified it. Discard any unsaved changes, then refresh the list.
Cause: Another user deleted the row while you modified it.
Action: Discard any unsaved changes, then refresh the list.

Level: 1

Type: ERROR

Impact: Other

WCS-14503: Another user modified a row while you modified it. Discard any unsaved changes, then refresh the list.
Cause: Another user modified a row while you modified it.
Action: Discard any unsaved changes, then refresh the list.

Level: 1

Type: ERROR

Impact: Other

WCS-14504: Another user deleted the list after you displayed it. Discard any unsaved changes, then refresh the list.
Cause: Another user deleted the list after you displayed it.
Action: Discard any unsaved changes, then refresh the list.

Level: 1

Type: ERROR

Impact: Other

WCS-14505: Another user modified this list after you displayed it. Discard any unsaved changes, then refresh the list.
Cause: Another user modified this list after you displayed it.
Action: Discard any unsaved changes, then refresh the list.

Level: 1

Type: ERROR

Impact: Other

WCS-14506: Invalid minimum/maximum range
Cause: Minimum value must be less than or equal to maximum value.
Action: Modify the minimum value or maximum value.

Level: 1

Type: ERROR

Impact: Other

WCS-14507: Default value is out of range
Cause: Default value must be between the minimum and maximum values.
Action: Modify the default value, minimum value, or maximum value.

Level: 1

Type: ERROR

Impact: Other

WCS-14508: An error occurred accessing the WebCenter repository.
Cause: An error occurred accessing the repository.
Action: Contact your system administrator. Check the log for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-14509: Your permission to perform this operation was revoked. Refresh the list and discard unsaved changes.
Cause: Your permission to perform this operation was revoked.
Action: Request permission to perform this operation.

Level: 1

Type: ERROR

Impact: Other

WCS-14510: The Lists service was disabled, preventing you from performing this operation. Refresh the list and discard unsaved changes.
Cause: The Lists service was disabled, preventing you from performing this operation.
Action: Enable the Lists service.

Level: 1

Type: ERROR

Impact: Other

WCS-14514: An unexpected error occurred. Please retry the operation.
Cause: An unexpected error occurred.
Action: Retry the operation. If the problem persists, contact your administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-14515: Default value is too long
Cause: Default value must not exceed the maximum length.
Action: Modify the default value or maximum length.

Level: 1

Type: ERROR

Impact: Other

WCS-14516: The WebCenter metadata repository was temporarily unavailable. Please retry the operation.
Cause: The connection to the WebCenter metadata repository failed.
Action: Retry the operation. If the problem persists, contact your administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-14517: Another user deleted the list after you displayed it. Discard any unsaved changes, then click Close to exit list edit mode.
Cause: Another user deleted the list after you displayed it.
Action: Discard any unsaved changes, then click Close to exit list edit mode.

Level: 1

Type: ERROR

Impact: Other

WCS-14518: Another user deleted the list. Click Close to exit list edit mode.
Cause: Another user deleted the list.
Action: Click Close to exit list edit mode.

Level: 1

Type: ERROR

Impact: Other

WCS-14519: The list row was not found.
Cause: The list row could not be found.
Action: None.

Level: 1

Type: ERROR

Impact: Other

WCS-14522: Lists are disabled, preventing you from performing this operation. Enable lists to continue making changes.
Cause: Lists are disabled, preventing you from performing this operation.
Action: Enable lists.

Level: 1

Type: ERROR

Impact: Other

WCS-16005: An unexpected error occurred
Cause: ADFContext is null
Action: Contact Oracle Support Services for assistance.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16007: An unexpected error occurred
Cause: An error occurred while saving custom panel data
Action: Contact Oracle Support Services for assistance.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16008: An unexpected error occurred
Cause: An error occurred while saving event wiring data
Action: Contact Oracle Support Services for assistance.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16009: Error saving EL
Cause: An error occurred while saving an EL '{0}'
Action: Ensure that the EL is valid

Level: 1

Type: ERROR

Impact: Other

WCS-16010: An error occured while obtaining the list of persistence handlers
Cause: Cannot find a persistence handler by name {0}
Action: Ensure that persistence handler is correctly registered in pe_ext.xml

Level: 1

Type: ERROR

Impact: Other

WCS-16011: An unexpected error occurred
Cause: Managed bean {0} does not implement {1}
Action: Correct the implementation of {0}

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16012: An unexpected error occurred
Cause: Circular reference detected for parameter {0}
Action: Correct the circular referencing of parameters and retry

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16013: Parameter list is null
Cause: Parameter list is null
Action: Contact Oracle Support Services for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-16014: Page Definition not found
Cause: Page Definition not found
Action: Contact Oracle Support Services for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-16015: Could not get design time binding container
Cause: Could not get design time binding container
Action: Contact Oracle Support Services for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-16016: Composer configured incorrectly
Cause: The task flow binding required for Composer to function correctly may be missing from the pages definition file.
Action: Ensure that the pages definition file has a task flow binding with id set to "pageeditorpanel" and taskFlowId set to "#{pageEditorBean.pageEditorPanel}".

Level: 1

Type: ERROR

Impact: Other

WCS-16026: error downloading file {0}
Cause: An error occurred while downloading file {0}.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16027: error downloading all customizations
Cause: An error occurred while downloading all customizations.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16028: error uploading file {0}
Cause: An error occurred while uploading file {0}.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16029: error uploading file {0}
Cause: File {0} was not well formed. syntax error {1} occurred at line {2} column {3}
Action: Correct the XML syntax and upload the file again.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16030: error deleting file {0}
Cause: An error occurred while deleting file {0}.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16031: error promoting file {0} from label {1}
Cause: An error occurred while promoting file {0} from label {1}.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16076: Deleting tip layer customizations failed for {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16116: An unexpected error occurred. The structure navigator is not initialized
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-16117: An error occurred executing phase listener - {0}
Cause: An error occurred executing phase listener - {0}
Action: Contact Oracle Support Services for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-16118: An error occurred while deleting {0}
Cause: An error occurred while persisting component deletion to datastore
Action: Contact Oracle Support Services for assistance.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16130: Error occurred while re-ordering components.
Cause: An error occurred while re-ordering components. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-16197: Error encountered while dispatching an Composer event. Composer will continue with the next event handler.
Cause: An error occurred while dispatching ''{0}'' event in the event handler ''{1}''.
Action: Resolve the error caused by the event handler or contact Oracle Support Services for assistance.

Level: 1

Type: WARNING

Impact: Other

WCS-16232: Exception while identifying dragged resource
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16234: getItemBinding is null
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16276: You do not have permission to edit the page
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16277: Destroying Sandbox because you do not have permission to edit the page
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16278: An exception occurred while creating the permission class - {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16279: Failed to get flag pageSecurityMetadata from security context
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16301: A facet named {0} declared by the toolbarLayout attribute was not found in page {1}.
Cause: Failed to retrieve a facet definition corresponding to the declaration provided in the pageCustomizable's toolbarLayout attribute
Action: Verify all facets declared in toolbarLayout have a definition

Level: 1

Type: ERROR

Impact: Other

WCS-16302: Error in key sequence "{0}" configured for "{1}".
Cause: Key sequence configured in adf-config.xml has errors.
Action: Verify the key sequence configured in adf-config.xml.

Level: 1

Type: ERROR

Impact: Other

WCS-16303: Unexpected error occurred invoking method expression {0}.
Cause: Method expression configured for mode-switch-handler in adf-config.xml has errors.
Action: Verify the mode-switch-handler configured in adf-config.xml.

Level: 1

Type: WARNING

Impact: Other

WCS-16351: Could not update the resource bundle entry for the key {0} Where {0} points to the key of the resource
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16352: Could not add the resource bundle entry {0} Where {0} points to the key of the new resource
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16353: Could not find override resource bundle
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16354: No content is found for a metadata object
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16355: Could not find resource entry for {0}
Cause: An error occurred while finding resource entry for {0}, The resource entry does not exist in the override bundle. It could also have been deleted.
Action: Ensure that the resource key entry is correctly spelt. Recreate the resource entry if it has been deleted.

Level: 1

Type: WARNING

Impact: Other

WCS-16407: An error occurred while destroying the sandbox
Cause: An error occurred while destroying the sandbox - {0}
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16408: Unable to create Application Session Options Factory {0}
Cause: An error occurred while creating Application Session Options Factory {0}
Action: Verify configuration of Application Session Options Factory {0}

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16409: Unable to create Sandbox {0} for Page {1}
Cause: An error occurred while creating Sandbox {0} for Page {1}
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16410: Error retrieving Metadata Object for page: {0}
Cause: An error occurred while retrieving the Metadata Object
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16676: Not nested in ADF Faces tag: {0}
Cause: The Behavior tag is not nested inside an ADF Faces tag.
Action: Enclose the Behavior tag inside an ADF Faces tag.

Level: 1

Type: ERROR

Impact: Other

WCS-16677: Parent UIComponent instance is null.
Cause: Parent UIComponent is not created.
Action: Enclose the Behavior tag inside a UIComponent tag.

Level: 1

Type: ERROR

Impact: Other

WCS-16678: Component: {0} does not support client listeners.
Cause: Parent component enclosing the Behavior tag does not support client listeners.
Action: Enclose the Behavior tag inside an ADF Faces tag that supports client listeners. Check if the Behavior tag is enclosed within a ADF command component.

Level: 1

Type: ERROR

Impact: Other

WCS-16679: Component: {0} does not support client attributes.
Cause: Parent component enclosing the behavior tag does not support client attributes.
Action: Enclose the Behavior tag inside an ADF Faces tag that supports client attributes.

Level: 1

Type: ERROR

Impact: Other

WCS-16702: Unable to get Region Parameters.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16705: Auto wiring for task flow with id: {0} failed with message {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16706: Parameter {0} of task-flow {1} has not been wired with any event
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16728: Unable to parse markup: {0}
Cause: An error occurred parsing the markup
Action: Please check if the markup is well formed

Level: 1

Type: WARNING

Impact: Other

WCS-16729: I/O Exception occurred while parsing the markup: {0}
Cause: An I/O error occurred parsing the markup
Action: Please take corrective action given by the exception stack trace.

Level: 1

Type: WARNING

Impact: Other

WCS-16754: An error occurred while performing move action
Cause: Error occurred while persisting the changes to datastore
Action: Check whether the persistence configuration is defined correctly and whether the document being customized specifies id's for all elements enclosed within pageCustomizable

Level: 1

Type: WARNING

Impact: Other

WCS-16756: Error retrieving Metadata Object for page: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16757: Error creating permission class: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16759: An error occurred while performing move action
Cause: An error occurred while re-ordering components. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-16851: Error cloning portlet {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16852: Unable to generate portlet events inside portlet binding
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16853: Problems when generating portlet parameters in the binding
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16854: Unable to generate variableIterator in the page definition
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16855: Error getting portlet instance
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16856: Unable to retrieve portlet parameters.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16857: Error updating page definition
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16858: Null page definition
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16862: Page Definition not found for the page: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16912: The built-in extension file {0} is not found, or an error has occurred while reading the built-in extension file.
Cause: Could not find the built-in extension file or error reading it.
Action: The Composer component may have been damaged or is inaccessible to the application. Ensure that the Composer JAR file is not damaged and is accessible to the application.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-16937: Error adding a custom property panel
Cause: An error occurred adding a custom panel {0} for component of type {1}.
Action: Ensure that the expression {0} associated with "isRendered" attribute of the custom panel usage executes without errors.

Level: 1

Type: WARNING

Impact: Other

WCS-16948: Error adding {0} entry. The entry {1} of {2} specified in {3} cannot be null; therefore, ignoring this entry.
Cause: The {0} entry {1} of {2} specified in {3} was not defined.
Action: Ensure that {0} entry {1} of {2} is defined in {3} and there are no typing errors.

Level: 1

Type: WARNING

Impact: Other

WCS-16951: An error has occurred while creating the security policy {0}.
Cause: An error occurred while creating the security policy {0}.
Action: Ensure that the class {0} is in the classpath and has inherited the security policy specified by oracle.adf.view.page.editor.security.SecurityPolicy.

Level: 1

Type: WARNING

Impact: Other

WCS-16952: Cannot create the component security policy provider because the component value is null.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16953: Cannot create the page security policy provider because the path of the page is null.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-16954: An error has occurred while finding the component with client ID {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-18001: An unexpected error occurred.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18002: Missing Configuration for List of Contacts. Could not locate the class {0}.
Cause: An incorrect class name was provided.
Action: Please contact Oracle Support.

Level: 1

Type: ERROR

Impact: Other

WCS-18003: Class {0} does not implement the interface {1}.
Cause: The specified class had not implemented the required interface.
Action: Ensure that the class implements the required interface.

Level: 1

Type: ERROR

Impact: Other

WCS-18004: Cannot instantiate class {0}.
Cause: The specified class did not have a default constructor accessible to public.
Action: Ensure that the class has a default constructor and it is accessible to public.

Level: 1

Type: ERROR

Impact: Other

WCS-18005: Cannot instantiate class {0}.
Cause: Either the specified class was not a concrete implementation or it did not have a default constructor accessible to public.
Action: Ensure that the class is a concrete implementation and has a default constructor accessible to public.

Level: 1

Type: ERROR

Impact: Other

WCS-18006: The implementation class {0} returned null.
Cause: The implementation class returned a null object.
Action: Ensure that the implementation class returns a non-null list of contacts.

Level: 1

Type: WARNING

Impact: Other

WCS-18007: An error occurred while trying to validate metadata.
Cause: Invalid metadata has been introduced.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18008: Unable to save the metadata in persistence store
Cause: An error occurred while writing to persistence store or metadata was locked by another user.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18009: Cannot apply the current metadata changes to a concurrently modified metadata.
Cause: Recent changes in this session conflicts with changes made in the same session.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18010: Cannot locate the requested metadata.
Cause: The metadata was not found in the configured metadata stores or it had been deleted on this session.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18011: Cannot obtain the metadata for write operations.
Cause: The metadata store could be spanning multiple back-end stores or concurrent updates were attempted.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18012: Metadata already exists in metadata store.
Cause: An attempt was made to create a metadata document when it already exists.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18013: The reference to the specified metadata is invalid.
Cause: The reference to the metadata was incorrect.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18014: Could not be complete the sort operation.
Cause: A null table component was returned.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18015: Could not get contact details.
Cause: The selected contact details were unavailable due to an internal error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18016: Could not launch the dialog for view {0}.
Cause: Profile page details are unavailable due to an internal error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18017: Could not perform a people search.
Cause: Instance of identity store is not available.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18018: Could not get display name from user profile.
Cause: User did not have the display name or user's profile was not accessible.
Action: Contact the administrator of directory services/webcenter.

Level: 1

Type: WARNING

Impact: Other

WCS-18019: Could not get name from user profile.
Cause: User does not have the name or user's profile is not accessible.
Action: Please contact the administrator of directory services/webcenter.

Level: 1

Type: WARNING

Impact: Other

WCS-18020: Could not save the search criterion.
Cause: An internal error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18021: Could not fetch the search criterion.
Cause: An internal error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18022: Could not fetch the sort criteria.
Cause: An internal error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18023: Could not save the sort criteria.
Cause: An internal error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18024: Cannot get an instance of the identity store
Cause: There was either an improper configuration or an internal error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18025: Could not create the contacts list.
Cause: An internal error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18026: Could not perform a people search.
Cause: An internal error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18401: An unexpected error occurred in the Message Board sub-system.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18402: Failed to create an instance of Message Board
Cause: Message Board viewing user name not found
Action: Make sure that the user is logged in

Level: 1

Type: ERROR

Impact: Other

WCS-18403: Failed to create an instance of Message Board
Cause: Message Board owner user name not specified
Action: Provide owner user name in the request for an instance of Message Board

Level: 1

Type: ERROR

Impact: Other

WCS-18405: Failed to publish Message Board activity
Cause: Activity Stream service raised an exception
Action: Verify the reason for the failure in the Activity Stream sub-system

Level: 1

Type: ERROR

Impact: Other

WCS-18406: Message Board message cannot be deleted
Cause: User is not authorized to delete this message
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18407: Failed to delete Message Board message
Cause: Message does not exist
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18408: Message Board message cannot be updated
Cause: User is not authorized to update this message
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18409: Failed to update Message Board message
Cause: Message does not exist
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18410: Message Board message cannot be added
Cause: Message content is empty
Action: Provide a non empty message board message text

Level: 1

Type: ERROR

Impact: Other

WCS-18411: Message Board message cannot be hidden
Cause: User is not authorized to hide message
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18412: Failed to hide Message Board message
Cause: Message does not exist
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18413: Failed to retrieve user display name from profile service
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-18414: Failed to add message to Message Board.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18415: Failed to hide or unhide message in Message Board.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18416: Failed to delete message in Message Board.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18417: Failed to query messages in Message Board.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18418: Failed to update message in Message Board.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18419: Failed to create an instance of Message Board.
Cause: Message Board preferences manager not specified
Action: Provide preferences manager in the request for Message Board

Level: 1

Type: ERROR

Impact: Other

WCS-18420: Failed to query preferences for Message Board.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18421: Message cannot be added to Message Board.
Cause: User is not authorized to add message
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18422: Failed to retrieve Message Board message
Cause: Message does not exist
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18423: Failed to find the portal of the message board.
Cause: The portal doesn't exist.
Action: Contact your administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-18424: Failed to find the user of the message board.
Cause: The user doesn't exist.
Action: Contact your administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-18425: Failed to attach file to selected portal.
Cause: The portal does not exist or does not have document services configured.
Action: Contact your administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-18451: Unexpected error getting preference.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18452: Unexpected error saving preference.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18453: Encountered exception: {0}. For diagnosis, turn on the logging level to FINEST and retry the operation. Details about the current state: {1}.
Cause: An unexpected error occurred.
Action: To diagnose the error, turn on the logging level to FINEST and retry the operation.

Level: 1

Type: WARNING

Impact: Other

WCS-18501: Error retrieving {0}''s Profile
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18502: User: {0} not found in identity store.
Cause: An unexpected error occurred.
Action: Check if the specified user exists in the configured identity store and contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18503: Personal status note can be changed only for the current user
Cause: attempt made by an user to update personal status of another user
Action: login as the user whose status you want to change

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18504: unexpected error operating on personal status note
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18506: User does not have the privilege required to access the user profile.
Cause: Either the system policy or the target user's access control settings restrict the current user from performing this operation.
Action: Contact the Administrator to grant the required permission, or contact the target user to allow access.

Level: 1

Type: ERROR

Impact: Other

WCS-18507: Insufficient Privilege.
Cause: Cannot Edit Profile.
Action: Contact Webcenter Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-18508: Unexpected error retrieving user {0}''s photo
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18509: Unexpected error saving user {0}''s photo to the back-end. The photo may not have been saved. Please refresh to find out and then retry the operation.
Cause: An unexpected error occurred.
Action: The photo may not have been saved. Please refresh to find out and then retry the operation. If the issue persists contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18510: Unexpected error invalidating user {0}''s photo cache
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18511: User not specified
Cause: The supplied username was null or blank.
Action: Specify a valid username that is not null or blank.

Level: 1

Type: ERROR

Impact: Other

WCS-18514: Unexpected error saving the Profile Admin Settings
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18515: Unexpected error saving the Profile user preference
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18516: Unexpected error initializing the admin config bean
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18517: Unexpected error saving the profile
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18520: Unexpected error retrieving unique identifier for user {0}''s photo
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18521: Unexpected error evaluating property ''{0}'' of base {1}
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18522: Modifying property ''{0}'' of base {1} not allowed
Cause: The application does not allow modifying the value of the specified property of the specified base object.
Action: Ensure that property of the object being modified is not read-only.

Level: 1

Type: ERROR

Impact: Other

WCS-18523: Error getting the instant message address for the person
Cause: unexpected error getting the sip address
Action: contact the administrator

Level: 1

Type: ERROR

Impact: Other

WCS-18524: Error getting tag data
Cause: unexpected error getting tag data
Action: contact the administrator

Level: 1

Type: ERROR

Impact: Other

WCS-18525: Unexpected error saving attribute: {0}
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services with the error on the log.

Level: 1

Type: ERROR

Impact: Other

WCS-18526: User does not have the privilege required for updating the user profile
Cause: The system policy restricts the current user from updating the user profile.
Action: Contact the Administrator to obtain the required permission.

Level: 1

Type: ERROR

Impact: Other

WCS-18527: The image file {0} you tried to upload was invalid. Provide a valid image file.
Cause: Unable to upload the image as the file is null or invalid.
Action: Upload a valid image file

Level: 1

Type: ERROR

Impact: Other

WCS-18528: Unexpected error instantiating object.
Cause: Unexpected error instantiating object.
Action: contact the administrator

Level: 1

Type: ERROR

Impact: Other

WCS-18529: Error instantiating profile (user name: {0}, GUID: {1})
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18530: Unable to retrieve display name for profile (user name: {0}, GUID: {1}) in locale {2}. For diagnosis, turn on the logging level to FINEST and retry the operation. Error summary: {3}.
Cause: An unexpected error occurred.
Action: To diagnose the error, turn on the logging level to FINEST and retry the operation.

Level: 1

Type: WARNING

Impact: Other

WCS-18531: Error navigating the hierarchy
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18532: Unexpected error writing vcard
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18533: Unexpected error retrieving reporting chain
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18534: Unexpected error searching user profiles
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18535: User: {0} not found in identity store or user does not have the required privilege for updating the user profile.
Cause: Either user is not available in the user repository or system policy restriction is applied.
Action: contact the administrator

Level: 1

Type: ERROR

Impact: Other

WCS-18536: User Class type not expected, found: {0} expected{1}.
Cause: The User instance found in the cache is not of the expected Class type.
Action: Check if the Profile Service Lifecycle Listener is executed which sets the appropriate UserFactory.

Level: 1

Type: ERROR

Impact: Other

WCS-18537: Error updating {0} with {1} and {2}.
Cause: The cause of this error could be MetadataNotFoundException, UnsupportedUpdateException, MDSIOException, ConcurrentMOChangeException or ValidationException
Action: Check if the pages.xml is present, you have update permission on the document or if the pages.xml has some invalid content. If all the things listed are fine then try again after sometime.

Level: 1

Type: ERROR

Impact: Other

WCS-18538: An unknown error occurred while trying to determine security attributes of type {0}
Cause: Review the logs for the underlying exception
Action: Take action based on the underlying exception. Rerun the crawl.

Level: 1

Type: WARNING

Impact: Other

WCS-18539: An unknown error occurred while trying to determine security attributes of type {0} for user {1}
Cause: Review the logs for the underlying exception
Action: Take action based on the underlying exception. Rerun the crawl.

Level: 1

Type: WARNING

Impact: Other

WCS-18540: Unknown error accessing assets
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18541: Action {0} cannot be executed on asset type {1}
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18542: You do not have privileges to perform {0} on {1}.
Cause: The user does not have permission to perform the action on the given asset or asset type.
Action: Contact your administrator to give you privileges to perform the required action.

Level: 1

Type: WARNING

Impact: Other

WCS-18543: Unknown error while determining if user can access asset manager in scope {0}.
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-18544: Unknown error while determining if user can access {0} asset type in asset manager in scope {1}.
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-18545: Unknown error while deleting assets permission for scope {0}.
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-18546: Selected operation cannot be performed as the asset is already deleted, refresh the list using the refresh icon.
Cause: The asset on which the action is being performed does not exist.
Action: Refresh the list using the Refresh icon.

Level: 1

Type: ERROR

Impact: Security

WCS-18547: Unknown error while trying to delete a resource for scope {0}, resourceType {1}, resourceGUID {2} and backURL {3}.
Cause: An unexpected error occurred while trying to delete a resource.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: ERROR

Impact: Other

WCS-18548: Unknown error while trying to toggle the visibility of a resource for scope {0}, resourceType {1} and resourceGUID {2}
Cause: An unexpected error occurred while trying to toggle the visibility of a resource.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: ERROR

Impact: Other

WCS-18549: Unknown error while trying to get resources.
Cause: An unexpected error occurred while trying to get the resources from the resource query options.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: ERROR

Impact: Other

WCS-18701: An unexpected error occurred in the Feedback sub-system.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18702: Failed to create an instance of Feedback
Cause: Feedback object's viewing user name not found
Action: Make sure that the user is logged in

Level: 1

Type: ERROR

Impact: Other

WCS-18703: Failed to create an instance of Feedback
Cause: Feedback object's user name not specified
Action: Provide user name in the request for an instance of Feedback

Level: 1

Type: ERROR

Impact: Other

WCS-18705: Failed to publish Feedback activity
Cause: Activity Stream service raised an exception
Action: Verify the reason for the failure in the Activity Stream sub-system

Level: 1

Type: ERROR

Impact: Other

WCS-18706: Feedback message cannot be deleted
Cause: User is not authorized to delete this message
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18707: Failed to delete Feedback message
Cause: Message does not exist
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18708: Feedback message cannot be updated
Cause: User is not authorized to update this message
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18709: Failed to update Feedback message
Cause: Message does not exist
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18710: Feedback message cannot be added
Cause: User is not authorized to add message
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18711: Feedback message cannot be hidden
Cause: User is not authorized to hide message
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18712: Failed to hide Feedback message
Cause: Message does not exist
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-18713: Feedback message cannot be added
Cause: Feedback message content is empty
Action: Provide a non empty feedback message text

Level: 1

Type: ERROR

Impact: Other

WCS-18714: Failed to retrieve user display name from profile service
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-18715: Failed to add feedback.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18716: Failed to hide or unhide feedback.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18717: Failed to delete feedback.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18718: Failed to query feedback messages.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18719: Failed to create an instance of Feedback
Cause: Feedback object's preferences manager not specified
Action: Provide preferences manager in the request for an instance of Feedback

Level: 1

Type: ERROR

Impact: Other

WCS-18720: Failed to query preferences for Feedback object.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-18751: Unknown error accessing portal assets
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18752: Unknown error in instantiating portal assets factory
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18753: Unexpected error occurred while adding a portal asset.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18754: Unexpected error occurred while deleting a portal asset
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18755: Unexpected error occurred while updating a portal asset
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18756: Unexpected error occurred while getting the list of portal assets
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18757: Portal asset for update is not valid
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18758: An attribute in this asset is not valid.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18759: An error occurred in setting up the asset
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18760: Copy operation resulted in error. If you see the asset in asset manager, delete it.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18761: Delete operation resulted in error. If you see the asset in asset manager, try deleting it again.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18762: You do not have the privileges required to perform this operation.
Cause: No privilege to do the current operation
Action: Contact webcenter administrator for change in role.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18763: Asset with the same display name already exists.
Cause: An unexpected error occurred.
Action: Enter a new display name for the asset.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18764: An unexpected error occurred while trying to check {0} access for {1}, denying access.
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-18765: Unable to import, as the asset being imported conflicts with another asset.
Cause: Another asset in the target has the metadata file or jspx with the same path as the asset being imported.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-18766: Unable to import as the asset being imported conflicts with another asset of a different type in the same portal.
Cause: Either the metadata file or jspx with the same path already exists on the target application in same scope.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-18767: Unable to validate the content of the archive. Import of asset is aborted.
Cause: Error while trying to check if a document exists in MDS.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-18768: Unable to import as {1}, as the asset in the archive is of type {0}
Cause: Select the correct asset type to import.
Action: Select the correct asset type to import.

Level: 1

Type: ERROR

Impact: Other

WCS-18769: Encountered exception while trying to determine if path {0} points to an asset, resorting to default security check.
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-18770: Asset with id "{0}" does not exist.
Cause: The asset was possibly deleted by another user.
Action: Refresh the asset manager to see if the asset still exists

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18771: Unable to export as the asset is type {0} but was invoked as {1}
Cause: Incorrect asset type
Action: Select the correct asset type to import.

Level: 1

Type: ERROR

Impact: Other

WCS-18772: Unable to upload as the asset belongs to {0} but is being uploaded into {1}
Cause: The asset you are trying to upload belongs to a different portal.
Action: Verify which portal owns the asset and then upload the asset to that portal.

Level: 1

Type: ERROR

Impact: Other

WCS-18773: Unable to upload the asset. The owner of the asset is not valid.
Cause: Cannot identify the owner of the asset.
Action: The archive is corrupt with invalid documents. Contact Oracle Support Services and provide log information.

Level: 1

Type: ERROR

Impact: Other

WCS-18774: Global asset of type "{2}", with ID "{0}" does not exist.
Cause: The specified asset was probably deleted by another user.
Action: Refresh the list of assets to see if the asset still exists.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18775: Asset of type "{2}", with ID "{0}" does not exist in the portal "{1}".
Cause: The specified asset was probably deleted by another user.
Action: Refresh the list of assets to see if the asset still exists.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18776: You do not have the permissions required to perform the operation. Verify that you have the appropriate Create/Edit/Delete permission for the type of shared asset you are attempting to upload/download.
Cause: Verify that you have the appropriate Create/Edit/Delete permission.
Action: Contact your WebCenter Portal administrator to request the required permissions.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18777: You do not have the permissions required to perform the operation. Verify that you have the appropriate Create/Edit/Delete permission for all portal assets or for the specific type of portal asset you are attempting to upload/download.
Cause: Verify that you have the appropriate Create/Edit/Delete asset permissions for the portal.
Action: Contact the portal administrator to request the required permissions.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18778: Unable to upload as the archive does not contain a shared asset.
Cause: The asset you are trying to upload belongs to a specific portal, it is not a shared asset.
Action: Verify which portal owns the asset and then upload the asset to that portal.

Level: 1

Type: ERROR

Impact: Other

WCS-18779: Unable to upload the asset as the archive does not contain an asset that belongs to this portal.
Cause: The asset you are trying to upload belongs to a different portal.
Action: Verify which portal owns the asset and then upload the asset to that portal.

Level: 1

Type: ERROR

Impact: Other

WCS-18780: Global asset of type "{2}", with name "{0}" does not exist.
Cause: The specified asset was probably deleted by another user.
Action: Refresh the list of assets to see if the asset still exists.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18781: Asset of type "{2}", with name "{0}" does not exist in the portal "{1}".
Cause: The specified asset was probably deleted by another user.
Action: Refresh the list of assets to see if the asset still exists.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18782: Name or Resource Id of the resource to be exported is not specified. Specify either the name or the Id of the resource.
Cause: Name or ID of the resource to be exported in not mentioned.
Action: Specify either the name or the ID of the resource.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18783: Name, Resource Id and type of the resource to be exported do not match.
Cause: Name, Resource Id and type of the resource to be exported do not match.
Action: Specify either the name or the ID of the resource.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18784: Asset is a system asset. You cannot export system assets.
Cause: The asset you are trying to export is a system asset.
Action: Refer to export documentation for more information or contact your administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-18785: Asset is a system asset. You cannot import system assets.
Cause: The asset you are trying to import is a system asset.
Action: Refer to import documentation for more information or contact your administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-18786: Global asset of type "{3}", with the name "{0}" already exists with a different guid "{2}".
Cause: An unexpected error occurred.
Action: Enter a new display name for the global asset.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18787: Asset of type "{3}", with the name "{0}" already exists in the portal "{1}" with a different guid "{2}".
Cause: An unexpected error occurred.
Action: Enter a new display name for the asset.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18788: Asset of type "{1}", with id "{0}" is a system asset. You cannot export system assets.
Cause: The asset you are trying to export is a system asset.
Action: Refer to export documentation for more information or contact your administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-18789: Asset of type "{1}", with name "{0}" is a system asset. You cannot export system assets.
Cause: The asset you are trying to export is a system asset.
Action: Refer to export documentation for more information or contact your administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-18790: Portal asset for copy is not valid
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services with logs.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18791: The asset archive specified is not a valid asset archive.
Cause: The asset archive specified is not a valid asset archive.
Action: Verify the asset archive and provide a valid archive.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18792: An exception occurred while exporting the data for the asset named "{0}" of type {1}.
Cause: An exception occurred while exporting the persistence data for the asset.
Action: Verify the asset data in the persistence store and retry the operation.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18793: An exception occurred while importing the data for the asset named "{0}" of type {1}.
Cause: An exception occurred while importing the persistence data for the asset.
Action: Verify the asset data in the persistence store and retry the operation.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18794: Error occurred while trying to find resource with id {0} and type {1}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-18801: Access Policy for component "{0}" could not be saved.
Cause: There was an error in saving access policy.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18802: Access Policy for component "{0}" defined by {1} could not be read.
Cause: There was an error in reading access policies of the component.
Action: Verify in 'Display Options' tab that the el expression in 'Show Component' property is not malformed

Level: 1

Type: WARNING

Impact: Other

WCS-18803: Attribute "{0}" could not be read for component "{1}"
Cause: There was an error in reading an attribute of the component.
Action: Verify in 'Display Options' tab that the el expression in 'Show Component' property is not malformed

Level: 1

Type: WARNING

Impact: Other

WCS-18804: Attribute "rendered" of component "{0}" having EL expression "{1}" could not be parsed.
Cause: There was an error in parsing EL Expression of attribute "rendered"
Action: Verify in 'Display Options' tab that the el expression in 'Show Component' property is not malformed

Level: 1

Type: WARNING

Impact: Other

WCS-18805: Attributes of component "{0}" has not been modified.
Cause: Attributes of selected component has not been modified.
Action: Message is informational only

Level: 1

Type: WARNING

Impact: Other

WCS-19001: Unexpected error occurred
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19002: Unable to execute operation on {0}
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19003: Metadata file {0} not found
Cause: The expected metadata file was not found
Action: Contact Oracle Support Services

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19004: Unexpected error occurred while creating page table
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19005: Internal error while creating policy store metadata for {0}
Cause: Policy store for WebCenter Portal not found
Action: Contact Oracle Support Services

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19007: Unable to copy application or portal policies for {0}
Cause: Exception occurred while copying policies for WebCenter Portal.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19008: No matching users were found with search string {0}
Cause: No users matched the search string you entered: {0}
Action: Enter a new search term and try again

Level: 1

Type: ERROR

Impact: Other

WCS-19010: Couldn''t retrieve metadata for role {0}
Cause: No roles matched the search string you entered: {0}
Action: Enter a new search term and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19013: User not specified
Cause: A null or empty string was provided for the user name.
Action: Enter a valid user name.

Level: 1

Type: ERROR

Impact: Other

WCS-19014: Role not specified
Cause: A null or empty string was provided for the role name.
Action: Enter a valid role name.

Level: 1

Type: ERROR

Impact: Other

WCS-19016: Unable to grant user {2} with role {1} in {0}
Cause: An attempt to grant a user role failed. Either, role {1} does not exist, user {0} does not exist, or the user is already granted the role
Action: Determine the cause and, if necessary, try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19017: Unable to revoke role {1} from identity {0}
Cause: An attempt to grant a identity role failed. Either, role {1} does not exist,identity {0} does not exist, or the identity does not have the specified role.
Action: Determine the cause and, if necessary, try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19018: Unable to add role {0} to the policy store
Cause: An attempt to create a new role failed. Either the role already exists, or the policy store is currently unavailable
Action: Determine the cause and, if necessary, try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19019: An error occurred while trying to remove role {0} from the policy store
Cause: An attempt to delete the specified role failed. Either the role does not exist, or the policy store is currently unavailable.
Action: Determine the cause and, if necessary, try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19020: Identity {0} has already been granted the role(s).
Cause: User has been already granted the same role.
Action: Determine the cause and, if necessary, try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19022: Role {0} already exists in the policy store
Cause: An attempt to create a new role failed because the policy store contains a role with the name specified.
Action: Enter a unique name for the role.

Level: 1

Type: ERROR

Impact: Other

WCS-19025: Only authenticated users can perform the requested operation
Cause: You do not have sufficient privileges to perform the requested operations.
Action: Ask your WebCenter Portal administrator to grant you the appropriate privileges and then try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19026: Unable to revoke permission {0}
Cause: The specified permission was not removed from the policy store. The permission may not exist
Action: Check whether the permission exists in the policy store

Level: 1

Type: ERROR

Impact: Other

WCS-19027: Unable to grant permission {0}
Cause: The user was not granted the specified permission. The user may already be assigned that permission.
Action: Check whether the user is assigned this permission.

Level: 1

Type: ERROR

Impact: Other

WCS-19029: Policy for WebCenter Portal could not be found
Cause: Policy for WebCenter Portal was missing from the policy store.
Action: Check the policy store for WebCenter Portal is configured correctly.

Level: 1

Type: ERROR

Impact: Other

WCS-19030: Page definition for page {0} not found
Cause: Page definition for page {0} does not exist.
Action: Check whether the page definition for page {0} exists

Level: 1

Type: ERROR

Impact: Other

WCS-19031: Policy store instance cannot be null
Cause: No policy store instance was found
Action: Verify and instantiate the policy store instance and try the operation again.

Level: 1

Type: ERROR

Impact: Other

WCS-19032: Security Manager already initialized
Cause: An attempt was made to initialize the Security Manager but it was already initialized.
Action: Use the existing Security Manager.

Level: 1

Type: ERROR

Impact: Other

WCS-19033: Security Manager is not initialized
Cause: A security operation was attempted before the Security Manager was initialized.
Action: Initialize the Security Manager and try again

Level: 1

Type: ERROR

Impact: Other

WCS-19034: WebCenterSecurityManager class cannot be initialized directly
Cause: An attempt was made to initialize the WebCenterSecurityManager class through a protected constructor.
Action: Initialize the WebCenterSecurityManager class with a default constructor.

Level: 1

Type: ERROR

Impact: Other

WCS-19035: Security Manager is null
Cause: Security Manager could not be initialized
Action: Use valid parameters and try again.

Level: 1

Type: WARNING

Impact: Other

WCS-19036: Scoped Security Manager is null for scope {0}
Cause: Security manager can not be initialized
Action: Please try to initialize again with proper parameters

Level: 1

Type: WARNING

Impact: Other

WCS-19037: Invalid context {1} for scope {0}
Cause: Current scope did not match the cached scope
Action: Refresh your page again and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19038: An error occurred while importing security policies.
Cause: Failed to create security policies (grants, roles and permissions) during import.
Action: Verify that the export archive is valid, otherwise check logs for error details and contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19039: ADFContext is NULL, so returning NULL as username
Cause: An internal error occurred while fetching the user name.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19040: SecurityContext is NULL, so returning NULL as username
Cause: SecurityContext was not found for the current session
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19042: Unable to retrieve Personal Sidebar items
Cause: An error locating for opening the JSPX document for the Personal Sidebar
Action: Ensure that the JSPX document pointing to the Personal Sidebar is available to the application

Level: 1

Type: ERROR

Impact: Other

WCS-19043: Unable to persist personalization for tag with webcenterId ''{0}'' in the Personal Sidebar
Cause: An error saving the personalization document for the Personal Sidebar JSPX, or the tag with this webcenterId could not be located.
Action: Ensure that the personalization is enabled on the Personal Sidebar JSPX, and the tag has a unique webcenterId

Level: 1

Type: ERROR

Impact: Other

WCS-19044: Unable to retrieve item called {0} from the shell in the request {1}
Cause: Either the item name is incorrect or the item is not available in the current shell context
Action: Verify that the item name is correct and that the shell context is setup properly for the current request.

Level: 1

Type: WARNING

Impact: Other

WCS-19045: Unable to register shell handler of type {0}
Cause: Either the class name of the shell handler is incorrect or there was a problem while instantiating the shell handler
Action: Verify whether the shell handler type is correct or determine why the shell handler is not instantiating properly

Level: 1

Type: WARNING

Impact: Other

WCS-19046: Unable to retrieve the visibility of shell panel {0}
Cause: An error occurred trying to retrieve the visibility information from the shell handler of the current request.
Action: Defaulting visibility to 'true'

Level: 1

Type: WARNING

Impact: Other

WCS-19048: Unable to retrieve panel metadata for panel properties (panel name: {0})
Cause: The metadata for the panel in the shell metadata document may be corrupted or missing, or the name of the panel is incorrect.
Action: Verify whether the panel name is correct and whether the metadata for the panel is valid

Level: 1

Type: ERROR

Impact: Other

WCS-19049: An attempt to set change the skin was ignored
Cause: An attempt was made to change the skin but this feature is not yet implemented.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-19051: An attempt was made to set the template and ignored
Cause: This change would not take place as the feature is not implemented
Action: Please contact Oracle Support for more details

Level: 1

Type: WARNING

Impact: Other

WCS-19054: Error retrieving a physical page view-id for the request {0} (context URL {1})
Cause: The request URL could be invalid, or an unknown problem occurred fetching the metadata
Action: Verify the request URL and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19055: Unable to display a page for the requested URL {0}
Cause: The request URL was invalid, either because there was no shell handler or the shell handler could not provide a physical page to forward to.
Action: Verify the request URL and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19058: Unable to retrieve scope IDs for the current user
Cause: An internal error occurred while fetching the scope for the current user.
Action: Contact Oracle Support Services

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19061: Unable to INSTANTIATE shell handler factory of type {0}
Cause: Shell handler factory of type {0} was not in the classpath.
Action: Contact Oracle Support Services

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19062: Unable to INITIALIZE the shell handler factory
Cause: An internal error occurred while initializing the shell handler factory.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19066: Unable to set up the default shell handler factory.
Cause: An internal error occurred while setting up the default shell handler factory.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19067: Unable to navigate to the page. Page creation might have failed or an error occurred while attempting to load the new page. Open your Manage Pages dialog box to see if the page exists. If the problem persists, contact your administrator.
Cause: An error occurred trying to reference the newly created page (the page may not have been created properly).
Action: Try to selecting the new page from the pages dropdown list. If the page is not listed, try creating the page again

Level: 1

Type: ERROR

Impact: Other

WCS-19068: Unable to create page in the current scope
Cause: An unexpected error occurred while trying to create a page in a scope.
Action: Ask your WebCenter Portal administrator to resolve the issue.

Level: 1

Type: ERROR

Impact: Other

WCS-19070: Unable to delete page {0} ({1})
Cause: An attempt to delete a page failed. Either the page and/or its associated files (for example, ADFm page definition) have been modified but not saved
Action: Verify that the page is not being modified and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19071: Page {0} ({1}) not deleted properly. Unable to remove associated metadata.
Cause: An attempt was made to delete a page when metadata associated with the page was in use.
Action: Try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19072: Unable to retrieve the list of users
Cause: An attempt to retrieve the user list failed.Either the Identity store was corrupt or is inaccessible.
Action: Verify that the identity store is valid and accessible, and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19073: Unable to register page {0} (of scope {1}) for navigation
Cause: An error occurred while registering the page {0}.
Action: Try to register the page again and if unsuccessful contact Oracle Support.

Level: 1

Type: WARNING

Impact: Other

WCS-19075: No users available
Cause: No users found in the identity store associated with WebCenter Portal.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-19077: Permission class {0} does not have proper constructor method
Cause: The specified class does not have the required constructor
Action: Provide the required constructor in the specified class

Level: 1

Type: ERROR

Impact: Other

WCS-19079: Unable to process the security extension metadata
Cause: The argument is not an instance of ExtensionPermissionMetadata
Action: Provide an instance of ExtensionPermissionMetadata as the argument

Level: 1

Type: ERROR

Impact: Other

WCS-19080: Unable to access permission class {0} in your project libraries
Cause: Either the specified permission class does not exist or it is not in the correct location.
Action: Ensure that the specified permission class is in the correct location.

Level: 1

Type: ERROR

Impact: Other

WCS-19082: Unable to load up the {0} service.
Cause: An internal error occurred and the {0} service failed to load.
Action: Contact Oracle Support Services

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19083: Access to permission class {0} is not allowed
Cause: An attempt was made to access the specified permission class.Permission class {0} is not accessible.
Action: Contact Oracle Support Services

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19084: Permission class{0} can not be instantiated
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19085: Unable to instantiate the policy store for WebCenter Portal
Cause: An error occurred while trying to access the policy store associated with WebCenter Portal.
Action: Contact Oracle Support Services

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19088: Failed to register application management beans
Cause: Application management beans(MBean) registration failed.Either there are issues with OC4J or the application was not packaged properly.
Action: Restart OC4J or examine OC4J log files for further details.

Level: 1

Type: ERROR

Impact: Other

WCS-19089: Failed to unregister application management beans
Cause: Application management beans(MBean) unregistration failed. Either the Mbeans were not registered or the Mbeans were already unregistered.
Action: Examine the OC4J log files for further details.

Level: 1

Type: ERROR

Impact: Other

WCS-19090: An unexpected error has occurred, unable to complete the export process.
Cause: The export process failed due to an internal error.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19101: Unable to save the export archive on the local file system due to an unexpected error.
Cause: Unexpected error occurred while saving the export archive on the local file system.
Action: Contact Oracle Support Services

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19102: Unexpected error occurred while exporting the security policy. Unable to export the policy store.
Cause: An unexpected error occurred while exporting policy store metadata to the local file system.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19104: Unable to export connection details for external application with ID {0}
Cause: An internal error occurred. Unable to retrieve details for an external application appearing in WebCenter Portal.
Action: Ask your WebCenter Portal administrator to clean up external applications appearing in the Sidebar or reconfigure the external application connection using Enterprise Manager.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19105: Unable to find connection details for external application with ID {0}
Cause: No connection details found for external application with the specified ID.
Action: Remove the external application link associated with the specified ID from the Applications pane in the Sidebar.

Level: 1

Type: WARNING

Impact: Other

WCS-19106: Unable to save preference settings
Cause: An error occurred while attempting to save preferences settings to the metadata store.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19107: Invalid date format {0} retrieved from the preference store.
Cause: An attempt was made to retrieve date information but the source date format was invalid.
Action: Verify whether the date format source returns the correct date format.

Level: 1

Type: WARNING

Impact: Other

WCS-19108: Invalid time format {0} retrieved from the preference store.
Cause: An attempt was made to retrieve time information but the source time format was invalid.
Action: Verify whether the time format source returns the correct time format

Level: 1

Type: WARNING

Impact: Other

WCS-19109: Unable to find service.
Cause: Unable to find the service metadata in WebCenter Portal
Action: Contact Oracle Support Services

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19110: Specify a location on server.
Cause: Unable to locate archive for import.
Action: Specify the archive's name and server location, and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19111: Specify an archive that exists on the file system.
Cause: Unable to locate archive for import.
Action: Specify a valid archive that exists on the file system and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19112: Specify a server location.
Cause: Unable to locate the specified directory for the export archive.
Action: Specify a valid directory on the server for the export archive and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19113: Specify an existing directory on the server.
Cause: Unable to locate the specified directory.
Action: Specify a valid directory on the server and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19114: Specify a valid name for the portal archive. Usage of special character / or \ is not allowed.
Cause: Usage of special character / or \ is not allowed.
Action: Specify a valid name for the portal archive.

Level: 1

Type: ERROR

Impact: Other

WCS-19115: Specify a valid name for the portal template archive. Usage of special character / or \ is not allowed.
Cause: Usage of special character / or \ is not allowed.
Action: Specify a valid name for the portal template archive.

Level: 1

Type: ERROR

Impact: Other

WCS-19116: Specify a valid name for the portal archive with the file extension {0}.
Cause: Invalid file extension specified.
Action: Specify a valid name for the portal archive with the file extension '.par'

Level: 1

Type: ERROR

Impact: Other

WCS-19117: Specify a valid name for the portal template archive with the file extension {0}.
Cause: Invalid file extension specified.
Action: Specify a valid name for the portal template archive with the file extension '.par'

Level: 1

Type: ERROR

Impact: Other

WCS-19118: Invalid portal archive extension provided: {0}. Specify a valid name for the portal archive and use the file extension {1}.
Cause: Invalid portal archive extension specified.
Action: Specify a valid name for the portal archive and use the file extension '.par'

Level: 1

Type: ERROR

Impact: Other

WCS-19119: Unable to add the new link : {0}
Cause: An attempt to add a new link {0} to the metadata store failed.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19120: Unable to add link as no proper handler found for the selected resource type
Cause: An attempt to add a new link but the resource being added is neither a task flow or an external application.
Action: Only task flows or external application link can be included.

Level: 1

Type: ERROR

Impact: Other

WCS-19121: Unable to retrieve the shell configuration metadata
Cause: The metadata file is corrupt or missing.
Action: Ensure that the file exists and complies with the schema.Alternatively, contact your WebCenter Portal administrator for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-19122: Invalid shell panel name
Cause: The shell panel name was probably NULL.
Action: Provide a valid shell panel name.

Level: 1

Type: ERROR

Impact: Other

WCS-19123: Unable to retrieve the shell handler for the current request {1}
Cause: The shell handler was not set for the current request
Action: Verify the URL and that the WebCenter Portal shell filter is configured to handle requests of this kind

Level: 1

Type: WARNING

Impact: Other

WCS-19124: Unable to save changes to shell metadata
Cause: An error occurred while saving the shell metadata document.
Action: Ensure that the shell metadata document is not corrupt and is writable and personalizable.

Level: 1

Type: ERROR

Impact: Other

WCS-19125: Account for user {0} is disabled
Cause: The account for user {0} account is disabled.
Action: Ask the WebCenter Portal administrator to activate the account.

Level: 1

Type: ERROR

Impact: Other

WCS-19126: Account for user {0} is inactive
Cause: The account for user {0} is disabled.
Action: Ask the WebCenter Portal administrator to activate the account.

Level: 1

Type: ERROR

Impact: Other

WCS-19127: The account for user {0} is locked
Cause: The account is locked for user {0}
Action: Ask the WebCenter Portal administrator to unlock the account.

Level: 1

Type: ERROR

Impact: Other

WCS-19128: Password has expired for user account {0}
Cause: Password for this user has expired
Action: Contact the WebCenter Portal administrator for assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-19129: Incorrect Old Password for user account {0}
Cause: The old password specified for this user is not correct.
Action: Enter the correct password

Level: 1

Type: ERROR

Impact: Other

WCS-19130: Password for user account {0} is null
Cause: No password was specified.
Action: Enter a valid password.

Level: 1

Type: ERROR

Impact: Other

WCS-19131: Error occurred granting permissions to user {0} for the newly created page {1}
Cause: An unexpected error occurred while granting the user permission
Action: Contact the WebCenter Portal administrator

Level: 1

Type: WARNING

Impact: Other

WCS-19132: Unable to retrieve the permission target for page {0}
Cause: An unexpected error occurred. The ADFm page definition of the page may be missing
Action: Ensure that the page definition exists and is valid.

Level: 1

Type: WARNING

Impact: Other

WCS-19133: Unable to determine the page in focus
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

WCS-19134: Unable to hide a page, locked by another user
Cause: An attempt was made to hide a page that is currently locked by another user.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19135: No page selected for hiding
Cause: Unable to determine which page has focus.
Action: Select the page you want to hide and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19136: Unable to hide the page.
Cause: An attempt was made to hide the last open page.
Action: Open some other page and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19137: Unable to determine the page focus for hiding
Cause: Unable to determine which page has focus.
Action: Select the page you want to hide and try again. Alternatively, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19138: Unable to encode the value {1} of parameter {0} using encoding format {2}
Cause: The encoding format was unexpectedly invalid.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19139: Unable to decode the value {1} of parameter {0} using encoding format {2}
Cause: The encoding format was unexpectedly invalid.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19140: Unable to update the page titled {0} ({1})
Cause: An error occurred while saving the changes.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19141: Unable to save changes to the metadata store
Cause: An error occurred while saving the changes.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19142: Role mapping SPIs are throwing exception
Cause: An internal occurred error while accessing role mapping SPIs.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19143: Unable to retrieve the catalog for adding applications
Cause: An attempt to access the external application catalog failed. Either the external application catalog is not configured or configuration details are unavailable.
Action: Check whether the ext-app-catalog attribute is configured in webcenter-config.xml

Level: 1

Type: ERROR

Impact: Other

WCS-19144: Role name for user account is null or contains invalid characters
Cause: Either the role name was left blank or the role name contained invalid characters.
Action: Enter a valid role name.

Level: 1

Type: ERROR

Impact: Other

WCS-19145: Operation succeeded with errors. The mapping of roles failed
Cause: Changes in services failed due to the following errors
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19146: Grant role completed with errors The mapping of roles failed in scope {0}
Cause: Changes in services failed due to the following errors
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19147: Page path can not be null
Cause: The specified page path is null or an empty string.
Action: Provide a valid string for the page path.

Level: 1

Type: ERROR

Impact: Other

WCS-19148: Cannot get the service categories metadata from the application metadata
Cause: Service category metadata has not been defined in the application metadata
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19149: Cannot get metadata for all services from the application metadata.
Cause: All service metadata has not been defined in the application metadata.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19150: Cannot get metadata for configurable services from the application metadata
Cause: Metadata for configurable services has not been defined in the application metadata.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19151: Cannot find a service with the ID {0}
Cause: No definition exists for a service with the specified service identifier
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19152: User {0} already has access.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19153: Edit the user to modify his role.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19154: This exception is due to one or more of the following exceptions -
Cause: One or more services configurations have failed.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19155: User {0} already has access or is invited.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19156: You cannot send an invite to this user as an invite has already been sent.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19157: Portal {0} may have been deleted or renamed
Cause: An attempt was made to access a portal that has been deleted or renamed.
Action: Contact the portal moderator or try searching for the portals.

Level: 1

Type: ERROR

Impact: Other

WCS-19158: Cannot personalize visibility of page {0} in portal {1}
Cause: A personalization attempt failed. Either the backing store could not be accessed or some other personalization operation was performed simultaneously.
Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19159: Unable to save page creation
Cause: An attempt to save the new page failed. Either the back-end store could not be accessed or another page was created simultaneously.
Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19160: Unable to save the personal sequence of pages in scope {0}
Cause: An attempt to personalize the page sequence failed. Either the back-end store could not be accessed or some other personalization operation was performed simultaneously
Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19161: Unable to save the change in sequence of pages in scope {0}
Cause: An attempt to change page sequence failed. Either the back-end store could not be accessed or a similar operation was performed simultaneously.
Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19162: Revoke role completed with errors The mapping of roles failed
Cause: Changes in services failed due to the following errors
Action: Contact Oracle Support Services

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19163: Scope is NULL for Security Manager
Cause: Scope identifier passed to the security manager is NULL.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19164: The security policy in the archive file was found to be invalid.
Cause: The imported security policy file was found to be invalid.
Action: Export the data again and try the import operation again.

Level: 1

Type: WARNING

Impact: Other

WCS-19165: The security policy in the archive file to be imported is invalid as it contains more than one jazn-policy node.
Cause: The imported security policy file is invalid as it contains more than one jazn-policy node.
Action: Export the data again the import operation again.

Level: 1

Type: WARNING

Impact: Other

WCS-19166: The security policy in the archive file to be imported is located on a read-only file system and this means the data cannot be updated.
Cause: The imported security policy file is located on a read-only file system and this means the data cannot be updated.
Action: Export the data again and try the import operation again.

Level: 1

Type: WARNING

Impact: Other

WCS-19167: Failed to import security configuration from the selected archive.
Cause: An unexpected error occurred while updating the deployed application in the import source archive.
Action: Check the logs for details of the error.Alternatively, contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-19168: Role {0} is created successfully but failed to copy the permissions from role {1}. The role {1} is not found.
Cause: An attempt to create the role failed because the base role was not found.
Action: Check whether the base role is still available.

Level: 1

Type: ERROR

Impact: Other

WCS-19169: An error occurred while trying to remove a role {0} from the policy store.
Cause: The specified role does not exist in the policy store.
Action: Check the details of the error and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19170: Application role {0} still used in the policy store
Cause: The specified role is in use.
Action: Remove the usage of the role and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19171: Application role {0} to be granted is not found
Cause: Specified role was not found.
Action: Check the role name {0} and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19172: Internal error while creating security manager for portal {0}
Cause: Unable to resolve the Scope GUID for Scope {0}
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19173: New passwords for user account {0} do not match
Cause: Passwords were entered incorrectly.
Action: Enter the correct passwords.

Level: 1

Type: ERROR

Impact: Other

WCS-19174: Few of the mandatory resource(s) are in use. Please try again later.
Cause: The lock, client is trying to release is already locked.
Action: Try after some time

Level: 1

Type: ERROR

Impact: Other

WCS-19175: Unable to release the lock on document {0}
Cause: A call to release lock in the back-end has failed.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19176: Releasing the current lock on {0} failed
Cause: The lock, client is trying to release is already released.
Action: Acquire the lock again to release.

Level: 1

Type: ERROR

Impact: Other

WCS-19177: Name Cannot Be Null
Cause: Name Cannot Be Null
Action: Enter a User or Group

Level: 1

Type: WARNING

Impact: Other

WCS-19178: User Not Found
Cause: User Not Found
Action: Enter a username

Level: 1

Type: WARNING

Impact: Other

WCS-19179: Group not found or multiple groups with the same name exist.
Cause: Group not found or multiple groups with the same name exist
Action: Enter a Group

Level: 1

Type: WARNING

Impact: Other

WCS-19180: User with this name doesn't exist
Cause: User with this name doesn't exist
Action: Enter a role which has users

Level: 1

Type: WARNING

Impact: Other

WCS-19181: Unable to read the application configuration metadata
Cause: The metadata file could have got corrupt or removed
Action: Please ensure that the file exists and complies with the schema, or contact the administrator for assistance

Level: 1

Type: ERROR

Impact: Other

WCS-19182: Unable to move link/folder
Cause: The metadata file could have got corrupt or removed
Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

WCS-19183: Unable to create folder {0}
Cause: The metadata file could have got corrupt or removed
Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

WCS-19184: Unable to delete link/folder {0}
Cause: The metadata file could have got corrupt or removed
Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

WCS-19185: Role cannot be created because it contains special characters
Cause: Creation of Role {0} failed because it contains special characters
Action: Remove special characters used in your role and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19186: Role {0} cannot be created, as the role of same name exists in the policy store
Cause: Creation of Role {0} failed because policy store already contains a role of same name
Action: Try changing role name

Level: 1

Type: ERROR

Impact: Other

WCS-19187: Granting of Role {0} partially succeeded for identity {1}. Granting permissions for {2} failed. You can take actions regarding these warnings in portal settings.
Cause: Granting of Role for certain Services failed due to RoleMapping Exception
Action: Please check the log for actual error stack.

Level: 1

Type: ERROR

Impact: Other

WCS-19188: Revoking of Role {0} partially succeeded for identity {1}. Revoking permissions for {2} failed. You can take actions regarding these warnings in portal settings.
Cause: revoking of Role for certain Services failed due to RoleMapping Exception
Action: Please check the log for actual error stack.

Level: 1

Type: ERROR

Impact: Other

WCS-19189: Mapping the permissions {0} failed. You may want to try the operation again after some time or can contact Administrator.
Cause: Granting of Role for certain Services failed due to RoleMapping Exception
Action: Please check the log for actual error stack.

Level: 1

Type: ERROR

Impact: Other

WCS-19190: Fatal Error while granting role for certain services.
Cause: Granting of Role for certain Services failed due to RoleMapping Exception
Action: Please check the log for actual error stack.

Level: 1

Type: ERROR

Impact: Other

WCS-19191: User(s) {0} has already been granted the role {1}.
Cause: Current User / Role {0} has been already granted the application role.
Action: Don't Provision this user since it is already provisioned.

Level: 1

Type: ERROR

Impact: Other

WCS-19192: Role has been granted with errors. You might want to contact Administrator or Remove/Grant Role again.
Cause: Role was granted with errors.
Action: Contact the Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19193: Fatal Error while granting the role.
Cause: Fatal Error while granting the role.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19194: Invitations were sent out but persisting the invited users data resulted in fatal error.
Cause: Members Fatal Error while granting the role.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19195: Page {0} cannot be found in the system
Cause: The page may have been deleted or the page path is incorrect
Action: Specify a correct path to an existing page

Level: 1

Type: ERROR

Impact: Other

WCS-19196: {0} : Irresolvable error(s) occurred. You may want to contact Administrator with the error reference.
Cause: Fatal Error occurred.
Action: Contacts the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19197: {0} : Unexpected error(s) occurred. You may want to contact Administrator with the error reference.
Cause: Fatal Error occurred.
Action: Contacts the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19198: {0} : Unknown error(s) occurred. You may want to contact Administrator with the error reference.
Cause: Fatal Error occurred.
Action: Contacts the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19199: {0} : Multiple errors occurred {1}
Cause: Fatal Error occurred.
Action: Contacts the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19200: Fatal error while removing some grants. Please contact Administrator with error reference.
Cause: Fatal Error occurred.
Action: Contacts the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19201: Fatal error while removing the role. Please contact Administrator with error reference.
Cause: Fatal Error occurred.
Action: Contacts the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19202: Revoking role was partially successful. You can try this operation again after some time or contact Administrator.
Cause: Fatal Error occurred.
Action: Contacts the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19203: Fatal error while creating the role. Please contact Administrator with error reference.
Cause: Fatal Error occurred.
Action: Contacts the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19204: Unable to save Invite message for portal {0} due to unknown errors. Please try later or contact administrator
Cause: Error occurred while obtaining the invite message
Action: Try later or contact administrator

Level: 1

Type: ERROR

Impact: Other

WCS-19205: Unable to save member changes for a portal{0} due to unknown errors. Please try later or contact administrator
Cause: Error occurred while saving the member changes
Action: Try later or contact administrator

Level: 1

Type: ERROR

Impact: Other

WCS-19206: Could not find security policy in the archive file being imported.
Cause: The security policy file was not found in import archive.
Action: Export the data again and try the import operation again.

Level: 1

Type: ERROR

Impact: Other

WCS-19207: One or more mandatory roles are not found in the copied instance for scope {0}. Role Name: {1}
Cause: One or more mandatory roles are not found in the copied instance.
Action: Add the mandatory role {1} in the security metadata to get WebCenter Portal functionality or contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19208: Deletion of security metadata failed for scope {0}
Cause: Deletion of roles for the current scope {0} has failed.
Action: Try later or contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19209: An unexpected error occurred while trying to upload WebCenter Portal logo to path {0}
Cause: MDS StreamedObject creation failed for WebCenter Portal logo
Action: Contact administrator for further assistance.

Level: 1

Type: ERROR

Impact: Other

WCS-19210: The image upload failed as the image file you tried to upload was invalid. Provide a valid image file.
Cause: Unable to upload the WebCenter Portal logo as the file is null or not available.
Action: Upload a valid image file

Level: 1

Type: ERROR

Impact: Other

WCS-19211: An error occurred while trying to retrieve the templates to be used for page creation. Please contact Administrator with error reference.
Cause: An unexpected error occurred.
Action: Contacts the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19212: An error occurred while trying to determine the template selected for page creation. Please contact Administrator with error reference.
Cause: An unexpected error occurred.
Action: Contacts the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19213: Unable to persist customization for tag with webcenterId ''{0}'' in the Personal Sidebar
Cause: An error saving customizations on the Personal Sidebar JSPX, or the tag with this webcenterId could not be located.
Action: Ensure that the customization is enabled on the Personal Sidebar JSPX, and the tag has a unique webcenterId

Level: 1

Type: ERROR

Impact: Other

WCS-19214: Failed to get the custom page permission for pageDef {0} for action {1}
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19215: Failed to get the roles having permission {0}
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19216: Failed to get the users having permission {0}
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19217: Unable to get list of links
Cause: An error occurred while getting the list.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19218: An error occurred while saving the page default settings. The settings may not have been saved.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19219: Unexpected error occurred while deleting the page
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19220: Search for role {0} resulted in more than one result. Please contact Administrator to get it rectified
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19221: While provisioning the services, errors were encountered for following services - {0}. Check if these services have been configured correctly.
Cause: While copying the services, errors were encountered for certain services.
Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19222: Unknown error in adding link to the table
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19223: Unknown error in retrieving the link information
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19224: Unknown error in updating the link information
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19225: Unknown error in deleting the link
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19226: Unable to close connection
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19227: Unexpected error occurred while restoring the page
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19228: Unexpected error occurred while creating list of pages
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19229: Error occurred in getting the complete list of pages you can access. Please contact the administrator.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19230: Invalid page name
Cause: Invalid page name
Action: Please enter a valid page name.

Level: 1

Type: ERROR

Impact: Other

WCS-19231: Unexpected error occurred while creating the page
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19232: While provisioning the services, errors were encountered for following services - {0}. Check if these services have been configured correctly.
Cause: While provisioning the services, errors were encountered for certain services.
Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19233: While renaming all the provisioned services, errors were encountered for following services - {0}.
Cause: While renaming the portal, errors were encountered for certain services.
Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19234: While unprovisioning the services, errors were encountered for following services - {0}.
Cause: While unprovisioning the services, errors were encountered for certain services.
Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19235: Unknown error occurred. Please contact Administrator.
Cause: Unknown error occurred.
Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19236: The following service(s) are currently unavailable: {0}. If the problem persists contact your administrator.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19237: Unable to export the portal {0}. Either the portal does not exist or the portal is being exported/imported by another user. Refresh the portal list and try again.
Cause: Unable to acquire a lock on the scope of portal.
Action: Refresh the portal list and try again. If the problem persists, contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19238: Unable to export the portal template {0}. Either the portal template does not exist or the portal template is being exported/imported by another user. Refresh the portal template list and try again.
Cause: Unable to acquire a lock on the scope of portal template.
Action: Refresh the portal template list and try again. If the problem persists, contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19239: Unable to import portals as required resources are not available. Portals being replaced on the target either do not exist or are being exported/imported by another user. Refresh the portal list and try again.
Cause: Unable to acquire a global lock to prevent create, delete, rename or import operations on portals.
Action: Wait for some time and try the import operation again. If the problem persists, contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19240: Unable to import portal templates as required resources are not available. Portal templates being replaced on the target either do not exist or are being exported/imported by another user. Refresh the portal template list and try again.
Cause: Unable to acquire a global lock to prevent create, delete, rename or import operations on portal templates.
Action: Wait for some time and try the import operation again. If the problem persists, contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19241: Errors occurred in the page.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19242: Unexpected error occurred while accessing copyright message.
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19243: Unexpected error occurred while accessing privacy URL.
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19244: Unexpected error occurred while accessing footer information.
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19245: An error occurred while saving the page security settings. The settings may not have been saved.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19246: Error occurred while refreshing the table of pages.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19247: Modification of role operation not supported for scope {0}
Cause: Currently the modification of role not supported.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19248: Portal {0} being exported is either online or being exported/imported by another user. Wait for some time and try the export operation again.
Cause: Portal is either online or blocked by another user/process.
Action: Refresh the portal list and try to export the portal again. If the problem persists, contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19249: Portal template {0} you are trying to export is being exported/imported by another user. Wait for some time and try the export operation again.
Cause: Portal template is blocked by another user/process.
Action: Refresh the portal template list and try to export the portal template again. If the problem persists, contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19250: Portal template {0} you are trying to import is being exported/imported by another user on the target. Wait for some time and try the import operation again.
Cause: Portal template is blocked by another user/process.
Action: Wait for some time and try to import the portal template again. If the problem persists, contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19251: You are trying to import portals but the archive specified contains portal templates. Check the archive file and try again.
Cause: You are trying to import portals but the archive specified contains portal templates.
Action: Use an export archive that contains portals.

Level: 1

Type: ERROR

Impact: Other

WCS-19252: You are trying to import portal templates but the archive specified contains portals. Check the archive file and try again.
Cause: You are trying to import portal templates but the archive specified contains portals.
Action: Use an export archive that contains portal templates.

Level: 1

Type: ERROR

Impact: Other

WCS-19253: Cannot locate the document ''{0}''.
Cause: The path is incorrect or it is not available in the system.
Action: Verify whether the path is correct and is available in the system.

Level: 1

Type: ERROR

Impact: Other

WCS-19254: Error occurred while reading the WebCenter Portal environment configuration file {0}.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19255: Unexpected error occurred while navigating to portal administration pages.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19256: Error occurred while saving the folder.
Cause: An unexpected error occurred while saving the folder.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19257: Unexpected error occurred while acquiring the write lock on the document {0}.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19258: Error occurred while clearing the deleted/renamed portal page.
Cause: Error occurred while clearing the deleted/renamed portal page.
Action: Error occurred while clearing the deleted/renamed portal page.

Level: 1

Type: ERROR

Impact: Other

WCS-19259: Portal "{0}" on the target application is either online or being exported/imported by another user. Wait for some time and try the import operation again.
Cause: Portal either online or blocked by another user/process.
Action: Wait for some time and try the import operation again. If the problem persists, contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19260: The current process could not be executed. Wait for some time and try again.
Cause: An unexpected error occurred while saving administration changes.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19261: Error occurred while saving administration changes.
Cause: An unexpected error occurred while saving administration changes.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19262: Another administrator is modifying the setting. Try again later.
Cause: An unexpected error occurred while saving administration changes.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19263: Fatal error occurred while getting the roles for current scope.
Cause: An unexpected error occurred while getting the roles.
Action: Please contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19264: Fatal error occurred while inviting user {0} for role {1}
Cause: An unexpected error occurred while getting the members.
Action: Please contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19265: Fatal error occurred while getting members.
Cause: An unexpected error occurred while getting the members.
Action: Please contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19266: Fatal error occurred while getting invitation message from the repository.
Cause: An unexpected error occurred while getting message.
Action: Please contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19267: Error occurred while reading the list of tabs from persistence store.
Cause: An unexpected error occurred while reading the list of tabs.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19268: Following error occurred while storing the list of tabs to persistence store - {0}
Cause: An unexpected error occurred while storing the list of tabs.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19269: Error in processing the pages.
Cause: Unexpected error occurred while adding the page.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19270: Error in processing the pages.
Cause: Unexpected error occurred while removing the page.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19271: Error in processing the pages.
Cause: Unexpected error occurred while finding the page.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19272: Error in processing the pages.
Cause: Unexpected error occurred while creating the menu model.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19273: Error in navigation.
Cause: Unexpected error occurred while navigating to secondary page.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19274: Error in processing the pages.
Cause: Unexpected error occurred while preparing the children.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19275: Error in processing the pages.
Cause: Unexpected error occurred while preparing the page for current request.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19276: Error in navigation.
Cause: Unexpected error occurred while getting the navigable path to the page.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19277: An error occurred while changing the page visibility. Refresh the page list and retry.
Cause: Unexpected error occurred while changing the page's visibility.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19278: Error in renaming the page.
Cause: Unexpected error occurred while changing the page name.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19279: Error in creating a copy of the page.
Cause: Unexpected error occurred while copying the page.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19280: The role name {0} is reserved, please use some other name.
Cause: Unexpected error occurred while creating the role name.
Action: Try creating a role with some other name.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19281: Unexpected error occurred while refreshing list of pages.
Cause: Unexpected error occurred while refresh.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19282: Unable to save the BusinessRole sequence of pages.
Cause: An attempt to customize the BR page sequence failed. Either the back-end store could not be accessed or some other customization operation was performed simultaneously
Action: Try the operation again. If the problem persists, contact your administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19283: Error in reordering the pages.
Cause: Unexpected error occurred while reordering the pages.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19284: Error in reordering the business role pages.
Cause: Unexpected error occurred while reordering the business role pages.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19285: Error in reordering the pages.
Cause: Unexpected error occurred while reordering the pages.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19286: Error in moving the page up.
Cause: Unexpected error occurred while moving the page up.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19287: Error in moving the page down.
Cause: Unexpected error occurred while moving the page down.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19288: Error in processing the pages.
Cause: Unexpected error occurred while closing the page.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19289: Unexpected error in closing page(s).
Cause: Unexpected error occurred while closing the pages.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19290: Unexpected error in getting list of moderators.
Cause: Unexpected error occurred while getting the list of moderators.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19291: Unexpected error occurred in getting the page Uri for the favorites.
Cause: Unexpected error occurred while getting the Uri for the favorites.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19292: Unexpected error occurred in creating the new folder.
Cause: Unexpected error occurred while creating a new folder.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19293: Unexpected error occurred while getting the list of favorites.
Cause: Unexpected error occurred while getting the list of favorites.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19294: Unexpected error occurred while trying to navigate to bookmark.
Cause: Unexpected error occurred while trying to navigate to bookmark.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19295: Error occurred while reverting administration changes.
Cause: An unexpected error occurred while reverting administration changes.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19296: The application failed to access backend data store and cannot process requests
Cause: Access to backend data store failed
Action: Ensure the back-end data store that contains the WebCenter Portal schema and MDS schema is accessible.

Level: 1

Type: ERROR

Impact: Other

WCS-19297: The URL typed by current user is not accessible, so redirecting to the unAuthorized page
Cause: The current user does not have privileges to see the current URL
Action: Please contact system administrator

Level: 1

Type: ERROR

Impact: Other

WCS-19298: Unexpected error occurred, please retry the operation
Cause: An internal error occurred
Action: Retry the operation. Contact Oracle Support Services if the issue persists.

Level: 1

Type: ERROR

Impact: Other

WCS-19299: Unexpected error occurred while preparing the administration pages
Cause: An internal error occurred
Action: Retry the operation. Contact Oracle Support Services if the issue persists.

Level: 1

Type: ERROR

Impact: Other

WCS-19300: Unexpected error trying to restore the Login page
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19301: Unexpected error trying to navigate to the Login page
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19302: Unexpected error trying to open the Login page for edit
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19303: Unexpected error occurred while moving a page to top of the pages list
Cause: Unexpected error occurred while moving a page to top of the pages list
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19304: Unexpected error occurred while moving a page to bottom of the pages list
Cause: Unexpected error occurred while moving a page to bottom of the pages list
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19305: Drag and drop is not allowed for ungrouped view
Cause: Drag and drop was attempted in ungrouped view
Action: Drag and drop operation is not allowed for ungrouped view

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19306: Reorder of personal pages is not allowed here
Cause: A personal page was selected as either the drag source or the drop target
Action: Exclude personal pages from drag and drop operations

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19307: Unexpected error occurred while creating mandatory document.
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19308: Failed to grant a role {1} to identity {0} in scope {2}
Cause: Failed to find identity {0} in Identity Store while Granting a role {1} in scope {2}
Action: Create a new Identity {0} in Identity Store and try again

Level: 1

Type: WARNING

Impact: Other

WCS-19309: Unexpected error retrieving services for configuration
Cause: An unexpected error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19310: Unexpected error occurred while trying to retrieve list of languages
Cause: Unexpected error occurred while trying to retrieve list of languages
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19311: Error occurred granting role {0} in {1}. Refresh the members list to see which users were added successfully. Some errors are displayed below. Contact your administrator for a complete list of errors.
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19312: Identities : {0}, failed with the errors {1}
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19313: Setting {0} role for {1} failed. Please contact Administrator
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19314: Portal template {0} is an out-of-the-box template. You cannot export out-of-the-box portal templates.
Cause: Portal template is an out-of-the-box template.
Action: Refer to export documentation for more information or contact your administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19315: One or more pages of portal {0} are being edited by other users. Wait for some time and try again.
Cause: One or more portal pages are being edited by other users. You cannot export when pages are in edit mode.
Action: Close all the pages from edit mode or contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19316: One or more pages of portal {0} are being edited by other users. Wait for some time and try again.
Cause: One or more portal pages are being edited by other users. You cannot import when pages are in edit mode..
Action: Close all the pages from edit mode or contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19317: An unexpected error has occurred while sending notification to the administrator.
Cause: An unexpected error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19318: Granting of Role {0} partially succeeded for identity {1}. Granting permissions for {2} failed.
Cause: Granting of Role for certain Services failed due to RoleMapping Exception
Action: Please check the log for actual error stack.

Level: 1

Type: ERROR

Impact: Other

WCS-19319: Revoking of Role {0} partially succeeded for identity {1}. Revoking permissions for {2} failed.
Cause: revoking of Role for certain Services failed due to RoleMapping Exception
Action: Please check the log for actual error stack.

Level: 1

Type: ERROR

Impact: Other

WCS-19320: File {0} already exists. Do you want to overwrite it?
Cause: File already exists in the location where the export archive is being saved.
Action: Provide a new file name or overwrite the file.

Level: 1

Type: ERROR

Impact: Other

WCS-19321: Issues were faced while provisioning the service(s) - {0}. Check the portal services settings page if these services have been provisioned.
Cause: While provisioning the services, errors were encountered for certain services.
Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19322: You do not have sufficient permission to edit the page.
Cause: Your permission to edit the page might have been revoked.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19323: The image file {0} you tried to upload was invalid. Provide a valid image file.
Cause: Unable to upload the image as the file is null or invalid.
Action: Upload a valid image file

Level: 1

Type: ERROR

Impact: Other

WCS-19324: An error occurred while cleaning the pages from persistence store for current user.
Cause: An unexpected error occurred while cleaning the list of pages.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19325: One needs to login to access this url {0}
Cause: Public Users don't have access to this url
Action: Please login first.

Level: 1

Type: ERROR

Impact: Other

WCS-19326: Couldn''t invalidate joc region {0} due to {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19327: Could not delete joc region {0} due to {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19328: Could not add object {1} to joc region {0} due to {2}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19329: Could not replace object {1} in joc region {0} due to {2}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19330: Could not retrieve object {1} from joc region {0} due to {2}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19331: Could not invalidate object {1} in joc region {0} due to {2}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19332: Unexpected error occurred while processing roles in {0}
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19333: Unexpected error occurred while processing users in {0}
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19334: Unexpected error occurred while retrieving all users who have been assigned {0} in {1}
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19335: Could not validate user due to {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19336: Unexpected error occurred while retrieving enterprise roles for user {0}
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19337: Unexpected error occurred while retrieving application role {0}
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19338: Could not retrieve display name for user {0} due to {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19339: Unable to retrieve user mail ID for {0} due to {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19340: Unable to retrieve members mailing list for {0} due to {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19341: Could not verify lifecycle block status due to {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19342: Unexpected error occurred while retrieving users / groups who have been granted application role {0}
Cause: An unexpected error occurred.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19343: Unable to send notification to administrator(s). The reason is : {0}.
Cause: The BPEL server is not configured
Action: Configure workflows.

Level: 1

Type: ERROR

Impact: Other

WCS-19344: User(s) {0} has already been invited to portal.
Cause: An unexpected error occurred while inviting users.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19345: Errors occurred in inviting user(s) to join the portal {1} as role {0}. Please refresh the members list below to see the latest status about the invited users. Some of the errors are displayed below( Please note that following list may not be listing all the errors. For the complete list of errors, please contact the administrator).
Cause: An unexpected error occurred while inviting users.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19346: User {0} not invited to portal {1}.
Cause: User {0} not invited to portal {1}.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19347: The default shell-config document cannot be read for looking up application-specific URL parameters, due to {0}.
Cause: The metadata repository might be down or the document may have got corrupted.
Action: Verify that the metadata repository is up and the document contents are valid.

Level: 1

Type: WARNING

Impact: Other

WCS-19348: Error occurred during permissions related operations. Refresh the roles screen to see the updated information. Contact your administrator for the list of errors.
Cause: An unexpected error occurred during permission related operations.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19349: Could not find application role matching the search string {0} due to {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19350: Removing role mapping related to service {0} failed due to {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19351: Could not send notification to administrator as server may be down or Portal workflows are not accessible. Try again after some time.
Cause: Failed to connect to SOA server.
Action: Check if the SOA server is up or if Portal workflows are deployed on SOA server.

Level: 1

Type: ERROR

Impact: Other

WCS-19352: Unable to complete the export process as required resources are not available. Another export or import process might be in progress. Please try export again after sometime.
Cause: Export operation failed. Either another export process or portal operation is in progress.
Action: Wait for some time and try the export operation again. If the problem persists, contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19353: Import failed. The portal archive contains new portals without security information.
Cause: The portal archive you are trying to import contains new portals without security. All new portals must include security information.
Action: Export the portals again with security and try again. If the problem persists, contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19354: The page {0} (in {1}) cannot be copied due to {2}.
Cause: An error occurred while trying to copy the page.
Action: Refine the logging level, retry the operation, and check the logs for more information about the error, or contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19355: Unable to make updates to the attributes of the page {0} due to {1}.
Cause: An error occurred while trying to make updates to the page attributes.
Action: Refine the logging level, retry the operation, and check the logs for more information about the error, or contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-19356: Unable to open the requested page.
Cause: An unexpected error while opening the page or while creating a copy of it for editing.
Action: Contact the administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-19357: Could not find the page label due to {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19358: Identity(s) {0} has already been added to portal.
Cause: An unexpected error occurred while adding users.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19359: You cannot invite yourself as a member.
Cause: Operation not allowed.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19360: Could not retrieve the role {0}. Please contact administrator.
Cause: An unexpected error occurred.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19361: Could not find the page visibility due to {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19362: You cannot add yourself as a member.
Cause: Operation not allowed.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19363: SDP Messaging URL cannot be obtained due to {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19364: Unable to compute context URL for page {0} with title {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19365: Unable to change password. Contact administrator.
Cause: An unexpected error occurred while setting the password.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19366: Export failed. The export process took too long to complete. Use the export WLST command to perform this export operation.
Cause: Export timeout occurred. Either the export set is too large or the policy store information to be exported is too large.
Action: Try exporting fewer portals or use WLST to perform the export operation.

Level: 1

Type: ERROR

Impact: Other

WCS-19367: Import failed. The import process took too long to complete. Use the import WLST command to perform this import operation.
Cause: Import timeout occurred. Either the import set is too large or the policy store information to be imported is too large.
Action: Try importing fewer portals or use WLST to perform the import operation.

Level: 1

Type: ERROR

Impact: Other

WCS-19368: Could not find the secondary tab for the current request. PrimaryTab found : {0}, SubTabs : {1}, LastAccesedPage(From previous session) : {2}, Page service cache : {3}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19369: Get Member Info not supported for scope
Cause: Currently get Member Info not supported.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19370: You can not invite a group for the portal subscription
Cause: Inviting group is not supported
Action: Please contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19371: Failed to read the notification message from backend datastore
Cause: Notification message is null, try setting it
Action: Please contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19372: Group name is empty
Cause: Given group name is empty
Action: Please pass the correct group name

Level: 1

Type: ERROR

Impact: Other

WCS-19373: Granting of role {0} failed for identities {1}.
Cause: Exception occurred while granting a role {0} to identities {1}
Action: Please check the log for actual error stack.

Level: 1

Type: ERROR

Impact: Other

WCS-19374: Group {0} grant to {1} failed for users {2}. The following users are already granted a role: {3}
Cause: An internal error occurred
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19375: Group {0} is not found in Identity Store
Cause: Given group name is not found
Action: Please pass the correct group name

Level: 1

Type: ERROR

Impact: Other

WCS-19376: {0} User(s) including {1} have already been granted role(s) {2}.
Cause: User(s) already granted roles.
Action: User(s) already granted roles.

Level: 1

Type: ERROR

Impact: Other

WCS-19377: Group(s) {0} has already been granted role(s).
Cause: Group(s) already granted role(s)
Action: Group(s) already granted role(s)

Level: 1

Type: ERROR

Impact: Other

WCS-19378: Unable to grant role mapping permissions for role {0} in scope {1}
Cause: The role was not granted role mapping permissions. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-19379: Unable to drop role mapping permissions for role {0} in scope {1}
Cause: There was an error while dropping role mapping permissions for the role. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-19380: Unexpected error while restoring the Default Profile Gallery Page.
Cause: There was an error while removing the profile page customization. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-19381: Unexpected error occurred while setting the language
Cause: Unexpected error occurred while trying to save the language choice
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19382: Copying of members failed for following identities {0}
Cause: Copying of members failed for following identities {0}.
Action: Try again after some time or Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19383: Operation not allowed on child portal {0}
Cause: Child portal does not support the operation.
Action: Perform on correct parent portal or Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19384: Unexpected error occurred while getting the list of page templates
Cause: Unexpected error occurred while getting the list of Page Templates
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19385: Unexpected error occurred while getting the list of Resource Catalogs
Cause: Unexpected error occurred while getting the list of Resource Catalogs
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19386: Unexpected error occurred while getting the languages
Cause: Unexpected error occurred while trying to retrieve the languages
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19387: Unexpected error occurred while creating translations for the imported portal.
Cause: Unexpected error occurred while creating the translations.
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-19388: Unexpected error occurred while collapsing the sidebar
Cause: Unexpected error occurred while
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19389: Unexpected error occurred while expanding the sidebar
Cause: Unexpected error occurred while
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19390: Unexpected error occurred while getting the list of recently accessed portals.
Cause: Unexpected error occurred while getting the list of recently accessed portals.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19391: Unexpected error downloading vcard
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19392: Unexpected error looking up user profile
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19393: Unexpected error launching resource
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19394: Unexpected error occurred while getting the list of portals current user can access.
Cause: Unexpected error occurred while getting the list of portals current user can access.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-19395: A page named {0} already exists.
Cause: A page with the specified name exists.
Action: Specify a unique name for the page.

Level: 1

Type: ERROR

Impact: Other

WCS-19396: Unexpected error while restoring the Default Page.
Cause: There was an error while removing the page customization. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-19397: Unexpected error while changing the permission model for portal {0}.
Cause: Unexpected error while changing the permission model for portal {0}.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19398: No users/groups selected
Cause: No users/groups were selected to perform the requested operation on.
Action: Select one or more users/groups and retry the operation.

Level: 1

Type: ERROR

Impact: Other

WCS-19399: Exception occurred while searching groups for a user :{0}
Cause: An unexpected error/exception occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-19400: Failed to determine public access on page {0} due to {1}
Cause: An unexpected error/exception occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-19401: "Unexpected error getting read lock on {0}
Cause: An unexpected error/exception occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-19402: Error determining the template for the current page
Cause: Unexpected severe error.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19403: Error occurred while fetching the list of navigations.
Cause: Unexpected error while fetching list of navigations.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19404: Scope list cannot be empty.
Cause: Unexpected error while fetching list of portals.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19405: Unable to set the security parent of {0} to {1}.
Cause: Unexpected error while setting the security parent.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19406: Unable to delete base docs from archive.
Cause: Unexpected error while deleting base docs from archive.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19407: Resources conflict. Base resource on target is not same as the base resource on source. Import cannot proceed.
Cause: Resources conflict occurred at the target.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19408: Unable to flush changes for deleted base docs from archive.
Cause: Unexpected error while deleting base docs from archive.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19409: Could not create site registry as folder does not exists.
Cause: Unexpected error while creating the site registry.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19410: Error occurred while refreshing template cache.
Cause: Unexpected error occurred while refreshing template cache.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19411: {0}.
Cause: Unexpected error while fetching list of navigations.
Action: Contact Administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-19412: Error occurred while saving the custom attributes in metadata.
Cause: Unexpected error occurred while saving the custom attributes in metadata.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19413: Error occurred while granting permission to portal {0} for the provisioned service(s).
Cause: Unexpected error occurred while granting permission.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19414: Error occurred while checking for portal permission.
Cause: Error occurred while checking community manage permission.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19415: For user {0}, couldn''t retrieve the list of pages last accessed due to {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19416: Check for valid repository failed.
Cause: Either the database is down or the WebCenter Portal repository is not installed.
Action: Check the exception's details to why this error occurred.

Level: 1

Type: ERROR

Impact: Other

WCS-19417: For user {0}, the last accessed page couldn''t be found due to {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19418: For user {0}, couldn''t clean the last accessed page due to {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19419: For user {0}, couldn''t retrieve the last accessed page in {1} due to {2}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-19420: Unexpected error occurred while checking custom access for the portal {0}.
Cause: Likely the authorizer class specified in WebCenter Portal configuration could not be accessed. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-19421: Denying access for scope {0} as {1} property not specified in WebCenter Portal configuration
Cause: The authorizer class is not specified against specified property in WebCenter Portal Configuration
Action: Define the specified property pointing to the required ResourceAuthorizer implementation in WebCenter Portal configuration

Level: 1

Type: WARNING

Impact: Other

WCS-19422: Grant Role to Role Mapped Service for Portal User role not supported in scope {0}
Cause: Grant Role to Role Mapped Service for Portal User role not supported in scope {0}.
Action: Do not try this operation in this scope

Level: 1

Type: ERROR

Impact: Other

WCS-19423: Grant Role to Role Mapped Service for Public User role not supported in scope {0}
Cause: Grant Role to Role Mapped Service for Public User role not supported in scope {0}.
Action: Do not try this operation in this scope

Level: 1

Type: ERROR

Impact: Other

WCS-19424: Unable to delete site resource registry file from archive.
Cause: Unexpected error while deleting site resource registry file from archive.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19425: Checking whether portal is published to Portal user is not supported in Home Portal.
Cause: An attempt was made to check whether the portal is published to Portal user in Home portal.
Action: This API must be invoked in the context of portal and not Home portal

Level: 1

Type: ERROR

Impact: Other

WCS-19426: Encountered exception: {0}. For diagnosis, turn on the logging level to FINEST and retry the operation. Details about the current state: {1}
Cause: An exception was encountered unexpectedly.
Action: Turn on the logging level to FINEST and retry the operation.

Level: 1

Type: WARNING

Impact: Other

WCS-19427: Error in setting Show Page of the business role page.
Cause: Unexpected error occurred while setting Show Page of the business role page.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19428: Unexpected error occurred while importing the security policy. Unable to import the policy store.
Cause: An unexpected error occurred while importing policy store metadata from the import archive.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19429: Unexpected error occurred while checking if the current user can {0} the scope {1}.
Cause: Unexpected error occurred while checking if the current user can {0} the scope {1}.
Action: Try again later or contact administrator

Level: 1

Type: ERROR

Impact: Other

WCS-19430: Unexpected error occurred while checking if the current user can {0} the asset {1} in scope {2}.
Cause: Unexpected error occurred while checking if the current user can {0} the asset {1} in scope {2}.
Action: Try again later or contact administrator

Level: 1

Type: ERROR

Impact: Other

WCS-19431: Unexpected error occurred while fetching roles for user {0} in portal {1}.
Cause: Unexpected error occurred while fetching roles for user {0} in portal {1}.
Action: Try again later or contact administrator

Level: 1

Type: ERROR

Impact: Other

WCS-19432: Fetching the roles of current user is not supported in default scope.
Cause: Fetching the roles of current user is not supported in default scope.
Action: Do not try this operation

Level: 1

Type: ERROR

Impact: Other

WCS-19433: Unexpected error occurred while setting action {0} to role {1}.
Cause: Unexpected error occurred while setting action {0} to role {1}.
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-19434: Fatal error occurred while getting members count.
Cause: An unexpected error occurred while getting the members count.
Action: Please contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19435: Couldn''t get the first accessible page for the Home portal due to {1}.
Cause: Error in getting the first accessible page for the Home portal.
Action: Contact the application administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-19436: The community query permission is not found
Cause: The community query permission is not found.
Action: Contact the application administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-19437: The community manage membership permission is not found
Cause: The community manage membership permission is not found.
Action: Contact the application administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-19438: The community view membership permission is not found
Cause: The community view membership permission is not found.
Action: Contact the application administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-19439: The community edit membership permission is not found
Cause: The community edit membership permission is not found.
Action: Contact the application administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-19440: One or more pages of portal {0} is being edited by other users. The export archive may not contain the page changes.
Cause: One or more portal pages is being edited by other users. The export archive may not contain the page changes.
Action: Close all pages open in edit mode and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19441: One or more pages of portal {0} is being edited by other users. The import may not complete properly.
Cause: One or more portal page is in edit mode. The import may not complete properly.
Action: Close all pages open in edit mode and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19442: Invalid input - unmatched quotes
Cause: A string was provided with unmatched quotes.
Action: Ensure all quotes are opened and closed.

Level: 1

Type: ERROR

Impact: Other

WCS-19450: Unable to fetch custom property {0} at the application level
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: WARNING

Impact: Other

WCS-19451: Unable to fetch custom property {0} from scope {1}
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: WARNING

Impact: Other

WCS-19452: Could not initialize Default Portal Setting
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Other

WCS-19453: Could not update the default portal identity settings
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Other

WCS-19454: Could not update the default portal public setting
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Other

WCS-19455: Could not update the default portal default setting
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Other

WCS-19456: Could not set the redirect on login setting for default portal
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Other

WCS-19457: Could not update default portal settings to handle rename of portal from {0} to {1}
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details. Change the portal manually in Administration screens

Level: 1

Type: ERROR

Impact: Other

WCS-19458: Could not update default portal settings to handle delete of portal {0}
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details. Change the portal manually in Administration screens

Level: 1

Type: ERROR

Impact: Other

WCS-19459: The default portal configuration is being modified by another user. Try operation after some time.
Cause: >Another admin user is updating the default portal configuration
Action: Try the operation after some time

Level: 1

Type: WARNING

Impact: Other

WCS-19460: Could not fetch the default portal configuration from webcenter-config
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Go the Default Portal Configuration screen and change the default setting to desired values

Level: 1

Type: WARNING

Impact: Other

WCS-19461: Unexpected error while fetching the default portal due to {0}
Cause: Unexpected error while fetching the default portal
Action: Unexpected error while fetching the default portal

Level: 1

Type: WARNING

Impact: Other

WCS-19462: User {0} does not have the privileges required for this operation on Portals/Portal Templates. Verify that the user has ''Create Portal'' permission while performing import or deployment operation, ''Create and Manage Portal'' permission while performing redeployment operation and ''Manage Portal'' permission while performing export or propagation operation.
Cause: Check if the user has required permission on Portals for performing lifecycle operations.
Action: Try performing the operation as an administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19463: Error occurred while importing the security policy as the UCM server is down.
Cause: Error occurred while importing the security policy as the UCM server is down.
Action: Start the UCM server and retry this operation

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19464: User {0} not authorized to view Application.
Cause: User not authorized to view Application
Action: Contact Administrator to grant more permissions.

Level: 1

Type: ERROR

Impact: Other

WCS-19465: User {0} not authorized to configure Application.
Cause: User not authorized to configure Application
Action: Contact Administrator to grant more permissions.

Level: 1

Type: ERROR

Impact: Other

WCS-19466: Error occurred in creating translated scope resource bundle {0} due to {1}.
Cause: Unexpected error while creating scope resource bundle for newely created Portal/Template.
Action: Take action based on the underlying exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-19467: Error occurred while parsing document name due to {0}.
Cause: Unexpected error while parsing scope resource bundle file name.
Action: Take action based on the underlying exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-19468: Unexpected error occurred while adding Business Role Page for Impersonation due to {0}.
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-19469: Error occurred while adding Impersonation page:{0} to pages:{1} due to {2}.
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-19470: Error occurred while granting navigation permissions for role {0} for the scope {1} due to {2}
Cause: An unexpected error occurred while granting the user permission
Action: Contact the WebCenter Portal administrator

Level: 1

Type: WARNING

Impact: Other

WCS-19471: Error occurred while deleting the list of tabs to persistence store
Cause: An unexpected error occurred while deleting the list of pages.
Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19472: Unexpected error occurred while fetching current device group due to {0}
Cause: Unexpected error occurred while fetching current device group due to {0}
Action: Contact Administrator for more details

Level: 1

Type: ERROR

Impact: Other

WCS-19473: Get GUID call for LibOVDUser {0} returned null, which caused NullPointerException.
Cause: Misconfiguration found in jps-config.xml.
Action: Please contact the WebCenter Portal administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-19474: There are no Portal Server URL connections set.
Cause: There are no Portal Server URL connections set for deploying the portals.
Action: Please create a Portal Server URL Connection.

Level: 1

Type: ERROR

Impact: Other

WCS-19475: Failed to update application ready status
Cause: Status update to indicate application readiness with ReadyApp failed. There may be issues with registering or configuring the application.
Action: Examine WebLogic Server debug logs for further details.

Level: 1

Type: ERROR

Impact: Other

WCS-19476: Failed to update application not ready status
Cause: Status update to indicate application non-readiness with ReadyApp failed. There may be issues with registering or configuring the application.
Action: Examine WebLogic Server debug logs for further details.

Level: 1

Type: ERROR

Impact: Other

WCS-19477: Creation of seeded role is not supported for scope {0}
Cause: Currently the creation of seeded role is not supported.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-19478: Unable to grant permissions to {0} role in the policy store
Cause: An attempt to grant permissions failed due to unexpected errors.
Action: Determine the cause and, if necessary, try again.

Level: 1

Type: ERROR

Impact: Other

WCS-19479: Password does not adhere to password policy. {0}
Cause: Password does not adhere to password policy.
Action: Password must adhere to password policy.

Level: 1

Type: ERROR

Impact: Other

WCS-26001: Search Configuration Error: {0}
Cause: A configuration error has been encountered.
Action: Refer to the error details and the documentation for how to debug this.

Level: 1

Type: ERROR

Impact: Other

WCS-26021: Invalid Query {0}.
Cause: An invalid query was sent.
Action: Query validity is dependent on the service running it. Refer to the query in the log and the documentation for the service involved to debug this.

Level: 1

Type: ERROR

Impact: Other

WCS-26022: Contradiction caused when clause "{0}" is added to "{1}"
Cause: An unexpected programming error occurred. This is not something that can be fixed.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26023: The addition of criteria to {0} existing date criterion is not supported
Cause: An unexpected programming error occurred. This is not something that can be fixed.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26041: General Search Execution Error
Cause: A general execution error has been encountered.
Action: Query execution error is dependent on the service running it. Refer to the Query in the log and the documentation for the service involved to debug this.

Level: 1

Type: ERROR

Impact: Other

WCS-26042: The execution of the query does not complete within the execution time limit
Cause: The search query does not complete within the time limit.
Action: Re-try the search query again later.

Level: 1

Type: ERROR

Impact: Other

WCS-26061: General Search Response Error
Cause: A general response error has been encountered.
Action: Query execution response error is dependent on the service running it. Refer to the Query in the log and the documentation for the service involved to debug this.

Level: 1

Type: ERROR

Impact: Other

WCS-26062: Query results are immutable; removing elements from it is unsupported.
Cause: A caller tried to remove an element from the result set.
Action: Inform the caller that this is not a supported function.

Level: 1

Type: ERROR

Impact: Other

WCS-26063: SQL ResultSet consumption failed with the message "{0}".
Cause: A SQL ResultSet cannot be consumed.
Action: Refer to the underlying exception to debug this.

Level: 1

Type: WARNING

Impact: Other

WCS-26064: Cannot call "remove" method before calling "next" method.
Cause: Caller tried to call "remove" method of QueryResult class before calling "next" method.
Action: Inform the caller that this is an illegal operation.

Level: 1

Type: ERROR

Impact: Other

WCS-26065: Cannot convert "{0}" value to "{1}".
Cause: The target object had no "valueOf" method to convert the source.
Action: No action is needed; appropriate contingencies have been applied.

Level: 1

Type: WARNING

Impact: Other

WCS-26066: Parameter type {0} cannot be converted into a primitive type.
Cause: The conversion failed because the bean property was not of primitive type.
Action: No action is needed; appropriate contingencies have been applied.

Level: 1

Type: WARNING

Impact: Other

WCS-26081: General Search Authentication Error
Cause: A general authentication error has been encountered.
Action: Query execution authentication error is dependent on the service running it. Refer to the Query in the log and the documentation for the service involved to debug this.

Level: 1

Type: ERROR

Impact: Other

WCS-26091: Search API Implementation error in {0} class
Cause: An implementation error has been encountered.
Action: Report to the provider of the Search API Implementation.

Level: 1

Type: ERROR

Impact: Other

WCS-26101: An error occurred while parsing an XML document at {0}.
Cause: The XML document in question may not be well-formed or valid with respect to the referred XML schema.
Action: Examine the XML document again and check the XML schema to make sure there are not any mistakes or typos.

Level: 1

Type: ERROR

Impact: Other

WCS-26102: An error occurred while parsing the search configuration in adf-config.xml at {0}.
Cause: The XML fragment within adf-config.xml may not be well-formed or valid with respect to what is expected for search configuration.
Action: Examine the adf-config.xml document again and check the documented XML schema to make sure there are not any mistakes or typos.

Level: 1

Type: ERROR

Impact: Other

WCS-26103: An unexpected XML error occurred.
Cause: Something with the underlying XML system or implementation of JAXP failed unexpectedly.
Action: Check the nested exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-26121: A general MDS error has occurred.
Cause: An MDS-related error has occurred. Something with the MDS setup is misconfigured.
Action: Check the nested exception for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-26122: An MDS error has occurred because a Metadata Object by the name of {0} cannot be found.
Cause: An MDS Metadata Object was not found.
Action: Check the details of the Metadata Object and check the MDS repository to confirm that it is there.

Level: 1

Type: ERROR

Impact: Other

WCS-26123: Encountered "{0}" with message "{1}" when committing MDS changes.
Cause: Something within the current MDS Session cannot be committed.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26124: Saved Search Deletion aborted because the Metadata Object (MO) Reference for ID "{0}" is not found.
Cause: The system is in an inconsistent state allowing deletion of non-existent MDS documents
Action: There is nothing to be done about this. No deletion is performed.

Level: 1

Type: WARNING

Impact: Other

WCS-26125: Encountered "{0}" with message "{1}" while formulating the final MDS Condition.
Cause: Some MDS conditions that are being joined caused a failure to come up with the final condition.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26126: MDS query result is null
Cause: MDS query result set is null. The MDS repository might be unavailable.
Action: Perform the operation again after MDS repository becomes available again.

Level: 1

Type: ERROR

Impact: Other

WCS-26141: A configuration error has occurred for the Search service model. The offending configuration is {0}.
Cause: The Search service keeps its configuration in adf-config.xml, connections.xml, and MDS.
Action: Check in the appropriate configuration files to see if there are any obvious erroneous data.

Level: 1

Type: ERROR

Impact: Other

WCS-26142: A security error has occurred for the Search service model. The offense is {0}.
Cause: The Search service model security maintained by the service caused a failure.
Action: Check the security settings for each underlying service to identify any anomalies.

Level: 1

Type: ERROR

Impact: Other

WCS-26143: Failed to commit changes to Search preferences, encountering {0}.
Cause: Some underlying MDS issues with the Preferences implementation is causing the failure.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26144: An error occurred while parsing the default full crawl interval "{0}".
Cause: An internal error occurred while trying to instantiate a DatatypeFactory for parsing Duration values.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26145: An invalid full crawl interval "{0}" was specified in adf-config.xml.
Cause: The fullCrawlInterval attribute of the crawl-properties element in adf-config.xml may not be well-formed or valid.
Action: Make sure that the fullCrawlInterval attribute value is in the duration format as defined in the W3C XML Schema 1.0.

Level: 1

Type: WARNING

Impact: Other

WCS-26146: An invalid full crawl interval "{0}" was specified for service {1}.
Cause: The fullCrawlInterval attribute of a service-crawl-properties element in adf-config.xml may not be well-formed or valid.
Action: Make sure that the fullCrawlInterval attribute value is in the duration format as defined in the W3C XML Schema 1.0.

Level: 1

Type: WARNING

Impact: Other

WCS-26147: An error occurred while parsing the crawl-properties element in adf-config.xml.
Cause: An internal error occurred while trying to parse the crawl-properties element in adf-config.xml.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26161: Encountered a message from MDS indicating unsupported operation while deleting a Saved Search with ID "{0}", MO Reference name "{1}", and MO Absolute Name "{2}".
Cause: The deletion of a Saved Search triggered some MDS operation that is not supported on said Saved Search document.
Action: Contact Oracle Support Services

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26162: A saved search with name "{0}" already exists, use a different name.
Cause: The name you provided is used already.
Action: Use a different name when saving your searches.

Level: 1

Type: ERROR

Impact: Other

WCS-26163: Duplicated identifier found while adding a saved search with a identifier "{0}" with Metadata Object name "{1}"; replacing with "{2}".
Cause: The system is in an inconsistent state where an old ID is used on a new Saved Search.
Action: This is a cautionary message only. Appropriate actions will be taken to fix the uniqueness issue.

Level: 1

Type: WARNING

Impact: Other

WCS-26164: Encountered an MDS exception "{1}" with message "{2}" while querying for saved searches with condition "{0}".
Cause: An underlying MDS exception occurred during the query execution.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26165: Failed to retrieve a Saved Search in MDS with Metadata Object reference name "{0}", and absolute name "{1}".
Cause: This can be due to an MDS misconfiguration issue.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26166: Failed to retrieve most recent Saved Searches in MDS with Metadata Object reference name "{0}", and absolute name "{1}".
Cause: This can be due to an MDS misconfiguration issue.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26167: Encountered an MDS exception "{2}" with message "{3}" while saving a saved search with Metadata Object name "{0}", and absolute name "{1}".
Cause: This can be due to an MDS misconfiguration issue.
Action: Refer to MDS documentation to resolve a lookup failure with the given details.

Level: 1

Type: ERROR

Impact: Other

WCS-26168: Encountered an MDS exception "{2}" with message "{3}" while deleting a saved search with Metadata Object name "{0}", and absolute name "{1}".
Cause: An underlying MDS exception caused this.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26169: Encountered an MDS reference exception "{1}" with message "{2}" while retrieving Saved Search Metadata Object reference in MDS with Metadata Object absolute name "{0}".
Cause: An underlying MDS exception caused this.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26170: Saved Search Update aborted because the Metadata Object (MO) Reference for ID "{0}" is not found.
Cause: This can be due to an MDS misconfiguration issue.
Action: Refer to MDS documentation to resolve a lookup failure with the given details.

Level: 1

Type: WARNING

Impact: Other

WCS-26171: Encountered an MDS exception "{1}" with message "{2}" while creating a document with Metadata Object absolute name "{0}".
Cause: An underlying MDS exception caused this.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26181: Failed to retrieve UI Metadata in MDS with Metadata Object reference name "{0}", and absolute name "{1}".
Cause: This can be due to an MDS misconfiguration issue.
Action: Refer to MDS documentation to resolve a lookup failure with the given details.

Level: 1

Type: WARNING

Impact: Other

WCS-26182: Encountered an MDS exception "{2}" with message "{3}" while adding a UI Metadata with identifier "{0}" and Metadata Object name "{1}".
Cause: An underlying MDS exception caused this.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26183: Encountered an MDS exception "{1}" with message "{2}" while querying for UI Metadata with condition "{0}".
Cause: An underlying MDS exception caused this.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26184: Encountered an MDS reference exception "{1}" with message "{2}" while looking up UI Metadata Object reference in MDS with Metadata Object absolute name "{0}".
Cause: An underlying MDS exception caused this.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26185: Encountered an MDS exception "{0}" with message "{1}" while creating default service list in MDS.
Cause: An underlying MDS exception occurred during the creation of the service list in the Search UI Metadata.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26186: Encountered an MDS exception "{1}" with message "{2}" while updating UI Metadata Object in MDS with Metadata Object absolute name "{0}".
Cause: An underlying MDS exception occurred during the update of the Search UI Metadata.
Action: The update by this user will be lost. Refresh the page and continue.

Level: 1

Type: ERROR

Impact: Other

WCS-26201: Encountered "{2}" with message "{3}" when loading QueryManager Class "{0}" for service "{1}" in Extension Handler.
Cause: Any one of the possible exceptions resulting from loading a class using reflection occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26202: Search Extension Registry loading failed, encountering "{0}" with message "{1}".
Cause: There may be misconfiguration in the adf-config.xml file.
Action: Check your adf-config.xml to see if the Search extension registry is declared. Make sure that the version numbers match those specified in the documentation.

Level: 1

Type: ERROR

Impact: Other

WCS-26203: Cannot access children, encountering "{0}" with message "{1}".
Cause: Encountered a Search exception when trying to extract children executors from a Query Federator
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26204: Failed in creating a Row QueryHandler for "{0}", encountering "{1}" with message "{2}".
Cause: A run time or Search exception was encountered. This can be due to the creation process timing out or any service-specific creation failure.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26205: {0} occurred during the preparation of Query Handler with identifier "{1}".
Cause: The Query Handlers are prepared in parallel; the preparation failed because of underlying concurrency mechanism.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26206: Creation of Row QueryHandler did not complete within the time limit for executor {0}.
Cause: The time allowed to create a Row QueryHandler is not sufficient.
Action: If this problem is persistent, increase the value of prepareExecutionTimeoutMs parameter in adf-search-config section of adf-config.xml file.

Level: 1

Type: WARNING

Impact: Other

WCS-26207: Oracle Secure Enterprise Search (SES) is not configured. Search query cannot be executed.
Cause: Oracle Secure Enterprise Search (SES) is not configured.
Action: Oracle Secure Enterprise Search (SES) must be configured before search query can be executed.

Level: 1

Type: ERROR

Impact: Other

WCS-26221: Search execution was interrupted because of "{0}" with message "{1}".
Cause: The service search execution was interrupted because of a timeout or a failure.
Action: Examine the log to determine the root cause and take appropriate debugging steps.

Level: 1

Type: ERROR

Impact: Other

WCS-26222: Search execution failure for service "{0}", encountering "{1}" with message "{2}".
Cause: An exception occurred while executing search.
Action: Examine the log to determine the root cause and take appropriate debugging steps.

Level: 1

Type: ERROR

Impact: Other

WCS-26223: Search executors not initialized due to null Query.
Cause: Query is not set so no Query Executors have been initialized.
Action: No action is necessary; this is just a diagnostic message.

Level: 1

Type: WARNING

Impact: Other

WCS-26224: Query Handler creation of {0} was interrupted.
Cause: The Query Handler named took too long to be created and was timed out.
Action: Increase your prepareTimeoutMs value in the search-config section of the adf-config.xml file

Level: 1

Type: WARNING

Impact: Other

WCS-26225: {0} occurred during Search result transfer of service with identifier "{1}" with message "{2}"
Cause: An unexpected exception occurred when transferring search results after execution.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26226: Failed to extract Refiners from executor {0}.
Cause: Failure occurred when extracting refiners from the execution results of an executor.
Action: Inspect the failure message and fix accordingly.

Level: 1

Type: WARNING

Impact: Other

WCS-26227: Column not found for {0}
Cause: When formulating an query with a condition based on an attribute, the attribute is not found.
Action: Inspect your input and make sure that the values for the attributes are one of "name", "title", "description", "creator", "created", "modifier", "modified", and "tags".

Level: 1

Type: WARNING

Impact: Other

WCS-26228: Parsing of date operand "{0}" failed
Cause: When formulating an query with a condition based on a date attribute, the date value specified fails to be parsed.
Action: Inspect your date attribute and make sure that it follows the format: "yyyy-MM-dd"

Level: 1

Type: WARNING

Impact: Other

WCS-26229: Search query execution timed out for service "{0}".
Cause: The search query does not complete within the time limit.
Action: Re-try the search query again later.

Level: 1

Type: WARNING

Impact: Other

WCS-26281: getSessionVersion failed with Exception {0}
Cause: Operation to get Sessions Version from SES failed.
Action: Examine the log files to extract the root cause to identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26282: getAllFacets failed with Exception {0}
Cause: Operation to fetch allfacets from SES failed.
Action: Examine the log files to extract the root cause to identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26283: getAllAttributes failed with Exception {0}
Cause: Operation to fetch allattributes from SES failed.
Action: Examine the log files to extract the root cause to identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26284: getAllAttributes failed with Exception {0}
Cause: Operation to fetch all attributes from SES failed.
Action: Examine the log files to extract the root cause to identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26322: Skipping consumption of a Date ComplexPredicate with 1 child because its type {0} is not AttributePredicate<Calendar> as expected.
Cause: A Date ComplexPredicate was passed down from the query that contains the wrong type for its single child.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26323: Skipping consumption of a Date ComplexPredicate with 2 children because their types {0} and {1} are not AttributePredicate<Calendar> as expected.
Cause: A Date ComplexPredicate was passed down from the query that contains the wrong type for both its children.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26324: Skipping consumption of a Date ComplexPredicate with {0} children because we only support at most two.
Cause: Too many children are passed down the Date ComplexPredicate when we can only handle two.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26325: Execution of the search query to show all rows did not complete within the time limit for executor {0}.
Cause: The time allowed to execute the search query to show all rows is not sufficient.
Action: Increase the value of showAllExecutionTimeoutMs parameter in adf-search-config section of adf-config.xml file.

Level: 1

Type: ERROR

Impact: Other

WCS-26326: Execution of the search query did not complete within the time limit for executor {0}.
Cause: The time allowed to execute the search query is not sufficient.
Action: If this problem is persistent, increase the value of executionTimeoutMs parameter in adf-search-config section of adf-config.xml file.

Level: 1

Type: WARNING

Impact: Other

WCS-26327: Query execution failed for {0}.
Cause: Query execution failed.
Action: Examine the log files to extract the root cause to identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26328: Search failure: time out error
Cause: Search execution timed out.
Action: Examine the log files to extract the root cause to identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26329: Search failure: problem preparing search executor
Cause: Unable to create a search executor.
Action: Examine the log files to extract the root cause to identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26330: Search failure: problem with execution
Cause: Search execution problem.
Action: Examine the log files to extract the root cause to identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26331: Search failure: problem with adding refiner
Cause: Unable to add refiner.
Action: Examine the log files to extract the root cause to identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26332: Search failure: problem with removing refiner
Cause: Unable to remove refiner.
Action: Examine the log files to extract the root cause to identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26333: Search failure: problem with updating refiner
Cause: Unable to update the refiner.
Action: Examine the log files to extract the root cause to identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26341: Search UI Metadata Lookup Failed: {0}
Cause: The UI Metadata document necessary for rendering Search views could not be found.
Action: Refer to the error messages presented in the dialog box and act accordingly.

Level: 1

Type: ERROR

Impact: Other

WCS-26342: Search UI Metadata Update Failed: {0}
Cause: The UI Metadata document necessary for rendering Search views could not be updated (customized).
Action: Refer to the error messages presented in the dialog box and act accordingly.

Level: 1

Type: ERROR

Impact: Other

WCS-26343: Search Options Update Failed
Cause: An MDS error caused the update of search options to fail.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26361: Failed to update the last used date / time of saved search with ID "{0}".
Cause: An MDS error caused the update of the Saved Search document to fail when updating the last accessed date.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26362: Saved Search Update Failed
Cause: An error occurred when trying to update a Saved Search.
Action: Refer to the error messages presented in the dialog box and act accordingly.

Level: 1

Type: ERROR

Impact: Other

WCS-26363: Saved Search Creation Failed
Cause: An error occurred when trying to create a Saved Search.
Action: Refer to the error messages presented in the dialog box and act accordingly.

Level: 1

Type: ERROR

Impact: Other

WCS-26364: Saved Search Deletion Failed
Cause: An error occurred when trying to delete a Saved Search.
Action: Refer to the error messages presented in the dialog box and act accordingly.

Level: 1

Type: ERROR

Impact: Other

WCS-26365: Failed to delete saved search with ID "{0}".
Cause: An MDS error caused the deletion of the Saved Search document to fail.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26366: Failed to update the sharing setting of saved search with ID "{0}".
Cause: An MDS error caused the update of the Saved Search document to fail when updating the sharing setting.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26367: Saved search with ID "{0}" could not be found.
Cause: Saved search was deleted by another user.
Action: Refresh page to get updated list of saved searches.

Level: 1

Type: WARNING

Impact: Other

WCS-26381: Resource ID is not available to show the resource.
Cause: A link to render a resource did not carry the unique identifier for that resource and therefore could not perform the rendering.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26391: Encountered an exception "{2}" with message "{3}" while populating Data Flavor "{0}" of "{1}" class.
Cause: Failed to populate the given Data Flavor in the Resource Catalog Adapter.
Action: Examine the log for the root cause and take appropriate debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26392: Failed to initialize Search service context DirContext Schema with message "{0}"
Cause: A naming exception was encountered when binding attributes while initializing the Resource Catalog schema for the Search service.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26393: Failed to get attributes of resource "{0}"
Cause: Failed to get attributes of a given resource.
Action: Examine the log for the root cause and take appropriate debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26396: Search Box Size not a number - "{0}". Using Default size instead.
Cause: taskflow parameter passed to this component not an integer.
Action: Examine the taskflow parameter and replace value with a number.

Level: 1

Type: WARNING

Impact: Other

WCS-26397: Search Taskflow ID does not correspond to a valid taskflow. Using Default taskflow instead.
Cause: taskflow parameter passed to this component not a valid taskflow id.
Action: Examine the taskflow parameter and replace with appropriate value.

Level: 1

Type: WARNING

Impact: Other

WCS-26398: Search Scope ID parameter value is not a Scope object - "{0}".
Cause: taskflow parameter EL or value is not a Scope object
Action: Examine the taskflow parameter and replace value with a valid Scope object.

Level: 1

Type: WARNING

Impact: Other

WCS-26399: Service with service ID: "{0}" is not registered and cannot be included in Categories list.
Cause: Service Id is not a registered service.
Action: Have an administrator remove service from Services to be included list.

Level: 1

Type: WARNING

Impact: Other

WCS-26400: Locale or Service Registry not found.
Cause: Taskflow is not in an appropriate application or adf context was lost.
Action: Refresh page or place taskflow in appropriate template.

Level: 1

Type: WARNING

Impact: Other

WCS-26401: Encountered "{0}" during proxy login with application entity "{1}" to Oracle SES at [{2}], as search user "{3}".
Cause: The proxy login operation encountered error. Some underlying exception is causing the error.
Action: Refer to the root exception and identify the proper debugging steps.

Level: 1

Type: ERROR

Impact: Other

WCS-26402: Received status "{0}" during proxy login with application entity "{1}" to Oracle SES at [{2}], as search user "{3}". Defaulting to public.
Cause: The application entity may not have been provisioned in the identity management system used by SES, or its password may have been expired.
Action: Log on to the Oracle SES administration tool and make sure that the application entity has been provisioned. Then make sure that the account is enabled on the identity management system and has not expired.

Level: 1

Type: WARNING

Impact: Other

WCS-26403: Federation Trusted Entity parameters not configured. Search as public user on Oracle SES.
Cause: Federation Trusted Entity parameters not configured.
Action: Configure Federation Trusted Entity parameters.

Level: 1

Type: WARNING

Impact: Other

WCS-26421: Failed to initialize data group ID from {0} in {1}, encountering {2}
Cause: Either the group ID in question does not exist or SES is down.
Action: Make sure that SES is up and check the group IDs present on SES.

Level: 1

Type: WARNING

Impact: Other

WCS-26422: Failed to discover attributes from {0} in {1}, encountering {2}
Cause: Some underlying exception is causing the discovery of attributes from SES to fail.
Action: Refer to the root exception and identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26423: No attributes discovered from {0} in {1}
Cause: The SES instance in question does not offer any attributes to query on.
Action: Confirm that Oracle SES is up.

Level: 1

Type: WARNING

Impact: Other

WCS-26424: Failed to discover info source nodes from {0} in {1}, encountering {2}
Cause: Some underlying exception is causing the discovery of info source nodes of SES to fail.
Action: Refer to the root exception and identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26441: Retrieving the SES Reference failed with Connection Architecture
Cause: Something occurred when getReference of the SesReferenceable is called.
Action: Refer to the root exception and identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26442: Looking up the SES Connection failed with Connection Architecture
Cause: Encountered a JCA ResourceException when calling getConnection on the connection factory for Searchlets.
Action: Refer to the root exception and identify the proper debugging steps.

Level: 1

Type: WARNING

Impact: Other

WCS-26443: Connection entry "{0}" not found
Cause: The specified connection entry is not in connections.xml
Action: Add the specified connection entry to connections.xml

Level: 1

Type: ERROR

Impact: Other

WCS-26444: Invalid value for addrType attribute in "{1}" entry. Expected value is "{0}"
Cause: Incorrect value for addrType attribute found in connections.xml
Action: Update connections.xml with the correct value for addrType attribute

Level: 1

Type: ERROR

Impact: Other

WCS-26451: Failed to create an instance of class "{0}"
Cause: Failed creating an instance of the XML object representing an SES admin object.
Action: A RuntimeException would have been thrown to propagate the underlying Exception causing this. Please inspect the log to see what else can be done to fix the issue.

Level: 1

Type: WARNING

Impact: Other

WCS-26452: This command is not supported for the version of SES running on the target SES instance.
Cause: The version of SES running on the target SES instance does not support this command.
Action: This command requires SES 11.2.2.2.0 or later.

Level: 1

Type: ERROR

Impact: Other

WCS-26461: Failed to marshal SES Filter for Advanced Search due to JAXB issues - {0}
Cause: A JAXB problem has caused the marshalling of an SES filter before sending it to SES for execution.
Action: Examine the log to look at the XML structure to verify validity.

Level: 1

Type: WARNING

Impact: Other

WCS-26462: SES Search Execution failed, encountering "{0}" with message "{1}".
Cause: The cause is embedded in the Exception and can be SES-specific.
Action: Examine the log files to extract the root cause to identify the proper debugging steps.

Level: 1

Type: ERROR

Impact: Other

WCS-26463: Can not convert SES Result Element value from {0} to {1}
Cause: Conversion from SES Result Element value failed.
Action: No action is needed. The conversion will default to using String

Level: 1

Type: WARNING

Impact: Other

WCS-26464: Cannot find attribute mapping for column {0}
Cause: You have specified a column ID that cannot be found in the list of SES attributes.
Action: Examine your SES installation and make sure the attribute has a valid column ID.

Level: 1

Type: WARNING

Impact: Other

WCS-26465: Failed to create JAXBContext using package {0}
Cause: A JAXBContext instance could not be created for the SES cluster deserializer.
Action: Make sure that the required files can be found in the specified package and that the required classes can be loaded from the classpath.

Level: 1

Type: ERROR

Impact: Other

WCS-26466: Failed to unmarshal byte stream into Cluster
Cause: Unmarshalling failed because a JAXBContext instance could not be obtained.
Action: Make sure that the required files can be found in the specified package and that the required classes can be loaded from the classpath.

Level: 1

Type: WARNING

Impact: Other

WCS-26467: SES search query execution timed out - "{0}" with message "{1}".
Cause: The search query does not complete within the time limit.
Action: Re-try the search query again later.

Level: 1

Type: WARNING

Impact: Other

WCS-26468: Unable to determine whether primary search configuration is elasticsearch.
Cause: Review the underlying exception to determine the cause.
Action: Take action based on the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-26481: SearchCrawlExtension class is not found for service {0}
Cause: Portal crawler failed to introspect a Crawlable SPI implementation for the involved service, specified by a URL parameter indicating a crawler's intent to crawl said service. This theoretically should never happen because the URL that crawlers would use are all generated by the Search framework code when crawlers access the root feed that we provide. But if a crawler explicitly starts with a particular service, bypassing our root feed, this warning may result.
Action: Please check the potential crawling SES instances to make sure that there isn't a source that directly targets a service which has no Crawlable implementation.

Level: 1

Type: WARNING

Impact: Other

WCS-26491: The processing and preparing of the control feed for service {0} failed
Cause: The processing and preparing of the control feed for service {0} failed. This could mean that there is a fundamental error in the writing the feed content to the output stream which is to be returned to the caller of the URL.
Action: Most likely there is a network issue which may well be temporary. Restart the crawl again and see if the problem persists.

Level: 1

Type: ERROR

Impact: Other

WCS-26492: The processing and preparing of the data feed for service {0} failed
Cause: The processing and preparing of the data feed for service {0} failed. This could mean that there is a fundamental error in the writing the feed content to the output stream which is to be returned to the caller of the URL.
Action: Most likely there is a network issue which may well be temporary. Restart the crawl again and see if the problem persists.

Level: 1

Type: ERROR

Impact: Other

WCS-26493: No new entries to crawl for service {0}
Cause: There are no items to crawl for the service
Action: This is expected if there are no items available for crawl. If on the contrary, there are artifacts pertaining to this service, then try scheduling crawl again.

Level: 1

Type: WARNING

Impact: Other

WCS-26501: Creation of the Tags service failed.
Cause: The Tags service is loaded by reflection. Something may have happened to cause that to fail.
Action: Check whether the class name logged is accessible through the class path of the WebCenter Web application.

Level: 1

Type: ERROR

Impact: Other

WCS-26502: Query Federator for the Tags service not created because a Tags Service cannot be created.
Cause: The creation of the Tags service was unsuccessful causing the subsequent creation of a Row Query Federator for Tagging to fail.
Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.

Level: 1

Type: ERROR

Impact: Other

WCS-26503: findSystemResources failed because of invalid arguments passed in to the method: keywords ({0}).
Cause: One of the input arguments to findSystemResources was invalid.
Action: Make sure that arguments passed in to findSystemResources are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26504: findSystemTags failed because of invalid arguments passed in to the method: keywords ({0}).
Cause: One of the input arguments to findSystemResources was invalid.
Action: Make sure that arguments passed in to findSystemTags are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26505: lookupTag failed because of invalid arguments passed in to the method: tagName ({0}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26506: findFilteredPersonalTags failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26507: findTopFilteredSystemTags failed because of invalid arguments passed in to the method:userId({0}), filter ({1}), count({2}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26508: findTopFilteredPersonalTags failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}), count({3}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26509: findAllTopFilteredSystemTags failed because of invalid arguments passed in to the method:userId({0}), filter({1}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26510: findAllTopFilteredPersonalTags failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26511: findSystemTags failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26512: findRelatedSystemTagsByTag failed because of invalid arguments passed in to the method: userId ({0}), tagWords ({1}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26513: findRelatedSystemTags failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId({1}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26514: findRecommendedTags failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}), userId ({2}), count ({3}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26515: deleteTag failed because of invalid arguments passed in to the method: tag ({0}).
Cause: One of the input arguments is invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26516: deletePersonalTags failed because of invalid arguments passed in to the method: userId ({0}), tagWord ({1}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26517: renamePersonalTags failed because of invalid arguments passed in to the method: userId ({0}), oldTagWord ({1}) newTagWord({2}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26518: renamePersonalTags failed because of invalid arguments passed in to the method: userId ({0}), tagWord ({1}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26519: getTagsByName failed because of invalid arguments passed in to the method: userId ({0}), tagWord ({1}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26520: lookupResource failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId({1}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26521: createNewResource failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}), resource name ({2}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26522: findFilteredPersonalResource failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26523: findSystemResources failed because of invalid arguments passed in to the method: userId ({0}), userFilters ({1}), tagFilters ({2}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26524: findPersonalResources failed because of invalid arguments passed in to the method: userId ({0}), userFilters ({1}), tagFilters ({2}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26525: findRelatedSystemResources failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26526: findRelatedUsers failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}).
Cause: One of the input arguments is invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26527: findRelatedUsersByTag failed because of invalid arguments passed in to the method: userId({0}), tagWords ({1}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26528: createNewBookmark failed because of invalid arguments passed in to the method: userId ({0}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26529: lookupBookmark failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}, userId ({2}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26530: saveBookmark failed because of invalid arguments passed in to the method: bookmark ({0}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26531: deleteBookmark failed because of invalid arguments passed in to the method: bookmark ({0}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26532: A bookmark has been updated at the same time.
Cause: There was a concurrent update on the bookmarks.
Action: Ask user to retry the operation.

Level: 1

Type: ERROR

Impact: Other

WCS-26533: A database exception was thrown (for example., Unique Key constraint violation error).
Cause: Tried to insert a duplicate object.
Action: Retry the action.

Level: 1

Type: ERROR

Impact: Other

WCS-26534: Resource can not be displayed because the service with ID {0} is not found in the Service Registry.
Cause: Service definition is not found in Service Registry.
Action: Please register the service in Service Registry

Level: 1

Type: ERROR

Impact: Other

WCS-26535: Tags service is not available due to {0}.
Cause: Check the cause specified in the message.
Action: Act appropriately to reverse the cause.

Level: 1

Type: ERROR

Impact: Other

WCS-26536: Resource can not be displayed because the authorizerClass {0} is not found.
Cause: Class specified by authorizerClass is not found.
Action: Check the class path of the application to verify inclusion of the authorizerClass.

Level: 1

Type: WARNING

Impact: Other

WCS-26537: findPopularTags failed because of invalid arguments passed in to the method: userId ({0}), order ({1}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26538: findPopularTags failed because of invalid arguments passed in to the method: userId ({0}), serviceId ({1}), resourceId ({2}).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26539: findUpdatedResources failed because of invalid arguments passed in to the method: serviceId ({0}), date ({1})).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26540: getTags failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1})).
Cause: One of the input arguments was invalid.
Action: Make sure that arguments passed in are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26541: Error encountered while publishing to activity stream due to {0}.
Cause: Error caused by Activity Stream
Action: Turn on the logging to finest to check the exception detail.

Level: 1

Type: ERROR

Impact: Other

WCS-26542: Error encountered while retrieving user profile due to {0}.
Cause: Error caused by Profile server
Action: Turn on the logging to finest to check the exception detail.

Level: 1

Type: ERROR

Impact: Other

WCS-26543: Error encountered while renaming personal tags.
Cause: The creation of the Tagging Service failed or input arguments were invalid
Action: Turn on the logging to finest to check the exception detail.

Level: 1

Type: ERROR

Impact: Other

WCS-26544: Error encountered while deleting personal tags.
Cause: The creation of the Tagging Service failed or input arguments were invalid
Action: Turn on the logging to finest to check the exception detail.

Level: 1

Type: ERROR

Impact: Other

WCS-26545: Error encountered while finding personal tags.
Cause: The creation of the Tagging Service failed or input arguments were invalid
Action: Turn on the logging to finest to check the exception detail.

Level: 1

Type: ERROR

Impact: Other

WCS-26546: Error encountered while finding personal resources.
Cause: The creation of the Tagging Service failed or input arguments were invalid
Action: Turn on the logging to finest to check the exception detail.

Level: 1

Type: ERROR

Impact: Other

WCS-26547: saveBookmark callback failed for service {0}.
Cause: The specified service encountered an internal error.
Action: Make sure that the service is configured correctly and that arguments passed in are all valid.

Level: 1

Type: WARNING

Impact: Other

WCS-26548: service-definition.xml requires a resource-type element and one or more object-type elements.
Cause: The service-definition.xml does not have the appropriate components.
Action: Add a resource-type and an object type to the service-definition.xml

Level: 1

Type: WARNING

Impact: Other

WCS-26601: No service ID or resource ID - cannot perform {0}.
Cause: The consumption of the EditBookmarkBean from the view layer did not pass in the service or the resource IDs necessary.
Action: Check the view layer to make sure that the resourceId and the serviceId parameters are passed into the page flow scope.

Level: 1

Type: ERROR

Impact: Other

WCS-26602: Cannot create a recommended list because the Tags service cannot be created.
Cause: The creation of the Tags service was unsuccessful, so the recommended list could not be created.
Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.

Level: 1

Type: ERROR

Impact: Other

WCS-26603: Bookmark cannot be loaded because Tags service cannot be created.
Cause: The creation of the Tags service was unsuccessful, so the bookmark object could not be created.
Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.

Level: 1

Type: ERROR

Impact: Other

WCS-26604: Bookmark saving failed because a Tags service cannot be created.
Cause: The creation of the Tags service was unsuccessful, so the bookmark could not be saved.
Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.

Level: 1

Type: ERROR

Impact: Other

WCS-26605: lookupBookmark failed because of invalid arguments passed in to the method: service ID ({0}), resource ID ({1}), and user ID ({2}).
Cause: One of the input arguments to lookupBookmark was invalid.
Action: Make sure that arguments passed in to lookupBookmark are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26606: createBookmark failed because of invalid arguments passed in to the method: service ID ({0}), resource ID ({1}), resource name ({2}), and user ID ({3}).
Cause: One of the input arguments to createBookmark was invalid.
Action: Make sure that arguments passed in to createBookmark are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26607: findRecommendedTags failed because of invalid arguments passed in to the method: service ID ({0}), resource ID ({1}), and user ID ({2}).
Cause: One of the input arguments to findRecommendedTags was invalid.
Action: Make sure that arguments passed in to findRecommendedTags are all valid.

Level: 1

Type: ERROR

Impact: Other

WCS-26608: This item has been tagged by the same user at the same time. Re-apply your changes.
Cause: Concurrent update on the bookmarks.
Action: Retry the action.

Level: 1

Type: WARNING

Impact: Other

WCS-26609: Some items whose tags are to be renamed have been updated at the same time. Re-apply your changes.
Cause: Concurrent update on the bookmarks.
Action: Retry the action.

Level: 1

Type: WARNING

Impact: Other

WCS-26610: Some items whose tags are to be deleted have been updated at the same time. Re-apply your changes.
Cause: Concurrent update on the bookmarks.
Action: Retry the action

Level: 1

Type: WARNING

Impact: Other

WCS-26611: Tagging Button or Tagging Menu Item will not be rendered because the region "tagging-launch-dialog" is not included in the page.
Cause: While building the page, the tagging button was added without adding a corresponding popup task flow.
Action: Check to make sure the "tagging-launch-dialog" region is indeed included in the page.

Level: 1

Type: WARNING

Impact: Other

WCS-26612: The tagging component "{0}" was not rendered because the underlying Tags service was not available.
Cause: The underlying Tags service was not available.
Action: Look for the errors causing the underlying Tags service to not be available and fix them.

Level: 1

Type: WARNING

Impact: Other

WCS-26613: Error encountered while renaming personal tags.
Cause: The creation of the Tagging Service failed or input arguments were invalid
Action: Turn on the logging to finest to check the exception detail.

Level: 1

Type: ERROR

Impact: Other

WCS-26614: Error encountered while deleting personal tags.
Cause: The creation of the Tagging Service failed or input arguments were invalid
Action: Turn on the logging to finest to check the exception detail.

Level: 1

Type: ERROR

Impact: Other

WCS-26615: Error encountered while finding personal tags.
Cause: The creation of the Tagging Service failed or input arguments were invalid
Action: Turn on the logging to finest to check the exception detail.

Level: 1

Type: ERROR

Impact: Other

WCS-26616: Error encountered while finding personal resources.
Cause: The creation of the Tagging Service failed or input arguments were invalid
Action: Turn on the logging to finest to check the exception detail.

Level: 1

Type: ERROR

Impact: Other

WCS-26617: Error encountered while updating resource with serviceId: {0} resourceId:{1} and resourceName:{2}.
Cause: There was a problem saving the updated resource.
Action: Turn on the logging to finest to check the exception detail.

Level: 1

Type: ERROR

Impact: Other

WCS-26618: This item has been deleted by another user while being tagged. Refresh this page.
Cause: Resource was deleted while being tagged.
Action: Retry the action.

Level: 1

Type: WARNING

Impact: Other

WCS-26621: EncodeBegin error for TaggingPopup tag
Cause: Catastrophic error
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-26622: Error in Tagging Button tag usage - component {0} has attribute {1} whose value is {2}.
Cause: The attribute mentioned in the error cannot be null, but no value was found for this attribute.
Action: Correct your tag usage.

Level: 1

Type: WARNING

Impact: Other

WCS-26623: Component {0} does not support client listeners.
Cause: Tried to add a client listener to a component that does not support client listeners.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26701: Could not determine if primary search configuration is Elasticsearch.
Cause: Review the underlying exception to determine the cause.
Action: Take action based on the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-26702: Invalid query string {0}, returning empty results.
Cause: The query string for searching is probably empty or null.
Action: Ensure you give a valid search query string.

Level: 1

Type: WARNING

Impact: Other

WCS-26703: Invalid JSON query format {0}.
Cause: Review the underlying exception to determine the cause.
Action: Take action based on the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-26704: Invalid Search Response {0}.
Cause: Review the response received and determine the cause.
Action: Take action based on the response received.

Level: 1

Type: WARNING

Impact: Other

WCS-26705: Connection failure while obtaining search result.
Cause: Review the underlying exception to determine the cause.
Action: Take action based on the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-26706: Unsupported search facet {0}.
Cause: Review the underlying exception to determine the cause.
Action: Take action based on the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-26707: Could not obtain search provider factory.
Cause: Review the underlying exception to determine the cause.
Action: Take action based on the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-26708: Crawl failed for service {0}.
Cause: Review the underlying exception to determine the cause.
Action: Take action based on the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-26709: No records to crawl for service {0}.
Cause: There is no data to crawl for the given service.
Action: No action required. If the service does have some data, then review the logs for any other exceptions that might explain why service data is not getting crawled.

Level: 1

Type: WARNING

Impact: Other

WCS-26710: Could not determine last crawled time for service {0} while performing partial crawl, performing full crawl therefore.
Cause: Full crawl has not been run on service data yet.
Action: Full crawl needs to be performed before partial crawl.

Level: 1

Type: WARNING

Impact: Other

WCS-26711: Invalid Crawl source {0}.
Cause: Crawling not supported for the given source.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26712: Type and mapping creation failed for service {0} with response {1}.
Cause: Review the underlying exception to determine the cause.
Action: Take action based on the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-26713: Elasticsearch is not configured, crawl no-op for type {0}.
Cause: Elasticsearch is not configured.
Action: Ensure you have configured Elasticsearch for the application.

Level: 1

Type: WARNING

Impact: Other

WCS-26714: No new entries to crawl for service {0}.
Cause: There are no items to crawl for the service.
Action: This is expected if there are no items available for crawl. If on the contrary, there are artifacts pertaining to this service, then try scheduling crawl again.

Level: 1

Type: WARNING

Impact: Other

WCS-26715: Failure to set last crawled time for service {0}.
Cause: Review the underlying exception for the cause.
Action: Take action based on the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-26716: Error occurred while obtaining MBean server connection.
Cause: Review the underlying exception for the cause.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26717: Crawler source is null.
Cause: The crawler source object passed is null.
Action: Ensure that you have passed non-null object.

Level: 1

Type: WARNING

Impact: Other

WCS-26718: Crawler source type is null.
Cause: The crawler source type object passed is null.
Action: Ensure that you have passed non-null object.

Level: 1

Type: WARNING

Impact: Other

WCS-26719: Error occurred while obtaining the details of external application connection {0}.
Cause: Review the underlying exception for the cause.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26720: Error occurred while obtaining external application connections.
Cause: Review the underlying exception for the cause.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26721: Error occurred while creating external application connection {0}.
Cause: Review the underlying exception for the cause.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26722: Error occurred while saving external application connection {0}.
Cause: Review the underlying exception for the cause.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26723: Error occurred while looking up external application connection {0}.
Cause: Review the underlying exception for the cause.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26724: Error occurred while editing external application connection {0}.
Cause: Review the underlying exception for the cause.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26725: Error occurred while setting credentials for external application connection.
Cause: Review the underlying exception for the cause.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26726: Crawler schedule is null.
Cause: The crawler schedule object passed is null.
Action: Ensure that you have passed non-null object.

Level: 1

Type: WARNING

Impact: Other

WCS-26727: Error occurred while creating/updating the crawler schedule for source: {0}.
Cause: Review the underlying exception for the cause.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26728: Error occurred while updating crawler schedule for source: {0}, status: {1}.
Cause: Review the underlying exception for the cause.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26729: Crawler schedule not found for source: {0}.
Cause: Review the underlying exception for the cause.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26730: Error occurred while executing the crawler for type: {0}.
Cause: Review the underlying exception for the cause.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26731: Error occurred while enabling crawler source: {0}.
Cause: Review the underlying exception for the cause.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26732: Error occurred while getting crawler schedule for source: {0}.
Cause: Review the underlying exception for the cause.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-26733: Crawler is executing for source: {0}.
Cause: Trying to perform an operation which is not supported while crawler is executing.
Action: Ensure that you perform the operation once the crawler execution is complete.

Level: 1

Type: WARNING

Impact: Other

WCS-26734: Create Mapping failed for type {0} due to {1}.
Cause: Creating mapping in Elasticsearch failed due to reason mentioned.
Action: Review the cause and take action based on that. Run crawl again.

Level: 1

Type: WARNING

Impact: Other

WCS-26735: Search connection configured is not of type Elasticsearch. Unexpected response {0} received.
Cause: Unexpected response received while trying to determine if search connection configured is elastic.
Action: If your search is SES based, ignore this warning. Otherwise review the cause and take action based on that. Restart the Portal Server afterwards.

Level: 1

Type: WARNING

Impact: Other

WCS-26736: Primary Search Connection URL {0} or index {1} not configured.
Cause: Search connection URL or search index is not configured
Action: Configure the search connection and properties and retry.

Level: 1

Type: WARNING

Impact: Other

WCS-26737: Error occurred while trying to fetch search attributes for service {1}
Cause: Review the underlying exception for the cause
Action: Take action based on the underlying exception

Level: 1

Type: WARNING

Impact: Other

WCS-26738: Error occurred while trying to fetch all search attributes configured
Cause: Review the underlying exception for the cause
Action: Take action based on the underlying exception

Level: 1

Type: WARNING

Impact: Other

WCS-26739: Search Attribute {0} was found to be different to {1}. Search Attributes with same name cannot be different.
Cause: Search Attributes with same name cannot be different.
Action: Follow documentation and ensure that search attributes with same name are similar in their attributes.

Level: 1

Type: WARNING

Impact: Other

WCS-26740: Attribute {0} is missing in the configured search attributes for service {1}
Cause: Search Attribute is missing in the search-service-attributes.xml which is used to create Elasticsearch mappings and to display custom attributes in search screens.
Action: Follow documentation and add the missing attribute in the MDS repository.

Level: 1

Type: WARNING

Impact: Other

WCS-26741: Exception while fetching user attributes for Discussions for user: {0}.
Cause: Could not fetch Security Attributes from Discussions Crawler Schema.
Action: Could not fetch Security Attributes.

Level: 1

Type: WARNING

Impact: Other

WCS-26742: Discussions Service is not configured.
Cause: Discussions Service is not configured.
Action: Discussions Service is not configured.

Level: 1

Type: WARNING

Impact: Other

WCS-26743: Exception while fetching partial crawl data.
Cause: Failed to parse last crawl time : {0}.
Action: Could not fetch data for partial crawl.

Level: 1

Type: WARNING

Impact: Other

WCS-26744: Failed to create Elasticsearch index: {0}. Response code: {1}.
Cause: Review the underlying exception to determine the cause.
Action: Take action based on the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-26745: Authorization error while creating Elasticsearch index: {0}.
Cause: Review the underlying exception to determine the cause.
Action: Take action based on the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-26746: Error occurred while creating Elasticsearch index: {0}. Response code: {1}.
Cause: Review the underlying exception to determine the cause.
Action: Take action based on the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-26747: Could not create elastic search index for source {0}
Cause: Review the underlying exception to determine the cause.
Action: Take action based on the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-26748: Deleting index failed for {0} due to {1}
Cause: Review the underlying exception to determine the cause.
Action: Take action based on the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-26749: Index {0} already exists, therefore not creating it.
Cause: The index already exists
Action: Specify a different alias. If you wish to recreate the index, then delete the said index and retry.

Level: 1

Type: WARNING

Impact: Other

WCS-28701: Unable to retrieve portlet parameters.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-28702: Error updating page definition
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-28703: Null page definition
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-28704: Page Definition not found for the page: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-28706: Task flow binding not found for component with id: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-28707: Parameter {0} of component {1} has not been wired with any event payload
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-28709: Event {0} could not be resolved for region {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-28710: Binding for taskflow {0} could not be resolved in region {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-28711: Parameter {0} of component {1} has no mapping information for event {2}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-28712: Unable to get Region Parameters.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-28713: Wiring information for parameter {0} of component {1} having expression {2} could not be read
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-28714: Pre-existing wiring information for parameter {0} of component {1} having expression {2} could not be set
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-28715: Binding resolver for component "{0}" having id "{1}" could not be found
Cause: There was an error in instantiating a suitable binding resolver for the selected component.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-28716: Wiring information for parameter "{0}" could not be reset.
Cause: Wiring information for parameter could not be reset.
Action: Go to page definition of the page and assign a empty EL expression to the parameter

Level: 1

Type: WARNING

Impact: Other

WCS-35006: cannot load metadata from XML node
Cause: The content of the data-control file (.dcx) might be invalid.
Action: Verify that the content in the data-control file (.dcx) is valid.

Level: 1

Type: ERROR

Impact: Other

WCS-35008: Login failed.
Cause: The specified user credentials were invalid.
Action: Provide valid user credentials.

Level: 1

Type: ERROR

Impact: Other

WCS-35013: missing method parameters
Cause: The data-control operation was invoked without any parameters.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35016: Retrieving data-control definition from runtime data-control object returned null.
Cause: The ADF framework did not set the data-control definition within the runtime data control.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35300: Parameters for the operation are missing.
Cause: The ADF framework passed a null parameter map to the data-control operation.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35301: The path parameter is not correct.
Cause: The path string that was specified was not a valid JCR repository path.
Action: Verify that the specified path string is a valid path in the content repository, and that it starts with /.

Level: 1

Type: ERROR

Impact: Other

WCS-35302: The type parameter is not correct.
Cause: The type string that was specified was not a valid node type in the JCR repository.
Action: Make sure the type specified is valid in the content repository on which the data control is based. Both the prefix and the local name should be valid. For example, nt:file and nt:folder are valid types.

Level: 1

Type: ERROR

Impact: Other

WCS-35303: cannot generate XPath query
Cause: The parameters that were given in the search operation could not be resolved into a valid XPath query string using the content repository session.
Action: Ensure the attribute names and prefixes used in the parameters are valid and registered in the JCR repository.

Level: 1

Type: ERROR

Impact: Other

WCS-35304: incorrect attribute {0} specified in the predicate
Cause: The specified attribute was not found in the repository.
Action: Provide a valid attribute name.

Level: 1

Type: ERROR

Impact: Other

WCS-35305: incorrect prefix for the attribute {0} in the predicate
Cause: The namespace that was used in the attribute was not correct or not registered in the JCR repository.
Action: Provide a valid prefix, or report the problem to the provider of the JCR adapter used with the repository.

Level: 1

Type: ERROR

Impact: Other

WCS-35306: cannot resolve attribute {0} using the repository session
Cause: An invalid attribute or an unregistered prefix was used in the JCR session.
Action: Provide a valid attribute name in the JCR repository session.

Level: 1

Type: ERROR

Impact: Other

WCS-35307: operator {0} not supported
Cause: An invalid operator was specified.
Action: Specify a valid operator.

Level: 1

Type: ERROR

Impact: Other

WCS-35309: The XPath query {0} is not supported by the JCR adapter.
Cause: The JCR adapter might not have been compliant with the XPath support that is required to work with the Content Repository data control.
Action: Verify that the XPath query is supported by this JCR adapter.

Level: 1

Type: ERROR

Impact: Other

WCS-35310: error in the JCR repository
Cause: An error occurred in the JCR adapter.
Action: Check the exception's cause and JCR adapter's error log.

Level: 1

Type: ERROR

Impact: Other

WCS-35311: error getting the item's URL
Cause: An error occurred while generating the URL for an item.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35312: invalid return attribute name {0}
Cause: An invalid Java name was entered. The name of a return attribute must be a valid Java name and must be different from "name", "URL", "path" and "primaryType".
Action: Verify that the attribute name is valid and is not "name", "URL", "path" and "primaryType".

Level: 1

Type: ERROR

Impact: Other

WCS-35313: invalid return attribute type
Cause: An invalid return attribute type was specified. Return attributes must be one of the following JCR types: Boolean, Integer, Double, String, or Date.
Action: Specify a valid return attribute type.

Level: 1

Type: ERROR

Impact: Other

WCS-35314: cannot get value for attribute {0}
Cause: The value for the specified attribute could not be retrieved from the JCR node.
Action: Verify that the JCR path for the attribute is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-35501: No repository was set in the environment.
Cause: No repository was specified for this resource.
Action: Specify a repository to use in creating the resource.

Level: 1

Type: ERROR

Impact: Other

WCS-35502: could not log on to the content repository
Cause: There was a problem logging on to the content repository.
Action: Verify that the connection and credentials are defined correctly and that the repository is accessible.

Level: 1

Type: ERROR

Impact: Other

WCS-35503: An error occurred while accessing the content repository.
Cause: There was a problem accessing the content repository.
Action: Verify that the content repository is accessible.

Level: 1

Type: ERROR

Impact: Other

WCS-35504: An error occurred while trying to close the connection.
Cause: Could not close the content repository connection.
Action: Verify that the connection is still available, and try to close it again.

Level: 1

Type: ERROR

Impact: Other

WCS-35505: Item {0} is not a file or folder.
Cause: An item was specified that is not a file or folder.
Action: Specify an item that is either a file or a folder.

Level: 1

Type: ERROR

Impact: Other

WCS-35506: Item {0} does not exist.
Cause: An item was specified that does not exist.
Action: Verify that the specified item exists.

Level: 1

Type: ERROR

Impact: Other

WCS-35507: unknown control type: {0}
Cause: An unknown control type was specified.
Action: Specify a known control type.

Level: 1

Type: ERROR

Impact: Other

WCS-35508: {0} does not name a ContentDirContext.
Cause: An item was specified that is not a ContentDirContext.
Action: Verify that the item specified is a ContentDirContext.

Level: 1

Type: ERROR

Impact: Other

WCS-35509: invalid search operation: {0}
Cause: An unrecognized search operation was specified.
Action: Use only recognized search operations.

Level: 1

Type: ERROR

Impact: Other

WCS-35510: unable to generate schema
Cause: An error occurred while adding attributes to the schema.
Action: Make sure the schema attributes are defined properly and are not already bound.

Level: 1

Type: ERROR

Impact: Other

WCS-35511: unable to create DataFlavor
Cause: An error occurred while trying to create a DataFlavor from the given MIME type.
Action: Make sure the MIME type is valid and non-null, and that any referenced classes can be loaded.

Level: 1

Type: WARNING

Impact: Other

WCS-35513: unable to create TaskFlowDescriptor
Cause: An error occurred while trying to create a TaskFlowDescriptor object.
Action: Make sure the required classes are in the classpath.

Level: 1

Type: ERROR

Impact: Other

WCS-35514: This feature is only available in a design environment.
Cause: A call to a design time only feature was made from run time.
Action: Do not call this method from run time code.

Level: 1

Type: ERROR

Impact: Other

WCS-35515: Error getting information for connection {0}. The connection will be skipped in the resource catalog.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-35516: This factory cannot be used at design time.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-35517: Not a valid content URL: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-35518: Error getting information for node ID {0}. This node will be skipped in the resource catalog.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-35900: Illegal value state, cannot read a value previously streamed.
Cause: The application mixed calls to getStream() and other get* accessors on the same value object.
Action: Verify your application code.

Level: 1

Type: ERROR

Impact: Other

WCS-35901: Illegal value state, cannot stream a value previously read.
Cause: The application mixed calls to getStream() and other get* accessors on the same value object.
Action: Verify your application code.

Level: 1

Type: ERROR

Impact: Other

WCS-35902: Error in value conversion (source type = {0}, target type = {1}).
Cause: The JCR values could not be converted to the specified type; the source and target type may not be compatible.
Action: Verify the value conversion rules defined in the JCR specification.

Level: 1

Type: ERROR

Impact: Other

WCS-35903: Error in value conversion (invalid ISO8601 string).
Cause: The specified string was not a valid ISO8601 string as specified by JCR and therefore could not be converted to a date.
Action: Verify the format of the date string.

Level: 1

Type: ERROR

Impact: Other

WCS-35904: Cannot create REFERENCE values.
Cause: Values of type REFERENCE are not supported by this JCR repository.
Action: Avoid using properties of type REFERENCE in your application.

Level: 1

Type: WARNING

Impact: Other

WCS-35905: Input/Output error while reading the binary stream.
Cause: The data for the binary property could not be accessed.
Action: Verify that the storage medium for the JCR repository is accessible.

Level: 1

Type: WARNING

Impact: Other

WCS-35906: UTF8 encoding not supported on this JVM
Cause: The JVM does not support UTF-8 encoding.
Action: Use a supported Java 5 compliant JVM.

Level: 1

Type: WARNING

Impact: Other

WCS-35907: This iterator does not contain any more elements.
Cause: The iterator has exhausted all its elements.
Action: Check the usage of the RangeIterator by your application.

Level: 1

Type: WARNING

Impact: Other

WCS-35908: This iterator does not support the remove operation.
Cause: The remove() operation is not supported on this iterator.
Action: Avoid making calls to RangeIterator#remove() in your application.

Level: 1

Type: WARNING

Impact: Other

WCS-35909: The item at path {0} is not a node.
Cause: An item was found at the specified path but it was not a node.
Action: Check that your application is specifying the correct path.

Level: 1

Type: WARNING

Impact: Other

WCS-35910: "{0}" is not a known namespace prefix.
Cause: The name or path contained a namespace prefix unknown to this repository.
Action: Check the namespace mappings in the current session.

Level: 1

Type: WARNING

Impact: Other

WCS-35911: "{0}" is not a known namespace URI.
Cause: The repository did not recognize the specified namespace URI.
Action: Check the set of namespaces allowed by the current repository.

Level: 1

Type: WARNING

Impact: Other

WCS-35912: The prefix "{0}" is already used.
Cause: The specified prefix was already mapped to a namespace and could not be remapped.
Action: Change the prefix mapping for the URI associated with that prefix before mapping it to another URI.

Level: 1

Type: WARNING

Impact: Other

WCS-35913: {0} is a reserved namespace prefix and cannot be remapped
Cause: The "xml" prefix could not be remapped as it is reserved by JCR.
Action: Check that your application is not trying to remap the "xml" prefix.

Level: 1

Type: WARNING

Impact: Other

WCS-35914: Namespace prefix remapping is not permitted
Cause: Could not remap the namespace as the JCR repository does not permit persistent namespace remapping.
Action: Use the session for any namespace remapping requirements.

Level: 1

Type: WARNING

Impact: Other

WCS-35915: Invalid JCR name or path: {0}
Cause: The name or path specified was not a valid JCR name or path.
Action: Check that the name or path uses valid namespace prefixes and satisfies the JCR grammar rules for names and paths.

Level: 1

Type: WARNING

Impact: Other

WCS-35916: Cannot append an absolute Path
Cause: Could not append an absolute path to the existing path.
Action: Make sure that the appended path is always relative.

Level: 1

Type: WARNING

Impact: Other

WCS-35918: Unexpected error while accessing node type
Cause: An unexpected error occurred while accessing a node type.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-35919: No such node type: {0}
Cause: The node type specified was unknown to the JCR repository.
Action: Ensure that your are using correct node types for this repository.

Level: 1

Type: WARNING

Impact: Other

WCS-35920: Not a supported query language: {0}
Cause: The query language specified was a not a supported query language; this repository only supports XPath.
Action: Make sure you use only XPath queries.

Level: 1

Type: WARNING

Impact: Other

WCS-35921: Saved queries are not supported.
Cause: Could not save the query as this repository does not support saved queries.
Action: Ensure that your application does not call unsupported JCR functionality.

Level: 1

Type: WARNING

Impact: Other

WCS-35922: Incorrect XPath expression
Cause: Could not recognize the XPath expression specified as it is not supported by this JCR repository.
Action: Check that your XPath query conforms to the JCR specification.

Level: 1

Type: WARNING

Impact: Other

WCS-35923: XPath expression error: invalid enumeration value.
Cause: An internal data structure used an invalid value.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35924: XPath expression error: invalid expression tree.
Cause: The XPath expression specified was not recognized as it is not supported by this JCR repository.
Action: Check that your XPath query conforms to the JCR specification.

Level: 1

Type: WARNING

Impact: Other

WCS-35925: Error while generating XML representation of expression tree
Cause: Could not create an XML representation of this expression tree.
Action: Check the exception stack trace for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-35926: Invalid xpath expression.
Cause: The XPath expression specified was not recognized as it is not supported by this JCR repository.
Action: Check that your XPath query conforms to the JCR specification.

Level: 1

Type: WARNING

Impact: Other

WCS-35927: Invalid qualified name: {0}
Cause: The specified XPath expression contained an invalid qualified name.
Action: Check that your XPath query conforms to the JCR specification.

Level: 1

Type: WARNING

Impact: Other

WCS-35928: Unexpected error during XML export.
Cause: There was an XML processing error while performing an XML export operation.
Action: Check that you are using Oracle XML parser v2.

Level: 1

Type: WARNING

Impact: Other

WCS-35930: Index out of bound while accessing path
Cause: The specified index for a path element was not valid.
Action: Check your use of the path object.

Level: 1

Type: WARNING

Impact: Other

WCS-35988: FOTY0012: argument node does not have a typed value
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-35989: XPST0010: The query uses an axis that is not supported by the query engine.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-35990: XPST0081: A QName used in the expression contains a namespace prefix that cannot be expanded into a namespace URI by using the statically known namespaces.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-35991: "{0}" is not a valid expression for use as a search string with jcr:contains().
Cause: The specified full text search expression was not a valid argument for jcr:contains().
Action: Check the full text search expression syntax defined in the JCR specification.

Level: 1

Type: WARNING

Impact: Other

WCS-35992: "{0}" is not a valid expression for use as a search string with jcr:like().
Cause: The specified regular expression was not a valid argument for jcr:like().
Action: Check the regular expression syntax defined in the JCR 1.0 specification.

Level: 1

Type: WARNING

Impact: Other

WCS-35993: This XPath expression contains constructs that are not supported by this query engine.
Cause: Could not execute this XPath query as it contained constructs that were not supported by this repository.
Action: Check that your XPath query conforms to the JCR specification.

Level: 1

Type: WARNING

Impact: Other

WCS-35994: XPTY0004: It is a type error if, during the static analysis phase, an expression is found to have a static type that is not appropriate for the context in which the expression occurs, or during the dynamic evaluation phase, the dynamic type of a value does not match a required type as specified by the matching rules in 2.5.4 SequenceType Matching.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-35995: XPST0017: It is a static error if the expanded QName and number of arguments in a function call do not match the name and arity of a function signature in the static context.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-35996: FORG0006: invalid argument type
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-35997: FORG0001: invalid value for cast/constructor
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-35998: XPTY0006: (Not currently used)
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-35999: FONC0001: undefined context item
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36201: Unable to find Page Definition for the template page.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36202: Cannot find page with name "{0}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36203: Failed to create SubPath "{0}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36204: Cannot find Page Definition with name "{0}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36205: Unable to find page with path "{0}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36206: Pages metadata file already exists under the path "{0}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36207: Unable to update DataBindings.cpx to update page usageId.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36208: Scope folder "{0}" for rename does not exist.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36209: Failed to get Permission class for page "{0}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36210: Failed to get Permission target for page "{0}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36211: Cache is not available.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36212: Failed to add pages to cache "{0}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36213: Failed to invalidate cache "{0}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36214: Failed to invalidate cache for scope "{0}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36215: A page with name {0} under path {1} does not exist.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36216: Failed to remove the page permissions for "{0}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36217: Failed to create .rdf file for page "{0}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36218: Failed to delete .rdf file "{0}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36301: Unable to find page "{0}" in the Binding Context.
Cause: Page objects do not exist in the Binding Context.
Action: Check if the page in the specified path exists.

Level: 1

Type: ERROR

Impact: Other

WCS-36302: Unable to create a document with name "{0}".
Cause: Invalid MO name supplied for creation in MDS.
Action: Check the name provided for creation of the document and ensure that it is a valid MO name.

Level: 1

Type: ERROR

Impact: Other

WCS-36303: Unable to create a document in path "{0}".
Cause: MDS raised an MDS_UNSUPPORTED_UPDATE exception while creating document.
Action: Check the MDS config to ensure that the path is editable.

Level: 1

Type: ERROR

Impact: Other

WCS-36304: Unable to create a pagedefs directory under the scope "{0}".
Cause: MDS raised an exception while creating pagedefs folder.
Action: Check the MDS config to ensure that the path is editable.

Level: 1

Type: ERROR

Impact: Other

WCS-36305: Unable to delete page "{0}".
Cause: MDS raised an exception while deleting the page.
Action: Check the MDS config to ensure that the path is editable.

Level: 1

Type: ERROR

Impact: Other

WCS-36306: Unable to create metadata for page "{0}".
Cause: MDS raised an exception while creating metadata for page.
Action: The metadata for the page already exists under the scope.

Level: 1

Type: ERROR

Impact: Other

WCS-36307: Unable to copy page "{0}".
Cause: MDS raised an exception while copying the page.
Action: Check the MDS config to ensure that the path is editable.

Level: 1

Type: ERROR

Impact: Other

WCS-36308: Unable to rename scope "{0}" to "{1}".
Cause: MDS raised an exception while renaming the pages under the scope.
Action: Check the MDS config to ensure that the path is editable.

Level: 1

Type: ERROR

Impact: Other

WCS-36309: An unexpected error occurred.
Cause: An unexpected error occurred.
Action: Contact your system administrator.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-36310: Unable to create a page with the name "{0}".
Cause: A page with the same name already exists.
Action: Change to use a different name.

Level: 1

Type: ERROR

Impact: Other

WCS-36311: PageService object is not an instance of PageServiceImpl.
Cause: PageService object is not an instance of PageServiceImpl.
Action: Create a Page service instance and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-36312: Could not flush changes to MDS. Adding view activity failed.
Cause: Could not flush changes to MDS.
Action: Try to create a new page.

Level: 1

Type: ERROR

Impact: Other

WCS-36313: Unable to find page definition file for page "{0}".
Cause: The page definition file does not exist or the page definition path is wrong in the Binding Context file.
Action: Check if the page definition file exists and make sure its path is correct in the Binding Context file.

Level: 1

Type: ERROR

Impact: Other

WCS-36314: Unable to create a page for now because another page is being created.
Cause: Another page is being created and all page metadata is locked.
Action: Try again.

Level: 1

Type: ERROR

Impact: Other

WCS-36315: The page style is no longer available.
Cause: The page style is deleted or hidden.
Action: Choose another page style.

Level: 1

Type: ERROR

Impact: Other

WCS-36316: Cannot perform the requested operation.
Cause: You do not have sufficient privileges to perform the requested operations.
Action: Ask your administrator to grant you the appropriate privileges and then try again.

Level: 1

Type: ERROR

Impact: Other

WCS-36701: Failed to redirect because the page is not specified.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36702: An ADF component with name "{0}" is not found.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36703: Failed to redirect because the page is not specified.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36704: User {0} already has access to the page.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36705: You do not have permission to change page security settings anymore.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36706: You do not have permission to change page properties anymore.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36707: Failed to save the changes because another page operation was in progress.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36708: Failed to instantiate DocSecurityBean.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36709: Failed to instantiate PageSecurityManager.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-36801: Failed to change page permission to "{0}".
Cause: An unexpected error occurred when changing page permission.
Action: Check error stack for details.

Level: 1

Type: ERROR

Impact: Other

WCS-36802: Failed to grant page permission "{0}" to user "{1}".
Cause: An unexpected error occurred when granting page permission to a user.
Action: Check error stack for details.

Level: 1

Type: ERROR

Impact: Other

WCS-36803: Failed to revoke page permission from user "{0}".
Cause: An unexpected error occurred when granting page permission to a user.
Action: Check error stack for details.

Level: 1

Type: ERROR

Impact: Other

WCS-36804: Failed to change page security to default mode.
Cause: An unexpected error occurred when changing page security mode.
Action: Check error stack for details.

Level: 1

Type: ERROR

Impact: Other

WCS-36805: A page named {0} already exists.
Cause: A page with the specified name exists.
Action: Specify a unique name for the page.

Level: 1

Type: ERROR

Impact: Other

WCS-37001: An unexpected error occurred.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-37002: An object of type {0} with this ID ({1}) already exits.
Cause: An attempt was made to create an object with an existing ID.
Action: Use a unique ID to Create the object.

Level: 1

Type: ERROR

Impact: Other

WCS-37003: Configuration invalid.
Cause: Either the configuration does not exist or the MDS instance is not specified.
Action: Specify a valid configuration with a MDS instance.

Level: 1

Type: ERROR

Impact: Other

WCS-37004: The name ({0}) is invalid.
Cause: The name specified was not valid.
Action: Specify a valid name.

Level: 1

Type: ERROR

Impact: Other

WCS-37006: Object modified by another user.
Cause: The object has been changed by another user.
Action: Refresh the object and try again.

Level: 1

Type: WARNING

Impact: Other

WCS-37007: Object of type {0} with ID={1} could not be found.
Cause: The ID is invalid.
Action: Specify a valid object ID.

Level: 1

Type: ERROR

Impact: Other

WCS-37008: Object ({0}) is immutable.
Cause: An attempt to change this object was made but this object is currently immutable.
Action: Either update object to allow changes or perform this operation on another object.

Level: 1

Type: ERROR

Impact: Other

WCS-37009: Method: {1} in class: {0} is invalid.
Cause: The specified class.method does not exist or is invalid.
Action: Check underlying method/property specification.

Level: 1

Type: ERROR

Impact: Other

WCS-37010: {0} is not a valid reference name to MDS.
Cause: The name specified is not a valid MDS reference name.
Action: Correct the name to a valid reference.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-37500: The note no longer exists.
Cause: Another user deleted the note.
Action: Refresh the links to see the latest changes.

Level: 1

Type: ERROR

Impact: Other

WCS-37501: This note has been modified by another user.
Cause: Another user modified the note. You can only modify the latest version.
Action: Refresh the page to see the latest changes.

Level: 1

Type: ERROR

Impact: Other

WCS-38001: An unexpected error occurred.
Cause: The cause of this error is unknown.
Action: Try repeating the action that caused this error.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-38002: Data source ({0}) does not exist.
Cause: The specified data source is invalid.
Action: Specify a valid data source and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-38003: Invalid configuration.
Cause: Either the configuration does not exist or MDSInstance is not specified.
Action: Specify a valid MDS configuration and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-38004: Object ({0}) is immutable.
Cause: An attempt to change this object was made but this object is currently immutable.
Action: Either update the object to allow changes or perform this operation on another object.

Level: 1

Type: ERROR

Impact: Other

WCS-38005: An object of type {0} with ID={1} could not be found.
Cause: The object ID is invalid.
Action: Specify a valid object ID.

Level: 1

Type: ERROR

Impact: Other

WCS-38006: Unable to perform transformation
Cause: Transformation input sources were invalid.
Action: Validate the input sources and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-38007: A search error occurred while searching for lists.
Cause: The search parameters were invalid.
Action: Validate the search parameters and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-38008: An error occurred while configuring the List API.
Cause: An invalid List API configuration was specified.
Action: Specify a valid List API configuration and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-38009: An error occurred while looking up list row data.
Cause: The database connection not found.
Action: Verify that a valid database connection exists and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-38010: A search error occurred while searching the discussion forums.
Cause: A connection to the discussion forum service could not be established.
Action: Validate the discussion forum connection details in connections.xml and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-38011: An error occurred while retrieving recent activity information.
Cause: Invalid parameters were passed to the Recent Activity API.
Action: Validate the API usage and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-38012: A search error occurred while searching the service.
Cause: Invalid parameters were passed to the Search API.
Action: Validate the API usage and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-38013: Unable to instantiate class
Cause: An invalid class reference was detected.
Action: Validate the class usage and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-38014: Illegal access exception while accessing class
Cause: An invalid class reference was detected.
Action: Validate the class usage and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-38015: Unable to find class
Cause: An unknown class was referenced.
Action: Verify the class reference and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-38016: Unable to find 'getEnabledScopes' method in class
Cause: Class is missing required method.
Action: Verify that the method exists and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-38017: Service exception while getting service registry.
Cause: Invalid parameters were passed to the Service Registry API.
Action: Validate the API usage and try again.

Level: 1

Type: ERROR

Impact: Other

WCS-38018: A null stream was returned for the RSS XML
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-38019: Object instance for reading RSS feed is not available
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-38020: Unable to get a HTTP connection object for the URL {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-38021: Null object for the XML document
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-38022: The RSS XML does not have a root element
Cause: Invalid XML content detected
Action: Ensure that the RSS feed URL returns XML conforming to the RSS format

Level: 1

Type: WARNING

Impact: Other

WCS-38023: The root element name of the RSS XML is not rss
Cause: The XML content is not RSS XML format compliant.
Action: Ensure that the XML returned by the feed URL is RSS XML format compliant.

Level: 1

Type: WARNING

Impact: Other

WCS-38024: The root element name of the RSS XML does not have any child elements
Cause: The XML content returned by the feed URL is not valid
Action: Ensure that the XML returned by the feed URL is RSS XML format compliant.

Level: 1

Type: WARNING

Impact: Other

WCS-38025: The XML content returned by the feed URL does not have the channel element
Cause: The XML content is not RSS XML format compliant
Action: Ensure that XML returned by the feed URL is RSS XML format compliant.

Level: 1

Type: WARNING

Impact: Other

WCS-38026: The channel element of the RSS XML does not have any child elements
Cause: The XML content returned by the feed URL is invalid
Action: Ensure that the XML returned by the feed URL is RSS XML format compliant.

Level: 1

Type: WARNING

Impact: Other

WCS-39001: Unable to get portlet response (Internal Error) for portlet binding {0}.
Cause: An internal error occurred in the portlet consumer.
Action: Check the portlet consumer application logs to locate the cause of the problem.

Level: 1

Type: ERROR

Impact: Other

WCS-39002: The binding context for this request is null.
Cause: An internal error occurred in setting the context for the request.
Action: Check if the page definition exists for this page and the request is correctly passing through the adfBinding filter, where bindingcontext is created. You can see this error for log level finer, when the application does not have any Model objects.

Level: 1

Type: ERROR

Impact: Other

WCS-39003: Unable to get the binding container for page {0}.
Cause: The application was unable to load the page definition for the requested page.
Action: Check whether the page definition for page {0} is properly defined.

Level: 1

Type: ERROR

Impact: Other

WCS-39101: Portlet component could not retrieve stored Faces View URL
Cause: Information about the current Faces View should have been stored on the current request so that it can be passed to Oracle JPDK portlets but it was not found.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-39251: Unable to process portlet action for portlet binding {0}.
Cause: An exception occurred during the processing of a portlet action in the portlet client.
Action: Check the portlet client logs for portlet binding {0}.

Level: 1

Type: ERROR

Impact: Other

WCS-39252: Unable to access the portlet container.
Cause: A failure occurred trying to access the portlet container. It could be a configuration problem where the run time is not able to locate the registered producer metadata.
Action: Check the portlet run-time logs and confirm your configuration (MDS path location) in adf-config.xml.

Level: 1

Type: ERROR

Impact: Other

WCS-39253: Unable to get the portlet with instance ID {0} from the container for portlet binding {1}.
Cause: The portlet instance was stale or unavailable in the list of portlet instances from the registered producer.
Action: Confirm whether the portlet instance ID {0} is correct and has not been modified. Try removing the portlet and associated portlet bindings {1} from the page and page definition and add this portlet to the page again.

Level: 1

Type: ERROR

Impact: Other

WCS-39254: Runnable portlet for portlet instance {0} for portlet binding {1} is null.
Cause: This error occurred due to some internal errors in the portlet client.
Action: Check the portlet client logs for this error and take appropriate action.

Level: 1

Type: ERROR

Impact: Other

WCS-39255: Unable to get portlet response for portlet instance ID {0} for portlet binding {1}.
Cause: Errors have occurred in the Portlet consumer while getting the portlet response. The Stack trace for the actual error should be able to provide more information about the cause of error.
Action: Check the portlet client logs for the cause and action of this error.

Level: 1

Type: ERROR

Impact: Other

WCS-39256: Unable to find the public parameter {0} for portlet binding {1}.
Cause: The public parameter {0} defined in the portlet binding {1} did not match the available portlet public parameters.
Action: Check the public parameter exposed by the portlet and make sure the public parameters used in the portlet bindings are the same as the one available in the portlet.

Level: 1

Type: ERROR

Impact: Other

WCS-39257: Unable to set portlet mode {0} for portlet binding {1}
Cause: An exception occurred in the portlet run-time client.
Action: Check the portlet run-time client logs.

Level: 1

Type: ERROR

Impact: Other

WCS-39258: Unable to set the portlet window state {0} for the portlet view component {1}.
Cause: An exception occurred in the portlet run-time client.
Action: Check the portlet run-time client logs.

Level: 1

Type: ERROR

Impact: Other

WCS-39259: Unable to process the portlet action for the portlet component {0} exception {1}.
Cause: An exception occurred during the processing of a portlet action in the portlet client.
Action: Check the portlet client logs for the portlet component {0}.

Level: 1

Type: ERROR

Impact: Other

WCS-39260: Unable to get the portlet binding object for the portlet component {0}.
Cause: Run time was not able to evaluate the value attribute of the portlet tag.
Action: Check the value attribute of the portlet tag and ensure it is defined properly in the associated page definition.

Level: 1

Type: ERROR

Impact: Other

WCS-39261: Portlet bindings object {0} is not properly defined for the portlet view component {1} (not of type portlet binding).
Cause: The portlet binding (value) defined for portlet component {0} is of an illegal type.
Action: Check whether the portlet binding defined for the portlet component {0} is pointing to the PortletBinding element in the page definition.

Level: 1

Type: ERROR

Impact: Other

WCS-39262: Unable to get portlet binding object {0} from page {1}.
Cause: The portlet servlet was not able to locate the portlet bindings from the supplied information.
Action: Check if the value attribute of the portlet tag is correctly defined and a PortletBinding of that object exists in the page definition. Also ensure that ADFPhaseListener (or its subclasses) are registered in the lifecycle phase listener in your application faces-config.xml.

Level: 1

Type: ERROR

Impact: Other

WCS-39263: Unknown error for portlet instance Id {0} exception {1}.
Cause: Errors have occurred in the Portlet runtime while getting the portlet response. The Stack trace for the actual error should be able to provide more information about the cause of error.
Action: Check portlet client logs for the cause and action of this error.

Level: 1

Type: ERROR

Impact: Other

WCS-39264: Portlet bindings are null for portlet component {0}.
Cause: Run time was not able evaluate the value attribute of the portlet tag.
Action: Check the value attribute of the portlet tag and ensure it is defined properly in the associated page definition.

Level: 1

Type: ERROR

Impact: Other

WCS-39265: Unable to get portlet response (time-out) for portlet binding {0}.
Cause: Timeout occurred while performing a task at the producer side. This can happen if some tasks at the producer are taking longer than the timeout specified for the registered producer.
Action: Edit the registration details for this producer and increase the timeout entry.

Level: 1

Type: ERROR

Impact: Other

WCS-39266: Unable to get portlet metadata naming policy.
Cause: The portlet metadata naming policy class could not be initialized.
Action: The default naming policy will be used unless the resource META-INF/portlet/ADFPortletNamingPolicy is accessible and contains the name of a valid naming policy class.

Level: 1

Type: ERROR

Impact: Other

WCS-39267: Portlet binding was not refreshed.
Cause: The portlet binding was not refreshed when it was accessed by the portlet view component to which it is bound.
Action: Check that the refresh option on the portlet binding is not set to Never.

Level: 1

Type: ERROR

Impact: Other

WCS-39268: Page variable {0} not defined in page definition {1}.
Cause: The named page variable which is referenced by the parameter definition of a PortletBinding is not defined.
Action: Verify that the Portlet parameter page variable declarations in the page definition are correct.

Level: 1

Type: ERROR

Impact: Other

WCS-39269: FullPageModeRequest object not found on Portlet UIComponent {0}
Cause: The request object required to forward to Portlet full page modes is missing from the Portlet UIComponent.
Action: This is an internal error. The redirect to the full page mode will still occur but some information, such as stylesheet information may be missing when the full page mode is rendered.

Level: 1

Type: ERROR

Impact: Other

WCS-39270: Invalid request made to the portlet servlet.
Cause: A request was made to the portlet servlet for a full page mode rendition or for portlet iframe content but the request parameters and / or information stored in the session were incomplete or incorrect.
Action: Portlet authors should ensure that all links or form action URLs back to the portlet are created using the appropriate portlet API.

Level: 1

Type: ERROR

Impact: Other

WCS-39271: Portlet with id {0} is not inside an appropriate JSF Form.
Cause: This usually occurs because the portlet was not placed inside of a JSF Form.
Action: Ensure that the portlet is a descendent, direct or otherwise, of the page's JSF Form.

Level: 1

Type: ERROR

Impact: Other

WCS-39272: The metadata for portlet binding {0} was not found in MDS.
Cause: This is often caused by a failed producer import or export.
Action: Check the server logs for producer import errors during application deployment. Also check for export errors when the application was packaged prior to deployment. For example, if deployed from JDeveloper, check the deployment messages for errors.

Level: 1

Type: ERROR

Impact: Other

WCS-39273: Failed to unmarshall payload for Portlet Event {0} on PortletBinding {1}. Expected type {2}.
Cause: It is likely that the payload XML was not compatible with the stated payloadclass type.
Action: Ensure that the event declaration in the PortletBinding in the page definition has a suitable payloadclass attribute.

Level: 1

Type: ERROR

Impact: Other

WCS-39274: Failed to unmarshall payload for Portlet Event {0} on PortletBinding {1}. No payload class name was specified.
Cause: Unmarshalling of an Portlet Event payload failed. The payload class name was not specified in the Portlet Binding definition so payload unmarshalling can only happen if the payload type is sent with the event. This will only work with producers that support sending the event type. It is also possible that the class that was sent by the producer as the event payload type is not available on the consumer.
Action: Ensure the payload class is available on the consumer or explicitly specify a payload class name in the Portlet Binding that can be used for unmarshalling the event payload.

Level: 1

Type: ERROR

Impact: Other

WCS-39275: Declared payload class {0} not found for event {1} in PortletBinding {2}.
Cause: A class name was specified as the payload type of an event but that class could not be found.
Action: Ensure that the payloadclass value is correct and that the class is available to the application.

Level: 1

Type: ERROR

Impact: Other

WCS-39276: An error occurred on the remote portlet for PortletBinding {0}.
Cause: An error was returned by the remote portlet.
Action: Check the portlet producer application logs to locate the cause of the problem.

Level: 1

Type: ERROR

Impact: Other

WCS-39277: Unable to transfer error details from the Portlet Servlet to the JSF lifecycle.
Cause: An error occurred in a request handled by the Portlet Servlet but information about that error was not successfully transferred back to the JSF lifecycle.
Action: This is an internal error. Check the server logs of the original error which will have been logged independently by the Portlet Servlet.

Level: 1

Type: ERROR

Impact: Other

WCS-39278: An error has occurred for Portlet Binding {0}.
Cause: An error has occurred which has caused the PortletBinding to be placed in an error state. This will prevent the portlet being rendered.
Action: Review the cause exception.

Level: 1

Type: ERROR

Impact: Other

WCS-39279: An error has occurred for Portlet Binding {0}.
Cause: An error has occurred which has caused the Portlet Component to be placed in an error state. This will prevent the portlet being rendered.
Action: Review the cause exception.

Level: 1

Type: ERROR

Impact: Other

WCS-39280: An error has occurred in the ADFPortletServlet
Cause: An error has occurred in the servlet that serves Portlet content for iframes and full page modes.
Action: Review the cause exception.

Level: 1

Type: ERROR

Impact: Other

WCS-39281: Attempt to invoke portlet action in non-POST request
Cause: An attempt to invoke a portlet action via an HTTP method other than POST was detected. This could be a CSRF attack.
Action: Verify that the URL used to access the page was correct.

Level: 1

Type: ERROR

Impact: Other

WCS-39501: Unable to create portlet parameter {0} with associated page variable {1} for portlet binding {2}.
Cause: Portlet parameter name {0} or associated page variable {1} for portlet binding {2} was not defined or was null.
Action: Check the portlet parameter name {0} or associated page variable {1} in portlet binding {2}. If they are properly defined, they should use name and pageVariable with non-null string values.

Level: 1

Type: WARNING

Impact: Other

WCS-39502: Unable to find variable manager for page definition {0}.
Cause: The variable manager was not defined in the page definition.
Action: Check the page definition {0} and ensure that page variables are being used and that the VariableIterator element is available inside executable binding section.

Level: 1

Type: WARNING

Impact: Other

WCS-39503: ADF lifeCycle does not execute properly for portlet bindings {0}.
Cause: The ADF lifeCycle terminated abruptly.
Action: Check log files for any errors that occurred during the execution life cycle on other resources in the page definition.

Level: 1

Type: WARNING

Impact: Other

WCS-39504: Warning: Runnable portlet for portlet instance {0} for portlet binding {1} is null, trying to get again.
Cause: This error was due to some internal errors from the portlet client.
Action: Check portlet client logs for this error and take the appropriate action.

Level: 1

Type: WARNING

Impact: Other

WCS-39505: Unable to create portlet event {0} for portlet binding {1}.
Cause: Portlet parameter event {0} or associated payload {1} for portlet binding {2} was not defined or was null.
Action: Check the portlet event name {0} or associated payload {1} in portlet binding {2}. If they are properly defined, they should use name and payload with non-null string values.

Level: 1

Type: WARNING

Impact: Other

WCS-39507: Iframe content request checksum verification failed.
Cause: The checksum verification of the parameters in the request for Portlet markup in the iframe has failed.
Action: This may indicate that a deliberately modified request for Portlet content has been made.

Level: 1

Type: WARNING

Impact: Other

WCS-39508: Portlet mode change unauthorized. Portlet {0} bound to PortletBinding {1}; Requested mode: {2}
Cause: A portlet mode change was requested but the user does not have permission to access that mode.
Action: The mode change may have been via mode change links rendered by the Portlet.

Level: 1

Type: WARNING

Impact: Other

WCS-39509: Event definition in PortletBinding {0} has no name
Cause: All events defined within the PortletBinding must have a name attribute.
Action: Add a name attribute to the Event definition.

Level: 1

Type: WARNING

Impact: Other

WCS-39510: Event definition {0} in PortletBinding {1} has invalid eventType ["{2}"]. Valid values are [{3}].
Cause: An invalid value was specified for the eventType in the event declaration.
Action: Change the eventType to a valid value.

Level: 1

Type: WARNING

Impact: Other

WCS-39511: The portlet event in event definition {0} in PortletBinding {1} does not specify the localpart of the portlet event QName.
Cause: Portlet events are identified by a QName. The QName namespace is optional but the localpart is required.
Action: Check that the portletevent element has a valid localpart attribute.

Level: 1

Type: WARNING

Impact: Other

WCS-39512: The portlet event in event definition {0} in PortletBinding {1} does not specify a payloadclass attribute.
Cause: In order to unmarshall the Portlet Event payload the payload class must be specified.
Action: Specify the Portlet Event payload classname in the payloadclass attribute of the portletevent element.

Level: 1

Type: WARNING

Impact: Other

WCS-39513: The payload derived from Contextual Event {0}, of payload type {1}, is not of a valid type to be used as a portlet event payload for portlet event {2}. The portlet event will not be fired.
Cause: When ADFm Contextual Events are mapped to Portlet Events, the resulting payload, whether used directly or transformed must be a simple java type, a JAXB-bindable type or Serializable.
Action: Use a payload of a suitable type. Contextual Event payloads can also be mapped to other types in the Contextual Event EventMap.

Level: 1

Type: WARNING

Impact: Other

WCS-39514: Failed to set value to event payload mapping EL expression "{0}".
Cause: When defining payload mappings for Contextual Events that are received by a Portlet and sent of Portlet events, the parameter "name" attribute should contain an valid EL lvalue expression that includes #{portletEventPayload} or some valid variant of it. It's also possible that the value being assigned is of the wrong type.
Action: Check that the payload mapping EL expressions are valid.

Level: 1

Type: WARNING

Impact: Other

WCS-39515: Failed to evaluate payload mapping EL expression "{0}".
Cause: When defining payload mappings for Contextual Events that are received by a Portlet and sent as Portlet events, the parameter "value" attribute should contain an valid EL rvalue expression.
Action: Check that the payload mapping EL expression is valid.

Level: 1

Type: WARNING

Impact: Other

WCS-39516: Could not find payload class "{0}" defined as the payload type for event {1} associated with PortletBinding {2}.
Cause: The type of the Portlet Event payload can come from the remote producer, e.g. defined in portlet.xml, or it can be defined or overridden in an event section of the Portlet Binding declaration in the page definition.
Action: Check that the payload type is a class that is available in the portlet consumer application.

Level: 1

Type: WARNING

Impact: Other

WCS-39518: Invalid Additional Context EL expression {0} on PortletBinding {1}. The EL evaluated to {2}.
Cause: The additionalContext attribute should contain an EL expression that returns a Map<String, Serializable> of additional context values to pass to the portlet. On this occasion it did not.
Action: Check that the Additional Context EL expression returns a valid Map<String, Serializable> of context values.

Level: 1

Type: WARNING

Impact: Other

WCS-39519: The Additional Context EL expression {0} on PortletBinding {1} returned a null valued additional context property. The property key was {2}.
Cause: The additionalContext attribute should contain an EL expression that returns a Map<String, Serializable> of additional context values to pass to the portlet. This map cannot contain null valued Map entries. Null valued entries will not be sent to the portlet.
Action: Check that the Additional Context EL expression returns a valid Map<String, Serializable> of non-null additional context values.

Level: 1

Type: WARNING

Impact: Other

WCS-39520: The Additional Context EL expression {0} on PortletBinding {1} returned an additional context property that was not a String or Serializable Object. The property key was {2}.
Cause: The additionalContext attribute should contain an EL expression that returns a Map<String, Serializable> of additional context values to pass to the portlet. This map can only contains String or Serializable Object values. Other entries will not be sent to the portlet.
Action: Check that the Additional Context EL expression returns a valid Map<String, Serializable> of context values.

Level: 1

Type: WARNING

Impact: Other

WCS-39521: The Additional Context EL expression {0} on PortletBinding {1} returned a Map with a key that was not a String.
Cause: The additionalContext attribute should contain an EL expression that returns a Map<String, Serializable> or additional context values to pass to the portlet. On this occasion it did not.
Action: Check that the Additional Context EL expression returns a valid Map<String, Serializable> of context values.

Level: 1

Type: WARNING

Impact: Other

WCS-39522: An error occurred whilst evaluating Additional Context EL expression {0} on PortletBinding {1}.
Cause: The additionalContext attribute should contain an EL expression that returns a Map<String, Serializable> or additional context values to pass to the portlet. An error occurred whilst evaluating this expression and so no context will be sent.
Action: Check that the Additional Context EL expression returns a valid Map<String, Serializable> of context values.

Level: 1

Type: WARNING

Impact: Other

WCS-39523: An error occurred whilst serializing Additional Context object for key {0} on PortletModel {1}
Cause: An error occurred during object serialization.
Action: Review the specific error reported and take appropriate corrective action.

Level: 1

Type: WARNING

Impact: Other

WCS-39524: Specified PortletErrorRenderer not found or not of a PortletErrorRenderer subclass. Using the default PortletErrorRenderer.
Cause: The error renderer can be specified in the renderkit configuration in faces-config.xml. The specified PortletErrorRenderer was either not found or not of the correct type. A default PortletErrorRenderer has been used instead.
Action: Verify the PortletErrorRenderer configuration.

Level: 1

Type: WARNING

Impact: Other

WCS-39525: Exception occurred when de-serializing Contextual Event payload.
Cause: An exception occurred while attempting to de-serialized a serialized Contextual Event payload received from a remote portlet.
Action: Examine the associated cause exception.

Level: 1

Type: WARNING

Impact: Other

WCS-39526: The parameterMap EL {0} on PortletBinding {1} evaluated to null.
Cause: The PortletBinding has a parameterMap attribute that specifies an EL expression that evaluated to null.
Action: Check and correct the parameterMap attribute.

Level: 1

Type: WARNING

Impact: Other

WCS-39527: The parameterMap on PortletBinding {0} contained a key that was not a String.
Cause: parameterMaps must contain String keys that are portlet parameter names.
Action: Check and correct the parameterMap keys.

Level: 1

Type: WARNING

Impact: Other

WCS-39528: The parameterMap on PortletBinding {0} contained a key {1} that is not a parameter on the portlet.
Cause: parameterMaps must contain String keys that are portlet parameter names.
Action: Check and correct the parameterMap keys.

Level: 1

Type: WARNING

Impact: Other

WCS-39529: The parameterMap EL {0} on PortletBinding {1} did not return a Map.
Cause: The parameterMap EL must return a Map object.
Action: Check and correct the parameterMap.

Level: 1

Type: WARNING

Impact: Other

WCS-39530: An error occurred whilst evaluating the parameterMap EL expression {0} on PortletBinding {1}.
Cause: The parameterMap should contain an EL expression that returns a Map of portlet parameter values. An error occurred whilst evaluating this expression.
Action: Check that the parameterMap EL expression returns a valid Map of parameter vales..

Level: 1

Type: WARNING

Impact: Other

WCS-39531: Cannot set parameter {0} on PortletBinding {1} with a value that is not a String or String Array.
Cause: An attempt was made to set a portlet parameter with a value that is not a String or String Array.
Action: Check the parameter values being set via page variables or the parameterMap attribute on the portlet.

Level: 1

Type: WARNING

Impact: Other

WCS-40001: Configuration error: property "{0}".
Cause: The named configuration property has a invalid value.
Action: Correct the value of the property.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40002: Configuration error: property "{0}" value "{1}" is not an integer.
Cause: The named configuration property does not have an integer value.
Action: Specify an integer value for the named property.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40003: Configuration error: property "{0}" invalid value "{1}".
Cause: The named configuration property has a invalid value.
Action: Correct the value of the property.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40004: Configuration error: property "{0}" value "{1}" is not a number.
Cause: The named configuration property does not have a numeric value.
Action: Specify a numeric value for the named property.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40009: {0} element without a name or default="true".
Cause: User or subscriber cache partition settings are being defined for an unnamed entity.
Action: Specify a name or declare the element as defining default values.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40010: Parameter {0} specifies an unrecognized cache level: {1}.
Cause: A cache configuration parameter uses an invalid cache level.
Action: Correct the parameter such that it uses a cache level of either 'system' or 'user'.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40011: Invalid cache configuration parameter: {0}.
Cause: A configuration parameter starting with 'cache.' has an invalid name.
Action: Correct the parameter name.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40014: Unable to open Java Object Cache.
Cause: Java Object Cache failed to open.
Action: Examine the Java Object Cache log file to determine the cause.

Level: 1

Type: ERROR

Impact: Other

WCS-40015: Object {0} is too big to cache in region {1}.
Cause: Portlet content cannot be cached because it is too large.
Action: Reconfigure the cache such that enough space is available for the content.

Level: 1

Type: ERROR

Impact: Other

WCS-40016: Unable to insert data into cache region {0} using key {1}.
Cause: An error occurred while trying to cache portlet content.
Action: Examine the Java Object Cache log file to determine the cause.

Level: 1

Type: ERROR

Impact: Other

WCS-40017: Unable to access cache to get entry for {0}.
Cause: An error occurred while trying to retrieve content from the cache.
Action: Examine the Java Object Cache log file to determine the cause.

Level: 1

Type: ERROR

Impact: Other

WCS-40018: Unable to access cache to remove entry for {0}.
Cause: An error occurred while trying to remove content from the cache.
Action: Examine the Java Object Cache log file to determine the cause.

Level: 1

Type: ERROR

Impact: Other

WCS-40021: Configuration error: property "{0}" cannot be greater than property "{1}".
Cause: The named configuration properties have invalid values.
Action: Correct the values of the properties.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40022: Configuration error: property "{0}" cannot be less than property "{1}".
Cause: The named configuration properties have invalid values.
Action: Correct the values of the properties.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40024: Timing out task: {0}.
Cause: A task took too long to complete.
Action: If the problem persists, increase the timeout period for the task.

Level: 1

Type: WARNING

Impact: Threads

WCS-40025: Muffling exception in method {0}, context = {1}.
Cause: An error occurred but processing was allowed to continue.
Action: Use the context information to determine if remedial action is required.

Level: 1

Type: WARNING

Impact: Other

WCS-40026: Invalid client id "{0}" for portlet resource request handle "{1}".
Cause: A portlet resource request contained an invalid client id.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40027: Error proxying resource.
Cause: An unexpected error occurred while proxying a request for a portlet resource.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40029: Error accessing ADF configuration.
Cause: The portlet client was unable to access ADF configuration information.
Action: Examine the associated stack trace to resolve the issue.

Level: 1

Type: WARNING

Impact: Configuration

WCS-40030: Cannot export portlet {0} because it is a producer offered portlet.
Cause: An attempt has been made to export a producer offered portlet.
Action: Remove the offered portlet from the export set.

Level: 1

Type: ERROR

Impact: Other

WCS-40031: Unexpected portlet (handle = {0}) in group {1} for producer {2}.
Cause: The producer returned a portlet in an export set that was not requested by the client.
Action: Check the producer's log file to determine that it is functioning correctly.

Level: 1

Type: WARNING

Impact: Other

WCS-40032: Failed to export portlets with handles: {0}. Reason given by producer was: {1}.
Cause: A producer was unable to export one or more portlets.
Action: Resolve the issue given by the producer as the reason for the failure and retry the export.

Level: 1

Type: WARNING

Impact: Other

WCS-40033: Producer {0} does not support the WSRP ImportPortlets operation. Unable to proceed with import using API.
Cause: An attempt was made to import data obtained using the WSRP ExportPortlets operation into a producer that does not support the ImportPortlets operation.
Action: The client will fall back to importing portlets by cloning. Enable ImportPortlets on the producer to import portlets using the API.

Level: 1

Type: WARNING

Impact: Other

WCS-40034: Error calling producer to import portlets for export group {0}.
Cause: The producer failed to import a group of portlets.
Action: Examine the associated exception and producer logs to resolve the issue.

Level: 1

Type: WARNING

Impact: Other

WCS-40035: Unexpected portlet with ID {0} in ImportPortletResponse.
Cause: The producer returned a portlet in an import response that was not requested by the client.
Action: Check the producer's log file to determine that it is functioning correctly.

Level: 1

Type: WARNING

Impact: Other

WCS-40040: Error calling producer to delete portlet handle {0} overwritten during import.
Cause: A call to the producer to delete a portlet failed.
Action: Delete the portlet manually if possible.

Level: 1

Type: WARNING

Impact: Other

WCS-40041: Unable to import portlet with ID {0}.
Cause: A portlet with the same ID already exists but is based on a different offered portlet.
Action: Remove the existing portlet and retry the import operation.

Level: 1

Type: WARNING

Impact: Other

WCS-40042: Failed to import portlets with IDs: {0}. Reason given by producer was: {1}.
Cause: A producer was unable to import one or more portlets.
Action: Resolve the issue given by the producer as the reason for the failure and retry the import.

Level: 1

Type: WARNING

Impact: Other

WCS-40046: Filter unable to modify markup.
Cause: An exception caused filtering of portlet markup to fail.
Action: Examine the associated exception to resolve the issue.

Level: 1

Type: WARNING

Impact: Other

WCS-40047: Could not load markup filter {0}. Portlet markup cannot be filtered.
Cause: An error prevented a portlet markup filter from being created.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40050: Unexpected content type "{0}" in {1} response.
Cause: The producer responded with a content type the client was not expecting.
Action: Consult the producer's log file to determine why the incorrect content type was used.

Level: 1

Type: ERROR

Impact: Other

WCS-40052: WSRP producer {0} supports the export feature but does not support export by value. Portlets will be exported by cloning.
Cause: The producer supports the export feature but does not support export by value.
Action: If possible, enable the export by value feature on the producer.

Level: 1

Type: WARNING

Impact: Other

WCS-40053: WSRP v2 style import failed for producer {0}. Will attempt import by cloning.
Cause: An attempt to import portlets by calling the producer's ImportPortlets operation failed.
Action: Consult the client and producer logs to determine why the import failed.

Level: 1

Type: WARNING

Impact: Other

WCS-40055: Error processing initSession for producer {0}.
Cause: Invoking a WSRP producer's InitCookie operation failed.
Action: Consult the producer's log file to determine the cause of the failure.

Level: 1

Type: WARNING

Impact: Other

WCS-40057: Ignoring remote producer requery handle: {0}.
Cause: This feature is not implemented.
Action: No action required.

Level: 1

Type: WARNING

Impact: Other

WCS-40058: ID {0} not found.
Cause: An ID requested for export does not correspond to an object.
Action: Verify that the ID is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-40059: ID {0} is not for a producer or portlet.
Cause: An ID requested for export does not correspond to a producer or a portlet. Only producers and portlets can be exported.
Action: Correct the ID or remove it from the export request.

Level: 1

Type: ERROR

Impact: Other

WCS-40060: Error during portlet export. Portlets will not be available in the target application. Context: input mds repository file path = {0}. output mds repository file path = {1}. input connections file path and name = {2}. export ID = {3}. producer/portlet IDs to export: {4}.
Cause: An exception was thrown during a portlet export operation.
Action: Examine the exception and resolve the issue that caused the failure.

Level: 1

Type: ERROR

Impact: Other

WCS-40061: Error during portlet import. Context: input mds repository file path = {0}. output mds repository file path = {1}. output connections file path and name = {2}. export ID = {3}.
Cause: An exception was thrown during an import operation.
Action: Examine the exception and resolve the issue that caused the failure.

Level: 1

Type: ERROR

Impact: Other

WCS-40062: No object with ID {0}.
Cause: An ID does not correspond to an object.
Action: Verify that the ID is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-40063: Object with ID {0} expected type {1} actual type {2}.
Cause: An ID does not correspond to an object of the expected type.
Action: Verify that the ID and expected type are correct.

Level: 1

Type: ERROR

Impact: Other

WCS-40064: Parse error : unknown element "{0}".
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40065: Parse error : unknown attribute "{0}".
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40066: Source portlet ID = "{0}" not found when attempting to create copy name = "{1}" ID = "{2}".
Cause: An ID does not correspond to an object.
Action: Verify that the ID is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-40067: Future.get() returned null [activity {0}].
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40068: Future.get() returned type "{0}" expected "{1}".
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40069: Could not import portlet with ID "{0}".
Cause: A suitable offered portlet could not be found.
Action: Check that the producer that owns the imported portlet is properly registered.

Level: 1

Type: ERROR

Impact: Other

WCS-40070: Portlet lists differ between locale {0} and {1}.
Cause: The remote producer returned unexpected portlets for a particular locale.
Action: Check that the remote producer is functioning correctly.

Level: 1

Type: ERROR

Impact: Other

WCS-40071: Portlet {0} has no definition.
Cause: An attempt was made to create a RunnablePortletBean based on a PortletBean without a definition.
Action: Associate a PortletDef with the PortletBean before creating a RunnablePortletBean.

Level: 1

Type: ERROR

Impact: Other

WCS-40072: Mode {0} not allowed on producer offered portlets.
Cause: An attempt was made to change to a invalid mode for a producer offered portlet.
Action: Only use this mode for non-offered portlets.

Level: 1

Type: ERROR

Impact: Other

WCS-40073: Invalid portlet rendition generated.
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40074: Could not import producer with ID "{0}" because that ID is already used by an object of a different type "{1}".
Cause: The ID given for an imported producer is in use.
Action: If possible, use a different ID for the imported producer.

Level: 1

Type: ERROR

Impact: Other

WCS-40075: Could not import portlet with ID "{0}" because that ID is already used by an object of a different type "{1}".
Cause: The ID given for an imported portlet is in use by an object which is not a portlet.
Action: If possible, use a different ID for the imported portlet.

Level: 1

Type: ERROR

Impact: Other

WCS-40076: Could not import portlet with ID "{0}" because that ID is already used by a portlet with a different producerPortletId. Importing producerPortletId = "{1}", existing producerPortletId = "{2}".
Cause: The ID given for an imported portlet is in use by a portlet based on a different producer offered portlet.
Action: If possible, use a different ID for the imported portlet.

Level: 1

Type: ERROR

Impact: Other

WCS-40077: Could not import portlet with ID "{0}" because that ID is already used by a portlet belonging to a different producer with ID "{1}".
Cause: The ID given for an imported portlet is in use by a portlet belonging to a different producer.
Action: If possible, use a different ID for the imported portlet.

Level: 1

Type: ERROR

Impact: Other

WCS-40078: Errors during transport: {0}.
Cause: The portlet producer reported errors during an export or import operation.
Action: Refer to the errors reported by the producer.

Level: 1

Type: ERROR

Impact: Other

WCS-40079: SOAP Exception Fault Code = {0}
Cause: The portlet producer raised a SOAP fault in response to a request.
Action: Refer to the error reported by the producer.

Level: 1

Type: ERROR

Impact: Other

WCS-40080: Unexpected input of type {0} passed to the {1} pipe.
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40081: Unexpected output of type {0} passed to the {1} pipe.
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40082: Could not create a runnable for portlet {0}.
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40083: Error copying portlet {0}.
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40084: Error returned from prepareRendition(): {0}
Cause: An error occurred while preparing portlet markup.
Action: Use the reported error message to resolve the issue.

Level: 1

Type: ERROR

Impact: Other

WCS-40085: JNDI lookup failed for {0}.
Cause: Looking up an object using the Java Naming and Directory Interface failed.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40086: Unable to obtain interaction for producer {0}.
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40087: WSRP registration returned null producer.
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40088: {0}Pipe caught exception: {1}: {2}
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40089: WSRP producer returned markup but did not specify a MIME type.
Cause: The producer behaved in an unexpected way.
Action: Contact the producer's administrator.

Level: 1

Type: WARNING

Impact: Compliance

WCS-40090: WSRP producer returned both {0} and {1}. The {2} field will be ignored.
Cause: The producer behaved in an unexpected way by returning values for mutually exclusive fields.
Action: Contact the producer's administrator.

Level: 1

Type: WARNING

Impact: Compliance

WCS-40091: Parse error processing SOAP response: {0}
Cause: The portlet client was unable to process a response it received from a producer.
Action: Check the producer URL and verify that the producer is running. Alternatively, contact the producer's administrator.

Level: 1

Type: ERROR

Impact: Requests/Responses

WCS-40092: Web producer responded with an error: {0} (Fault code: {1})
Cause: The portlet client received an error in response to a request to a producer.
Action: Check the producer URL and service ID. Alternatively, contact the producer's administrator.

Level: 1

Type: ERROR

Impact: Requests/Responses

WCS-40093: An I/O error occurred while contacting a producer.
Cause: The portlet client was unable to successfully communicate with the producer.
Action: Examine the stack trace associated with this message to determine the root cause.

Level: 1

Type: ERROR

Impact: Network

WCS-40094: Portlet instance "{0}" already exists.
Cause: An attempt was made to create a portlet with a name that is already in use.
Action: Retry the operation using a different name.

Level: 1

Type: ERROR

Impact: Other

WCS-40095: Unable to locate connection: {0}.
Cause: A connection used for a producer cannot be found.
Action: Check that the connection exists.

Level: 1

Type: ERROR

Impact: Other

WCS-40096: Unable to locate URL connection: {0}.
Cause: A URL connection used by a producer connection cannot be found.
Action: Check that the URL connection exists.

Level: 1

Type: ERROR

Impact: Other

WCS-40097: Error processing notification of {0} operation for object {1}.
Cause: A portlet operation succeeded but notification of a listener failed.
Action: Examine the stack trace associated with this message to determine the root cause.

Level: 1

Type: ERROR

Impact: Other

WCS-40098: Unsupported WSRP service version: {0}.
Cause: An attempt was made to use a WSRP service of an supported version.
Action: Use a version of the WSRP service that is supported or upgrade the portlet client.

Level: 1

Type: ERROR

Impact: Compliance

WCS-40099: No suitable WSRP ports found in WSDL at {0}.
Cause: An attempt was made to use a WSDL document that does not define any WSRP ports that are compatible with this version of the portlet client.
Action: Verify that the URL for the WSRP WSDL document is correct and that the document is valid.

Level: 1

Type: ERROR

Impact: Compliance

WCS-40100: WSRP producer responded with an error ({0}).
Cause: The portlet client received an error in response to a request to a producer.
Action: Examine the stack trace associated with this message to determine the cause.

Level: 1

Type: ERROR

Impact: Other

WCS-40101: Cannot open Web producer connection.
Cause: An error occurred while opening a Web producer connection.
Action: Verify that the connection URL and any proxy server settings are correct.

Level: 1

Type: ERROR

Impact: Network

WCS-40102: Error setting proxy server details ({0}) for connection {1}.
Cause: There is a problem with the proxy server defined for a connection.
Action: Correct the proxy server details for the connection.

Level: 1

Type: ERROR

Impact: Network

WCS-40103: HTTP {0} request to URL {1} failed with status code {2} reason {3}. Check that the producer URL has been correctly specified, that the producer server machine and producer container are running, that the producer application is deployed correctly, and that the client can reach the server if behind a firewall.
Cause: There was a problem communicating over HTTP to a remote producer.
Action: Check that the producer URL has been correctly specified, that the producer server machine and producer container are running, that the producer application is deployed correctly, and that the client can reach the server if behind a firewall. Also check that the producer server has no errors.

Level: 1

Type: ERROR

Impact: Network

WCS-40104: HTTP error
Cause: There was a problem communicating over HTTP to a remote producer.
Action: Check that the producer URL has been correctly specified, that the producer server machine and producer container are running, that the producer application is deployed correctly, and that the client can reach the server if behind a firewall. Lastly check that the producer server has no errors.

Level: 1

Type: ERROR

Impact: Network

WCS-40105: Remote error
Cause: There was an error on the remote producer server.
Action: Check the remote producer server logs for further details.

Level: 1

Type: ERROR

Impact: Other

WCS-40106: Client queue full.
Cause: This request was rejected because the client portlet request queue was full.
Action: Resubmit the request, or if this persists consider increasing the configured queue size.

Level: 1

Type: ERROR

Impact: Other

WCS-40107: Client request time out.
Cause: The client portlet request took too long to complete and so was timed out. This could have been because the client was too busy, the network was slow, or the remote producer server was too busy or in error.
Action: Resubmit the request, or if this persists consider increasing the configured timeout periods.

Level: 1

Type: ERROR

Impact: Other

WCS-40108: Client producer connection not found.
Cause: The client producer connection was not found in connections.xml.
Action: Create the producer connection.

Level: 1

Type: ERROR

Impact: Other

WCS-40109: Client metadata error.
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40110: Error
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40111: Invalid Keystore Type ({0}).
Cause: The valid keystore types are JKS and PKCS12.
Action: Correct the keystore type given for the connection.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40112: Content type error.
Cause: The portlet response was of the wrong content type.
Action: This may indicate that the producer is returning an error, or that the URL registered is incorrect and not actually a producer URL, Check the registration and producer server logs.

Level: 1

Type: ERROR

Impact: Other

WCS-40113: External Application : {0} does not exist.
Cause: The external application does not exist.
Action: Verify that the external application specified in the registration wizard exists.

Level: 1

Type: ERROR

Impact: Other

WCS-40114: Error determining disk cache status.
Cause: An error occurred while requesting the status of the caching service's disk cache.
Action: Check the caching service's configuration and log file.

Level: 1

Type: ERROR

Impact: Other

WCS-40115: Error reading exception from byte array.
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40116: Error writing exception to byte array.
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40117: The portlet attempted to issue a redirect in response to a render or resource request. Redirect URL: {0}.
Cause: The portlet attempted to redirect the browser window in response to a render request.
Action: This operation is not allowed in an Oracle WebCenter application. A portlet may only issue a redirect in response to a user interaction directly within the portlet. Contact the portlet developer.

Level: 1

Type: ERROR

Impact: Other

WCS-40118: The parameter {0} may not be used in conjunction with wsrp-urlType {1}. The parameter will be ignored.
Cause: The WSRP portlet markup contained an incorrectly formatted wsrp_rewrite token.
Action: Contact the portlet developer.

Level: 1

Type: WARNING

Impact: Compliance

WCS-40119: The WSRP service defined by {0} is not compatible with this version of the portlet client.
Cause: The portlet client could not communicate with the remote producer using WSRP. This may be because the WSRP service implements a pre-release version of the WSRP 2.0 specification.
Action: If possible, update the WSRP container that is running the service.

Level: 1

Type: ERROR

Impact: Compliance

WCS-40120: External application not found.
Cause: The portlet is configured on the client with an external application, however the application or user credential for it was not found.
Action: Correct the portlet configuration, external application configuration, or user.

Level: 1

Type: ERROR

Impact: Other

WCS-40121: External application authentication failed.
Cause: The portlet is associated with an external application, however the user credentials failed authentication.
Action: Correct the user credentials.

Level: 1

Type: ERROR

Impact: Other

WCS-40122: ADF context get connections context failed.
Cause: An unexpected error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40123: Portlet transfer not supported for transfer mode {0}.
Cause: An MDS transfer was performed that included portlet metadata but is not supported by the portlet MDS transfer listener.
Action: No action required.

Level: 1

Type: WARNING

Impact: Other

WCS-40124: Queue Full [cause={0} submittedTasks={1} queuedTasks={2} queueFreeSpace={3} completedTasks={4} activeThreads={5} corePoolSize={6} keepAliveTime={7} largestPoolSize={8} maxPoolSize={9} poolSize={10} isShutdown={11} isTerminated={12} isTerminating={13}]
Cause: A portlet request was submitted to be processed but the queue of portlet requests was already too large so it was rejected.
Action: If the server is under load then such warnings are fine, however if the system is not under load then the configuration settings such as thread pool size and queue size should be checked in relation to the server's hardware specification.

Level: 1

Type: WARNING

Impact: Other

WCS-40125: Possible loss of portlet customizations for producer {0} : V2 export imported to V1.
Cause: A WSRP V2 producer export may contain portlet customizations but is being imported to a V1 producer which cannot import them.
Action: Check that there are either no customizations to be imported, or that it is acceptable to not import them.

Level: 1

Type: WARNING

Impact: Other

WCS-40126: This portlet must be rendered within an IFRAME.
Cause: This portlet has declared that it must be rendered within an IFRAME. It cannot be rendered inline on an ADF page.
Action: Set the property renderPortletInIFrame on the portlet tag to "auto" or "true".

Level: 1

Type: ERROR

Impact: Other

WCS-40127: Null resource ID for portlet resource request handle "{0}"
Cause: A portlet resource request contained a null resource ID.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40128: Unable to verify or sign resource URL.
Cause: The supplied resource key is invalid.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40129: Unable to proxy request for resource with ID: "{0}" due to an incorrect checksum.
Cause: A portlet resource request was received whose URL was not generated by the portlet client.
Action: Do not attempt to modify portlet resource URLs.

Level: 1

Type: WARNING

Impact: Other

WCS-40131: Error introspecting object of class {0}. Unable to set WSRP UserProfile data correctly.
Cause: An unexpected error occurred.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40132: Unable to set field {0} to value {1} for UserProfile bean of class {2}.
Cause: An exception was thrown while trying to set a UserProfile value.
Action: If possible, resolve the issue by setting the corresponding user property value correctly.

Level: 1

Type: ERROR

Impact: Other

WCS-40133: User attribute {0} cannot be retrieved from the identity store repository.
Cause: The identity store repository cannot provide the required information.
Action: User profile information passed to producers may be incomplete.

Level: 1

Type: WARNING

Impact: Other

WCS-40134: Unable to lookup value for user property {0}.
Cause: User profile information is not available.
Action: Verify that the identity store repository is correctly configured.

Level: 1

Type: WARNING

Impact: Other

WCS-40135: Security context is not available.
Cause: The current ADFContext does not define a security context.
Action: Verify that the application's security settings are correct.

Level: 1

Type: WARNING

Impact: Other

WCS-40136: User profile information is not available.
Cause: The current Security Context does not define user profile information.
Action: Verify that the identity store repository is correctly configured.

Level: 1

Type: WARNING

Impact: Other

WCS-40137: Unable to set field {0} to value {1} for UserProfile bean of class {2}. Expected format: {3}.
Cause: The format of data supplied for UserProfile data is incorrect.
Action: If possible, resolve the issue by setting the user property value correctly.

Level: 1

Type: ERROR

Impact: Other

WCS-40138: External Application Adapter not configured for portlets.
Cause: A portlet uses an External Application, but an adapter is not configured.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40139: Private key not set via Web Adapter.
Cause: No private key was defined.
Action: Set the key to a random value using the 'private.key' Servlet context parameter.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40140: Web Adapter private key is too short.
Cause: The specified private key is too short.
Action: Make sure that the value of 'private.key' Servlet context parameter is at least 10 characters in length.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40141: Resource URL checksums may not be correct across all nodes.
Cause: Data cannot be written to MDS in order to coordinate private key generation.
Action: Make sure MDS is correctly configured and writable.

Level: 1

Type: WARNING

Impact: Configuration

WCS-40142: Error removing lock following private key generation.
Cause: A exception was raised while releasing a lock.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40143: Using locally generated private key.
Cause: It was not possible to co-ordinate distributed creation of a key.
Action: If possible, resolve the issue using information in this log.

Level: 1

Type: WARNING

Impact: Other

WCS-40144: Import of producer {0} failed. The failure has been stored for possible retry.
Cause: A producer import failed, however the operation was instructed to accept and store failures for later retry rather than to fail completely.
Action: The reason for failure must be investigated and corrected, then the import retried.

Level: 1

Type: WARNING

Impact: Other

WCS-40146: Portlet session invalid.
Cause: A producer response indicated that the session was invalid.
Action: Retry the request, but if the problem persists it may indicate a problem with the producer, and the producer status and logs should be checked.

Level: 1

Type: ERROR

Impact: Other

WCS-40147: Could not import portlet with ID "{0}" because the portlet does not exist on the remote producer.
Cause: The producer being imported to is different from that exported from and does not include the specified portlet.
Action: Check if the producer being imported to is of the correct type.

Level: 1

Type: WARNING

Impact: Other

WCS-40149: Exception exporting producer with ID "{0}".
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-40151: A request to the producer URL "{0}" resulted in a status {1} response with fault string "{2}". The fault code given was "{3}".
Cause: The portlet producer raised a SOAP fault in response to a request.
Action: Contact the producer's administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-40152: A request to the producer URL "{0}" resulted in a status {1} response with fault string "{2}". The fault code given was "{3}". The producer generated a timestamp of {4} and associated the following stack trace with the fault message: {5}.
Cause: The portlet producer raised a SOAP fault in response to a request.
Action: Refer to the stack trace and contact the producer's administrator if appropriate.

Level: 1

Type: ERROR

Impact: Other

WCS-40153: A request to the producer URL "{0}" resulted in a status {1} response. There was no fault message returned in the response.
Cause: A request to a portlet producer resulted in an error.
Action: Verify that the producer is accessible and contact the producer's administrator if appropriate.

Level: 1

Type: ERROR

Impact: Other

WCS-40154: The payload for event {0} could not be processed. The event will not be sent to the producer.
Cause: The event payload is not a simple type, and could not be marshalled by JAXB or serialized.
Action: Verify that the payload set on the event is valid.

Level: 1

Type: WARNING

Impact: Other

WCS-40155: The event payload with simple type {0} could not be processed.
Cause: The event payload was requested as a simple type, but could not be unmarshalled.
Action: Verify that the class specified for the payload is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-40157: Failed to process the payload. Could not unmarshal with JAXB and could not deserialize.
Cause: The payload supplied by the producer could not be instantiated in the consumer.
Action: Verify that the class specified for the payload is correct, and is present on the context classpath.

Level: 1

Type: ERROR

Impact: Other

WCS-40158: Event payload class {0} could not be loaded.
Cause: The payload classname was supplied by the producer but could not be loaded (or is null).
Action: Either make the payload class available, or specify an alternative classname to unmarshal the payload.

Level: 1

Type: ERROR

Impact: Other

WCS-40160: Failed to process the payload. Could not marshal with JAXB and could not serialize.
Cause: The payload supplied for an event could not be encoded to send to the producer.
Action: Verify that the class specified has a JAXB binding, or is serializable if the producer supports serialized payloads.

Level: 1

Type: ERROR

Impact: Other

WCS-40161: Payload class {0} does not match declared XML type {1}
Cause: The payload class specified when requesting the payload value is a simple type class that is not consistent with the declared XML type of the payload.
Action: Verify that the class specified for the payload is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-40162: Portlet {0} needs one or more user profile items which are not available.
Cause: One or more user properties that a portlet requires for complete functionality is not defined in the current context.
Action: Specify values for the missing properties.

Level: 1

Type: WARNING

Impact: Other

WCS-40163: The connection type specified ({0}) is not supported for automatic registration.
Cause: The portlet has been configured to automatically register its producer, but the connection name supplied to not correspond to a connection of a supported type.
Action: Check that the connection name has been correctly specified. Automatic registration is supported for WSRPProducerConnection and WebProducerConnection.

Level: 1

Type: WARNING

Impact: Other

WCS-40164: Unexpected error occurred while processing the producer metadata. One or more producers may be down or unavailable. Data for these producers will be excluded from the application export archive. Use the WLST command exportPortalClientMetadata to export data for these producers when available. Producers affected: {0}
Cause: The producer may be down or unavilable.
Action: Use the WLST command exportPortalClientMetadata to export the producer.

Level: 1

Type: WARNING

Impact: Other

WCS-40165: Digest algorithm {0} is not available, attempting to use {1} instead.
Cause: A particular message digest algorithm is not available on this system.
Action: Ensure that a security provider for the missing algorithm is available.

Level: 1

Type: WARNING

Impact: Other

WCS-40166: Digest algorithm {0} is not available.
Cause: A particular message digest algorithm is not available on this system.
Action: Ensure that a security provider for the missing algorithm is available.

Level: 1

Type: ERROR

Impact: Other

WCS-40167: Portlets require ADFContext but ADFContext has not been intialized.
Cause: Portlets are running in an ADF environment but ADFContext has not been intialized.
Action: Check that the ADF Bindings filters are correctly configured in web.xml

Level: 1

Type: WARNING

Impact: Other

WCS-40168: Private key not set.
Cause: No private key was defined.
Action: Set a private key via the external config object if appropriate.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40500: Unable to read portlet deployment descriptor from path "{0}".
Cause: The path to the portlet deployment descriptor was wrong.
Action: Check that the portlet deployment descriptor exists and is readable at the given directory.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40501: Error processing deployment descriptor "{0}".
Cause: There was a problem parsing the deployment descriptor.
Action: Check that the portlet deployment descriptor conforms to the appropriate schema.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40502: Null value passed to method {0}.
Cause: A null value was passed to the specified method.
Action: Check that a non-null value is passed to the specified method.

Level: 1

Type: ERROR

Impact: Programmatic

WCS-40503: Unable to load resource bundle "{0}".
Cause: The specified resource bundle could not be found.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40504: Parameter of invalid type passed to method {0}.
Cause: One of the parameters passed to the specified method was of an incorrect type.
Action: Check that the correct set of parameter types are being passed to the specified method.

Level: 1

Type: ERROR

Impact: Programmatic

WCS-40505: Unable to create instance of class "{0}".
Cause: Unable to create instance of the specified class.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40507: Unrecognized character encoding "{0}".
Cause: The specified character was not recognized.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40508: Window state "{0}" is not allowed in current context.
Cause: The specified window state is not allowed.
Action: Check that the use of the specified window state is allowed by the consumer.

Level: 1

Type: ERROR

Impact: Programmatic

WCS-40509: Portlet mode "{0}" is not allowed in current context.
Cause: The specified portlet mode is not allowed.
Action: Check that the use of the portlet mode is allowed by the consumer.

Level: 1

Type: ERROR

Impact: Programmatic

WCS-40510: Illegal call to {0}: response is already committed.
Cause: The response was already committed.
Action: Do not call the specified method on a committed response.

Level: 1

Type: ERROR

Impact: Programmatic

WCS-40511: Content type "{0}" is not allowed in current context.
Cause: The response was trying to set a content type that is not allowed by the request.
Action: Correct the portlet code.

Level: 1

Type: ERROR

Impact: Programmatic

WCS-40512: Value "{0}" not recognized as a session scope.
Cause: The specified value is an invalid value for the session scope.
Action: Use one of the session scope values defined by the javax.portlet.PortletSession interface.

Level: 1

Type: ERROR

Impact: Programmatic

WCS-40515: Portlet mode "{0}" referenced by portlet "{1}" is not defined in the deployment descriptor.
Cause: The specified portlet mode for the portlet was not defined in the portlet deployment descriptor.
Action: Check that the configuration allows for the specified mode.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40516: Error initializing Java Object Cache.
Cause: Java Object Cache failed to start.
Action: Consult the Java Object Cache log file for more information.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40517: Error loading preferences from path "{0}".
Cause: Preference data could not be accessed properly.
Action: Check the persistence store is configured correctly.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40518: Error saving preferences to path "{0}".
Cause: Preference data could not be accessed properly.
Action: Check the persistence store is configured correctly.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40519: Error deleting preferences under path "{0}".
Cause: Preference data could not be deleted.
Action: Check the persistence store is configured correctly.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40520: Cannot find JNDI data source with specified name "{0}" or the Oracle Portal repository data source "{1}".
Cause: The JNDI data source in the configuration could not be found at the specified location.
Action: Check the container configuration for the data source is correct.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40521: Error getting connection from data source with JNDI path "{0}".
Cause: There was an error getting the connection from the specified data source.
Action: Check that the data source referenced is available.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40522: Error getting connection from Oracle Portal repository with the name "{0}".
Cause: There was an error connecting to the Oracle Portal repository.
Action: Check that the Oracle Portal repository is available.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40526: An internal error has occurred in method {0}.
Cause: The specified method caused an internal error.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40530: Method {0} cannot be called after method {1}.
Cause: The specified methods were not called in the correct order.
Action: Check that the specified methods are called in the correct order.

Level: 1

Type: ERROR

Impact: Other

WCS-40531: No such portlet "{0}".
Cause: The specified portlet was not available.
Action: Check that the portlet is available.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40532: Invalid handle "{0}".
Cause: Session, portlet, or registration handle specified was invalid.
Action: Use the associated error/stack trace to determine why the handle was invalid and resolve the issue.

Level: 1

Type: ERROR

Impact: Other

WCS-40533: Illegal call to {0}: an output stream is already in use.
Cause: The specified method cannot be called once the portlet has started writing binary data.
Action: Correct the portlet code.

Level: 1

Type: ERROR

Impact: Programmatic

WCS-40534: Illegal call to {0}: a writer is already in use.
Cause: The specified method cannot be called once the portlet has started writing character data.
Action: Correct the portlet code.

Level: 1

Type: ERROR

Impact: Programmatic

WCS-40535: Illegal call to {0}: a content type has not been set.
Cause: The setContentType() method was not called before the specified method.
Action: Correct the portlet code.

Level: 1

Type: ERROR

Impact: Programmatic

WCS-40538: Error attempting to create handle "{0}".
Cause: The specified handle could not be created in the persistent store.
Action: Use the associated error and/or stack trace to determine the cause of this error.

Level: 1

Type: ERROR

Impact: Other

WCS-40539: Error checking for existence of handle "{0}".
Cause: An error occured whilst checking for the existence of the given handle in the persistent store.
Action: Use the associated error and/or stack trace to determine the cause of this error.

Level: 1

Type: ERROR

Impact: Other

WCS-40540: Error attempting to delete handle "{0}".
Cause: The specified handle could not be deleted from the persistent store.
Action: Use the associated error and/or stack trace to determine the cause of this error.

Level: 1

Type: ERROR

Impact: Other

WCS-40541: Portlet "{0}" is not modifiable in this context.
Cause: The specified portlet is read only in this context.
Action: Check that the portlet is modifiable.

Level: 1

Type: ERROR

Impact: Programmatic

WCS-40542: Invalid URL "{0}".
Cause: The specified URL is invalid.
Action: Correct the portlet code.

Level: 1

Type: ERROR

Impact: Programmatic

WCS-40543: Unable to read Web application deployment descriptor from path "{0}".
Cause: The path to the Web application deployment descriptor was incorrect.
Action: Check that the Web application deployment descriptor exists and is readable at the given directory.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40544: Value "{1}" for JNDI environment entry "{0}" is not supported. Allowable values are "{2}".
Cause: The JNDI environment entry was not one of the allowable values specified.
Action: Check the JNDI environment entry is one of the allowable values specified.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40545: Location specified for persistent store "{0}" must be a directory.
Cause: The location of the specified persistent store is not a directory.
Action: Check the specified persistent store is a directory and that there is not a file in existence at the given location.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40546: Unable to create persistent store root directory at "{0}".
Cause: It was not possible to create the persistent store root directory at the specified location.
Action: Check that the parent directory is writable.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40547: Cannot resolve relative path ({0}) for persistent store, oracle.home system property is not set.
Cause: The oracle.home was not set for the specified relative path.
Action: Set the oracle.home system property.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40548: Error connecting to database {0}/{1}@{2}.
Cause: There is an error connecting to the specified database.
Action: Check that the specified database connection details are correct.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40549: Error obtaining details of persisted objects.
Cause: There was an error obtaining details of persisted objects.
Action: Use the associated error and/or stack trace to determine the cause of this error.

Level: 1

Type: ERROR

Impact: Data

WCS-40550: Unexpected database error.
Cause: An unexpected database error occurred.
Action: Use the associated error and/or stack trace to determine the cause of this error.

Level: 1

Type: ERROR

Impact: Data

WCS-40551: Unable to create persistent store directory "{0}" for group "{1}".
Cause: It was not possible to create the persistent store directory for the specified group.
Action: Check that the parent directory is writable.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40552: Unable to read mime mappings from path "{0}".
Cause: The path to the mime mappings file was wrong.
Action: Check that the mime mappings file exists and is readable at the given directory.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40554: Portlet with handle "{0}" is hidden.
Cause: The portlet entity was hidden and not currently available.
Action: Make sure the portlet is made available if that is the desired usage.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40555: Error processing file "{0}" at line {1} column {2}.
Cause: An error occurred while processing the file at the specified line and column.
Action: Fix the error to the file based on the message specified.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40556: Object named "{0}" could not be found in the persistent store.
Cause: Container object could not be found in the persistent store.
Action: This is an internal error. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Data

WCS-40561: Request timed out while shutting down portlet "{0}".
Cause: A timeout occurred while waiting for a portlet to shutdown.
Action: No action required.

Level: 1

Type: WARNING

Impact: Other

WCS-40562: Exception thrown while shutting down portlet "{0}".
Cause: The specified portlet raised an exception while it was being shutdown.
Action: Resolve the issue if possible by looking at the exception raised.

Level: 1

Type: WARNING

Impact: Other

WCS-40563: Exception thrown while deleting entity "{0}".
Cause: The specified entity raised an exception while it was being deleted.
Action: Resolve the issue if possible by looking at the exception raised.

Level: 1

Type: WARNING

Impact: Other

WCS-40564: Exception thrown while releasing session with handle "{0}".
Cause: The specified session raised an exception while is was being released.
Action: Resolve the issue if possible by looking at the exception raised.

Level: 1

Type: WARNING

Impact: Other

WCS-40565: Invalid security role reference: "{0}".
Cause: The security role specified is invalid.
Action: Check and reconfigure the security roles set for the portlets.

Level: 1

Type: WARNING

Impact: Configuration

WCS-40566: Locale "{0}" can only be matched to "{1}" Resource Bundle.
Cause: The locale requested by the client is not supported at the language level by the portlet. Fallback to English or Base bundle has occurred.
Action: The portlet must support the locale in the request.

Level: 1

Type: WARNING

Impact: Configuration

WCS-40570: The oracle.portlet.server.useStatelessProxying request attribute is being ignored when creating a resource URL.
Cause: Stateless proxying is not possible for resources served using the ResourceServingPortlet.serveResource() method.
Action: Use the RenderResponse.encodeURL() method to create the resource URL.

Level: 1

Type: WARNING

Impact: Other

WCS-40571: The oracle.portlet.server.useStatelessProxying request attribute is being ignored when creating a resource URL.
Cause: Stateless proxying is not possible for resources that require URL rewriting.
Action: If URL rewriting of the resource response is not required, set the oracle.portlet.server.resourceRequiresRewriting response attribute to false.

Level: 1

Type: WARNING

Impact: Other

WCS-40572: Portlet with handle "{0}" cannot be accessed using WSRP version {1}, it requires at least WSRP version {2}.
Cause: The portlet uses features that are not supported by the version of the WSRP protocol being used to access it.
Action: Check that the WSRP producer is accessed using the minimum protocol version (or higher).

Level: 1

Type: ERROR

Impact: Configuration

WCS-40573: Fast Connection Failover detected. Retrying operation once.
Cause: The portlet container detected that the database used for personalization has performed Fast Connection Failover. The portlet container will retry the operation once.
Action: Contact the database administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-40574: Java Object Cache support configured for this portlet application, but no display name specified in web.xml. Java Object Cache support will be disabled.
Cause: Java Object Cache support has been configured to persist portlet registration and preference data, but no display name has been configured for the portlet application in web.xml. Java Object Cache support will be disabled for this portlet application.
Action: Specify a unique display-name for this portlet application in web.xml

Level: 1

Type: ERROR

Impact: Configuration

WCS-40575: PortletApplicationImpl.initHandler error processing config handler "{0}".
Cause: Error processing the specified config handler.
Action: Check the JNDI environment entry mentioned.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40576: PortletApplicationImpl.initHandler error calling config handler setters "{0}" and "{1}".
Cause: Error calling the specified config handler setters.
Action: Check the locations of these files.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40577: PortletApplicationImpl.loadMimeCsMappings() error closing input stream "{0}".
Cause: The path to the mime mappings file was wrong.
Action: Check that the mime mappings file exists and is readable at the given directory.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40578: PortletApplicationImpl.isConfigFileChanged error calling config handler has changed methods for "{0}" and "{1}".
Cause: Error calling the specified config handler with change methods.
Action: Check the locations of these files.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40579: Error adding registration data for "{0}" to persistent store.
Cause: An error occured when accessing the persistent store.
Action: Check the configuration of the persistent store.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40580: Error accessing registration data "{0}" in persistent store.
Cause: An error occured when accessing the persistent store.
Action: Check the configuration of the persistent store.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40581: Error deleting registration data "{0}" from persistent store.
Cause: An error occured when accessing the persistent store.
Action: Check the configuration of the persistent store.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40582: Error adding portlet data for "{0}" to persistent store.
Cause: An error occured when accessing the persistent store.
Action: Check the configuration of the persistent store.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40583: Error accessing portlet data "{0}" in persistent store.
Cause: An error occured when accessing the persistent store.
Action: Check the configuration of the persistent store.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40584: Error deleting portlet data "{0}" from persistent store.
Cause: An error occured when accessing the persistent store.
Action: Check the configuration of the persistent store.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40585: Error accessing persistent store whilst modifying registration "{0}".
Cause: An error occured when accessing the persistent store.
Action: Check the configuration of the persistent store.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40586: Portlet "{0}" was created in context of registration "{1}" and cannot be accessed in the context of registration "{2}".
Cause: The attempt to access the persistent data store is not valid in the current context.
Action: Determine why the persisted data is invalid and recreate it if necessary.

Level: 1

Type: ERROR

Impact: Data

WCS-40587: Invalid producer offered portlet handle "{0}".
Cause: An attempt was made to use a producer offered portlet which is not valid in the current context.
Action: Supply a valid producer offered portlet handle.

Level: 1

Type: ERROR

Impact: Data

WCS-40588: Unable to upgrade portlet data, invalid portlet handle "{0}".
Cause: An error occured whilst upgrading persisted portlet data due to the portlet handle having an invalid format.
Action: Ensure that the portlet handle starts with "E:".

Level: 1

Type: ERROR

Impact: Upgrade

WCS-40589: Unable to upgrade portlet data for handle "{0}", producer offered portlet handle "{1}" is not valid.
Cause: An error occured whilst upgrading persisted portlet data.
Action: Ensure that the producer offered portlet handle is valid.

Level: 1

Type: ERROR

Impact: Upgrade

WCS-40590: Unable to upgrade consumer persisted registration data with handle {0}.
Cause: An error occured whilst upgrading consumer persisted registration data.
Action: Use the associated error/stack trace to determine why the data could not be upgraded.

Level: 1

Type: ERROR

Impact: Upgrade

WCS-40591: Unable to upgrade consumer persisted portlet data with handle {0}.
Cause: An error occured whilst upgrading consumer persisted portlet data.
Action: Use the associated error/stack trace to determine why the data could not be upgraded.

Level: 1

Type: ERROR

Impact: Upgrade

WCS-40593: Unable to import legacy portlet data with id {0} and offered portlet handle {1}.
Cause: The import context indicated an export data format that is understood but the data could not be read.
Action: Verify the integrity of the export data that is being imported.

Level: 1

Type: WARNING

Impact: Upgrade

WCS-40594: An error occured whilst writing the consumer persisted state for a {0} object with handle {1}.
Cause: There was a problem serialising an object.
Action: Use the associated error and/or stack trace to determine why the object could not be serialised.

Level: 1

Type: ERROR

Impact: Data

WCS-40595: An error occured whilst reading the consumer persisted state of a {0} object.
Cause: There was a problem deserialising an object.
Action: Use the associated error and/or stack trace to determine why the object could not be deserialised.

Level: 1

Type: ERROR

Impact: Data

WCS-40596: Handle {0} in {1} object state stored by the consumer does not match the handle for the object {2}.
Cause: An inconsistency was detected when reading the consumer maintained state of an object.
Action: Determine why the consumer supplied inconistent data and recreate the object if necessary.

Level: 1

Type: ERROR

Impact: Data

WCS-40701: Error initializing BridgeLifecycleListener: "{0}".
Cause: The named class could not be initialized.
Action: Check that the class name is correct and this it is available in the classpath.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40702: Error getting additional context object for key: "{0}".
Cause: An error occurred whilst decoding information sent from an ADF portlet consumer.
Action: Contact Oracle Support Services

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40703: An exception occurred whilst parsing configuration file: "{0}".
Cause: An error occurred whilst reading a configuration file.
Action: Ensure that the contents of the configuration file are correct.

Level: 1

Type: ERROR

Impact: Configuration

WCS-40704: Unable to deserialize event payload: {0}
Cause: An error occurred whilst trying to deserialize the payload of an event.
Action: Use the associated stack trace to determine the root cause of the problem.

Level: 1

Type: WARNING

Impact: Data

WCS-40705: Unable to serialize event payload of class: {0}
Cause: An error occurred whilst trying to serialize the payload of an event.
Action: Use the associated stack trace to determine the root cause of the problem.

Level: 1

Type: WARNING

Impact: Data

WCS-40706: Could not instantiate configured ADFPortletBridgeExceptionHandler class: {0}
Cause: An instance of the configured ADFPortletBridgeExceptionHandler could not be created.
Action: Check that the named class is available and that it defines a public zero argument constructor and a handleException(PortletRequest, PortletResponse, Throwable) method.

Level: 1

Type: WARNING

Impact: Configuration

WCS-40707: Could not find method {0} on class {1}
Cause: The named class does not define a required method.
Action: Check that the class defines the required method.

Level: 1

Type: WARNING

Impact: Configuration

WCS-40708: Could not call method {0} on class {1}
Cause: The named method could not be called on an instance of the class.
Action: Use the associated stack trace to determine the cause of the method invocation failure.

Level: 1

Type: WARNING

Impact: Configuration

WCS-40709: Could not access method {0} on class {1}
Cause: The named method was not accessible on an instance of the class.
Action: Check that the named method has public access.

Level: 1

Type: WARNING

Impact: Configuration

WCS-40710: Exception while writing PPR error response
Cause: An error occurred whilst writing a PPR error response.
Action: No action required.

Level: 1

Type: WARNING

Impact: Other

WCS-40711: Could not load ADFPortletBridgeExceptionManager class specified in services config: {0}
Cause: A class loading error occurred.
Action: Check that the ADFPortletBridgeExceptionManager class is available.

Level: 1

Type: WARNING

Impact: Configuration

WCS-40712: Unhandled exception in {0}. Reverting to default handler.
Cause: An unexpected exception occurred.
Action: No action required.

Level: 1

Type: WARNING

Impact: Other

WCS-40713: Muffling exception in method {0}, context = {1}.
Cause: An error occurred but processing was allowed to continue.
Action: Use the context information to determine if remedial action is required.

Level: 1

Type: WARNING

Impact: Other

WCS-40714: ADF PPR exception happened in remote portlet communication.
Cause: An error occurred during ADF ppr request processing.
Action: Use the context information to determine if remedial action is required.

Level: 1

Type: WARNING

Impact: Other

WCS-42301: The external application ID {0} found while rendering the credential provisioning page is invalid.
Cause: The external application being referred was probably deleted.
Action: Check the configuration of the service that is being accessed and fix up the external application reference.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42302: No back URL exists in the process scope.
Cause: The credential provisioning page could not establish the back URL because of the following possible reasons: 1) The page was run either in the standalone mode or as a dialog. 2) There was some unexpected error while setting the back URL in the process scope.
Action: Ensure you haven't run the credential provisioning page in a standalone mode. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Configuration

WCS-42303: cannot retrieve the back URL to redirect the credential provisioning page
Cause: An I/O error occurred while trying to obtain the back URL to redirect the credential provisioning page.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42304: The external application ID is found to be null while rendering the credential provisioning page.
Cause: The credential provisioning page was probably run standalone, or it was invoked from a portlet added from a producer that was not associated with an external application.
Action: While running the credential provisioning page, ensure that: 1) It is not run in the standalone mode. 2) It is invoked from the link in portlets added from the producers associated with the external application.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42305: The page is available only to authenticated users.
Cause: You had not logged into the application before accessing the external application credential provisioning page.
Action: Ensure that you have logged in before accessing the external application credential provisioning page.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42306: cannot initialize credential provisioning page
Cause: An unexpected error occurred while trying to initialize the external application. Review the underlying exception in the logs for exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42307: cannot store credentials of external application {0} for user {1}
Cause: There was an unexpected error while trying to store external application credentials for the user. Review the underlying exception in the logs for exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42501: An unexpected error occurred.
Cause: Review the root cause of the exception for more details.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42502: A required parameter is missing. Parameter=[{0}]
Cause: An attempt was made to invoke a method without passing all the required parameters.
Action: This is likely a defect. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

WCS-42503: call to API {0} not supported at design time
Cause: This operation was not supported at design time.
Action: This is likely a defect. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

WCS-42504: The external application context cannot be configured.
Cause: An unexpected error occurred in initializing the external application manager while setting up the context. Review the underlying exception in the logs for the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42505: The page is available only to authenticated users.
Cause: A null user subject was obtained while trying to automatically log in to the external application.
Action: Ensure that the user has logged into the application before accessing the automated login functionality.

Level: 1

Type: WARNING

Impact: Security

WCS-42506: An unexpected error occurred while trying to automatically log in to the external application.
Cause: An error occurred while trying to log in to the external application. Review the underlying exception in the logs for more details.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42507: The external application that needs to be accessed cannot be found.
Cause: The external application ID was not available in the servlet request.
Action: Ensure that the external application ID is passed in the form of the extappid parameter while invoking the automated login servlet.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42508: cannot automatically log in to the external application
Cause: The login URL was not specified for the external application being used for automated login.
Action: To use the automated login functionality for an external application, ensure that the login URL is specified.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42509: A list of all external application connections cannot be obtained.
Cause: An unexpected error occurred while trying to obtain the list of all external application connections. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42510: Connection for the external application {0} cannot be obtained.
Cause: An unexpected error occurred while trying to obtain the connection for the external application. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42511: Cannot encode string {0} using encoding scheme {1}
Cause: Encoding Scheme was not supported
Action: Check if your JVM has support for the given scheme and try again

Level: 1

Type: WARNING

Impact: Logging

WCS-42512: An error occurred after notifying service of change in the external application {0} credentials.
Cause: An unexpected error occurred while the service was trying to process change in the external application credentials.
Action: Review the underlying exception in the logs. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Logging

WCS-42513: An unexpected condition occurred while trying to automatically log in to the external application {0} - {1}
Cause: A unexpected condition while trying to log in to the external application. Review the underlying exception in the logs for more details.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Logging

WCS-42601: The login URL {0} obtained for the external application {1} is invalid.
Cause: The data in the external application definition was damaged.
Action: Check the underlying connection data and ensure that the URL for the specified external application is valid.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42602: The option for enabling automated login for the external application is not supported.
Cause: The login URL for the external application was not specified.
Action: To enable automated login for the external application, set the login URL for the application.

Level: 1

Type: WARNING

Impact: Programmatic

WCS-42603: cannot process authentication failure for external application {0}
Cause: Public credentials were not enabled for this external application.
Action: To obtain external application credentials for a public user, configure the external application to specify public credentials.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42604: Credentials cannot be stored or deleted.
Cause: The external application identifier was not specified for the credential.
Action: Specify the external application identifier for the credential and then try to store or remove the credential.

Level: 1

Type: ERROR

Impact: Programmatic

WCS-42605: user {0} not authorized to access external application {1}
Cause: The user did not have access to the external application.
Action: Contact your administrator for the necessary permission. If you are a public user, the administrator needs to allow public access to this external application by specifying public credentials.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42606: The credentials specified by the user {0} for the external application {1} are invalid so clearing the password for user to reprovision on the next login attempt.
Cause: Credentials for the external application have changed.
Action: The invalid password has been cleared. Invoke the credential provisioning page to accept the latest set of credentials.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42607: Shared access credentials for the external application {0} are invalid.
Cause: Shared access credentials for the external application may have changed.
Action: Contact the administrator to update the shared access credentials.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42608: Public access credentials for external application {0} are invalid.
Cause: Public access credentials for the external application may have changed.
Action: Contact the administrator to update the public access credentials.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42609: Credentials not found for the user {0} for the external application {1}.
Cause: external application credentials were not provisioned for the user.
Action: Provide a link to the credential provisioning page so that the user can specify credentials.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42610: Unable to obtain shared or public credentials for the external application {0}.
Cause: The shared or public credentials could not be located or might have been damaged.
Action: Contact the administrator to specify the credentials via Enterprise Manager or WLST.

Level: 1

Type: WARNING

Impact: Logging

WCS-42613: Credentials cannot be deleted for the external application {0}.
Cause: The credential to be deleted was not found in the credential store.
Action: No action required as the credential does not exist.

Level: 1

Type: WARNING

Impact: Logging

WCS-42614: Field {0} in external application {1} is invalid.
Cause: The external application field used for the store or fetch credential operation does not exist.
Action: Check the field name used for the operation and ensure that it has been defined.

Level: 1

Type: WARNING

Impact: Logging

WCS-42651: The listener {0} cannot be added to the external application.
Cause: An unexpected error occurred while trying to register the listener. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42652: The listener {0} cannot be deregistered.
Cause: An unexpected error occurred while trying to deregister the listener. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42653: An external application with the name {0} already exists.
Cause: The name specified for the external application was already used by another application.
Action: Specify a unique name for the external application.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42654: URL {0} specified for external application {1} is invalid.
Cause: The HTTP URL set for the external application was invalid.
Action: Specify a valid HTTP URL.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42655: Property {0} specified for external application {1} is invalid.
Cause: The property specified for the external application was either null or empty.
Action: Set a valid value for the specified property.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42656: The authentication method {0} specified for the external application {1} is invalid.
Cause: The authentication method set for the external application was not one of the following: GET, BASIC, or POST.
Action: Set the authentication method as GET, POST, or BASIC. The default authentication method is POST.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42657: Field {0} already exists in external application {1}.
Cause: A duplicate field was encountered in the additional fields definition.
Action: Ensure that the names of the additional fields defined for the external application are unique.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42658: default value not specified for Field {0} in external application {1}
Cause: The specified additional field of the external application was marked as hidden.
Action: Specify a default value for the additional field marked as hidden. If there is no default value, mark the field as to be displayed to users.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42659: The {0} credential specified for external application {1} is invalid.
Cause: Either the user name or password was not specified.
Action: Ensure that both the user name and password are specified for shared or public credentials in an external application.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42660: external application {0} not found
Cause: The name passed for retrieving the external application was invalid or the underlying external application was deleted.
Action: Pass a valid external application name for retrieving the application.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42661: The ID of the external application cannot be set.
Cause: The external application ID could not be set because the external application already had an ID set.
Action: The ID of an external application cannot be modified. To set a new ID, delete the external application and re-create the application with a new ID.

Level: 1

Type: WARNING

Impact: Programmatic

WCS-42662: The external application {0} cannot be created.
Cause: An external application with the specified name already existed.
Action: Specify a unique name for your external application.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42663: The external application {0} cannot be created.
Cause: An unexpected error occurred while trying to create the external application. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42664: The external application {0} cannot be modified.
Cause: An unexpected error occurred while trying to modify the external application. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42665: cannot delete external application {0}
Cause: An unexpected error occurred while trying to delete the external application. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42666: An error has occurred while trying to retrieve the external application {0}.
Cause: An unexpected error occurred while trying to obtain the given external application. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42667: An error has occurred while trying to retrieve all available external applications.
Cause: An unexpected error occurred while trying to obtain all external applications. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42668: An error has occurred while trying to check if the specified external application name {0} is already used by another external application.
Cause: An unexpected error occurred while trying to check if the external application name was already used. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42669: An error has occurred while trying to obtain a list of external application names.
Cause: An unexpected error occurred while trying to obtain a list of external application names. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42670: An error has occurred while trying to obtain a map containing the ID-name pair of the external application.
Cause: An unexpected error occurred while trying to obtain a map containing the ID-name pair of the external application. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42671: An external application with the display name {0} already exists.
Cause: The display name specified for the external application was already used by another application.
Action: Specify a unique display name for the external application.

Level: 1

Type: WARNING

Impact: Configuration

WCS-42701: An unexpected naming exception has occurred while trying to create the external application connection {0}.
Cause: An unexpected naming exception occurred while trying to create an external application connection. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42702: cannot update external application connection {0}
Cause: An unexpected naming exception occurred while trying to update the external application connection. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42703: cannot delete external application connection {0}
Cause: An unexpected naming exception occurred while trying to delete the external application connection. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42704: An unexpected naming exception has occurred while trying to look up the external application connection {0}.
Cause: An unexpected naming exception occurred while trying to look up the external application connection. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42705: An unexpected naming exception has occurred while trying to list all available external application connections.
Cause: An unexpected naming exception occurred while trying to list external application connections. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42706: Invalid fragment obtained while trying to build the external application connection from the reference {0}.
Cause: Could not parse the required external application connection attributes from the reference because the entry in connections.xml may have been tampered with.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Configuration

WCS-42707: An unknown error occurred while trying to obtain connections context.
Cause: An unknown exception occurred while trying to obtain connections context. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42708: A Connection Store cannot be configured for the external application {0}.
Cause: An unexpected error occurred while trying to set up the connection store for the application. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Configuration

WCS-42801: An error occurred while creating a transferable object for the external application connection {0}.
Cause: An unexpected error occurred while creating a transferable object for an external application connection. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42802: An error occurred while generating the transfer data for the external application connection {0}. DataFlavor={1}, TransferData={2}
Cause: An unexpected error occurred while generating the transfer data for an external application connection. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-42803: cannot initialize the Resource Catalog adapter.
Cause: An unexpected error occurred while initializing the Resource Catalog adapter. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Logging

WCS-43001: Unable to find the service with ID "{0}" in the service registry.
Cause: Either the service ID is wrong or the corresponding META-INF/service-definition.xml file is not available in the classpath.
Action: Ensure the service ID is correct and the corresponding META-INF/service-definition.xml file is available in the classpath. Note: service-definition.xml file is mostly available from service libraries (within .jar file) of each service, make sure the required service libraries are in the classpath.

Level: 1

Type: WARNING

Impact: Other

WCS-43002: Cannot add service to the registry with the same ID. Service with ID "{0}" is already registered from source "{1}". Failed to add service read from source "{2}".
Cause: Either the service-definition contains a service Id that conflicts with another service definition or the same service library (.jar containing the service-definition.xml) is available from multiple classpath locations.
Action: Ensure the service ID is correct in the corresponding META-INF/service-definition.xml file. Also ensure the same jar file is not available from multiple classpath locations.

Level: 1

Type: WARNING

Impact: Other

WCS-43003: Failed to parse the service-definition.xml found at location "{0}". Due to : {1}
Cause: Either the service-definition.xml does not conform to the schema or its not well-formed xml file or its not readable.
Action: Verify the corresponding service-definition.xml file conforms to the schema with well-formed xml and read access is set on it.

Level: 1

Type: WARNING

Impact: Other

WCS-43004: ServiceContext resource configuration file "{0}" not found, cannot proceed.
Cause: The main configuration file that defines the default implementation of ServiceContext class is missing.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43005: ServiceContext resource configuration file "{0}" found, but the data is missing. Cannot proceed.
Cause: The main configuration file that defines the default implementation of ServiceContext class is misconfigured, all the required data is not available in this file.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43006: ServiceContext resource configuration file "{0}" found, but the class defined "{1}" is not an instance of oracle.webcenter.framework.service.ServiceContext.
Cause: The main configuration file that defines the default implementation of ServiceContext class is misconfigured, the supplied class is not an instance oracle.webcenter.framework.service.ServiceContext.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43007: service-definition being processed from source location "{0}" does not conform to the schema. Missing ''definitions'' tag.
Cause: This is caused due to wrong configuration of service-definition.xml file.
Action: Update the corresponding file and ensure it starts with 'definitions' tag with namespace as 'http://xmlns.oracle.com/webcenter/framework/service' (e.g.: <definitions xmlns="http://xmlns.oracle.com/webcenter/framework/service">).

Level: 1

Type: WARNING

Impact: Other

WCS-43008: Required attribute "{0}" missing from tag "{1}".
Cause: This is caused when the user is required to set the mandatory attribute for the given tag, but and its not set.
Action: Modify the appropriate configuration file to and supply the mandatory attribute with corresponding value.

Level: 1

Type: WARNING

Impact: Other

WCS-43009: Attempt to invoke "{0}" method on class "{1}", when its locked.
Cause: This class or method is locked and cannot be invoked in the current state.
Action: Do not invoke methods on this class in a state its not accessible, please check the class documentation for more help.

Level: 1

Type: WARNING

Impact: Other

WCS-43010: Scope object cannot be null.
Cause: This is caused when an attempt is made to set scope with null value.
Action: Supply a valid scope object, or create a scope from ServiceContext.

Level: 1

Type: WARNING

Impact: Other

WCS-43011: Unable to find the "{0}" view definition from service: {1}.
Cause: The required view definition is missing from the service-definition file.
Action: Check the appropriate service-definition.xml file to have an entry of the required view definition. Refer to service documentation for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-43012: Error occurred processing the service-definition.xml file from source location "{0}". Due to: {1}.
Cause: Either the service-definition is malformed or does not conform to the schema defined.
Action: Update the corresponding service-definition.xml with correct details.

Level: 1

Type: WARNING

Impact: Other

WCS-43013: ExtensionRegistry instance found "{0}" for registry Id "{1}", is not an instance of {2} class.
Cause: This is caused due to wrong configuration of adf-service-config tag in the adf-config.xml file.
Action: Check the adf-config.xml file for an entry of adf-service-config tag. Search for extension-registry tag here with ID "oracle.webcenter.framework.service.ServiceRegistry", this tag's registry-class attribute should point to a class that is extending from ServiceRegistry class.

Level: 1

Type: WARNING

Impact: Other

WCS-43014: Either the supplied registry Class "{0}" for extension-registry ID "{1}", is not an instance of oracle.webcenter.framework.service.ExtensionRegistry or the class is not available in the classpath. Please check the adf-config.xml for corresponding configuration details.
Cause: This is caused due to wrong configuration of extension-registry in the adf-config.xml file.
Action: Check the adf-config.xml file for an entry of adf-service-config tag. Search for extension-registry tag and ensure this tag's registry-class attribute point's to a class that is an instance of 'oracle.webcenter.framework.service.ExtensionRegistry' class. Also this class should be available in the classpath, otherwise it will fail to load.

Level: 1

Type: WARNING

Impact: Other

WCS-43015: Unable to find the Extension Registry information in the adf-config for registry ID "{0}". Please check the adf-config.xml for corresponding configuration details.
Cause: This is caused due to missing tension-registry in configuration in the adf-config.xml file.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43016: Either the supplied handler Class "{0}" for extension-registry ID "{1}", is not an instance of oracle.webcenter.framework.service.ExtensionHandle or the class is not available in the classpath. Please check the adf-config.xml for corresponding configuration details.
Cause: This is caused due to wrong configuration of extension-registry in the adf-config.xml.
Action: Check the adf-config.xml file for an entry of adf-service-config tag. Search for extension-registry tag and ensure this tag's handler-class attribute point's to a class that is an instance of 'oracle.webcenter.framework.service.ExtensionHandler' class. Also this class should be available in the classpath, otherwise it will fail to load.

Level: 1

Type: WARNING

Impact: Other

WCS-43017: Extension tag name cannot be null or empty value.
Cause: Wrong extension configuration, mandatory tag name cannot hold null or empty string.
Action: Refer to the service framework documentation for details on extension-registry configuration.

Level: 1

Type: WARNING

Impact: Other

WCS-43018: No Extension Registry information available for element type "{0}", with the ServiceRegistry. Please check the adf-config.xml for extension registry configuration details.
Cause: This is caused due to missing extension-registry configuration in the adf-config.xml for the specified registry Id.
Action: Check the adf-config.xml file for an entry of adf-service-config tag. Search for extension-registry tag for the appropriate registry Id that is missing and ensure all the registry details are provided.

Level: 1

Type: WARNING

Impact: Other

WCS-43019: ADFConfig does not contain adf-service-config details. Ensure adf-config.xml file contains adf-service-config tag with namespace : {0}.
Cause: This is caused due to missing adf-service-config tag from adf-config.xml file.
Action: Check the adf-config.xml file for an entry of adf-service-config tag.

Level: 1

Type: WARNING

Impact: Other

WCS-43020: No ADF Config information.
Cause: ADFConfig could not be acquired, either adf-config.xml file is missing or application is not configured properly.
Action: >Examine the adf-config.xml file and add or update the WebCenter section.

Level: 1

Type: ERROR

Impact: Configuration

WCS-43021: No Oracle WebCenter Framework information in adf-config file.
Cause: The application adf-config.xml was found, but the Oracle WebCenter Framework section could not be read or is missing.
Action: Examine the adf-config.xml file and add or update the WebCenter section.

Level: 1

Type: ERROR

Impact: Configuration

WCS-43022: resourceInfoPopup jsp inclusion missing from the page.
Cause: The jspx or jsff page containing the rah:resourceActionBehavior tag does not include the inline popup fragment: /oracle/webcenter/framework/service/view/jsf/fragments/resourceInfoPopup.jsff that is required to show resource mini-views.
Action: If this is a custom usage of rah:resourceActionBehavior, add a jsp:include to the page and a reference to the resourceMiniViewPopup page in the page definition. If this is not a custom usage of rah:resourceActionBehavior, contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-43023: Could not find component : {0}.
Cause: The specified component is missing from the current page.
Action: If this is a customized jsff or jspx page, verify that the component is included at the correct location.

Level: 1

Type: WARNING

Impact: Other

WCS-43024: The ADF Faces application to be used for WebCenter RAH requests has already been specified as {0} in another web.xml.
Cause: Multiple web.xml files in the application ear have been marked as being the web application to use for RAH requests.
Action: Examine the web.xml files from each war file and remove from all but the web application to be used for handling RAH requests.

Level: 1

Type: WARNING

Impact: Other

WCS-43026: No resource ID found for resource group: {0}.
Cause: This error occurs when the resource view does not define corresponding group ID.
Action: Supply valid resource group ID.

Level: 1

Type: WARNING

Impact: Other

WCS-43027: Failed to generate an absolute URL to a resource view.
Cause: A runtime problem occurred whilst generating the absolute URL to a resource view.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43028: Scope with name "{0}" already exists.
Cause: This error occurs when user tries to create a scope with a name that is already created. Duplicate scopes are not allowed.
Action: Chose a different name for the scope.

Level: 1

Type: WARNING

Impact: Other

WCS-43029: Scope with name "{0}" does not exist.
Cause: This error occurs when user tries to read a scope with a name that is not created earlier.
Action: Create the scope with the appropriate name and then access it.

Level: 1

Type: WARNING

Impact: Other

WCS-43030: Could not handle complex element "{0}". Neither element has a class attribute nor any of the ElementTypeResolvers could handle it.
Cause: This can occur due to missing extension-registry configuration in the adf-config.xml or there is no set/add method on the corresponding application bean to handle complex node.
Action: Have a proper extension handler registered for this complex node or have set/add method on the bean with the tag name.

Level: 1

Type: WARNING

Impact: Other

WCS-43031: XML processing error: unable to create instance of the class: {0}. {1}
Cause: This can occur due to missing extension-registry configuration in the adf-config.xml or there is no set/add method on the corresponding application bean to handle complex node.
Action: Have a proper extension handler registered for this complex node or have set/add method on the bean with the tag name.

Level: 1

Type: WARNING

Impact: Other

WCS-43032: Class: {0} does not have set or add method for tag: {1}.
Cause: This can occur due to missing extension-registry configuration in the adf-config.xml file or there is no set/add method on the corresponding application bean to handle complex node.
Action: Have a proper extension handler registered for this complex node or have set/add method on the bean with the tag name.

Level: 1

Type: WARNING

Impact: Other

WCS-43033: An error occurred processing the xml, due to: {0}.
Cause: Runtime problem invoking the operation.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43034: Unable to set or get an ADF Preference value.
Cause: The ADF Preference service raised an exception whilst initializing, getting or setting a preference value.
Action: Check MDS classpath includes PreferenceNode.xsd.

Level: 1

Type: WARNING

Impact: Other

WCS-43036: Cannot provide the resource link. No FacesContext and no webapp base URL set.
Cause: Unable to build up a URL to WebCenter from outside of the web application.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43038: Unable to find help for the current topic.
Cause: Either the help system is not setup or it is not accessible.
Action: Examine the WebCenter Configuration for Help and make sure that Help System is up and running.

Level: 1

Type: ERROR

Impact: Configuration

WCS-43039: Scope Provider resource configuration file "{0}" not found, cannot proceed.
Cause: The main configuration file that defines the default implementation of ScopeMetadataProvider class is missing.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43040: Scope Provider resource configuration file "{0}" found, but the data is missing. Cannot proceed.
Cause: The main configuration file that defines the default implementation of ScopeMetadataProvider class is misconfigured, all the required data is not available in this file.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43041: ScopeMetadataProvider resource configuration file "{0}" found, but the class defined "{1}" is not an instance of oracle.webcenter.framework.service.ScopeMetadataProvider.
Cause: The main configuration file that defines the default implementation of ScopeMetadataProvider class is misconfigured, the supplied class is not an instance oracle.webcenter.framework.service.ScopeMetadataProvider.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43042: Resource Action not created due to missing attributes.
Cause: The Group ID (Service ID) and the Resource ID are not present as f:attribute values in the consuming JSPX page.
Action: Check the JSPX page where this originated from and make sure you add the groupId and resourceId attributes and that they are not null.

Level: 1

Type: WARNING

Impact: Other

WCS-43043: Failed to load resource action handler class "{0}"; using default.
Cause: The resource action handler class specified failed to load.
Action: Check the classpath to inspect whether this class is available; then check accompanying exceptions in the log to further debug the cause.

Level: 1

Type: WARNING

Impact: Other

WCS-43044: Failed to parse view renderer "{0}" as a valid TaskFlow ID; returning null.
Cause: The specified task flow ID cannot be parsed properly.
Action: Check the value of the view renderer specified and investigate how you arrived at that value.

Level: 1

Type: WARNING

Impact: Other

WCS-43045: Failed to parse view renderer "{0}" as a valid TaskFlow ID; treating it as a View ID instead.
Cause: The specified task flow ID cannot be parsed properly.
Action: Check the META-INF/service-definition.xml of the service to verify whether it is a view ID or a TaskFlow ID by checking the documented syntax of both.

Level: 1

Type: WARNING

Impact: Other

WCS-43046: Can not find the message key {0} in the resource bundle "{1}" (from original bundle: {2} ).
Cause: The string identified by the given key is not found in the resource bundle.
Action: If this is a custom resource bundle, add a message with the given key to the resource bundle, otherwise contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-43047: The JPS Service Locator cannot be obtained.
Cause: The error was caused while obtaining the JPS Service Locator. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-43048: User Principal could not be found for authenticated user.
Cause: This indicates an error with the Identity Store, or Java Platform Security setup.
Action: This is an internal warning. The Administrator needs to verify the Identity Store setup.

Level: 1

Type: WARNING

Impact: Other

WCS-43049: An error occurred reading the Connections Context.
Cause: This indicates an error with reading the Connection Context.
Action: Refer to exception detail. If insufficient details to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-43050: An error occurred reading a service's configuration.
Cause: This indicates an error with reading a service's configuration.
Action: Refer to exception detail. If insufficient details to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-43051: cannot access Java Object Cache
Cause: An exception occurred while accessing Java object cache.
Action: Review the exception thrown for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-43052: cannot create userprofile region in Java Object Cache
Cause: An exception occurred while creating userprofile region in Java object cache.
Action: Review the exception thrown for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-43053: cannot destroy userprofile region in Java Object Cache.
Cause: An exception occurred while removing userprofile region from Java object cache.
Action: Review the exception thrown for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-43054: An error occurred while trying to lookup connection {0}.
Cause: The name may not have been pointing to a valid connection, or some other error occurred when trying to retrieve the connection object.
Action: Ensure that the connection defined in connections.xml is valid and that the necessary classes can be loaded.

Level: 1

Type: WARNING

Impact: Other

WCS-43055: Resource can not be displayed because the authorizerClass {0} is not found.
Cause: Class specified by authorizerClass is not found.
Action: Check the class path of the application to verify inclusion of the authorizerClass.

Level: 1

Type: WARNING

Impact: Other

WCS-43056: Database type {0} is not recognized.
Cause: WebCenter has been configured with a database platform that is not recognized.
Action: Ensure that the database platform type is set correctly.

Level: 1

Type: WARNING

Impact: Other

WCS-43057: Error closing entity manager factory
Cause: An unexpected exception occurred while closing the entity manager factory.
Action: Review the exception thrown for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-43058: Could not load LifecycleListener class for "{0}" from the service definition.
Cause: An unexpected exception occurred while attempting to access the LifecycleListener.
Action: Review the exception thrown for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-43059: The WebCenterConfig will be reinitialized. Expected class "{0}", class loader "{1}", parent class loader "{2}". Actual class "{3}", class loader "{4}", parent classLoader "{5}".
Cause: This indicates an recoverable error with retrieving the WebCenterConfig.
Action: No action required.

Level: 1

Type: WARNING

Impact: Other

WCS-43060: The connection named "{0}" cannot be found.
Cause: The connection name may be incorrect.
Action: Ensure that the name matches a connection defined for the application.

Level: 1

Type: WARNING

Impact: Other

WCS-43061: Unable to find the WebCenter data source
Cause: The data source may not have been configured or cannot be read.
Action: Check the configuration of the WebCenter data source.

Level: 1

Type: ERROR

Impact: Other

WCS-43062: Unable to parse link
Cause: The link URL or network connection is wrong.
Action: Check the network connection, proxy setting and the link URL.

Level: 1

Type: WARNING

Impact: Other

WCS-43063: Error retrieving enterprise ID/prefix from ADF Context.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-43064: The version ({0}) of WebCenter Framework Design Time used to create the Portal application is not the same as the version ({1}) of WebCenter Framework Runtime.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-43065: The build label ({0}) of WebCenter Framework Design Time used to create the Portal application is not the same as the build label ({1}) of WebCenter Framework Runtime.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-43067: Error "{1}" getting service with ID "{0}".
Cause: An unexpected error occurred getting a service by ID.
Action: Check the configuration of the WebCenter data source.

Level: 1

Type: ERROR

Impact: Other

WCS-43068: Error "{0}" reading service category configuration.
Cause: An unexpected error occurred reading the service category configuration.
Action: Review the exception thrown for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-43069: WebCenterUserNotFoundWarning: Unable to find user {0}.
Cause: User with the given name, unique identifier or distinguished name does not exist in the identity store.
Action: Ensure the user name, unique identifier or distinguished name is correct.

Level: 1

Type: WARNING

Impact: Other

WCS-43070: Unable to find enterprise role {0}.
Cause: Role with the given name does not exist in the identity store.
Action: Ensure the role name is correct.

Level: 1

Type: WARNING

Impact: Other

WCS-43071: Could not obtain display name for user {0} in locale {1}, will resort to default display name
Cause: There was an error trying to fetch locale specific display name from identity store.
Action: Turn on logging and check the logs for the cause of the exception

Level: 1

Type: WARNING

Impact: Other

WCS-43072: cannot access Coherence Cache
Cause: An exception occurred while accessing Coherence cache.
Action: Review the exception thrown for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-43073: cannot destroy userprofile region in Coherence Cache.
Cause: An exception occurred while removing userprofile region from Coherence cache.
Action: Review the exception thrown for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-43075: Unexpected error occurred while encoding the URL {0} due to {1}.
Cause: Unexpected error occurred while encoding the URL.
Action: Review the exception thrown for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-43076: Unexpected error occurred while decoding the URL {0} due to {1}.
Cause: Unexpected error occurred while decoding the URL.
Action: Review the exception thrown for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-43077: Unexpected error occurred while renaming the document {0} to {1} due to {2}.
Cause: Unexpected error occurred while renaming the document.
Action: Review the exception thrown for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-43078: An error occurred while sanitizing the HTML input
Cause: Unexpected error occurred while sanitizing the HTML input
Action: Review the exception thrown for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-44001: cannot load role provider implementation for service ID: {0}
Cause: The provider class configured in role-mapping-metadata tag of the specified service definition was not available to the classloader.
Action: Ensure that the provider class specified in the service-definition.xml file is available to the classloader.

Level: 1

Type: ERROR

Impact: Security

WCS-44002: The Role Mapping provider encountered an exception while performing security role mapping for service {0}.
Cause: This is caused by an error experienced by service-specific Role Mapping provider.
Action: Inspect the server logs and rectify the problem encountered by the service Role Mapping provider.

Level: 1

Type: ERROR

Impact: Security

WCS-44003: The Role Mapping provider cannot find the service role: {0}. Exception from the provider: {1}.
Cause: The Role Mapping provider cannot find the service role. Review the exception from the provider to determine the exact cause.
Action: Inspect the server logs and rectify the problem encountered by the service Role Mapping provider.

Level: 1

Type: ERROR

Impact: Security

WCS-44004: An internal JPS error occurred while retrieving information from the Application Policy Store.
Cause: Review the underlying exception in the logs to determine the cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44005: cannot find security extension in Service Registry for service ID: {0}
Cause: No security extension was registered for the given service. Perhaps the service library was not available in the classpath.
Action: Check the service library is available in the classpath. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44006: There is no mapped service role for the WebCenter Portal role {1} to which the user {0} is assigned.
Cause: A user was assigned to a WebCenter Portal role that was not yet mapped to any service role.
Action: Ensure that the WebCenter Portal role is mapped to a service role.

Level: 1

Type: WARNING

Impact: Security

WCS-44007: An internal JPS error occurred while initializing the Application Policy Store.
Cause: The Application Policy Store (jps-config.xml) was probably not configured correctly.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44009: Error obtaining JPS Service instance: {0}.
Cause: The value returned for the JPS Service instance was null. This may be caused by configuration error in jps-config.xml.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44010: A JPS error occurred while deleting users from the service ID/service role: {0} / {1}.
Cause: The error was caused while accessing the application policy store for deleting users. Review the underlying exception in the logs to determine the exact cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44011: Error getting handle to application policy for application {0}.
Cause: Either the application policy is not available or policy store is not configured correctly. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44012: Error getting handle to default policy store.
Cause: Either the policy store is not accessible or not configured correctly. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44101: Invalid PeoplePicker Scope {0} passed.
Cause: The scope is not of the valid type. It can be GLOBAL or SUB_SCOPED
Action: Pass a valid scope

Level: 1

Type: WARNING

Impact: Configuration

WCS-44102: Invalid PeoplePicker Scope ID {0} passed.
Cause: An invalid Scope ID has been passed.
Action: Ensure a valid scope/community ID is passed.

Level: 1

Type: WARNING

Impact: Configuration

WCS-44103: Unknown error encountered while selecting user(s) in people picker.
Cause: Review the root cause of the exception for more details.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44104: Scope Id is a required parameter for scoped people search.
Cause: Scope Id not provided.
Action: Provide Scope Id.

Level: 1

Type: WARNING

Impact: Security

WCS-44105: And unknown error occurred while trying to validate if user {0} exists
Cause: Review the root cause of the exception for more details.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44106: Unknown error encountered while selecting group(s) in group picker.
Cause: Review the root cause of the exception for more details.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44107: And unknown error occurred while trying to validate if group {0} exists
Cause: Review the root cause of the exception for more details.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44108: The search exceeded the time limit. Check the identity store connection details or refine your search criterion.
Cause: The underlying identity store and policy store could be down.
Action: Check that underlying repositories are accessible. Check logs and contact Oracle Support

Level: 1

Type: WARNING

Impact: Security

WCS-44109: The search exceeded the size limit. Refine your search criterion.
Cause: The search results in a large dataset that is not supported by the underlying identity store.
Action: Refine your search criterion to something more narrow.

Level: 1

Type: WARNING

Impact: Security

WCS-44110: An unexpected error occurred while searching for users/roles. Check logs for further details.
Cause: An unexpected error occurred while searching for identities. Consult the underlying cause.
Action: If the underlying cause does not provide any action, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Security

WCS-44151: An error occurred while retrieving the Identity Store.
Cause: This is caused when the Identity Store configured in jps-config.xml is not accessible or is not running. Review the underlying exception in the logs to determine the exact cause.
Action: Ensure that the Identity Store is configured correctly in jps-config.xml and is running. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44152: An error occurred while sending an e-mail.
Cause: The error occurred because the e-mail account or the e-mail service was not configured correctly or the e-mail server was not running.
Action: Ensure that your e-mail account and the e-mail service are configured properly and the e-mail server is running.

Level: 1

Type: ERROR

Impact: Security

WCS-44153: An error occurred while generating the HMAC token.
Cause: The JVM did not support MessageDigest algorithms, such as MD5 or SHA, or the UTF8 encoding.
Action: Ensure the JVM supports UTF8 encoding and MD5/SHA message digest algorithms. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44154: An error occurred while getting the scope roles for scope ID {0}.
Cause: Either the policy store was configured incorrectly or was inaccessible or the scope ID passed was invalid.
Action: Ensure that the policy store is configured correctly and is running. Also, ensure that the scope ID passed is valid.

Level: 1

Type: ERROR

Impact: Security

WCS-44155: The permission class is null for the service ID: {0}.
Cause: The permission class was not defined in the service-definition.xml file.
Action: Ensure that the permission class is defined in the service-definition.xml file for the service.

Level: 1

Type: ERROR

Impact: Security

WCS-44156: The value of resource bundle is null for the service ID: {0}.
Cause: The resource bundle was not defined in the service-definition.xml file.
Action: Ensure that the resource bundle is defined in the service-definition.xml file.

Level: 1

Type: ERROR

Impact: Security

WCS-44157: The value of permission target is null for the service ID: {0}.
Cause: The permission target was not defined in the service-definition.xml file.
Action: Ensure that the permission target is defined in the service-definition.xml file.

Level: 1

Type: ERROR

Impact: Security

WCS-44158: The value of permission action is not defined for the service ID: {0}.
Cause: The permission action (permission-action-list tag) was not defined in the service-definition.xml file.
Action: Ensure that the permission actions are defined in the service-definition.xml file by using the permission-action-list tag.

Level: 1

Type: ERROR

Impact: Security

WCS-44159: The value of permission admin action is not defined for the service ID: {0}.
Cause: The permission admin action (permission-manage-action tag) was not defined in the service-definition.xml file.
Action: Ensure that the permission admin actions are defined in the service-definition.xml file by using the permission-manage-action tag.

Level: 1

Type: ERROR

Impact: Security

WCS-44160: The role mapping class is not defined for the service ID: {0}.
Cause: The role mapping class was not defined in the service-definition.xml file.
Action: Ensure that the role mapping class is defined in the service-definition.xml file.

Level: 1

Type: ERROR

Impact: Security

WCS-44161: The role mapping resource bundle is not defined for the service ID: {0}.
Cause: The role mapping resource bundle was not defined in the service-definition.xml file.
Action: Ensure that the role mapping resource bundle is defined in the service-definition.xml file.

Level: 1

Type: ERROR

Impact: Security

WCS-44162: Security Extension is not defined for the service ID: {0}.
Cause: The Security Extension (security-definition node) was not defined in the service-definition.xml file of the service.
Action: Ensure that the Security Extension (security-definition node) is properly defined in the service-definition.xml file.

Level: 1

Type: ERROR

Impact: Security

WCS-44163: An error occurred while retrieving service extension definition(service-definition.xml).
Cause: The service jars are not correctly packaged or the jars are corrupt.
Action: Ensure that webcenter framework shared library is correctly defined and the library jars are not corrupt.

Level: 1

Type: ERROR

Impact: Security

WCS-44164: An error occurred while retrieving the spi file .
Cause: The are multiple spi files.
Action: Ensure that only spi file with the name oracle.webcenter.security.selfregistration.custom.SelfRegActionHandlerSpi.properties exists.

Level: 1

Type: ERROR

Impact: Security

WCS-44165: The principal is not of type JpsRole
Cause: The principal object passed to the api is not of type JpsRole.
Action: Ensure that the parameter passed to the api is of type JpsRole.

Level: 1

Type: WARNING

Impact: Security

WCS-44166: Application Policy for {0} does not exist. Creating a new application policy.
Cause: The application did not package any policies.
Action: None as a new policy has been created. However ensure that application did not indeed package any policies and this was not a case of policies not being migrated. Contact Oracle Support in that case.

Level: 1

Type: WARNING

Impact: Security

WCS-44167: Public registration is not enabled for this site.
Cause: The public registration option is not enabled.
Action: Ensure that public registration is enabled in the general tab of Webcenter administration.

Level: 1

Type: WARNING

Impact: Security

WCS-44168: The principal argument is null
Cause: The principal object passed to the api is null.
Action: Ensure that the parameter passed to the api is not null.

Level: 1

Type: WARNING

Impact: Security

WCS-44169: Error while determining security attributes for user {0}
Cause: The user {0} passed to determine security attributes does not exist in the underlying identity store.
Action: Ensure the user name is valid.

Level: 1

Type: WARNING

Impact: Security

WCS-44170: Error occurred while retrieving the security attributes of user {0}
Cause: An error occurred while querying the identity store or the policy store to determine the user's security attributes. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44171: Error occurred while determining security attributes for service {0}
Cause: An error occurred while querying the policy store to determine the principals that were granted view access for the given service. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44172: Error occurred while determining security attributes for service {0} in scope {1}
Cause: An error occurred while querying the policy store to determine the principals that were granted view access for the given service and scope. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44173: Error occurred while determining security attributes for artifact {0} belonging to service {1}
Cause: An error occurred while querying the policy store to determine the principals that were granted view access for the given service and artifact. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44174: Error encountered while getting the HMAC initial key from the credential store
Cause: There is a problem while accessing the credential store. Review the underlying exception in the logs to determine the exact cause.
Action: Ensure the credential store is setup properly. Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44175: Error occurred while obtaining mapped service {0} roles for WebCenter Portal role {1}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44176: Error occurred while obtaining mapped application roles for service {0} and service role with ID {1} in scope {2}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44177: Error occurred while adding role mapping entry for service {0} and service role {1} to webcenter role {2}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services. This error can be ignored if upgrade is being re-run.

Level: 1

Type: ERROR

Impact: Security

WCS-44178: Error occurred while removing role mapping entry for service {0} and service role {1} from WebCenter Portal role {2}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44179: Error occurred while removing role mapping entries for service {0} in scope {1}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44180: Error occurred while removing role mapping entries for scope {0}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44181: Error occurred while fetching role mapping metadata for scope {0}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44182: Error occurred while adding role mapping metadata to scope {0}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44183: Cannot copy role mapping metadata for scope {0} as the metadata already exists
Cause: Role mapping metadata already existed for the given scope.
Action: Remove the role mapping metadata for the scope and then perform this operation again. Alternatively, you can pass a different scope for which the role mapping metadata does not already exist.

Level: 1

Type: ERROR

Impact: Security

WCS-44184: Error occurred while fetching role mapping metadata for service {0} in scope {1}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44185: Error occurred while adding role mapping metadata for service {0} in scope {1}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44186: Unable to obtain service {0} role mapping metadata for scope {1}
Cause: The query to obtain role mapping metadata for the scope returned a path for which the metadata did not exist.
Action: Ensure the service role mapping metadata exists for the scope.

Level: 1

Type: WARNING

Impact: Security

WCS-44187: The role mapping metadata for service {0} in scope {1} is being modified by another user. Try the operation again after some time.
Cause: Another user acquired the write lock on the service role mapping metadata.
Action: Try the operation after some time.

Level: 1

Type: WARNING

Impact: Security

WCS-44188: Cannot copy the role mapping metadata for service {0} in scope {1}
Cause: The service role mapping metadata for the scope already existed.
Action: Remove the service role mapping for the scope and then perform the operation again. Alternatively, you can pass a different service and scope for which the role mapping metadata does not already exist.

Level: 1

Type: ERROR

Impact: Security

WCS-44189: Cannot find the WebCenter Portal application role {0}
Cause: The WebCenter Portal application role passed to Role Manager did not exist.
Action: Ensure that a valid application role is passed to Role Manager.

Level: 1

Type: ERROR

Impact: Security

WCS-44190: Error copying role mapping metadata from role {0} to role {1} in scope {2}
Cause: Role mapping metadata could not be copied. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. To perform role mapping, use the Roles tab in the portal settings.

Level: 1

Type: ERROR

Impact: Security

WCS-44191: Error deleting role mapping metadata from role {0} in scope {1}
Cause: The role mapping metadata could not be deleted. Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44192: Error while determining enterprise role mapping support. Enterprise groups, and not the individual group members, will be added directly as members.
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: If a service configured does not support enterprise role mapping, then take action based on the underlying exception details.

Level: 1

Type: WARNING

Impact: Security

WCS-44193: The permission action is invalid for the service ID: {0}.
Cause: Either permission action name or icon was not specified in the service-definition.xml file.
Action: Ensure that the permission action name and icon is defined correctly in the service-definition.xml file for the service. The permission action should be specified as <permission-action name="view" icon="/adf/webcenter/view_qualifier.png"/>

Level: 1

Type: ERROR

Impact: Security

WCS-44194: The application level permission class is null for the service ID: {0}.
Cause: The application permission class was not defined in the service-definition.xml file.
Action: Ensure that the application permission class is defined in the service-definition.xml file for the service. The application permission class should be specified as <application-permission-impl>permission class</application-permission-impl> in <application-permission> node.

Level: 1

Type: ERROR

Impact: Security

WCS-44195: The application level permission target is not defined for the service ID: {0}.
Cause: The application permission target was not defined in the service-definition.xml file.
Action: Ensure that the application permission target is defined in the service-definition.xml file for the service. The application permission target should be specified as <application-permission-target-id>permission target</application-permission-target-id> in <application-permission> node.

Level: 1

Type: ERROR

Impact: Security

WCS-44196: The application level permission actions is not defined for the service ID: {0}.
Cause: The application permission actions list was not defined in the service-definition.xml file.
Action: Ensure that the application permission actions list is defined in the service-definition.xml file for the service. The application permission actions should be specified as <application-permission-action-list>permission actions</application-permission-action-list> in <application-permission> node.

Level: 1

Type: ERROR

Impact: Security

WCS-44197: The scope level permission class is not defined for the service ID: {0}.
Cause: The scope permission class was not defined in the service-definition.xml file.
Action: Ensure that the scope permission class is defined in the service-definition.xml file for the service. The scope permission class should be specified as <scope-permission-impl>permission class</scope-permission-impl> in <scope-permission> node.

Level: 1

Type: ERROR

Impact: Security

WCS-44198: The scope level permission target is not defined for the service ID: {0}.
Cause: The scope permission target was not defined in the service-definition.xml file.
Action: Ensure that the scope permission target is defined in the service-definition.xml file for the service. The scope permission target should be specified as <scope-permission-target-id>permission target</scope-permission-target-id> in <scope-permission> node.

Level: 1

Type: ERROR

Impact: Security

WCS-44199: The scope level permission actions is not defined for the service ID: {0}.
Cause: The scope permission actions list was not defined in the service-definition.xml file.
Action: Ensure that the scope permission actions list is defined in the service-definition.xml file for the service. The scope permission actions should be specified as <scope-permission-action-list>permission actions</scope-permission-action-list> in <scope-permission> node.

Level: 1

Type: ERROR

Impact: Security

WCS-44200: The resource level permission class is not defined for the service ID: {0}.
Cause: The resource permission class was not defined in the service-definition.xml file.
Action: Ensure that the resource permission class is defined in the service-definition.xml file for the service. The resource permission class should be specified as <resource-permission-impl>permission class</resource-permission-impl> in <resource-permission> node.

Level: 1

Type: ERROR

Impact: Security

WCS-44201: The resource level permission target is not defined for the service ID: {0}.
Cause: The resource permission target was not defined in the service-definition.xml file.
Action: Ensure that the resource permission target is defined in the service-definition.xml file for the service. The resource permission target should be specified as <resource-permission-target-id>permission target</resource-permission-target-id> in <resource-permission> node.

Level: 1

Type: ERROR

Impact: Security

WCS-44202: The resource level permission actions is not defined for the service ID: {0}.
Cause: The resource permission actions list was not defined in the service-definition.xml file.
Action: Ensure that the resource permission actions list is defined in the service-definition.xml file for the service. The resource permission actions should be specified as <resource-permission-action-list>permission actions</resource-permission-action-list> in <resource-permission> node.

Level: 1

Type: ERROR

Impact: Security

WCS-44203: The application role operations list is not specified at the application level for the service ID: {0}.
Cause: The application role operations list is not specified at the application level. It was not defined in the service-definition.xml file.
Action: Ensure that the application role operations list is defined at the application level in the service-definition.xml file for the service.

Level: 1

Type: ERROR

Impact: Security

WCS-44204: The application role operations list is not specified at the scope level for the service ID: {0}.
Cause: The application role operations list is not specified at the scope level was not defined in the service-definition.xml file.
Action: Ensure that the application role operations list is defined at the scope level in the service-definition.xml file for the service.

Level: 1

Type: ERROR

Impact: Security

WCS-44205: The application role operations list is not specified at the resource level for the service ID: {0}.
Cause: The application role operations list is not specified at the resource level was not defined in the service-definition.xml file.
Action: Ensure that the application role operations list is defined at the resource level in the service-definition.xml file for the service.

Level: 1

Type: ERROR

Impact: Security

WCS-44206: The application role operation specified is invalid for the service ID: {0}.
Cause: Operation name or application role or icon has not been specified correctly for the application role operation in service-definition.xml
Action: Ensure that the application role operation is specified correctly with operation name, application role and icon in the service-definition.xml file for the service. An application role operation entry looks like this - <application-operation name="manage" approle="AppConnectionManager" icon="/adf/webcenter/manage.png"/>

Level: 1

Type: ERROR

Impact: Security

WCS-44207: Error occurred while adding resource {0} security override entry for service {1} in scope {2}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44208: Error occurred while removing resource {0} security override entry for service {1} in scope {2}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44209: Error occurred while checking if resource {0} override security for service {1} in scope {2}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44210: Error occurred while removing security override entries for scope {0}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44211: Error occurred while removing security override entries for service {0} in scope {1}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44212: The security override metadata for service {0} in scope {1} is being modified by another user. Try the operation again after some time.
Cause: Another user acquired the write lock on the service security override metadata.
Action: Try the operation after some time.

Level: 1

Type: WARNING

Impact: Security

WCS-44213: Invalid Security Handler for service {0}. Expected Type: {1} Actual Type: {2}.
Cause: Security Handler defined in service-definition was of incorrect type
Action: Define the correct security handler in the service-definition as specified

Level: 1

Type: ERROR

Impact: Security

WCS-44214: Security Extension not found for service {0}.
Cause: Security Extension not defined in service-definition.
Action: Define the security extension appropriately in the service-definition.

Level: 1

Type: ERROR

Impact: Security

WCS-44215: Security Handler not found for service {0}.
Cause: Security Handler specified in the security extension is either undefined or could not be found.
Action: Ensure the correct security handler class is defined in the security extension of service-definition.

Level: 1

Type: ERROR

Impact: Security

WCS-44216: Could not determine security authorization type for service {0}. It needs to be one of the following - PERMISSION, APPLICATION_ROLE or ROLEMAPPING.
Cause: The security extension either does not contain any authorization model or contains more than one.
Action: Depending on the authorization model, security extension must be updated to specify the appropriate security model.

Level: 1

Type: ERROR

Impact: Security

WCS-44217: Permission security model not defined at {0} level for service {1}.
Cause: Permission check or provisioning is being attempted at specified level where as the security extension in the service-definition does not define given level permission security model
Action: Either define specified level permission security metadata or do not attempt security provisioning or check at given level for the service.

Level: 1

Type: ERROR

Impact: Security

WCS-44218: Application Roles security model not defined at {0} level for service {1}.
Cause: Security check or provisioning is being attempted at specified level where as the security extension in the service-definition does not define given level application role security model
Action: Either define specified level application role security metadata or do not attempt security provisioning or check at given level for the service.

Level: 1

Type: ERROR

Impact: Security

WCS-44219: Error occurred revoking permissions for {0} service resource {1}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44220: Application Role not defined for {0} service action {1} at {2} level.
Cause: Application Role for the given service action and level not defined in security extension of service-definition.
Action: Define the application role mapping for the given service action at the given level else do not attempt security provisioning or check for the service at given level.

Level: 1

Type: ERROR

Impact: Security

WCS-44221: Error occurred checking {0} action for {1} service at {2} level.
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44222: An error occurred while retrieving the policies or permissions.
Cause: This is caused when the policy store is not accessible or is not running or the service definition is not defined properly.
Action: Ensure that the policy store and service definition is configured properly and is running.

Level: 1

Type: ERROR

Impact: Security

WCS-44223: An error occurred while saving the permissions.
Cause: This is caused when the policy store is not accessible or is not running or the service definition is not defined properly.
Action: Ensure that the policy store and service definition is configured properly and is running.

Level: 1

Type: ERROR

Impact: Security

WCS-44224: An error occurred while saving the permissions.
Cause: This is caused when the service definition is not defined properly.
Action: Ensure that the service definition is configured properly.

Level: 1

Type: ERROR

Impact: Security

WCS-44225: An error occurred while setting service id.
Cause: This is caused when the service definition is not defined properly.
Action: Ensure that the service definition is configured properly.

Level: 1

Type: ERROR

Impact: Security

WCS-44226: Error while accessing data from OPSS Policy Store.
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

WCS-44227: An error occurred while getting portal assets and WebCenter Portal services
Cause: This is caused when the service definition is not defined properly.
Action: Ensure that the service definition is configured properly.

Level: 1

Type: ERROR

Impact: Security

WCS-44228: An error occurred while determining list of portal assets that override security for service {0} in scope {1}
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44229: An error encountered while getting mapped action.
Cause: This is caused when the service definition is not defined properly.
Action: Ensure that the service definition is configured properly.

Level: 1

Type: WARNING

Impact: Security

WCS-44230: An error encountered while trying to retrieve {0} service policies at {1} level for scope {2} and asset {3}.
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44231: An error encountered while trying to grant {0} service policies at {1} level for scope {2} and asset {3}.
Cause: Review the underlying exception in the logs to determine the exact cause. The grant could already exist.
Action: Take action based on the underlying exception details. If the grant already exists, revoke the grant using WLST and perform operation again.

Level: 1

Type: ERROR

Impact: Security

WCS-44232: An error encountered while trying to revoke {0} service policies at {1} level for scope {2} and asset {3}.
Cause: Review the underlying exception in the logs to determine the exact cause. The grant being revoked probably does not exist.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44233: An error encountered while trying to obtain subject for user {0}, returning anonymous user subject instead.
Cause: Review the underlying exception in the logs to determine the exact cause.
Action: Take action based on the underlying exception details.

Level: 1

Type: WARNING

Impact: Security

WCS-44234: An error encountered while trying to create role {0}.
Cause: Review the underlying exception in the logs to determine the exact cause. The role may be already exists or there is a problem with policy store.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44235: An error encountered while trying to get application roles.
Cause: Review the underlying exception in the logs to determine the exact cause. The roles may not exists or there is an issue with the policy store.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44236: An error encountered while trying to create role {0}.
Cause: Review the underlying exception in the logs to determine the exact cause. The role may be already exists or there is a problem with the policy store.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44237: An error encountered while trying to get members.
Cause: Review the underlying exception in the logs to determine the exact cause. The members may not exist or there is a problem with the policy store.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44238: An error encountered while trying to get members.
Cause: Review the underlying exception in the logs to determine the exact cause. The member may not exist or there is a problem with the policy store.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44239: An error encountered while trying to delete members.
Cause: Review the underlying exception in the logs to determine the exact cause. The member may already exist or there is a problem with the policy store.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44240: Cannot access the resource
Cause: The service was not defined properly.
Action: Ensure that the service definition is configured properly.

Level: 1

Type: ERROR

Impact: Security

WCS-44241: Failed to issue token.
Cause: Trust Service Token Manager failed to issue the token.
Action: Take action based on the underlying exception details.

Level: 1

Type: WARNING

Impact: Security

WCS-44242: TrustService instance is null.
Cause: Failed to get TrustService instance from the JPS context.
Action: Take action based on the underlying exception details.

Level: 1

Type: WARNING

Impact: Security

WCS-44243: TokenManager instance is null.
Cause: Failed to get TokenManager instance from the TrustService.
Action: Take action based on the underlying exception details.

Level: 1

Type: WARNING

Impact: Security

WCS-44244: Could not execute search
Cause: The identity store is not up or is not configured properly.
Action: Ensure that the identity store is up and configured properly.

Level: 1

Type: ERROR

Impact: Security

WCS-44245: Could not add to role
Cause: The policy object already exists or the policy store is not configured properly.
Action: Ensure that the policy is not already added and policy store is configured properly.

Level: 1

Type: ERROR

Impact: Security

WCS-44246: An internal JPS error occurred while exporting / importing application roles.
Cause: This may have been caused when retrieving information from the Application Policy Store or while granting permissions to roles.
Action: Review the exception to determine exact cause.

Level: 1

Type: WARNING

Impact: Security

WCS-44247: Could not delete application role {0}.
Cause: This may have been caused because the role to be deleted does not exist any more.
Action: Review the exception to determine exact cause.

Level: 1

Type: WARNING

Impact: Security

WCS-44248: The documents role mapping failed during import for portal : {0} and application role {1}.
Cause: This is caused by an error experienced by service-specific Role Mapping provider.
Action: Inspect the server logs and rectify the problem encountered by the service Role Mapping provider.

Level: 1

Type: ERROR

Impact: Security

WCS-44249: No application role found for scope : {0}.
Cause: This may be due to an error that could have occurred during Portal creation or import due to which the roles were not created.
Action: Inspect the logs to confirm which Portal is this error being thrown for and try manually accessing the Portal. If the Portal is inaccessible, re try import or, re create the Portal.

Level: 1

Type: WARNING

Impact: Security

WCS-44250: Unable to obtain MDSSession to initialize {0} store.
Cause: This is caused by an underlying MDS Configuration exception while trying to initialize the customization config.
Action: Review the exception to determine exact cause.

Level: 1

Type: ERROR

Impact: Security

WCS-44251: Start time {0} specified for an impersonation grant cannot be after end time {1}
Cause: Start time for impersonation grant is after end time
Action: Ensure start time specified for an impersonation grant is before end time

Level: 1

Type: WARNING

Impact: Security

WCS-44252: You cannot add, update, or remove yourself as an impersonator
Cause: Adding, updating, or removing oneself as an impersonator is not allowed
Action: Ensure impersonator being added, updated or removed is a valid impersonator

Level: 1

Type: WARNING

Impact: Security

WCS-44253: Impersonator {0} already added for user {1}
Cause: You can add an impersonator only once for a user
Action: Ensure you add an impersonator only once for a user. To specify a different time duration, edit the existing grant

Level: 1

Type: WARNING

Impact: Security

WCS-44254: Impersonatee {0} already added for user {1}
Cause: You can add an impersonator only once for a user
Action: Ensure you add an impersonator only once for a user. To specify a different time duration, edit the existing grant

Level: 1

Type: WARNING

Impact: Security

WCS-44255: Cannot update or delete impersonator {0} for user {1} as impersonator not yet added
Cause: The impersonator being updated or deleted has not been added yet
Action: Ensure the impersonator has been added before trying to update or remove the impersonation grant

Level: 1

Type: WARNING

Impact: Security

WCS-44256: Cannot update or delete impersonatee {0} for user {1} as impersonatee not yet added
Cause: The impersonator being updated or deleted has not been added yet
Action: Ensure the impersonator has been added before trying to update or remove the impersonation grant

Level: 1

Type: WARNING

Impact: Security

WCS-44257: Impersonator user {0} could not be found
Cause: The impersonator specified is not a valid user
Action: Ensure you specify a valid impersonator

Level: 1

Type: WARNING

Impact: Security

WCS-44258: Impersonatee user {0} could not be found
Cause: The impersonatee specified is not a valid user
Action: Ensure you specify a valid impersonatee

Level: 1

Type: WARNING

Impact: Security

WCS-44259: Fetching Impersonator user {0} failed
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Security

WCS-44260: Fetching Impersonatee user {0} failed
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Security

WCS-44261: Adding impersonator {0} for user {1} failed
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Security

WCS-44262: Updating impersonator {0} for user {1} failed
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Security

WCS-44263: Removing impersonator {0} for user {1} failed
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Security

WCS-44264: Getting impersonators for user {0} failed
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Security

WCS-44265: Getting impersonatees for user {0} failed
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Security

WCS-44266: Removing expired impersonation grants for user {0} failed
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Security

WCS-44267: Starting impersonation session for user {0} failed
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Security

WCS-44268: Terminating impersonation session for current user failed
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Security

WCS-44269: User {0} is not a valid impersonator
Cause: The user specified as impersonator does not belong to webcenter#-#impersonators role.
Action: Ensure you specify a user that belongs to webcenter#-#impersontors role.

Level: 1

Type: WARNING

Impact: Security

WCS-44270: Determining if user {0} is a valid impersonator failed
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Security

WCS-44271: Adding or updating impersonator {0} for user {1} failed
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Security

WCS-44272: Searching for impersonators matching pattern {0} failed
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Security

WCS-44273: Impersonation Time delta {0} specified is in invalid format
Cause: Time delta specified was not a valid integer
Action: Check documentation to understand the format in which this delta needs to be specified. It needs to be a valid integer

Level: 1

Type: WARNING

Impact: Security

WCS-44274: Impersonation configuration check failed
Cause: Review the underlying exception in the logs to determine the exact cause
Action: Take action based on the underlying exception details

Level: 1

Type: ERROR

Impact: Security

WCS-44275: End time {0} cannot be before current time.
Cause: End time for impersonation grant is before current time
Action: Ensure end time is not before current time

Level: 1

Type: WARNING

Impact: Security

WCS-44300: An error encountered while granting permissions
Cause: Review the underlying exception in the logs to determine the exact cause. The policy may already have been granted or the identity may not exist or there is a problem with the policy store.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44301: An error encountered while revoking permissions
Cause: Review the underlying exception in the logs to determine the exact cause. The policy may not exist or the identity may not exist or there is a problem with the policy store.
Action: Take action based on the underlying exception details.

Level: 1

Type: ERROR

Impact: Security

WCS-44302: An OPSS error occurred while locating the audit service.
Cause: The error would be caused when Audit Service is not configured. Review the jps-config.xml configuration file in conjunction with the stack trace if Audit Service needs to be enabled for WebCenter Portal.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Security

WCS-44304: Invalid security attribute {0} obtained for artifact {1} in service {2}
Cause: The security attribute returned by the service does not comply to the list of expected security attributes
Action: Ensure the security attribute is one of the expected values i.e. user, group, application role, authenticated and anonymous roles

Level: 1

Type: ERROR

Impact: Security

WCS-44305: An error occurred while upgrading portal role {0} due to {1}
Cause: Review the underlying exception in the logs to determine the exact cause. The role may already have been upgraded.
Action: Take action based on the underlying exception details.

Level: 1

Type: WARNING

Impact: Security

WCS-44306: An error occurred while upgrading portal roles due to {0}
Cause: Review the underlying exception in the logs to determine the exact cause. The role may already have been upgraded.
Action: Take action based on the underlying exception details.

Level: 1

Type: WARNING

Impact: Security

WCS-46001: unexpected error has occurred
Cause: Review the root cause of the exception for more details.
Action: If the root cause does not provide sufficient information to resolve the issue, contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-46002: cannot initialize the resource catalog
Cause: There was an error initializing the catalog using the catalog specified in adf-config.xml or there was a problem with the underlying resource catalog service.
Action: Verify that the catalog name specified in adf-config.xml is valid.

Level: 1

Type: WARNING

Impact: Logging

WCS-46004: cannot create item for resource [{0}], path [{1}], catalog [{2}]
Cause: There was an internal error when creating an item for the resource indicated above.
Action: Verify that the Resource Catalog and resource adapters are working correctly.

Level: 1

Type: WARNING

Impact: Logging

WCS-46005: cannot create a Folder object for resource [{0}], catalog [{1}]
Cause: There was an internal error when creating the folder object using the path specified.
Action: Verify that the Resource Catalog and resource adapters are working correctly.

Level: 1

Type: WARNING

Impact: Logging

WCS-46006: cannot retrieve items in [{0}] from catalog [{1}]
Cause: There was an error retrieving any resources from the catalog.
Action: Verify that the catalog is correctly configured in adf-config.xml.

Level: 1

Type: WARNING

Impact: Logging

WCS-46007: Search predicate [{0}] is not valid for search path [{1}] in catalog [{2}].
Cause: The search condition specified was invalid or incorrect.
Action: Correct the code that creates the search condition for the resource catalog viewer.

Level: 1

Type: WARNING

Impact: Logging

WCS-46008: Specified folder [{0}], path [{1}] to search does not exist in catalog [{2}].
Cause: The selected folder does not exist anymore.
Action: Perform the search by selecting a different folder.

Level: 1

Type: WARNING

Impact: Logging

WCS-46009: cannot execute search for folder [{0}]
Cause: An internal error occurred while executing the requested search.
Action: Verify that the Resource Catalog and resource adapters are working correctly.

Level: 1

Type: WARNING

Impact: Logging

WCS-46010: cannot retrieve folder path for item [{0}]
Cause: The folder path specified was not found.
Action: The folder path requested is either incorrect or does not exist anymore.

Level: 1

Type: WARNING

Impact: Logging

WCS-46011: cannot find Item [{0}] in catalog [{1}]
Cause: The requested item could not be found.
Action: The item requested is either incorrect or does not exist anymore.

Level: 1

Type: WARNING

Impact: Logging

WCS-46012: cannot find Folder [{0}] in catalog [{1}]
Cause: The requested folder could not be found.
Action: The folder requested is either incorrect or does not exist anymore.

Level: 1

Type: WARNING

Impact: Logging

WCS-46013: cannot retrieve icon
Cause: Icon associated with the requested resource not found.
Action: Verify that the underlying resource provider adapter supports the iconURI attribute.

Level: 1

Type: WARNING

Impact: Logging

WCS-46014: cannot retrieve attributes for item [{0}]
Cause: Could not retrieve one or more attributes.
Action: Verify that the underlying resource provider supports the requested attributes.

Level: 1

Type: WARNING

Impact: Logging

WCS-46015: cannot retrieve transferable for item [{0}]
Cause: Could not retrieve transferable for resource.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-46016: cannot retrieve repository reference for item [{0}]
Cause: Could not retrieve a repository reference.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-46017: cannot retrieve schema attributes for folder [{0}]
Cause: Error occurred while fetching information about the schema.
Action: Verify that the Resource Catalog and resource adapters are working correctly.

Level: 1

Type: WARNING

Impact: Logging

WCS-46018: cannot retrieve any resources for folder [{0}]
Cause: Error occurred while fetching resource catalog resources.
Action: Verify that the Resource Catalog and resource adapters are working correctly.

Level: 1

Type: WARNING

Impact: Logging

WCS-46019: cannot retrieve any folders for folder [{0}]
Cause: Error occurred while fetching resource catalog folders.
Action: Verify that the Resource Catalog and resource adapters are working correctly.

Level: 1

Type: WARNING

Impact: Logging

WCS-46020: cannot retrieve any items for folder [{0}]
Cause: Error occurred while fetching resource catalog items.
Action: Verify that the Resource Catalog and resource adapters are working correctly.

Level: 1

Type: WARNING

Impact: Logging

WCS-46021: cannot retrieve any attributes for item [{0}]
Cause: Error occurred while fetching resource catalog resource attributes.
Action: Verify that the Resource Catalog and resource adapters are working correctly.

Level: 1

Type: WARNING

Impact: Logging

WCS-46022: cannot execute a search in folder [{0}], search criteria [{1}], include subfolders [{2}]
Cause: Search could not be executed due to unknown reasons.
Action: Verify that the Resource Catalog and resource adapters are working correctly.

Level: 1

Type: WARNING

Impact: Logging

WCS-46023: cannot retrieve the complete path for folder [{0}]
Cause: Error occurred while fetching the full path of the resource.
Action: The resource may not exist anymore. Refresh the viewer to get the latest content.

Level: 1

Type: WARNING

Impact: Logging

WCS-46024: cannot retrieve the current folder
Cause: There was an error while retrieving information about the current folder.
Action: The folder may not exist anymore. Refresh the viewer to get the latest content.

Level: 1

Type: WARNING

Impact: Logging

WCS-46025: cannot initialize the catalog using the parameters specified in adf-config.xml
Cause: The catalog name specified in adf-config.xml could not be used or the there was an error retrieving the catalog name from the catalog selector class specified in adf-config.xml.
Action: Verify that the catalog name specified in adf-config.xml or the one returned by the catalog selector class exists.

Level: 1

Type: WARNING

Impact: Logging

WCS-46027: cannot print attributes for item [{0}]
Cause: Error printing information about the item attributes in the viewer.
Action: Check the error stack for more information.

Level: 1

Type: WARNING

Impact: Logging

WCS-46028: cannot load ResourceCatalogConfig implementation using class [{0}]
Cause: Resource catalog configuration implementation class defined in adf-config.xml is invalid.
Action: Check adf-config.xml to verify the implementation class is valid.

Level: 1

Type: WARNING

Impact: Logging

WCS-46029: cannot instantiate the catalog config class [{0}]
Cause: An error occurred while instantiating a class defined in the <rcv-adf-config> section in adf-config.xml.
Action: Verify that the class name is correct and it implements the required interface

Level: 1

Type: WARNING

Impact: Logging

WCS-46030: cannot obtain the catalog name. ResourceCatalogSelector=[{0}] DefaultCatalog=[{1}].
Cause: The resource catalog viewer was unable to determine the catalog to use for the current context and no default was specified.
Action: Verify the ResourceCatalogSelector implementation and specify a default catalog in adf-config.xml.

Level: 1

Type: WARNING

Impact: Logging

WCS-46032: cannot retrieve item for item with ID [{0}]
Cause: An error occurred while fetching the item using the item id.
Action: Review the resource catalog service logs for additional information.

Level: 1

Type: WARNING

Impact: Logging

WCS-46033: cannot retrieve root folder
Cause: An error occurred while fetching the root folder.
Action: Check the Resource Catalog logs for additional information.

Level: 1

Type: WARNING

Impact: Logging

WCS-46035: cannot initialize the catalog context with catalog [{0}]
Cause: The catalog name specified in adf-config.xml could not be used or the there was an error retrieving the catalog name from the catalog selector class specified in adf-config.xml.
Action: Verify that the catalog name specified in adf-config.xml or the one returned by the catalog selector class exists.

Level: 1

Type: WARNING

Impact: Logging

WCS-46037: cannot retrieve the catalog instance
Cause: The catalog name specified in adf-config.xml could not be used or the there was an error retrieving the catalog name from the catalog selector class specified in adf-config.xml.
Action: Verify that the catalog name specified in adf-config.xml or the one returned by the catalog selector class exists.

Level: 1

Type: WARNING

Impact: Logging

WCS-46039: cannot parse the rcv config in adf-config.xml
Cause: The rcv config xml element specified in adf-config.xml could not be parsed.
Action: Verify that the rcv config element specified in adf-config.xml exists and it is valid.

Level: 1

Type: WARNING

Impact: Logging

WCS-46040: Cannot find catalog with ID [{0}].
Cause: The specified catalog cannot be found.
Action: Verify that the specified catalog exists.

Level: 2

Type: WARNING

Impact: Logging

WCS-46041: Using the default catalog [{0}].
Cause: The catalog specified by the catalog selector cannot be found.
Action: Verify that the catalog specified by the catalog selector exists.

Level: 2

Type: WARNING

Impact: Logging

WCS-46042: The default catalog with ID [{0}] cannot be found.
Cause: The specified default catalog cannot be found.
Action: Verify that the specified default catalog exists.

Level: 2

Type: WARNING

Impact: Logging

WCS-46043: Could not create the breadcrumbs for item [{0}].
Cause: The requested item could not be found.
Action: The item requested is either incorrect or does not exist anymore.

Level: 1

Type: ERROR

Impact: Logging

WCS-46044: Search for [{0}] timed out after [{1}]ms. Partial results returned.
Cause: A resource catalog search timed out
Action: Try using a less complex search expression

Level: 1

Type: WARNING

Impact: Logging

WCS-46045: Maximum number of matches ({1}) exceeded while search for [{0}]. Partial results returned.
Cause: A resource catalog search reached the maximum number of matches before the search completed
Action: Use a more specific search expression

Level: 1

Type: WARNING

Impact: Logging

WCS-47201: An unexpected error occurred in the Activity Stream sub-system.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-47202: The publish activity failed because invalid arguments were passed to the method: activity ({0}).
Cause: One of the input arguments was invalid.
Action: Ensure that all arguments passed are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47203: The retrieve activities failed because invalid arguments were passed to the method: privateAndUpActorIds ({0}), sharedAndUpActorIds ({1}), publicActorIds ({2}).
Cause: One of the input arguments was invalid.
Action: Ensure that all arguments passed are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47205: Cannot establish connections. A connections exception was thrown.
Cause: A connections exception has been thrown.
Action: Check the exception's details to see why it was thrown.

Level: 1

Type: ERROR

Impact: Other

WCS-47206: A Service Framework exception was thrown.
Cause: A Service Framework exception has been thrown.
Action: Check the exception's details to see why it was thrown.

Level: 1

Type: ERROR

Impact: Other

WCS-47207: A Settings exception was thrown.
Cause: A Settings exception was thrown.
Action: Check the exception's details to see why it was thrown.

Level: 1

Type: ERROR

Impact: Other

WCS-47208: The retrieve activities failed because invalid arguments were passed to the method: applicationId ({0}), servivceId ({1}), activityType ({2}).
Cause: One of the input arguments was invalid.
Action: Ensure that all arguments passed are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47209: The retrieve activities failed because invalid arguments were passed to the method: applicationId ({0}), servivceId ({1}), activityType ({2}), sinceDate ({3}).
Cause: One of the input arguments was invalid.
Action: Ensure that all arguments passed are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47210: A database exception occurred in the Activity Stream Toplink module.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47211: A query exception occurred in the Activity Stream Toplink module.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47212: Create Actor failed because an invalid argument was passed to the method: guid ({0}).
Cause: One of the input arguments was invalid.
Action: Ensure that all arguments passed are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47213: Create Object failed because an invalid argument was passed to the method: guid ({0}), type ({1}), displayName ({2}).
Cause: One of the input arguments was invalid.
Action: Ensure that all arguments passed are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47214: Create Activity Element failed because an invalid argument was passed to the method: applicationID ({0}), scope ({1}), serviceID ({2}), activityType ({3}), actors ({4}), permission ({5}), activityTime ({6}).
Cause: One of the input arguments was invalid.
Action: Ensure that all arguments passed are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47215: Create Activity Type failed because an invalid argument was passed to the method: id ({0}).
Cause: One of the input arguments was invalid.
Action: Ensure that all arguments passed are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47216: Create Object Type failed because an invalid argument was passed to the method: id ({0}).
Cause: One of the input arguments was invalid.
Action: Ensure that all arguments passed are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47217: Create Activity Element failed because an invalid argument was passed to the method: applicationID ({0}), activityType ({1}), actors ({2}), permission ({3}), activityTime ({4}).
Cause: One of the input arguments was invalid.
Action: Ensure that all arguments passed are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47218: Publish activity {0} failed due to {1}.
Cause: An unexpected error during the publishing activity.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47219: An error occurred due to {0}.
Cause: An exception occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47220: An unexpected error occurred resolving property ''{0}'':''{1}'' for an Analytics event of type {2}
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47221: Unable to publish the Analytics event (of type {0}).
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47222: This operation is not supported.
Cause: This operation not supported.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47223: Skipping profile information for user {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-47224: For user {0}, the last accessed page couldn''t be found due to {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-47225: Check for valid repository failed.
Cause: Either the database is down or the WebCenter repository is not installed.
Action: Check the exception's details to why this error occurred.

Level: 1

Type: ERROR

Impact: Other

WCS-47226: For user {0}, couldn''t retrieve the list of pages last accessed due to {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-47227: For user {0}, couldn''t retrieve the last accessed page in {1} due to {2}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-47228: For user {0}, couldn''t clean the last accessed page due to {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-47229: The task flow instance was not specified.
Cause: The supplied taskflow instance ID was null or blank.
Action: Specify a valid taskflow instance ID that is not null or blank.

Level: 1

Type: ERROR

Impact: Other

WCS-47230: An activity exception was encountered during the bulk publish operation.
Cause: One or more activities threw an exception.
Action: Check the individual activity exception.

Level: 1

Type: ERROR

Impact: Other

WCS-47231: Create Cust Attr failed because an invalid argument was passed to the method: name ({0}), value ({1}), url ({2}).
Cause: One of the input arguments was invalid.
Action: Ensure that all arguments passed are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47232: An unexpected error occurred while setting up the Comments service.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47233: An unexpected error occurred while retrieving comments.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47234: An unexpected error occurred while posting a comment.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47235: An unexpected error occurred while preparing a comments summary.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47236: An unexpected error occurred while preparing comments.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47237: Comment text cannot be empty.
Cause: The supplied text for the comment is null or blank.
Action: Specify a non-empty text for the comment.

Level: 1

Type: ERROR

Impact: Other

WCS-47238: An object was not specified.
Cause: The supplied object identifier is null.
Action: Specify a non-null object identifier.

Level: 1

Type: ERROR

Impact: Other

WCS-47239: An object ID is not present for the specified object.
Cause: The ID of the specified object is null.
Action: Specify an object with a valid ID.

Level: 1

Type: ERROR

Impact: Other

WCS-47240: A service ID is not present for the specified object.
Cause: The service ID for the specified object is null.
Action: Specify an object with a valid service ID.

Level: 1

Type: ERROR

Impact: Other

WCS-47241: An object type is not present for the specified object.
Cause: The object type for the specified object is null.
Action: Specify an object with a valid object type.

Level: 1

Type: ERROR

Impact: Other

WCS-47242: An unexpected error while expanding comments.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47243: An unexpected error occurred while collapsing comments.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47244: An unexpected error occurred while setting up the Likes service.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47245: An unexpected error occurred while retrieving Likes.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47246: An unexpected error occurred while retrieving Likes.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47247: An unexpected error occurred while posting a Like.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47248: A comment ID not specified.
Cause: The supplied comment ID was null or blank.
Action: Specify a valid comment ID that is not null or blank.

Level: 1

Type: ERROR

Impact: Other

WCS-47249: An unexpected error occurred while deleting a comment.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47250: An unexpected error occurred while initializing the scope.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47252: The follow object failed because an invalid arguments was passed to the method: actor ({0}), object ({1}), object service id ({2}).
Cause: One of the input arguments is invalid.
Action: Ensure that all arguments passed are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47253: Can''t archive due to an invalid argument: date ({0}).
Cause: One of the input arguments is invalid.
Action: Ensure that all arguments passed are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47254: An unexpected error occurred while archiving.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47255: Failed to register application management beans.
Cause: Application management beans(MBean) registration failed. Either there are issues with WebLogic or the application was not packaged properly.
Action: Restart WebLogic or examine WebLogic log files for further details.

Level: 1

Type: ERROR

Impact: Other

WCS-47256: Failed to unregister application management beans.
Cause: Application management beans(MBean) unregistration failed. Either the Mbeans were not registered or the Mbeans were already unregistered.
Action: Examine the WebLogic log files for further details.

Level: 1

Type: ERROR

Impact: Other

WCS-47257: An unexpected error occurred while deleting service data corresponding to the activity.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47258: The advanced query parameter contains invalid or unsupported constructs.
Cause: There are invalid or unsupported SQL constructs specified in the Advanced Query filter parameter.
Action: Correct the Advanced Query filter parameter.

Level: 1

Type: ERROR

Impact: Other

WCS-47259: An unexpected error occurred in setting up the JMS queue {0}.
Cause: The AQ JMS ConnectionFactory or Queue lookup failed.
Action: Correct JMS Modules in Admin Console.

Level: 1

Type: ERROR

Impact: Other

WCS-47260: An unexpected error occurred while send message to the JMS queue.
Cause: The JMS Queue found, but enqueue failed.
Action: Examine the Weblogic log files for exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-47261: Fail to get Resource URI for published Activity.
Cause: The ResourceActionUtils.getUrl() failed for input Activity.
Action: Examine the Weblogic log files for exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-47262: Fail to get Activity message for message key {0} in bundle {1}.
Cause: The getMessage() failed for input Activity.
Action: Examine the Weblogic log files for exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-47263: Failed to unfollow objects due to {0}.
Cause: An unexpected error occurred during the unfollowing objects.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47264: The unfollowed object failed because an invalid arguments was passed to the method: actor ({0}), object ({1}).
Cause: One of the input arguments is invalid.
Action: Ensure that all arguments passed are valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47265: Failed to initialize context for asynchronous activity listeners processing.
Cause: Failed to initialize context for asynchronous activity listeners processing.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-47266: Failed to parse the activity definition file {0} due to {1}
Cause: Validate the activity-definition.xml file..
Action: Examine the Weblogic log files for exception details.

Level: 1

Type: ERROR

Impact: Other

WCS-47267: Failed to lookup connection for name {0}.
Cause: Invalid OSN connection name.
Action: Contact Administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-47268: Could not load extension handler due to {0}.
Cause: Could not load extension handler.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47269: Can not close transaction due to {0}.
Cause: Can not close transaction.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47270: Can not close statement due to {0}.
Cause: Can not close statement.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47271: Can not get result set due to {0}.
Cause: Can not get result set.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47272: Can not rollback transaction due to {0}.
Cause: Can not rollback transaction.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47273: Can not load XML actor detail data due to {0}.
Cause: Can not load XML actor detail data.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47274: Can not insert new actor details due to {0}.
Cause: Can not insert new actor details.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47275: Error occurs when processing activity {0} for activity listener{1} due to {2}.
Cause: Could not call activity listener's onsActivity method.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47276: Failed while retrieving activity listeners due to {0}
Cause: Failed while retrieving activity listeners.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47277: Failed to initialize due to {0}
Cause: Failed to initialize.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47278: Cannot get service registry due to {0}.
Cause: Error to get service registry.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47279: Error closing entity manager factory due to {0}
Cause: An unexpected exception occurred while closing the entity manager factory.
Action: Review the exception thrown for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47280: No default value found for key {0}.
Cause: No default value found for key {0}.
Action: Ensure default value for key {0} is valid.

Level: 1

Type: WARNING

Impact: Other

WCS-47281: Cannot get activity services list due to {0}.
Cause: Cannot get activity services list.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47282: Resource bundle not found. bundle = {0}, key = {1} .
Cause: Resource bundle not found.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47283: Key not found. bundle = {0}, key = {1} .
Cause: Key not found.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47284: Service category {0} is invalid, title key not found, ignoring.
Cause: Service category is invalid, therefore title key not found.
Action: Examine the WebCenter log files for exception details

Level: 1

Type: WARNING

Impact: Other

WCS-47285: Unable to compare Service Settings due to {0}.
Cause: Unable to compare Service Settings.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47286: Cannot parse to date due to {0}.
Cause: Cannot parse to date.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47287: Cannot parse from date due to {0}.
Cause: Cannot parse from date.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47288: Cannot set access control configurable due to {0}.
Cause: Cannot set access control configurable.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47289: Cannot set configurable service category settings due to {0}.
Cause: Cannot set configurable service category settings.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47290: Can not process activity {0} due to {1}.
Cause: >Can not process activity.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47291: Failed to get profile guid {0} due to {1}.
Cause: Failed to get profile guid.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47292: Failed to get profile id {0} due to {1}.
Cause: Failed to get profile guid.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47293: Cannot summarize activities due to activity list is null.
Cause: Cannot summarize activities due mActivities is null.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47294: Cannot get object type display name due to {0}.
Cause: Cannot get object type display name.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47295: Could not publish activity even after retry due to {0}.
Cause: Could not publish activity even after retry.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47296: Error while retrieving activities due to {0}.
Cause: Error while retrieving activities.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47297: Error while processing personal criteria due to {0}.
Cause: Error while processing personal criteria.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47298: Error while processing portals criteria due to {0}.
Cause: Error while processing portals criteria.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47299: Error while processing service id criteria due to {0}.
Cause: Error while processing service id criteria .
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47300: Error while processing activity type criteria due to {0}.
Cause: Error while processing activity type criteria.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47302: Error while processing enterprise id criteria due to {0}.
Cause: Error while processing enterprise id criteria.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47303: Error while processing date criteria due to {0}.
Cause: Error while processing date criteria.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47304: Skipping rendering activity {0} due to {1}.
Cause: Skipping rendering activity.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47305: Cannot get profile due to {0}.
Cause: Cannot get profile.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47306: Failed to get activity type icon url due to {0}.
Cause: Failed to get activity type icon url.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47307: Failed to get activity type due to {0}.
Cause: Failed to get activity type.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47308: Failed to get activity type category due to {0}.
Cause: Failed to get activity type category.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47309: Failed to get inline preview due to {0}.
Cause: Failed to get inline preview.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47310: Failed to get object type due to {0}.
Cause: Failed to get object type.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47311: Client listener not supported {0}.
Cause: Client listener not supported.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47312: Cannot convert user guid {0} to id due to {1}.
Cause: Cannot convert user guid to id.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47313: Could not publish activity due to {0}.
Cause: Could not publish activity.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47314: Cannot get preference maps due to {0}.
Cause: Cannot get preference maps .
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47315: Cannot obtain scope {0} due to {1}.
Cause: Cannot obtain scope.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47316: Failed to publish Activity. Activity Detail: {0}.
Cause: Could not publish activity.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47317: Failed to publish Activity. Actor Detail: {0}.
Cause: Could not publish activity.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47318: During creating of UI components, can not get the object type.
Cause: During creating of UI components, can not get the object type.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47319: Failed to initialize activity stream settings due to {0}
Cause: Fail to initialize activity stream settings.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47320: Cannot summarize activities due to {0}.
Cause: Cannot summarize activities.
Action: Examine the WebCenter log files for more details.

Level: 1

Type: WARNING

Impact: Other

WCS-47321: Cannot get service {0} due to {1}.
Cause: Error to get service.
Action: Examine the WebCenter log files for exception details.

Level: 1

Type: WARNING

Impact: Other

WCS-47322: An unexpected error occurred while saving settings.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47323: An unexpected error occurred while preparing the activity record.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47324: An unexpected error occurred while refreshing preference settings.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47325: An unexpected error occurred while removing the activity record.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47326: An unexpected error occurred while hiding the popup.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47327: An unexpected error occurred while preparing the activity view or components.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47328: An unexpected error occurred while fetching service IDs.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47329: An unexpected error occurred while initializing activity stream settings.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47330: An unexpected error occurred while saving or hiding preferences.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47331: An unexpected error occurred while fetching the portals.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47332: An unexpected error occurred while retrieving the activities.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47333: An unexpected error occurred while retrieving the summary activities.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47334: An unexpected error occurred while retrieving activities data.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47335: An unexpected error occurred while saving setup options.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47336: Input text 'No of activities to display per page' accepts positive value.
Cause: Wrong user input
Action: Correct the invalid input and retry.

Level: 1

Type: ERROR

Impact: Other

WCS-47695: Unexpected error saving settings
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47696: Fatal error initializing the settings management sub-system
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-47697: Unexpected error retrieving settings
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47698: Unable to locate the settings document
Cause: Either the document path was incorrect or the document had got deleted.
Action: Ensure that the document path is correct and that the document exists.

Level: 1

Type: ERROR

Impact: Other

WCS-47699: Unable to determine current user
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47801: An unexpected error occurred in the Connections sub-system.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-47802: User not specified
Cause: The supplied username was null or blank.
Action: Specify a valid username that is not null or blank.

Level: 1

Type: ERROR

Impact: Other

WCS-47803: Unexpected error retrieving connections for user ''{0}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47804: Unexpected error retrieving invitations for current user
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47805: User ''{0}'' not found
Cause: The system could not find any user with the specified username.
Action: Specify a valid username.

Level: 1

Type: ERROR

Impact: Other

WCS-47806: Unexpected error sending invitation to user ''{0}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47807: Invitation not found (the invitation may have been withdrawn, accepted, or declined already)
Cause: The system could not find any invitation with the specified ID.
Action: Ensure that the specified invitation ID is valid.

Level: 1

Type: ERROR

Impact: Other

WCS-47808: Invitation ID not specified
Cause: The supplied invitation ID was null or blank.
Action: Specify a valid invitation ID that is not null or blank.

Level: 1

Type: ERROR

Impact: Other

WCS-47809: Unexpected error accepting invitation with ID ''{0}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47810: Unexpected error declining invitation with ID ''{0}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47811: Unexpected error ignoring invitation with ID ''{0}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47812: Unexpected error removing connection with user ''{0}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47813: Unexpected error retrieving profile of user ''{0}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47814: Unexpected error retrieving the connection lists owned by user ''{0}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47815: Connection list not specified
Cause: The supplied connection list name was null or blank.
Action: Specify a valid connection list name that is not null or blank.

Level: 1

Type: ERROR

Impact: Other

WCS-47816: Connection list named ''{0}'' not found for user ''{1}''
Cause: The system could not find any connection list with the specified name owned by the specified user.
Action: Ensure that the username is correct and that the connection list name refers to a connection list owned by that user.

Level: 1

Type: ERROR

Impact: Other

WCS-47817: Unexpected error getting Connection list ''{0}'' for user ''{1}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47818: User does not have the privilege required to perform specified operation
Cause: Either the system policy or the target user's access control settings restrict the current user from performing this operation
Action: Contact the Administrator to grant the required permission, or contact the target user to allow access

Level: 1

Type: ERROR

Impact: Other

WCS-47819: Unexpected error creating a Connection list with name ''{0}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47820: Unexpected error adding users to Connection list with name ''{0}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47821: Unexpected error deleting Connection list with name ''{0}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47822: Unexpected error retrieving members of Connection list with name ''{0}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47823: Unexpected error retrieving invitations sent by current user
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47824: Unexpected error removing user ''{0}'' from one or more Connection lists
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47825: Unexpected error setting Connection list membership of user ''{0}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47826: Unexpected error retrieving the Connection lists to which user ''{0}'' belongs
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47827: Unexpected error creating a connection between users ''{0}'' and ''{1}''
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47829: Cannot invite oneself as a connection
Cause: You have specified yourself as the invitee.
Action: Specify a username other than that of yourself.

Level: 1

Type: ERROR

Impact: Other

WCS-47830: Cannot invite a user who has been invited already ({0})
Cause: The user you have specified has already been invited.
Action: Wait for the invited user to act on your invitation.

Level: 1

Type: ERROR

Impact: Other

WCS-47831: Cannot invite a user who has already invited you ({0})
Cause: The user you have specified has already invited you.
Action: Accept the invitation you have received from the user.

Level: 1

Type: ERROR

Impact: Other

WCS-47832: Cannot invite a user you are already connected with ({0})
Cause: You have specified one of your existing connections as the invitee.
Action: Specify a username other than that of your existing connections.

Level: 1

Type: ERROR

Impact: Other

WCS-47833: Unexpected error searching for users with filter pattern ({0})
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47834: Cannot create a connection between users ''{0}'' and ''{1}'' who already connected
Cause: The specified users are already connected with each other.
Action: Specify users who are not yet connected.

Level: 1

Type: ERROR

Impact: Other

WCS-47835: Unexpected error reading default configuration ''{0}'' or custom configuration
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47836: Unexpected error getting connections with preferences (userGuid = {0}, applicationId = {1}, scope = {2}, serviceId = {3}, settingKey = {4}, configurableSettingKey = {5})
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47837: Unexpected error getting connections lists with preferences (listNames = {0}, userGuid = {1}, applicationId = {2}, scope = {3}, serviceId = {4}, settingKey = {5}, configurableSettingKey = {6})
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-47838: Cannot create a Connection list with the same name as existing one ({0})
Cause: You already have a connection list with the specified name.
Action: Specify a name other than that of your existing connection lists.

Level: 1

Type: ERROR

Impact: Other

WCS-49001: Injectable Service provider did not set list service
Cause: Injectable Service provider could not find the list service.
Action: Make sure List Service injectable provider is available in webapp.

Level: 1

Type: ERROR

Impact: Other

WCS-49002: List id is null
Cause: List ID was not specified in request.
Action: Make sure List ID is specified in request.

Level: 1

Type: ERROR

Impact: Other

WCS-49003: Column id is null
Cause: Column ID was not specified in request.
Action: Make sure Column ID is specified in request.

Level: 1

Type: ERROR

Impact: Other

WCS-49004: Row id is null
Cause: Row ID was not specified in request.
Action: Make sure Row ID is specified in request.

Level: 1

Type: ERROR

Impact: Other

WCS-49005: No 'column' in the request body
Cause: Column data was not found in the request body.
Action: Make sure Column data is specified in the request body.

Level: 1

Type: ERROR

Impact: Other

WCS-49006: No 'list' in the request body
Cause: List data was not found in the request body.
Action: Make sure List data is specified in the request body.

Level: 1

Type: ERROR

Impact: Other

WCS-49007: No 'row' in the request body
Cause: Row data was not found in the request body.
Action: Make sure Row data is specified in the request body.

Level: 1

Type: ERROR

Impact: Other

WCS-49008: List could not be found for list id [{0}]
Cause: List ID was not found.
Action: Make sure List ID exists.

Level: 1

Type: ERROR

Impact: Other

WCS-49009: Column could not be found for column id [{0}]
Cause: Column ID was not found.
Action: Make sure Column ID exists.

Level: 1

Type: ERROR

Impact: Other

WCS-49010: Row could not be found for row id [{0}]
Cause: Row ID was not found.
Action: Make sure Row ID exists.

Level: 1

Type: ERROR

Impact: Other

WCS-49011: Unable to create list
Cause: List was not created.
Action: See logs for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-49012: 'id' should not be supplied with a POST -- use PUT if you want to update
Cause: 'id' should not be supplied with a POST.
Action: Use PUT if you want to update.

Level: 1

Type: ERROR

Impact: Other

WCS-49013: Search parameter must follow [column:[operator:]]value;[column:[operator:]value] syntax
Cause: Search parameter syntax not understood.
Action: Syntax must follow: [column:[operator:]]value;[column:[operator:]value]

Level: 1

Type: ERROR

Impact: Other

WCS-49014: Comparator [{0}] is invalid
Cause: Invalid search comparator.
Action: Use valid search comparator.

Level: 1

Type: ERROR

Impact: Other

WCS-49015: MetaColumn [{0}] is a required field, and cannot be set to null
Cause: Missing required field.
Action: Make sure required field is present.

Level: 1

Type: ERROR

Impact: Other

WCS-49016: Invalid ''row'' data in the request body [{0}]
Cause: Invalid row data was found in the request body.
Action: Make sure valid row data is specified in the request body.

Level: 1

Type: ERROR

Impact: Other

WCS-49017: Portal name not found [{0}]
Cause: Portal name not found.
Action: Please specify a valid portal name.

Level: 1

Type: ERROR

Impact: Other

WCS-49018: Portal name not found for GUID [{0}]
Cause: Portal name GUID not found.
Action: Please specify a valid portal name GUID.

Level: 1

Type: ERROR

Impact: Other

WCS-49101: Injectable Service provider did not set forum service
Cause: Injectable Service provider could not find the forum service.
Action: Make sure Forum Service injectable provider is available in webapp.

Level: 1

Type: ERROR

Impact: Other

WCS-49102: Can't establish Forum Session
Cause: Injectable Service provider could not establish a Forum Session.
Action: Make sure Jive Forum is configured and running and/or you have a valid user session established. Re-authenticating may help.

Level: 1

Type: ERROR

Impact: Other

WCS-49103: Forum id not found [{0}]
Cause: Forum not found.
Action: Please specify a valid forum.

Level: 1

Type: ERROR

Impact: Other

WCS-49104: Portal name not found [{0}]
Cause: Portal name not found.
Action: Please specify a valid portal name.

Level: 1

Type: ERROR

Impact: Other

WCS-49105: All resources require a name.
Cause: Resource name required.
Action: Please specify a resource name in the request body.

Level: 1

Type: ERROR

Impact: Other

WCS-49106: Topic id not found [{0}]
Cause: Topic not found.
Action: Please specify a valid topic.

Level: 1

Type: ERROR

Impact: Other

WCS-49201: Injectable Service provider did not set Spaces service
Cause: Injectable Service provider could not find Space the service.
Action: Make sure Space Service injectable provider is available in webapp.

Level: 1

Type: ERROR

Impact: Other

WCS-49202: Portal id is null
Cause: Portal ID was not specified in request.
Action: Make sure Portal ID is specified in request.

Level: 1

Type: ERROR

Impact: Other

WCS-49203: No 'document' in the request body
Cause: Portal document data was not found in the request body.
Action: Make sure Portal document is specified in the request body.

Level: 1

Type: ERROR

Impact: Other

WCS-49204: Portal name not found [{0}]
Cause: Portal name not found.
Action: Please specify a valid portal name.

Level: 1

Type: ERROR

Impact: Other

WCS-49205: Members not found for portal [{0}]
Cause: No Members found.
Action: Please specify a portal with members.

Level: 1

Type: ERROR

Impact: Other

WCS-49206: Member [{0}] not found in portal [{1}]
Cause: Member not found.
Action: Please specify a different member or portal name.

Level: 1

Type: ERROR

Impact: Other

WCS-49207: Attributes not found in portal [{0}]
Cause: Attributes not found.
Action: Please specify a different portal name.

Level: 1

Type: ERROR

Impact: Other

WCS-49208: Attribute name [{0}] not found in portal [{1}]
Cause: Attribute name not found.
Action: Please specify a different Attribute name or portal name.

Level: 1

Type: ERROR

Impact: Other

WCS-49209: Portal params [{0}] and [{1}] result in exception
Cause: General exception.
Action: Please specify a different set of parameters.

Level: 1

Type: ERROR

Impact: Other

WCS-49210: Attempted operation resulted in security exception
Cause: Insufficient authorization.
Action: Contact portal administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-49211: Retrieving Portal failed due to service unavailability
Cause: Service inaccessible.
Action: Contact portal administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-49212: Failed to retrieve document repository info for portal.
Cause: Unknown document repository error.
Action: Contact portal administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-49213: No Portal provided in body.
Cause: Portal was not provided in POST body of request.
Action: Provide Portal in POST body of request.

Level: 1

Type: ERROR

Impact: Other

WCS-49214: Portal template name not specified.
Cause: No portal template name was specified in POST body of request.
Action: Please specify a portal template name.

Level: 1

Type: ERROR

Impact: Other

WCS-49215: Portal name not specified.
Cause: No portal name was specified in POST body of request.
Action: Please specify a portal name.

Level: 1

Type: ERROR

Impact: Other

WCS-49216: Unable to create Portal.
Cause: Internal error creating Portal.
Action: Contact portal administrator and/or see logs for additional errors.

Level: 1

Type: ERROR

Impact: Other

WCS-49217: No Member provided in body.
Cause: Member was not provided in POST body of request.
Action: Provide Member in POST body of request.

Level: 1

Type: ERROR

Impact: Other

WCS-49218: Member name not specified.
Cause: No member name was specified in POST body of request.
Action: Please specify a member name.

Level: 1

Type: ERROR

Impact: Other

WCS-49219: Role name not specified.
Cause: No role name was specified in POST body of request.
Action: Please specify a role name.

Level: 1

Type: ERROR

Impact: Other

WCS-49220: Retrieving Portal Assets failed due to service unavailability
Cause: Service inaccessible.
Action: Contact portal administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-49221: Injectable Service provider did not set Asset Lifecycle service
Cause: Injectable Service provider could not find Asset Lifecycle the service.
Action: Make sure Asset Lifecycle Service injectable provider is available in webapp.

Level: 1

Type: ERROR

Impact: Other

WCS-49222: Portal name specified for asset publishing not found : {0}
Cause: Portal name not found.
Action: Specify a valid portal name.

Level: 1

Type: ERROR

Impact: Other

WCS-49223: Archive for asset upload has not been provided
Cause: Asset archive for upload not provided.
Action: Specify an asset archive for upload.

Level: 1

Type: ERROR

Impact: Other

WCS-49224: Asset archive is invalid : {0}
Cause: Asset archive files or content is not packaged properly.
Action: Include a valid asset archive. See associated message for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-49225: Portal template not found with the name not specified.
Cause: No portal template was found corresponding to the name specified in POST body of request.
Action: Please specify an existing portal template name.

Level: 1

Type: ERROR

Impact: Other

WCS-49251: REST API Injectable Service provider did not set message board service.
Cause: REST API Injectable Service provider did not set message board service.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49252: No 'message' in the request body
Cause: Message data was not found in the request body.
Action: Make sure Message data is specified in the request body.

Level: 1

Type: WARNING

Impact: Other

WCS-49253: Message body not specified
Cause: No 'message' in the body when trying to create a new message.
Action: Specify a valid message body that is not null or blank.

Level: 1

Type: WARNING

Impact: Other

WCS-49254: 'id' should not be supplied with a POST -- use PUT if you want to update
Cause: 'id' should not be supplied with a POST.
Action: Use PUT if you want to update.

Level: 1

Type: WARNING

Impact: Other

WCS-49255: Error accessing profile for user with GUID {0}. Ignoring.
Cause: Error retrieving user profile.
Action: Verify that the user GUID is correct.

Level: 1

Type: WARNING

Impact: Other

WCS-49256: Permissions class called with wrong number of resource IDs. Expecting 2 or 3, but got {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49257: Error accessing user or portal message board {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49258: Error accessing message {0} from user or portal message board {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49259: Error retrieving messages {0} to {1} from user or portal message board {2}.
Cause: Error retrieving message from user's message board.
Action: Check startIndex and itemsPerPage.

Level: 1

Type: ERROR

Impact: Other

WCS-49260: Error trying to delete message {0} from message board for user or portal {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49261: Error trying to create message on message board for user or portal {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49262: Invalid message board type. Got ''{0}'', expected ''person'' or ''space''.
Cause: Invalid message board type in URI.
Action: Verify that the message board type is either 'person' or 'space'.

Level: 1

Type: ERROR

Impact: Other

WCS-49263: Invalid message type. Got ''{0}'', expected ''private'', ''public'', ''hidden'', ''private_hidden''.
Cause: Invalid message type in URI.
Action: Verify that the message type is either 'private', 'public', hidden' or 'private_hidden'.

Level: 1

Type: ERROR

Impact: Other

WCS-49264: Message type ''{0}'' not supported with message board type ''{1}''.
Cause: Invalid message type in URI.
Action: Verify that the message type is empty.

Level: 1

Type: ERROR

Impact: Other

WCS-49265: Message type ''{0}'' not supported for users other than current user.
Cause: Invalid message type in URI.
Action: Verify that the message type is empty.

Level: 1

Type: ERROR

Impact: Other

WCS-49301: REST API Injectable Service provider did not set profile service.
Cause: REST API Injectable Service provider did not set profile service.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49302: Cannot delete a member from a list that the current user does not own.
Cause: Cannot delete a member from a list that the current user does not own.
Action: Make sure REST URL specifies the correct list and is accessing list for the current user.

Level: 1

Type: WARNING

Impact: Other

WCS-49303: Retrieving list names is only supported for current user. Found GUID {0}.
Cause: Retrieving list names is only supported for current user.
Action: Make sure REST URL specifies the current user GUID (or @me).

Level: 1

Type: WARNING

Impact: Other

WCS-49304: Creating lists is only supported for the current user. Found GUID {0}.
Cause: Creating lists is only supported for current user.
Action: Make sure REST URL specifies the current user GUID (or @me).

Level: 1

Type: WARNING

Impact: Other

WCS-49305: No 'list' in the request body
Cause: List data was not found in the request body.
Action: Make sure List data is specified in the request body.

Level: 1

Type: WARNING

Impact: Other

WCS-49306: List name not specified
Cause: No 'name' in the body when trying to create a new list.
Action: Specify a valid list name that is not null or blank.

Level: 1

Type: WARNING

Impact: Other

WCS-49307: Creating connections is only supported for the current user. Found GUID {0}.
Cause: Creating connections is only supported for current user.
Action: Make sure REST URL specifies the current user GUID (or @me).

Level: 1

Type: WARNING

Impact: Other

WCS-49308: No 'member' in the request body
Cause: Member data was not found in the request body.
Action: Make sure member data is specified in the request body.

Level: 1

Type: WARNING

Impact: Other

WCS-49309: Connection GUID not specified
Cause: No 'guid' in the body when trying to create a new connection.
Action: Specify a valid user GUID that is not null or blank.

Level: 1

Type: WARNING

Impact: Other

WCS-49310: Only connection lists can be deleted, and only by the current user. Found GUID {0} and list ID {1}.
Cause: Only connection lists can be deleted, not the current user or the intrinsic connections list. They can only be deleted by the current user.
Action: Make sure REST URL specifies the connection list ID, not @self or @connections, and is accessing the current user.

Level: 1

Type: WARNING

Impact: Other

WCS-49311: Accessing status is only supported for @self id. Found selector {0}.
Cause: Accessing status is only supported for @self id.
Action: Make sure REST URL specifies the @self selector.

Level: 1

Type: WARNING

Impact: Other

WCS-49312: Updating status is only supported for the current user. Found GUID {0}.
Cause: Accessing status is only supported for the current user.
Action: Make sure REST URL is accessing the current user.

Level: 1

Type: WARNING

Impact: Other

WCS-49313: Error trying to access profile for user {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49314: Error checking for people permissions. Wrong number of arguments. Expected 1-3, but found {0} for permission {1}. Ignoring.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49315: Error checking for people permissions. Could not parse type {0}. Expected: person, status, lists, list, member. Ignoring.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49316: Error trying to access connection lists for user {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49317: Error accessing connection list {0}.
Cause: Error accessing connection list.
Action: Verify that the list ID is correct.

Level: 1

Type: WARNING

Impact: Other

WCS-49318: Error accessing connection relationship of user {0} to current user {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49319: Error adding/deleting user {0} for list {1} of current user.
Cause: Error adding/deleting user in connection list of current user.
Action: Verify that the list ID is correct and is not @CONNECTIONS (use invitations instead) and the user GUID is correct, and that the user is not already a member of the list when adding user.

Level: 1

Type: WARNING

Impact: Other

WCS-49320: "Error using Resource Action Handler to get link to user {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49321: Invalid user search query {0}. Unable to process search. Verify that the search query is of the form [loginid:equals:X] or [guid:equals:Y].
Cause: Invalid search query was passed into People REST API.
Action: Verify that the search query is of the form [loginid:equals:X] or [guid:equals:Y].

Level: 1

Type: WARNING

Impact: Other

WCS-49322: Error accessing connection list {0} for user {1}.
Cause: Error accessing connection list.
Action: Verify that the list ID and GUID are correct.

Level: 1

Type: WARNING

Impact: Other

WCS-49323: Invalid invitation search query {0}. Unable to process search. Verify that the search query is either [invitor:equals:@me] or [invitee:equals:@me].
Cause: Invalid search query was passed into People Invitations REST API.
Action: Verify that the search query is either [invitor:equals:@me] or [invitee:equals:@me].

Level: 1

Type: WARNING

Impact: Other

WCS-49324: No 'invitation' in the request body
Cause: Invitation data was not found in the request body when trying to create a new invitation.
Action: Make sure Invitation data is specified in the request body.

Level: 1

Type: WARNING

Impact: Other

WCS-49325: Invitation invitee GUID not specified
Cause: No 'invitee' item or 'guid' item in 'invitee' in the body when trying to create a new invitation.
Action: Specify a valid invitee user GUID that is not null or blank.

Level: 1

Type: WARNING

Impact: Other

WCS-49326: Error retrieving invitations for current user.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49327: Error inviting user {0} to be a connection of the current user
Cause: Error inviting user {0} to be a connection of the current user.
Action: Verify the invitee user GUID is correct and is not null or blank.

Level: 1

Type: WARNING

Impact: Other

WCS-49328: The invitation ID in the request body ({0}) did not match the ID in the query string ({1})
Cause: The invitation ID in the request body did not match the ID in the query string when trying to update invitation status.
Action: Make sure the invitation ID specified in the request body matches the invitation ID in the query string.

Level: 1

Type: WARNING

Impact: Other

WCS-49329: Error deleting invitation {0}
Cause: Error deleting invitation {0}.
Action: Verify the invitation ID is correct, and that the current user has permissions to delete the invitation (i.e. created or received it).

Level: 1

Type: WARNING

Impact: Other

WCS-49330: Unable to update invitation {0} with status {1}. Verify that the invitation id is valid, the current user has permission to update the invitation, and that the status is either "accepted" or "ignored".
Cause: Unable to update invitation status.
Action: Verify that the invitation id is valid, the current user has permission to update the invitation, and that the status is either "accepted" or "ignored".

Level: 1

Type: WARNING

Impact: Other

WCS-49331: Error inviting user {0} to be a connection of current user.
Cause: Error inviting user to be a connection of current user.
Action: Verify that the user GUID is correct, and that the user has not already been invited by the current user.

Level: 1

Type: WARNING

Impact: Other

WCS-49332: Error accessing relationship information for connections and invitations of current user.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49333: Unable to lookup email address {0}.
Cause: Unable to lookup email address.
Action: Make sure the email address is correct, and the identity store is configure properly.

Level: 1

Type: WARNING

Impact: Other

WCS-49334: Error creating connection list {0}. List already exists.
Cause: Error creating connection list. List already exists.
Action: Choose a new name for the new connection list.

Level: 1

Type: WARNING

Impact: Other

WCS-49351: REST API Injectable Service provider did not set activity service.
Cause: REST API Injectable Service provider did not set activity service.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49352: No 'activity' in the request body
Cause: Activity data was not found in the request body.
Action: Make sure Activity data is specified in the request body.

Level: 1

Type: WARNING

Impact: Other

WCS-49353: 'id' should not be supplied with a POST -- use PUT if you want to update
Cause: 'id' should not be supplied with a POST.
Action: Use PUT if you want to update.

Level: 1

Type: WARNING

Impact: Other

WCS-49354: Creating activities requires the service ID and activity type to be present.
Cause: Creating activities requires the service ID and activity type.
Action: Make sure the activity POST contains the service ID and activity type.

Level: 1

Type: WARNING

Impact: Other

WCS-49355: Error accessing activity {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49356: Error accessing activities for user {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49357: Error accessing activities for Portal {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49358: Error trying to access profile for user {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49359: Unable to retrieve object type for parameter object {0} in activity {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49360: Unable to retrieve object with index {0} for parameter object {1} in activity {2}, because there are only {3} objects available.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49361: Unable to parse key {0}, activity type {1}, service id {2}, activity id {3} for activity parameter. Should be of form ''{actor[n]''} or ''{object[n]''}.
Cause: Unable to parse key for activity parameter.
Action: Make sure key starts with actor or object and the index is numeric.

Level: 1

Type: WARNING

Impact: Other

WCS-49362: Unable to find Portal scope for {0}.
Cause: Unable to find Portal scope from specified value.
Action: Make sure Portal value is correct.

Level: 1

Type: WARNING

Impact: Other

WCS-49363: Unable to publish activity for service {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49364: Error accessing comments for object {2} with service id {0} and type {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49365: Error creating comment for object {2} with service id {0} and type {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49366: Error deleting comment {0}.
Cause: Unable to delete comment.
Action: Make sure current user has permission to delete this comment.

Level: 1

Type: WARNING

Impact: Other

WCS-49367: Error accessing activity object with id {2} with service id {0} and type {1}.
Cause: Unable to access activity object.
Action: Make sure the service id, object type, and object id are correct.

Level: 1

Type: WARNING

Impact: Other

WCS-49368: Error accessing activity object details for object with id {2} with service id {0} and type {1}.
Cause: Unable to access activity object details.
Action: Make sure the service id, object type, and object id are correct.

Level: 1

Type: WARNING

Impact: Other

WCS-49369: Error accessing comments service.
Cause: Error accessing comments service.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49370: REST API Injectable Service provider did not set comment service.
Cause: REST API Injectable Service provider did not set comment service.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49371: No 'comment' in the request body
Cause: Comment data was not found in the request body.
Action: Make sure comment data is specified in the request body.

Level: 1

Type: WARNING

Impact: Other

WCS-49372: Creating comments requires the comment text to be present.
Cause: Creating comments requires the comment text.
Action: Make sure the comment POST contains the comment text.

Level: 1

Type: WARNING

Impact: Other

WCS-49373: Invalid data parameter ''{0}'' for activity. Must include ''data'', and may include ''commentsSummary'' and ''likesSummary''.
Cause: Invalid data parameter for activity.
Action: Make sure the data parameter includes 'data'. 'commentsSummary' and 'likesSummary' are optional.

Level: 1

Type: WARNING

Impact: Other

WCS-49374: Error accessing likes for object {2} with service id {0} and type {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49375: Error creating like for object {2} with service id {0} and type {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49376: Error deleting like {0}.
Cause: Unable to delete like.
Action: Make sure current user has permission to delete this like.

Level: 1

Type: WARNING

Impact: Other

WCS-49377: Error accessing likes service.
Cause: Error accessing likes service.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49378: REST API Injectable Service provider did not set like service.
Cause: REST API Injectable Service provider did not set like service.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49379: No 'like' in the request body
Cause: Like data was not found in the request body.
Action: Make sure like data is specified in the request body.

Level: 1

Type: WARNING

Impact: Other

WCS-49380: Activity ID is null
Cause: Activity ID cannot be null.
Action: Use valid activity ID.

Level: 1

Type: WARNING

Impact: Other

WCS-49382: Error accessing comments for activity {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49383: Error creating comment for activity {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49384: Error creating like for activity {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49385: Error accessing likes for activity {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49386: User has insufficient permission to access object {2} with service id {0} and type {1}.
Cause: Unable to access the object due to permission settings.
Action: Make sure current user has permission to access this object.

Level: 1

Type: WARNING

Impact: Other

WCS-49387: User has insufficient permission to access activity {0}.
Cause: Unable to access the object due to permission settings.
Action: Make sure current user has permission to access this object.

Level: 1

Type: WARNING

Impact: Other

WCS-49388: User has insufficient permission to access object {2} with service id {0} and type {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49389: User has insufficient permission to access activity {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49390: Unable to parse date {0}. Make sure date format is yyyy-MM-dd.
Cause: Date format is not correct.
Action: Make sure date format is yyyy-MM-dd.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49401: REST API Injectable Service provider did not set feedback service.
Cause: REST API Injectable Service provider did not set feedback service.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49402: No 'message' in the request body
Cause: Message data was not found in the request body.
Action: Make sure Message data is specified in the request body.

Level: 1

Type: WARNING

Impact: Other

WCS-49403: Message body not specified
Cause: No 'message' in the body when trying to create a new feedback item.
Action: Specify a valid message body that is not null or blank.

Level: 1

Type: WARNING

Impact: Other

WCS-49404: 'id' should not be supplied with a POST -- use PUT if you want to update
Cause: 'id' should not be supplied with a POST.
Action: Use PUT if you want to update.

Level: 1

Type: WARNING

Impact: Other

WCS-49405: Error retrieving display name from profile for user with GUID {0}. Ignoring.
Cause: Error retrieving user profile.
Action: Verify that the user GUID is correct.

Level: 1

Type: WARNING

Impact: Other

WCS-49406: Permissions class called with wrong number of resource IDs. Expecting 1 or 2, but got {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49407: Error accessing feedback for user {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49408: Error accessing feedback item from user {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49409: Error retrieving received feedback items from {0} to {1} for user {2}.
Cause: Error retrieving received feedback for user.
Action: Check startIndex and itemsPerPage.

Level: 1

Type: ERROR

Impact: Other

WCS-49410: Error retrieving given feedback items from user {0} for items {1} to {2}.
Cause: Error retrieving feedback for user.
Action: Check startIndex and itemsPerPage.

Level: 1

Type: ERROR

Impact: Other

WCS-49411: Error trying to delete feedback {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49412: Error trying to create feedback for user {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49413: Unable to find link {0} for feedback item {1}..
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49414: Error trying to get feedback for user. Either unknown GUID {0} or unknown selector {1}.
Cause: Either an unknown GUID was entered, expected @me or GUID or unknown selector was entered, expected @self, @all, or valid GUID. Selector can only be a valid GUID if the {guid} value entered is @me or the GUID of the current logged in user.
Action: Double check the GUID or selector entered is valid.

Level: 1

Type: WARNING

Impact: Other

WCS-49415: No 'receivedUser' in the request body
Cause: The received user data was not found in the request body.
Action: Make sure the received user is specified in the request body.

Level: 1

Type: WARNING

Impact: Other

WCS-49416: Invalid selector for creating feedback. Expected ''@self'', but found ''{0}''.
Cause: Feedback can only be POSTed to a URI of the form {guid}/@self.
Action: Make sure the URI selector is @self.

Level: 1

Type: WARNING

Impact: Other

WCS-49417: GUID specified in URI and GUID specified in POST body do not match. URI GUID was ''{0}'', POST body received user GUID was ''{1}''.
Cause: GUID in URI and GUID specified in POST body received user GUID must match.
Action: Make sure the URI GUID and POST body received user GUID match.

Level: 1

Type: WARNING

Impact: Other

WCS-49451: Error trying to access profile for user {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49452: The current DB version does not support this REST API. Expected version 11.1.1.2.0 or greater.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49453: Unable to use Resource Action Handler to get link to object with type {0} from service {1} and ID {2}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49454: The ''{0}'' parameter was not found in the query string, or was empty.
Cause: The query string was missing a required parameter.
Action: Make sure the specified parameter is present in the query string and is not empty.

Level: 1

Type: WARNING

Impact: Other

WCS-49455: The ''{0}'' date time parameter could not be parsed: ''{1}''
Cause: The query string date time parameter was not formatted correctly.
Action: Make sure the specified date time parameter is formatted according to the XSD spec: YYYY-MM-DD with optional time and timezone components hh:mm:ss, +HH:mm, -HH:mm, or Z. The time component may include milliseconds, but they will not be used.

Level: 1

Type: WARNING

Impact: Other

WCS-49456: Unable to encode data for use in URI.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-49457: Unable to decode data from URI: {0}.
Cause: Unable to decode data from URI.
Action: Make sure the specified data is correctly URL encoded before being passed to the server.

Level: 1

Type: WARNING

Impact: Other

WCS-49458: A query string parameter was set to the default value of ''{0}'', which is a default template parameter, not a valid value.
Cause: A query string parameter was set to a default template parameter value with a starting '{ and ending '}, which is not a valid value.
Action: Make sure the query string parameter is either set to a valid value, or removed.

Level: 1

Type: WARNING

Impact: Other

WCS-49459: Secure Enterprise Search is not configured.
Cause: SES Crawl is not enabled for this instance
Action: Make sure crawl is enabled for Documents, Forums, and Portals sources

Level: 1

Type: WARNING

Impact: Other

WCS-49460: This Secure Enterprise Search version is not supporting facets.
Cause: SES Version is not supporting faceted queries
Action: Make sure to use the SES version that supports faceted serch

Level: 1

Type: WARNING

Impact: Other

WCS-49461: No UriService is available for the REST resource {0}.
Cause: No UriService is available for the REST resource.
Action: Make sure the REST resource is correctly configured and annotated.

Level: 1

Type: ERROR

Impact: Other

WCS-49501: Injectable Service provider did not set search service
Cause: Injectable Service provider could not find the search service.
Action: Make sure Search Service injectable provider is available in webapp.

Level: 1

Type: ERROR

Impact: Other

WCS-49509: Column could not be found for column id [{0}]
Cause: Column ID was not found.
Action: Make sure Column ID exists.

Level: 1

Type: ERROR

Impact: Other

WCS-49513: Search parameter must follow [column:[operator:]]value;[column:[operator:]value] syntax
Cause: Search parameter syntax not understood.
Action: Syntax must follow: [column:[operator:]]value;[column:[operator:]value]

Level: 1

Type: ERROR

Impact: Other

WCS-49514: Search parameter must follow [column:[operator:]]value;[column:[operator:]value] syntax
Cause: Search parameter syntax not understood.
Action: Syntax must follow: [column:[operator:]]value;[column:[operator:]value]

Level: 1

Type: ERROR

Impact: Other

WCS-49515: Comparator [{0}] is invalid
Cause: Invalid search comparator.
Action: Use valid search comparator.

Level: 1

Type: ERROR

Impact: Other

WCS-49516: Invalid argument: [{0}]
Cause: Invalid search argument.
Action: Use valid search argument.

Level: 1

Type: ERROR

Impact: Other

WCS-49517: Internal Search Error: [{0}]
Cause: Internal search error.
Action: Please see error on server console.

Level: 1

Type: ERROR

Impact: Other

WCS-49551: REST API Injectable Service provider did not set event service.
Cause: REST API Injectable Service provider did not set event service.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49552: Unable to find Portal scope for {0}.
Cause: Unable to find Portal scope from specified value.
Action: Make sure Portal value is correct.

Level: 1

Type: WARNING

Impact: Other

WCS-49553: Unable to access calendar for scope {0}.
Cause: Unable to access requested calendar.
Action: Make sure the scope value is a valid Portal GUID.

Level: 1

Type: WARNING

Impact: Other

WCS-49554: Unable to access event {0} in Portal scope {1}.
Cause: Unable to access Portal event.
Action: Make sure Portal and event ID values are correct.

Level: 1

Type: WARNING

Impact: Other

WCS-49555: Unable to create event in Portal scope {1}.
Cause: Unable to create Portal event.
Action: Make sure the Portal ID is correct and the current user has permission to create an event in that Portal.

Level: 1

Type: WARNING

Impact: Other

WCS-49556: Unable to update event {0} in Portal scope {1}.
Cause: Unable to update Portal event.
Action: Make sure Portal and event ID values are correct.

Level: 1

Type: WARNING

Impact: Other

WCS-49557: Unable to delete event {0} in Portal scope {1}.
Cause: Unable to delete Portal event.
Action: Make sure Portal and event ID values are correct.

Level: 1

Type: WARNING

Impact: Other

WCS-49558: No 'event' in the request body.
Cause: Event data was not found in the request body.
Action: Make sure Event data is specified in the request body.

Level: 1

Type: WARNING

Impact: Other

WCS-49559: Event POST or PUT request bodies cannot contain the ID, author, created date, modifier, modified date, or duration.
Cause: Event POST or PUT request bodies cannot contain the ID, author, created date, modifier, modified date, or duration.
Action: Make sure Event data does not contain the ID, author, created date, modifier, modified date, or duration in the request body.

Level: 1

Type: WARNING

Impact: Other

WCS-49560: The event object was missing required data. Events are required to have summary, startTime, and endTime data.
Cause: The event object was missing required data.
Action: Make sure Event summary, startTime, and endTime data are specified in the event object.

Level: 1

Type: WARNING

Impact: Other

WCS-49561: Invalid portal GUID {0}.
Cause: This GUID does not refer to a valid portal.
Action: Make sure the portal GUID is not null or empty, and refers to a valid portal. Home Portal cannot be used for portal events.

Level: 1

Type: WARNING

Impact: Other

WCS-49562: Invalid time sequence: startTime {0} must be before endTime {1}..
Cause: The startTime must be before the endTime.
Action: Make sure the startTime is before the endTime.

Level: 1

Type: WARNING

Impact: Other

WCS-49563: Unable to access event categories for Portal scope {0}.
Cause: Unable to access Portal event categories.
Action: Make sure Portal guid is correct.

Level: 1

Type: WARNING

Impact: Other

WCS-49564: Unable to create event category {0} in Portal scope {1}.
Cause: Unable to create Portal event category.
Action: Make sure the Portal ID is correct and the current user has permission to create an event category in that Portal.

Level: 1

Type: WARNING

Impact: Other

WCS-49565: Unable to delete event category {0} in Portal scope {1}.
Cause: Unable to delete Portal event category.
Action: Make sure Portal and event category name values are correct.

Level: 1

Type: WARNING

Impact: Other

WCS-49601: Injectable Service provider did not set tagging service
Cause: Injectable Service provider could not find the tagging service.
Action: Make sure Tagging Service injectable provider is available in webapp.

Level: 1

Type: ERROR

Impact: Other

WCS-49613: Required query Parameter "{0}" was not found.
Cause: Query parameter "{0}" omitted or null.
Action: Query parameter "{0}" required. Please try again with a non-null value for this parameter

Level: 1

Type: ERROR

Impact: Other

WCS-49614: {1} Body must include "{0}" as a field. Could not complete POST Request.
Cause: {1} Body must include "{0}" as a field.
Action: Provide a complete {1} Object as the body for this request

Level: 1

Type: ERROR

Impact: Other

WCS-49615: Tag {0} could not be deleted.
Cause: There was an error while deleting this item
Action: Please check if item exists and if you have the appropriate permissions to delete this item.

Level: 1

Type: ERROR

Impact: Other

WCS-49616: Item with service Id: {0} and resource id: {1} could not be deleted.
Cause: There was an error while deleting this item
Action: Please check if item exists and if you have the appropriate permissions to delete this item.

Level: 1

Type: ERROR

Impact: Other

WCS-49617: Item with service id: {0} and resource id: {1} is already tagged by you
Cause: There was an error while tagging this item
Action: Please check if item exists and if you have the appropriate permissions to tag this item.

Level: 1

Type: ERROR

Impact: Other

WCS-49618: Item with service id: {0} and resource id: {1} was not found
Cause: There was an error while finding this item
Action: Please check if item exists and if you have the appropriate permissions to tag this item.

Level: 1

Type: ERROR

Impact: Other

WCS-49619: Tag {0} could not be found.
Cause: There was an error while finding this tag
Action: Please check if item exists and if you have the appropriate permissions to tag this item.

Level: 1

Type: ERROR

Impact: Other

WCS-49620: Required query Parameter "{0}" was not valid.
Cause: Query parameter "{0}" not valid.
Action: Query parameter "{0}" required. Please try again with a valid value for this parameter

Level: 1

Type: ERROR

Impact: Other

WCS-49651: REST API Injectable Service provider did not set links service.
Cause: REST API Injectable Service provider did not set links service.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49652: No 'source' in the request body
Cause: Links source object was not found in the request body.
Action: Make sure source object is specified in the request body.

Level: 1

Type: ERROR

Impact: Other

WCS-49653: No 'target' in the request body
Cause: Links target object was not found in the request body.
Action: Make sure target object is specified in the request body.

Level: 1

Type: ERROR

Impact: Other

WCS-49654: Error trying to create links.
Cause: Error trying to create links
Action: Make sure webcenter repository is available.

Level: 1

Type: ERROR

Impact: Other

WCS-49655: No 'link' in the request body
Cause: Link data was not found in the request body.
Action: Make sure Link data is specified in the request body.

Level: 1

Type: ERROR

Impact: Other

WCS-49656: Unable to create link
Cause: Link was not created.
Action: See logs for more information.

Level: 1

Type: ERROR

Impact: Other

WCS-49657: Source "serviceid" or "resourceid" not specified
Cause: No source "serviceid" or "resourceid" when trying to create a link.
Action: Specify valid "serviceid" and "resourceid" that are not null or blank.

Level: 1

Type: ERROR

Impact: Other

WCS-49658: Target "serviceid" or "resourceid" not specified
Cause: No target "serviceid" or "resourceid" when trying to create a link.
Action: Specify valid "serviceid" and "resourceid" that are not null or blank.

Level: 1

Type: ERROR

Impact: Other

WCS-49659: Attempted operation resulted in security exception
Cause: Insufficient authorization.
Action: Contact portal administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-49701: Injectable Service provider did not set recommendation service
Cause: Injectable Service provider could not find the recommendation service.
Action: Make sure the Activity Graph Service injectable provider is available in webapp.

Level: 1

Type: ERROR

Impact: Other

WCS-49702: A database exception occured when connecting to the recommendation service
Cause: A database exception occured when connecting to the recommendation service
Action: Make sure the Activities data source is correctly configured and that the database server is working.

Level: 1

Type: ERROR

Impact: Other

WCS-49703: The Activity Graph engines have not been run yet; there is no data to query. Please contact your administrator to configure and run the Activity Graph engines.
Cause: The Activity Graph engines have not been run yet and there is no data to query.
Action: Please contact your administrator to configure and run the Activity Graph engines.

Level: 1

Type: WARNING

Impact: Other

WCS-49704: An exception occured when connecting to the recommendation service
Cause: An exception occured when connecting to the recommendation service
Action: Make sure the Activity Graph server is correctly configured and is working.

Level: 1

Type: WARNING

Impact: Other

WCS-49705: The item class urn and object urns in the request body ({0}, {1}) did not match the values in the path ({2}, {3})
Cause: The item class urn and object urns in the request body did not match the values in the path when trying to update item status.
Action: Make sure the item class urn and object urn specified in the request body matches the values in the uri path.

Level: 1

Type: WARNING

Impact: Other

WCS-49706: Unable to update item {0}, {1} with status {2}. Verify that the item''s class URN and object URN are valid, that the current user has permission to update the item, and that the status is either "interested" or "not interested".
Cause: Unable to update the item's status.
Action: Verify that the item's class URN and object URN are valid, that the current user has permission to update the item, and that the status is either "interested" or "not interested".

Level: 1

Type: WARNING

Impact: Other

WCS-49707: Unable to update item. Verify that the item's class URN and object URN are valid.
Cause: The item's class URN and object URN must be specified
Action: Verify that the item's class URN and object URN are valid and specified

Level: 1

Type: ERROR

Impact: Other

WCS-49708: Unable to query for common items. Verify that the required parameters are valid and specified.
Cause: One or more mandatory query parameters have not been specified.
Action: Verify that the required parameters are valid and specified.

Level: 1

Type: WARNING

Impact: Other

WCS-49709: Unable to query for recommendations. Verify that the required parameters are valid and specified. You need to provide a recipe, an objectURN and either a classURN or serviceId parameters.
Cause: One or more mandatory query parameters have not been specified.
Action: Verify that the required parameters are valid and specified. You need to provide a recipe, an objectURN and either a classURN or serviceId parameters.

Level: 1

Type: WARNING

Impact: Other

WCS-49710: One of the query arguments is invalid. Verify that all arguments are correct, and that recipe and similarity URNs match the specified object types.
Cause: One or more query parameters is invalid.
Action: Verify that all arguments are correct, and that recipe and similarity URNs match the specified object types.

Level: 1

Type: WARNING

Impact: Other

WCS-49711: The following recipe is invalid: {0}. Verify that all similarity URNs are correct, that each URN has a positive weight, and that the recipe is formatted like this: item-edit:100;item-tag:10.
Cause: The recipe is invalid.
Action: Verify that all similarity URNs are correct, that each URN has a positive weight, and that the recipe is formatted like this: item-edit:100;item-tag:10.

Level: 1

Type: WARNING

Impact: Other

WCS-49712: The Activity Graph service is not present in this installation. It has either not been installed or not been configured correctly. Please contact your administrator to install and configure the Activity Graph service.
Cause: The Activity Graph service is not present in this installation. It has either not been installed or not been configured correctly.
Action: Please contact your administrator to install and configure the Activity Graph service.

Level: 1

Type: WARNING

Impact: Other

WCS-49713: Unable to query for top items. Verify that the required parameters are valid and specified.
Cause: One or more mandatory query parameters have not been specified.
Action: Verify that the required parameters are valid and specified.

Level: 1

Type: WARNING

Impact: Other

WCS-49714: Unable to query for autocompletions because the query string or index URNs are empty or missing. Verify that the required query string and index URN arguments are present and not empty.
Cause: The autocomplete query string or index URNs are missing.
Action: Verify that the autocomplete query string and index URN arguments are present and not empty.

Level: 1

Type: WARNING

Impact: Other

WCS-49715: The Activity Graph autocomplete engine has not been run yet; there is no data to query. Please contact your administrator to configure and run the Activity Graph engines.
Cause: The Activity Graph autocomplete engine has not been run yet and there is no data to query.
Action: Please contact your administrator to configure and run the Activity Graph engines.

Level: 1

Type: WARNING

Impact: Other

WCS-49716: An exception occured when connecting to the autocomplete service
Cause: An exception occured when connecting to the autocomplete service
Action: Make sure the Activity Graph server is correctly configured and is working.

Level: 1

Type: WARNING

Impact: Other

WCS-49801: Invalid ID
Cause: ID provided in the URL or query parameters is incorrect.
Action: Make sure provided IDs in path or parameters are correct.

Level: 1

Type: ERROR

Impact: Other

WCS-49802: Portal Not Found
Cause: Portal does not exist.
Action: Make sure you specify the correct portal ID is provided and that this portal has not been deleted.

Level: 1

Type: ERROR

Impact: Other

WCS-49803: Could not create object.
Cause: Could not create object based on provided PropertyBean.
Action: Make sure valid paramters were passed for object creation.

Level: 1

Type: ERROR

Impact: Other

WCS-49804: Invalid Query or OrderBy Parameter {0}.
Cause: Query or OrderBy param provided in the URL is incorrect.
Action: Verify that the query name and query parameters you specified are correct. For more information, refer to the PortalQuery API documentation.

Level: 1

Type: ERROR

Impact: Other

WCS-49805: Portal specified with short ID {0} not found.
Cause: Portal not found.
Action: Specify a valid portal short id.

Level: 1

Type: ERROR

Impact: Other

WCS-49806: Portal archive for import has not been provided. Specify the portal archive against the control name {0}.
Cause: Portal archive for import not provided.
Action: Specify a portal archive for import archive against the control name fileName.

Level: 1

Type: ERROR

Impact: Other

WCS-49807: Failed to create temporary directory within 5 attempts.
Cause: Failed to create temporary directory.
Action: Make sure you have read and write permissions on the temporary locations on the server.

Level: 1

Type: ERROR

Impact: Other

WCS-49808: Asset specified for download operation with short ID {0} not found.
Cause: Asset not found.
Action: Specify a valid asset short id.

Level: 1

Type: ERROR

Impact: Other

WCS-49809: Asset specified for download operation with short ID {0} does not belong to the portal {1}.
Cause: Asset specified for download operation does not belong to the specified portal.
Action: Specify a valid asset short id which belongs to the specified portal.

Level: 1

Type: ERROR

Impact: Other

WCS-49810: Asset archive for upload has not been provided. Specify the asset archive against the control name {0}.
Cause: Asset archive for upload not provided.
Action: Specify an asset archive for upload archive against the control name fileName.

Level: 1

Type: ERROR

Impact: Other

WCS-49811: Invalid limit ({0}) or offset ({1}) value for REST query.
Cause: Invalid limit or offset value for REST query.
Action: Make sure the limit is greater than zero and the offset is greater than or equal to zero.

Level: 1

Type: ERROR

Impact: Other

WCS-49812: The portal archive specified is invalid. Specify a valid archive that exists on the file system, and try again.
Cause: The portal archive specified is invalid.
Action: Specify a valid portal archive for upload against the fileName attribute.

Level: 1

Type: ERROR

Impact: Other

WCS-49813: The asset archive specified is invalid. Specify a valid archive that exists on the file system, and try again.
Cause: The asset archive specified is invalid.
Action: Specify a valid asset archive for upload against the fileName attribute.

Level: 1

Type: ERROR

Impact: Other

WCS-49814: Unable to clean up after creation failed for portal template {0}.
Cause: Portal template creation has failed and cleanup has failed.
Action: Check the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-49815: Unable to clean up after creation failed.
Cause: Creation has failed and cleanup has failed.
Action: Check the underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-49816: Seeded asset modification is not allowed.
Cause: Seeded asset modification is not allowed.
Action: Seeded asset modification is not allowed.

Level: 1

Type: ERROR

Impact: Other

WCS-50001: An unexpected error occurred in the notification sub-system.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-50002: Error in Notification Button tag usage - component {0} has attribute {1} whose value is {2}.
Cause: The attribute mentioned in the error cannot be null, but no value was found for this attribute.
Action: Correct your tag usage.

Level: 1

Type: WARNING

Impact: Other

WCS-50003: Component {0} does not support client listeners.
Cause: Tried to add a client listener to a component that does not support client listeners.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-50004: Mandatory parameter {0} not provided in parameters
Cause: The caller did not provide the required parameter to generate notification
Action: Contact your system administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50005: Notification template {0} not found
Cause: The service failed to read the notification template. The template is not available
Action: Contact your system administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50006: Could not create notification contents based on default template {0}
Cause: The service failed to process the default notification template.
Action: Contact your system administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50007: Invalid child element {0} found for parent {1}
Cause: The template contains invalid child elements.
Action: Contact your system administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50008: End tag {0} not found in CDATA section corresponding to the tag at index {2}
Cause: The CDATA section of the template contains a notification tag without corresponding end tag.
Action: Contact your system administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50009: Value for the token {0} not found in parameters
Cause: The value for the token is not provided in the list of parameter values
Action: Contact your system administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50010: Message key {0} not defined in resource bundle of service {1}
Cause: The message key used in the template does not exist in the service resource bundle
Action: Contact your system administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50011: Error occurred in parsing message {0} in resource bundle of service {1}
Cause: The message has invalid syntax
Action: Contact your system administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50012: An unexpected error occurred in the notification sub-system.
Cause: An unexpected error occurred.
Action: Contact your system administrator.

Level: 1

Type: WARNING

Impact: Other

WCS-50013: Failed to add subscription.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-50014: Failed to remove subscription.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-50015: Failed to query subscription.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-50016: Failed to update subscription.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-50017: Failed to save subscription.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-50018: Failed to remove subscription.
Cause: Subscription does not exist
Action: Resubmit the request with correct parameters

Level: 1

Type: ERROR

Impact: Other

WCS-50019: Subscription cannot be added.
Cause: Subscription content is empty
Action: Provide a non empty description

Level: 1

Type: ERROR

Impact: Other

WCS-50020: Error occurred in initializing the notification sender
Cause: Failed initialize notification sender
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50021: Error occurred in sending notification
Cause: Failed to send notification
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50022: Fail to get UMS instance url.
Cause: An unexpected error occurred.
Action: Contact your system administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-50023: Error occurred in saving user preference settings
Cause: Failed to save user preference settings
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50024: The settings document is invalid
Cause: Contents of the settings document are invalid
Action: Verify and correct the settings document

Level: 1

Type: ERROR

Impact: Other

WCS-50025: Fail to get user preference settings for the service {0}
Cause: Fail to get user preference settings for the service
Action: Verify and correct the service

Level: 1

Type: ERROR

Impact: Other

WCS-50026: Service Framework Exception is thrown.
Cause: Service Framework exception thrown.
Action: Check the exception's detail to see the reason why the exception is thrown.

Level: 1

Type: ERROR

Impact: Other

WCS-50027: Notification sender is not configured
Cause: Notification sender is not configured
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50028: Error in parsing notification configuration
Cause: Error in parsing notification configuration
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50029: Error processing activity for notifications
Cause: Error in processing activity for notification
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50030: Failed to initialize context for asynchronous processingError processing
Cause: Failed to initialize context for asynchronous processingError processing
Action: Contact Administrator

Level: 1

Type: ERROR

Impact: Other

WCS-50031: Unexpected error occurred, please retry the unsubscribe operation
Cause: An internal error occurred
Action: Retry the unsubscribe operation. Contact Oracle Support Services if the issue persists.

Level: 1

Type: ERROR

Impact: Other

WCS-50032: Can not find scope for the given name
Cause: The given scope name is invalid
Action: Verify and correct the scope name

Level: 1

Type: ERROR

Impact: Other

WCS-50033: An unexpected error occurred while retrieving configuration document.
Cause: Failed to get configuration document.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-50034: An unexpected error occurred while retrieving service name for service id {0}.
Cause: Failed to get service name.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-50035: An unexpected error occurred while retrieving subscription object type.
Cause: Failed to get subscription object type.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-50036: An unexpected error occurred while sending UMS notification message.
Cause: Failed to send UMS notification message.
Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-52002: error obtaining content repository connection
Cause: A JNDI naming exception occurred while attempting to obtain the content repository connection.
Action: Verify that connections.xml contains a valid entry for the content repository connection.

Level: 1

Type: WARNING

Impact: Other

WCS-52003: error obtaining blog folder for the page
Cause: The blog folder for the page cannot be found or created.
Action: Check the server logs for details on this exception.

Level: 1

Type: WARNING

Impact: Other

WCS-52004: After fail-over, failed to get the item {0} from the repository.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-52005: error obtaining blog entry for the page
Cause: The blog entry for the page cannot be found.
Action: Check the server logs for details on this exception.

Level: 1

Type: WARNING

Impact: Other

WCS-62001: Unexpected error occurred while saving translations for {0},{1}.
Cause: Unexpected error getting translations.
Action: Contact Oracle support services.

Level: 1

Type: ERROR

Impact: Other

WCS-62002: Unexpected error loading translations into WebCenter Portal.
Cause: Unexpected error loading translations.
Action: Contact Oracle support services.

Level: 1

Type: ERROR

Impact: Other

WCS-62003: The MDS Root location for loading translations cannot be null.
Cause: Null MDS root provided for loading translations.
Action: Please specify a valid MDS root location.

Level: 1

Type: ERROR

Impact: Other

WCS-63001: An unexpected error occurred.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63002: An object of type {0} with this id ({1}) already exits.
Cause: An attempt was made to create an object with an id that is already in use.
Action: Specify a unique id.

Level: 1

Type: ERROR

Impact: Other

WCS-63003: The name ({0}) is not valid.
Cause: The specified name is not valid.
Action: Specify a valid name.

Level: 1

Type: ERROR

Impact: Other

WCS-63004: Object has been changed by another user.
Cause: The object has been changed by another user.
Action: Reload the object and try the operation again.

Level: 1

Type: ERROR

Impact: Other

WCS-63005: An Object of type {0} with id={1} could not be found.
Cause: The specified object could not be found. This may be due to the object being deleted by another user.
Action: Specify a valid id.

Level: 1

Type: ERROR

Impact: Other

WCS-63006: Object ({0}) is immutable.
Cause: An attempt to change this object was made, but this object is currently immutable.
Action: Retrieve mutable object to make changes.

Level: 1

Type: ERROR

Impact: Other

WCS-63007: {0} is not a valid reference name to MDS.
Cause: The name is not a valid MDS reference name.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63008: The MDS session does not support updates.
Cause: MDS was not configured correctly to support updates.
Action: Configure the MDS store to support updates.

Level: 1

Type: ERROR

Impact: Other

WCS-63009: An IO error occurred when accessing metadata.
Cause: An IO error occurred in MDS.
Action: See the log for more details on the specific IO error to correct the problem.

Level: 1

Type: ERROR

Impact: Other

WCS-63010: The object is not valid.
Cause: The metadata for the object does not pass validation.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63011: Failed to construct attribute set for list [{0}].
Cause: Failed to construct attribute set for list.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63012: Failed to add data flavor to ListTransferable. List=[{0}] DataFlavor=[{1}]
Cause: Failed to add data flavor to ListTransferable.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63013: The query attribute predicate {0}{1}{2} was ignored because the column does not exist or the comparator is not supported.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-63014: An error occurred when deleting metadata.
Cause: An error occurred in MDS while deleting metadata.
Action: See the log for more details on the specific error to correct the problem.

Level: 1

Type: ERROR

Impact: Other

WCS-63015: A column with the name ({0}) already exists.
Cause: A column was created or renamed with the name of an existing column in the list.
Action: Specify a unique column name within the list.

Level: 1

Type: ERROR

Impact: Other

WCS-63016: A list with the name ({0}) already exists.
Cause: A list was created or renamed with the name of an existing list.
Action: Specify a unique list name.

Level: 1

Type: ERROR

Impact: Other

WCS-63017: The maximum number of columns for this list has been exceeded.
Cause: A list was created or modified with more than 30 columns.
Action: Do not add more than 30 columns to a list.

Level: 1

Type: ERROR

Impact: Other

WCS-63019: The Lists service is not provisioned for scope {0}.
Cause: The Lists service is not provisioned for the specified scope.
Action: Provision the Lists service for the specified scope.

Level: 1

Type: ERROR

Impact: Other

WCS-63020: The value is the wrong data type. The data type expected is {0}.
Cause: The value is the wrong data type.
Action: Use the value with the correct data type.

Level: 1

Type: ERROR

Impact: Other

WCS-63021: The WebCenter repository is not available.
Cause: An error occurred accessing the repository.
Action: Contact your system administrator. Check the log for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-63022: An error occurred accessing the WebCenter metadata repository.
Cause: An error occurred accessing the repository.
Action: Contact your system administrator. Check the log for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-63023: List column values were converted or deleted based on list column changes during import: scope={0}, list={1}, column={2}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-64001: JAXRS framework encryption service threw exception with message {0}.
Cause: JAXRS framework encryption service not initialized correctly.
Action: Ensure JAXRS framework encryption service is initialized.

Level: 1

Type: ERROR

Impact: Other

WCS-64002: JAXRS framework encryption service set up required. Key generator algorithm not set up in credential store framework.
Cause: Key generator algorithm not set up in credential store framework.
Action: Set up key generator algorithm in credential store framework.

Level: 1

Type: WARNING

Impact: Other

WCS-64003: JAXRS framework encryption service set up required. Cipher transformation not set up in credential store framework.
Cause: Cipher transformation not set up in credential store framework.
Action: Set up cipher transformation in credential store framework.

Level: 1

Type: WARNING

Impact: Other

WCS-64005: The ResourceType element named \"{0}\" is missing its \"{1}\" element.
Cause: The specified element is required by ResourceType element and cannot be empty.
Action: Correct the ResourceType by setting the specified element to a non-empty value.

Level: 1

Type: ERROR

Impact: Other

WCS-64006: ResourceType maps require the key element to be of type String.
Cause: The ResourceType map key should be of type String.
Action: Correct the ResourceType by setting the specified map key to a String.

Level: 1

Type: ERROR

Impact: Other

WCS-64007: The ResourceType element \"resourceTypeUrn\" requires a urn value.
Cause: The specified element value is required by ResourceType.
Action: Correct the ResourceType by setting the specified element to a non-empty value.

Level: 1

Type: ERROR

Impact: Other

WCS-64008: The ResourceType element named \"{0}\" must match the end of the resourceType urn name, \"{1}\".
Cause: The end of the resourceType urn name must match the element's name.
Action: Correct the ResourceType by setting the specified element's name to the end of the resourceType urn string.

Level: 1

Type: ERROR

Impact: Other

WCS-64010: The resource config provider cannot be instantiated.
Cause: The resource config provider for Jersey servlet is not configured properly.
Action: Check web.xml to make sure the resource config provider is configured correctly.

Level: 1

Type: ERROR

Impact: Other

WCS-64011: The TokenManager is not initialized.
Cause: The Token Manager is not configured correctly and cannot be initialized.
Action: Check web.xml to make sure the Token Manager is configured correctly.

Level: 1

Type: ERROR

Impact: Other

WCS-64012: Failed to set capabilities for REST resource type {0} due to exception {1}.
Cause: Failed to set capabilities for REST resource.
Action: Make sure REST resource is annotated correctly.

Level: 1

Type: WARNING

Impact: Other

WCS-64013: Null injectee in REST injection resolver class {0}.
Cause: Null injectee in REST injection resolver class.
Action: Make sure REST servlet and resources are configured correctly.

Level: 1

Type: WARNING

Impact: Other

WCS-64014: Missing WebCenter resource registration class.
Cause: The WebCenter resource registration class is missing.
Action: Make sure a WebCenter resource registration class is implemented and registered in the web.xml file and mapped to the oracle.jaxrs.config.registration context parameter.

Level: 1

Type: ERROR

Impact: Other

WCS-64015: The WebCenter resoruce registration class {0} is incorrectly implemented.
Cause: The WebCenter resource registration class does not implement the WebCenterResourceRegistration interface.
Action: Make sure the WebCenter resource registration class implements the WebCenterResourceRegistration interface and is correctly registered in the web.xml file.

Level: 1

Type: ERROR

Impact: Other

WCS-64016: Failed to invoke the WebCenter resoruce registration class {0} due to exception {1} with message {2}.
Cause: Failed to invoke the WebCenter resource registration class at runtime.
Action: Make sure the WebCenter resource registration class is correctly implemented and registered in the web.xml file.

Level: 1

Type: ERROR

Impact: Other

WCS-65001: Web service data control creation failed. Check the WSDL and re-create the data control
Cause: WSDL may be inaccessible or the WSDL file may be incorrect.
Action: Make sure the WSDL is accessible and correct, then re-create the data control.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-65002: An unexpected error occurred while creating visualization.
Cause: Parameter form not generated.
Action: Check the logs for exception.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-67001: {0} caught exception getting {1} caller thread context.
Cause: Some context could not be obtained from a calling thread for propgation to a worker thread.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Threads

WCS-67002: {0} caught exception current subject from caller thread context.
Cause: The current subject could not be obtained from a calling thread.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Threads

WCS-67003: {0} caught exception setting {1} worker thread context.
Cause: Some context could not be set on a worker thread.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Threads

WCS-67004: {0} caught exception removing {1} worker thread context.
Cause: An error occured whilst removing context from a worker thread.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Threads

WCS-67005: {0} caught exception running task: {1}.
Cause: An error occured whilst running a task using the concurrency service.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Threads

WCS-67006: Unexpected name "{0}"
Cause: The given name was not expected.
Action: Correct the name.

Level: 1

Type: ERROR

Impact: Configuration

WCS-67007: Unexpected unit "{0}"
Cause: The given unit was not expected.
Action: Correct the unit.

Level: 1

Type: ERROR

Impact: Configuration

WCS-67008: Error parsing element "{0}"
Cause: An error occured whilst parsing XML for concurrency service configuration.
Action: Correct the configuration XML data.

Level: 1

Type: WARNING

Impact: Configuration

WCS-67009: Error parsing global attribute "{0}" with value "{1}"
Cause: An error occured whilst parsing the value of a global attribute.
Action: Correct the attribute value.

Level: 1

Type: WARNING

Impact: Configuration

WCS-67010: Error parsing attribute "{0}" with value "{1}" for service "{2}"
Cause: An error occured whilst parsing the value of an attribute for a particular service.
Action: Correct the attribute value.

Level: 1

Type: WARNING

Impact: Configuration

WCS-67011: Error parsing attribute "{0}" with value "{1}" for service "{2}" / resource "{3}"
Cause: An error occured whilst parsing the value of an attribute for a particular resource.
Action: Correct the attribute value.

Level: 1

Type: WARNING

Impact: Configuration

WCS-67012: Missing attribute "{0}"
Cause: A mandatory attribute is not defined.
Action: Add the missing attribute.

Level: 1

Type: ERROR

Impact: Configuration

WCS-67013: Invalid time period "{0}"
Cause: The time period used is not recognised.
Action: Specify an integer value followed by a unit of h(hours), m(minutes), s(seconds) or ms(milliseconds).

Level: 1

Type: ERROR

Impact: Configuration

WCS-67014: WebCenter Concurrency Service startup failed
Cause: The concurrency service failed to start successfully.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Threads

WCS-67015: WebCenter Concurrency Service shutdown failed
Cause: The concurrency service failed to shutdown properly.
Action: No action required.

Level: 1

Type: WARNING

Impact: Threads

WCS-67016: {0} is not set
Cause: A required configuration property has not been set.
Action: Set the missing property.

Level: 1

Type: ERROR

Impact: Configuration

WCS-67017: {0} must be positive
Cause: A property is required to have a positive value.
Action: Give the property a positive value.

Level: 1

Type: ERROR

Impact: Configuration

WCS-67018: ADF configuration not available
Cause: ADF configuration for the concurrency service was not available
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

WCS-67019: ADFContext for caller thread has already been got
Cause: The ADFThreadContext.get() has already been called
Action: Make sure that the get() method is only called once

Level: 1

Type: ERROR

Impact: Threads

WCS-67020: No ADFContext for caller thread
Cause: An ADFContext is not available from the caller thread
Action: Make sure an ADFContext is set for the caller thread

Level: 1

Type: ERROR

Impact: Threads

WCS-67021: ADFContext for worker thread is null
Cause: The ADFContext is not available for the worker thread
Action: Make sure that ADFContext.get() has been called

Level: 1

Type: ERROR

Impact: Threads

WCS-67022: ADFContext for worker thread has not been set
Cause: ADFContext.remove() was called before ADFContext.get() was called
Action: Make sure get() is called before remove()

Level: 1

Type: ERROR

Impact: Threads

WCS-67023: {0} caught exception activating worker thread context.
Cause: Some context could not be activated on a worker thread.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Threads

WCS-67024: {0} caught exception deactivating worker thread context.
Cause: Some context could not be deactivated on a worker thread.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Threads

WCS-69251: {0} of {1} is out-of-bounds
Cause: Page is not responding within configured limits
Action: Check the regions on the page to identify which region is problematic, or general system health

Level: 1

Type: WARNING

Impact: Other

WCS-69252: {0} of {1} is out-of-bounds
Cause:
Action:

Level: 1

Type: WARNING

Impact: Other

WCS-69253: {0} of {1} is out-of-bounds.
Cause: Portlet is not responding within configured limits
Action: Check the backend Producer or the network connectivity to it, or general system health

Level: 1

Type: WARNING

Impact: Other

WCS-69254: {0} of {1} is out-of-bounds
Cause: Document Library Upload service is not responding within configured limits
Action: Check the Content Server or the network connectivity to it, or general system health

Level: 1

Type: WARNING

Impact: Other

WCS-69255: {0} of {1} is out-of-bounds
Cause: Document Library Download service is not responding within configured limits
Action: Check the Content Server or the network connectivity to it, or general system health

Level: 1

Type: WARNING

Impact: Other

WCS-72001: Missing @PersistProperty, @PersistText, @PersistCollection or @PersistReference annotation on method: {0}.
Cause: @PersistProperty, @PersistText, @PersistCollection or @PersistReference annotation is required on the accessors corresponding to persistence methods to enable access through the Portal Core Persistence Layer.
Action: Add the @PersistProperty, @PersistText, @PersistCollection or @PersistReference annotation to the accessor as defined in the Portal Core Persistence Layer's integration documentation.

Level: 1

Type: ERROR

Impact: Other

WCS-72002: PersistenceManager does not support method: {0}.
Cause: An attempt was made to use a method that is not supported by the Portal Core Persistence Layer.
Action: Add the required method to the class.

Level: 1

Type: ERROR

Impact: Other

WCS-72003: Invalid value passed to reference operation ''{0}'' for reference ''{1}''. Expected {2}, received {3}.
Cause: A value passed to a reference mutator could not be converted to the required type.
Action: Modify calling code to ensure references are only updated with valid types.

Level: 1

Type: ERROR

Impact: Other

WCS-72004: Cannot instantiate object using abstract PortalEntity interface: {0}
Cause: An attempt was made to create a PortalEntity object using an interface that is marked as abstract.
Action: Supply a non-abstract type or remove the @AbstractEntity annotation from this interface.

Level: 1

Type: ERROR

Impact: Other

WCS-72005: Unable to delete null {0}.
Cause: A null PortalEntity or PortalEntityObject was supplied.
Action: Supply a non-null PortalEntity or PortalEntityObject.

Level: 1

Type: WARNING

Impact: Other

WCS-72006: Unable to delete PortalEntity. A PortalEntity in portal ''{0}'' and namespace ''{1}'' with name ''{2}'' was not found.
Cause: An attempt was made to delete a PortalEntity object that does not exist.
Action: Ensure that the supplied portal, namespace and name values are correct.

Level: 1

Type: WARNING

Impact: Other

WCS-72007: Unable to delete PortalEntity. A PortalEntity with ID ''{0}'' was not found.
Cause: An attempt was made to delete a PortalEntity object that does not exist.
Action: Ensure that the supplied ID is correct.

Level: 1

Type: WARNING

Impact: Other

WCS-72008: PortalEntity in portal ''{0}'' and namespace ''{1}'' with name ''{2}'' was found but is not of the requested type. Type requested = {3}, type found = {4}.
Cause: The type of PortalEntity object found in the persistence store was not as expected.
Action: Ensure that the supplied portal, namespace, name and type parameters are correct.

Level: 1

Type: ERROR

Impact: Other

WCS-72009: PortalEntity object with ID ''{0}'' was found but is not of the requested type. Type requested = {1}, type found = {2}.
Cause: The type of PortalEntity object found in the persistence store was not as expected.
Action: Ensure that the supplied ID and type parameters are correct.

Level: 1

Type: ERROR

Impact: Other

WCS-72010: An error occurred while starting a transaction.
Cause: An error occurred while starting a transaction.
Action: Check the root cause of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-72011: An error occurred while committing a transaction.
Cause: An error occurred while committing a transaction.
Action: Check the root cause of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-72012: An error occurred while rolling-back a transaction.
Cause: An error occurred while rolling-back a transaction.
Action: Check the root cause of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-72013: An error occurred while checking the status of a transaction.
Cause: An error occurred while checking the status of a transaction.
Action: Check the root cause of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-72014: Unable to read the value of property ''{0}'' of PortalEntity ''{1}'' using method ''{2}''.
Cause: An error occurred while trying to read a property of a PortalEntity object.
Action: Use the associated exception to determine why the property could not be read.

Level: 1

Type: ERROR

Impact: Other

WCS-72015: Unable to create XML document.
Cause: An error occurred while using JAXB to create an XML document.
Action: Use the associated exception to determine why JAXB serialization failed.

Level: 1

Type: ERROR

Impact: Other

WCS-72018: Unable to read XML document.
Cause: An error occurred while using JAXB to read an XML document.
Action: Use the associated exception to determine why JAXB deserialization failed.

Level: 1

Type: ERROR

Impact: Other

WCS-72019: Unable to set the value of property ''{0}'' for PortalEntity ''{1}'' using method ''{2}''.
Cause: An error occurred while trying to set a property of a PortalEntity object.
Action: Use the associated exception to determine why the property could not be set.

Level: 1

Type: ERROR

Impact: Other

WCS-72020: Unable to find set method for property ''{0}'' of PortalEntity ''{1}''.
Cause: An error occurred while trying to set a property of a PortalEntity object.
Action: Unable to find set method for the property.

Level: 1

Type: ERROR

Impact: Other

WCS-72021: Unable to set references for ''{0}'' of property ''{1}'' for PortalEntity ''{2}''.
Cause: An error occurred while trying to set a reference property of a PortalEntity object.
Action: Use the associated exception to determine why the property could not be set.

Level: 1

Type: ERROR

Impact: Other

WCS-72022: Unsupported data type: {0}.
Cause: A data type has been used for a persisted property of an object which is not supported by the Portal Core Persistence Layer.
Action: Use a data type specified by the oracle.webcenter.portal.persistence.PersistedDataType enum.

Level: 1

Type: ERROR

Impact: Other

WCS-72023: Invalid offset {0} for data type {1}
Cause: The offset used for a persisted property is not valid.
Action: Try using a smaller offset value, if possible.

Level: 1

Type: ERROR

Impact: Other

WCS-72024: PortalEntity object with short ID ''{0}'' was found but is not of the requested type. Type requested = {1}, type found = {2}.
Cause: The type of PortalEntity object found in the persistence store was not as expected.
Action: Ensure that the supplied short ID and type parameters are correct.

Level: 1

Type: ERROR

Impact: Other

WCS-72025: Unable to delete PortalEntity. A PortalEntity with short ID ''{0}'' was not found.
Cause: An attempt was made to delete a PortalEntity object that does not exist.
Action: Ensure that the supplied short ID is correct.

Level: 1

Type: WARNING

Impact: Other

WCS-72026: A PortalEntity object with ID ''{0}'' and name ''{1}'' was found but is not of the expected type. Type expected = {2}, type found = {3}.
Cause: The type of a PortalEntity object found in the persistence store was not as expected.
Action: Ensure that the type requested in the query is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-72027: Invalid pagination requested in query: Row limit {0}, first row {1}.
Cause: Invalid criteria specified for query pagination.
Action: Ensure that the row limit is greater than zero, and the first row index is greater than or equal to zero.

Level: 1

Type: ERROR

Impact: Other

WCS-72028: Permission class ''{0}'' cannot be used with actions ''{1}''.
Cause: The permission class name and actions specified via an @Authorization annotation on a PortalEntity class cannot be used with the current security manager.
Action: Correct the permission class name or actions.

Level: 1

Type: ERROR

Impact: Other

WCS-72029: Could not find permission class named: ''{0}''.
Cause: A permission class specified by the permissionClassName element of an @Authorization annotation could not be loaded.
Action: Ensure that the name of the class is correct.

Level: 1

Type: ERROR

Impact: Other

WCS-72030: Type ''{0}'' is not valid. More than one property has datatype {1} and offset {2}, see methods: {3} and {4}.
Cause: A type makes incorrect use of the @PersistProperty annotation.
Action: Use a different offset for one of the methods named in the error message.

Level: 1

Type: ERROR

Impact: Other

WCS-72031: Could not find the persistence object with ID {0} and type {1} in the persistent store.
Cause: A PortalEntity was passed to the PersistenceManager but does not correspond to an entity in the persistent store.
Action: Requery the PortalEntity and try the operation again.

Level: 1

Type: ERROR

Impact: Other

WCS-72032: Invalid from-clause for the query. You must specify one or more types.
Cause: The Query.from(Class... types) method was called with either a null or empty list of types.
Action: Update the code to pass one or more types to the Query.from(Class... types) method.

Level: 1

Type: ERROR

Impact: Other

WCS-72033: The query contains an invalid reference to property {0}.
Cause: An invalid property name has been specified in the query.
Action: Update the query to correct the error.

Level: 1

Type: ERROR

Impact: Other

WCS-72034: The property {0} cannot be used for a property comparsion in a query.
Cause: The property type does not implement the Comparable interface and so cannot be used in with an operation that requires a Comparable interface.
Action: Update the query to correct the error.

Level: 1

Type: ERROR

Impact: Other

WCS-72035: The property {0} is not indexed and so cannot be used in a query without enabling the unindexed property mode.
Cause: The property maps to a column that was not marked as indexed and the unindexed property mode is not enabled.
Action: Either use a different property in the query or enable the unindexed property mode for the query.

Level: 1

Type: ERROR

Impact: Other

WCS-72036: The property {0} cannot be used in the order-by clause of the query.
Cause: An invalid property was used in an order-by clause.
Action: Update the query to use a valid property for the order-by clause.

Level: 1

Type: ERROR

Impact: Other

WCS-72037: Could not set the value of the long text field because the CLOB has not been created.
Cause: There has been an attempt to set the value of the long text field before the CLOB has been created.
Action: Update the calling code to create the CLOB before setting the long text field.

Level: 1

Type: ERROR

Impact: Other

WCS-72038: Cannot import ''{1}'' resource ''{0}'' as the target portal is not set and the source portal is not part of the export set
Cause: Resource import failed because the portal ID associated with the resource did not match any portal in the target portal server, or the specified portal was not part of the export set, or the target portal was not set on the importXML() method.
Action: Update the importXML() method to specify a valid portal on the target.

Level: 1

Type: ERROR

Impact: Other

WCS-72039: The target portal for the import does not exist on the portal server.
Cause: Import failed as the target portal does not exist on the portal server.
Action: Update the importXML() method to specify a valid portal on the target.

Level: 1

Type: ERROR

Impact: Other

WCS-72040: The text property getter method {0} has an invalid return type {1}.
Cause: The getter method for the text property has a return type that is neither String nor java.io.Reader.
Action: Update the method to return either String or java.io.Reader.

Level: 1

Type: ERROR

Impact: Other

WCS-72041: The text property setter method {0} has an invalid parameter {1}.
Cause: The first parameter of the setter method for the text property is neither String nor java.io.Reader.
Action: Update the method so that the first parameter is a String or java.io.Reader.

Level: 1

Type: ERROR

Impact: Other

WCS-72042: An attempt was made to create a PortalEntity object named ''{0}'' and type ''{1}'' with a null Portal property.
Cause: PortalEntities must specify a Portal on creation, unless the type of PortalEntity is a Portal.
Action: Ensure that a Portal is set on the PortalEntity object prior to creation.

Level: 1

Type: ERROR

Impact: Other

WCS-72043: An attempt was made to set a PortalEntity object named ''{0}'' and type ''{1}'' with a null Portal property.
Cause: PortalEntities must not specify null as the Portal property on a set operation, unless the type of PortalEntity is a Portal.
Action: Ensure that a null is not set on the PortalEntity, unless the type of PortalEntity is a Portal.

Level: 1

Type: ERROR

Impact: Other

WCS-72044: Failed to set collection ''{0}'' of type ''{1}'' for PortalEntity object of type ''{2}'' on import.
Cause: Collections of this type are not supported.
Action: Ensure that the data being imported is compatible with this version of the portal server.

Level: 1

Type: ERROR

Impact: Other

WCS-72045: While importing object ''{0}'' with ID ''{1}'', could not find referenced object with ID ''{2}'' (reference name ''{3}'').
Cause: An object referenced by an object in the export set could not be found on the target server.
Action: If required, transfer the referenced object from the source server to the target server.

Level: 1

Type: WARNING

Impact: Other

WCS-72046: While importing object ''{0}'' with ID ''{1}'', could not find referencing object with ID ''{2}'' and type ''{3}'' (reference name ''{4}'').
Cause: An object referencing an object in the export set could not be found on the target server.
Action: If required, transfer the referencing object from the source server to the target server.

Level: 1

Type: WARNING

Impact: Other

WCS-72047: Unable to copy a Portal because a Portal with the name ''{0}'' already exists.
Cause: An attempt was made to copy a Portal with the name of an existing Portal.
Action: Ensure that the supplied Portal name is unique.

Level: 1

Type: WARNING

Impact: Other

WCS-72048: The targetPortal parameter must be null when copying a Portal.
Cause: An attempt was made to copy a Portal with the targetPortal parameter set to a none-null value.
Action: Ensure that the targetPortal parameter is set to null.

Level: 1

Type: ERROR

Impact: Other

WCS-72049: The current user is not authorized to perform action ''{2}'' on object {0} ({1}).
Cause: The current user does not have permission to perform an action on an object.
Action: Ensure that the user is granted appropriate permissions.

Level: 1

Type: ERROR

Impact: Other

WCS-72050: A conflict has occurred with your edit, it will be necessary to resubmit the changes using the updated resource.
Cause: An optimitistic locking exception was raised by the persistence store, due to an earliuer update on the resource by another transaction.
Action: Re-try your edits using the updated resource.

Level: 1

Type: ERROR

Impact: Other

WCS-72051: Attempted to apply a security ID {0} on an entity {1} with no Authorization annotation (type {2})
Cause: Either setSecurityId() or setSecurityEntity() was called on this entity with a non-null value, but the type of this entity has no Authorization annotation defined.
Action: Modify the type definition to add the Authorization annotation, or avoid securing this entity type.

Level: 1

Type: ERROR

Impact: Other

WCS-72052: The current user is not authorized to create an object of type ''{0}'' in portal with ID ''{1}''..
Cause: The current user does not have permission to create objects of the specified type.
Action: Ensure that the user is granted appropriate permissions.

Level: 1

Type: ERROR

Impact: Other

WCS-72053: Permission class ''{0}'' cannot be used with actions ''{1}'' in @CreateAuthorization annotation.
Cause: The permission class name and actions specified via a @CreateAuthorization annotation on a PortalEntity class cannot be used with the current security manager.
Action: Correct the permission class name or actions.

Level: 1

Type: ERROR

Impact: Other

WCS-72054: An error occurred while setting the timeout of a transaction.
Cause: An error occurred while setting the timeout of a transaction.
Action: Check the root cause of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-72055: The user is not authorized to perform this operation.
Cause: The user was not authorized to perform the operation.
Action: Check the root cause of the exception for further details.

Level: 1

Type: ERROR

Impact: Other

WCS-72056: A PortalEntity could not be created from PortalEntityObject {0} because no type factories could be found.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72057: None of the available type factories were able to create a PortalEntity from PortalEntityObject {0}.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72058: The EntityManager's transaction is already active.
Cause: An error occurred initializing the TransactionManager.
Action: Modify calling code to remove direct acces to the Portal EntityManager's transaction.

Level: 1

Type: ERROR

Impact: Other

WCS-72059: The EntityManager is configured for JPA.
Cause: An error occurred initializing the TransactionManager.
Action: The Portal EntityManager must be configured for resource local transactions.

Level: 1

Type: ERROR

Impact: Other

WCS-72060: The TransactionManager has uncommitted changes which have been rolled back.
Cause: The TransactionManager's context is ending and the uncommitted changes have been rolled back.
Action: Contact your Oracle Support representative.

Level: 1

Type: ERROR

Impact: Other

WCS-72061: The TransactionManager has uncommitted changes which cannot be rolled back.
Cause: The TransactionManager's context is ending and rollback of its uncommitted changes has failed.
Action: Check the root cause of the exception and contact your Oracle Support representative.

Level: 1

Type: ERROR

Impact: Other

WCS-72062: The TransactionManager cannot begin the transaction as the EntityManager's transaction is already active.
Cause: The EntityManager's transaction is already active.
Action: Ensure that no calling code is directly accessing the Portal EntityManager's transaction.

Level: 1

Type: ERROR

Impact: Other

WCS-72063: The TransactionManager must fully rollback.
Cause: All outstanding transactions must be rolled-back.
Action: Rollback all outstanding transactions.

Level: 1

Type: ERROR

Impact: Other

WCS-72064: An error occurred executing a transactional method.
Cause: An error occurred executing a transactional method.
Action: Check the root cause of the exception.

Level: 1

Type: ERROR

Impact: Other

WCS-72065: Transactions cannot be commited out of order.
Cause: The calling code is attempting to commit transactions out of order.
Action: The calling code must commit transactions in the same order as they were begun.

Level: 1

Type: ERROR

Impact: Other

WCS-72067: Failed to set translation ''{0}'' for Locale ''{1}'' on PortalEntity object of type ''{2}'' on import.
Cause: An error occurred while trying to set a property of a PortalEntity object.
Action: Use the associated exception to determine why the property could not be set.

Level: 1

Type: ERROR

Impact: Other

WCS-72068: None of the available factories are able to create an instance of type ''{0}''.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72401: Cannot determine the ID of the current page. The current page will not be available via the Portal Request Context.
Cause: The Portal Runtime Framework was unable to obtain the ID of the current page using JSF.
Action: Ensure that the application is running in a JSF environment.

Level: 1

Type: WARNING

Impact: Other

WCS-72402: Cannot find a page with ID ''{0}''. The current page will not be available via the Portal Request Context.
Cause: The current page with the given ID could not be found in the Portal's persistent store.
Action: Ensure that the page with the given ID is present in the Portal's persistent store.

Level: 1

Type: WARNING

Impact: Other

WCS-72403: The AdfPortalController Failed to redirect to URL ''{0}''.
Cause: An internal error occurred whilst attempting to perform a redirect of the portal.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72404: Could not load policy factory of type: {0}
Cause: No policy factory classes of the given type could be found.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72405: PortalExternalContext accessed when the PortalExternalContext stack is empty.
Cause: A PortalExternalContext must be pushed on to the context stack before it is first accessed.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72501: Unable to find the CDI bean for type: {0}.
Cause: No beans of the given type are available for injection.
Action: Make sure that an injectable implementation of the given type is on the classpath.

Level: 1

Type: ERROR

Impact: Other

WCS-72551: Method ''{0}'' cannot be called when the current transaction is active.
Cause: A method with a Transactional annotation whose propagation element was set to NEVER was called when a transaction was active.
Action: Make sure the transaction is not active when the method is called.

Level: 1

Type: ERROR

Impact: Other

WCS-72552: Method ''{0}'' must be called when the current transaction is active.
Cause: A method with a Transactional annotation whose propagation element was set to MANDATORY was called when a transaction was not active.
Action: Make sure the transaction is active when the method is called.

Level: 1

Type: ERROR

Impact: Other

WCS-72571: Cache name ''{0}'' is invalid.
Cause: An invalid cache name has been used.
Action: Make sure the cache name is of the form ''oracle.webcenter.*''.

Level: 1

Type: ERROR

Impact: Other

WCS-72601: Failed to create a document with Metadata Object absolute name "{0}".
Cause: An underlying MDS exception caused this.
Action: See related log entries.

Level: 1

Type: ERROR

Impact: Other

WCS-72602: Metadata Object absolute name "{0}" already exists.
Cause: Metadata already exists.
Action: Check the metadata to be created.

Level: 1

Type: ERROR

Impact: Other

WCS-72603: Pattern syntax error in name "{0}".
Cause: Pattern syntax error in name.
Action: Check name.

Level: 1

Type: ERROR

Impact: Other

WCS-72604: Metadata Object absolute name "{0}" not found.
Cause: Metadata not found.
Action: Check the metadata to be found.

Level: 1

Type: ERROR

Impact: Other

WCS-72605: Encountered an MDS exception "{0}" with message "{1}".
Cause: An underlying MDS exception caused this.
Action: Check underlying exception.

Level: 1

Type: ERROR

Impact: Other

WCS-72608: Failed to update a Portal object.
Cause: An underlying exception caused this.
Action: Check underlying exception.

Level: 1

Type: ERROR

Impact: Other

WCS-72609: Failed to delete a Portal object.
Cause: An underlying exception caused this.
Action: Check underlying exception.

Level: 1

Type: ERROR

Impact: Other

WCS-72610: Required parameter {0} not specified.
Cause: Required parameter is not specified.
Action: Ensure that the required parameter is specified.

Level: 1

Type: ERROR

Impact: Other

WCS-72611: Required parameters {0} and/or {1} not specified.
Cause: Required parameters are not specified.
Action: Ensure that the required parameters are specified.

Level: 1

Type: ERROR

Impact: Other

WCS-72612: File type is required for paramter {0}
Cause: File type is not specified in the parameter.
Action: Ensure that the file type is specified.

Level: 1

Type: ERROR

Impact: Other

WCS-72613: A version conflict was detected when updating the portal object. {0}
Cause: The supplied PropertyBean has a non-null currentVersionId property, and it does not match the current version ID of the object it was applied to.
Action: Requery the portal object properties and apply the update again if appropriate.

Level: 1

Type: ERROR

Impact: Other

WCS-72615: PropertyBean create validation failed: {0}
Cause: The supplied PropertyBean violates the validation constraints that are enforced for creation with this type of PropertyBean.
Action: Review the error message for details of the constraint violations.

Level: 1

Type: ERROR

Impact: Other

WCS-72616: PropertyBean update validation failed: {0}
Cause: The supplied PropertyBean violates the validation constraints that are enforced for update with this type of PropertyBean.
Action: Review the error message for details of the constraint violations.

Level: 1

Type: ERROR

Impact: Other

WCS-72620: ValidationFrame not populated.
Cause: The ValidationFrame providing context for PropertyBean validation did not contain state that was expected to be present.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72621: FrameAwareValidator invoked outside of a ValidationFrame.
Cause: The ValidationFrame providing context for PropertyBean validation was not found.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72622: Error getting bean value.
Cause: Inspect the cause exception to determine the underlying cause.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72624: An error occurred while attempting to copy the portlets.
Cause: An exception was thrown while attempting to copy the portlets for a page.
Action: Check the root cause of the exception.

Level: 1

Type: WARNING

Impact: Other

WCS-72625: An error occurred while trying to instantiate the query manager or named query via reflection.
Cause: An exception was thrown while attempting to load query classes via reflection.
Action: Check that the classes requested are valid for this operation.

Level: 1

Type: ERROR

Impact: Other

WCS-72627: The asset of the given Id {0} is not found.
Cause: The asset is not found.
Action: Check that the asset with the given Id value exists.

Level: 1

Type: ERROR

Impact: Other

WCS-72628: Duplicate name: {0}.
Cause: An attempt was made to create an object with a name that has already been used.
Action: Use a different name.

Level: 1

Type: ERROR

Impact: Other

WCS-72629: Duplicate portal name: {0}.
Cause: An attempt was made to create a portal with a name that has already been used for a portal.
Action: Use a different name for the portal.

Level: 1

Type: ERROR

Impact: Other

WCS-72632: Device Operation {0} not allowed.
Cause: Devices and Device Groups cannot be created, modified or deleted in a custom portal
Action: Ensure that the operations are performed at the portal server

Level: 1

Type: ERROR

Impact: Other

WCS-72633: Device group {0} being customized in {1} portal does not exist at the portal server
Cause: Device group being customized at the portal level does not exist
Action: Ensure that device group being customized exists in the portal server

Level: 1

Type: ERROR

Impact: Other

WCS-72637: Authorization failure when trying to delete {0} type object "{1}" with ID: {2}
Cause: The current user is not authorized to delete the object
Action: Ensure that the user is granted the appropriate permissions

Level: 1

Type: ERROR

Impact: Other

WCS-72638: Authorization failure when trying to update {0} type object "{1}" with ID: {2}
Cause: The current user is not authorized to update the object
Action: Ensure that the user is granted the appropriate permissions

Level: 1

Type: ERROR

Impact: Other

WCS-72639: The Portal API object is not attached.
Cause: The Portal API object has a null id. This means it is not attached to any underlying persistence object.
Action: The Portal API client should attach the object or obtain a new object with a valid id from the PortalObjectRepository. The object can become unattached if it has been deleted.

Level: 1

Type: ERROR

Impact: Other

WCS-72640: The persistence resource with ID "{0}" associated with the ManagedPortalObject could not be found.
Cause: The Portal API ManagedPortalObject object is attached to an underlying persistence resouce that is no longer available.
Action: The Portal API client should take appropriate action to account for the deleted Portal API object.

Level: 1

Type: ERROR

Impact: Other

WCS-72641: There was a failure adding member ''{0}'' to portal ''{1}''
Cause: A failure occurred adding a member to a portal.
Action: Examine the logged exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-72642: There was a failure removing member ''{0}'' from portal ''{1}''
Cause: A failure occurred removing a member from a portal.
Action: Examine the logged exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-72643: There was a failure removing members for role ''{0}'' from portal ''{1}''
Cause: A failure occurred removing all members with a role from a portal.
Action: Examine the logged exception for more details.

Level: 1

Type: ERROR

Impact: Other

WCS-72646: Duplicate portal display name: {0}.
Cause: An attempt was made to create a portal with a display name that has already been used for a portal.
Action: Use a different display name for the portal.

Level: 1

Type: ERROR

Impact: Other

WCS-72647: Null portal name.
Cause: An attempt was made to create a portal with a null name.
Action: Use a non-null name for this portal.

Level: 1

Type: ERROR

Impact: Other

WCS-72648: Null portal display name.
Cause: An attempt was made to create a portal with a null display name.
Action: Use a non-null display name for this portal.

Level: 1

Type: ERROR

Impact: Other

WCS-72649: Operation forbidden without authorization to perform action {0} on {1} (type {2}, id {3})
Cause: An attempt was made to perform an unauthorized action.
Action: Ensure user is authorized to perform this action and retry.

Level: 1

Type: ERROR

Impact: Other

WCS-72650: Invalid name: {0}.
Cause: An attempt was made to create an object with a invalid name.
Action: Use a different valid name.

Level: 1

Type: ERROR

Impact: Other

WCS-72651: Invalid portal name: {0}.
Cause: An attempt was made to create a portal with a invalid name.
Action: Use a name containing only letters and digits.

Level: 1

Type: ERROR

Impact: Other

WCS-72652: Invalid portal template name: {0}.
Cause: An attempt was made to create a portal template with a invalid name.
Action: Use a name containing only letters and digits.

Level: 1

Type: ERROR

Impact: Other

WCS-72653: Failed to rename a Portal object.
Cause: An underlying exception caused this.
Action: Check underlying exception.

Level: 1

Type: ERROR

Impact: Other

WCS-72654: Unable to cleanup properly after failed creation of {0}.
Cause: An underlying exception caused this.
Action: Check underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-72655: Some properties have violated their constraints.
Cause: Constrainst have been violated on setting or updating the properties.
Action: Check that the properties values are correct.

Level: 1

Type: ERROR

Impact: Other

WCS-72656: The combination of (isDiscoverable=false and isPublic=true) is not allowed.
Cause: The Access Level setting constraint has been violated.
Action: Check that the properties values are correct.

Level: 1

Type: ERROR

Impact: Other

WCS-72657: Operation is forbidden.
Cause: The operation is forbidden.
Action: Do not attempt this operation.

Level: 1

Type: ERROR

Impact: Other

WCS-72658: Cannot copy service {0} from {1} to {2}, as service not provisioned in {1}.
Cause: The service cannot be copied as it is not provisioned in the source portal.
Action: Exclude the service from the portal copy request.

Level: 1

Type: ERROR

Impact: Other

WCS-72659: Attempt to modify or delete seeded object {0}. Seeded objects cannot be modified or deleted.
Cause: Seeded objects cannot be modified or deleted.
Action: None

Level: 1

Type: ERROR

Impact: Other

WCS-72660: A failure occurred during MDS document contents substitution.
Cause: An underlying exception caused this.
Action: Check underlying exception.

Level: 1

Type: ERROR

Impact: Other

WCS-72661: Unable to cleanup properly after failed deletion of {0}.
Cause: An underlying exception caused this.
Action: Check underlying exception.

Level: 1

Type: WARNING

Impact: Other

WCS-72662: Unable to copy resource bundle documents for portal : {0}.
Cause: An underlying exception caused this.
Action: Check underlying exception.

Level: 1

Type: ERROR

Impact: Other

WCS-72663: Invalid display name: {0}.
Cause: An attempt was made to create an object with a invalid display name.
Action: Use a different valid display name.

Level: 1

Type: ERROR

Impact: Other

WCS-72664: Invalid portal display name: {0}.
Cause: An attempt was made to create a portal with a invalid display name.
Action: Use a display name containing only letters and digits.

Level: 1

Type: ERROR

Impact: Other

WCS-72701: Error in checking if the service ${0} is provisioned for portal ${1}.
Cause: Unable to discover the service's provisioning status.
Action: Examine the exception for further information.

Level: 1

Type: ERROR

Impact: Other

WCS-72702: Error in checking which services are configured.
Cause: Unable to discover which services are configured.
Action: Examine the exception for further information.

Level: 1

Type: ERROR

Impact: Other

WCS-72703: Error in provisioning service ${0} for portal ${1}.
Cause: Unable to provision the service for the portal.
Action: Examine the exception for further information.

Level: 1

Type: ERROR

Impact: Other

WCS-72704: Error in unprovisioning service ${0} for portal ${1}.
Cause: Unable to unprovision the service for the portal.
Action: Examine the exception for further information.

Level: 1

Type: ERROR

Impact: Other

WCS-72705: Error in retrieving the ScopeAPI for the ${0} service.
Cause: Unable to get the ScopeAPI for the service.
Action: Examine the exception for further information.

Level: 1

Type: ERROR

Impact: Other

WCS-72706: Error getting group info for user ${0}.
Cause: Unable to get group info for a user.
Action: Examine the exception for further information.

Level: 1

Type: ERROR

Impact: Other

WCS-72707: Error in copying service ${0} from portal ${1} to portal {2}.
Cause: Unable to unprovision the service for the portal.
Action: Examine the exception for further information.

Level: 1

Type: ERROR

Impact: Other

WCS-72801: Error publishing activity to the activity stream
Cause: Unable to publish an activity to the activity stream.
Action: Examine the exception for further information.

Level: 1

Type: WARNING

Impact: Other

WCS-72802: The {2} role has already been granted for user {1} in portal {0}
Cause: Unable to grant the role because it has already been granted.
Action: Examine the exception for further information.

Level: 1

Type: ERROR

Impact: Other

WCS-72803: Failed to grant the {2} role for user {1} in portal {0}
Cause: Unable to grant the role due to an exception.
Action: Examine the exception for further information.

Level: 1

Type: ERROR

Impact: Other

WCS-72804: Failed to revoke the {2} role for user {1} in portal {0}
Cause: Unable to revoke the role due to an exception.
Action: Examine the exception for further information.

Level: 1

Type: ERROR

Impact: Other

WCS-72805: Failed to set permissions for portal {0}
Cause: Unable to set permissions due to an exception.
Action: Examine the exception for further information.

Level: 1

Type: ERROR

Impact: Other

WCS-72806: Failed to drop role {0} for portal {1}
Cause: Unable to drop role due to an exception.
Action: Examine the exception for further information.

Level: 1

Type: ERROR

Impact: Other

WCS-72807: Failed to to set permission actoins for role {0} for portal {1} on member {2}
Cause: Unable to set a member's permission actions for a role due to an exception.
Action: Examine the exception for further information.

Level: 1

Type: WARNING

Impact: Other

WCS-72808: Failed to to create translation bundle for portal {0}
Cause: Unable to create translation bundle due to an exception.
Action: Examine the exception for further information.

Level: 1

Type: WARNING

Impact: Other

WCS-72901: The method {0} is not supported
Cause: A method that is not supported has been called.
Action: Update the application to use another method.

Level: 1

Type: WARNING

Impact: Other

WCS-73000: Muffling exception.
Cause: An error occurred but processing was allowed to continue.
Action: Use the context information to determine if remedial action is required.

Level: 1

Type: WARNING

Impact: Other

WCS-73001: Unable to instantiate upgrade handler {0}.
Cause: Review the underlying exception in the logs to determine the cause.
Action: Make sure that handler implementation is on the classpath.

Level: 1

Type: ERROR

Impact: Other

WCS-73002: Unable to instantiate upgrade manager.
Cause: Review the underlying exception in the logs to determine the cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73003: Upgrade failed for portal {0}.
Cause: Review the underlying exception in the logs to determine the cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73004: Upgrade clean up failed for portal {0}.
Cause: Review the underlying exception in the logs to determine the cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73005: Upgrade initialization failed for handler {0}.
Cause: Review the underlying exception in the logs to determine the cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73006: Upgrade validation failed for {0}:{1} in scope {2}.
Cause: Review the underlying exception in the logs to determine the cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73007: Upgrade validation failed for {0}:{1} in scope {2} due to : {3}.
Cause: Validation failed for the said cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73008: Upgrade phase failed for {0}:{1} in scope {2}.
Cause: Review the underlying exception in the logs to determine the cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73009: Upgrade clean up failed for {0}:{1} in scope {2}.
Cause: Review the underlying exception in the logs to determine the cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73010: Post upgrade failed for {0}:{1} in scope {2}.
Cause: Review the underlying exception in the logs to determine the cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73011: Portal {0} with id {1} not found in the repository.
Cause: Either the portal upgrade has not happened or there is some data corruption.
Action: Check logs for related error. Re-run upgrade. If you still continue to see the issue, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73012: Default portal upgrade failed therefore halting the upgrade.
Cause: Review the related exception in the logs to determine the cause.
Action: Re-run upgrade. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73013: Exception while resolving the reference for {0} , message: {1}.
Cause: Review the related exception in the logs to determine the cause.
Action: Re-run upgrade. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73014: Exception while getting a list of scopes for upgrade, message: {0}.
Cause: Review the related exception in the logs to determine the cause.
Action: Re-run upgrade. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73015: Exception while getting a list of scopes for clean up, message: {0}.
Cause: Review the related exception in the logs to determine the cause.
Action: Re-run upgrade. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73016: Exception while persisting the information related to upgrade scope failure, message: {0}.
Cause: Review the related exception in the logs to determine the cause.
Action: Re-run upgrade. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73017: An error occurred while trying to audit portal server using MDS root {0}.
Cause: Review the related exception in the logs to determine the cause.
Action: Re-run audit. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73018: An error occurred while trying to generate audit report for portal server in report directory {0}.
Cause: Review the related exception in the logs to determine the cause.
Action: Re-run audit. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73019: An error occurred while trying to audit portals {0} using MDS root {1}.
Cause: Review the related exception in the logs to determine the cause.
Action: Re-run audit. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73020: An error occurred while trying to generate audit report for portals {0} in report directory {1}.
Cause: Review the related exception in the logs to determine the cause.
Action: Re-run audit. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73021: An error occurred while trying to initialize mbeans to audit deprecated connection usage.
Cause: Review the related exception in the logs to determine the cause.
Action: Re-run audit. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73022: An error occurred while trying to audit deprecated connection usage.
Cause: Review the related exception in the logs to determine the cause.
Action: Re-run audit. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73023: An error occurred while trying to audit deprecated usage of type {0} in scopes {1}.
Cause: Review the related exception in the logs to determine the cause.
Action: Re-run audit. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73024: Exception while getting a list of scopes for post upgrade, message: {0}.
Cause: Review the related exception in the logs to determine the cause.
Action: Re-run upgrade. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73025: Post upgrade failed for portal {0}.
Cause: Review the underlying exception in the logs to determine the cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73026: Unable to instantiate Upgrade Context for scope {0}.
Cause: Review the underlying exception in the logs to determine the cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73027: An error occurred while upgrade.
Cause: Review the underlying exception in the logs to determine the cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73028: Could not find scope having identifier {0} while auditing {1} with path {2}
Cause: This looks like a case of data corruption where scope does not exist for a resource
Action: Review list of portals in the Portal Server and see if you can find the required portal or any logs pertaining to its failure. Otherwise contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-73029: Unable to update the audit data for the resources of scope {0}.
Cause: An error occurred applying the audit data.
Action: No action may be required if this information is not deemed as important, otherwise if the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-73030: Unable to update the audit data for the resource with id {0} of scope {1}.
Cause: An error occurred applying the audit data.
Action: No action may be required if this information is not deemed as important, otherwise if the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-73031: Failed to delete data file ({0}) associated with the audit data for scope {1}.
Cause: An error occurred deleteing the audit data file.
Action: If the exception details do not provide sufficient information to resolve the issue. However, this failure is unlikely to affect the success of the upgrade.

Level: 1

Type: WARNING

Impact: Other

WCS-73032: One or more scopes failed to have audit data columns updated, e.g. Portal last updated by and updated date information.
Cause: An error occurred during audit column data update.
Action: No action may be required if this information is not deemed as important, otherwise see if the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-73033: The upgrade process was unable to create a directory ({0}) required to persist upgrade data during the upgrade process.
Cause: An error occurred during directory creation.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73034: The upgrade process was unable to read the audit column data file ({0}) for scope {1}.
Cause: An error occurred during an attempt to read the audit column datafile.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73035: The upgrade process was unable to create a file ({0}) required to persist upgrade data during the upgrade process.
Cause: An error occurred during file creation.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73036: Could not find the devices data file in the MDS repository. No devices and device groups will be migrated.
Cause: The instance being upgraded is probably release 11.1.1.7.0 or earlier where the device support feature did not exist.
Action: If the instance being upgraded is release 11.1.1.7.0 or earlier, this is expected and can be safely ignored.

Level: 1

Type: WARNING

Impact: Other

WCS-73037: Upgrade of portal {0} encountered a custom attribute named {1} with the following value exceeding the limit of 2000 characters : {2}
Cause: A large value has been set for a custom attribute which exceeds the size limit for upgraded Portal's custom attributes.
Action: If this attribute is required in the upgraded Portal attempt to use a value of less than 2000 characters, or find another mechanism to handle the requirements which does not utilize the custom attribute mechanism.

Level: 1

Type: WARNING

Impact: Other

WCS-73038: Error while trying to determine whether default scope upgrade succeeded
Cause: Review the underlying exception in the logs to determine the cause.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

WCS-73039: Default Scope cleanup is not attempted due to existing failures in other scopes
Cause: A few scopes have failed during upgrade. Default Scope cleanup is not attempted until all other scopes pass upgrade
Action: Address the existing failures and run the upgrade process again.

Level: 1

Type: WARNING

Impact: Other

WCS-73040: Portal Members not copied to Moderator role for portal {0}
Cause: There may not be any portal members with the moderator role or the member data is corrupted.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-73041: An error occurred while trying to obtain a list of members from the moderator role for portal {0}.
Cause: Review the underlying exception in the logs to determine the cause. This may be a case of data corruption, where there are no moderators for the portal.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-73042: Permissions not copied for Moderator role for portal {0}
Cause: Permissions may not be set for the moderator role or the member data is corrupted.
Action: Contact the administrator.

Level: 1

Type: ERROR

Impact: Other

WCS-73043: An error occurred while trying to obtain permissions for the moderator role for portal {0}.
Cause: Review the underlying exception in the logs to determine the cause. This may be a case of data corruption, where the permissions are not set for the moderator role.
Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-73044: Skipping sub portal security upgrade for portal {0} since security is not inherited for this portal.
Cause: Skipping sub portal security handler upgrade since security is not inherited for this portal.
Action: Check the portal for any data issues.

Level: 1

Type: WARNING

Impact: Other

WCS-73045: Upgrade for scope {0} has not been attempted.
Cause: Upgrade may have been halted abruptly.
Action: Rerun Upgrade again

Level: 1

Type: WARNING

Impact: Other

WCS-89001: An unexpected error occurred in the activity stream sub-system.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-89002: WSRP Connection Name {0} already exists.
Cause: Connection Name used already exists.
Action: Use a different name for the connection.

Level: 1

Type: ERROR

Impact: Other

WCS-89003: Web Service Connection Name {0} already exists. WSRP connection {1} cannot be created.
Cause: Connection Name used already exists.
Action: Use a different name for the connection.

Level: 1

Type: ERROR

Impact: Other

WCS-89004: Cannot register the producer due to connectivity issues.
Cause: Failed to connect to the producer. Either the connection details specified were invalid or there was a network problem.
Action: Verify that the producer connection details are correct, and then check to see if a firewall or some other network issue is blocking the connection.

Level: 1

Type: ERROR

Impact: Other

WCS-89005: Unable to register the producer due to an invalid WSDL URL.
Cause: The WSDL URL specified for the WSRP producer was invalid.
Action: Specify a valid WSDL URL, and then try again.

Level: 1

Type: ERROR

Impact: Other

WCS-89006: URL Connection Name {0} already exists.
Cause: Connection Name used already exists.
Action: Use a different name for the connection.

Level: 1

Type: ERROR

Impact: Other

WCS-89007: Web Producer Name {0} already exists.
Cause: Web Producer Name used already exists.
Action: Use a different name for the Web producer.

Level: 1

Type: ERROR

Impact: Other

WCS-89008: Unable to register the producer due to exception {0}. Contact your administrator.
Cause: Error occurred registering the producer.
Action: Examine the log files for more detail.

Level: 1

Type: ERROR

Impact: Other

WCS-89009: Unable to unregister the producer due to exception {0}. Contact your administrator.
Cause: Error occurred deregistering the producer.
Action: Examine the log files for more detail.

Level: 1

Type: ERROR

Impact: Other

WCS-89010: Unable to get producer connections due to exception {0}. Contact your administrator.
Cause: Error occurred retrieving the list of producers.
Action: Examine the log files for more detail.

Level: 1

Type: ERROR

Impact: Other

WCS-89011: Unable to register the WSRP producer due to exception {0}. Contact your administrator.
Cause: Error occurred registering the WSRP producer.
Action: Examine the log files for more detail.

Level: 1

Type: ERROR

Impact: Other

WCS-89012: Unable to register the JPDK producer due to exception {0}. Contact your administrator.
Cause: Encountered an exception when registering the JPDK producer.
Action: Examine the log files for more detail.

Level: 1

Type: ERROR

Impact: Other

WCS-89013: Unable to create the WSRP producer connection due to exception {0}. Contact your administrator.
Cause: Error occurred creating the WSRP producer connection.
Action: Examine the log files for more detail.

Level: 1

Type: ERROR

Impact: Other

WCS-89014: Unable to refresh the producer connections due to exception {0}
Cause: Error occurred refreshing the list of producers.
Action: Examine the log files for more detail.

Level: 1

Type: ERROR

Impact: Other

WCS-89015: Failed to clean up producer registration due to exception {0}. Contact your administrator.
Cause: Error occurred cleaning up the producer registration.
Action: Examine the log files for more detail.

Level: 1

Type: ERROR

Impact: Other

WCS-89016: The operation failed due to an exception. Contact your administrator.
Cause: Error occurred performing the operation.
Action: Examine the log files for more detail.

Level: 1

Type: ERROR

Impact: Other

WCS-89017: Error parsing policy XML ({0}) from PolicyApplication mbean with message {1}
Cause: Error parsing policy XML from PolicyApplication mbean.
Action: Make sure the policy XML in the PolicyApplication mbean is set correctly.

Level: 1

Type: ERROR

Impact: Other

WCS-89501: An unexpected error occurred in the activity stream sub-system.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-89502: External Application Connection Name {0} already exists.
Cause: Connection Name used already exists.
Action: Use a different name for Connection.

Level: 1

Type: ERROR

Impact: Other

WCS-89503: No connection selected for this operation.
Cause: No External Application connection selected for this operation.
Action: Select a External Application connection from the table listing the available connections.

Level: 1

Type: ERROR

Impact: Other

WCS-90100: No moveplan.xml file available.
Cause: moveplan.xml file missing.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WCS-90200: Error in validating the source environment.
Cause: Invalid source environment.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other