The following are the possible exceptions that orchestration activities might throw.
Refer to Orchestration Exception Properties for a description of the properties stored in each exception.
ConnectorException (Code 1000, SubCode 0)
The connection to a server closed. Possible causes are inactivity, server was reset, or a communication error occurred.
UnrecognizedMessageException (Code 1300, SubCode 200)
The message received from the host does not match any ePortal Server Message in the data source project.
To correct this problem, you must create the corresponding server message by importing the correct version of the data description.
Note: This exception only applies to the AB Suite/EAE data source type.
MessageFormatException (Code 1400, SubCode 300)
The message received from the host is not the same version or format as the ePortal Server Message in the data source project.
To correct this problem, you must recreate the corresponding server message by importing the correct version of the data description.
Note: This exception only applies to the AB Suite/EAE data source type.
ConnectorException (Code 2000, SubCode 0)
The server explicitly closed the connection.
ConnectFailedException, ConnectorException (Code 3000)
Code 3000 Subcodes
| Exception SubCode | Message | Additional Explanation if needed |
|---|---|---|
| 0 |
| No available connection. |
| 1 | Incompatible Terminal Services version. |
|
| 2 | Invalid terminal name. |
|
| 3 | Terminal name is in use. |
|
| 4 | Terminal name is not yours. |
|
| 5 | Host Transaction Server is short on resources. |
|
| 6 | Host PCM is in an invalid state. |
|
| 7 | Host PCM is short on resources. |
|
| 8 | Invalid connection attributes. |
|
| 9 | Invalid virtual terminal requested. |
|
| 10 | Product license not available. |
|
| 11 | Product license users exceeded. |
|
| 12 | Product unknown. |
|
| 99 | Connection denied by host. |
|
| 100 | Internal error. |
|
| 101 | Could not open TCP port. |
|
| 102 | The hostname could not be resolved. |
|
| ERROR-MC-01 | McpcobolConnectionProperties is NULL. | Internal Error: There are no connection properties available. Report this problem to the Unisys Support Center. Gather Diagnostics on the current solution. |
| ERROR-MC-02 | WindowName property is NULL | WindowName must be configured in McpcobolConnectionProperties. This is done from the website menu option ClearPath ePortal Application Configuration or from the ePortal Manager if already deployed. |
| ERROR-MC-03 | IOException writing data to Mcpcobol | Internal Error: Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-06 | SocketException while setting SOTimeout | Internal Error: Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-07 | Invalid framing header | Invalid framing header received from MCP Connector PSH. Recreate the problem with ePortal logs set to Verbose and contact the Unisys Support Center with the resulting diagnostics. |
| ERROR-MC-09 | IOException(maybe timeout) reading data from Mcpcobol | IOException(maybe timeout) reading data from Socket. Recreate the problem with ePortal logs set to Verbose and contact the Unisys Support Center with the resulting diagnostics. |
| ERROR-MC-10 | {0} occurred during PhysicalConnection initialization: {1} | Some error occurred while attempting to Connect to the MCP Connector PSH. Recreate the problem with ePortal logs set to Verbose and contact the Unisys Support Center with the resulting diagnostics. |
| ERROR-MC-12 | PhysicalConnection Instance previously destroyed | Internal Error: Internal connection object was previously destroyed. This error can be ignored. |
| ERROR-MC-13 | ResourceException occurred while closing connections | ResourceException occurred while closing connections. A previous error should be reported. Check the ePortal log, or contact the Unisys Support Center with diagnostics gathered for more information. |
| ERROR-MC-17 | Cannot convert from state({0}) to state({1}) | Internal Error: Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-18 | No detailed error information available | Internal error: The Connector PSH returned an error on the Connect or Disconnect that was not recognized by ePortal. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-19 | PSH Version is not supported | Internal Error: The Connector PSH did not recognize the Version sent by ePortal. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-20 | Unable to establish a connection to Mcpcobol. Please check Window Name and Station Name | Unable to establish a connection to Mcpcobol. Please check Window Name and Station Name in the ePortal Application Configuration or using ePortal Manager if the application is already deployed. |
| ERROR-MC-21 | PSH Attribute ({0}) is not supported | Internal Error: The Connector PSH did not recognize the identified attribute sent by ePortal. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-22 | PSH Internal error | Internal Error: The Connector PSH returned an internal error on a connect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-23 | Malformed PSH attribute value ({0}) | Internal Error: The Connector PSH returned this error on a connect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-24 | Missing PSH attribute ({0}) | Internal Error: The Connector PSH returned this error on a connect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-25 | Invalid usercode or password | The usercode or password sent in the Connect_Basic or Connect_AutoLogon server message is not recognized on the MCP server. Check the credentials sent and try again. |
| ERROR-MC-26 | Unexpected PSH attribute: ({0}) | Internal Error: The Connector PSH returned this error on a connect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-27 | Authentication error | The Connector PSH returned this error on a connect request. The request cannot be authenticated. Check the user credentials and try again. |
| ERROR-MC-28 | Malformed message | Internal Error: The Connector PSH returned this error on a connect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-29 | Credentials not supported | Reserved for future use. |
| ERROR-MC-30 | Unsupported PSH attribute version | Internal Error: The Connector PSH returned this error on a connect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-31 | Fully qualified domain name and realm unavailable | Reserved for future use. |
| ERROR-MC-32 | Cleartext password support on PSH is disabled | This error indicates that the Cleartext password support is disabled on the MCP, but sent by ePortal. Check that the security mode chosen for the ePortal application is also enabled in the Connector PSH. |
| ERROR-MC-34 | Mcpcobol attribute not supported ({0}) | Internal Error: The Connector PSH returned this error on a connect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-35 | Unable to validate logon information | Internal Error: The Connector PSH returned this error on a connect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics from ePortal and the Connector PSH and report this problem to the Unisys Support Center. |
| ERROR-MC-36 | PSH does not support attribute ({0}) | Internal Error: The Connector PSH returned this error on a connect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-37 | Unknown CUCI error ({0}) | Internal Error: The Connector PSH returned this error on a disconnect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-38 | Unspecified network error | Internal Error: The Connector PSH returned this error on a disconnect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-39 | Error found within framing header | Internal Error: The Connector PSH returned this error on a disconnect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center |
| ERROR-MC-40 | Error found within framing header fragment | Internal Error: The Connector PSH returned this error on a disconnect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-41 | Message too big | Internal Error: The Connector PSH returned this error on a disconnect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-42 | Protocol error | Internal Error: The Connector PSH returned this error on a disconnect request. Check the version of the Connector PSH on the MCP. Gather all diagnostics and report this problem to the Unisys Support Center. |
| ERROR-MC-43 | PSH shut down for unknown reasons | Internal Error: The Connector PSH returned this error on a disconnect request. Check the Connector PSH on the MCP. Gather all diagnostics from ePortal and the Connector PSH and report this problem to the Unisys Support Center. |
| ERROR-MC-44 | PSH executed a normal shutdown | This error is returned on a disconnect request and indicates that the Connector PSH is shutdown. |
| ERROR-MC-45 | PSH executed a fast shutdown | This error is returned on a disconnect request and indicates that the Connector PSH is shutdown. |
| ERROR-MC-46 | Unsolicited message from Mcpcobol | This error is returned on a disconnect request and indicates that the Connector PSH is not expecting this message from ePortal. |
| ERROR-MC-47 | The connection to Mcpcobol has been terminated | This error is returned on a disconnect request and indicates that the Connector PSH has terminated the connection with ePortal. |
| ERROR-MC-48 | The connection to Mcpcobol has been cleared | This error is returned on a disconnect request and indicates that the Connector PSH has terminated the connection with ePortal. |
| ERROR-MC-49 | The Mcpcobol window closed | This error is returned on a disconnect request and indicates that the MCP Window is closed. |
| ERROR-MC-51 | The Mcpcobol program is unavailable | Check that the MCP COBOL program is enabled. |
| ERROR-MC-52 | The Mcpcobol window is unavailable | Check that the MCP COBOL Window is configured and enabled. |
| ERROR-MC-53 | Duplicate station name | This error is returned on a connect request to indicate that the station name is already in use. Recreate the problem with ePortal Verbose logs set and analyze the log results. |
| ERROR-MC-54 | Invalid window name | The window name sent to the MCP is invalid. Ensure that the window name is configured correctly on both the ePortal side and the MCP. |
| ERROR-MC-55 | Invalid station name or station name prefix | The station name sent on the Connect request is invalid. Check the station name prefix set in the ePortal COBOL configuration. |
| ERROR-MC-57 | PhysicalConnection timed out | The Connection to the MCP timed out. |
Internal Error (cannot be caught by Orchestration) (Code 4000)
| Exception SubCode | Message | Additional Explanation |
|---|---|---|
| 0 | Internal System Error | Internal Error: Gather all diagnostics and report this problem to the Unisys Support Center |
AssignMessageException (Code 5000)
| Exception SubCode | Message | Additional Explanation |
|---|---|---|
| 0 | Invalid cast of Orch.Message | Invalid cast of Orch.Message. Check the orchestration file for a message that has not been cast correctly. |
UnorchestratedMessageException (Code 6000)
| Exception SubCode | Message | Additional Explanation |
|---|---|---|
| 1 | Unorchestrated message received from server. | Determine where the server message should be in the orchestration. |
| 2 | Unorchestrated message received from client. | Determine where the client message should be in the orchestration. |
Also, refer to Using Map and Forward to Simplify Orchestration.
ArithmeticException (Code 7000)
| Exception SubCode | Message | Additional Explanation |
|---|---|---|
| 0 | Dot Net generated text | Arithmetic error, for example, divide by zero. |
NullReferenceException (Code 8000)
| Exception SubCode | Message | Additional Explanation |
|---|---|---|
| 0 | Dot Net generated text | Attempted access of an uninitialized variable or field. |
InvalidCastException (Code 9000)
| Exception SubCode | Message | Additional Explanation |
|---|---|---|
| 0 | Dot Net generated text | Invalid cast of data types. |
ReceiveTimeoutException (Code 10000)
| Exception SubCode | Message | Additional Explanation |
|---|---|---|
| 0 | Message Receive Timeout | A message was not received in an InvokeServer or ReceiveServer activity in the time specified. |
InputDataOverflowException (Code 11000)
| Exception SubCode | Additional Explanation |
|---|---|
| 0 | Indicates that the length of an input value is greater than the size of the record item that will receive the input. This prevents truncation of input being passed to a ClearPath program. |
InvalidCastException (Code 12000)
| Exception SubCode | Additional Explanation |
|---|---|
| 0 | Indicates that a single-byte character was provided as input for a record item declared as USAGE NATIONAL, USAGE KANJI, or USAGE DISPLAY-2. |
InvalidFormatException (Code 13000)
| Exception SubCode | Additional Explanation |
|---|---|
| 1 | Indicates that an attempt was made to set a string type message field to an empty string, but a field value is required. |
| 2 | Indicates that an attempt was made to set a string type message field to a value which does not match the configured pattern. |
OutOfRangeException (Code 14000)
| Exception SubCode | Additional Explanation |
|---|---|
| 0 | Indicates that an attempt was made to set a numeric type message field to a value which is outside the configured range for that field. |