PRT-00001: Unable to get portlet response (Internal Error) for portlet binding {0}
Cause: An internal error occurred in the portlet run-time code.
Action: Check the portlet client logs to locate the cause of the problem.
PRT-00002: 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.
PRT-00003: 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.
PRT-00251: 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}.
PRT-00252: 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.
PRT-00253: 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.
PRT-00254: 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.
PRT-00255: Unable to get portlet response for portlet instance ID {0} for portlet binding {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 the portlet client logs for the cause and action of this error.
PRT-00256: 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.
PRT-00257: 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.
PRT-00258: 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.
PRT-00259: 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}.
PRT-00260: 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.
PRT-00261: 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.
PRT-00262: 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 defs. Also ensure that ADFPhaseListener (or its subclasses) are registered in the lifecycle phase listener in your application faces-config.xml
PRT-00263: 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.
PRT-00264: 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.
PRT-00265: Unable to get portlet response (time-out) for portlet binding {0}
Cause: Timeout occurred while performing a task at the producer side
Action: This can happen if some tasks at the producer are taking longer than the timeout specified for the registered producer. Edit the registeration details for this Producer and increase the timeout entry.
PRT-00501: 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.
PRT-00502: 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.
PRT-00503: 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.
PRT-00504: 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.
PRT-00751: Available modes from the portlet {0} are null
Cause: There were errors in getting a portlet response and therefore, the modes extraction from the portlet markup failed.
Action: This error can be resolved if the request is able to get the correct portlet response. Check for other errors or exceptions reported before this error and take appropriate action. Also, check if any exceptions are reported at the producer level.
PRT-01001: Configuration error: property {0}
Cause: The named configuration property has an invalid value.
Action: Correct the value of the property.
PRT-01002: 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.
PRT-01003: Configuration error: property {0} invalid value {1}
Cause: The named configuration property has an invalid value.
Action: Correct the value of the property.
PRT-01004: 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.
PRT-01009: {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.
PRT-01010: Parameter {0} specifies an unrecognised cache level: {1}
Cause: Invalid cache level used for a cache configuration parameter.
Action: Correct the parameter such that it uses a cache level of either 'system' or 'user'.
Cause: A configuration parameter starting with 'cache.' has an invalid name.
Action: Correct the parameter name.
PRT-01014: 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.
PRT-01015: Object {0} is too big to cache in region {1}
Cause: Portlet content could not be cached because it is too large.
Action: Reconfigure the cache such that enough space is available for the content.
PRT-01016: 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.
PRT-01017: 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.
PRT-01018: 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.
PRT-01021: 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.
PRT-01022: 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.
PRT-01024: Timing out task: {0}
Cause: A task took too long to complete.
Action: If the problem persists, increase the timeout period for the task.
PRT-01025: Muffling throwable in method {0}, context={1}
Cause: An unexpected error occurred in the named method.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01026: Invalid portlet request handle {0}
Cause: A portlet resource request handle was invalid or did not correspond to a proxied resource.
Action: Consult the portlet client log file for more information.
PRT-01027: 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.
PRT-01029: Error accessing adf-config.xml
Cause: The portlet client was unable to access the adf-config.xml file.
Action: Examine the associated stack trace to resolve the issue or contact Oracle Support Services.
PRT-01030: Cannot export portlet {0} because it is a producer-offered portlet
Cause: An attempt was made to export a producer-offered portlet.
Action: Remove the offered portlet from the export set.
PRT-01031: 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 log file to determine that it is functioning correctly.
PRT-01032: 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 and retry the export.
PRT-01033: Producer {0} does not support the WSRP IMPORTPORTLETS operation. Unable to proceed with import using the 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.
PRT-01034: 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.
PRT-01035: Unexpected portlet with ID {0} in an import portlet response
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.
PRT-01040: Error calling producer to destroy portlet handle {0} overwritten during import
Cause: A call to the producer to destroy a portlet failed.
Action: Destroy the portlet manually if possible.
PRT-01041: 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.
PRT-01042: 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 and retry the import.
PRT-01046: Filter unable to modify markup
Cause: An exception caused filtering of portlet markup to fail.
Action: Examine the associated exception to resolve the issue.
PRT-01047: 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.
PRT-01050: 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.
PRT-01052: 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.
PRT-01053: 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.
PRT-01055: 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.
Cause: An exception was thrown during an import operation.
Action: Examine the causing exception and resolve the issue that caused the failure.
PRT-01062: No object with ID {0}
Cause: An ID does not correspond to an object.
Action: Verify that the ID is correct.
PRT-01063: 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.
PRT-01064: Parse error : unknown element {0}
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01065: Parse error : unknown attribute {0}
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01066: 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.
PRT-01067: Future.get() returned null [activity {0}]
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01068: Future.get() returned type {0} expected {1}
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01069: Could not import portlet with ID {0}
Cause: A suitable offered portlet could not be found.
Action: Check if the producer that owns the imported portlet is properly registered.
PRT-01070: Portlet lists differ between locale {0} and {1}.
Cause: The remote producer returned unexpected portlets for a particular locale.
Action: Ensure that the remote producer is functioning correctly.
PRT-01071: 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.
PRT-01072: Mode {0} not allowed on producer-offered portlets
Cause: An attempt was made to change to an invalid mode for a producer-offered portlet.
Action: Use this mode for non-offered portlets only.
PRT-01073: Invalid portlet rendition generated
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01074: Could not import producer with ID {0} because that ID is already used by an object of a different type {1}.
Cause: An ID specified for an imported producer already exists.
Action: If possible, use a different ID for the imported producer.
PRT-01075: Could not import portlet with ID {0} because that ID is already used by an object of a different type {1}.
Cause: An ID given for an imported portlet is in use by an object that is not a portlet.
Action: If possible, use a different ID for the imported portlet.
PRT-01076: 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: An 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.
PRT-01077: 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: An 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.
PRT-01080: Unexpected input passed of type {0}
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01081: Unexpected output passed in of type {0}
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01082: Could not create a runnable for portlet {0}
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01083: Error copying portlet {0}
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01084: Error returned from prepareRendition(): {0}
Cause: An error occurred while preparing portlet markup.
Action: Use the reported error message to resolve the issue.
PRT-01085: 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.
PRT-01086: Unable to obtain interaction for producer {0}
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01087: WSRP registration returned null producer
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01088: {0}Pipe caught exception: {1}: {2}
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01089: WSRP producer returned markup but did not specify a MIME type
Cause: The producer behaved in an inappropriate manner.
Action: Contact the producer's administrator.
PRT-01090: WSRP producer returned both {0} and {1}. The {2} field will be ignored.
Cause: The producer behaved in an inappropriate manner by returning values for mutally exclusive fields.
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.
PRT-01092: 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.
PRT-01093: An I/O error occurred while contacting a producer.
Cause: The portlet client was unable to sucessfully communicate with the producer.
Action: Examine the stack trace associated with this message to determine the root cause.
PRT-01094: 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.
PRT-01095: Unable to locate connection: {0}
Cause: A connection used for a producer cannot be found.
Action: Ensure that the connection exists.
PRT-01096: Unable to locate URL connection: {0}
Cause: A URL connection used by a producer connection cannot be found.
Action: Ensure that the URL connection exists.
PRT-01097: 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.
PRT-01098: Unsupported WSRP service version: {0}
Cause: An attempt was made to use a WSRP service of an unsupported version
Action: Use a version of the WSRP service that is supported or upgrade the portlet client.
PRT-01099: No WSRP ports found in WSDL at {0}.
Cause: An attempt was made to use a WSDL document that does not define any WSRP ports
Action: Verify that the URL for the WSRP WSDL document is correct and that the document is valid.
PRT-01100: 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.
PRT-01101: Cannot open web producer connection
Cause: An error occurred whilst opening a web producer connection.
Action: Verify that the connection URL and any proxy server settings are correct.
PRT-01102: 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.
PRT-01103: 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 system 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 system 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.
PRT-01104: 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 system 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.
PRT-01105: Remote error
Cause: There was an error on the remote producer server.
Action: Check the remote producer server logs for further details.
PRT-01106: Client queue full
Cause: The client portlet request queue was full and therefore, this request was rejected.
Action: Resubmit the request, or if this persists, consider increasing the configured queue size.
PRT-01107: Client request time out
Cause: The client portlet request took too long to complete and was therefore 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: Resumbit the request, or if this persists, consider increasing the configured timeout periods.
PRT-01108: Client producer connection not found
Cause: The client producer connection was not found in connections.xml.
Action: Create the producer connection.
PRT-01109: Client metadata error
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01110: Error
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01111: 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.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01898: SAX Exception : Unable to parse the MDS configuration file
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01899: Invalid XML : Unable to parse the MDS configuration file
Cause: The configuration file does not contain the correct format
Action: Validate the XML
PRT-01900: Unable to find deployed MDS repository in the application
Cause: The specified MDS location input is incorrect
Action: Rerun tool and specify correct MDS location
PRT-01901: Error validating deployment profile
Cause: The values supplied in the profile are not valid
Action: Check the MDS repository path is writeable and all producer proxy ports have a valid TCP/IP port number
PRT-01902: Unexpected PortletException
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01903: XML Mapping File is not in a recognised format.
Cause: The format of the Mapping file is incorrect
Action: Let the tool re-create the file if you have manually modified it
PRT-01904: IOException Exception
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01905: There is no deployment profile with the specified name in the XML configuration file.
Cause: Unable to find profile name specified
Action: Check that the profile name specified is in the configuration file
PRT-01906: Multiple deployment profiles in XML configuration file, specify which one should be used.
Cause: No profile was specified and there are multiple available
Action: Specify profile to be used
PRT-01907: SAX Parser exception
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01908: Unable to interpret the XML configuration file containing the deployment profile
Cause: There is an issue with the format of the profile file
Action: This is an internal error. Contact Oracle Support Services.
PRT-01909: Unable to interpret the adf-config.xml or connections.xml file in the source EAR
Cause: There is an issue with the format of the configuration file
Action: This is an internal error. Contact Oracle Support Services.
PRT-01910: File Not Found - Either the Source EAR, the Target Path or the XML configuration file cannot be found.
Cause: Specified EAR or the target path are incorrect or the XML file location is incorrect
Action: Check the paths specified are valid
PRT-01911: Failed to move EAR to target location, the target EAR can be found in {0}.
Cause: Unable to move file to target location
Action: Check space and permissions on target location
PRT-01912: IOException when creating archive file
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01913: File Not Found when creating archive file
Cause: One of the files to be zipped up into the archive does not exist
Action: Retry the action using another temporary directory
PRT-01914: Unexpected Exception whilst creating the Export Set
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01915: Portlet Exception while creating the Export Set (Producer may be inaccessible)
Cause: Exporting of MDS data failed
Action: Verify that the Producers are contactable
PRT-01916: Failed to create JNDI context in ConnectionsParser().
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01917: connections.xml IOException raised
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01918: connections.xml file not found
Cause: The file is missing from the EAR
Action: Check the EAR for the file
PRT-01919: Failed to save tmp connections.xml
Cause: Unable to create the connections file
Action: Check there is enough space and correct permission in the temp directory of your system.
PRT-01920: Unexpected exception
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01921: JNDI Naming Exception
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01922: Failed to lookup connection to be replaced. Name is {0}.
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01923: Unexpected exception during connection enumeration
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01924: Unable to create temporary work area
Cause: There is an issue with creating the temporary directory
Action: Check there is enough space and correct permission in the temp directory of your system.
PRT-01925: JNDI lookup problem for connection {0}
Cause: Looking up an object using the Java Naming and Directory Interface failed
Action: This is an internal error. Contact Oracle Support Services.
PRT-01926: Unable to contact WSRP Producer
Cause: The WSRP Producer URL is unaccessible
Action: Verify that the Producer can be accessed using a Browser
PRT-01927: Unable to contact Web Producer
Cause: The Web Producer URL is unaccessible
Action: Verify that the Producer can be accessed using a Browser
PRT-01979: ERROR
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01980: ERROR : {0}
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01981: ERROR: Illegal argument specified {0}
Cause: Wrong format of argument specified
Action: Check the usage of the tool and correct the format
PRT-01989: ERROR: Internal unknown error
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01990: Exception {0}
Cause: An internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
PRT-01992: File copy failed from {0} to {1}
Cause: Unable to copy the source files to the target
Action: Check that there is enough space and you have write permissions
PRT-01993: Move by rename failed, doing a copy and delete instead.
Cause: File already exists, so deleting it first and then creating new version
Action: No Action required. For information only.
PRT-01994: Unable to move directory, recursively moving children instead
Cause: The directory and sub-directories need to be created before we can move the required directory
Action: No Action required. For information only.
PRT-01996: Could not move {0} as {1} exists
Cause: File or directory already exists in target location
Action: Remove target location
PRT-02000: Failed to create : {0}
Cause: The parent directory path does not exist or user has insufficient permissions
Action: Verify that the path exists and has write permissions
PRT-03101: An unexpected error occurred: {0}
Cause: An unexpected error occurred.
Action: Report the error to Oracle Support Services.
PRT-03102: Could not configure adf-config at design time for application {0}
Cause: An unexpected error occurred while trying to configure adf-config at design time.
Action: Report the error to Oracle Support Services.
PRT-03151: Could not initialize the External Applications folder in the Applications Navigator for application {0}
Cause: An unexpected error occurred while initializing the External Applications folder in the Applications Navigator.
Action: Report the error to Oracle Support Services.
PRT-03152: Could not create the External Applications folder for application {0}
Cause: An unexpected error occurred while trying to create the External Applications folder.
Action: Report the error to Oracle Support Services.
PRT-03153: Could not register the external application listener in application {0}
Cause: An unexpected error occurred while trying to register the external application listener.
Action: Report the error to Oracle Support Services.
PRT-03154: Could not initialize the External Applications folder in application {0}
Cause: An unexpected error occurred while trying to add external application nodes to the folder.
Action: Report the error to Oracle Support Services.
PRT-03155: Could not add the External Application {0} node to the Applications Navigator in application {1}
Cause: An unexpected error occurred while trying to add the external application.
Action: Report the error to Oracle Support Services.
PRT-03156: Could not edit the External Application {0} node in application {1}
Cause: An unexpected error occurred while trying to edit the external application.
Action: Report the error to Oracle Support Services.
PRT-03157: Could not delete the External Application {0} node in application {1}
Cause: An unexpected error occurred while trying to delete the external application.
Action: Report the error to Oracle Support Services.
PRT-03201: Could not register External Application {0} in application {1}
Cause: An unexpected error occurred while trying to register the external application.
Action: Report the error to Oracle Support Services.
PRT-03202: Could not edit External Application {0} in application {1}
Cause: An unexpected error occurred while trying to edit the external application.
Action: Report the error to Oracle Support Services.
PRT-03251: Could not get the credential page path configured by the user for project {0}, using the default path instead
Cause: An unexpected error occurred while trying to obtain the credential page path configured by the user.
Action: Report the error to Oracle Support Services if the error persists.
PRT-03252: Could not add the Credential Provisioning page into project {0}
Cause: An unexpected error occurred while trying to add the Credential Provisioning page to the project.
Action: Report the error to Oracle Support Services.
PRT-03253: Could not ensure that the managedBean {0} entry is valid for project {1}
Cause: An unexpected error occurred while trying to ensure that the external application managed bean entry was valid.
Action: Add a new valid managed bean entry. Remove the old entry, that is, the one that occurs first.
PRT-03254: Could not ensure that the navigation rule {0} entry is valid for project {1}
Cause: An unexpected error occurred while trying to ensure that the external application navigation rule entry was valid.
Action: Add a new valid navigation rule entry. Remove the old entry, that is, the one that occurs first.
PRT-03301: Invalid MDS Config for application {0}
Cause: An invalid MDS configuration entry exists in adf-config.xml for the application.
Action: Report the error to Oracle Support Services.
PRT-03302: Could not check if adf-config.xml exists for application {0}
Cause: An unexpected error occurred while trying to check if adf-config.xml exists for the application.
Action: Report the error to Oracle Support Services.
PRT-03303: Could not check if the application {0} is of WebCenter type
Cause: An unexpected error occurred while trying to check if application was of type WebCenter.
Action: Report the error to Oracle Support Services.
PRT-03601: Unexpected error occurred
Cause: An unexpected error has occurred.
Action: Report the problem to Oracle Support Services.
PRT-03602: The system has incorrectly invoked a method {0}
Cause: The system attempted to call a method but has not passed a suitable set of paramaters to that method.
Action: Report the error to Oracle Support Services.
PRT-03604: Could not initialize External Application Manager for application {0}
Cause: An unexpected error occurred during MDS instance setup for the application.
Action: Report the error to Oracle Support Services.
PRT-03605: Invalid login url {0} was obtained for external application {1}.
Cause: There has been a data corruption in the external application definition.
Action: Report the error to Oracle Support Services.
PRT-03606: Could not obtain External Application Manager for application {0}
Cause: The External Application Manager has not been initialized for this application yet. This should have been done earlier.
Action: Report the errot to Oracle Support Services.
PRT-03606: Error occurred while adding listener {0}.
Cause: An unexpected error occurred while trying to register the listener.
Action: Report the error to Oracle Support Services.
PRT-03607: Error occurred while removing listener {0}.
Cause: An unexpected error occurred while trying to deregister listener.
Action: Report the error to Oracle Support Services.
PRT-03651: External application MDS Store could not be configured for application {0}.
Cause: An unexpected error occurred while trying to set up MDS Store for the application.
Action: Report the error to Oracle Support Services.
PRT-03653: The external application with ID {0} cannot be found.
Cause: The ID passed for obtaining the external application is invalid.
Action: Pass a valid external application ID for retrieving the application.
PRT-03654: The system has attempted an action which should have succeeded but, did not.
Cause: The primary cause is that the system performed an action in a context that was not anticipated . Another reason could be that there were more serious problems in the system, such as hardware faults.
Action: Review the system for other errors and report this error to Oracle Support Services.
PRT-03655: The external application record with ID {0} already exists and cannot be created again.
Cause: An attempt was made to create an external application record with an ID that already exists. Such an operation is not supported and should not be attempted.
Action: Report the error to Oracle Support Services.
PRT-03656: The application record identified by {0} could not be found.
Cause: An attempt was made to load the external application record with ID {0}, but the external application was not found.
Action: Report the error to Oracle Support Services.
PRT-03657: The application record identified by {0} could not be found.
Cause: An attempt was made to delete the external application record with ID {0}, but the external application was not found. There is a possibility that a separate thread or process had removed the external application.
Action: Report the error to Oracle Support Services.
PRT-03658: The ID ({0}) used to read, write, or delete the persistent object for this application is invalid.
Cause: The ID ({0}) used to read, write, or delete the persistent object for this application was invalid. Such an invalid ID should not have been used.
Action: Report the error to Oracle Support Services.
PRT-03659: Generation of a suitable external-application ID has failed.
Cause: The system was attempting to generate an ID with which it could save an external-application object. The id derived by the system {0} was invalid.
Action: Report the error to Oracle Support Services.
PRT-03660: A resource seems to have disappeared between being reported as an element in a result set and being accessed while iterating over that result set.
Cause: The system performed a search and the results included the resource with reference {0}. However, that resource could not be fetched. This may not be a problem because the resource may have been there when the search was performed but, was removed by another process or thread before the resuorce details were fetched.
Action: Unless the system is showing other peculiar behaviour, this operation can be ignored.
PRT-03661: The key to an object identified in a query is reported to be invalid.
Cause: The system performed a search but, one of the search result references had problems when passed back to the persistence API to actually fetch that resource. This is an internal inconsistency that should not have occurred.
Action: Report the error to Oracle Support Services.
PRT-03662: Cannot update application record with ID {0}
Cause: The persistent object representing an external application could not be found for update. It is possible that it was deleted by a separate but concurrent persistence session.
Action: Review the messages from the application. If this is not a one-off event, contact Oracle Support Services.
PRT-03663: Error occurred while registering new external application {0}!
Cause: An unexpected error occurred while trying to register the external application.
Action: Report the error to Oracle Support Services.
PRT-03664: Error occurred while modifying external application {0}!
Cause: An unexpected error occurred while trying to modify the external application.
Action: Report the error to Oracle Support Services.
PRT-03665: Error occurred while deleting external application {0}!
Cause: An unexpected error occurred while trying to delete the external application.
Action: Report the error to Oracle Support Services.
PRT-03666: Error ocurred while flushing MDS changes!
Cause: An unexpected error occurred while flushing MDS changes for the external application.
Action: Report the error to Oracle Support Services.
PRT-03667: Invalid MDS Configuration for application {0}
Cause: The required MDS configuration for configuring external applications does not exist in adf-config.xml. Some one may have tampered with the configuration data, or tried to manually configure MDS prior to registering the external application or producer.
Action: Report the error to Oracle Support Services.
PRT-03668: MDS has not been configured for application {0}.
Cause: MDS gets configured for the application only if an external application or a producer has been registered with the application. In this case, external application operations have been invoked before the MDS was configured.
Action: Ignore this error. However, if it is causing a functionality loss, report the error to Oracle Support Services.
PRT-03701: Invalid external application ID {0} was found while rendering the Credential Provisioning page.
Cause: An invalid external application ID was found in the process scope.
Action: Close the current session and try running the page again. If the problem persists, report the error to Oracle Support Services.
PRT-03702: No back URL exists in the process scope
Cause: The credential page could not establish the back URL to go to in case of ok and cancel events. This could be because the user ran the page standalone or there was some unexpected error while setting back URL in the process scope.
Action: If this error occurred when the credential page was invoked from a portlet, then report the error to Oracle Support Services. However, in case the credential page was run standalone, this is not supported.
PRT-03703: An unexpected IO error occurred while trying to retrieve the back URL to redirect the credential page.
Cause: An unexpected error occurred while trying to obtain the back URL to redirect the credential page.
Action: Try manually going back to the page you came from. Alternatively if the error persists, report the error to Oracle Support Services.
PRT-03704: External application ID was found to be null while rendering the Credential Provisioning page!
Cause: The credential page was probably run standalone or invoked from a portlet added from a producer that must be but has not been associated with an external application.
Action: The credential page must be invoked from the link in portlets added from producers associated with the external application. Running the credential page standalone is not supported.
PRT-03705: You need to be authenticated to be able to view this page!
Cause: A null user subject was obtainined while rendering the credential provisioning page.
Action: Ensure that the credential provisioning page is invoked after the user credentials are established.
PRT-03706: An unexpected error occurred while trying to initialize the Credential Provisioning page.
Cause: An unexpected error occurred while trying to intialize the Credential Provisioning page.
Action: Report the error to Oracle Support Services.
PRT-03707: Could not store external application {0} credentials for user {1}
Cause: There was an unexpected error while trying to store external application credentials for the user.
Action: Close the current session and repeat the steps. If the problem persists, report the error to Oracle Support Services.
PRT-03708: Credentials were not found for the user {0} for the external application with ID {1}.
Cause: External application credentials were not found for the user.
Action: Provide a link to the Credential Provisioning page to enable users to supply their credentials.
PRT-06503: The call to method {0} is not supported at design time.
Cause: This operation is not supported at design time.
Action: Report the error to Oracle Support Services.
