Volt MX Foundry Integration Service Error Codes
The following are the error codes that Volt MX Foundry Integration Service throws. Each error code table consists of the error message, description of the error, severity, way to reproduce the error, error resolution and point of contact.
| Error 1528 |
|
| MESSAGE |
One or more of the services failed in the composite service. |
| DESCRIPTION |
It means that one of the services executed as part of the composite service failed. You can find the actual error code and message in the logs for the individual services. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Provide invalid service URL for one of the services. |
| RESOLUTION |
Resolve the issue faced by the individual service that depends on the error code provided by that service. |
| POINT OF CONTACT |
Depends on the error code for the individual services. |
| Error 5000 |
|
| MESSAGE |
Controller Initialization Error. |
| DESCRIPTION |
It means that the initialization of the ControllerDef.xml file is improper. |
| SEVERITY |
LOW |
| REPRODUCE THE ERROR |
Create improper XML tags in the ControllerDef.xml file. Restart the server. While loading the controller configurations, this error appears. |
| RESOLUTION |
Check the ControllerDef.xml file. |
| POINT OF CONTACT |
VOLTMX |
| Error 5001 |
|
| MESSAGE |
Mandatory Request parameter channel is missing. |
| DESCRIPTION |
Volt MX Foundry Integration Service is hit from places other than the device. Mandatory parameter channel is missing. |
| SEVERITY |
SEVERE |
| REPRODUCE THE ERROR |
Remove the request parameter "channel" while invoking Volt MX Foundry Integration Service. |
| RESOLUTION |
Check the request parameters for mandatory parameter: channel. |
| POINT OF CONTACT |
VOLTMX |
| Error 5002 |
|
| MESSAGE |
Mandatory Request parameters - appID, serviceID or both are missing. |
| DESCRIPTION |
Volt MX Foundry Integration Service is hit from places other than the device. All the mandatory parameters such as- appID, serviceID or both are missing. |
| SEVERITY |
SEVERE |
| REPRODUCE THE ERROR |
Remove the request parameter appID or serviceID while invoking Volt MX Foundry Integration Service. |
| RESOLUTION |
Check the request parameters for mandatory parameter : appID and serviceID. |
| POINT OF CONTACT |
VOLTMX |
| Error 5004 |
|
| MESSAGE |
Processor definition does not exit. |
| DESCRIPTION |
This means that the processor classes (DataChunking, ImageProcessor, ServiceDelegate and so on) are not present in the ControllerDef.xml file. This may lead to loss of functionality. Possible tampering. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Remove the with attribute name "ServiceDelegator" from the ControllerDef.xml file. |
| RESOLUTION |
Check ControllerDef.xml for the processor being invoked and check if it is present and correct. |
| POINT OF CONTACT |
VOLTMX |
| Error 5005 |
|
| MESSAGE |
Cannot load the processor class. |
| DESCRIPTION |
This means that the processor classes (DataChunking, ImageProcessor, ServiceDelegate and so on) present in the ControllerDef.xml file could not be loaded by the JVM. This may lead to loss of functionality. Possible tampering. Check availability of the classes. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Modify the tag with attribute name "ServiceDelegator" and change the classname to "abc.xyz". Since this class is not present, it throws up this error. |
| RESOLUTION |
Check if the middleware-system.jar is present and the processor class is present in that jar. Also, check if no other jar file contains the same class name as this processor class. |
| POINT OF CONTACT |
VOLTMX |
| Error 5006 |
|
| MESSAGE |
Cannot create processor class instance. |
| DESCRIPTION |
This means that the processor classes (DataChunking, ImageProcessor, ServiceDelegate and so on) present in the ControllerDef.xml file cannot be instantiated by the JVM. This may lead to loss of functionality. Possible tampering. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Modify the tag with attribute name "ServiceDelegator" and change the classname to "abc.xyz" where abc.xyz is an interface / abstract class. Since this an interface, it throws up this error. |
| RESOLUTION |
Check if the middleware-system.jar is present and the processor class is present in the jar. Also, check if the processor class being invoked is not an interface / abstract class. |
| POINT OF CONTACT |
VOLTMX |
| Error 5101 |
|
| MESSAGE |
Sequence definition does not exit. |
| DESCRIPTION |
It means that the sequence of processors (as described above) are not present for that particular channel (Native Apps, and Mobile Web). This should be present in the ControllerDef.xml file. This may lead to loss of functionality. Possible tampering. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Remove the with attribute name "default" from the ControllerDef.xml file. |
| RESOLUTION |
Check if the required sequence is present and correctly defined in the controllerDef.xml. |
| POINT OF CONTACT |
VOLTMX |
| Error 5101 |
|
| MESSAGE |
Problem in Creating / Loading the sequence class. |
| DESCRIPTION |
This means that the sequence of processors (as described above) are not loaded for that particular channel (Native Apps, Mobile Web and so on). Check ControllerDef.xml file for the sequence. Check availability of the classes defined. This may lead to loss of functionality. Possible tampering. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Modify the tag with attribute name "default" and change the classname to "abc.xyz". Since this class is not present, this error appears. |
| RESOLUTION |
Check if the sequence class invoked is present in the middleware-system.jar. Check if no other jar file contains the same class name as this processor class. Also, check if there is no IllegalAccessError while instantiating the class. |
| POINT OF CONTACT |
VOLTMX |
| Error 5104 |
|
| MESSAGE |
Metadata mismatch: Either request,session or context data doesnt match with metadata configuration. |
| DESCRIPTION |
Mismatch between the middleware configuration files. |
| SEVERITY |
SEVERE |
| REPRODUCE THE ERROR |
|
| RESOLUTION |
Place correct / updated middleware-bootconfig files at server end. |
| POINT OF CONTACT |
VOLTMX |
| Error 5301 |
|
| MESSAGE |
No Device ID found for . |
| DESCRIPTION |
Fallback device not found. Device database may be corrupt or wrong. The Volt MX Foundry Integration Service is unable to locate the fallback device IDs in the device database. |
| SEVERITY |
SEVERE |
| REPRODUCE THE ERROR |
Remove the entries for 'voltmxua' and 'voltmxrc' in the device database. |
| RESOLUTION |
Check the device database if the fallback rcidentifiers ‘voltmxrc’ and fallback useragent ‘voltmxua’ are present. Also, check the connectivity to the device database. |
| POINT OF CONTACT |
VOLTMX |
| Error 6000 |
|
| MESSAGE |
Session does not exist. |
| DESCRIPTION |
Session does not exist. |
| SEVERITY |
MEDIUM |
| REPRODUCE THE ERROR |
Set the session object to null in the pre-processor. |
| RESOLUTION |
Check the pre-processor. |
| POINT OF CONTACT |
VOLTMX |
| Error 6001 |
|
| MESSAGE |
Session exists (may be newly created) but there are no expected values. |
| DESCRIPTION |
The session exists but the value in the session is null. |
| SEVERITY |
MEDIUM |
| REPRODUCE THE ERROR |
In the service-definition file, change the scope of an input variable to "session" and do not save this value in session in the pre-processor or any previous service. |
| RESOLUTION |
Ensure that the value looked for is present in the session. Check the service-definition file for the particular service and check if the scope of the concerned input variable is correct (It can be session / request). |
| POINT OF CONTACT |
VOLTMX |
| Error 6003 |
|
| MESSAGE |
Mandatory request parameter loop_count or dependant_tag /dependant_value not found in the request. |
| DESCRIPTION |
Looping Connector has a feature to break out the execution of service with dependant_tag / dependant_value / loop_count. |
| SEVERITY |
SEVERE |
| REPRODUCE THE ERROR |
Give empty value in loopingConnector loop_count or dependant_tag / dependant_value in request. |
| RESOLUTION |
Check non empty input params of LoopingConnector loop_count or dependant_tag / dependant_value in request. |
| POINT OF CONTACT |
VOLTMX |
| Error 6004 |
|
| MESSAGE |
Invalid loop count when execution type is concurrent. |
| DESCRIPTION |
Looping Connector has a feature to break out the execution of service with dependant_tag / dependant_value / loop_count. |
| SEVERITY |
SEVERE |
| REPRODUCE THE ERROR |
Give negative value in loopingConnector loop count. |
| RESOLUTION |
Enter a non-negative value for LoopingConnector loopCount. |
| POINT OF CONTACT |
VOLTMX |
| Error 6004 |
|
| MESSAGE |
Unable to instantiate the connector class. |
| DESCRIPTION |
Class names are incorrect. |
| SEVERITY |
SEVERE |
| REPRODUCE THE ERROR |
|
| RESOLUTION |
Check if the class name present in jar file is correct. |
| POINT OF CONTACT |
VOLTMX |
| Error 6005 |
|
| MESSAGE |
Unable to execute services parallely. |
| DESCRIPTION |
When Looping Connector services execute parallely with multiple threads, if any exception occurs, then the error appears. |
| SEVERITY |
SEVERE |
| REPRODUCE THE ERROR |
Looping Connector with more than 10 services wants to execute parallely. |
| RESOLUTION |
Define less than 10 services to execute parallely. |
| POINT OF CONTACT |
VOLTMX |
| Error 7001 |
|
| MESSAGE |
Invalid source to the param . |
| DESCRIPTION |
When the mandatory param is expected from defined source like request / session, if the param is not available, then the error appears. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Invalid template param defined in service definition file for JavaService. |
| RESOLUTION |
Define source of input request or session for param value in JavaService. |
| POINT OF CONTACT |
VOLTMX |
| Error 8004 |
|
| MESSAGE |
Operation invocation problem. |
| DESCRIPTION |
Unable to invoke the method on pre / post processors or the Java services. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Remove the application jar from the application server libraries. |
| RESOLUTION |
Check if the latest application jar is present. Also, check if there is no class conflict in the logs. |
| POINT OF CONTACT |
VOLTMX |
| Error 8005 |
|
| MESSAGE |
Response is empty. |
| DESCRIPTION |
Backend service is returning empty response. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Re-direct the service call to a dummy server that returns an empty response. |
| RESOLUTION |
Check the back-end services if they are up. Check connectivity with the back-end servers. |
| POINT OF CONTACT |
Back-end service provider. |
| Error 8006 |
|
| MESSAGE |
Invalid XML Response. |
| DESCRIPTION |
Check response from back-end server. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Create a dummy service on the back-end server to return a HTTP Response with error codes such as 401/500, it throws up the error. |
| RESOLUTION |
Check response string from back-end servers. A common scenario can be when the back-end server returns an HTTP Response (401/500) for an XML / Soap request. This is treated as invalid by Volt MX Foundry Integration Service. Check if the response from the back-end server is a valid XML or Soap request. |
| POINT OF CONTACT |
Back-end service provider. |
| Error 8007 |
|
| MESSAGE |
Error parsing the XML response. |
| DESCRIPTION |
This error is returned if the Volt MX Foundry Integration Service could not parse the XML with the given XPath. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Provide incorrect XPath to parse the XML response. |
| RESOLUTION |
Check if the XPath matches the XML response returned by the service. |
| POINT OF CONTACT |
VOLTMX |
| Error 8008 |
|
| MESSAGE |
Invalid Result object returned on method invocation. |
| DESCRIPTION |
The object returned after invoking the pre / post processor or the Java service does not cast to com.hcl.voltmx.middleware.dataobject.Result object. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Modify the processor such that it does not return valid Result object. |
| RESOLUTION |
Ensure if proper application.jar is present and is returning proper object. Also, check if there is no class conflict in the logs. |
| POINT OF CONTACT |
VOLTMX |
| Error 8009 |
|
| MESSAGE |
Request unsuccessful, server responded with status code xxx. |
| DESCRIPTION |
If the received status code is not 200, Volt MX Foundry Integration Service throws this error. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Shutdown the service so that a 404 or 500 error is thrown by the server hosting the service. Try to access the service through Volt MX Foundry Integration Service and the error is reproduced. |
| RESOLUTION |
Check if the services are accessible. |
| POINT OF CONTACT |
Back-end service provider. |
| Error 8010 |
|
| MESSAGE |
Operation invocation problem. |
| DESCRIPTION |
Unable to invoke the method Scraper services. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Remove the scraper.jar from the application server libraries. |
| RESOLUTION |
Check if the latest scraper.jar is present. Also, check if there is no class conflict in the logs. |
| POINT OF CONTACT |
VOLTMX |
| Error 8011 |
|
| MESSAGE |
Invalid Result object returned on method invocation. |
| DESCRIPTION |
The object returned after invoking the Scraper service does not cast to com.hcl.voltmx.middleware.dataobject.Result object. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
Modify the Scraper code such that it does not return valid Result object. |
| RESOLUTION |
Ensure if proper scraper.jar is present and returns proper object. Also, check if there is no class conflict in the logs. |
| POINT OF CONTACT |
VOLTMX |
| Error 8013 |
|
| MESSAGE |
Cannot get value for the expression. |
| DESCRIPTION |
The tag is empty for the particular xpath in the response. |
| SEVERITY |
LOW |
| REPRODUCE THE ERROR |
Create a service-output parameter that is not present in the response for that particular service. |
| RESOLUTION |
Check the XML response and the service-definition file to ensure that the tag is parsed for is present in the response. Modify the service-definition file if this is not the case. |
| POINT OF CONTACT |
VOLTMX |
| Error 8018 |
|
| MESSAGE |
Unable to instantiate object. |
| DESCRIPTION |
Unable to invoke the pre / post processors or the Java services. |
| SEVERITY |
LOW |
| REPRODUCE THE ERROR |
Remove the application jar from the application server libraries. |
| RESOLUTION |
Check if the application jar is present. Also, check if there is no class conflict in the logs. |
| POINT OF CONTACT |
VOLTMX |
| Error 8701 |
|
| MESSAGE |
Invalid source to the parameter for . |
| DESCRIPTION |
Incorrect scope (value of 'src') is used for parameters values. |
| SEVERITY |
LOW |
| REPRODUCE THE ERROR |
Provide value other than 'request' or 'session'. |
| RESOLUTION |
Parameter source must be either of 'request', or 'session'. |
| POINT OF CONTACT |
VOLTMX |
| Error 8702 |
|
| MESSAGE |
Request failed with exception:. |
| DESCRIPTION |
Exception occurred while requesting SAP service. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
|
| RESOLUTION |
|
| POINT OF CONTACT |
VOLTMX |
| Error 8703 |
|
| MESSAGE |
Request failed with JCO exception:. |
| DESCRIPTION |
Exception occurred while requesting SAP service. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
|
| RESOLUTION |
|
| POINT OF CONTACT |
VOLTMX |
| Error 8704 |
|
| MESSAGE |
Request failed with ABAP exception:. |
| DESCRIPTION |
Exception occurred while requesting SAP service. |
| SEVERITY |
HIGH |
| REPRODUCE THE ERROR |
|
| RESOLUTION |
|
| POINT OF CONTACT |
VOLTMX |
| Error 8710 |
|
| MESSAGE |
Provide the properties file for connection information. |
| DESCRIPTION |
SAP properties file (sap_.properties) config parameter is missing in the service definition. |
| SEVERITY |
MEDIUM |
| REPRODUCE THE ERROR |
When service does not have properties file in service definition. |
| RESOLUTION |
You need to provide the SAP properties file in the service definition, using 'sapserverfile' config parameter. |
| POINT OF CONTACT |
VOLTMX |
| Error 8711 |
|
| MESSAGE |
Provide 'username' as a request parameter. |
| DESCRIPTION |
The 'username' is missing from the request parameters. |
| SEVERITY |
LOW |
| REPRODUCE THE ERROR |
Do not provide username in the service request. |
| RESOLUTION |
Provide the 'username' through request parameter. |
| POINT OF CONTACT |
VOLTMX |
| Error 8712 |
|
| MESSAGE |
Provide 'password' as a request parameter. |
| DESCRIPTION |
The 'password' is missing from the request parameters. |
| SEVERITY |
LOW |
| REPRODUCE THE ERROR |
Do not provide password in the service request. |
| RESOLUTION |
Supply the 'password' through request parameter. |
| POINT OF CONTACT |
VOLTMX |
| Error 8713 |
|
| MESSAGE |
SAP properties not loaded at server load (SAPConnectorListner in web.xml needs to be enabled). |
| DESCRIPTION |
SAP properties files are not loaded at server start. |
| SEVERITY |
LOW |
| REPRODUCE THE ERROR |
Do not register SAPConnectorListener in web.xml. |
| RESOLUTION |
Register SAPConnectorListner in web.xml. |
| POINT OF CONTACT |
VOLTMX |
| Error 8714 |
|
| MESSAGE |
Error parsing input parameters. |
| DESCRIPTION |
Could not parse the input JSON data supplied. |
| SEVERITY |
MEDIUM |
| REPRODUCE THE ERROR |
Provide invalid JSON data in the service request. |
| RESOLUTION |
Validate the input data JSON format. |
| POINT OF CONTACT |
VOLTMX |
| Error 8715 |
|
| MESSAGE |
An exception occurred while performing auto commit operation (BAPI_TRANSACTION_COMMIT). |
| DESCRIPTION |
Auto commit failed for the given transaction. |
| SEVERITY |
MEDIUM |
| REPRODUCE THE ERROR |
Provide a valid service that is capable of performing autocommit. |
| RESOLUTION |
Check whether the service that you provided supports autocommit or not. |
| POINT OF CONTACT |
VOLTMX |
| Error 8801 |
|
| MESSAGE |
Siebel sessionid is empty, login again. |
| DESCRIPTION |
Siebel session is empty in the request. |
| SEVERITY |
LOW |