2 ADF-MF-10001 to ADF-MF-16221

ADF-MF-10001: Unable to load class: {0}

Cause: Couldn't load the passed in class

Action: Please make sure correct class name is passed and the class exists in the path specified by the complete name.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10002: Unable to load class for managed property type; property name: {0}; property type: {1}

Cause: Couldn't load the passed in class

Action: Please make sure correct class name is passed and the class exists in the path specified by the complete name.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10003: Unable to resolve method: {0}

Cause: Unable to resolve method with provided parameters.

Action: Please make sure that correct method is being invoked with correct arguments.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10004: Unresolved class / method: {0} / {1}

Cause: Unable to resolve method with provided parameters.

Action: Please make sure that correct method is being invoked on correct class with correct arguments.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10005: Unable to set Managed Property: {0}; {1}

Cause: An unexpected error occurred while attempting to initialize a managed property definition.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10006: Unable to create bean instance: {0}

Cause: An unexpected error occurred while attempting to creata a managed bean instance.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10007: Process AdfException caught: {0}

Cause: There was a problem generating a response object from the request

Action: Please see the exception message for the exact problem.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10008: Process throwable caught: {0}

Cause: There was a problem generating a response object from the request

Action: Please see the exception message for the exact problem.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10009: {0} Error: {1}

Cause: Unable to invoke method with provided parameters.

Action: Please make sure that correct method is being invoked on correct class with correct arguments.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-10010: Looks like the wrong method (parameter: {0})

Cause: Internal Error. An incorrect method signature was passed in a channel request.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10011: adf message (size {0} != {1})

Cause: Internal Error. A VM Channel message size does not match its stated value in the header.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10012: Invalid Exception argument passed

Cause: Invalid Exception argument passed

Action: Invoke this method with valid exception argument.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10013: Attempting to evaluate ({0}) as a boolean.

Cause: Attempting to convert invalid value to boolean.

Action: Please pass valid value to be converted to boolean.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10014: Malformed ADF Message '{0}' of type '{1}'

Cause: Malformed Message received.

Action: Please make sure that a valid message with all the desired fields is returned.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10015: Cannot serialize the object as cyclical reference to {0} ({1}) was detected during the JSON serialization process. A possible resolution to this could be to make the {0} field transient.

Cause: Cyclical object was detected during JSON serialization process.

Action: Make sure to verify that the object being passed to serialize isn't cyclic. A possible resolution to this could be to make erroneous field transient.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10016: No getter defined for property "{0}" in class "{1}"

Cause: No getter was defined for property in the class.

Action: Make sure that the class defines the property and it's getter appropriately.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10017: The number entered is outside the range of values a Long can hold.

Cause: The number entered is outside the range of values a Long can hold.

Action: The number should be between Long.MIN_VALUE and Long.MAX_VALUE.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10018: The number entered is outside the range of values a Double can hold.

Cause: The number entered is outside the range of values a Double can hold.

Action: The number should neither be Double.NEGATIVE_INFINITY nor be Double.POSITIVE_INFINITY.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10019: Not A Number (NaN) was passed.

Cause: Invalid number was passed.

Action: The number should be valid and not equal to Double.NaN.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10020: Unable to create new array of {0} with size {1}

Cause: Failed to create an array of passed in class with passed in length.

Action: Make sure to pass correct and valid values.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10021: Unable to convert the specified String value ''{0}'' into a Date/Time/Timestamp object

Cause: The string was not in one of the standard date formats recognized by the system.

Action: Make sure the String you are trying to convert is in a valid format. Consult the Java documentation for more details on valid date/time/timestamp formats.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10022: Unable to convert the specified String value ''{0}'' into a Date/Time/Timestamp object using the specified format ''{1}''

Cause: The string could not be converted into a date according to the format specified.

Action: Make sure the String you are trying to convert matches the format you have specified.

Level: 1

Type: ERROR

Impact: Logging

Cause: The format specified is invalid.

Action: Consult the Java documentation for more details on valid date/time/timestamp formats.

ADF-MF-10023: Format exception: unknown token {0}

Cause: Unknown token was received.

Action: Make sure to have valid token array to generate a valid Calendar object.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10024: Attempting to log to null/undefined logger

Cause: Logging method was invoked with invalid logger.

Action: Please pass valid logger name or logger object.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10025: Null resource bundle class specified.

Cause: Logging method was invoked with invalid resource bundle class.

Action: Please pass valid resource bundle class.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10026: Null calling class specified.

Cause: Logging method was invoked with invalid calling class.

Action: Please pass valid calling class.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10027: Error processing UTF-8 encoded data.

Cause: The system is unable to process UTF-8 encoded data.

Action: Make sure the application contains the Java libraries necessary to process UTF-8 encoded data.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10034: Batch Validation Exception

Cause: Batched exceptions.

Action: See exceptions.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10035: Validation Exception

Cause: Validation Exception

Action: See exception.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10036: Resolution Exception

Cause: Resolution Exception

Action: See exception.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10037: Batch Adf Exception

Cause: Batch Adf Exception.

Action: See exception.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10038: Invalid Response Exception

Cause: Invalid Response Exception.

Action: See exception. Invalid response seems to be received for the request.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10039: Attempting to send {0} for request {1}

Cause: Invalid Response Exception.

Action: See exception. Invalid response seems to be received for the request.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10040: Malformed Message Exception

Cause: Malformed Message Exception.

Action: See exception. Message body is malformed. Make sure the message body is valid.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10041: Unhandled ADF Message Exception

Cause: Unhandled ADF Message Exception.

Action: See exception.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10042: Unhandled ADF Message {0} of type: {1}

Cause: Unhandled ADF Message Exception.

Action: See exception.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10043: Unknown ADF Message Exception

Cause: Unknown ADF Message Exception.

Action: See exception.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10044: Unknown ADF Message {0} of type: {1}

Cause: Unknown ADF Message Exception.

Action: See exception.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10045: Date Parse Exception

Cause: Date Parse Exception.

Action: See exception and logs. Make sure date is passed in correct expected format.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10046: Invalid exception message format. "exception" key not found.

Cause: Invalid exception message format.

Action: See exception. Exception message is not passed in expected format.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10047: Unable to convert AdfException object to JSON.

Cause: Serialization of exception object failed.

Action: Internal Error: Make sure valid exception object is passed for serialization.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10048: No setter defined for property "{0}" in class "{1}"

Cause: No setter was defined for property in the class.

Action: Make sure that the class defines the property and it's setter appropriately.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10049: AdfControlChannel.init .... failed can not continue CH = {0}

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-10050: Attribute validation failed due to unrecognized attributes: {0}

Cause: The XML element contains attributes that it is not supposed to contain.

Action: Remove unrecognized attributes from XML element.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-10051: Children validation failed due to unrecognized children: {0}

Cause: The XML element contains children that it is not supposed to contain.

Action: Remove unrecognized children from XML element.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-10052: Failed to load metadata from: {0}

Cause: Unable to read metadata from xml file.

Action: Make sure that the specfied xml file exists in the desired location and is valid.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10053: Error reading the XmlAnyDefinition at {0}

Cause: The specified resource could not be loaded as an xml document.

Action: Verify the resource is a valid xml document.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10054: Missing '{0}' value

Cause: Could not find the specified attribute.

Action: Verify that the specified attribute exists.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10055: Class '{0}' is not equal to '{1}'

Cause: Internal error. The ping response from the feature channel was invalid.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11001: Action attribute was an invalid value: {0}

Cause: Internal error. An action binding on a pagedef used an invalid value for the 'action' attribute.

Action: Examine the application log for further exception messages.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11002: Unable to load application metadata directory file: {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11003: Exception thrown from getCustomOperation (Provider Class: {0})- Exception: {1}; Message: {2}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11004: {0} - Attempt to create invoker for method: {1} returned null

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11005: Evaluated parameter to pass to invoker - value: ''{0}''

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11006: Unable to locate the data provider for this iterator

Cause: Internal error. A DataControl attempted to create an iterator accessor iterator and was unable to load the data provider.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11007: Check the implementation of {0} with {1} parameters.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11008: Check the implementation of {0} with a {1} parameter.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11009: getIteratorBinding({0}, {1}) has a problem - {2}

Cause: Internal error. An unexpected error occurred in the framework while attempting to create the named iterator.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11010: Data Control: {0} was not found.

Cause: The framework was unable to locate a declaration for the named data control.

Action: Ensure your application defines the named DataControl. If it is java bean based, simply right click on the bean class and choose 'Create Data Control'.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11011: Data Control: {0} is not a supported data control.

Cause: The framework attempted to load an unsupported DataControl type.

Action: Ensure your application only uses java bean based or web service Data controls.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11012: Attempting to set the Web Service Provider to null.

Cause: A web service data control attempted to set a null provider. This may due to a failed call.

Action: Check that the application's web service(s) have been properly configured, and that the web service(s) themselves are sending appropriate data values down to the client.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11013: Invalid data provider. Expected a WebServiceObject.

Cause: A web service data control attempted to set an invalid provider. This may due to a failed call.

Action: Check that the application's web service(s) have been properly configured, and that the web service(s) themselves are sending appropriate data values down to the client.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11014: Error: Unable to determine the return type for operation {0}

Cause: Internal error. The framework was unable to determine the return type of a virtual provider operation.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11015: Error defining the property: {0} - {1}

Cause: Internal error. The framework was unable to load a virtual provider type for the given property name.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11016: No Web Service definition defined.

Cause: Internal error. The framework was unable to load a web service definition required for an operation.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11017: Operation {0} should have returned a {1} but nothing was returned.

Cause: A web service data control operation had a null response. This may due to a failed call.

Action: Check that the application's web service(s) have been properly configured, and that the web service(s) themselves are sending appropriate data values down to the client.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11018: Error with the HTTP connection while processing ''{0}'' - {1}

Cause: There was an exception trying to open the connection to the server.

Action: Verify that the device is connected to the internet and has access to the specified server.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11019: Error obtaining the output stream with the HTTP connection while processing ''{0}''

Cause: Could not open an output stream to write data to the server.

Action: Verify that the device is connected to the internet and has access to the specified server.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11020: Error while processing ''{0}'' - SOAP FAULT: {1} - {2}

Cause: A SoapFault occurred while executing an operation.

Action: Determine the cause of the error via the supplied fault code, contact technical support.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11021: Attempting to cache ({0}, {1})

Cause: Internal error. An attempt was made to cache a framework metadata element of an unsupported type.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11022: Connector Error: {0}

Cause: There was an exception trying to open the connection to the server.

Action: Verify that the device is connected to the internet and has access to the specified server.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11023: Connection Error: {0}

Cause: Could not open an input stream to read data from the server.

Action: Verify that the device is connected to the internet and has access to the specified server.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11024: Connection Error: unable to establish a connection.

Cause: There was an exception trying to open the connection to the server.

Action: Verify that the device is connected to the internet and has access to the specified server.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11025: EL: Unable to resolve variable: {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11026: Exception resolving variable: {0} : {1}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11027: Error parsing pageDef metadata : {0}

Cause: Internal error. An unexpected error occurred while parsing pagedef metadata.

Action: Ensure that all pagedef xml files are valid. Examine the application log for further exception messages, contact technical support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11028: {0} failed to execute - {1}: {2}.

Cause: See Error

Action: See Error.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11029: Could not find or create the binding container for context key: {0}

Cause: See Error

Action: See Error.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11030: Unable to load resource:

Cause: Locale unknown.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11031: Attribute set with value {1} for attribute {0} failed

Cause: The attribute did not pass validation.

Action: Fix the value and set the attribute again.

Level: 1

Type: ERROR

Impact: Data

ADF-MF-11032: Attempting to deliver a location update for ID ''{0}'', but no listener has been registered for that ID

Cause: An attempt was made to deliver a location update, but there is no listener registered for the corresponding watchID.

Action: Ensure that you have registered a valid GeolocationCallback for this watchID.

Level: 1

Type: ERROR

Impact: Data

ADF-MF-11033: An error occurred while trying to retrieve the requested image data.

Cause: Either the device could not retrieve the requested image from the file system, or the device's camera did not take a valid picture.

Action: If you have requested an image from the camera, ensure that the camera is in proper working order by taking a picture from the standalone camera application. If you have requested an image from the device's file system, try to select the desired image from the photo album. You may also need to reduce the size of the image by specifying a different image encoding, requesting a file instead of a binary image object, or specifying a target height and width to dynamically scale the image.

Level: 1

Type: ERROR

Impact: Data

ADF-MF-11034: Unable to determine device's current position.

Cause: The device's current position could not be determined.

Action: Ensure that you have enabled location services for this application on your device, and that you have good wireless reception.

Level: 1

Type: ERROR

Impact: Data

ADF-MF-11035: Unable to monitor changes in the device's position.

Cause: The device's current position could not be monitored.

Action: Ensure that you have enabled location services for this application on your device, and that you have good wireless reception.

Level: 1

Type: ERROR

Impact: Data

ADF-MF-11036: Error encountered in preferences map: {0}

Cause: The internal map used to maintain preferences has encountered an unexpected error.

Action: Examine error message for more information.

Level: 1

Type: ERROR

Impact: Data

ADF-MF-11037: Error retrieving preferences: {0}

Cause: Retrieving preference has encountered an unexpected error.

Action: Examine error message for more information.

Level: 1

Type: ERROR

Impact: Data

ADF-MF-11038: Error setting preference: {0}

Cause: Setting preference has encountered an unexpected error.

Action: Examine error message for more information.

Level: 1

Type: ERROR

Impact: Data

ADF-MF-11039: Error getting preference from internal map: {0}

Cause: Getting preference from internal map used to maintain preferences has encountered an unexpected error.

Action: Examine error message for more information.

Level: 1

Type: ERROR

Impact: Data

ADF-MF-11040: Error setting preference from internal map: {0}

Cause: Setting preference in internal map used to maintain preferences has encountered an unexpected error.

Action: Examine error message for more information.

Level: 1

Type: ERROR

Impact: Data

ADF-MF-11041: Unable to create validator ({0}): {1}

Cause: Attempting to create the specified validator failed.

Action: Examine error message for more information.

Level: 1

Type: ERROR

Impact: Data

ADF-MF-11042: setContext: No binding context exists for this feature

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11043: Failed to locate registered pagedef for path: {0}. Container will not be loaded and bindings will not resolve in this context.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11044: Unable to read DataControl Usages, on loadDataControl for id: {0}.

Cause: Internal Error.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11045: Unable to load DataControls.dcx , on loadDataControl for id: {0}.

Cause: Internal Error.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11046: Unable to load Adapter DC definition for id: {0}.

Cause: Internal Error.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11047: Unable to load Data Control Factory, on loadDataControl for id: {0}.

Cause: Internal Error.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11048: The name read from the DataControl {0}, does not match the definition's ID: {1}.

Cause: Internal Error.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11049: Unable to load Data Control {0} due to following error: {1}.

Cause: Internal Error, see message.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11050: Invalid (Null) Contact object passed

Cause: An attempt was made to remove/create/update a null contact.

Action: Ensure you are specifying a valid contact object for these operations, then try again.

Level: 1

Type: WARNING

Impact: Logging

ADF-MF-11051: Invalid (Null) arguments passed

Cause: Invalid arguments were passed to an operation that expected non-null arguments.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: WARNING

Impact: Logging

ADF-MF-11052: Unable to get the device data control manager

Cause: A serious internal error has occurred.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11053: A {0} was expected but instead a {1} was found.

Cause: The web service call expected a value of a certain type, but instead a different type was found.

Action: Check that the application's web service(s) have been properly configured, and that the web service(s) themselves are sending appropriate data values down to the client.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11054: Invalid value for custom HTTP header. Expected {0} but received {1}

Cause: The web service call requires one or more custom HTTP headers, but these headers could not be set correctly.

Action: Check that the application's web service(s) have been properly configured, and that the web service(s) themselves are sending appropriate data values down to the client.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11055: The web service method {0} is unsupported at this time.

Cause: The application attempted to make use of an unsupported HTTP method.

Action: Make sure that the web service(s) are configured to work with a supported HTTP method, such as GET or POST.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11056: Unable to find metadata definition for {0}, which is required for this web service operation.

Cause: The application could not find the required metadata to support the web service operation.

Action: Clean and redeploy the application. Try to execute the same web service operation in JDeveloper's web services tester.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11057: Encountered exception while invoking SOAP request EndPoint: {0} SOAPAction: {1} Exception: {2}

Cause: The application encountered an error while attempting to invoke a SOAP web service operation.

Action: Ensure the web service is available at the specified address. Try to execute the same web service operation in JDeveloper's web services tester.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11058: Operation {0} returned an unknown response.

Cause: The web service returned an unsupported response type.

Action: Try to execute the same web service operation in JDeveloper's web services tester to make sure it is valid.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11059: Unable to remove contact due to: {0}

Cause: The contact could not be removed from the device's address book.

Action: Ensure that the contact exists, and that no other application is currently using the address book.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11060: Exception caught, e: {0}

Cause: Internal error. An unexpected error occurred while processing preferences.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11061: Couldn't load resource bundle. Bundle Name: {0}

Cause: Can't load resource bundle.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11062: Response [Error: {0}]: {1}

Cause: Internal error. An unexpected error occurred while processing an HTTP response.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11063: value is Null

Cause: A null value was passed to a SelectItem object's value property.

Action: Examine the application log for further exception messages.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11064: label is Null

Cause: A null value was passed to a SelectItem object's label property.

Action: Examine the application log for further exception messages.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11065: Unable to load definition for {0}

Cause: Internal error. The framework was unable to load a virtual type definition.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11066: No application definition (cpx) found

Cause: The framework was unable to locate the Data Binding Registry file, usedto map page ids to the pagedef.xml files that define the page's data bindings.

Action: If your application uses data control based bindings, ensure that a valid DataBindings.cpx file exists.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11067: id is null

Cause: Internal error. An unexpected error occurred while trying to process a REST web service definition.

Action: Report this message to Oracle support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11068: Expected id {0} but received {1}

Cause: Internal error. An unexpected error occurred while trying to process a REST web service definition.

Action: Report this message to Oracle support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11069: Invalid connections.xml

Cause: Internal error. An unexpected error occurred while trying to process web service connection information declared in connections.xml.

Action: Report this message to Oracle support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11070: Unable to load class: "{0}" for managed bean definition bean definition - Name: {1}; Class: {2}; Scope: {3}

Cause: An unexpected error occurred while trying to create a new instance of the named class used as a managed bean.

Action: Ensure the class is on your application or feature classpath.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11071: AdfChannel.send response on channel [{0}] failed - {1}

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11072: Error handling the VMChannel message: {0}

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11073: Argument "{0}" is null

Cause: A null argument was encountered.

Action: Ensure that the argument is valid.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11074: Error in the channel creation confirmation - {0}

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11074: Feature not found with Id "{0}"

Cause: Invalid Feature Id argument.

Action: Please use an existing and valid Feature Id.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11075: metadataDef is not a BeanBindingIteratorBaseDefinition. Element Name: {0}

Cause: Internal error. A DataControl attempted to create an iterator based on invalid metadata.

Action: Report this message to Oracle support.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11075: Feature not found with Name "{0}"

Cause: Invalid Feature Name argument.

Action: Please use an existing and valid Feature Name.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11076: Can't find bundle for bundlePath: {0}

Cause: The framework was unable to find a resource bundle at the indicated path.

Action: Ensure that the resource bundle is included and packaged in your application at the indicated path.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11076: Invalid type of queue entry : {0}

Cause: There was a problem broadcasting a queued event because event type {0} is not a valid event type.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11077: Unable to load class object for type: {0}. Conversions to or from this type will not occur when evaluating the expression: {1}

Cause: An unexpected error occurred while trying to create a new instance of the named class

Action: Ensure the class is on your application or feature classpath and that it has a public default constructor

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11077: Version {0} failed to be activated: {1}

Cause: There was a problem activating version {0} using Configuration Service.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11078: Caught Throwable, wrapping as RuntimeException and rethrowing. Original Exception type: {0}; Original Exception message: {1}

Cause: This is a notification that a framework initiated call caught an exception and is marshaling it back as an AdfException instance.

Action: Examine the application log for further exception messages.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11078: Version {0} is not available for activation

Cause: Version is not available for activation.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11079: flushDataChangeEvent - Exception from container call to adf.mf.api.processDataChangeEvent.

Cause: A call from the embedded CVM to the container function adf.mf.api.processDataChangeEvent has returned with an Exception.

Action: Examine the application log for further exception messages.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11079: Version {0} is locked

Cause: Version is locked.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11080: flushDataChangeEvent - caught Exception, rethrowing as AdfException

Cause: This is a notification that a framework initiated call caught an exception and is marshaling it back as an AdfException instance.

Action: Examine the application log for further exception messages.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11080: Artifact {0}, Version {1} does not exist

Cause: Artifact cannot be found.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11081: BindingContainer: {0}; Could not locate object with id: {1}

Cause: The named identifier could not be located in the named Binding Container.

Action: Check your pages for for any expressions of the form '#{bindings.id.*}'. Ensure that a bindings, executables, or variable id element in the corresponding pagedef.xml file exists with that id.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11081: Artifact {0}, Version {1} could not be validated

Cause: Artifact cannot be validated using checksum or last modified information. Please check the manifest.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11082: Checksum do not match for Artifact {0}, new version may be available

Cause: Checksum do not match.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11083: Last Modified time does not match for Artifact {0}, new version may be available

Cause: Last Modified does not match.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11084: Artifact {0} version {1} already exists.

Cause: Artifact already exist, may not have been cleaned up previously.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11085: Failed setting connection security for connection {0}

Cause: Security configuration error. WS cannot set credential from store.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11085: Unable to get Artifact {0} as input : {1}.

Cause: Unable to get input contents of artifact, maybe pointing to invalid location or not accessible.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11086: Error parsing {0}: {1}

Cause: An unexpected error occurred while parsing a PDefViewObject xml file.

Action: Check that any xml files in the application's persDef.* packages are valid xml.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11086: Unable to get handle to a file {0} file - {1}.

Cause: Unable to get handle to a file.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11087: Unable to resolve methodExpression: {0}

Cause: The named EL expression could not resolve to an actual method call.

Action: Verify that the path to the method in the expression will resolve to valid objects, and that the named method (and signature) actually exists.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11087: Unable to copy artifact {0} to {1}.

Cause: Unable to copy file.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11088: Unable to load class: {0}; Error Message: {1}

Cause: An unexpected error occurred while trying to load the named class.

Action: Ensure the class is on your application or feature classpath.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11088: Unable to unzip file {0} to {1}.

Cause: Unable copy file from zip.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11089: Tree binding: {0} has a corrupt key; Cannot serialize collectionModel

Cause: Internal error. An unexpected error occurred trying to serialize a key in the named tree binding's collectionModel.

Action: Report this message to Oracle support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11089: Unable to parse catalog versions. Server returned {0}. Exception : {1}

Cause: Unable to parse catalog versions.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11090: whichSet value is not in {"previous", "current", "next"}

Cause: An invalid value was passed for the whichSet parameter to IteratorHandler.fetchSetRelativeTo.

Action: Check that any calls to this method pass one of the documented valid values.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11090: Unable to parse manifest. Server returned {0}. Exception : {1}

Cause: Unable to parse manifest.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11091: Invalid argument passed to getDirectoryPathRoot

Cause: An invalid argument was passed to AdfmfJavaUtilities.getDirectoryRoot.

Action: Check that any calls to this method pass one of the documented valid values.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11091: Unable to update json profiles : {0}

Cause: Unable to parse json profiles, used to update skin family.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11092: Feature argument is null

Cause: A null feature argument was encountered while processing a feature element from maf-feature.xml.

Action: Ensure that the maf-feature.xml file is valid.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11092: Error processing {0} encoded data.

Cause: The system is unable to process the encoded data.

Action: Make sure the application contains the Java libraries necessary to process the encoded data.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11093: Invalid feature argument form

Cause: An invalid feature argument was encountered while processing a feature element from maf-feature.xml.

Action: Ensure that the maf-feature.xml file is valid.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11093: Unable to retrieve list of sandboxes from the server. Server returned {0}. Exception : {1}

Cause: Unable to get list of sandboxes.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11094: {0}: Unexpected element - {1}; Expected - {2}

Cause: Internal error. An xml parser encountered an unexpected child xml element name for the parsers current xml node.

Action: Report this message to Oracle support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11094: Unable to find base skin with id {0} while going through the ancestors of skin id {1}

Cause: Invalid skin configuration.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11095: {0}: key argument is null

Cause: A call to an iterator operation that takes a key (i.e. setCurrentRowWithKeyValue) passed a null key value.

Action: Check that any values passed to or bound to a key parameter in an iterator operation will pass valid keys.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11095: Complex EL not supported for adding application scope data change listener for expression {0}

Cause: Invalid EL set for configuring skin family / skin version.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11096: Unable to locate key: {0} in Iterator: {1}

Cause: A call to an iterator operation that takes a key (i.e. setCurrentRowWithKeyValue) passed a key value that does not exist on that iterator's provider.

Action: Check that any values passed to or bound to a key parameter in an iterator operation will pass valid keys.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11096: Invalid EL format in expression {0} for adding application scope data change listener, EL should be in the format 'Scope.ManagedBean.Property'

Cause: Invalid EL set for configuring skin family / skin version.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11097: {0} - provider data must be a Map

Cause: A call was made to BasicIterator.createRowWithData passing a provider that does not implement Map.

Action: Ensure that the object passed to createRowWithData is of type Map.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11097: Unsupported scope for adding application scope data change listener in expression {0}. Scope should be applicationScope

Cause: Invalid EL set for configuring skin family / skin version.

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11098: No value was returned

Cause: An uxpected error occurred while processing a REST web service operation.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11098: Unable to add property change listener {0} on {1}. Exception {2}

Cause: Internal Error

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11099: Unknown element coming back

Cause: An unexpected error occurred while processing a SOAP data provider type.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11100: SOAP-VERSION {0} not supported.

Cause: The SOAP version encountered is not currently supported.

Action: Refer to the documentation for the supported SOAP versions and contact the server administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11101: Could not load wsdl from location: {0}

Cause: There was an exception trying to load the wsdl.

Action: Verify that the device is connected to the internet and has access to the specified document.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11102: Invalid connection: {0}

Cause: Internal error. The connection specified in the connections.xml could not be found.

Action: Verify that the connections.xml refers to a valid connection.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11103: Transient expressions are unsupported: {0}

Cause: A transient expression was encountered while parsing a PDefViewObject xml file.

Action: Ensure that any xml files in the application's persDef.* packages do not contain transient expressions.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11104: Error parsing {0}: {1}

Cause: An unexpected error occurred while parsing a PDefViewObject xml file.

Action: Check that any xml files in the application's persDef.* packages are valid xml.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11105: Error loading: {0}

Cause: Internal Error. An unexpected error occurred while loading a DataControl.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11107: Unable to create SOAP type for identifier {0}

Cause: The SOAP type for the identifier could not be created.

Action: Verify the identifier is a valid SOAP object and contact the server administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11108: ProviderChangeEvent - provider key: {0} is not a valid accessor on provider: {1}

Cause: A ProviderChangeEvent was sourced using a provider key that does not match an accessor name on the provider it was sourced from.

Action: Check your application for calls to ProviderChangeSupport.fireProviderCreate, Delete, or Update, and ensure that the provider name parameter matches the name of an accessor on the sourcing class

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11109: Unable to encrypt the database due to: {0}. Ensure that you are passing an unencrypted database connection and are specifying a valid password.

Cause: Unable to encrypt the database due to: {0}.

Action: Ensure that you are passing an unencrypted database connection and are specifying a valid password.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11110: Unable to decrypt the database due to: {0}. Ensure that you are passing an unencrypted database connection.

Cause: Unable to decrypt the database due to: {0}.

Action: Ensure that you are passing an unencrypted database connection and are specifying a valid password.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11111: Unable to retrieve Property Descriptors for {0}

Cause: Internal Error.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11112: Unable to invoke setter with value {0} on attribute {1} of {2}

Cause: Internal Error. See Error message.

Action: Ensure that a set accessor exists and is public for this attribute.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11113: Unable to invoke getter on attribute {0} of {1}

Cause: Internal Error. See Error message.

Action: Ensure that a get accessor exists and is public for this attribute.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11114: Unable to retrieve Accessor Attribute for {0} on Java Bean Definition {1}

Cause: The Accessor Attribute for the specified Java Bean Definition could not be found.

Action: Make sure the specified Accessor Attribute exists on the current Java Bean Definition.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11115: Unable to retrieve Java Bean Definition for {0}

Cause: The Java Bean Definition could not be found.

Action: Make sure the specified value is a valid Java Bean Definition.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11117: Unable to create new instance of {0}

Cause: An unexpected error occurred while trying to create a new instance of the named class

Action: Ensure the class is on your application or feature classpath and that it has a public default constructor

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11118: Unable determine array item name for {0}

Cause: The beanClass Class type passed in is an array type, but the attributeName is empty.

Action: Send in a valid attributeName that is a valid field on the GenericType instance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11119: Unable to create GenericType from array {0}. The class type must not be an Array.

Cause: The bean Object passed in is of type Array.

Action: Pass in an Object that is not of type Array.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11120: Error processing list binding metadata: {0}

Cause: An unexpected error occurred while processing list binding declaration

Action: Check that the list binding named in the message has a valid metadata declaration in the pagedef.xml file for the current page

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11121: invokeContainerUtilitiesMethod '{0}' encountered an error [{1}].

Cause: A call from the embedded CVM to a container function has returned with an Exception

Action: Examine the container function named in the message

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11122: Error serializing Data Change Event: {0}

Cause: Internal error. An unexpected error occurred while attempting to serialize a PropertyChangeEvent or a ProviderChangeEvent

Action: Examine the exception message, contact technical support

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11123: Invalid Event

Cause: An instance of a type other than ProopertyChangeEvent or ProviderChangeEvent was passed to DataChangeManager.enqueue

Action: Check your application for calls to DataChangeManager.enqueue and ensure valid parameters.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11124: Exception from container call to {0}

Cause: A call from the embedded CVM to a container function has returned with an Exception.

Action: Examine the container function named in the message, examine the application log for further exception messages.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11125: caught Exception, rethrowing as AdfException

Cause: This is a notification that a framework initiated call caught an exception and is marshaling it back as an AdfException instance.

Action: Examine the application log for further exception messages, contact technical support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11126: Feature not found with Id "{0}"

Cause: Invalid Feature Id argument.

Action: Please use an existing and valid Feature Id.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11127: Feature not found with Name "{0}"

Cause: Invalid Feature Name argument.

Action: Please use an existing and valid Feature Name.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11128: Unable to locate treeBindingID: {0} in Binding container: {1}

Cause: Unable to locate tree binding id in binding container.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11129: Binding container in current EL context is null.

Cause: Binding container in current EL context is null.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11130: Unable to resolve binding container in current EL context

Cause: Unable to resolve binding container in current EL context.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11131: Unable to locate connection "{0}" in: {1}

Cause: Unable to locate connection in connections.xml

Action: Make sure you have defined this connection in connections.xml.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11133: Unable to locate connection "{0}". No connections are defined (check connections.xml)

Cause: No connections are defined in connections.xml.

Action: Make sure connections.xml contains valid connection(s).

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11134: Unable to load bundle: basename = {0}

Cause: Unable to load resource bundle.

Action: Make sure the resource bundle exists in the desired location. Contact Administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11136: Connection not found ({0})

Cause: Either connection target cannot be found, or the protocol type is not supported.

Action: See exception message.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11137: Security Issue ({0})

Cause: Thrown by the security manager to indicate a security violation.

Action: See exception message.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11138: I/O Error ({0})

Cause: I/O exception of some sort has occurred.

Action: See exception message.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11139: Internal Problem ({0})

Cause: Internal Problem.

Action: See exception message.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11140: Cannot modify read-only collection - operation "{0}" is unsupported.

Cause: An attempt was made to modify a read-only collection.

Action: Do not add, modify, or remove values from this collection.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11141: The EL expression "applicationScope.configuration.{0}" is read-only

Cause: An attempt was made to modify a read-only EL expression.

Action: Do not try to change values that are children of applicationScope.configuration.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11142: An error occurred while populating the EL node "applicationScope.configuration" - {0}. Device-specific configuration properties will not be available

Cause: An internal error occurred.

Action: Contact technical support

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11143: Unable to clear password for username "{0}" with adfCredentialStoreKey "{1}"

Cause: Either the adfCredentialStoreKey or username is invalid.

Action: Please check the adfCredentialStoreKey value and username used to clear password.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11144: Unable to set value to the property due to invalid binding iterator.

Cause: Unable to set value to the property as iterator value was null.

Action: Make sure that the property is bound to a valid iterator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11145: Unable to get value for the property due to invalid binding iterator.

Cause: Unable to get value for the property as iterator value was null.

Action: Make sure that the property is bound to a valid iterator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11146: Cannot invoke asynchronous javascript function due to device is not ready from the Container side.

Cause: The embedded Java framework does not receive device ready event from the Container side within timeout.

Action: Check if there is any deadlock or error during application startup.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11147: Interrupted during waiting for device ready.

Cause: The embedded java thread is interrupted during waiting for device ready.

Action: Restart the application.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11148: Access violation trying to invoke javascript on communication Id {0} and feature Id {1}.

Cause: Invoke Javascript functions on other feature is not allowed.

Action: Contact administrator to remove the offending logic from the application.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11149: Unable to display file. Exception: {0}

Cause: The file could not be displayed.

Action: Ensure that the file exists at the given location and that it is of a supported type.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11150: Cannot delegate following notification to feature - {0}

Cause: Feature ID is null or empty

Action: Pass a valid feature ID

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11151: Cannot delegate following notification to feature with ID {0} - {1}

Cause: No Feature Lifecycle Listener is associated with the feature with ID {0}

Action: Associate a feature lifecycle listener with the feature with ID : {0}

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11152: Unknown child node '{0}' encountered in element node '{1}'

Cause: Unknown child node was encountered.

Action: Please contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11153: Unknown attribute name '{0}' encountered in element node '{1}'

Cause: Unknown attribute name was encountered.

Action: Please contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11154: maf-config.xml could not be loaded due to error: {0}

Cause: Error loading maf-config.xml

Action: Please contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11155: Could not find the data control named: {0} in the binding context.

Cause: Data control name is not valid

Action: Pass a valid data control name defined in the binding context

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11156: Specified watchID "{0}" is already in use.

Cause: The watchID you have specified is already in use, and all watchIDs must be unique.

Action: Either specify a different watchID, or stop listening for updates on this watchID before attempting to reuse it.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11157: Failed to fetch amx file: {0}

Cause: There was a problem loading the amx file

Action: Check that your amx include tags reference valid paths, and confirm the necessary resources are packaged into your deployed application

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11158: Unable to commit changes due to a null data provider

Cause: The data provider is null for an ADFBC REST commit operation.

Action: Please contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11159: Unable to commit changes due to an invalid data provider: {0}

Cause: The data provider is not an instance of the expected ADFBC REST type.

Action: Please contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11160: Unable to initialize sync framework from settings file {0}; using defaults. Error was: {1}

Cause: There was a problem loading the sync config file

Action: Check that you have correctly specified the sync config file, and that it exists at the location indicated in the error message.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11161: Specified sync configuration file {0} not found; using default.

Cause: The specified sync config file does not exist

Action: Check that you have correctly specified the sync config file, and that it exists at the location indicated in the error message.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11162: Unable to commit changes due to an invalid data provider: {0}

Cause: The data provider is not an instance of the expected ADFBC REST type.

Action: Please contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11163: Unable to commit changes due to an invalid data provider: {0}

Cause: The data provider is not an instance of the expected ADFBC REST type.

Action: Please contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11164: Device Access is not enabled for: {0}

Cause: Device Access is not enabled

Action: Enable Device Access in maf-application.xml Overview editor

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11165: No login connection for specified key was found. Check connections.xml for adfCredentialStoreKey={0}

Cause: Login connection is not found in connections.xml for the key

Action: Contact system admin with the error message

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11166: Invalid connections.xml information for connection: {0}

Cause: Internal error. Expected web service connection information for the specified connection was not found in connections.xml.

Action: Report this message to Oracle support.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12001: Unable to load resource: {0}

Cause: The specified resource could not be found.

Action: Verify the resource exists.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12005: threw an exception: {0}

Cause: An exception occurred while invoking a container method.

Action: Examine the exception message to determine the correct fix.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12006: Timeout after {0} seconds

Cause: A timeout occurred while invoking a synchronous Javascript method.

Action: Verify the Javascript method is valid and returns a value before the timeout period.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12007: Interrupted: {0}

Cause: A thread was interrupted while invoking a synchronous Javascript method.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12008: Received an unsolicited response message: {0}

Cause: Internal error. An unsolicited response message was received from the channel.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12009: Error handling the VMChannel message: {0}

Cause: Internal error. An exception occurred while handling a VMChannel message.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12010: InvalidResponseSentException

Cause: Internal error. The specified response is invalid or is not ready to be sent.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12011: AdfControlChannel.init .... failed can not continue

Cause: Internal error. Unable to initialize the control channel.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12012: Unable to establish a control channel

Cause: Internal error. Unable to establish the control channel.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12013: Not supported yet. [control channel: {0}]

Cause: Internal error. The specified control channel action is not supported.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12014: Container was unable to create an associated feature context for the channel

Cause: Internal error. An exception occurred while trying to create an associated feature context for the channel.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12015: ActivationInformation: Missing featureId

Cause: Internal error. Unable to pause feature because the featureId is null.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12016: ActivationInformation: Missing listener

Cause: Internal error. Unable to pause feature because the listener is null.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12017: ActivationInformation: The value of pausedFeature is null.

Cause: Internal error. Unable to pause feature because the pausedFeature value is null.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12018: Invalid action: {0}

Cause: The specified action is invalid or unsupported.

Action: Pass in a valid action.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12019: Error: {0}

Cause: An exception occurred during processing.

Action: Examine the exception message to determine the correct fix.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12020: Exception: {0}

Cause: An exception occurred during processing.

Action: Examine the exception message to determine the correct fix.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12021: AdfSpringboardPhoneGapActivity.activeSpringboard was null

Cause: Could not create a new WebView because the activeSpringboard was null.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12022: Current view's context is not an instance of AdfPhoneGapActivity

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12023: Unable to load feature: {0}

Cause: Internal error. The specified feature could not be loaded.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12024: Failed creating dir: {0}

Cause: Internal error. A local directory could not be created to unpack assets to.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12025: Could not find contact with id: {0}

Cause: The specified contact could not be found.

Action: Pass in a valid contact id.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12026: The argument, 'featureId' cannot be null.

Cause: The featureId specified is null.

Action: Pass in a valid, non-null featureId.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12027: Bad argument in method: {0}

Cause: The argument passed into the method is invalid.

Action: Pass in a valid argument to this method.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12028: The feature id, '{0}' does not seem to be valid.

Cause: The featureId specified is invalid.

Action: Pass in a valid, non-null featureId.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12029: The feature context has not been set on this thread

Cause: The feature context was unable to be retrieved.

Action: Make sure the feature context is set on the local thread before attempting to retrieve it.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12031: File not found: {0}

Cause: Could not find the specified file.

Action: Make sure the file exists and is accessible.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12032: Exception finding styleable: {0}

Cause: The specified styleable resource could not be found.

Action: Make sure the styleable resource is valid and exists in the application.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12033: Exception finding class: {0}

Cause: The specified resource class could not be found.

Action: Make sure the resource class is valid and exists in the application.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12034: RemoteFileManager.copySecuredFileFromUrlToLocalPath failed with error code ({0}): {1}

Cause: Could not retrieve secured file from the specified URL.

Action: Verify the url is accessible and credentialis are valid.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12035: Invalid ping response.

Cause: Internal error. The ping response from the feature channel was invalid.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12036: Failed to suspend NFCM constructor.

Cause: Internal error. Could not suspend the thread in the Native Feature Context Manager.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12037: Failed to send ping

Cause: Internal error. A ping request to the feature channel could not be sent.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12038: Unable to send message as text messaging is not available on this device.

Cause: The text messaging Activity could not be found.

Action: Verify this device is provisioned to use text messaging.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12039: Unable to send email as email service is not available on this device.

Cause: The email Activity could not be found.

Action: Verify this device is provisioned for email.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12040: Unable to inject Query String data into the webview because the Activity is null.

Cause: Internal error. The current activity is not a valid Mobile Application Framework Activity to inject query string data to.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12041: Exception when trying to set value on model: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12042: Failed to persist installation date to file: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12043: Could not read installation date from file: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12044: Exception thrown when resetting feature: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12045: Failed to safely encode given URL: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12046: Failed to redirect output: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12047: Could not get Phonegap plugin manager: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12048: Exception thrown when notifying a lifecycle listener that a feature activation was paused: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12049: The copy of the connections.xml file from the bundle to the config service managed location has failed: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12800: ACS Failed

Cause: ACS is not running or ACS configuration error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12801: ACS not configured for default connection and constrained features are not made available.

Cause: Login connection is not configured correctly.

Action: Provide correct URL for ACS.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12802: Application level login failed due to missing authentication context.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12803: Application level login failed due to missing authentication context.

Cause: Configuration error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12804: General login error occurred. User might have entered invalid credentials, or login connection configuration may contain error. E.g. login URL and/or cookie name may be missing or wrong.

Cause: User error or configuration error.

Action: Enter correct usrname/password. If problem persists, contact aministrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12805: Multi-tenant header name is missing.

Cause: Configuration error.

Action: Contact aministrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12806: Cannot authenticate as not enough information is provided for authentication in multi-tenant application. Configuration is missing multi-tenant header name. Contact administrator.

Cause: Configuration error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12807: Tenant name was not entered.

Cause: User did not enter tenant name or configuration error.

Action: Enter tenant name. If problem persistes, contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12808: Cannot authenticate as tenant name was not provided. Please retry.

Cause: User did not enter tenant name or configuration error.

Action: Enter tenant name. If problem persistes, contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12809: Configuration Error.

Cause: Configuration error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12810: Configuration error. Contact administrator.

Cause: Configuration error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12811: Configuration Error.

Cause: Unknown configuration Error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12812: Error in Username.

Cause: User entered invalid user name.

Action: Enter correct user name.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12813: User name and/or tenant name used are different from original user name and/or tenant name. You need to correct the user name and/or tenant name if you entered wrong user name and/or tenant name. To log in as a new user, you must first exit application.

Cause: User entered wrong user name that is different from the original user name used.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12814: Feature level login failed due to unexpected condition.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12815: Invalid ACS configuration. User object was not retrieved correctly due to ACS configuration error. User may not be registered to ACS. Contact administrator.

Cause: ACS configuraton error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12816: Invalid username/password. Please try again.

Cause: User entered invalid credentials.

Action: Try again.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12818: Login Error

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12819: The server cannot be reached. Please make sure you are connected to Internet.

Cause: Server down, or error in device network setting. Network is not available.

Action: Connect to internet. Check proxy setting. Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12820: The login server is not reachable.

Cause: Server down, or error in device network setting. Network is not available.

Action: Connect to internet. Check proxy. Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12821: Logout

Cause: Logout was initiated.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12822: Logout was initiated. Application will terminate.

Cause: User initiated logout.

Action: None.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12823: Server is not reachable. Make sure your device is connected to Internet.

Cause: Server down, or error in device network setting. Network is not available.

Action: Connect to Internet. Check proxy. Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12824: Authentication error with unknown cause. Please contact administrator.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12826: Authentication Error

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12827: Access control service failed during application login.

Cause: ACS down or configuration error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12828: Access control service failed due to unsupported encoding.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12829: Application login connection is not defined. This application cannot be run. Contact administrator.

Cause: Configuration error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12830: Invalid username/password. If the problem persists, please contact your system administrator.

Cause: User entered invalid credentials or configuration error.

Action: Retry. If problem persists, contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12831: Failed to setup IDM security service.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12832: Failed to retrieve IDM authentication context.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12833: Failed to execute OMMobileSecurityService.authenticate. {0}

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12834: Failed to retrieve user object from credential store.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12835: Failed to get OMCredentialStore from service.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12836: Failed to retrieve credential for a key.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12837: URL is not valid when injecting cookies.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12838: Failed to create OMMobileSecurityService.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12839: Invocation of access control service failed. {0}

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12840: Exception while parsing access control service response.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12841: Exception while parsing node of access control service response.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12842: Exception while parsing elements in access control service response.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12844: Contact administrator. Security configuration has serious error.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12845: Failed to complete IDM setup. {0}

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12846: Failed to call authenticate. {0}

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12847: Cannot connect to login server. Check the network and try again. If the problem persists, contact administrator.

Cause: Network error or configuration error.

Action: Connect to Internet. Check proxy setting. Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12848: Internal Error: OIC error when the challenge answer is invalid

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12849: Invalid username/password. If the problem persists, please contact your system administrator.

Cause: User did not enter username/password that is not recognized by the authentication server.

Action: Enter correct username/password and retry. Contact administrator to verify the credentials, if necessary.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12850: Internal Error: Not able to parse the response from the server. Contact administrator.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12851: The device is not yet authentication with the OIC server.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12852: There is no valid authentication scheme provided. Contact administrator. Internal error.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12853: Authentication failed.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12854: Configuration Error: Not able to find a valid sso agent application. Contact administrator.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12855: Configuration Error: Not able to find a valid sso agent application. Contact administrator.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12856: Configuration Error: Cannot authenticate through sso agent application. Contact administrator.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12857: Configuration Error: Application profile is invalid. Contact administrator.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12858: Internal Error: Setup not completed before calling authenticate method. Contact administrator.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12859: SSO agent application service domain does not match to the business application in OIC. Contact administrator.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12860: User token is missing when trying to access a resource. Contact administrator.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12861: Application signatures are invalid for processing the authentication. Contact administrator.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12863: Configuration error: MobileSecurityService object is not initialized properly.(SSOAgentApp initialization) Contact administrator.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12864: Login Failed

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12865: Maximum allowed login attempts has exceeded. The application will terminate. Contact administrator.

Cause: User has exceeded maximum allowed attempts for login without success.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12866: Could not find string resource for ID {0} extracted from {1}

Cause: The strings.xml file did not contain a value for the given ID.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12870: Device's location is currently unavailable

Cause: Device location is currently unavailable.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12871: pausedFeature was not obtained

Cause: pausedFeature was not obtained.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12872: Authentication context was not obtained

Cause: The authentication context was not obtained.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12873: Error while logging in: {0}

Cause: There was an error while logging in.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12874: Could not find connection for ID: {0}

Cause: connections.xml did not contain a connection for the given ID.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12875: An error occurred while attaching phonegap to SpringView, threw an exception {0}

Cause: Internal Error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12876: Configuration error.

Cause: Security not configured correctly. Shutting down the application.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12877: Login connection configuration error. {0} Contact administrator.

Cause: Configuration error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12878: Credential Store Key is not specified.

Cause: Configuration error. Credential store key in connection.xml is missing or malformed.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12879: Invalid or missing username and/or password.

Cause: Username is not correctly entered.

Action: Edit and retry.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12881: Error in composite credential store key.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12882: Invalid Access Control Service URL.

Cause: Configuration error. Access Control Service URL is missing or malformed.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12883: Invalid Logout URL.

Cause: Configuration error. Logout URL is missing or malformed.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12884: Invalid Login URL.

Cause: Configuration error. Login URL is missing or malformed.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12885: Cookie is not specified.

Cause: Configuration error. Login server cookie is not configured correctly.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12886: Idle timeout must be 10 or larger, session timeout must be 30 or larger and larger than idle timeout.

Cause: Configuration error. Error in timeout values.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12887: Login Connection Configuration Error

Cause: Configuration error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12888: Authentication URL responded with illegal HTTP response code. It is not a basic authentication end point. Please contact administrator.

Cause: Configuration error. The login URL responded with an HTTP response code that cannot be processed by basic authentication response handler. The login URL cannot be used as the authenticaton URL.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12889: Terminating...

Cause: Title for application termination dialog. Fatal error in security configuration or fatal user input error in login screen.

Action: Contact administrator if it was caused by configuration error and error says contact administrator..

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12890: Failed to get active security context. Internal error. Contact administrator.

Cause: Internal framework (MAF) error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12891: Error encountered displaying application settings: {0}

Cause: Preferences are corrupted.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12892: Failed to invoke method {0}. Threw an exception: {1}

Cause: Internal framework (MAF) error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12893: Exception invoking getLoginViewInitData. Contact administrator.

Cause: Internal framework (MAF) error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12894: File not found. URL: {0}

Cause: Could not find a file at the given URL.

Action: Provide a URL that points to an existing file.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12895: No activity found capable of displaying file: extension = {0}, MIME type = {1}

Cause: Could not find an activity capable of displaying given file type

Action: Install an application capable of displaying files of given type.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12898: Unable to load ADF_HIDDEN_BACKGROUND feature; device datacontrol features will be unavailable.

Cause: Internal error. The metadata which defines this feature could not be found.

Action: Contact system administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12899: The previous execution of the application was terminated abruptly. Please close the application and restart again.

Cause: The application was terminated abruptly earlier and credential store has residual security information.

Action: User must restart the application.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12900: Calling Invoke Java on another feature is not allowed.

Cause: A request was made to invoke Java from a feature using some other feature's ID. This is not allowed.

Action: The developer needs to either remove the Feature ID from the request or use the feature ID or the background Channel ID.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12901: Access violation

Cause: A request was made to invoke Java from a feature using some other feature's ID. This is not allowed.

Action: The developer needs to either remove the Feature ID from the request or use the feature ID or the background Channel ID.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12902: GetPassword failed

Cause: Failed to decrypt password retrieved from credential store

Action: Contact administrator

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12903: Javascript is not currently available for feature {0}

Cause: The current feature is not yet set up to invoke Javascript.

Action: Wait until the feature is fully loaded and no login prompts are being displayed, then try again.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12904: Error registering for receiving push notifications. Error ID returned from GCM is {0}

Cause: Error ID returned from GCM is {0}

Action: Consult GCM documentation for the error ID to determine the corrective action.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12905: Failed to get current install date: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.

Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12906: An attempt was made to invoke a Java method {0} from the main thread.

Cause: Invalid attempt to invoke Java method from the main thread.

Action: Use a worker thread when invoking Java methods.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12907: Unable to complete action due to the device not supporting the activity.

Cause: The requested activity could not be found.

Action: The web element should not be rendered on this device.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12908: Configuration error in getSecuredDomain. Security configuration was not persisted.

Cause: The persisted security configuration was not found for key. It suggests configuration error.

Action: The administrator needs to verify the configuration.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12909: An error occurred while accessing stored credentials.

Cause: An unexpected error occurred while accessing the stored credentials for the current user.

Action: Attempt to logout and restart the application. If the error persists contact the administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12910: An error occurred while showing login view.

Cause: An unexpected error occurred while showing login view.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12911: The passed in configuration parameter does not conform to the required format. key = {0}

Cause: An unexpected parameter error occurred while parsing login configuration.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15001: Error while resolving value {0}

Cause: Error resolving attribute.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15002: Volatile state access requires an AMX node ID but was given: {0}

Cause: An attempt was made to get or set the volatile state of an AMX node but the AMX node ID was not able to be determined. This is most likely the result of using the API improperly or at the wrong time.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15003: Volatile state access failed to establish a place for storage: {0}

Cause: The application was unable to establish a place to retrieve or store the volatile state for an AMX node.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15004: Client state access requires an AMX node ID but was given: {0}

Cause: An attempt was made to get or set the client state of an AMX node but the AMX node ID was not able to be determined. This is most likely the result of using the API improperly or at the wrong time.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15005: Client state state access failed to establish a place for storage: {0}

Cause: The application was unable to establish a place to retrieve or store the client state for an AMX node.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15006: Client state access failed: {0}

Cause: The application was unable to access the client state data.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15007: Navigation failed due to not being able to set the mobile framework context: {0}

Cause: The application was unable to establish the mobile framework context during a navigation.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15008: Navigation failed due to not being able to remove the mobile framework context: {0}

Cause: The application was unable to remove the mobile framework context during a navigation.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15009: Navigation failed due to an unexpected error: {0}

Cause: The application was unable to navigate due to an unexpected error.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15010: Critical section in use

Cause: An attempt was made to enter the AMX critical section when other code is already inside of the critical section.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15011: Critical section in not currently in use

Cause: An attempt was made to queue a critical section task when the AMX critical section is not in use.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15012: Failed to sort AMX nodes

Cause: Sorting of AMX nodes failed. The error has most likely been caused by passing AMX nodes that are not in the same hierarchy.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15013: Invalid use of $jq.drag, use adf.mf.api.amx.addDragListener instead.

Cause: Improper use of an internal API has been made to $.fn.drag.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15014: Failed to load an XML document: {0}

Cause: An XML file was not able to be parsed. The XML file should be checked for improper syntax.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15015: No attribute list defined for the given location. List name: {0}

Cause: An attribute list for an AMX fragment was used without a definition for the list.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15016: Attribute list used outside of a fragment. List name: {0}

Cause: An attribute list was used outside of a fragment.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15017: Nested attribute list when the parent list is not currently being processed

Cause: A nested attribute list was used outside when the parent list was not being processed.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15018: Attribute list step attribute set to 0

Cause: The step attribute of the attribute list must be set to a positive or negative number, not zero.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15019: amx:fragmentDef must have a <fragment> tag definition as the first child

Cause: fragment definition must have a fragment meta-data tag as its first child.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15020: No attribute defined for name {0}

Cause: An amx:attribute tag has been used for an attribute that was not declared in the meta-data of the fragment.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15021: No facet defined for name {0}

Cause: An amx:facet tag has been used for a facet that was not declared in the meta-data of the fragment.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15022: Required attribute {0} missing value

Cause: A required attribute for a fragment was either not passed or the value that was passed was null.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15023: Recursive fragment inclusion detected

Cause: A fragment is being included in a recursive loop.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15024: Unassignable EL '{2}' in attribute '{1}' for AMX node '{0}'

Cause: AMX node has an unassignable EL value for one of its attributes.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15501: Error message for Selenium test with argument: {0}

Cause: Error while parsing EL expression.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15502: The number of MIME types specified, {0}, does not match the number of attachments, {1}.

Cause: An attempt was made to send an e-mail with attachments, but the number of MIME types does not correspond to the number of attachments.

Action: Either explicitly specify a MIME type for each attachment, or do not specify any MIME types at all and let the system automatically determine the correct MIME type for each file.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15503: Request: {0} exception: {1}

Cause: Error happened in the request.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15504: Exception: {0} when trying to resolve: {1}

Cause: Exception happened while resolving EL expression.

Action: Please make sure that the EL expression being passed is valid.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15505: Exception: {0}

Cause: Exception happened.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15506: Set local value failed, but callback threw exception: {0}

Cause: Exception happened while calling error callback for setLocalValue.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15507: Set local value succeeded, but callback number {0} threw exception: {1}

Cause: Exception happened while calling success callback for setLocalValue.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15508: Get value succeeded, but callback number {0} threw exception: {1}

Cause: Exception happened while calling success callback for getValue.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15509: Get value failed, but callback number {0} also threw exception: {1}

Cause: Exception happened while calling error callback for getValue.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15510: Set local value failed, and about to execute callback(s). Thrown exception was: {0}

Cause: Exception happened in setLocalValue.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15511: Error processing the data change event - {0}

Cause: Exception happened in processing data change event.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15512: Unable to set data change event values [{0}]

Cause: Exception happened.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15513: Error encountered when calling the bulk data change notification callback. Error: {0}

Cause: Exception happened.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15514: Error encountered when calling the data change notification callback for {0}. Error: {1}

Cause: Exception happened.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15515: Error encountered when calling the error callback

Cause: Exception happened.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15516: Error encountered when calling the error handlers. - {0}

Cause: Exception happened.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15517: Error when resetting the binding context. - {0}

Cause: Exception happened.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15518: Managed beans in a non-java based environment is not supported.

Cause: Exception happened.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15519: Ran into a problem updating {0} keys - {1}

Cause: Exception happened.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15520: Unable to update the provider because cm is undefined.

Cause: Exception happened.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15521: EL Parsing Error: {0} -- [column {1}] {2}

Cause: Exception happened.

Action: Please contact your local administrator for assistance.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15522: Unable to resolve {0} with the given variables:

Cause: Unable to resolve EL expression.

Action: Please make sure that a valid EL expression is passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15523: Incorrect number of operands {0} - {1}

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15524: Non-matching () or []

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15525: No ending expression marker found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15526: Unknown character '{0}' found.

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15527: Unexpected constant found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15528: Unexpected number constant found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15529: Unexpected string constant found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15530: Unexpected variable found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15531: Nested EL Expressions are not supported.

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15532: Unexpected operator found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15533: Unexpected (unary) operation found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15534: Unexpected (binary) operation found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15535: Unexpected (ternary) operation found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15536: Incorrect number of arguments passed

Cause: Exception happened as incorrect number of arguments were passed to setLocalValue.

Action: Please make sure that you have exactly 3 arguments passed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16000: ERROR: %@

Cause: A generic error occurred prefix. See the text in the error for more details.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16001: Class %@ generated an error when it was alloc-ed and init-ed - Aborting add of Application Lifecycle Listener ERROR: %@

Cause: A configured native Objective-C lifecycle listener class could not be allocated or initialized.

Action: Ensure the configured native Objective-C class is implemented and linked into the iOS native framework. Ensure the initialization of the object is not throwing an exception.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16002: Invalid Use

Cause: Used as the title for an exception when a method that must run of the main thread has been called on the main thread. Can also be used as the title in the case where a method required to run on the main thread has not been called on the main thread.

Action: See the error message for more details on altering the type of thread the method is called on.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16003: This function must be called on the main thread.

Cause: A method that must be called on the main thread has been called on a thread other than the main thread.

Action: Alter your use of the method to call the method on the main thread.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16004: This function must NOT be called on the main thread.

Cause: A method that must NOT be called on the main thread has been called on the main thread.

Action: Alter your use of the method to call the method off the main thread.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16005: Bad Config File

Cause: Loading the configuration file into a string for inspection has failed. One example is the verification of connections.xml during a configuration service check for new configuration.

Action: Verify the connections.xml file on the configuration server is not corrupt or the connections.xml in the app bundle is not corrupt.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16006: Invalid Configuration

Cause: The configured Container Utilities class could not be created or initialized.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16007: AdfmfContainerUtilities implementer not configured.

Cause: The configured Container Utilities class could not be found. Are all native dependency libraries linked in?

Action: Ensure all iOS native libraries have been linked in.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16008: AdfmfContainerUtilities implementer class not found.

Cause: The configured Container Utilities class could not be found. Are all native dependency libraries linked in?

Action: Ensure all iOS native libraries have been linked in.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16009: AdfmfContainerUtilities implementer could not be created.

Cause: The configured Container Utilities class was found but could not be allocated or initialized. Are all native dependency libraries linked in?

Action: Ensure all iOS native libraries have been linked in. Ensure the class is not throwing an exception on initialization.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16010: Bad Request

Cause: Used as a title for an error encountered when downloading a configuration file failed with a 400 error from the server.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16011: Could not download file due to 400 Bad Request.

Cause: Downloading a configuration file failed with a 400 error from the server.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16012: Unauthorized

Cause: Used as a title for an error encountered when downloading a configuration file failed with a 401 error from the server.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16013: Could not download file due to 401 Unauthorized (bad username or password).

Cause: Downloading a configuration file failed with a 401 error from the server.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16014: Forbidden

Cause: Used as a title for an error encountered when downloading a configuration file failed with a 403 error from the server.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16015: Could not download file due to 403 Forbidden.

Cause: Downloading a configuration file failed with a 403 error from the server.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16016: Not Found

Cause: Used as a title for an error encountered when downloading a configuration file failed with a 404 error from the server.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16017: Could not download file due to 404 Not Found.

Cause: Downloading a configuration file failed with a 404 error from the server.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16018: Bad Gateway

Cause: Used as a title for an error encountered when downloading a configuration file failed with a 502 error from the server.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16019: Could not download file due to 502 Bad Gateway.

Cause: Downloading a configuration file failed with a 502 error from the server.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16020: Service Unavailable

Cause: Used as a title for an error encountered when downloading a configuration file failed with a 503 error from the server.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16021: Could not download file due to 503 Service Unavailable.

Cause: Downloading a configuration file failed with a 502 error from the server.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16022: Invalid Argument

Cause: Used as a title for an error when an invalid argument is passed into a method.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16023: A nil package name was passed to [oraADFLogger getLogger:].

Cause: A nil package name was passed into the get logger call.

Action: Pass a non nil string into the call.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16024: Error file url cannot be nil

Cause: A nil file url was passed into the initialization of a remote file manage.

Action: Pass a non nil string url into the initialization.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16025: Property name cannot be nil.

Cause: A nil key was passed into a get value call when requesting a value for the adf-config.xml file.

Action: Pass a non nil key name into the call.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16026: Too few arguments.

Cause: The PhoneGap handler for goto feature is missing the feature id.

Action: Pass a feature id to the PhoneGap call.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16027: Missing classname.

Cause: A call to one of the Container Utilities invoke calls is missing a classname.

Action: Pass a classname to the invoke call.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16028: Missing method.

Cause: A call to one of the Container Utilities invoke calls is missing a method name.

Action: Pass a method name to the invoke call.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16029: Feature Id missing.

Cause: A call to one of the Container Utilities invoke calls is missing a featureId.

Action: Pass a featureId to the invoke call.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16030: Unrecognized Call Type

Cause: The PhoneGap handler received a request for a Container Utilities invoke of something other than Java, Container or JavaScript.

Action: Pass a valid invoke type.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16031: FeatureContext not found.

Cause: The Container Utilities invoke call was passed a featureId for a feature that may not be available.

Action: Insure the featureId is valid and the user has access to that feature.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16032: Unexpected Response

Cause: Used as a general title in a situation where an unexpected response was encountered.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16033: CVM Response returned a nil response.

Cause: The CVM return a nil response message.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16034: CVM Response returned a nil FeatureContextAccessor.

Cause: The feature context accessor returned by a CVM call was nil.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16035: JS Response returned a nil response.

Cause: The framework return from the a call to JavaScript was nil. Even if the JavaScript did not have a return that information should have been returned in a response.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16036: Cannot send JavaScript calls to the channel '%@' that does not have a webview.

Cause: A JavaScript call was made on the control channel or a channel that does not yet have a webview. There is no associated web view so this request cannot be fulfilled.

Action: Make the JavaScript call using your featureId and that feature has been activated.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16037: IO Error

Cause: A generic title for an IO error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16038: Error removing file.

Cause: The configuration service could not remove an old file.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16039: Error copying file.

Cause: The configuration service could not copy a file.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16040: Expected file is missing.

Cause: After copying a file to a location a subsequent check for the file found it was missing.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16041: Error moving file.

Cause: Configuration Service had a problem placing the updated file in place. An attempt was made to place the original file back in place and that failed as well.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16042: Could not create directory.

Cause: Configuration Service had a problem creating the managed directory.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16043: Download Error

Cause: There was an error downloading a configuration file.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16044: Could not create connection

Cause: A connection to the configuration could not be made.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16045: There was an unexpected error downloading the file.

Cause: After the download of a file succeeded the path to the local file was nil.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16046: Authentication Failure

Cause: The credentials were either not provided to the remote file manager or were invalid.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16047: We have no username or password.

Cause: The credentials were not provided to the remote file manager.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16048: Could not download file due to authentication failure.

Cause: The credentials provided to the remote file manager were invalid.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16049: Invalid Container Document

Cause: The configuration file was invalid. See the message for more details.

Action: See the error message for details on why the document is invalid.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16050: Element 'feature' was encountered while an active 'feature' was being processed.

Cause: A feature element was encountered by the container while the container was parsing a previous feature element.

Action: Ensure your maf-feature.xml file conforms to the required format.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16051: The Feature Id, '_Control_Channel_' conflicts with a reserved VM Channel Identifier Name

Cause: A feature element is using '_Control_Channel_' as its id. This is a reserved feature id.

Action: Use a different feature id.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16052: Class 'OracleAdfmfFeature' was initialized with a wrong element type.

Cause: An internal error has caused the feature object model to be initialized with an element other than feature.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16053: Bad State

Cause: The remote file manager has been initialized with a nil URL.

Action: Initialize the remote file manager with a non-nil URL string.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16054: File url cannot be nil

Cause: The remote file manager has been initialized with a nil URL.

Action: Initialize the remote file manager with a non-nil URL string.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16055: Attempted to add an object that was not an ASIHTTPRequest to an ASINetworkQueue

Cause: Phrase appears to be unused.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16056: Create Contact Error

Cause: During the save of a contact in the PhoneGap handler an error was encountered and the contact could not be saved.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16057: Remove Contact Error

Cause: During the delete of a contact in the PhoneGap handler an error was encountered and the contact could not be deleted.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16058: Invalid argument Error

Cause: During contact operation an error was encountered that indicates an invalid argument was passed in.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16059: Timeout Error

Cause: During contact operation an error was encountered that indicates a timeout had occurred.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16060: Pending operation Error

Cause: During contact operation an error was encountered that indicates a pending operation error occurred.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16061: I/O Error

Cause: During contact operation an error was encountered that indicates an IO error occurred.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16062: Not Supported Error

Cause: During contact operation an error was encountered that indicates that contacts on this device are not supported.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16063: Permission Denied Error

Cause: During contact operation an error was encountered that indicates this user does not have permissions for the operation.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16064: Unknown Error

Cause: During contact operation an unknown error was encountered.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16066: Invalid Class

Cause: A class is missing an implementation of a function that must be overriden.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16067: Class missing an implementation of a required function. Enable debug to log information about the class.

Cause: A class is missing an implementation of a function that must be overriden.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16068: Feature view class not found.

Cause: A custom native Objective-C classname was specified as a feature view. That class could not be found.

Action: Ensure the library is properly linked in and the classname was properly specified.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16069: Feature view class could not be created.

Cause: A custom native Objective-C classname was specified as a feature view. That class was found but could not be allocated.

Action: Ensure the library is properly linked in and the classname was properly specified.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16070: View controller provided a nil view for feature view.

Cause: A custom native Objective-C classname was specified as a feature view controller. That class was found and created but when it provided its view it returned nil.

Action: Ensure the library is properly linked in and the classname was properly specified. Ensure your view controller returns a view.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16071: Class is not a valid view type. Currently supported subclass must be from: UIView or UIViewController

Cause: A custom native Objective-C classname was specified and was found to be something other than a UIView or UIViewController.

Action: Ensure the specifed custom native Objective-C classname is a UIView or UIViewController.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16072: An HttpURLConnection used by a feature was not found.

Cause: A feature specified a connection that was not found in the connections.xml configuration file.

Action: Ensure the feature specifies a valid connection.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16073: An HttpURLConnection used by a feature has a nil url.

Cause: A feature specified a connection that was found in the connections.xml configuration file but had a nil URL.

Action: Ensure the feature specifies a connection that has a url.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16074: Invalid Message

Cause: An invalid message was found. See the error message for more details.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16075: Unknown Message Type specified by message.

Cause: A low level ADF Message type other than 10000 was encountered.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16076: Login Error

Cause: There was an error logging into the app or a feature. See the message for more information.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16077: Configuration Error

Cause: There was an error while configuration service was processing the configuration files.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16078: UIWebView Load Failure

Cause: The Web UI failed to load. See the error message for more details.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16079: Failed to load feature '%@' URL: %@

Cause: The Web UI failed to load. This error should contain the content of the error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16080: Please contact administrator.

Cause: Phrase appears to be unused.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16081: The login server is not reachable.

Cause: This error code is returned by NSNetwork and IDM Mobile SDK passes it through. This error code indicates that network is active and Internet is reachable but cannot reach the specified login connection URL. Possible cause is the target server down, error in URL, etc.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16082: Invalid username/password. If the problem persists, please contact your system administrator.

Cause: The user has entered an invalid password and username combination.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16083: Configuration error. Contact administrator.

Cause: These error codes are returned by IDM Mobile SDK and indicates some sort of configuration error. because of the configuration error, SDK could not create a authentication request, or server returned error code that indicates configuration error in the request.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16084: ACS Failed

Cause: There was a authentication failure. See the error message for more details.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16085: Invalid ACS configuration. User object was not retrieved correctly due to ACS configuration error. User may not be registered to ACS. Contact administrator.

Cause: An invalid ACS configuration for this user.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16086: Server is not reachable. Make sure your device is connected to Internet.

Cause: The authentication server can not be reached.

Action: Make sure your device is connected to Internet. Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16087: Invalid username/password. Please try again.

Cause: The user entered an invalid username/password combination.

Action: Enter the correct username or password. Ensure you have a valid username.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16088: Configuration error. Access control service URL is missing. Contact administrator.

Cause: The security configuration is incorreclty missing a service URL.

Action: Provide the valid URL.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16089: You exceeded maximum allowed login attempts. You are locked out. Contact administrator.

Cause: The user has attempted to login with bad credentials too many times.

Action: Shutdown the app and restart it to try again.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16090: The check for configuration changes could not be performed. Please check your network connection or contact an administrator.

Cause: There was an error while trying to download the new configuration and test if it has changed.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16091: Could not update configurations from configuration service.

Cause: The new configuration files could not be moved into place for use after new configuration was found on the server.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16092: Malformed Message

Cause: A message was sent to the native framework from the CVM and it did not have the proper format.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16093: Empty request message is not allowed.

Cause: A VM Message was sent to the native framework from the CVM which resulted in a nil ADF Message.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16094: Unsupported Message

Cause: An invalid message was sent to the native framework from the CVM. See the message for more details.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16095: System messages are not supported on this channel

Cause: A system message was sent to the native framework from the CVM on a channel that does not have a system message handler.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16096: Invalid system request %@

Cause: A system message was sent to the native framework from the CVM but resulted in a non-AdfSystemRequest ADF Message.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16097: Application messages are not supported on this channel

Cause: An application message was sent to the native framework from the CVM on a channel that does not have an application message handler.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16098: Invalid application request %@

Cause: An application message was sent to the native framework from the CVM but resulted in a non-AdfApplicationRequest ADF Message.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16099: Unhandled Message

Cause: A message was sent to the native framework from the CVM but resulted in a non-application and non-system ADF Message.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16100: UnhandledAdfMessage - ReferenceId: %d Type: %d Body: %@

Cause: A message was sent to the native framework from the CVM but resulted in a non-application and non-system ADF Message.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16101: Received an unsolicited response message

Cause: A response message was sent to the native framework from the CVM but there was no recorded request expecting the response.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16102: Received an unknown message type

Cause: A message was sent to the native framework from the CVM abd resulted in a non-request and a non-response message.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16103: AdfChannel.handle - Error handling the VMChannel message: %@ - ERROR: %@

Cause: An exception occurred while processing a message sent to the native framework from the CVM.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16104: No '%@' specified. Error dropped: '%@'

Cause: An exception occurred in the processor for container utilities calls and a recovery could not be made. The request was lost.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16105: Device access disabled for feature '%@': url:%@, baseUrl:%@, msg:%@

Cause: A feature that was not granted access to the device through white listing made a PhoneGap request.

Action: Ensure the feature is granted white list access to the device.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16106: URL not allowed device access for feature '%@': url:%@, baseUrl:%@, msg:%@

Cause: A URL that was not granted access to the device through white listing made a PhoneGap request.

Action: Ensure the URL is included in the white list providing access to the device.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16107: ERROR During Whitelist: %@

Cause: There was an unexpected error during the processing of the white list for a device access request.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16108: Unable to send updated width/height to Java side

Cause: The native class used to update the width and height was not found or the required method was missing.

Action: Ensure the proper libraries are linked in. Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16109: Unable to register for network status change events. The network status will be unavailable

Cause: The iOS API class for registering for netowkr changes was either not found or did not have the required method.

Action: Ensure the proper libraries are linked in. Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16110: The default login connection, '%@', is not defined.

Cause: A default authorization connection was specified but it was not found in the connections.xml file.

Action: Add the connection to the connections.xml file.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16111: Skin '%@' is missing a family. Ignored.

Cause: A skin family in the specified skin was not found so the skin could not be added.

Action: Add a family to your skin.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16112: Active skin family '%@' returned no skin.

Cause: There was no skin family found for the configured active skin.

Action: Ensure you have specified the correct skin-family in your maf-config.xml file.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16113: Attachment %@ was not found or could not be read

Cause: During the attempt to send out an e-mail, the attachments specified could not be found at the specified location on the device.

Action: Ensure you have passed in the correct location for the file to be attached.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16114: %@ does not support deliverResponseJson:toCallbackSet:forRequest:

Cause: A UIView that does not implement deliverResponseJson was asked to deliver a response JSON.

Action: Implement the method deliverResponseJson:toCallbackSet:forRequest: on your custom view.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16115: %@ is not defined in the webview. JavaScript result call aborted.

Cause: While trying to deliver a response JSON message to a UIWebView it was discovered the response handler JavaScript functions do not exist.

Action: During normal use this should not happen. Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16116: There was a problem calling the function '%@': %@

Cause: An unexpected response was received while delivering a JSON response to a UIWebView JavaScript.

Action: During normal use this should not happen. Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16117: ERROR: encountered an exception when executing the %d callback: %@

Cause: An exception was generated while attempting to deliver a JSON response to a UIWebView JavaScript.

Action: During normal use this should not happen. Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16118: Application Authentication Error. Reason = %@

Cause: Phrase appears to be unused.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16119: Feature Authentication Error. Feature disabled. Reason = %@

Cause: Phrase appears to be unused.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16120: Authentication Error. Please retry.

Cause: Phrase appears to be unused.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16121: ACS returned error: %@

Cause: Generic Authentication Error. The message will provide the details.

Action: See the details in the message.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16122: ACS not configured for connection %@. User objects are not registered.

Cause: Phrase appears to be unused.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16123: Application level login failed due to missing authentication context.

Cause: Internal error (security).

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16124: File Exists At Cache Path

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16125: Cannot create a directory for the cache at '%@', because a file already exists

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16126: Failed To Create Cache Directory

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16127: Failed to create a directory for the cache at '%@'

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16128: Failed To Traverse Cache Directory

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16129: Listing cache directory failed at path '%@'

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16130: Failed To Remove Cache File

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16131: Failed to remove cached data at path '%@'

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16132: Crashing Now because configuration could not be downloaded.

Cause: This message will appear if the configuration service could not download the configuration on the first launch.

Action: Ensure you have network access. Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16133: Show Feature Failed

Cause: An exception occurred during the show of a feature. See the message for more details.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16134: Could not show feature. Attempt to show feature '%@' failed. ERROR: %@

Cause: An exception occurred during the show of a feature. The message should have more details about the failure.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16135: Application Controller Error

Cause: The folder specified as the application controller cannot be found.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16136: The application controller folder '%@' does not exist.

Cause: The folder specified as the application controller cannot be found.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16137: Could not load .properties file: %@ - ERROR: %@

Cause: Phrase appears to be unused.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16138: Error serializing return: %@

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16139: FeatureId could not be determined. Aborting call to Java Class.

Cause: The feature id could not be obtained from the ADFFeature.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16140: CVM Channel verification failed.

Cause: The ping/pong message on CVM starup did not succeed. This means the CVM did not properly start because a value of pong was not retured.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16141: CVM returned an unexpected object type: %@

Cause: The ping/pong message on CVM starup did not succeed. This means the CVM did not properly start because a string was not returned.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16142: Cannot Send Message

Cause: Title indicating an SMS message could not be sent.

Action: Ensure you have access to SMS and it is properly configured.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16143: Unable to send message as text messaging is not available on this device.

Cause: An error indicating an SMS message could not be sent.

Action: Ensure you have access to SMS and it is properly configured.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16144: Unable to send message as unable to get text message composer.

Cause: An error indicating an SMS message could not be sent.

Action: Ensure you have access to SMS and it is properly configured.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16145: AdfGenericInvokeHandler.processRequest - The 'classname' was not specified

Cause: The class name was not provided to the native container invoke method.

Action: Include the classname for the object type you want to call.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16146: adfGenericInvokeHandler.processRequest - The morphClassName call caused an ERROR: %@

Cause: The class name provided to the native container invoke method could not be morphed into an Objective-C class name.

Action: Ensure the class name you have provided is valid.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16147: AdfGenericInvokeHandler.processRequest - The 'classname' morphClassName failed.

Cause: The class name provided to the native container invoke method could not be morphed into an Objective-C class name.

Action: Ensure the class name you have provided is valid.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16148: AdfGenericInvokeHandler.processRequest - The 'method' was not specified

Cause: The method name was not provided to the native container invoke method.

Action: Ensure the method name is provided.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16149: Could not create class: %@

Cause: The class name provided to the native container invoke method did not result in an Objective-C class.

Action: Ensure the class name you have provided is valid. Ensure the libraries your class is in have been linked into the application.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16150: Requested class to be invoked could not be created: %@

Cause: The class name provided to the native container invoke method resulted in an Objective-C class that was found but could not be created.

Action: Ensure the class name you have provided is valid. Ensure the libraries your class is in have been linked into the application.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16151: Instance of %@ class does not respond to '%@' selector.

Cause: The class name provided to the native container invoke method result in an Objective-C class that does not support the method name requested.

Action: Ensure the class name you have provided is valid and has a selector that has a single parameter.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16152: Invoking '%@' caused error: %@

Cause: The class name provided to the native container invoke method result in an Objective-C class that generated an error during the invoke of the requested method.

Action: Ensure the class name you have provided is valid and has a selector that has a single parameter and that method does not throw and exception.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16153: Serializing result from '%@' on %@ type caused ERROR: %@

Cause: The class name provided to the native container invoke method result in an Objective-C class that returned an object that could not be serialized to JSON.

Action: Ensure the class/method name returns a JSON serializable object such as an NSDictionary or NSArray.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16154: Serializing result from '%@' on %@ type generated nil.

Cause: The class name provided to the native container invoke method result in an Objective-C class that returned an object that could not be serialized to JSON.

Action: Ensure the class/method name returns a JSON serializable object such as a non-nil NSDictionary or NSArray.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16155: credentialStoreKey for connection %@ cannot be nil

Cause: Incorrect security configuration, see your admin.

Action: Check connections.xml and ensure that adfCredentialStoreKey attribute exists inside the Reference element for the connection name %@

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16156: credentialStoreKey for connection cannot be nil

Cause: Incorrect security configuration, see your admin.

Action: Check connections.xml and ensure that adfCredentialStoreKey attribute exists inside the Reference element for all connections

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16157: General login error occurred. User might have entered invalid credentials, or login connection configuration may contain error. E.g. login URL and/or cookie name may be missing or wrong.

Cause: There was an error logging into the app or a feature. See the message for more information.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16158: The server cannot be reached. Please make sure you are connected to internet.

Cause: This error code is returned by NSNetwork and IDM Mobile SDK passes it through. This error code indicates that network is active but Internet is not reachable. Possible cause is the proxy setting error, firewall down, ISP down, etc.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16159: Error in threadShellInitializationComplete: %@

Cause: While processing the initilization of the UI after the configuration files were loaded, an exception was generated.

Action: See the message for more details. Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16160: Error in paintMirrorLoop: %@

Cause: There was an exception when tryign to paint the screen mirror.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16161: ACS not configured for default connection and constrained features are not made available.

Cause: Internal error (security).

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16162: Error in Username

Cause: An attempt was made to login with a username different from the original login. This is not supported.

Action: Shutdown the application to log in as a different user.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16163: User name and/or tenant name used are different from original user name and/or tenant name. You need to correct the user name and/or tenant name if you entered wrong user name and/or tenant name. To log in as a new user, you must first exit application.

Cause: An attempt was made to login with a username different from the original login. This is not supported.

Action: Shutdown the application to log in as a different user.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16164: Multi-tenant header name is missing

Cause: The app is configured for multi-tenant and no multi-tenant header name was found.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16165: Cannot authenticate as not enough information is provided for authentication in multi-tenant application. Configuration is missing multi-tenant header name. Contact administrator.

Cause: The app is configured for multi-tenant and no multi-tenant header name was found.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16166: Tenant name was not entered

Cause: The user did not enter a tenant name.

Action: Enter a tenant name in the login dialog.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16167: Cannot authenticate as tenant name was not provided. Please retry.

Cause: The user did not enter a tenant name.

Action: Enter a tenant name in the login dialog.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16168: Application level login will be attempted. Server=%@ for user=%@

Cause: Logged just before the login is being attempted.

Action: No action needed. This is just information.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16169: Application level login succeeded.

Cause: Logged just after the login succeeded.

Action: No action needed. This is just information.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16170: OMCredentialStore did not return property for kSecAttrLabel.

Cause: Internal error (security).

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16171: Application user objects is fetched from credential store: %@

Cause: Internal error (security).

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16172: User authentication test returns %@.

Cause: Internal error (security).

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16173: Feature level login failed due to unexpected condition.

Cause: Internal error (security).

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16174: Feature level login attempt for user=%@.

Cause: Internal information (security).

Action: No action needed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16175: Feature level logout attempt.

Cause: Internal information (security).

Action: No action needed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16176: User objects are being pulled as it is a remote feature login.

Cause: Internal information (security).

Action: No action needed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16177: Authentication success.

Cause: Internal information (security).

Action: No action needed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16178: returned user objects response=%@

Cause: Internal information (security).

Action: No action needed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16179: returned user objects privileges=%@ roles=%@

Cause: Internal information (security).

Action: No action needed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16180: Invoking ACS with payload=%@.

Cause: Internal information (security).

Action: No action needed.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16181: CredentialStoreHandler.logout: authContext was not obtained.

Cause: Internal error (security).

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16182: CredentialStoreHandler.isAuthenticated: pausedFeature was not obtained.

Cause: Internal error (security).

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16183: CredentialStoreHandler.isAuthenticated: authContext was not obtained.

Cause: Internal error (security).

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16184: CredentialStoreHandler.login: pausedFeature was not obtained.

Cause: Internal error (security).

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16185: CredentialStoreHandler.login: authContext was not obtained.

Cause: Internal error (security).

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16186: Configuration Error

Cause: Configuration error (security).

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16187: Application login connection is not defined. This application cannot be run. Contact administrator.

Cause: Configuration error (security).

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16188: Feature login connection is not defined. This feature cannot be accessed. Contact administrator.

Cause: Configuration error (security).

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16189: Logout

Cause: Title for a shutdown notification due to logout.

Action: No action.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16190: Logout was initiated. Application will terminate.

Cause: Message that the application is shutting down due to a logout.

Action: No action.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16191: Login connection configuration error. {0} Contact administrator.

Cause: Configuration error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16192: Credential Store Key is not specified.

Cause: Configuration error. Credential store key in connection.xml is missing or malformed.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16193: Invalid or missing username and/or password.

Cause: Username and/or password is not correctly entered.

Action: Edit and retry.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16195: Error in composite credential store key.

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16196: Invalid Access Control Service URL.

Cause: Configuration error. Access Control Service URL is missing or malformed.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16197: Invalid Logout URL.

Cause: Configuration error. Logout URL is missing or malformed.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16198: Invalid Login URL.

Cause: Configuration error. Login URL is missing or malformed.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16199: Cookie is not specified.

Cause: Configuration error. Login server cookie is not configured correctly.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16200: Idle timeout must be 10 or larger, session timeout must be 30 or larger and larger than idle timeout.

Cause: Configuration error. Error in timeout values.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16201: Login Connection Configuration Error

Cause: Configuration error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16202: Authentication URL responded with illegal HTTP response code. It is not a basic authentication end point. Please contact administrator.

Cause: Configuration error. The login URL responded with an HTTP response code that cannot be processed by basic authentication response handler. The login URL cannot be used as the authenticaton URL.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16203: File not found: %@

Cause: The URL was not pointing to an existing file.

Action: Please provide a URL that points to an existing file.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16204: The email message was not saved or queued, possibly due to an error.

Cause: Network or configuration error.

Action: Verify the device is connected to the network and that at least one e-mail account is properly configured.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16205: An error occurred trying to save the email message to the Drafts folder.

Cause: An underlying operating system error prevented the e-mail draft from being saved

Action: Ensure the device has sufficient free space to save the draft.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16206: An error occurred while trying to queue or send the email message.

Cause: Network or configuration error.

Action: Verify the device is connected to the network and that at least one e-mail account is properly configured.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16207: An unknown error occurred while trying to compose or send an e-mail

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16208: An unknown error occurred while trying to compose or send a text message

Cause: Internal error.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16209: File not found

Cause: Used as a title for an error when a URL points to a non-existant location.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16210: Encountered an invalid prefix to URI mapping. Prefix: %@ is already mapped to URI: %@, re-mapping the prefix to URI: %@ is not allowed

Cause: The metadata contains same prefix mapped to multiple URI's.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16211: Encountered an invalid prefix to URI mapping. URI: %@ is already mapped to prefix: %@, re-mapping the URI to prefix: %@ is not allowed

Cause: The metadata contains multiple prefixes mapped to a URI.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16212: Unable to find UIWebview for feature %@.

Cause: There seems to be some problem with the internal view structure.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16213: Calling Invoke Java on another feature is not allowed.

Cause: A request was made to invoke Java from a feature using some other feature's ID. This is not allowed.

Action: The developer needs to either remove the Feature ID from the request or use the feature ID or the background Channel ID.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16214: Access violation

Cause: A request was made to invoke Java from a feature using some other feature's ID. This is not allowed.

Action: The developer needs to either remove the Feature ID from the request or use the feature ID or the background Channel ID.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16215: Unable to encrypt password: %@

Cause: A problem occurred while attempting to encrypt the generated password.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16216: Unable to generate password via hashing: %@

Cause: A problem occurred while attempting to generate a password.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16217: Unable to decrypt password: %@

Cause: A problem occurred while attempting to decrypt the generated password.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16218: Invalid parameter key. ParameterKey= %@

Cause: A problem occurred while iterating through parameter list before persisting them.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16219: loginComplete failed with exception: %@

Cause: A problem occurred in loginComplete.

Action: Contact administrator.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16220: Could not determine the return type of class %@ for method %@.

Cause: The return type of the method being invoked could not be determined.

Action: Ensure the class name you have provided is valid and has a selector that has a single parameter that returns a supported type.

Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16221: Invalid return type for method %@ in class %@.

Cause: The return type of the method being invoked is not void or an Objective-C object.

Action: Ensure the class name you have provided is valid and has a method that returns either void or an Objective-C object.

Level: 1

Type: ERROR

Impact: Logging