Skip Headers
Oracle® Fusion Middleware Error Messages Reference
11g Release 1 (11.1.1.7.0)

Part Number E10113-10
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 ADF-MNC-10000 to ADF-MNC-50073

ADF-MNC-10000: Cannot find schema resource at {0}.
Cause: Schema file is missing.
Action: Place Schema file in the required location.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10001: Problem registering schema {0}, exception = {1}.
Cause: Schema file is invalid.
Action: Fix Schema file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10002: Cannot instantiate rendering class {0} for platform {1}, exception = {2}.
Cause: Exception occurred during creation of rendering kit.
Action: Check ADF Mobile Client configuration file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10003: {0} attribute is missing for one of the platforms in {1}.
Cause: Required attribute missing in configuration file.
Action: Check ADF Mobile Client configuration file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10004: Duplicate platform with id = {0}, display value = {1} found in {2}.
Cause: Duplicate Platform Id specified in configuration file.
Action: Check ADF Mobile Client configuration file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10005: {0} element is missing in {1}.
Cause: Required element missing in configuration file.
Action: Check ADF Mobile Client configuration file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10006: Missing or invalid width/height attribute found for one of the form factors in {0}, exception = {1}.
Cause: Width/Height attribute is missing or invalid in the configuration file.
Action: Check ADF Mobile Client configuration file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10007: Form factor element has negative width/height attribute defined in {0}, width = {1}, height = {2}.
Cause: Width/Height attribute has negative value in configuration file.
Action: Check ADF Mobile Client configuration file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10008: Missing or invalid idref attribute found for {0} in {1}, idref = {2}.
Cause: idref missing or invalid in configuration file.
Action: Check ADF Mobile Client configuration file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10009: Rendering kit factory class is not specified for id = {0} in {1}.
Cause: Missing rendering kit factory class in configuration file.
Action: Check ADF Mobile Client configuration file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10010: Platform {0} does not have a rendering kit mapping defined in {1}.
Cause: Rendering kit mapping missing in configuration file.
Action: Check ADF Mobile Client configuration file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10011: Problem opening configuration file {0}, exception = {1}.
Cause: Exception opening configuration file.
Action: Check ADF Mobile Client configuration file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10012: Image repository is not specified for {0}.
Cause: Missing image repository in configuration file.
Action: Check ADF Mobile Client configuration file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10013: Invalid configuration file for control {0}. The control will be loaded using default configuration.
Cause: Exception loading control configuration file.
Action: Check control configuration file in image repository.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10014: Invalid {0} attribute found for control id = {1}.
Cause: Invalid attribute in mcx file.
Action: Check mcx file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10015: Unable to resolve EL = {0}.
Cause: Exception occurred while resolving EL expression.
Action: Check EL expression in mcx file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10016: Missing or invalid group/index/weight attribute found for one of the default menu items in {0}, exception = {1}.
Cause: Group/Index/Weight attribute is missing or invalid in the configuration file.
Action: Check ADF Mobile Client configuration file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10017: Invalid group/index attribute found for one of the default menu items in {0}, group = {1}, index={2}.
Cause: Group/Index attribute is not in the valid range of 0 to 65535.
Action: Check ADF Mobile Client configuration file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10018: Invalid weight attribute found for one of the default menu items in {0}, weight = {1}.
Cause: Weight attribute has negative value in configuration file.
Action: Check ADF Mobile Client configuration file.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10019: An error occurred when attempting to read or write a record in table REPLAY_TYPE with TYPE_NAME value "{0}"
Cause: A database error occurred.
Action: Ensure that the required database is accessible and is configured properly for Transaction Replay Service. If necessary, run the TRS configuration wizard to reconfigure TRS for the mobile application.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10020: Failed to find record in table REPLAY_TYPE with TYPE_NAME value "{0}" when it is expected to exist. Run the TRS configuration wizard to reconfigure TRS for your mobile application.
Cause: The specified database record does not exist in table REPLAY_TYPE when it is expected to exist.
Action: Run the TRS configuration wizard to reconfigure TRS for your mobile application.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10021: Failed to update a record in database table REPLAY_TYPE. The database record has Type Name "{0}"
Cause:
Action:

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10022: Type Name "{0}" conflicts with an existing record in database table REPLAY_TYPE. Each type name must be unique. Specify a different type name.
Cause:
Action:

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10023: A database access error occurred.
Cause:
Action:

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10024: The chosen database connection "{0}" is not valid. Run the Transaction Replay Service configuration wizard to choose a valid database connection that identifies where the ADFmc Transaction Replay Schema is deployed.
Cause: Cannot find or validate the selected database connection indicated in the message.
Action: Run the Transaction Replay Service configuration wizard for the mobile application to choose a valid database connection.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10025: The chosen database connection is not valid. Connection Name: "{0}", Connection Store Name: "{1}"
Cause:
Action:

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10026: The chosen database connection is corrupt. Connection Name: "{0}", Connection Store Name: "{1}". Run the TRS Configuration Wizard.
Cause:
Action:

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10027: Cannot update file adf-config.xml to configure Transaction Replay Service for mobile application.
Cause:
Action:

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10027: TRS configuration has been corrupted. To fix it, run the Transaction Replay Service configuration wizard to configure your mobile application to use Transaction Replay Service.
Cause: Corrupt internal metadata has been detected in the project .JPR file for the Transaction Replay Service configuration wizard.
Action: Run the Transaction Replay Service configuration wizard to configure Transaction Replay Service for your mobile application. This will fix the problem by overwriting the corrupt metadata.

Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-50000: Could not open {0}.
Cause: File is missing.
Action: Check that location and file both exist.

Level: 1

Type: ERROR

Impact: Files

ADF-MNC-50001: Corrupt COD: {0}.
Cause: The COD file is corrupt.
Action: Delete the COD file and attempt to regenerate it.

Level: 1

Type: ERROR

Impact: Files

ADF-MNC-50002: Error: The specified module was rejected by the device and cannot be loaded.
Cause: The file is corrupt.
Action: Delete the file and attempt to regenerate it.

Level: 1

Type: ERROR

Impact: Files

ADF-MNC-50003: Unknown Error: Examine logging information for additional details
Cause: An unknown error occurred.
Action: Examine logging information for additional details.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50004: BlackBerry JDE directory not specified. Set this in JDeveloper Preferences on the Mobile Client panel.
Cause: BlackBerry JDE directory not specified.
Action: Set the BlackBerry JDE directory in JDeveloper Preferences on the Mobile Client panel.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50005: Could not create destination directory {0}
Cause: Location may have disk problem.
Action: Examine disk for problems or permission issues.

Level: 1

Type: ERROR

Impact: Files

ADF-MNC-50006: Could not create directory {0}
Cause: Location may have disk problem.
Action: Examine disk for problems or permission issues.

Level: 1

Type: ERROR

Impact: Files

ADF-MNC-50007: Illegal install directory (must be absolute): {0}
Cause: Illegal install directory specified. This cannot be relative.
Action: Change to legal installation directory.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50008: Illegal source path (must be absolute): {0}
Cause: Illegal source path specified. This cannot be relative.
Action: Change to legal source path.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50009: File not found: {0}
Cause: File being added to CAB cannot be found.
Action: Check packaging directory for file.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50010: Invalid argument (CPU): {0}
Cause: Specified CPU is not supported.
Action: Select a supported CPU value.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50011: Mobile server connection not specified.
Cause: No mobile server connection has been specified.
Action: Select a mobile server connection.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50012: Cannot find connection {0} in {1}.
Cause: Specified connection cannot be found.
Action: Select a different connection.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50013: Mobile Client application failed to deploy to BlackBerry device.
Cause: Device or device connection may not be working.
Action: Examine device and device connection. Consider restarting device.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50014: General failure deploying package to device.
Cause: Device or device connection may not be working.
Action: Examine device and device connection. Consider restarting device.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50015: Connection timeout attempting to deploy package to device.
Cause: Device or device connection may not be working.
Action: Examine device and device connection. Consider restarting device.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50016: Error attempting to deploy package to device: {0} not found.
Cause: Application CAB not found after packaging.
Action: Check packaging directory for file.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50017: Error attempting to deploy package to device: {0} found on device, but overwrite flag not set.
Cause: Application CAB already exists on device.
Action: Delete CAB from device.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50018: Error attempting to deploy package to device: Could not write {0} to device.
Cause: Device storage might be full.
Action: Check device storage for available space and permissions.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50019: Error attempting to deploy package to device: Could not execute {0} on device.
Cause: User might not have permissions.
Action: Check user permissions on device.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50020: Error attempting to deploy package to device: Could not create directory {0} on device.
Cause: User might not have permissions.
Action: Check user permissions on device.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50021: Error attempting to deploy package to device: Unknown error code ({0}).
Cause: An unknown error occurred.
Action: Examine logging information for additional details.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50022: Mobile Client Runtime failed to deploy to BlackBerry device.
Cause: There was a problem deploying the ADF Mobile Client Runtime library to the BlackBerry device.
Action: Examine logging information for additional details.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50023: Failed to deploy application debug files to BlackBerry simulator directory.
Cause: JDeveloper could not deploy application debug files to BlackBerry simulator directory.
Action: Make sure you have write privileges for BlackBerry simulator directory.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50024: Exception caught: {0}
Cause: Exception caught while updating root-task-flow in adf-config.xml.
Action: Check adf-config.xml for write permissions.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50025: File exists: {0}
Cause: File exists in destination location preventing copy operation.
Action: Delete file.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50026: BlackBerry JDE directory specified refers to a location that does not exist. Set this in JDeveloper Preferences on the Mobile Client panel.
Cause: BlackBerry JDE directory does not exist.
Action: Set the BlackBerry JDE directory in JDeveloper Preferences on the Mobile Client panel.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50027: Mobile Client application failed to deploy to BlackBerry simulator.
Cause: Device simulator or simulator connection may not be working.
Action: Examine device simulator and simulator connection. Consider restarting device simulator.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50028: BlackBerry simulator directory not specified. Set this in JDeveloper Preferences on the Mobile Client panel.
Cause: BlackBerry simulator directory not specified.
Action: Set the BlackBerry simulator directory in JDeveloper Preferences on the Mobile Client panel.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50029: BlackBerry simulator directory specified refers to a location that does not exist. Set this in JDeveloper Preferences on the Mobile Client panel.
Cause: BlackBerry simulator directory specified refers to a location that does not exist.
Action: Set the BlackBerry simulator directory in JDeveloper Preferences on the Mobile Client panel.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50030: Error attempting to deploy package to device: There is not enough free space on device.
Cause: There is not enough free space on device.
Action: Attempt to free up space on device by removing unnecessary applications or files.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50031: Mobile Client Runtime failed to deploy to BlackBerry simulator.
Cause: There was a problem deploying the ADF Mobile Client Runtime library to the BlackBerry simulator.
Action: Examine logging information for additional details.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50032: Mobile Client Runtime failed to deploy to BlackBerry device as the device is not connected.
Cause: BlackBerry device was not detected
Action: Connect the BlackBerry device and try the operation again.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50033: Failed to delete all old files in the Deployment Folder at {0}
Cause: Some or all old files were not deleted from the deployment folder
Action: Verify user file privileges and try the operation again.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50034: Failed to create Deployment folder: {0}
Cause: Unable to create deployment folder
Action: Verify user privileges and try the operation again.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50035: The Client Database Name must be alpha-numeric and 1 to 28 characters long.
Cause: The client database name contains invalid characters or is not the correct length.
Action: Rename the client database to contain alpha-numerical characters only and ensure its length is valid.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50036: The path of the standalone database must be between 1 and 255 characters long.
Cause: The path to the location of the standalone database is not specified or has an invalid length.
Action: Specify a valid path to the location of the database and ensure its length is valid.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50037: The path of the standalone database script must between 1 and 255 characters long.
Cause: The path to the location of the standalone database initialization script has an invalid length.
Action: Specify a valid path to the location of the script contained in the application JAR file and ensure the path has a valid length.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50038: Failed to obtain the workspace.
Cause: Context information did not contain a valid value for the workspace property.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50039: Failed to locate a project containing adf-config.xml.
Cause: The workspace either does not have a project containing the 'ADF Mobile Client UI' technology or has an invalid or missing adf-config.xml configuration file.
Action: Ensure the workspace has a 'Mobile Client View Controller Project' containing the 'ADF Mobile Client UI' technology. Also, verify that the project has a valid adf-config.xml configuration file.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50040: Failed to get the client database. Exception message: {0}
Cause: An exception occurred when attempting to obtain the client database configuration value.
Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50041: Failed to save the client database. Exception message: {0}
Cause: Failed to update adf-config.xml or failed to determine if a publication already exists for the application.
Action: Check adf-config.xml for write permissions. Verify the data publication configuration is correct and retry.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50042: Deployment failed as Preverify returned an error code.
Cause: Preverify utility failed to preverify the application jar file.
Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50043: Deployment failed as RAPC returned an error code.
Cause: RAPC utility failed.
Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50044: Application Name cannot be empty
Cause: Application name field in BlackBerry Deployment Options panel was empty.
Action: Valid application name is required to deploy the application on BlackBerry device.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50045: Application Name cannot contain any of the following characters: / ? : \ * " < > | -
Cause: BlackBerry application name contained one of the un-supported characters.
Action: Remove un-supported characters from the BlackBerry application name.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50046: Application Name cannot begin with '.'
Cause: BlackBerry application name contained period in the beginning of the name.
Action: Remove the period from the beginning of the BlackBerry application name.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50047: Application Name cannot be empty
Cause: Application name field in Windows Mobile Deployment Options panel was empty.
Action: Valid application name is required to deploy the application on Windows Mobile device.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50048: Application Name cannot contain any of the following characters: / ? : & \ * " < > | # %
Cause: Windows Mobile application name contained one of the un-supported characters.
Action: Remove un-supported characters from the Windows Mobile application name.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50049: Application Name cannot begin or end with '.'
Cause: Windows Mobile application name contained period in the beginning or ending of the name.
Action: Remove the period from the beginning and ending of the Windows Mobile application name.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50050: Application Name cannot be Windows system reserved names, including CON, AUX, PRN, COM1 or LPT2
Cause: Windows Mobile application name used one of the Windows system reserved names.
Action: Modify Windows Mobile application name not to use any Windows system reserved names as specified.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50051: Unable to locate {0}. Make sure to enter valid path.
Cause: Invalid Icon file path was entered.
Action: Verify the path entered.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50052: Selected icon file is not within the project directory. Please select the icon from within the following project directory: {0}
Cause: The icon file was selected from outside the project directory.
Action: Select the icon file from within the project directory. Copy the icon in the project if it is not there.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50053: File type is not a supported icon type. Please provide supported icon type ({0}).
Cause: Invalid Icon file type selected
Action: Select one of the supported file types only.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50054: Invalid parameter detected in method {0}. Parameter {1} is null or empty.
Cause: Internal programming error.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50055: Invalid parameter detected in method {0}. The value {1} is not allowed for a ADF setting of {2}.
Cause: Internal programming error.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50056: Failed to obtain a database provider for connection named {0}.
Cause: Unable to obtain connection information for the Oracle Mobile Server Repository.
Action: Verify the database connection definition for the Oracle Mobile Server Repository is correct and ensure the database is available.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50057: Connection with ActiveSync could not be established. Ensure that PC-to-device/emulator connectivity is working correctly. Restarting JDeveloper may restore communications. See ADF Mobile Client documentation on Troubleshooting if the problem persists.
Cause: JDeveloper could not connect to ActiveSync and initialize communication channel.
Action: Restart Windows Mobile Emulator, Windows Mobile Emulator Manager and ActiveSync. Ensure that PC-to-device/emulator connectivity is working correctly. Restarting JDeveloper may restore communications. See ADF Mobile Client documentation on Troubleshooting if the problem persists.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50058: Method {0} detected a invalid null parameter {1}.
Cause: Internal programming error.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50059: MDK is not installed or the path is not set. Publication is not created.
Cause: The location to your Oracle Database Lite installation is not configured.
Action: Specify the location to your Oracle Database Lite installation available as an ADF Mobile Client preference option.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50060: The TRS database is either not configured correctly or does not have the TRS schema installed. TRS Publication is not created.
Cause: The database may not be avaiable or does not have the TRS schema installed.
Action: Verify the database is available and has the TRS schema installed.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50061: Detected an invalid profile type.
Cause: Internal programming error.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50062: There are no entity objects defined in the application. The Synchronization Publication deployment profile cannot be edited unless there are entity objects to be synchronized in the application.
Cause: The application does not have entity objects imported from an ADF library.
Action: Import entity objects from an ADF library using the 'Business Components from ADF Library' wizard.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50063: Could not find dummy class file: {0}
Cause: ADFMC_Dummy.class file is required but was not found in the source location
Action: Check with the administrator.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50064: You have specified an application schema outside of the database where the mobile server repository schema is installed. You must run the "apprepwizard" to install the remote application repository and then specify the password in the "Remote Application Repository Credential" section.
Cause: The application schema and Oracle Mobile Server Repository schema are in different databases.
Action: Run the "apprepwizard" and specify the credential needed to access the application schema.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50065: Failed to determine if the connection {0} has the TRS Schema installed. Exception: {1}.
Cause: A database error occurred.
Action: Verify the database containing the TRS Schema is available and examine logging information for additional details.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50066: Connection {0} does not have the TRS Schema installed. Please select a different connection or install the TRS Schema and try again.
Cause: The schema does not have the TRS tables installed.
Action: Install the TRS schema.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50067: The connection, {0}, is not valid and has been reset.
Cause: The TRS connection defintiion was not valid.
Action: Verify the database containing the TRS schema is available.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50068: Failed to get the TRS configuration from the profile.
Cause: The project did not contain TRS configuration options.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50069: Failed to establish a connection to {0}. Exception: {1}.
Cause: A connection exception occurred when connecting to the database.
Action: Verify the connection configuration is correct and the database is online and available.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50070: Failed to initialize the TRS Publication panel. Exception: {0}.
Cause: The panel failed to initialize.
Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50071: Mobile server repository connection information must be entered first.
Cause: There is no connection configuration for the Oracle Mobile Server Repository schema or the connection is not valid.
Action: Verify there is a valid connection definition for the Oracle Mobile Server Repository schema.

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50072: Windows Mobile deployment tool file not found: {0}
Cause: The PPCDeployer DLL file is missing. Windows Mobile deployment requires this file.
Action: Check the location of the PPCDeployer.dll. Reinstall the ADF Mobile Client extension to restore this file

Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50073: Windows Mobile deployment tool file is corrupt, or not supported on this operating system: {0}
Cause: The PPCDeployer DLL file is present, but it cannot be loaded correctly. It is either corrupt, or being invoked on an unsupported operating system.
Action: Reinstall the ADF Mobile Client extension to restore this file. Perform this operation in a Windows operating system environment.

Level: 1

Type: ERROR

Impact: Deployment