Incompatible object argument for a function call

Calls may fail when using EMBasicXMLInvoker, but succeed when using EMXMLInvoker if irrelevant libraries in the application class path (CLASSPATH) conflict with libraries that are required by the Control‑M/EM API. For example, a newer or older version of the APACHE Xerces Parser might be found in the CLASSPATH.

Corrective Action: Use one of the following solutions:

• Use the smallest set of classes possible when running the API. Doing so prevents your project from finding irrelevant products and libraries in the CLASSPATH.
• Ensure that the you have listed the required libraries first in the CLASSPATH so that they are found first.