Skip Headers
Oracle® Fusion Middleware Error Messages Reference
11
g
Release 1 (11.1.1)
E10113-02
Contents
Previous
Next
4
ADF-MNC-10000 to ADF-MNC-50025
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 one of the rendering kit mappings in {0}, idref = {1}.
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-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: BlackBerry package failed to deploy 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-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: ADF Mobile Client Runtime failed to deploy to BlackBerry.
Cause:
There was a problem deploying the ADF Mobile Client Runtime library to BlackBerry.
Action:
Examine logging information for additional details.
Level:
1
Type:
ERROR
Impact:
Deployment
ADF-MNC-50023: ADF Mobile Client Runtime failed to deploy to Windows Mobile.
Cause:
There was a problem deploying the ADF Mobile Client Runtime library to Windows Mobile.
Action:
Examine logging information for additional details.
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