26 MFT-02001 to MFT-08500

MFT-02001: Not able to load the MDS repository.

Cause: MDS repository initialization failed.

Action: Check the metadata repository configuration and make sure that they are valid.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02002: No transfer found for the source(ID {0}).

Cause: No transfer found for the source.

Action: Ensure that the source is attached to a transfer.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02003: No purge schedule found with name [{0}].

Cause: No purge schedule found with provided name.

Action: Ensure that the purge oschedule has been created.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02004: [{0}] with label [{1}] is not found in MDS.

Cause: Artifact does not exist in MDS.

Action: Please check artifact name.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02006: Data not found in MDS repository.

Cause: Data not found in MDS repository.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error. Make sure the meta data exists.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02007: Error while creating new label with value {0} in MDS repository.

Cause: An error while creating new MDS label. Check if the label already exists.

Action: Check the metadata repository configuration and make sure that they are valid. Check if the label already exists in the system.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02008: Not able to resolve the MDS reference for source with ID {0}.

Cause: Reference meta data not exists in repository.

Action: Restore the deleted data in the MDS repository.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02009: Not able to resolve the MDS reference for transfer with ID {0}.

Cause: Reference metadata does not exist in the repository.

Action: Restore the deleted data in the MDS repository.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02010: Not able to resolve the MDS reference for target with ID {0}.

Cause: Referenced metadata does not exist in the repository.

Action: Restore the deleted data in the MDS repository.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02011: Label {0} does not exist in the MDS repository.

Cause: Label no longer exists in the MDS repository.

Action: Problem not recoverable. Contact Oracle Support Services.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02101: Validation failed for the artifact [{0}].

Cause: Validation failed for the given artifact.

Action: Check the artifact configuration and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02102: Not able to retrieve {0} from the credential store for {1}.

Cause: Not able to retrieve the password from the credential store.

Action: Check the settings and data in the credential store or recreate the password. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02104: No target associated with the transfer.

Cause: No target is associated with the transfer.

Action: Associate at least one target with the transfer and redeploy.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02105: No source associated with the transfer.

Cause: No source is associated with the transfer.

Action: Associate a source with the transfer and redeploy.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02301: Error occurred while exporting the metadata.

Cause: Error during metadata export.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02302: Error generating the config plan XML.

Cause: Error generating the config plan XML.

Action: Review the diagnostic log for the exact error. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02351: Error occurred while importing the metadata.

Cause: Invalid import metadata.

Action: Make sure that import zip file is proper. Also, review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02401: The source [{0}] is currently associated with some transfers and so cannot be deleted.

Cause: The given source is currently referenced in some transfers and so cannot be deleted at this point.

Action: For each associated transfer that is associated with given source, detach the source, associate a new source, or delete the transfer. Then try deleting the source again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02402: The target [{0}] is currently associated with some transfers and so cannot be deleted.

Cause: The given target is currently referenced in some transfers and so cannot be deleted at this point.

Action: For each associated transfer that is associated with given target, detach the target, associate a new target, or delete the transfer. Then try deleting the target again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02403: Error occurred while resetting the metadata with preserved user changes {0}.

Cause: Exception while resetting the metadata.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02404: Error occurred while deleting the source [{0}] from metadata store.

Cause: Exception while deleting the given source from metadata store.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02405: Cannot delete the domain-info(name {0}) because it is referenced in some B2B source/target types.

Cause: Cannot delete the domain-info because it is referenced in some B2B source/target types.

Action: Detach the domain-info from the referring B2B sources or targets. Then try deleting the domain-info again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02406: Cannot delete the domain-info(name {0}) because it is referenced in some Healthcare source/target types.

Cause: Cannot delete the domain-info because it is referenced in some Healthcare source/target types.

Action: Detach the domain-info from the referring Healthcare sources or targets. Then try deleting the domain-info again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02407: Cannot delete the callout(name {0}) because it is referenced in some transfer preprocessing.

Cause: Cannot delete the callout because it is referenced in some transfer preprocessing.

Action: Detach the callout from the referring transfer preprocessing. Then try deleting the callout again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02408: Cannot delete the callout(name {0}) because it is referenced in some transfer postprocessing.

Cause: Cannot delete the callout because it is referenced in some transfer postprocessing.

Action: Detach the callout from the referring transfer postprocessing. Then try deleting the callout again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02409: Cannot delete the domain-info(name {0}) because it is referenced in some Web Service source/target types.

Cause: Cannot delete the domain-info because it is referenced in some Web Service source/target types.

Action: Detach the domain-info from the referring Web Service sources or targets. Then try deleting the domain-info again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02410: Error occurred while deleting the transfer [{0}] from metadata store.

Cause: Exception while deleting the given transfer from metadata store.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02411: Error occurred while deleting the target [{0}] from metadata store.

Cause: Exception while deleting the given target from metadata store.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02501: Error occurred while deploying the source artifact with id [{0}].

Cause: Error occurred while deploying the given source artifact.

Action: The configuration of the given source artifact may be incorrect or error occurred while deploying the artifact. Check the source configuration and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02502: Error occurred while enabling the source artifact with id [{0}].

Cause: Error occurred while enabling the given source artifact.

Action: The configuration of the given source artifact may be incorrect or error occurred while enabling the artifact. Check the source configuration and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02503: Error occurred while disabling the source artifact with id [{0}].

Cause: Error occurred while disabling the given source artifact.

Action: The configuration of the given source artifact may be incorrect or error occurred while disabling the artifact. Check the source configuration and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02504: Error occurred while undeploying the source artifact with id [{0}].

Cause: Error occurred while undeploying the given source artifact.

Action: The configuration of the given source artifact may be incorrect or error occurred while undeploying the artifact. Check the source configuration and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02505: Could not delete Deployment record for the currently deployed {0} [{1}] with label [{2}].

Cause: Artifact corresponding to given name and label is currently an Active deployment.

Action: Undeploy the artifact from the MFT console monitoring page and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02506: Deployment record does not exist for {0} [{1}] with label [{2}].

Cause: Artifact corresponding to given name and label is not found.

Action: Review the deployment history from the MFT console deployment page for the given artifact and check if artifact with the given label exists.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02507: Artifact {0} of type {1} is referenced in Transfer {2}.

Cause: Artifact corresponding to the given name is referenced in a transfer and cannot be deleted.

Action: Review deployment history for the given artifact and make sure it is not referenced in Transfer Deployments.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02508: Error deploying source {0}. Another source {1} was found deployed for URL {2}.

Cause: Another source that is already deployed is configured with the same URL.

Action: Configure the source with a different URL and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02509: Error deploying source {0}. Another source {1} was found deployed for folder {2}.

Cause: Another source that already deployed is configured with the same folder.

Action: Configure the source with a different folder and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02510: Error deploying SFTP source {0}. The configured private key is incorrect.

Cause: Error occurred while deploying the sFTP source. The configured private key is incorrect.

Action: Check if the key is imported to the key store. If not, import it and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02511: Error deploying SFTP target {0}. The configured private key is incorrect.

Cause: Error occurred while deploying the sFTP target. The configured private key is incorrect.

Action: Check if the key is imported to the key store. If not, import it and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02512: Error deploying source {0}. The configured PGP encryption alias is incorrect.

Cause: Error occurred while deploying the source. The configured PGP encryption alias is not valid.

Action: Check if the encryption key is imported to the key store. If not, import it and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02513: Error deploying source {0}. The configured PGP decryption alias is incorrect.

Cause: Error occurred while deploying the source. The configured PGP decryption alias is not valid.

Action: Check if the decryption key is imported to the key store. If not, import it and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02514: Error deploying transfer {0}. The configured PGP encryption alias for target {1} is incorrect.

Cause: Error occurred while deploying the target. The configured PGP encryption alias is not valid.

Action: Check if the encryption key is imported to the key store. If not, import it and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02515: Error deploying transfer {0}. The configured PGP decryption alias for target {1} is incorrect.

Cause: Error occurred while deploying the target. The configured PGP decryption alias is not valid.

Action: Check if the decryption key is imported to the key store. If not, import it and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02516: Error deploying transfer {0}. No Internal server address configured in server properties.

Cause: Error occurred while deploying the Web Service target. The internal server address is not configured.

Action: Go to the Server Properties page and check the internal server information under Advanced Delivery Properties. Enter correct values and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02517: Error deploying transfer {0}. No External server address configured in server properties.

Cause: Error occurred while deploying the Web Service target. The external server address is not configured.

Action: Go to the Server Properties page and check the external server information under Advanced Delivery Properties. Enter correct values and try deployment again

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02518: Error deploying transfer {0}. No internal FTP port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The Internal Server FTP port is not configured in server properties.

Action: Go to the Server Properties page and check the internal server information under Advanced Delivery Properties. Enter correct values and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02519: Error deploying transfer {0}. No external FTP port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The External FTP port is not configured in server properties.

Action: Go to the Server Properties page and check the external server information under Advanced Delivery Properties. Enter correct values and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02520: Error deploying transfer {0}. No internal FTPS port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The Internal Server FTPS port is not configured in server properties.

Action: Go to the Server Properties page and check the internal server information under Advanced Delivery Properties. Enter correct values and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02521: Error deploying transfer {0}. No external FTPS port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The External FTPS port is not configured in server properties.

Action: Go to the Server Properties page and check the external server information under Advanced Delivery Properties. Enter correct values and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02522: Error deploying transfer {0}. No internal sFTP port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The Internal Server sFTP port is not configured in server properties.

Action: Go to the Server Properties page and check the internal server information under Advanced Delivery Properties. Enter correct values and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02523: Error deploying transfer {0}. No external sFTP port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The External sFTP port is not configured in server properties.

Action: Go to the Server Properties page and check the external server information under Advanced Delivery Properties. Enter correct values and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02524: Deployment validation failed while deploying source {0}.

Cause: Deployment validation failed while deploying the source.

Action: Check the source configuration and try again. Deploy from the UI again to check what validations failed or deploy the source using WLST in interactive mode.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02525: Deployment validation failed while deploying transfer {1}.

Cause: Deployment validation failed while deploying the transfer.

Action: Check the transfer configuration and try again. Deploy from the UI again to check what validations failed or deploy the transfer using WLST in interactive mode.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02526: Deployment validation failed while deploying target {1}.

Cause: Deployment validation failed while deploying the target.

Action: Check the target configuration and try again. Deploy from the UI again to check what validations failed or deploy the target using WLST in interactive mode.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02527: Deployment of source {0} failed. The password configured is incorrect.

Cause: Deployment of source failed due to invalid password.

Action: Check the key store configuration and ensure the password configured for the source is available in the key store.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02528: Deployment of target {0} failed. The password configured is incorrect.

Cause: Deployment of target failed due to invalid password.

Action: Check the key store configuration and ensure the password configured for the target is available in the key store.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02529: Error deploying source {0}. Transport Endpoint validation failed.

Cause: Error occurred while deploying the source. Transport validation failed due to incorrect configuration of the source endpoint.

Action: Check the source configuration and try again. Deploy from the UI again to check what validations failed or deploy the source using WLST in interactive mode.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02530: Error deploying Target {0}. Transport endpoint validation failed.

Cause: Error occurred while deploying the target. Transport validation failed due to incorrect configuration of the target endpoint.

Action: Check the target configuration and try again. Deploy from the UI again to check what validations failed or deploy the target using WLST in interactive mode.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02531: Invalid configuration found in the associated source {0}.

Cause: Error occurred while deploying the transfer because source configuration is invalid.

Action: Go to the source page, fix the invalid configuration, and try redeploying the transfer.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02532: Invalid configuration found in the associated target {0}.

Cause: Error occurred while deploying the transfer because the target configuration is invalid.

Action: Go to the target page, fix the invalid configuration, and try redeploying the transfer.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02533: Error. Could not find a deployment record for source [{0}].

Cause: A deployment record for the given source artifact could not be found in database.

Action: Deploy the source and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02534: Error. Could not find a deployment record for target [{0}].

Cause: A deployment record for the given target artifact could not be found in database.

Action: Deploy the target and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02535: Error. Could not find a deployment record for transfer [{0}].

Cause: A deployment record for the given transfer artifact could not be found in database.

Action: Deploy the transfer and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02536: The transfer [{0}] is already enabled.

Cause: The deployment record for the given transfer artifact is already enabled.

Action: No action required.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02537: The source [{0}] is already enabled.

Cause: The deployment record for the given source artifact is already enabled.

Action: No action required.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02538: The target [{0}] is already enabled.

Cause: The deployment record for the given target artifact is already enabled.

Action: No action required.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02539: The transfer [{0}] is already disabled.

Cause: The deployment record for the given transfer artifact is already disabled.

Action: No action required.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02540: The source [{0}] is already disabled.

Cause: The deployment record for the given source artifact is already disabled.

Action: No action required.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02541: The target [{0}] is already disabled.

Cause: The deployment record for the given target artifact is already disabled.

Action: No action required.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02542: Error occurred while deploying the transfer artifact with id [{0}].

Cause: Error occurred while deploying the given transfer artifact.

Action: The configuration of the given transfer artifact may be incorrect or error occurred while deploying the artifact. Check the transfer configuration and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02543: Error occurred while deploying the target artifact with id [{0}].

Cause: Error occurred while deploying the given target artifact.

Action: The configuration of the given target artifact may be incorrect or error occurred while deploying the artifact. Check the target configuration and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02544: Error occurred while enabling the transfer artifact with id [{0}].

Cause: Error occurred while enabling the given transfer artifact.

Action: The configuration of the given transfer artifact may be incorrect or error occurred while enabling the artifact. Check the transfer configuration and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02545: Error occurred while enabling the target artifact with id [{0}].

Cause: Error occurred while enabling the given target artifact.

Action: The configuration of the given target artifact may be incorrect or error occurred while enabling the artifact. Check the target configuration and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02546: Error occurred while disabling the transfer artifact with id [{0}].

Cause: Error occurred while disabling the given transfer artifact.

Action: The configuration of the given transfer artifact may be incorrect or error occurred while disabling the artifact. Check the transfer configuration and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02547: Error occurred while disabling the target artifact with id [{0}].

Cause: Error occurred while disabling the given target artifact.

Action: The configuration of the given target artifact may be incorrect or error occurred while disabling the artifact. Check the target configuration and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02548: Error occurred while undeploying the transfer artifact with id [{0}].

Cause: Error occurred while undeploying the given transfer artifact.

Action: The configuration of the given transfer artifact may be incorrect or error occurred while undeploying the artifact. Check the transfer configuration and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02549: Error occurred while undeploying the target artifact with id [{0}].

Cause: Error occurred while undeploying the given target artifact.

Action: The configuration of the given target artifact may be incorrect or error occurred while undeploying the artifact. Check the target configuration and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02550: Error creating source [{0}]. Another source was found with this name.

Cause: Another source found with the same name as the given name.

Action: Configure the source with a different name and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02551: Error creating target [{0}]. Another target was found with this name.

Cause: Another target found with the same name as the given name.

Action: Configure the target with a different name and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02552: Error creating transfer [{0}]. Another transfer was found with this name.

Cause: Another transfer found with the same name as the given name.

Action: Configure the transfer with a different name and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02553: Incorrect additional http header value. Use key value pair and # as separator.Example pro1=value1#pro2=value2.

Cause: Incorrect additional http header value.

Action: Correct the value and try deploying again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02554: Payload access is referring to invalid user/groups/roles.

Cause: Payload access is referring to invalid resource.

Action: Associate valid users/groups/roles and try redeploying the transfer.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02555: Not valid integer value [{0}] for attribute [{1}].

Cause: Not valid integer value.

Action: Correct the value and reperform the action.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02556: Not valid boolean value [{0}] for attribute [{1}]. Only true/false is allowed.

Cause: Not valid boolean value.Only true/false is allowed.

Action: Correct the value and reperform the action.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02557: Not valid value [{0}] for attribute [{1}]. Only allowed values are {2}.

Cause: Possible values for the field are restricted to predefined. Specified value is not allowed for this field.

Action: Correct the value and reperform the action.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02558: Invalid patten [{0}].

Cause: Invalid pattern.

Action: Correct the pattern and reperform the action.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02559: Error creating source [{0}]. Another deployed source was found with this name.

Cause: Another deployed source found with the same name as the given name.

Action: Configure the source with a different name or undeploy the other source with same name and try again

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02560: Error creating target [{0}]. Another deployed target was found with this name.

Cause: Another deployed target found with the same name as the given name.

Action: Configure the target with a different name undeploy the other target with same name and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02561: Error creating transfer [{0}]. Another deployed transfer was found with this name.

Cause: Another deployed transfer found with the same name as the given name.

Action: Configure the transfer with a different name or undeploy the other transfer with same name and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02562: Another source [{0}] was found with similar settings. Undeploy one of the source if they are identical.

Cause: Another source with similar settings is already deployed.

Action: Undeploy one of the source is its duplicate.

Level: LOW

Type: WARNING

Impact: SYSTEM

MFT-02563: Error deploying source {0}. The configured signing key alias is incorrect.

Cause: Error occurred while deploying the source. The configured PGP signing key alias is not valid.

Action: Check if the signing key is imported to the key store. If not, import it and try deployment again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02564: Error deploying transfer {0}. The configured PGP signing key alias for target {1} is incorrect.

Cause: Error occurred while deploying the target. The configured PGP signing key alias is not valid.

Action: Check if the PGP signing key is imported to the key store. If not, import it and try deployment again.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02565: Invalid processing funcation order.

Cause: Invalid order specified for processing actions.

Action: Correct the processing order and retry.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02566: Callout param {0} doesn''t matches with the callout[{1}] definition.

Cause: Invalid paramerter specified in the request.

Action: Refer to the callout definition. Correct the callout parameters and rety.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02567: No need to deploy as latest version of the artifact is already deployed.

Cause: Latest version of the artifact is already deployed.

Action: No need to deploy the artifact again.

Level: LOW

Type: WARNING

Impact: MESSAGE

MFT-02568: startDate is not specified for the schedule.

Cause: startDate is required for the schedule.

Action: Provide the startDate and retry.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02569: Illegal Arguments Exception while fetching list of schedule occurrences from ESS

Cause: Problem with arguments passed to function

Action: Provide a valid time zone and retry

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02570: Unable to fetch schedule by schedule name

Cause: The Schedule name is invalid

Action: Provide a valid schedule name and retry

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02571: Schedule has expired

Cause: The Schedule has expired

Action: Change the schedule to a valid range and retry

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02572: Unable to submit schedule purge job

Cause: Submitting the purge job to ESS threw an exception

Action: Change the schedule and retry

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02600: Error in creating target {0} . Error Message: {1}

Cause: An Error occurred while either reading or parsing the metadata xml file.

Action: Refer to the plugin logs for more details.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-03001: Error while starting the MFT server.

Cause: Unable to initialize the MFT Server dependent components.

Action: Ensure the infrastructure components like Identity Store, Security Store, Database, JCA are configured properly.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03002: Error while registering the Web Service source {0} with the provider.

Cause: Unable to register the Web Service source with the provider.

Action: Verify the Web Service source configuration and provider availability.Contact Oracle Support Services if the problem persists.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03003: Error while Initializing Web Service source {0}.

Cause: An error occurred while registering the Web Service sources.

Action: Check the configuration of the deployed Web Service sources.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03004: Error while initializing Security components for Stripe {0}.

Cause: An Error occurred while creating the application policy data in the domain-wide policy store or while obtaining the connection to the default realm identity store.

Action: Ensure that the required permissions are granted to the MFT source and check the config parameters of the Identity Store.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03005: Error while initializing the WebLogic Work Manager {0}.

Cause: Unable to look up the Work Manager from the underlying environment.

Action: Check the Work Manager configuration in the WebLogic console.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03006: Error while registering the EM Discovery Mbean with Object name {0}.

Cause: An error occurred while registering the Config MBean with the Platform MBean Server.

Action: Review the diagnostic log for the exact error. Check whether management infrastructure is up and MFT MBean details are correct.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03007: Error while shutting down MFT server.

Cause: Unable to stop one or more dependent components of the MFT server.

Action: Review the diagnostic log for the exact error. Failure might be due to configuration of infrastructure components or connection problem.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03008: Error occurred while unsubscribing the Web Service source.

Cause: Unable to unsubscribe the Web Service source.

Action: Failure could be due to unavailability of Web Service registration service or improper Web Service configuration. Review the diagnostic log for the exact error.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03009: Error while getting the Application Properties metadata.

Cause: Unable to get the Application Properties details.

Action: Check the Application Properties configuration in the system.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03010: Error occurred while updating the port {2} for service {1} of server {0} by user {3}

Cause: Exception while updating the port details of databases.

Action: Check the service, server instance and port. If these are correct it could be due to database issue. Review the diagnostic log for the exact error.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03011: Error while loading the MFT Configuration MBean Properties from underlying infrastructure.

Cause: Unable to load the MBean Properties.

Action: Unable to load the MBean config properties from the underlying metadata store. Review the diagnostic log for the exact error.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03012: Error while initializing the MFT persistence context.

Cause: Unable to initialize the persistence units context.

Action: Check the database availability and connection configuration. Review the diagnostic log for the exact error.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03013: Error while initializing the MFT System event manager.

Cause: Unable to initialize the System event manager with required Queue and Topic receiver(s).

Action: Check the JMS system event Queue and Topic configurations in the WebLogic console.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03014: Error while initializing the MFT Purge event manager.

Cause: Unable to initialize the Purge event manager with required Queue receiver(s).

Action: Check the JMS purge event Queue and Topic configurations in the WebLogic console.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03015: Error while initializing the source listener {0}

Cause: Unable to start the JCA adapter to poll the files on the source.

Action: Check the source configuration parameters. Contact Oracle Support Services if the problem persists.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03016: Error updating port for server instance [{0}] and service [{1}]. The given server instance or service is incorrect.

Cause: Error occurred while updating port assignment for the given server instance and service in database.

Action: Check the port configuration for the server instance. Contact Oracle Support Services if the problem persists.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03017: File [{0}] doesn''t exists.

Cause: File doesn't exist.

Action: Check if the file exists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03018: Not able to create file [{0}].

Cause: Invalid location.

Action: Check if the parent directory exists. Also, check the file permission for the parent directory.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03019: Invalid XML format or scheam validation failed for [{0}].

Cause: Invalid XML or schema validation failed.

Action: Validate the XML against the schema and rerun.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03250: Invalid argument(s) {0} provided to MFT utility for method {1}.

Cause: Arguments of the MFT command line utility are either missing or invalid.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03251: MFT utility - Operation {0} failed for parameters {1}.

Cause: EJBException thrown by the MFT utility due to failure in operation.

Action: Refer to MFT utilities documentation to determine the arguments and their types for the given command.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03252: Exception occurred while executing runtime purge for batch id [{0}].

Cause: Exception occurred while executing runtime purge for batch id [{0}].

Action: Try again with the recovery option by passing same batch id. If the problem persists, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03253: Error while processing the purge event {0}.

Cause: An error occurred during processing of the purge event by the JCA JMS Adapter.

Action: Check the Purge Event Queue configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03254: Exception occurred while executing runtime archive for batch id [{0}].

Cause: Exception occurred while executing runtime archive for batch id [{0}].

Action: Try again by passing same batch id. If the problem persists, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03255: Exception occurred while executing runtime restore from archive file [{0}].

Cause: Exception occurred while executing runtime restore from archive file [{0}].

Action: Try again. If the problem persists, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03302: Failed to initialize the engine. The engine message queue receivers for queue {0} were not initialized properly.

Cause: Problem with JMS queue settings.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Correct the queue settings and restart the MFT server.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03303: Error while stopping queue receivers for queue {0}.

Cause: An error has occurred while stopping the queue receivers.

Action: Review the diagnostic log for the exact error. Check the MFT specific JMS Queue settings in the WebLogic console.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-03304: Failed to initialize the engine. The engine queue message producer for queue {0} was not initialized properly.

Cause: Problem with JMS queue settings.

Action: Check the MFT specific JMS Queue settings in the WebLogic console.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-03305: Error while stopping the message producer for queue {0}.

Cause: An error has occurred while stopping queue message producer.

Action: Review the diagnostic log for the exact error. Check the MFT specific JMS Queue settings in the WebLogic console.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-03306: Error while initializing the source listeners

Cause: Unable to start the JCA adapter to poll the files on the sources.

Action: Check the source configuration parameters. Contact Oracle Support Services if the problem persists.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03307: Error initializing the MFT message processing engine.

Cause: An error has occurred while starting the message processing engine for MFT.

Action: Check the MFT specific JMS Queue settings in the WebLogic console.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03308: Error during shutdown of source listener {0}.

Cause: Unable to stop the JCA Adapter that is polling the source.

Action: Review the diagnostic log for the exact error. Check the MFT specific JMS Queue settings in the WebLogic console.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03309: Error stopping the MFT message processing engine.

Cause: An error has occurred while stopping the message processing engine for MFT.

Action: Review the diagnostic log for the exact error. Check the MFT specific JMS Queue settings in the WebLogic console.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03310: Error initializing the task queue receivers.

Cause: An error has occurred while starting the task queue receivers for MFT.

Action: Check the MFT task queue JMS Queue settings in the WebLogic console.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03601: Error while starting the hosted server {0} with root dir {1} and port {2}.

Cause: An error occurred while starting the hosted server at a specified port and root directory.

Action: Check the root directory and Port assigned to the hosted server. For FTP over SSL and sFTP Servers, verify that all the required keys are configured.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03602: Error while shutting down the Hosted Server {0} running at port {1}.

Cause: An error occurred while stopping the hosted server running at the specified port.

Action: Review the diagnostic log for the exact error.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03604: Error while allocating the HA ports for the server instance {0}.

Cause: An error occurred while persisting the ports of the hosted servers for a given server instance.

Action: Check the ports definitions in MDS and the database config parameters. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'.Contact Oracle Support Services if the problem persists.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03605: Error while fetching the Key store configuration from MDS.

Cause: An Error occurred while getting the default key store MO from MDS.

Action: Unable to get the key store information from the underlying metadata store during initialization. Review the diagnostic log for the exact error.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03606: Error while fetching the ES root directories from path {0} with option {1} for {2} server

Cause: An Error occurred while getting the directories under the ES root directory

Action: Check the Embedded Server root directory configuration and access permissions. Review the diagnostic log for the exact error.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04001: No associated active source found for the incoming file {0} from the endpoint {1}.

Cause: No matching MFT source found for the incoming message.

Action: Create and deploy the matching source. Redeliver the message to MFT.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04002: Multiple matching active sources found for the file {0} from endpoint {1}. Matching sources : {3}.

Cause: Invalid configuration: multiple active deployed sources for the same endpoint.

Action: Activate only one source for a given endpoint configuration.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04003: Not able to find the metadata reference for source with id {0}.

Cause: Reference metadata for the given source id does not exist in repository.

Action: Restore the deleted data in the metadata repository and redeploy the source.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04004: Invalid source message received for source message processing. Source message ID {0}.

Cause: Internal processing error.

Action: Contact Oracle Support Services.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04005: Invalid source configuration.

Cause: Invalid source configuration.

Action: The listening or Web Service source could not be registered due to error while creating the endpoint. Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04007: Associated source {2} for the file {0} from endpoint {1} was disabled.

Cause: Associated source was disabled.

Action: Enable the source and redeliver the message to MFT.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04008: No matching active transfer found for the message.

Cause: There is no associated transfer with a matching content type for the incoming message.

Action: Associate and deploy the matching transfer for the incoming message and resubmit the source message.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04009: Error during source message processing.

Cause: Unexpected error.

Action: Unexpected error encountered during source processing. Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04010: Source {0} is disabled.

Cause: Source is disabled.

Action: Enable the source and retry.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04011: Duplicate source message. Original message id {0}.

Cause: Duplicate message submitted.

Action: Check the status of original message.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04012: Directory reference as payload is not allowed for the source if compression processing action is not associated with the source.

Cause: Directory reference as payload is not allowed if compression processing action is not associated with the source.

Action: Associate compression as processing action for the source and redeploy the source. Resubmit the message after that.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04013: Invalid Payload information.

Cause: Bad request or specified payload doesn't exists.

Action: Send valid request, make sure payload information is correct.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04014: No source metadata record found with name [{0}].

Cause: No source metadata record found with given name.

Action: Check if the source metadata was deleted. Try again by specifying correct source name.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04015: Source plugin error while creating the endpoint from source metadata.

Cause: Plugin error while creating the endpoint from source metadata..

Action: Check the logs for more details. In case of custom plugin implementation, check the plugin implementation otherwise contact Oracle Support Services if the problem persists

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04202: File {0} does not exist in the file system.

Cause: File does not exist in the file system.

Action: If the file has been purged, restore the file and resubmit the appropriate message.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04204: IO exception encountered during message processing.

Cause: IO exception.

Action: IO exception encountered. Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04205: Error while encrypting the payload using PGP.

Cause: PGP encryption setting error.

Action: Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04206: Error while decrypting payload using PGP.

Cause: Invalid PGP-encrypted payload.

Action: Check the incoming payload.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04207: Error while compressing the payload.

Cause: Compression setting error.

Action: Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04208: Error while decompressing the payload.

Cause: Invalid compressed payload.

Action: Check the incoming payload.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04209: Error while executing source preprocessing

Cause: Unexpected source preprocessing error.

Action: Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04210: Error while executing source postprocessing

Cause: Unexpected source postprocessing error.

Action: Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04211: Error while executing target preprocessing

Cause: Unexpected target preprocessing error.

Action: Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04212: Error while executing target postprocessing.

Cause: Unexpected target postprocessing error.

Action: Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04213: Error during instance message processing.

Cause: Unexpected error.

Action: Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04214: Unsupported compressed payload content.

Cause: The compression format of the payload is not supported in MFT.

Action: None: compressed format is not supported in MFT.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04215: Multiple file decompression is only supported for web service targets: SOAP, SOA, Service Bus, and ODI

Cause: Compressed payload contains multiple files.Multiple file decompression is only supported for web service targets: SOAP, SOA, Service Bus, and ODI.

Action: Decompress and submit a message for each decompressed file.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04216: No file found after decompression.

Cause: There were no files found after decompression.

Action: None: Invalid input message.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04217: PGP private key not found for key alias {0}

Cause: Key for the alias is not present in the key store.

Action: Import the key and resubmit the message.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04218: PGP public key not found for key alias {0}

Cause: Key for the alias is not present in the key store.

Action: Import the key and resubmit the message.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04219: Message cannot be processed as the associated schedule has expired.

Cause: Message cannot be processed as the associated schedule has expired.

Action: Associate valid schedule and redeploy.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04220: PGP private key is invalid or key password is incorrect.

Cause: PGP private key is invalid or key password is incorrect.

Action: Correct the key password if key password is incorrect otherwise import valid PGP private key.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04221: Incoming data is encrypted with different public key.

Cause: PGP public key used for encryption is not corresponding key pair for private key specified.

Action: Associate correct private key alias for the decryption action.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04222: Incoming data is not a valid PGP encrypted data.

Cause: Incoming data is not a valid PGP encrypted data.

Action: Check the incoming data.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04223: Encryption algorithm or key length is restricted under the java policy.

Cause: Encryption algorithm or key length is restricted.

Action: Make sure algorithms and key used is not restricted under java security policy.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04224: PGP Encryption key is not a valid encryption key.

Cause: PGP Encryption key is not a valid encryption key.

Action: Make sure key alias is a correct PGP encryption public key.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04225: Error while decryption.Signature is not valid.

Cause: Signature is not valid.

Action: Check if the encrypted payload is valid or not.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04226: Cannot find the matching signee key.

Cause: Unknown signee.

Action: Add signee's pgp key to the key store.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04227: Script({0}) execution failed with error: ({1})

Cause: Error in script execution.

Action: Review the diagnostic log for the exact error and resubmit the message after fixing script.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04228: Script({0}) execution failed with unknown error

Cause: Unexpected error in script execution.

Action: Review the diagnostic log for the exact error and resubmit the message after fixing script.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04229: Script({0}) execution timed out

Cause: Script execution timed out.

Action: Script execution is taking longer time then given timeout. Fix the script and resubmit the message.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04230: Script({0}) execution interrupted

Cause: Script execution interrupted.

Action: Please validate the script.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04401: Exception encountered during execution of callout {0}.

Cause: Error while executing custom callout.

Action: Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04501: Payload {0} not found in the MFT data storage.

Cause: Payload does not exist in the MFT data storage.

Action: If the data exists, try to restore the data.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04502: Invalid digest algorithm {0}.

Cause: Invalid algorithm.

Action: Correct the setting for the digest algorithm.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04503: Unexpected Error.

Cause: Unexpected exception occurred.

Action: Review the diagnostic log for the exact error.

Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-04504: JTA Transaction Error

Cause: JTA Transaction Error

Action: Review the diagnostic log for the exact error.

Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-04506: The archive {0} does not exist.

Cause: The given archive file could not be found. The file path is incorrect or the archive is empty.

Action: Check the archive file path. If path is correct, then ensure that the archive file is proper and try again.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04507: IP address or name of the host machine could not be determined.

Cause: IP address or name of the host machine could not be determined.

Action: Check if the system and network configuration is correct. Contact Oracle Administrator if problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-04508: Invalid argument.

Cause: Invalid argument.

Action: Check the input arguments provided and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04509: External ports in the application properties cannot be null.

Cause: External ports in the application properties are null.

Action: Set the external ports in the application properties.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04510: External ports in the application properties cannot be null.

Cause: External ports in the application properties are null.

Action: Set the external ports in the application properties.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04511: External ports in the application properties cannot be null.

Cause: External ports in the application properties are null.

Action: Set the external ports in the application properties.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04512: Error creating the directory {0}.

Cause: IO exception.

Action: Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04513: Invalid in-progress transfer count {0} for source.

Cause: Unexpected error.

Action: Internal error while calculating the progress in transfer count. No action needed.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04514: Invalid in-progress target count {0} for the transfer.

Cause: Unexpected error.

Action: Internal error while calculating the progress in transfer count. No action needed.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04515: Transfer {0} is disabled.

Cause: Transfer is disabled.

Action: Enable the transfer and retry.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04516: Target {0} is disabled.

Cause: Target is disabled.

Action: Enable the target and retry.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04517: No target record found for the instance ID {0}.

Cause: No target record found for the instance.

Action: Try resubmitting the transfer or source instead.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04518: Target {0} is no longer associated with transfer {1}.

Cause: Target is no longer associated with transfer {1}.

Action: Associate the target with the transfer and retry.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04519: Unexpected error occurred while processing message with id [{0}].

Cause: An unexpected error occurred during processing of the message with the given message id.

Action: Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04520: Internal ports in the application properties cannot be null.

Cause: Internal ports in the application properties are null.

Action: Set the internal ports in the application properties.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04521: Internal ports in the application properties cannot be null.

Cause: Internal ports in the application properties are null.

Action: Set the internal ports in the application properties.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04522: Internal ports in the application properties cannot be null.

Cause: Internal ports in the application properties are null.

Action: Set the internal ports in the application properties.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04523: Error while moving the file [{0}] to location [{1}].

Cause: Issue while moving the file from one location to another.

Action: Check user permissions in the destination location.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04524: Unexpected error occurred during instance message processing for transfer [{0}].

Cause: An unexpected error occurred during instance message processing for the given transfer.

Action: Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04525: Unexpected error occurred during message processing for target [{0}].

Cause: An unexpected error occurred during message processing for the given target.

Action: Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04526: Unexpected error occurred during message processing for source [{0}].

Cause: An unexpected error occurred during message processing for the given source.

Action: Review the diagnostic log for the exact error.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04801: Error while processing the system event {0}.

Cause: An error occurred during processing of the system event by the JCA JMS Adapter.

Action: Check the System Event Queue and Topic configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04802: Error while submitting the system event {0} for service {1}.

Cause: An error occurred during processing of the system event by the JCA JMS Adapter.

Action: Check the System Event Queue and Topic configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04803: Error while submitting the system event {0} with resubmit type as {1} for instances {2} by user {3}.

Cause: An error occurred during submission of the system event by the JCA JMS Adapter.

Action: Check the System Event Queue and Topic configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04804: Error while submitting the system event {0} with instance ID {1} by user {2}.

Cause: An error occurred during submission of the system event by the JCA JMS Adapter.

Action: Check the System Event Queue and Topic configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04805: Error while submitting pause transfer request. Target Message with Id [{0}] does not exist.

Cause: The given target message does not exist in database.

Action: Check the target message Id is correct and try again. Use the UI Monitoring Dashboard to verify target message details.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-04806: Error while submitting resume transfer request. Target Message with Id [{0}] does not exist.

Cause: The given target message does not exist in database.

Action: Check the target message Id is correct and try again. Use the UI Monitoring Dashboard to verify target message details.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05001: Unsupported endpoint {0} passed to adapter.

Cause: Unsupported endpoint has been passed to the adapter. Adapter only supports File / FTP / sFTP / JMS.

Action: Check the endpoint that was passed.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05002: Error occurred while creating JCABindingFactoryImpl. Type: {0}, endpoint: {1}.

Cause: An error occurred while initializing the adapter.

Action: Check the adapter properties and try again. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05003: No payload found while delivering to endpoint {0}.

Cause: No payload found while delivering a message.

Action: Try resubmitting the message.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05004: Error occurred while delivering message [{0}] to endpoint [{1}].

Cause: Error occurred while delivering message.

Action: Check the adapter properties and try again. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05005: Error occurred while closing connection after sending file to end point [{0}].

Cause: Error occurred while closing adapter connection.

Action: Check adapter properties and try again. If the problem persists,contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05006: Error occurred while trying to open connection for endpoint [{0}], Type [{1}] and interface [{2}].

Cause: Error occurred while trying to open connection.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05007: Exception occurred while sending file [{0}] to endpoint [{1}].

Cause: File [{0}] does not exist.

Action: Ensure that the file [{0}] exists and resubmit.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05008: Exception occurred while creating connection with [{0}] for operation [{1}].

Cause: Error occurred while creating connection.

Action: Check the adapter properties and try again. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05010: Exception occurred while validating adapter binding reference property for end point [{0}].

Cause: Could not validate Binding reference properties.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05011: Value for property 'Physical Directory' is missing.

Cause: No value specified for property 'Physical Directory' in the input connection properties.

Action: Specify a value for 'Physical Directory' in the connection properties for the endpoint and try again.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05012: Exception occurred while creating connection for polling to end point [{0}] for operation [{1}]

Cause: Error occurred while creating connection.

Action: Check the adapter properties and try again. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05013: Exception occurred while creating poller service for endpoint [{0}].

Cause: Error occurred while creating poller service.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05014: Exception occurred while starting poller service for endpoint [{0}].

Cause: Error occurred while starting poller service.

Action: Check the adapter properties and try again. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05015: Exception occurred while validating poller service for endpoint [{0}].

Cause: Could not validate adapter properties for poller service.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05016: NOT_IN_USE

Cause: NOT_IN_USE

Action: NOT_IN_USE

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05017: Error occurred while stopping the adapter polling.

Cause: Exception occurred while trying to close the adapter to stop polling the messages.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05018: NOT_IN_USE

Cause: NOT_IN_USE

Action: NOT_IN_USE

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05019: Exception occurred while creating file [{0}] received from end point [{1}]

Cause: Could not create the file [{0}], which was received from endpoint [{1}].

Action: Check if the file exists but is a directory rather than a regular file, does not exist but cannot be created, or cannot be opened for any other reason.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05020: IO Exception occurred while writing to file [{0}] received from endpoint [{1}].

Cause: File created, but could not write to the file [{0}], which was received from endpoint [{1}].

Action: Check if write permissions are provided for file [{0}].

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05021: IO Exception occurred while closing file [{0}] after writing. This file was received from endpoint [{1}].

Cause: File [{0}] written, but IO exception occurred while closing the file, which was received from endpoint [{1}].

Action: Check if write permissions are provided for the file [{0}].

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05022: Source Message was found null while transferring to endpoint [{0}].

Cause: Source message found null.

Action: Resubmit the message. If the problem persists, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05023: The JNDI queue name specified is null.

Cause: Adapter initialization failed because of invalid queue name.

Action: Try again. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05024: Exception occurred in postprocessing while moving or renaming the file after sending to [{5}]. Source File Name [{1}], Source Folder [{0}], Target Folder [{2}], Target File Name [{3}], Target File Naming Convention [{4}].

Cause: Error occurred while moving or renaming a file after sending.

Action: Check the adapter properties and resubmit the message. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05025: Exception occurred while creating directory [{0}] for storing file [{1}] received from endpoint [{2}].

Cause: Could not create directory [{0}].

Action: Ensure that permissions (for creating directory and files) are assigned to this folder.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05026: NOT_IN_USE

Cause: NOT_IN_USE

Action: NOT_IN_USE

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05027: Exception occurred while looking for directory for storing file [{0}] received from endpoint [{1}].

Cause: Error occurred while looking for directory for storing file.

Action: Check server properties. If the problem persists, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05028: Exception occurred while deactivating poller service for end point [{0}].

Cause: Error occurred while deactivating poller service.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05029: Exception occurred while closing poller service for endpoint [{0}].

Cause: Error occurred while closing poller service.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05030: Configuration mismatch found while polling to endpoint [{0}]. Alert code [{1}].

Cause: Configuration mismatch found while polling to endpoint [{0}].

Action: Ensure that the host name, port, username and password configured are correct and that the server is running.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05031: Error occurred while reading metadata of file [{0}] from endpoint [{1}].

Cause: Error occurred while reading metadata of file.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05032: Unexpected error during target delivery.

Cause: Unexpected error during target delivery.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05033: Error while creating the B2B/Healthcare endpoint {0} during target delivery.

Cause: Unexpected error while creating a b2b/healthcare endpoint.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05034: Error while delivering the payload to B2B/Healthcare target.

Cause: Unexpected error while delivering the payload.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05035: Error occurred while closing connection after getting size for file [{0}] for end point [{1}].

Cause: Error occurred while closing adapter connection.

Action: Check adapter properties and try again. If the problem persists,contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05036: Error occurred while closing connection after pausing transfer for end point [{0}].

Cause: Error occurred while closing adapter connection.

Action: Check adapter properties and try again. If the problem persists,contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05037: Value for property 'Host Name' is missing.

Cause: No value specified for property 'Host Name' in the input connection properties.

Action: Specify a value for 'Host Name' in the connection properties for the endpoint and try again.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05038: Value for property 'Port' is missing.

Cause: No value specified for property 'Port' in the input connection properties.

Action: Specify a value for 'Port' in the connection properties for the endpoint and try again.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05039: Value for property 'User Name' is missing.

Cause: No value specified for property 'User Name' in the input connection properties.

Action: Specify a value for 'User Name' in the connection properties for the endpoint and try again.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05040: Error occurred during shutting down while clearing JCA resources.

Cause: Unexpected error occurred while clearing JCA resources.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05041: Error occurred while polling the listening source {0}.

Cause: Unexpected error occurred while polling the JCA source.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05201: Access denied.

Cause: Access denied for the resource/action.

Action: Check if you have the permission for given resource/action.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05202: Unable to authenticate the user.

Cause: An error occurred while authenticating the user.

Action: Correct the username/password and retry.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05203: The Content-MD5 you specified did not match what is received.

Cause: Content-MD5 mismatch.

Action: .

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05204: A container with same name already exists.

Cause: A container with same name already exists.

Action: Provide a different container name and retry.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05205: Container isn't empty.

Cause: There are some objects stored in the container.

Action: Delete all the objects in the container and retry.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05206: No container found for given container name.

Cause: No container found.

Action: Provide a valid container name or create new container with the given name.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05207: Invalid key name.

Cause: Invalid key name.

Action: Provide a valid key name and retry.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05208: The requested range cannot be satisfied.

Cause: Invalid range.

Action: Provide a valid range.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05209: Invalid request.

Cause: Some required parameter is missing in the request.

Action: Provide all the parameters in the request and retry.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05210: Unexpected server error.

Cause: Unexpected server error, response code 500.

Action: Check the service setting and retry. For more details, review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05211: Malformed URL used.

Cause: A malformed URL has occurred. Either no legal protocol could be found in a specification string or the string could not be parsed.

Action: Correct the provided url and retry.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05212: Unexpected error occurred.

Cause: Unexpected error.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05213: Unexpected source error occurred.

Cause: Unexpected error.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05214: Error encountered while connection/authentication.

Cause: Error while connection/authentication.

Action: Make sure the connection url and user information is correct. Also, make sure to import the certificate in the server.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05215: Client error encountered for the request.

Cause: Client error encountered for the request.

Action: Check the server connection/user details. Also, review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05216: Server error encountered for the request.

Cause: Server error encountered for the request.

Action: Check the storgae service setting.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05217: Malformed URI used.

Cause: A malformed URI has been used. Unable to locate the required file

Action: Correct the provided uri and retry.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05218: File Not Found.

Cause: File you are trying to refer to is not found

Action: Correct the provided file path.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05219: IO Exception

Cause: An I/O Exception occurred

Action: An I/O exception occurred.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05220: URI Exception

Cause: URI Exception has occurred

Action: Please provide a valid URI location

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05250: Error while reading or writing the serialized configuration information for [{0}].

Cause: Endpoint configuration issue.

Action: Check the configuration and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05251: Error in the idc filters.

Cause: Error in the idc filters.

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05252: Errors while processing service request [{0}] from content server [{1}].

Cause: Errors thrown from the Content Server.

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05253: Error in the connection for endpoint [{0}].

Cause: Error in the protocol layer.

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05255: Folder [{0}] ''t accessible.

Cause: Folder not accessible.

Action: Check if the remote folder exists and user has permission to access the folder.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05256: Error while processing the service due to SSL configuration and setup for endpoint [{0}].

Cause: Exception due to SSL configuration and setup.

Action: Make sure certificate is imported properly.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05257: Error occured during the post download operation[{0}].

Cause: Error occured during the post download operation.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05400: Invalid SOAP request received by MFTService on endpoint {0}.

Cause: SOAP message contains invalid XML.

Action: Review the SOAP request and check if the SOAP message contains invalid XML. This can be done by copying the request to a temporary XML file and opening the file in a web browser.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05401: MFT Service could not deliver message to Web Service endpoint {0}.

Cause: Web Service endpoint configured in MFT Target definition is either invalid or down.

Action: Check the Target configuration in the MFT console and verify the Web Service configuration parameters such as url , Port and Service. Try connecting to the configured endpoint by typing URL in a web browser.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-05402: Invalid SOAP request received by MFT Discovery Service from URL {0}.

Cause: SOAP Message contains invalid XML.

Action: Review the SOAP request and check if the SOAP message contains invalid XML. This can be done by copying the request to a temporary XML file and opening the file in a web browser.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05403: Discovery service is unable to query MFT Sources for the given application {0} and search Filter {1}.

Cause: MFT Source Message Table cannot be queried due to a Persistence Error.

Action: Verify whether the MFT Server is initialized successfully in the MFT Diagnostic Log. If there are issues in loading MFT persistence, try restarting MFT.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05404: Discovery service is unable to create a SOAP response for the given application {0} and search Filter {1}.

Cause: SOAP exception in creating SOAP response.

Action: Contact your Oracle Administrator.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05405: SOAP Request received on endpoint url {0} contains multiple attachments, which is not supported in MFT.

Cause: SOAP message contains an AttachmentPart that has multiple attachments. MFT does not support multiple attachments inline. Only one attachment is allowed.

Action: Review the SOAP request and make sure that the AttachmentPart has only one attachment.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05406: MFT Service is unable to process the AttachmentPart in the SOAP request received from endpoint url {0}.

Cause: IO error in reading the attachment stream.

Action: Review the SOAP request and make sure the attachment is configured according to SOAP standards.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05407: MFT Service is unable to process inline payload received from endpoint url {0}.

Cause: IO exception in reading inline Payload embedded in the SOAP body.

Action: Review the SOAP request and make sure the inline payload embedded in the SOAP body conforms to the schema defined in the MFT Service wsdl.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05408: MFT Service is unable to process reference payload coming from the endpoint url {0}.

Cause: IO exception in reading Reference payload embedded in the SOAP body.

Action: Review the SOAP request and make sure the FileReference or FTPReference element in the SOAP body conforms to the schema defined in the MFT Service wsdl.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05409: MFT Service is unable to process SOAP Headers coming from the endpoint url {0}

Cause: IO exception in reading SOAP Headers embedded in the SOAP message.

Action: Review the SOAP request and make sure the headers conform to the MFTHeader element schema defined in the MFT Service wsdl.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05410: Invalid url in Reference Payload element received on endpoint url {0} for reference type {1}.

Cause: For an incoming SOAP request containing a Reference Payload element, the URL defined in the message is invalid.

Action: Review the SOAP request and verify that the URL element in the Reference Payload contains a valid URL.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05411: Unable to create SOAP message from MessageFactory.

Cause: Unknown error due to the SOAP MessageFactory being unable to create the SOAP message.

Action: Contact the Oracle Administrator.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-05412: MFT Web Service transport is unable to create a SOAP Message with InlinePayload for Web Service endpoint {0}.

Cause: SOAP exception while adding InlinePayload element in the SOAP message. This could be due to invalid inline payload data passed to Transport layer

Action: Review the SOAP target configured in the MFT console to verify the Payload type and message type configuration. Also verify that the InlinePayload being passed to transport layer.

Level: CRITICAL

Type: ERROR

Impact: MESSAGE

MFT-05413: MFT Web Service transport is unable to create a SOAP Message with Reference Payload for Web Service endpoint {0}.

Cause: SOAP exception while adding Reference Payload element in the SOAP message. This could be due to invalid Reference payload data passed to Transport layer

Action: Review the SOAP target configured in the MFT console to verify the type of reference defined.

Level: CRITICAL

Type: ERROR

Impact: MESSAGE

MFT-05414: MFT Web Service transport is unable to create SOAP Message with Reference of type {0} for Web Service endpoint {1}

Cause: SOAP exception while adding FTP reference Payload element in the SOAP message. This could be due to invalid Reference payload data passed to the transport layer

Action: Review the SOAP target configured in the MFT console to verify the type of reference defined.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05415: MFT Web Service transport is unable to create SOAP Message with Base64 Encoded format for Web Service endpoint {0}

Cause: Error in encoding the SOAP message in Base64 format.

Action: Review the SOAP target configured in the MFT console to verify the payload type and MessageType.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05416: MFT Web Service transport is unable to create SOAP Message with SOAP Header {0} for Web Service endpoint {1}.

Cause: SOAP Exception while adding the SOAP headers to SOAP Message.

Action: Contact the Oracle Administrator.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05417: MFT Web Service transport is unable to create SOAP Message with additional transport headers for Web Service endpoint {0}.

Cause: SOAP Exception while adding the HTTP headers to SOAP Message.

Action: Review Target configuration in MFT console to verify Additional headers field. Headers format is [header1]=[value1]#[header2]=[value2].

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05418: MFT Service is unable process SOAP Message containing Base64 content for Web Service endpoint {0}.

Cause: Error in Decoding the SOAP message containing Inline payload in Base64 format. This could be because the message does not contain a valid Base64 format.

Action: Review the SOAP target configured in the MFT console to verify the payload type and MessageType. Also check the SOAP request to validate the Base64 format.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05419: URL {0} configured for Web Service endpoint is invalid.

Cause: Web Service endpoint configured in MFT Target definition is either invalid or down.

Action: Check the target configuration in the MFT console and verify the Web Service URL. Try connecting to the configured endpoint by typing the URL in a web browser.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05420: MFT webservice Transport has encountered error parsing Inline XML payload for webservice endpoint {0}.

Cause: Error in parsing Inline XML payload. This could be because the Inline payload does not contain a valid XML format.

Action: Review the SOAP target configured in the MFT console to verify the payload type and MessageType. Also check the inline payload to validate the XML format.

Level: High

Type: ERROR

Impact: Message

MFT-05421: MFT webservice Transport has encountered error processing the payload stream.

Cause: Error in reading the inlne payload stream. This could be because the the payload stream may is Null or contains invalid data

Action: Review the SOAP target configured in the MFT console to verify the payload type and MessageType. Also check the payload received from MFT Source contains valid data.

Level: High

Type: ERROR

Impact: Message

MFT-05422: Error in processing EventService request. SourceName input parameter {0} is invalid.

Cause: Error in processing the EventService request. The provided Source name is invalid or does not exists.

Action: Submit the Event Request with valid Source Name.

Level: High

Type: ERROR

Impact: Message

MFT-05423: Error in processing EventService request. The Source {0} either doesn''t exists or not deployed.

Cause: Error in processing the EventService request. The provided Source does not exists or is not deployed.

Action: Submit the Event Request with valid Source Name or after deploying the intended Source.

Level: High

Type: ERROR

Impact: Message

MFT-05424: Error in processing EventService request. The Source {0} is not active.

Cause: Error in processing the EventService request. The provided Source is disabled.

Action: Submit the Event Request after enabling the intended Source.

Level: High

Type: ERROR

Impact: Message

MFT-05425: Error in processing EventService request. Unable to fetch the metadata for Source {0}.

Cause: Error in processing the EventService request. Error while fetching the metadata for the Source.

Action: Contact your Oracle Administrator.

Level: High

Type: ERROR

Impact: Message

MFT-05426: Error in processing EventService request. Event is not supported for Source {0}, which is of type {1}.

Cause: Error in processing the EventService request. The Source does not accept the event request, Event mechanism is not supported for these types of Sources.

Action: Submit the Event Request with Sources for which events are supported, ex. File, FTP, SFTP.

Level: High

Type: ERROR

Impact: Message

MFT-05427: Error in processing EventService request. Event is not enabled for Source {0}.

Cause: Error in processing the EventService request. The Event option is not enabled at the Source.

Action: Submit the Event Request after enabling the event option in the Source.

Level: High

Type: ERROR

Impact: Message

MFT-05428: Error in processing EventService request. User {0} is not authorized to invoke the Event on Source {1}.

Cause: Error in processing the EventService request. The User does not have the requisite permission to invoke the event on Source.

Action: Submit the request with user having the necessary permissions.

Level: High

Type: ERROR

Impact: Message

MFT-05429: Error in processing EventService request. There is an Event with session id {0} already active on Source {1}.

Cause: Error in processing the EventService request. Previous Event submitted for the source is still in progress.

Action: Submit the request once the previous event request is completed.

Level: High

Type: ERROR

Impact: Message

MFT-05430: Error in processing EventService request. Polling is active on Source {0}.

Cause: Error in processing the EventService request. Source is already started in polling mode.

Action: Submit the request once the polling is stopped.

Level: High

Type: ERROR

Impact: Message

MFT-05431: Error in processing EventService request. Error in validating the Event Request.

Cause: Error in processing the EventService request. Exception while validating the request.

Action: Submit the request again. Contact your Oracle Administrator if the problem persists.

Level: High

Type: ERROR

Impact: Message

MFT-05432: Error in processing EventService request. Required input parameter {0} is missing.

Cause: Error in processing the EventService request. The parameter required for processing the event request for source is missing.

Action: Submit the request with required parameter.

Level: High

Type: ERROR

Impact: Message

MFT-05433: Error in processing EventService request.

Cause: Exception in processing the EventService request.

Action: Contact your Oracle Administrator.

Level: High

Type: ERROR

Impact: Message

MFT-05434: Error in processing EventService request. Invalid User, unable to get the user details from request.

Cause: Exception in processing the EventService request. User Subject is null in the request.

Action: Contact your Oracle Administrator.

Level: High

Type: ERROR

Impact: Message

MFT-05435: Error in processing EventService request. Invalid Event Session Id {0}.

Cause: Exception in processing the EventService request. Provided Event Session Id is invalid.

Action: Resubmit the request with valid Event Session Id.

Level: High

Type: ERROR

Impact: Message

MFT-05436: Error in processing EventService request. No Event found with provided Event Session Id {0}.

Cause: Exception in processing the EventService request. No Event found with provided Event Session Id.

Action: Resubmit the request with valid Event Session Id.

Level: High

Type: ERROR

Impact: Message

MFT-05437: Error in processing EventService request. Persistence error while getting the Event/Instance details.

Cause: Exception in processing the EventService request. Error in Persistence layer.

Action: Contact your Oracle Administrator.

Level: High

Type: ERROR

Impact: Message

MFT-05438: Error in processing EventService request. SOAP error while creating the response.

Cause: Exception in processing the EventService request. Error in creating the response.

Action: Contact your Oracle Administrator.

Level: High

Type: ERROR

Impact: Message

MFT-05439: Parameter {0} configured with value {1} at ODIInvoke processing action is invalid.

Cause: The Parameter(s) configured at the ODIInvoke processing function is not valid.

Action: Correct the parameter configured as per the standard expected for Webservices.

Level: High

Type: ERROR

Impact: Message

MFT-05440: Error while getting the {1} type of Operation {0}.

Cause: An error occurred while parsing the request/response/fault types of an Operation.

Action: Verify whether the valid Operation is configured. Contact Oracle Support if the problem persists.

Level: High

Type: ERROR

Impact: Message

MFT-05441: Exception while processing the ODIInvoke Processing function. {0}

Cause: An error occurred while processing the ODIInvoke processing function.

Action: Verify whether the valid parameters are configured at the ODIInvoke processing function. Contact Oracle Support if the problem persists.

Level: High

Type: ERROR

Impact: Message

MFT-05442: Invalid Export type {0}.

Cause: Export type is not the supported one.

Action: Send the request again after changing the export type.

Level: High

Type: ERROR

Impact: Message

MFT-05443: Invalid {0} file.

Cause: The archive file uploaded is invalid.

Action: Send the request again after selecting the valid archive file.

Level: High

Type: ERROR

Impact: Message

MFT-05444: Invalid RESTful resource {0}.

Cause: The resource name provided in the url is invalid.

Action: Send the request again after changing resource name path parameter.

Level: High

Type: ERROR

Impact: Message

MFT-05445: Unable to list the resources catalog of MFT RESTful services.

Cause: An exception occured while listing the resources.

Action: Review diagnostic log for detailed error message.

Level: High

Type: ERROR

Impact: Message

MFT-05501: The {0} record {1} is already persisted.

Cause: The new record you are trying to persist is already available in the database.

Action: Check the details of the record you are trying to insert and try again.

Level: CRITICAL

Type: ERROR

Impact: MESSAGE

MFT-05502: No instance record found for message ID {0}.

Cause: There was no instance record found in the database.

Action: Check the ID of the entity.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05503: Error occurred while performing persistence operation.

Cause: Exception occurred while performing the persistence operation.

Action: Review diagnostic log for detailed error message.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05504: Could not perform the persistence lock operation {0} for entity {1}.

Cause: Exception occurred while performing the persistence operation.

Action: The exception may have occurred while performing the corresponding database lock operation. Check the logs for the exception trace.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05505: Error while deleting Data Storage {0}.

Cause: Error occurred while deleting the Data Storage entity in the database.

Action: Make sure the Data Storage is not associated with any entity. Check the logs for the exception trace.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05506: Error deleting Source Message for source {0}.

Cause: Error occurred while deleting the Source Message entity in the database.

Action: Make sure the source is not associated with any transfer. Check the logs for the exception trace.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05507: Error deleting transfer instance for transfer {0}.

Cause: Error occurred while deleting the transfer instance entity in the database.

Action: Check the logs for the exception trace.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05508: Error deleting Target Message {0}.

Cause: Error occurred while deleting the Target Message entity in the database.

Action: Check the logs for the exception trace.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05509: No retry info record exists in database.

Cause: Retry information not found for target.

Action: Resubmit the message again.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05510: No source lifecycle record exists for source name {0} and label {1} in database.

Cause: No record found.

Action: Redeploy the source and resubmit the message.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05511: No source record found for message ID {0}.

Cause: There was no source record found in the database.

Action: Check the ID of the entity.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05512: No transfer instance record found for message ID {0}.

Cause: There was no transfer instance record found in the database.

Action: Check the ID of the entity.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05513: No target message record found for ID {0}.

Cause: There was no transfer message record found in the database.

Action: Check the ID of the entity.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05514: Source {0} is not deployed.

Cause: Source is not deployed.

Action: Deploy the source and retry.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05515: Transfer {0} is not deployed.

Cause: Transfer is not deployed.

Action: Deploy the transfer and retry.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05516: Target {0} is not deployed.

Cause: Target is not deployed.

Action: Deploy the target and retry.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05517: Error deleting source {0}.

Cause: Error occurred while deleting the source in the database.

Action: Check the logs for the exception trace.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05518: Error deleting transfer {0}.

Cause: Error occurred while deleting the transfer in the database.

Action: Check the logs for the exception trace.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05519: Error deleting target {0}.

Cause: Error occurred while deleting the target in the database.

Action: Check the logs for the exception trace.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05520: Error fetching sources with label {0}.

Cause: Error occurred while fetching sources with this label from the database.

Action: Check the logs for the exception trace.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05521: Error fetching transfers with label {0}.

Cause: Error occurred while fetching transfers with this label from the database.

Action: Check the logs for the exception trace.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05522: Error fetching targets with label {0}.

Cause: Error occurred while fetching targets with this label from the database.

Action: Check the logs for the exception trace.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05523: Batch id [{0}] provided by user for purge recovery does not exist.

Cause: Batch id [{0}] provided by user for purge recovery does not exist.

Action: Check the passed batch id and try again. You can start a new purge also by passing the batch id as blank. Contact Oracle Support if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05524: Batch id [{0}] provided by user, for filesystem purge, does not exist.

Cause: Batch id [{0}] provided by user, for filesystem purge, does not exist.

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05525: Filesystem purge is already run successfully for the provided batch id [{0}].

Cause: Filesystem purge is already run successfully for the provided batch id [{0}].

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05526: Filesystem purge can not be run without a valid Root Directory configured.

Cause: No Root directory configured in the Application Settings.

Action: Check the Root Directory under Hosted Server properties. Contact Oracle Support if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05527: Runtime Purge is not yet executed for the batch id [{0}]. FS Purge can not be run without first running the Runtime Purge.

Cause: Runtime Purge is not yet executed for the batch id. FS Purge can not be run without first running the Runtime Purge.

Action: Check the Root Directory under Hosted Server properties. Contact Oracle Support if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05528: Filesystem archive is already run successfully for the provided batch id [{0}].

Cause: Filesystem archive is already run successfully for the provided batch id [{0}].

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05529: Batch id [{0}] provided by user, for filesystem archive, does not exist.

Cause: Batch id [{0}] provided by user, for filesystem archive, does not exist.

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05530: Filesystem archive can not be run without a valid Root Directory configured.

Cause: No Root directory configured in the Application Settings.

Action: Check the Root Directory under Hosted Server properties. Contact Oracle Support if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05531: Error while creating the archive file {0}. Error Message: {1}

Cause: Error while creating the archive file.

Action: Check the Root Directory under Hosted Server properties. Contact Oracle Support if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05532: Filesystem Archive operation started for the provided batch id [{0}] but not complete. Filesystem purge can not continue.

Cause: Filesystem Archive operation started for the provided batch id but not complete. Filesystem purge can not continue.

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05533: Error while adding payload {0} to the archive file. Error Message: {1}

Cause: Filesystem error while adding payload file to the archive.

Action: Check the payload file path, permissions and try again. Contact Oracle Support if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05534: Error while working with archive file {0}. Error Message: {1}

Cause: Filesystem error while working with archive file.

Action: Check the archive file path, permissions and try again. Contact Oracle Support if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05535: Error while working with archive file {0} for restore. Error Message: {1}

Cause: Filesystem error while working with archive file.

Action: Check the archive file path, permissions and try again. Contact Oracle Support if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05536: No Schedule Purge record found for schedule name [{0}].

Cause: There was no Schedule Purge record found in the database.

Action: Check the Name of the Schedule Purge. Please review the diagnostic logs for specified schedule purge

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05537: Error occurred while performing persistence operation.

Cause: Exception occurred while performing the persistence operation.

Action: Review diagnostic log for detailed error message.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05802: Exception occurred while querying for ESS job definition [{0}].

Cause: Unexpected exception occurred while querying for the ESS job definition [{0}].

Action: Ensure that the MFT Custom Hosting App is properly deployed. For further details, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05803: NOT_IN_USE

Cause: NOT_IN_USE

Action: NOT_IN_USE

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05804: NOT_IN_USE

Cause: NOT_IN_USE

Action: NOT_IN_USE

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05805: NOT_IN_USE

Cause: NOT_IN_USE

Action: NOT_IN_USE

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05806: Exception occurred while looking up JNDI context.

Cause: Unexpected exception occurred while looking up the JNDI context.

Action: Check the JNDI configuration for ESS on your application server.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05807: Exception occurred while looking up EJB [{0}].

Cause: Could not look up ESS EJB [{0}].

Action: Ensure that the MFT custom hosting app (MFTCustomHostingApp) is installed properly.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05808: Unexpected error occurred while submitting an ESS job with details: job type [{0}], schedule name [{1}], job description [{2}], schedule time [{3}].

Cause: Unexpected error occurred while submitting an ESS job.

Action: Check the schedule details and deploy again. Also verify that ESS environment is up and running.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05809: {0}

Cause: Validation failed for schedule.

Action: Check your schedule details. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05810: Exception occurred while looking for schedule with name [{0}].

Cause: Unexpected exception occurred while looking for schedule with name [{0}].

Action: Ensure that the schedule is attached to the artifact and try deploy again. For further details, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05811: Could not find schedule with name [{0}].

Cause: Could not find a schedule with name [{0}].

Action: Ensure that the schedule is attached with artifact and try deploy again. For further details, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05812: Exception occurred while opening ESS runtime service. Event: [{0}].

Cause: Could not open ESS runtime service.

Action: Check that ESS environment is up and running.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05813: Exception occurred while opening ESS metadata service. Event: [{0}].

Cause: Could not open ESS metadata service

Action: Check that ESS environment is up and running.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05814: Exception occurred while closing ESS runtime service. Event: [{0}].

Cause: Could not close ESS runtime service.

Action: Check that ESS environment is up and running.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05815: Exception occurred while closing ESS runtime service. Event: [{0}].

Cause: Could not close ESS metadata service.

Action: Check that ESS environment is up and running.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05816: Could not find ESS job with id [{0}] while cancelling.

Cause: Could not find the ESS job while cancelling.

Action: Ignore this exception. A new job has been submitted as part of a new deployment.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05817: Exception occurred while cancelling the ESS job with ID [{0}].

Cause: Illegal Job State Found. Cannot be cancelled.

Action: Try again or contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05818: Could not find ESS job request with ID [{0}]. Event [{0}].

Cause: Could not find ESS job request with id [{0}].

Action: Check that the artifact is deployed and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05819: Unexpected error occurred for job request ID [{0}]. Event [{1}].

Cause: Unexpected error occurred for job request ID [{0}].

Action: Check that the artifact is deployed and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05820: NOT_IN_USE

Cause: NOT_IN_USE

Action: NOT_IN_USE

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05821: Exception occurred while looking up EJB [{0}].

Cause: Could not look up ESS EJB [{0}].

Action: Ensure that the MFT custom hosting app (MFTCustomHostingApp) is installed properly. For further details, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05822: Error occurred for schedule name [{1}]. Event: [{0}].

Cause: Error occurred for schedule name [{1}]. Event: [{0}].

Action: Check the schedule details and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05823: Validation failed for schedule name [{1}]. Event [{0}].

Cause: Validation failed for schedule name [{1}]. Event: [{0}].

Action: Check the schedule details and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05824: Schedule already exists with name [{1}]. Event: [{0}].

Cause: Schedule already exists with name [{1}]. Event: [{0}].

Action: Check the schedule details and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05825: Null schedule passed for event [{0}].

Cause: Null schedule passed for event [{0}].

Action: Check the schedule details and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05826: ID in schedule found null for event [{0}].

Cause: ID in schedule found null for event [{0}].

Action: Check the schedule details and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05827: Exception occurred for schedule [{1}]. Event: [{0}].

Cause: Unexpected exception occurred for schedule.

Action: Check the schedule details and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05828: Validation failed for schedule [{1}]. Event: [{0}].

Cause: Validation failed for schedule [{1}]. Event: [{0}].

Action: Check the schedule details and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05829: Schedule object found null for event [{0}].

Cause: Schedule object found null.

Action: Check the schedule details and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05830: Passed schedule name is null for event [{0}].

Cause: Passed schedule name is null.

Action: Check the schedule details and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05831: No schedule found with given name [{0}].

Cause: No schedule found with given name.

Action: Check the schedule details and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05832: Unexpected error occurred while querying for schedule with name [{0}].

Cause: Unexpected error occurred while querying for schedule.

Action: Check the schedule details and try again. Also verify that ESS environment is up and running.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05833: Schedule name passed as NULL while deleting schedule.

Cause: Schedule name passed as NULL while deleting schedule.

Action: Check the schedule details and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05834: Unexpected error occurred while deleting schedule with name [{0}].

Cause: Unexpected error occurred while deleting schedule.

Action: Check the schedule details and try again. Also verify that ESS environment is up and running.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05835: Trying to deactivate a non-active Schedule Purge [{0}].

Cause: Trying to access a non-active schedule purge.

Action: Scheduled purge is not active, Please active it first.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05836: Error occurred while deleting an active schedule purge [{0}] with ESS Job ID[{1}]..

Cause: Trying to delete an active schedule purge.

Action: An active schedule purge can't be deleted. Deactivate it and then try to delete it.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05837: Trying to activate an active Schedule Purge [{0}].

Cause: Trying to activate an active Schedule Purge [{0}].

Action: Scheduled purge is active, Please deactive it first.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05838: Trying to modify an active Schedule Purge [{0}].

Cause: Trying to modify an active Schedule Purge [{0}].

Action: An active schedule purge can't be modified. Deactivate it and then try to modify it.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05839: Error occurred while creating ESS schedule for purge schedule [{0}].

Cause: Error occurred while creating ESS schedule for purge schedule [{0}].

Action: Check the purge schedule details and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05840: Error occurred while updating ESS schedule[{1}] for purge schedule [{0}].

Cause: Error occurred while updating ESS schedule[{1}] for purge schedule [{0}].

Action: Check the purge schedule details and try again.

Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05841: Could not find job definition with name [{0}].

Cause: Could not find job definition with name [{0}].

Action: Ensure that the MFT Custom Hosting App is deployed. For further details, contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05842: Exception occurred while checking if schedule with name [{0}] is in use.

Cause: Unexpected exception occurred while checking if schedule with name [{0}] is in use.

Action: Check the database connection.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05843: Could not find ESS job with id [{0}] while doing operation {1}.

Cause: Could not find the ESS job while doing a specified operation.

Action: Ignore this exception. Job has been cancelled already as part of deployment cleanup.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05844: Exception occurred while doing the operation {1} with ESS job ID [{0}].

Cause: Illegal Job State Found. Cannot do the specified operation.

Action: Try again or contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05845: Operation {1} with ESS job ID [{0}] is not allowed.

Cause: Specified operation is not allowed on the given job.

Action: Try again or contact Oracle Support Services.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05846: {0}

Cause: Exception occurred while interacting with ESS

Action: Check your ESS environment and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05847: {0}

Cause: Exception occurred while invoking the ESS through security interceptor.

Action: Check your ESS environment and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06001: Error while initializing security for stripe {0}.

Cause: An error occurred while defining the required policy for the application stripe.

Action: Check whether the application has all the required permissions in the EM and policy store connection properties. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06002: An error occurred while performing the security operation.

Cause: An error occurred while executing the security operation on the specified application stripe.

Action: Check the security store configuration in the WebLogic console or jps-config.xml and default permissions of MFT in the policy store. Review the diagnostic log for the exact error.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06003: Error while initializing the identity store for default realm.

Cause: An error occurred while initializing identity store with default security realm.

Action: Check the security store configuration in the WebLogic console or jps-config.xml and default permissions of MFT in the policy store. Review the diagnostic log for the exact error.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06005: Illegal MFTESPermission resource name {0}.

Cause: The resource name is not in the expected MFT ES Permission format.

Action: Correct the resource name parameter using the format 'resourceName={ResourceName},includeSubfolders=true|false,,serverType=FTP|SFTP'.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06006: Error while performing the SSH Key store operations on key type:{0} and alias {1}.

Cause: An error occurred while getting the SSH key store keys or aliases from the specified location.

Action: Check the key store location in the metadata repository and ensure that the required keys are present in the specified location. Review the diagnostic log for the exact error, and Contact Oracle Support Services if the problem persists.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06007: Secured Method {0} is not annotated with required parameters.

Cause: An error occurred while checking the access provisioning before executing the method.

Action: Annotate the method with the required parameters.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06008: Error while performing the credential operation {0} for alias {1}.

Cause: An error occurred while performing the credential operation.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06009: Error while performing the key store operation {0}.

Cause: An error occurred while performing the key store operation.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06010: An error occurred while performing the security operation on stripe {0}, store {1} and alias {2}.

Cause: An error occurred while executing the security operation on the specified application stripe.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06011: Invalid key file location [{0}]. The given path does not exist.

Cause: The given key file location does not exist or the key file is an empty file.

Action: Provide the correct path for export and while importing make sure that valid non empty key file exists at the given path.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06012: The imported key file {0} has multiple key rings. Importing multiple key rings is not supported.

Cause: The key file being imported has more than one PGP key.

Action: Import a valid key file that has only one key ring.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06013: Unable to get the resource type {0} while granting the permission for resource {1}.

Cause: Internal resource type definition might have failed, there is no associated resource type defined in the policy store.

Action: Resource type should be predefined before granting the permission by the security layer. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06014: Unable to get the Principal of user/group {0} with type {1}.

Cause: The principal type specified for permission grant is invalid.

Action: Grant the permission with the valid principal type which can be a User or Group or Application Role.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06015: Error while granting the permission {2} to resource {0} for principal(s){1}.

Cause: An exception occurred while granting the permission for a resource.

Action: Check the parameters used for granting the permission. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06016: Error while getting principals and actions of resource {0} with type {1}.

Cause: An exception occurred while getting the principals and actions of a resource.

Action: Check the resource name for validity. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06017: Error while revoking the permission {2} of a resource{0} for principal(s){1}.

Cause: An exception occurred while deleting the permissions of a resource.

Action: Check the revoke parameters. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06018: Authorization failure for principal(s) {0} to resource {1} for action {2}.

Cause: Access control exception occurred for a user while doing an operation.

Action: If this error encountered even if the operation was allowed for the user, then check the permissions of the user. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06019: Unable to create the MFT OPSS resource type {0}.

Cause: An error occurred while defining the resource type.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06020: Unable to create the Principal object for principal name {0} and type {1}.

Cause: An error occurred while creating the principal object.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06021: Unable to get the members of the role {0}.

Cause: An error occurred while fetching the members of a role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06022: Error while fetching all the application roles of application stripe {0}.

Cause: An error occurred while fetching the all the application roles.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06023: Error while fetching all the application roles of principal {0} with type {1}.

Cause: An error occurred while fetching the all the application roles of a principal.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06024: Error while fetching the granted resources of a principal {0}.

Cause: An error occurred while fetching the resources of a principal.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06025: Error while deleting all the grants of a resource {0} with type {1}.

Cause: An error occurred while deleting all the grants of a resource.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06026: Error while creating an application role with name {0}.

Cause: An error occurred while creating an application role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06027: Error while deleting the application role with name {0}.

Cause: An error occurred while deleting an application role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06028: Error while adding the member(s) {0} to application role {1}.

Cause: An error occurred while adding members to an application role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06029: Error while removing the member(s) {0} from application role {1}.

Cause: An error occurred while removing members of an application role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06030: Unable to authenticate the user {0}.

Cause: An error occurred while authenticating the user.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06031: Unable to get the enterprise groups of the user {0}.

Cause: An error occurred while getting the enterprise groups of the user.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06032: Error while retrieving the list of users/groups from identity store with criteria {0}.

Cause: An error occurred while fetching the users from identity store with search criteria.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06033: Invalid value [{0}] for parameter [{1}].

Cause: Parameter value supplied is incorrect.

Action: Provide the expected parameter value.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06034: The imported key file is not having valid encryption/decryption key.

Cause: The key file being imported has no valid PGP key.

Action: Import a key file that has a valid PGP key.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06035: A key already exists for the given key alias {0} in credential store.

Cause: A key is already created for the given key alias in the credential store.

Action: Import the key file again with a different key alias.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06036: Key not found for the given key alias {0} in credential store.

Cause: No key was found for the given key alias in the credential store.

Action: Check if a key for the given key alias has been generated or not in the credential store.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06037: Invalid key file [{0}]. The given key file is an empty file.

Cause: The given key file location to export CSF Key does not exist.

Action: Provide the correct path for export and while importing make sure that valid non empty key file exists at the given path.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06038: Path {0} specified on MFT embedded server for the resource is invalid.

Cause: No directory exists on MFT Embedded server specified by given path.

Action: Check if path specified is a valid directory on MFT Embedded server. If directory does not exist correct the Path input to point to existing directory OR create a new directory with the given Path.

Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-06039: Error in configuring home directory {0} for user {1}.

Cause: Error in configuring user home directory due to error accessing metadata for User/Group.

Action: Review Metadata repository configuration for MFT Embedded Server users. Try running MFT metadata export command to see if metadata repository configured properly.

Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-06040: Invalid Embedded Server types specified in the input.

Cause: Server Types specified in the input does not belong to one/more of the types FTP,SFTP.

Action: Provide server types which contains one ore more values FTP,SFTP.

Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-06041: Invalid permissions set {0} provided.

Cause: The permissions set provided contains one or more values that are not from the supported set 'READ,WRITE,DELETE,LIST'.

Action: Provide permissions that contains one or more values from supported set 'READ,WRITE,DELETE,LIST'.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-06042: Error while registering the WSM Security Policies to endpoint {0}.

Cause: An exception occurred while registering the WSM policies with WSM Policy Manager.

Action: Check the endpoint policies and WSM Manager configuration.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-06043: Error while unregistering the WSM Security Policies of endpoint {0}.

Cause: An exception occurred while unregistering the WSM policies from WSM Policy Manager.

Action: Check the endpoint policies and WSM Manager configuration.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-06044: Error while deleting the WSM assembly file of endpoint {0}.

Cause: An exception occurred while deleting the WSM assembly file from the MDS repository.

Action: Check the MDS configuration and endpoint availability.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-06045: No user found by name [{0}].

Cause: No user found.

Action: Specify the valid user name and retry the action.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-06046: No user group found by name [{0}].

Cause: No user group found.

Action: Specify the valid user group name and retry the action.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-07001: Error while creating audit record for the event {0}.

Cause: Error while creating audit record for the event .

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07002: Error while initializing audit framework.

Cause: Error initializing audit framework.

Action: Check Audit configuration in EM console. Contact Oracle Administrator.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07003: Audit enabled method {0} is not annotated with the required parameters.

Cause: An error occurred during auditing after executing a method.

Action: Annotate the method with the required parameters.

Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-07201: Error while sending notification.

Cause: Error while sending notification.

Action: Check the notification settings. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07202: Error while sending email notification.

Cause: Error while sending email notification.

Action: Check the notification settings. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07203: Error while sending sms notification.

Cause: Error while sending sms notification.

Action: Check the notification settings. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07204: Email settings are not configured for user [{0}].

Cause: Email settings are not configured for user.

Action: Configure the email settings for user in the user store and retry the action.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-07205: SMS settings are not configured for user [{0}].

Cause: SMS settings are not configured for user.

Action: Configure the SMS settings for user in the user store and retry the action.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-07206: Delivery channel [{0}] is not supported for notification. Only SMS/Email delivery channel is only supported.

Cause: Delivery channel is not supported.

Action: Change the delivery channel to Email/SMS and retry the action.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-07207: Delivery channel information is required.

Cause: Delivery channel cannot be null.

Action: Specify delivery channel and retry the action.

Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-07208: Notification template file[{0}] doesn''t exists.

Cause: Template file not exists.

Action: Specify the correct template file location and retry the action.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07209: Invalid notification template [{0}], no notification message subject found.

Cause: No notification message subject found.

Action: Correct the template file to add the message subject and retry the action.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07210: Invalid notification template [{0}], no notification message body found.

Cause: No notification message body found.

Action: Correct the template file to add the message body and retry the action.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07401: Callout with name: {0} exists in the Metadata Store. Not creating a new one.

Cause: An existing callout with same name was found in the Metadata Store.

Action: Change the callout name and try again. Refer to the MFT utilities documentation to determine the arguments and their types for the given command.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07402: Exception while creating Callout.

Cause: EJBException thrown by utility while creating callout.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07403: Callout definition XML input file [{0}] not found.

Cause: Callout definition XML input file not found. The given file name or file path is incorrect.

Action: Provide provide a valid file path and try again.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07404: Callout definition XML File validation failed. Correct the errors and rerun the utility.

Cause: Callout definition XML File validation failed. Correct the errors and rerun the utility.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07405: Invalid Notification event type: {0}.

Cause: Invalid notification event type.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07406: Contact Information not found. Type: {0} Value: {1}.

Cause: Contact not found. Add the contact to the system and rerun the utility.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07407: An Exception occurred while running MFT utility. {0}

Cause: An Exception occurred while running the MFT utility.

Action: Refer to the MFT utilities documentation to determine arguments and their types for the given command to make sure correct values are passed to the given method.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07408: Contact already exists. Type: {0} # Value: {1}.

Cause: A contact of the given type and value already exists in the system.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07409: Error while creating contact of type: {0} and value: {1}.

Cause: An error occurred while creating a new contact of the given type and value.

Action: Refer to the MFT utilities help to determine the arguments and their types for the given command to make sure correct values are passed to the given method.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07410: Error while deleting callout: {0}.

Cause: An error occurred while deleting the given callout.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07411: Error occurred while listing all the callouts in the system.

Cause: An error occurred while listing all the callouts in the system.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07412: Error while adding a contact to notification event. Event: {0} # Contact type: {1} # Value: {2}.

Cause: An error occurred while adding a contact to the notification event.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07413: Error while removing a contact from a notification event. Error Message: {0}.

Cause: An Error while removing a contact from a notification event.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07414: Error while deleting a contact from the system. Error Message: {0}.

Cause: An error occurred while deleting a contact from the system.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07415: Unsupported artifact type found. Artifact type: {0}.

Cause: Unsupported artifact type found. Supported values are SOURCE, TARGET and TRANSFER.

Action: Contact the Oracle Administrator.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07416: Exception while getting the id for source artifact [{0}].

Cause: Exception occurred while getting the source id from metadata store for the given name.

Action: Contact the Oracle Administrator.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07417: Cannot delete the contact. Given contact is associated with a notification event. Contact type: {0} :: Value: {1}.

Cause: Given contact is associated with a notification event. First remove the contact from the event and then try deleting the contact again.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07418: Error while listing contacts from the system. Contact type: {0}.

Cause: Error while listing the contacts of the given type. Try again.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07419: Callout with name: {0} not found in MDS. No changes done.

Cause: An existing callout with the given name was not found in the Metadata Store.

Action: Provide a different and correct callout name and try again. Refer to the MFT utilities documentation to determine the arguments and their types for the given command.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07420: Invalid value supplied for group name. Callout definition for {0} not changed.

Cause: Incorrect value provided for group name.

Action: Valid values for group name can contain any combination of comma-separated values of following: Source-pre,Source-post,Target-pre,Target-post. Refer to the MFT utilities documentation to determine the arguments and their types for the given command.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07421: Error while modifying callout {0}. Error Message: {1}.

Cause: An Error occurred while modifying the callout definition.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07422: Error while creating {0} keys. Error Message: {1}.

Cause: An Error occurred while creating sample keys.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07423: Exception while getting the id for target artifact [{0}].

Cause: Exception occurred while getting the target id from metadata store for the given name.

Action: Contact the Oracle Administrator.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07424: Exception while getting the id for transfer artifact [{0}].

Cause: Exception occurred while getting the transfer id from metadata store for the given name.

Action: Contact the Oracle Administrator.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07425: Exception while getting the name for transfer artifact id [{0}].

Cause: Exception occurred while getting the transfer id from metadata store for the given name.

Action: Contact the Oracle Administrator.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07426: Exception while getting the name for target artifact id [{0}].

Cause: Exception occurred while getting the target id from metadata store for the given name.

Action: Contact the Oracle Administrator.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07427: Exception while getting the name for source artifact id [{0}].

Cause: Exception occurred while getting the source id from metadata store for the given name.

Action: Contact the Oracle Administrator.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07428: Error while retrieving deployment history for transfer [{0}].

Cause: Exception occurred while retrieving deployment history information for the given transfer.

Action: Check the transfer deployment details in UI. Deploy the transfer from UI or WLST and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07429: Error while retrieving deployment history for target [{0}].

Cause: Exception occurred while retrieving deployment history information for the given target.

Action: Check the target deployment details in UI. Deploy the target from UI or WLST and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07430: Error while retrieving deployment history for source [{0}].

Cause: Exception occurred while retrieving deployment history information for the given source.

Action: Check the source deployment details in UI. Deploy the source from UI or WLST and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07431: Error while retrieving deployment history for transfer [{0}].

Cause: Exception occurred while retrieving deployment history information for the transfer source.

Action: Check the transfer deployment details in UI. Deploy the transfer from UI or WLST and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07432: Exception occurred while checking if transfer [{0}] exists in metadata store.

Cause: Exception occurred while checking if the given transfer exists in metadata store.

Action: Restore the deleted transfer artifact in metadata store and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07433: Exception occurred while checking if target [{0}] exists in metadata store.

Cause: Exception occurred while checking if the given target exists in metadata store.

Action: Restore the deleted target artifact in metadata store and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07434: Exception occurred while checking if source [{0}] exists in metadata store.

Cause: Exception occurred while checking if the given source exists in metadata store.

Action: Restore the deleted source artifact in metadata store and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07435: Could not parse xml [{0}]

Cause: Exception occurred while parsing xml

Action: Check / Validate the xml against given xsd and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07436: File [{0}] doesn''t exist or is a directory.

Cause: File doesn't exist or is a directory

Action: Ensure that file exists and try again. File should exist on machine where server is running.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07437: Exception while creating mds session.

Cause: Could not create mds session

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07438: Exception while creating mds artifact.

Cause: Could not create mds artifact.

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07439: Exception while querying mds artifact id using artifact name [{0}]

Cause: Could not query mds artifact id.

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07440: Exception while fetching mds artifact using artifact id [{0}].

Cause: Could not fetch mds artifact by id.

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07441: Exception while saving mds artifact.

Cause: Could not save mds artifact.

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07442: Exception while fetching processing functions.

Cause: Could not fetch processing functions from mds

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07443: Parameter not found with name [{0}] for function [{1}].

Cause: Could not find parameter with name [{0}] for function [{1}]

Action: Check the parameter name and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07444: Function not found with name [{0}].

Cause: Could not find function with name [{0}]

Action: Check the function name and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07445: Domain not found with name [{0}].

Cause: Could not find domain with name [{0}]

Action: Check the domain name and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07446: Exception while fetching domain MO from domain name {0}.

Cause: Could not fetch domain info from mds

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07447: Artifact with name [{0}] already exists.

Cause: Artifact with given name already exists.

Action: Try with a new name or pass updateIfExists as true.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07448: Could not parse date {0}.

Cause: Could not parse date.

Action: Correct the date format and try again. It should be 'MM/dd/yyyy H:m:s'

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07449: Could not parse given month of year {0} for schedule {1}.

Cause: Could not parse month of year given with schedule definition.

Action: Check the passed month of year and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07450: Could not parse given day of month {0} for schedule {1}.

Cause: Could not parse day of month given with schedule definition.

Action: Check the passed day of month and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07451: Could not parse given week of month {0} for schedule {1}.

Cause: Could not parse week of month given with schedule definition.

Action: Check the passed week of month and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07452: Could not parse given day of week {0} for schedule {1}.

Cause: Could not parse day of week given with schedule definition.

Action: Check the passed day of week and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07453: Could not initiate mds storage provider while attaching policy with artifact {0}.

Cause: Could not initiate mds storage provider.

Action: Check the mds settings and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07454: Error occurred while attaching OWSM policies for artifact {0}.

Cause: Error occurred while attaching OWSM policies.

Action: Check the policy details, ensure policy name is valid and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07455: Could not create empty assembly.

Cause: Could not create empty assembly.

Action: Review the diagnostic log for the exact error. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07456: Could not fetch domain from MDS store.

Cause: Could not fetch domain from MDS store.

Action: Check the mds settings and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07457: User is not authorize to create domain.

Cause: User is not authorize to create domain.

Action: Only Administrator can create the domain. Check the user permissions and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07458: Domain with name {0} not found.

Cause: Could not find domain with given name.

Action: Check the domain name and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07459: Error while deleting domain with name {0}.

Cause: Could not delete domain with given name.

Action: Review the diagnostic log for the exact error. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07460: Could not lookup EJB with name {0}.

Cause: Could not lookup EJB.

Action: Review the diagnostic log for the exact error. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07461: PGP encryption and decryption functions are not allowed in post processing.

Cause: PGP encryption and decryption functions are not allowed in post processing.

Action: Remove the PGP functions from post processing and try again. If required, these functions can be used as pre processing functions.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07462: Unsupported value {0} found for {1}.

Cause: Could not find given value.

Action: Check the documentation for supported values for [{1}] and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07463: Artifact not found for given name [{0}].

Cause: Could not find artifcat for given name.

Action: Check the artifact name and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07464: Callout [{0}] exists but not allowed for given artifact type.

Cause: Callout not allowed for given artifact.

Action: Check the artifact definition and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07465: Invalid processing function [{0}] found for post processing.

Cause: Processing function [{0}] is not allowed in post processing.

Action: Remove the function from post processing and try again. If required, these functions can be used as pre processing functions.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07466: Invalid action type found for source. Allowed action types are ''{1}'', ''{2}'' and ''{3}''. Value found: [{0}].

Cause: Invalid action type found for source.

Action: Check the action type and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07467: Invalid action type found for target. Allowed action types are ''{1}'', ''{2}'' and ''{3}''. Value found: [{0}].

Cause: Invalid action type found for target.

Action: Check the action type and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07468: One of property ['Physical Target Directory' / 'Moved To Folder' / 'File Naming Convention'] found null.

Cause: Required property found null.

Action: Check the properties and try again.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07469: Creating external contacts isn't allowed.

Cause: Creating external contacts is disabled.

Action: Creating external contacts is disabled so create internal user/group contact instead otherwise contact your administrator.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07470: Contact[{1}] is already associated with event[{0}].

Cause: Contact is already associated with the notification event.

Action: Check the contact details.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07471: Polling/Event options are not enabled for the source {0}.

Cause: Either One of Polling/Event options should be enabled.

Action: Enable one of the option and try again.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07472: Schedule definition is missing for source {0}.

Cause: Polling along with Event can be enabled only when schedule(s) are defined.

Action: Add schedule and try again.

Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07473: Unsupported action[{0}].

Cause: Unsupported action for schedule purge found. Supported values are ACTIVATE and DEACTIVATE.

Action: Contact the Oracle Administrator.

Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07474: Could not parse given date[{0}] in format[{1}].

Cause: Provided date in not in valid format.

Action: Check the input date and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07475: Could not parse given time[{0}] in format[{1}].

Cause: Provided time is not in valid format.

Action: Check the input time and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07476: Invalid Target artifact {0}. Only one among Append/Overwrite/CreateOnly attributes can be true.

Cause: Provided target artifact is not in valid format.

Action: Correct the target attributes and try again. Contact Oracle Support Services if the problem persists.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-08001: Error while reading metadata archive {0}. Error Message: {1}

Cause: An Error occurred while reading the metadata archive file.

Action: Refer to the plugin logs for more details.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-08002: Error while closing metadata archive {0}. Error Message: {1}

Cause: An Error occurred while closing the metadata archive file.

Action: Refer to the plugin logs for more details.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-08003: Error while processing metadata file {0}. Error Message: {1}

Cause: An Error occurred while either reading or parsing the metadata xml file.

Action: Refer to the plugin logs for more details.

Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-08500: Unsupported REST operation.

Cause: This REST operation is not supported.

Action: Check the input and try again. Contact Oracle Support Services if the problem persists.

Level: HIGH

Type: ERROR

Impact: SYSTEM