Errors generated by the Java API.
The following table describes the Control‑M/EM API Java client errors:
Minor code |
Severity |
Description |
---|---|---|
1 |
ERROR |
Fatal error |
2 |
ERROR |
Null XML document - nothing to do |
3 |
ERROR |
Failed to establish connection with server - no server registered under this hostname |
4 |
ERROR |
Failed to resolve server name - please check your hostname |
5 |
ERROR |
Failed to establish connection with server - not a valid component type, check your hostname |
6 |
ERROR |
Failed resolving XMLInvoker interface |
7 |
ERROR |
Failed to establish connection with server - check your Web Server. |
8 |
ERROR |
Failed to establish connection with - check your connection configuration. |
9 |
ERROR |
Properties file not found |
10 |
ERROR |
Failed to read properties file |
101 |
ERROR |
Invoke timeout - no response after |
102 |
ERROR |
Invoke request exited because a InterruptedException occurred |
111 |
ERROR |
Response format is not valid |
112 |
ERROR |
Response format is not valid, cannot find rule based calendar |
131 |
ERROR |
XML format is not valid |
132 |
ERROR |
Request format is not valid |
133 |
ERROR |
Cannot find user token |
140 |
ERROR |
Error parsing the XML |
141 |
ERROR |
Undefined Exception on Parser |
Parent Topic |