> # 5 Error Messages

> This chapter lists in numerical order error messages you may receive while using SequeLink. Each error message is followed by a description of the error and recommended actions, if applicable.

> 351 | Error detected while processing an administration request.
> | Cause | An administration request could not be processed by the server.
> | Action | Preceding or subsequent messages contain more detailed information.
> 352 | Error detected while processing an administration request.
> | Cause | An administration request could not be processed by the server.
> | Action | Preceding or subsequent messages contain more detailed information.
> 353 | Memory allocation failed while processing an administration request.
> | Cause | A request to the operating system to allocate memory for the SequeLink Server failed.
> | Action | Free memory resources. If the problem persists, contact DataDirect Technologies technical support.
> 354 | An invalid argument is passed to an administration function.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 360 | The requested node cannot be found in the monitor tree.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 361 | Duplicate object identifier in the monitor tree.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 362 | Could not delete the given node because it owns items that have not been deleted.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 370 | The specified entity type does not exist.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 371 | The specified attribute does not exist.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 372 | The specified entity instance could not be found.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 373 | The specified attributes do not match.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 374 | The specified attribute ID is not valid.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 375 | The specified entity type is not valid.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 376 | The specified entity type is read-only.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 377 | The specified configuration file could not be opened.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 378 | The syntax of the configuration file is incorrect.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 379 | An unexpected duplicate entity was detected.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 380 | The required primary key attributes were not provided.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 381 | The provided attribute is a primary key attribute.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 382 | The provided attribute already exists.
> | Cause | An attempt was made to add an attribute that already exists.
> | Action | This error only occurs when multiple SequeLink administrators attempt to add the same attribute to the configuration at the same time. Using the SequeLink Manager, reconnect to the SequeLink Agent service to refresh the SequeLink Manager view of the configuration file. Then, execute the administration task again.
> 383 | The configuration file was changed by someone else.
> | Cause | The configuration file has been modified by another administrator.
> | Action | Reload the configuration file and make the changes again.
> 390 | Received a request to stop listening, ignoring other events on the queue.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 391 | The semaphore operation could not be completed within the timeout period specified.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 392 | Request to send an event failed because there is no listener active on the event queue.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 393 | Request to send an event failed because the event queue is full.
> | Cause | The service could not send the events to the Event Processor because the event queue was full.
> | Action | Increase the value for both or either of the "ServiceEvQShmQSize" and "ServiceEvQShmQMaxResend" service attributes. Refer to the SequeLink Administrator's Guide for information about service attributes.
> 394 | Request to send an event failed because the event size exceeds the maximum event size.
> | Cause | The service could not send the event to the Event Processor because the event queue was too small to hold all the attributes of the event.
> | Action | Increase the value for the "ServiceEvQShmQSize" service attribute. Refer to the SequeLink Administrator's Guide for information about service attributes.
> 395 | Request to create an IPC object failed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 396 | The parameters needed to create an IPC key could not be found in the configuration file.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 397 | A call to ftok failed. Check if the file xxx exists and is readable.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 398 | Request to create or attach to shared memory (key=xxxx) failed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 399 | Request to create a semaphore (key=xxxx) failed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 400 | Request to create a message queue (key=xxxx) failed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 401 | Failed to terminate the event queue cache because it is not empty.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 410 | The specified parameter (xxxx) is invalid.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 411 | The attribute xxx is not found in the attribute list of the event that is being processed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 412 | The specified attribute (ID=xxxx) has an incorrect type.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 413 | Failed to evaluate the profile filter expression for event with ID=xxxx.
> | Cause | The specified profile filter is not valid.
> | Action | Correct the syntax of the profile filter.
> 414 | Profile filter evaluation failed because the expressions have incompatible types.
> | Cause | The specified profile filter is not valid.
> | Action | Correct the syntax of the profile filter.
> 415 | Failed to parse the expression because of a syntax error at position xxxx.
> | Cause | The specified profile filter is not valid.
> | Action | Correct the syntax of the profile filter.
> 416 | Failed to parse the profile filter expression.
> | Cause | The specified profile filter is not valid.
> | Action | Correct the syntax of the profile filter.
> 417 | The provided monitor path (xxxx) is invalid.
> | Cause | The specified profile filter is not valid.
> | Action | Correct the syntax of the profile filter.
> 418 | The specified action (xxxx) is not a valid event profile action.
> | Cause | The specified profile filter is not valid.
> | Action | Correct the syntax of the profile filter.
> 419 | An invalid parameter value (xxxx) was specified.
> | Cause | The specified profile filter is not valid.
> | Action | Correct the syntax of the profile filter.
> 420 | The specified event profile action (xxxx) failed to parse.
> | Cause | The specified profile filter is not valid.
> | Action | Correct the syntax of the profile filter.
> 421 | Failed to load profile with ID=xxxx.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 430 | Failed to open event trace file because the file version was not recognized.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 431 | Failed to resize the event trace file.
> | Cause | An attempt to resize the event trace file failed, probably because SequeLink Server was restarted with a new value for the "ServiceEventTraceSize" service attribute that may be too large.
> | Action | Make sure that there is enough disk space available for the event trace file, which can be found at the location specified by the "ServiceEventTraceLocation" service attribute.
> 432 | The request could not be completed because the event trace is in an error state.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 433 | Failed to open the event trace file.
> | Cause | The event trace file could not be opened during service startup because the SequeLink service was not stopped properly, for example, because the server machine failed or the SequeLink service was terminated with an operating system command while it was processing events.
> | Action | Delete the event trace file. Then, re-start the service.
> 434 | Failed to open the event trace file because event tracing was not stopped cleanly.
> | Cause | The event trace file has been left in an inconsistent state and can no longer be used.
> | Action | Delete the event trace file. Before deleting, make sure SequeLink services are stopped using the SequeLink Manager.
> 435 | The event trace file is corrupt.
> | Cause | An inconsistency was detected within the event trace file.
> | Action | Delete the event trace file. If the problem persists, contact DataDirect Technologies technical support.
> 436 | Failed to open file to export.
> | Cause | The specified export file cannot be opened.
> | Action | Verify the reason reported by the operating system.
> 437 | Failed to close file to export.
> | Cause | An error was encountered when closing the specified export file.
> | Action | The contents of the specified export file may be corrupted; use another export file.
> 1000 | System Exception: {0}.
> | Cause | An unexpected error occurred.
> | Action | Check the system exception {0} for more information. If necessary, contact DataDirect Technologies technical support.
> 1001 | No more data available to read.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 1002 | End of stream was detected on a read.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 1003 | Error opening/loading com.ddtek.util.transliteration.properties.
> | Cause | An unexpected error occurred while accessing the transliteration properties file.
> | Action | Contact DataDirect Technologies technical support.
> 1004 | Resource com.ddtek.util.transliteration.properties is corrupt.
> | Cause | An unexpected error occurred while accessing the transliteration properties file.
> | Action | Contact DataDirect Technologies technical support.
> 1005 | Transliteration table {0} not found.
> | Cause | The SequeLink Server uses a Code page that is currently not supported by the SequeLink Client.
> | Action | Contact DataDirect Technologies technical support.
> 1006 | Transliteration class {0} not found.
> | Cause | The SequeLink Server uses a Code page that is currently not supported by the SequeLink Client.
> | Action | Contact DataDirect Technologies technical support.
> 1007 | Unsupported VM encoding {0}.
> | Cause | The SequeLink Server uses a Code page that is currently not supported by the SequeLink Client.
> | Action | Contact DataDirect Technologies technical support.
> 1008 | Transliteration table {0} is corrupt.
> | Cause | An unexpected error occurred while accessing the transliteration table.
> | Action | Contact DataDirect Technologies technical support.
> 1009 | Transliteration failed.
> | Cause | An unexpected error occurred while transliterating the String.
> | Action | Contact DataDirect Technologies technical support.
> 1010 | Invalid transliteration class {0}.
> | Cause | An unexpected error occurred while accessing the transliteration table.
> | Action | Contact DataDirect Technologies technical support.
> 1011 | Character set {0} not found in com.ddtek.util.transliteration.properties.
> | Cause | The SequeLink Server uses a Code page that is currently not supported by the SequeLink Client.
> | Action | Contact DataDirect Technologies technical support.
> 1012 | IO Error creating temp file: {0}
> | Cause | An unexpected error occurred while creating a temporary file.
> | Action | Check the IO-exception {0} for more information. If necessary, contact DataDirect Technologies technical support.
> 1013 | IO Error writing temp file: {0}
> | Cause | An unexpected error occurred while writing a temporary file.
> | Action | Check the IO-exception {0} for more information. If necessary, contact DataDirect Technologies technical support.
> 1014 | IO Error reading temp file: {0}
> | Cause | An unexpected error occurred while reading a temporary file.
> | Action | Check the IO-exception {0} for more information. If necessary, contact DataDirect Technologies technical support.
> 1015 | IO Error reading temp file: {0}
> | Cause | An unexpected error occurred while reading a temporary file.
> | Action | Check the IO-exception {0} for more information. If necessary, contact DataDirect Technologies technical support.
> 1016 | Error fetching data from temp buffer
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 1017 | The object is closed
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 1018 | {0}
> | Cause | An unexpected error occurred. At runtime, an error message from the JDK will be displayed.
> | Action | Contact DataDirect Technologies technical support.
> 1019 | Error attempting to backup position in data stream
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 1020 | Error establishing socket. {0}
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 1021 | Error establishing socket. Unknown host: {0}
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 1201 | JDBC driver error: execute() returned true, but getResultSet() returned null.
> | Cause | A JDBC driver error occurred.
> | Action | Contact DataDirect Technologies technical support or the technical support of the JDBC driver vendor.
> 1202 | java.sql.ResultSetMetaData.isNullable(int column) returns invalid value.
> | Cause | A JDBC driver error occurred. The driver returned a value not defined in the JDBC specification.
> | Action | Contact DataDirect Technologies technical support or the technical support of the JDBC driver vendor.
> 1203 | java.sql.ResultSetMetaData.isNullable(int param) returns invalid value.
> | Cause | A JDBC driver error occurred. The driver returned a value not defined in the JDBC specification.
> | Action | Contact DataDirect Technologies technical support or the technical support of the JDBC driver vendor.
> 1204 | Java Virtual Machine initialization failed.
> | Cause | The DataDirect 32-BIT ODBC2JDBC driver could not initialize the Java Virtual Machine.
> | Action | Contact DataDirect Technologies technical support.
> 1205 | JNI function AttachCurrentThread() failed.
> | Cause | The DataDirect 32-BIT ODBC2JDBC driver could not attach the current thread to a Java Native Interface (JNI) thread context.
> | Action | Contact DataDirect Technologies technical support.
> 1206 | An exception occurred in the JDBC driver, but the ODBC2JDBC driver could not retrieve the exception from the JVM.
> | Cause | A Java Virtual Machine error occurred. An exception was thrown by the Java Virtual Machine, but the JNI failed to retrieve it.
> | Action | If you consider the error fatal, contact DataDirect Technologies technical support.
> 1207 | Unsupported SQL type.
> | Cause | A JDBC driver error occurred. The driver returned a value not defined in the JDBC specification.
> | Action | Contact DataDirect Technologies technical support or the technical support of the JDBC driver vendor.
> 1208 | Statement is not a stored procedure, but output parameters are bound.
> | Cause | An application logic error is the most likely cause.
> | Action | Modify the application. Do not bind output parameters with simple Select, Insert, Delete, or Update statements.
> 1209 | Statement is in an inconsistent state.
> | Cause | An application logic error is the most likely cause, and earlier errors reported by the DataDirect 32-BIT ODBC2JDBC driver were ignored.
> | Action | Check the logic of your application and respond properly to earlier reported errors.
> 1210 | DatabaseProperties not found, defaults will be used.
> | Cause | The application specified "DatabaseProperties=xxx" in the connection URL; however, the corresponding properties file XXX.PROPERTIES could not be loaded.
> | Action | Ensure the properties file XXX.PROPERTIES referred by "DatabaseProperties=xxx" is installed.
> 2200 | Network problem, local timeout during session setup, connection closed.
> | Cause | The session connection handshake could not be completed within the time limit set.
> | Action | Make sure that you are connecting to a SequeLink 5.x Server or higher. If the problem persists, increase the connection timeout value.
> 2201 | Network problem, remote timeout during session setup, connection closed.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2202 | Network resource problem, session aborted due to local buffer allocation failure, connection closed.
> | Cause | The SequeLink Client could not allocate internal buffers to read the reply sent from the SequeLink Server. The session was aborted and the connection was closed.
> | Action | Free memory resources. If the problem persists, contact DataDirect Technologies technical support.
> 2203 | Network resource problem, session aborted due to remote buffer allocation failure, connection closed.
> | Cause | The SequeLink Server could not allocate internal buffers to read the request coming from the SequeLink Client. The session was aborted and the connection was closed.
> | Action | Free memory resources. If the problem persists, contact DataDirect Technologies technical support.
> 2204 | Internal network error, session aborted due to local session protocol error, connection closed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2205 | Internal network error, session aborted due to remote session protocol error, connection closed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2206 | Network problem, cancel not allowed.
> | Cause | The cancel feature was disabled by the SequeLink service.
> | Action | If needed, the cancel feature can be enabled by setting the service attribute ServiceCancelEnabled=TRUE. For information about the "ServiceCancelEnabled" service attribute, refer to the SequeLink Administrator's Guide.
> 2207 | Internal network error, session aborted due to session protocol data unit format error, connection closed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2208 | Internal network error, session aborted, connection closed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2209 | Network problem, no pending request to cancel.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2211 | Network problem, cancel not possible because session is killed.
> | Cause | The cancel operation failed because the session was killed on the SequeLink Server. The connection was closed.
> | Action | Contact DataDirect Technologies technical support.
> 2213 | Internal network error, connection closed because session key not found in remote session list.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2215 | Network problem, cancel failed because all transport channels in use on remote session.
> | Cause | The cancel operation failed because the previous cancel request did not release all its resources on the SequeLink Server.
> | Action | Contact DataDirect Technologies technical support.
> 2217 | Network problem, session aborted due to internal error in remote procedure call, connection closed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2219 | Network problem, invalid IIOP object key, connection closed.
> | Cause | The SequeLink service the SequeLink Client is connected to did not accept the IIOP object key sent.
> | Action | Contact DataDirect Technologies technical support.
> 2221 | Network problem, invalid IIOP operation target, connection closed.
> | Cause | The SequeLink service the SequeLink Client is connected to did not accept the IIOP operation target sent.
> | Action | Contact DataDirect Technologies technical support.
> 2223 | Internal network error, session aborted due to remote procedure call failure, connection closed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2249 | Internal network error.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2251 | Connection closed due to session kill.
> | Cause | The session was killed on the SequeLink Server. The connection was closed.
> | Action | None.
> 2252 | Connection closed due to service shutdown.
> | Cause | The session was killed on the SequeLink Server because the SequeLink service was shutting down.
> | Action | None.
> 2253 | Connection closed, non SequeLink IIOP user exception received.
> | Cause | An IIOP user exception reply was received from a server that was not a SequeLink Server. The session was aborted, and the connection was closed.
> | Action | Contact DataDirect Technologies technical support.
> 2254 | Connection closed, non SequeLink IIOP system exception received.
> | Cause | An IIOP system exception reply was received from a server that was not a SequeLink Server. The session was aborted, and the connection was closed.
> | Action | Contact DataDirect Technologies technical support.
> 2255 | Connection closed, non SequeLink IIOP message format error received.
> | Cause | An IIOP message format error was received from a server that was not a SequeLink Server. The session was aborted, and the connection was closed.
> | Action | Make sure the client application is connecting to a SequeLink Server. If the problem persists, contact DataDirect Technologies technical support.
> 2300 | Network problem, connection unexpectedly closed by peer.
> | Cause | The server closed the transport connection. If logging was enabled, the message `give up waiting for incomplete record` will be recorded in the service debug log file. This error can occur when the server does not recognize the handshake request.
> | Action | Make sure the client application is connecting to a SequeLink Server. If the problem persists, contact DataDirect Technologies technical support.
> 2302 | TCP/IP error, the remote host cannot be reached from this host at this time.
> | Cause | TCP/IP cannot establish a connection with the SequeLink Server host because no route to the SequeLink Server was found.
> | Action | Make sure that: The network configuration is correct A network route to the SequeLink Server is available The SequeLink Server is active Try another TCP/IP network application to verify whether the server is reachable.
> 2303 | TCP/IP error, the network is not reachable from this host.
> | Cause | TCP/IP cannot establish a connection with the SequeLink Server host because no route can be found to the network on which the host resides.
> | Action | Make sure that: The network configuration is correct A network route to the SequeLink Server is available The SequeLink Server is active Try another TCP/IP network application to verify whether the server is reachable.
> 2304 | TCP/IP error, network subsystem down.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2305 | TCP/IP resource problem.
> | Cause | A network operation failed because TCP/IP had insufficient resources.
> | Action | Check for heavy traffic conditions on the server.
> 2306 | TCP/IP error, connection refused.
> | Cause | There was no process waiting for connections on the SequeLink Server host at the specified port or the SequeLink Server was experiencing too many simultaneous connection attempts.
> | Action | Contact DataDirect Technologies technical support.
> 2307 | TCP/IP error, the specified address is already in use.
> | Cause | TCP/IP resource problem. A connection failed because all ports were being used.
> | Action | Re-attempt the connection when more network resources are available.
> 2308 | TCP/IP error, connection timed out.
> | Cause | The connection has been closed because no response was received. The network may have gone down without notice, the client/server host was unreachable, or the SequeLink Server was experiencing too many simultaneous connection attempts.
> | Action | Check for heavy traffic conditions on the server.
> 2309 | Network problem, could not load transport manager.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2310 | TCP/IP error, connection reset by peer.
> | Cause | The connection was closed by the peer. When the specified port is serviced by a non-SequeLink Server, this warning message can occur if the server goes down while trying to process a handshake request.
> | Action | Check the server logs. If the failure was caused by the SequeLink Server stopping unexpectedly, contact DataDirect Technologies technical support.
> 2311 | TCP/IP network error, connection closed.
> | Cause | An unexpected TCP/IP error occurred. The connection was closed.
> | Action | Contact DataDirect Technologies technical support.
> 2312 | Network problem, connection closed due to idle event on transport endpoint not linked to session.
> | Cause | A connection was established with the SequeLink Server, but no data was received by the SequeLink Server within the keep alive time frame. The connection was closed.
> | Action | Increase the keep alive setting on the server.
> 2313 | Network resource problem, connection closed due to buffer allocation problem.
> | Cause | A request to the operating system to allocate memory failed.
> | Action | Free memory resources. If the problem persists, contact DataDirect Technologies technical support.
> 2314 | Internal network problem, connection closed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2315 | Network problem, unknown session conversation protocol.
> | Cause | An attempt was made to connect to a SequeLink Server with an incompatible version of SequeLink.
> | Action | Check the version of the SequeLink Server to make sure it is compatible with the current version of the installed SequeLink software. If the problem persists, contact DataDirect Technologies technical support.
> 2318 | Network problem, connection time out.
> | Cause | The TCP/IP connection could not be established within the set time limit.
> | Action | Increase the time interval and try again to connect.
> 2320 | Network problem, connection time out.
> | Cause | The TCP/IP connection to the server host could not be established within the set time limit.
> | Action | Increase the time interval and try again to connect.
> 2321 | Network problem, listener could not be started because port is already in use.
> | Cause | The port specified for the SequeLink service was being used by another application.
> | Action | Stop the application that is using the port or reconfigure the SequeLink service to use another port.
> 2402 | Session refused, service is shutting down, connection closed.
> | Cause | The requested session was not accepted because the service was shutting down.
> | Action | None.
> 2403 | Network resource problem, session refused, connection closed.
> | Cause | The SequeLink Server failed to allocate a network resource.
> | Action | Check for heavy traffic conditions on the server.
> 2404 | Session refused by service, connection closed.
> | Cause | The server process was unable to accept the connection request.
> | Action | Check the service debug log file or event trace file for details.
> 2405 | Network resource problem, session refused, connection closed.
> | Cause | The SequeLink Server failed to allocate a network resource.
> | Action | Check for heavy traffic conditions on the server.
> 2406 | Session refused, service process could not be spawned, connection closed.
> | Cause | The service process launch failed.
> | Action | Check the service debug log file or the system log facility for the specific problem.
> 2450 | Invalid host, no leading blanks allowed.
> | Cause | The specified host name starts with a blank character. Blank characters, including leading or trailing blanks, are not allowed in the host name.
> | Action | Specify the correct host name, making sure not to include a blank character at the beginning of the name.
> 2451 | Invalid port, no trailing blanks allowed.
> | Cause | The specified port ends with a blank character. Blank characters, including leading or trailing blanks, are not allowed in the port.
> | Action | Specify the correct port, making sure not to include any trailing blank characters.
> 2452 | Invalid host or port, no blanks allowed.
> | Cause | The specified host or port contained a blank character. Blank characters, including leading or trailing blanks, are not allowed in the host name or port.
> | Action | Specify the correct host name or port, making sure it does not contain any blank characters.
> 2453 | Invalid port, number out of range.
> | Cause | The specified port number exceeds the maximum value of 32768.
> | Action | Specify the correct port using a valid port value.
> 2454 | Internal network error during parsing host and port.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2455 | Internal network error, missing separator.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2456 | Invalid host or number, `:' character not allowed.
> | Cause | The host name or number included a colon (:).
> | Action | Specify the correct host name or number without a colon.
> 2457 | Invalid host, `:' character not allowed.
> | Cause | The host name included a colon (:).
> | Action | Specify the correct host name without a colon.
> 2458 | Invalid port, `:' character not allowed.
> | Cause | The port included a colon (:).
> | Action | Specify the correct port without a colon.
> 2459 | Internal network error during parsing host and port.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2460 | Internal network error during parsing host and port.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2461 | Invalid port, numerical value < 0 is not allowed.
> | Cause | An invalid port number was specified.
> | Action | Specify the correct port using a valid value.
> 2462 | Invalid port, numerical equal to 0 is not allowed.
> | Cause | An invalid port number was specified.
> | Action | Specify the correct port using a valid value.
> 2463 | Host name or service name too long.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2464 | Internal network error during parsing host and port.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2465 | Internal network error during parsing host and port.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2466 | Network resource problem, memory allocation failure during parsing host and port.
> | Cause | A system resource was not allocated while parsing the value provided for the host or port.
> | Action | Free memory resources. If the problem persists, contact DataDirect Technologies technical support.
> 2467 | Internal network error during parsing host and port.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2468 | Internal network error, no host and port specified.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 2469 | Network problem, host resolution failure.
> | Cause | The specified server host name could not be resolved to a valid IP address.
> | Action | Map the server host name to a valid IP address.
> 2470 | Network problem, port resolution failure.
> | Cause | The service name could not be resolved to a port number.
> | Action | Check the TCP/IP services configuration file.
> 3001 | Internal error, memory allocation failed.
> | Cause | Memory allocation error.
> | Action | Free memory resources. If the problem persists, contact DataDirect Technologies technical support.
> 3002 | Internal error, corrupt context.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3003 | Internal error, invalid request received from the client application.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3004 | Internal error, an unexpected exception was detected.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3005 | Internal error, a fatal server error was detected.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3006 | Internal error, a fatal error was detected during event processing.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3007 | Internal error, an invalid argument was specified.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3008 | OSLogon authentication mechanism requires root privilege.
> | Cause | An attempt was made to authenticate a connection to a UNIX SequeLink Server using the OSLogon mechanism, but the UNIX SequeLink Server is not running as root.
> | Action | Make sure that the UNIX SequeLink Server is running as root.
> 3009 | Authentication failed.
> | Cause | The "ServiceDetailedOSLogonErrors" service attribute is set to FALSE and the OSLogon authentication process detected an error.
> | Action | Correct the authentication information, typically the user name or password. If the problem persists, contact your system administrator to find out why the specified user is not allowed access to the server.
> 3010 | Could not create a log file in ServiceDebugLogPath.
> | Cause | A session Debug Log File could not be created.
> | Action | Verify that the UNIX System Services HFS directory specified in the "ServiceDebugLogPath" service attribute exists, and the Userid of the Server has authorization to create a file in this directory. Refer to the SequeLink Administrator's Guide for information about service attributes. In addition, check whether the file system is full.
> 3011 | Unable to find the specified session in the list of active sessions while processing the kill session request.
> | Cause | The service received a session ID of a non-existing session.
> | Action | None.
> 3012 | Configuration file was changed by someone else.
> | Cause | The configuration file has been modified by another administrator.
> | Action | Reload the configuration file and make the changes again.
> 3013 | The value for maximum number of threads (maxv) exceeds the OS defined limit (maxosv), maximum threads downgrading to OS limit.
> | Cause | The value of the ServiceMaxThreads service attribute is higher than the operating system allows. The service will only use the number of threads allowed by the operating system.
> | Action | Correct the value of the "ServiceMaxThreads" service attribute.
> 3014 | The value for minimum number of threads (maxv) exceeds the value for maximum number of threads (minv), downgrading min to max value.
> | Cause | The value of the ServiceMinThreads service attribute is higher than the value of the ServiceMaxThreads service attribute. The service will use the value of the ServiceMaxThreads service attribute as the value for the minimum number of threads.
> | Action | Correct the value of the "ServiceMinThreads" service attribute. Refer to the SequeLink Administrator's Guide for information about service variables.
> 3016 | Unable to configure enough threads (6) for the thread pool.
> | Cause | The value of the ServiceMinThreads service attribute is not a valid value. The service will not start.
> | Action | Make sure that the value of the "ServiceMinThreads" service attribute is at least 6. Refer to the SequeLink Administrator's Guide for information about service variables.
> 3017 | Error writing to trace file.
> | Cause | No data can be written to the session debug log file, probably because the file system is full.
> | Action | Remove old files on the full file system.
> 3021 | Internal error, unable to load the server configuration file.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3025 | Internal error, unable to locate settings for service xxxx in the server configuration file (xxxx).
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3043 | Internal error, event trace information is not available from a service with a process based connection model.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3044 | The configured debug log path for the service is not valid.
> | Cause | The directory specified by the "ServiceDebugLogPath" service attribute is not accessible.
> | Action | Make sure the specified directory exists and is accessible.
> 3045 | The server listener component ran out of network resources.
> | Cause | The SequeLink Server was unable to accept a new connection request because of insufficient network resources. The SequeLink Server will wait 1 second before accepting new SequeLink Client connections.
> | Action | Re-attempt the connection.
> 3046 | Internal error, unable to access the monitor tree.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3047 | Invalid table type filter is configured.
> | Cause | The value set for the DataSourceTableTypeFilterList service attribute is not valid.
> | Action | Specify a valid value for the "DataSourceTableTypeFilterList" service attribute. For information about valid values for SequeLink service attributes, refer to the SequeLink Administrator's Guide.
> 3048 | Internal error, failed to initialize the event trace component.
> | Cause | The service failed to start because the event trace component did not initialize correctly.
> | Action | Make sure that: The event trace file is not being used by another application The directory specified by the "ServiceEventTraceLocation" service attribute exists and is accessible There is enough disk space If the problem persists, contact DataDirect Technologies technical support.
> 3049 | Only select statements are allowed in this read-only connection.
> | Cause | The value for the DataSourceReadOnly service attribute was set to "select", and the application tried to execute a statement that was not a Select statement.
> | Action | Change your application, or change the "DataSourceReadOnly" service attribute to accept statements other than Select statements.
> 3050 | Internal error, an invalid action parameter was detected while processing a monitor request.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3051 | Due to a fatal error condition with the DBMS session, no new request can be processed.
> | Cause | A serious error has previously occurred within the DBMS session.
> | Action | The client application must disconnect.
> 3052 | Maximum cputime limit has been exceeded.
> | Cause | The session has exceeded its maximum CPU time, no more request are allowed.
> | Action | The client application must disconnect.
> 3053 | Only select and batch statements are allowed in this read-only connection.
> | Cause | The DataSourceReadOnly service attribute was set to "select and batches", and the application tried to execute a statement that was not a Select statement or a Batch statement.
> | Action | Change your application, or change the "DataSourceReadOnly" service attribute. For information about valid values for SequeLink service attributes, refer to the SequeLink Administrator's Guide.
> 3054 | Found syntax error(s) within the DataSourceSessionToken attribute.
> | Cause | Syntax error in DataSourceSessionToken attribute.
> | Action | Verify that the "DataSourceSessionToken" attribute contains valid placeholders.
> 3055 | Found syntax error(s) within the DataSourceAutoApplId attribute.
> | Cause | Syntax error in one of the DataSourceAutoApplId attribute entries.
> | Action | Verify that the syntax of the "DataSourceAutoApplId" attribute is correct. It must contain exactly 40 hexadecimal digits.
> 3056 | A batch cannot contain SQL statements that return a result set.
> | Cause | A batch cannot contain SQL statements that return a result set.
> | Action | Check your JDBC application. Make sure that only row count generating statements are used in a batch.
> 3057 | Internal error, the monitor request could not be processed because a required action parameter was not provided.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3058 | Internal error, error detected in the event processor.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3059 | The specified data source is not defined.
> | Cause | The specified server data source is not a valid data source for the specified SequeLink service.
> | Action | Specify a valid server data source for the SequeLink service.
> 3060 | Internal error, the specified authentication mechanism is not accepted.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3061 | Authorization failure.
> | Cause | The "ServiceAuthMethods" or "ServiceAdminAuthMethods" service attributes (in combination with the "ServiceUser" or "ServiceAdministrator" attributes, respectively) do not allow the user to perform the requested action.
> | Action | Contact your SequeLink administrator for details.
> 3062 | Internal error, unknown provide ID.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3063 | Maximum number of shared counter instances reached.
> | Cause | SequeLink was unable to export monitoring data for a new session to the Windows performance monitor because the shared counter memory was full. The size of the shared counter memory is configured by the ServiceEvQShmMonitorSize service attribute.
> | Action | Increase the shared counter memory by changing the "ServiceEvQShmMonitorSize" service attribute. For information about valid values for SequeLink service attributes, refer to the SequeLink Administrator's Guide.
> 3064 | Internal error, an invalid monitor object was specified while processing an event.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3065 | Save operation not allowed, file allocation status or file organization incorrect.
> | Cause | A remote SequeLink Agent tried to save changes, and the SequeLink Server was started with a SWANDD Data Definition that specified an incorrect file allocation status or file organization.
> | Action | Correct the SWANDM Data Definition in the server JCL (use DISP=OLD). Verify that the SequeLink configuration file has a sequential file organization. Then, restart the SequeLink Server.
> 3066 | Configuration file is in use by another connection, please retry.
> | Cause | An attempt to update the SequeLink configuration file was refused because another SequeLink Manager application has locked the SequeLink configuration file.
> | Action | Wait for the other SequeLink Manager application to release the lock on the SequeLink configuration file. Then, re-attempt the SequeLink Manager operation.
> 3067 | The user password was changed successfully.
> | Cause | An informational message was generated when the server password of the user was successfully changed.
> | Action | None.
> 3068 | The application specified an invalid application identifier.
> | Cause | The application ID specified by the application is not recognized by the SequeLink service.
> | Action | Make sure that the application is specifying the correct application ID, or change the DataSourceAutoApplId service attribute of the SequeLink service to accept the application ID. For information about application IDs or changing SequeLink service attributes, refer to the SequeLink Administrator's Guide.
> 3069 | The application failed to specify a valid application identifier.
> | Cause | Because the application did not provide a valid application ID, client requests will be refused.
> | Action | Make sure that the application is specifying the correct application ID, or change the "DataSourceApplID" service attribute of the SequeLink service to accept the application ID. For information about application IDs or changing SequeLink service attributes, refer to the SequeLink Administrator's Guide.
> 3070 | License verification failed.
> | Cause | The SequeLink Server could not locate the required license to execute the client request. The request is refused.
> | Action | Make sure a valid SequeLink license is registered. If the problem persists, contact DataDirect Technologies technical support.
> 3071 | Maximum number of sessions reached.
> | Cause | The number of active sessions is exceeding the value of the configuration parameter. Incoming client connection requests are denied.
> | Action | None.
> 3078 | Internal error, invalid search argument type specified.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3079 | Cannot initialize the ICU translator.
> | Cause | The ICU translator could not be initialized because one of the codepages is not supported by the ICU.
> | Action | Use an ICU supported codepage. If the problem persists, contact DataDirect Technologies technical support.
> 3080 | Service configuration error, the ServiceCodepage configuration setting has an incorrect value.
> | Cause | The current ServiceCodePage setting is not allowed.
> | Action | Change the setting of the "ServiceCodePage" service attribute. If the problem persists, contact DataDirect Technologies technical support.
> 3081 | Accessing a SequeLink service configured with ServiceCodepage = Database requires SequeLink client version 5.4 or higher.
> | Cause | The connection is using an unsupported version of the SequeLink Client.
> | Action | Upgrade the SequeLink Client to Version 5.4 or higher. If the problem persists, contact DataDirect Technologies technical support.
> 3082 | Access to datasource is disabled.
> | Cause | Access to the data source is rejected as specified in DataSourceEnableAccess. Refer to the SequeLink Administrator's Guide for more information on the DataSourceEnableAccess service attribute.
> | Action | If access is needed, contact your SequeLink administrator to change the "DataSourceEnableAccess" setting.
> 3084 | This system includes a licensed version of DataDirect SequeLink which may run on systems that include up to XX processors. The current system is configured with YY processors. Please contact DataDirect within the next 15 days to upgrade the license.
> | Cause | The number of processors detected on the current system has been changed.
> | Action | Contact DataDirect Technologies within the next 15 days to upgrade the license.
> 3085 | The SequeLink features that you've licensed are running in evaluation mode and will expire.
> | Cause | Some client components are running in evaluation mode and will expire.
> | Action | Contact DataDirect Technologies to obtain a permanent license.
> 3101 | Error detected while processing an administration request.
> | Cause | The administration request could not be processed by the SequeLink Server.
> | Action | Preceding or subsequent messages contain more detailed information.
> 3102 | An invalid argument was detected while processing an administration request.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3103 | Unexpected error detected while processing an administration request.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3104 | The requested administration function is not implemented on this platform.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3105 | Memory allocation failed while processing an administration request.
> | Cause | A request to the operating system to allocate memory for the SequeLink Server failed.
> | Action | Free memory resources. If the problem persists, contact DataDirect Technologies technical support.
> 3106 | A collection library function failed while processing an administration request.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3107 | An operation on the server configuration file failed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3108 | An operation on the NT registry failed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3110 | Failed to open the server configuration file for reading.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3111 | Failed to open the server configuration file for writing.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3112 | Failed to open the server configuration file because its syntax is incorrect.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3113 | Failed to open the server configuration file because the file does not exist.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3114 | Failed to save the server configuration file.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3115 | Failed to save the server configuration file because the file backup failed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3116 | Failed to attach to the event queue.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3117 | Failed to send event to event queue.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3118 | Failed to access the event queue.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3119 | Failed to send an event because a wait operation timed out.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3120 | Failed to process the administration request because the specified handle has not been opened.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3122 | Failed to process the administration request because the version of the configuration file is not supported by this version of SequeLink.
> | Cause | An attempt was detected to open a SequeLink configuration file with a SequeLink version that is incompatible with the current version of the installed SequeLink software.
> | Action | Use a compatible version of the installed SequeLink software to open the SequeLink configuration file.
> 3130 | Failed to process to remote administration request.
> | Cause | The administration request could not be processed by the server.
> | Action | Preceding or subsequent messages contain more detailed information.
> 3131 | The requested entity was not found in the server configuration file.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3132 | The requested attribute was not found in the server configuration file.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3133 | The specified attribute ID is not valid.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3134 | An unexpected duplicate entity was detected.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3137 | [swadm] Failed to open the Service Control Manager.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3138 | Failed to open the specified OS service.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3139 | Failed to create the specified OS service.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3140 | Failed to delete the specified OS service.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3141 | Failed to unregister the OS service because it is not stopped.
> | Cause | An attempt to delete or unregister a service that is still active was detected.
> | Action | If the SequeLink Manager lists the SequeLink service as inactive, the SequeLink service may be in the process of stopping. Wait for the SequeLink service to stop completely and retry.
> 3142 | Failed to register the specified OS service because the service already exists.
> | Cause | An attempt was made to register a SequeLink service with a name that was already used by another operating system service.
> | Action | Make sure the name you choose for your SequeLink service is not being used by another operating system service.
> 3143 | The required primary key attributes were not provided.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3144 | Requested operation on the specified OS service failed because a wait operation timed out.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3145 | The TCP port for the service could not be registered because it is registered for another network service.
> | Cause | The SequeLink service is configured to use a TCP/IP port that is registered for another network service on the machine. If the other service is active, it will not be possible to start the SequeLink service.
> | Action | If you are confident that the network service for which the port was registered will never be active at the same time as the SequeLink service you created, you can continue. If unsure, change the TCP/IP port for the SequeLink service.
> 3146 | The TCP port for the service could not be registered/unregistered because the services file could not be opened.
> | Cause | The %SystemRoot%\system32\drivers\etc\services file (Windows) or the /etc/services file (UNIX) could not be opened.
> | Action | Contact your system administrator. If the problem persists, contact DataDirect Technologies technical support.
> 3147 | The TCP port for the service could not be registered/unregistered because the services file could not be accessed.
> | Cause | A file input/output error was detected while accessing the services file (%SystemRoot%\system32\drivers\etc\services on Windows, or /etc/services on UNIX).
> | Action | Contact your system administrator. If the problem persists, contact DataDirect Technologies technical support.
> 3148 | Failed to unregister the OS service because it is not a SequeLink Service.
> | Cause | An attempt to unregister a SequeLink service failed because the SequeLink service name was being used by another operating system service.
> | Action | Make sure that the name you choose for your SequeLink service is not being used by another operating system service.
> 3149 | The configuration file was changed by someone else.
> | Cause | The configuration file has been modified by another administrator.
> | Action | Reload the configuration file and make the changes again.
> 3150 | Failed to process the remote management request.
> | Cause | The management request could not be processed by the server.
> | Action | Preceding or subsequent messages contain more detailed information.
> 3151 | Failed to start the specified SequeLink service.
> | Cause | The SequeLink service did not start.
> | Action | Examine the service debug log file or service event trace file for more information.
> 3152 | Failed to stop the specified SequeLink service.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3153 | Failed to obtain the status of the specified OS Service.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3154 | Failed to start the specified service because it is already running.
> | Cause | An attempt to start a SequeLink service that is already running was detected.
> | Action | If the SequeLink Manager lists the SequeLink service as inactive, the SequeLink service may be in the process of stopping. Wait for the SequeLink service to stop completely and then retry.
> 3155 | Failed to process the administration request because the required service executable is not found.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3156 | Failed to open the Service. The SequeLink Administrator has not enough privileges to start/stop a service.
> | Cause | The operating system requires processes that must have administrator privileges for opening the service controller.
> | Action | Ask your security administrator to grant sufficient privileges.
> 3160 | Failed to process remote monitoring request.
> | Cause | The monitoring request could not be processed by the server.
> | Action | Preceding or subsequent messages contain more detailed information.
> 3161 | Failed to process the monitor request because a required counter could not be found in the monitor.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3170 | Failed to process the remote query event trace request.
> | Cause | The event trace request could not be processed by the server.
> | Action | Preceding or subsequent messages contain more detailed information.
> 3171 | Failed to process the query event trace request because the specified handle has not been opened.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3172 | Failed to open the event trace.
> | Cause | The SequeLink Server was unable to open the event trace file.
> | Action | Make sure that the "ServiceEventTraceLocation" service attribute contains a valid event trace file location and that it is accessible. If the problem persists, contact DataDirect Technologies technical support.
> 3180 | Failed to process the profile generator request because the required object could not be found in the profile.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3181 | Failed to process the profile generator request because a duplicate object was found in the profile.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3186 | Failed to open the Service Control Manager. The SequeLink Administrator has not enough privileges to create/delete a service.
> | Cause | The operating system requires processes that must have administrator privileges for starting and deleting services.
> | Action | Ask your security administrator to grant sufficient privileges.
> 3201 | Unable to retrieve error message from backend ODBC driver.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3202 | Unable to retrieve warning message from backend ODBC driver.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3203 | Required user name is missing.
> | Cause | The SequeLink service has been configured to require a database user name, but the SequeLink Client did not provide a database user name.
> | Action | Make sure that all required connection attributes are specified.
> 3204 | Select statement not allowed in batch processing.
> | Cause | A Select statement was detected in a batch of statements.
> | Action | Change your application so that Select statements are not included in the batch.
> 3208 | Unable to retrieve the code page from IBM/DB2 UDB.
> | Cause | The SequeLink server could not retrieve the code page from IBM/DB2 UDB during the connection setup.
> | Action | Set the "ServiceDebugLogLevel" to debug. Make a new connection and look for the message in the session log file: `SWANDB_SPEC_GetDBCodePageSettings : cannot retrieve the DB2 codepage settings (sqlcode=`xxx`)`. Contact DataDirect Technologies technical support and provide the codepage setting information.
> 3209 | A connection to a SequeLink service with enhanced code page support can only be established when ServiceCodepage is set to "Database".
> | Cause | A connection to a SequeLink service with enhanced code page support was executed when the ServiceCodePage service attribute was set to Default or OS.
> | Action | Check the SequeLink configuration and verify that the "ServiceCodePage" service attribute is set to Database for the service to which you want to connect. If the problem persists, contact DataDirect Technologies technical support.
> 3210 | A connection to a SequeLink service without enhanced code page support can only be established when ServiceCodePage is set to "Default" or "OS".
> | Cause | A connection to a SequeLink service with enhanced code page support was executed and the ServiceCodePage service attribute is set to Database.
> | Action | Check the SequeLink configuration and verify that the "ServiceCodePage" service attribute for the service to which you want to connect is set to Default or OS. If the problem persists, contact DataDirect Technologies technical support.
> 3211 | A connection to a SequeLink service, set up with ServiceCodepage = Database, requires at least SequeLink 5.4 client or higher for ODBC, JDBC or ADO.NET.
> | Cause | A connection to a SequeLink service with enhanced code page support was executed using an unsupported version of the SequeLink Client. The ServiceCodePage=Database setting is supported on SequeLink Clients version 5.4 or higher.
> | Action | Check the version of the SequeLink ODBC, JDBC, or .NET Client.
> 3213 | CLOB data type in UTF8 is not supported in SequeLink for DB2 UDB.
> | Cause | DB2 UDB Unicode databases store character-based Large Objects (CLOB) data in UTF-8. SequeLink for DB2 UDB does not support this multi-byte character data type.
> | Action | Check your application. Remove the references to UTF-8-based CLOB columns or change the references to UCS-2-based DBCLOB columns.
> 3215 | The environment variable LIBPATH has not been set correctly. The JVM cannot be started.
> | Cause | LIBPATH does not contain the value for the library with the Java Virtual Machine DLL or shared library.
> | Action | Check LIBPATH to see if it contains the value for the library.
> 3216 | The Java Virtual Machine is started.
> | Cause | This is an informational message.
> | Action | None.
> 3301 | Optional feature not implemented.
> | Cause | A request to change to another catalog was refused. You cannot change to another catalog.
> | Action | Do not try to change to another catalog.
> 3302 | Unsupported transaction level.
> | Cause | A request to change to an unsupported transaction level was refused.
> | Action | Use a supported transaction level.
> 3303 | An invalid Oracle parameter kind is encountered.
> | Cause | Oracle returned a stored procedure parameter type that is not documented.
> | Action | Contact DataDirect Technologies technical support.
> 3304 | An incorrect number of parameter markers is encountered in the statement.
> | Cause | A stored procedure was executed, but the number of parameters did not correspond with the stored procedure definition.
> | Action | Change the stored procedure statement that executes the stored procedure in your application.
> 3305 | SequeLink does not support CLOB/BLOB parameters as stored procedure parameters.
> | Cause | A stored procedure was executed, but a CLOB/BLOB parameter was detected.
> | Action | Change the stored procedure in your application.
> 3306 | Internal error. An invalid OCI handle was passed to the database.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3307 | Unexpected XA error.
> | Cause | An Oracle-specific XA (distributed transaction) call failed.
> | Action | Contact DataDirect Technologies technical support.
> 3308 | The specified object does not exist.
> | Cause | A stored procedure was executed for which no definition was found.
> | Action | Make sure that the stored procedure you execute exists in the database and that you have the privileges to execute the stored procedure.
> 3309 | A filter value is too long.
> | Cause | The DataSourceSchemaFilterList or DataSourceTableTypeFilterList service attribute contains a value that is too long.
> | Action | Correct the "DataSourceSchemaFilterList" or "DataSourceTableTypeFilterList" service attribute value.
> 3310 | An Oracle procedure was created with compilation errors.
> | Cause | An error was detected in the syntax of the statement that created the stored procedure.
> | Action | Correct the syntax of the statement that created the stored procedure.
> 3311 | A data dictionary statement was called with an invalid parameter value.
> | Cause | A data dictionary statement (for example, SQLSpecialColumns) was called, but at least one of the parameters had a value that was not valid.
> | Action | Contact DataDirect Technologies technical support.
> 3312 | SequeLink does not support this data type for stored procedure parameters.
> | Cause | A stored procedure was executed, and a data type that SequeLink does not support for stored procedures was detected.
> | Action | Change the statement that executes the stored procedure in your application.
> 3313 | Internal error. The specified data source is not found in the SequeLink configuration file.
> | Cause | The specified server data source could not be found in the SequeLink configuration file.
> | Action | Contact DataDirect Technologies technical support.
> 3314 | Select statement not allowed in batch processing.
> | Cause | You cannot execute a Select statement in a batch of statements.
> | Action | Change your application so that Select statements are not included in the batch.
> 3315 | A required Oracle user name is missing.
> | Cause | The SequeLink service is configured to require a database user name, but a database user name was not provided by the SequeLink Client.
> | Action | Specify the database user name when you attempt to connect.
> 3316 | An invalid Oracle SID is specified in the SequeLink configuration file.
> | Cause | The SequeLink configuration file specified an invalid Oracle SID.
> | Action | Specify an existing, valid Oracle SID.
> 3317 | Internal error. An unsupported action is encountered in a fetch callback routine.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3318 | An Oracle DATE value can only be converted to a SequeLink timestamp value.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3319 | A SequeLink timestamp value can only be converted to an Oracle DATE value.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3320 | An Oracle NUMBER value can only be converted to a SequeLink decimal value.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3321 | A SequeLink decimal value can only be converted to an Oracle NUMBER value.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3322 | A backslash is not a valid value for a searchable input parameter of a data dictionary statement.
> | Cause | A searchable input parameter of a data dictionary statement (for example, SQLTables) has a backslash character (\) value that is not followed by another character.
> | Action | Change the data dictionary statement in your application to use a valid value for a searchable input parameter.
> 3323 | The precision of a decimal input parameter is out of range.
> | Cause | The SequeLink Client sent a decimal input value with a precision that is larger than the maximum allowed Oracle precision.
> | Action | Change your application.
> 3324 | The impersonation of the SequeLink Server for Oracle failed.
> | Cause | The SequeLink Server is configured in OS integrated mode (DataSourceLogonMethod=OSIntegrated), but the impersonation of the SequeLink Server failed.
> | Action | Contact DataDirect Technologies technical support.
> 3326 | Invalid querytimeout value.
> | Cause | Only positive values are allowed as querytimeout.
> | Action | Specify a valid querytimeout value.
> 3327 | Internal error. An invalid SequeLink decimal parameter value encountered.
> | Cause | The SequeLink Client sent a decimal value that is not recognized by the SequeLink Server.
> | Action | Contact DataDirect Technologies technical support.
> 3328 | Oracle TIMESTAMP WITH TIME ZONE is not supported by this SequeLink configuration.
> | Cause | By default, SequeLink does not support the Oracle type Timestamp With Time Zone because there is no corresponding ODBC/JDBC/ADO type to represent this data.
> | Action | SequeLink implements a workaround to support Timestamp With Time Zone. See the description of "DataSourceORAMapTSWTZ" in the SequeLink Administrator's Guide.
> 3330 | The Oracle datatype XMLTYPE is not supported. Please convert the XMLTYPE to a string or clob.
> | Cause | SequeLink does not support the Oracle data type XMLTYPE.
> | Action | Use the Oracle DBMS packages to convert the XMLTYPE to a string or CLOB.
> 3331 | The resultset contains an unsupported Oracle datatype.
> | Cause | The resultset contains an unsupported data type, resulting in unsupported behavior.
> | Action | Check the Oracle data types in your resultset. Refer to the SequeLink Developer's Reference for the Oracle data types that SequeLink supports.
> 3333 | Unsupported behavior for this SequeLink Server version.
> | Cause | Searching a CLOB with a CLOB locator as search argument is not supported.
> | Action | None.
> 3401 | The database does not support catalogs.
> | Cause | An attempt was made to use a catalog, but the database does not support catalogs.
> | Action | Do not try to use a catalog.
> 3402 | The database does not support the change of isolation level.
> | Cause | An attempt was detected to change the transaction isolation level, but the database does not support changing the isolation level.
> | Action | Do not try to change the transaction isolation level.
> 3403 | Schema/Owner is not supported in stored procedure calls, SQLProcedures, or SQLProcedureColumns.
> | Cause | Because DB2 stored procedures do not have schemas, you cannot specify a schema name in procedure-related data dictionary statements.
> | Action | Change the stored procedures in your application.
> 3404 | Invalid stored procedure name or not authorized to invoke this procedure.
> | Cause | Either an invalid stored procedure name was specified or you do not have sufficient privileges to invoke the stored procedure.
> | Action | Make sure that you execute a stored procedure that exists in the database and that you have sufficient privileges to execute it.
> 3405 | No default parameters are allowed in a stored procedure call.
> | Cause | Default parameters were used when invoking a stored procedure.
> | Action | Do not use the default parameters when invoking a stored procedure.
> 3406 | Number of parameters mismatch for stored procedure.
> | Cause | A stored procedure was executed, and the number of parameters did not correspond with the stored procedure definition.
> | Action | Change the number of parameters specified in your application.
> 3407 | Literals are not supported as stored procedure parameters.
> | Cause | Literals are used for stored procedure parameters.
> | Action | Change the stored procedure in your application so that it does not use literals.
> 3408 | Stored procedures can no longer be executed because a SET CURRENT SQLID occurred.
> | Cause | After issuing a a SET CURRENT SQLID, it is no longer possible to execute stored procedures.
> | Action | Change your application.
> 3409 | The kind (in, out or in/out) of a stored procedure parameter as specified by the SequeLink Client does not match with the stored procedure definition.
> | Cause | An invalid type of a stored procedure parameter was specified.
> | Action | Change the type of the stored procedure parameter specified in your application.
> 3410 | The stored procedure cannot handle NULL values.
> | Cause | A NULL value was specified for a stored procedure parameter.
> | Action | Change the value for the stored procedure parameter specified in your application.
> 3411 | Thread to DB2 could not be opened. Either a resource is unavailable or the requested resource (plan) is not known to DB2.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3412 | Info about DB2 connection could not be retrieved.
> | Cause | The SequeLink Server attempted to retrieve DB2-specific information.
> | Action | Check your service debug log file for details about this error.
> 3413 | More result sets have to be returned than defined.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3414 | Parameter list contains invalid data type.
> | Cause | The parameter list of a stored procedure contains an invalid or unsupported data type.
> | Action | Change the stored procedure in your application.
> 3415 | Conversion of a floating point number to a SequeLink decimal has failed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3416 | Some bind variables have not been defined.
> | Cause | Some required parameter markers have not been defined by the application.
> | Action | Correct your application.
> 3417 | Invalid data type conversion requested.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3418 | UIDMap associated with the service not found.
> | Cause | The specified UID Map could not be located.
> | Action | Make sure that the name of the UID Map you specify in the MVSServiceUIDMap service attribute is correct. For more information about valid values for SequeLink service attributes, refer to the SequeLink Administrator's Guide.
> 3419 | Access denied, user cannot be found in UIDMap.
> | Cause | The specified user was not found in the UID Map.
> | Action | Make sure that you have correctly defined the specified user in the UID Map. Also, make sure that you have specified the correct UID Map in the MVSServiceUIDMap service attribute. For more information about valid values for SequeLink service attributes, refer to the SequeLink Administrator's Guide.
> 3420 | Select statement not allowed in batch processing.
> | Cause | You cannot execute a Select statement in a batch of statements.
> | Action | Change your application so that Select statements are not included in the batch.
> 3421 | The maximum number of concurrent SQL statements is reached.
> | Cause | Too many statements are open at the same time.
> | Action | Close some statements before attempting to open a new statement.
> 3422 | Invalid value specified for scope.
> | Cause | The value for the scope input parameter of SQLSpecialColumns or GetBestRowIdentifier is not valid.
> | Action | Contact DataDirect Technologies technical support.
> 3423 | Schema name specified too long.
> | Cause | The schema name parameter of a data dictionary statement was too long.
> | Action | Change the schema name in your application.
> 3424 | Table name specified too long.
> | Cause | The table name parameter of a data dictionary statement was too long.
> | Action | Change the table name parameter in your application.
> 3425 | Filter value specified too long.
> | Cause | The filter value parameter of a data dictionary statement was too long.
> | Action | Change the filter value in your application.
> 3426 | Column value specified too long.
> | Cause | The value of a column you specified was too long.
> | Action | Change the column value in your application.
> 3427 | No row for parameter in SYSIBM.SYSPARMS.
> | Cause | SYSIBM.SYSPARMS contains a row for each parameter of a stored procedure. SequeLink could not find a row for at least one of the parameters.
> | Action | Check your procedure definition. Re-issue the call procedure. If the problem persists, contact DataDirect Technologies technical support.
> 3428 | Procedurename specified too long.
> | Cause | The length of the unqualified name of a stored procedure cannot exceed 18 characters.
> | Action | Correct the name of the stored procedure and re-issue the catalog statement.
> 3429 | Procedure parameter name specified too long.
> | Cause | The length of the name of a stored procedure parameter cannot exceed 18 characters.
> | Action | Correct the name of the stored procedure parameter and re-issue the catalog statement.
> 3430 | A valid database context could not be found.
> | Cause | A valid database context could not be found.
> | Action | Contact DataDirect Technologies technical support.
> 3431 | A database context could not be created.
> | Cause | A database context could not be created.
> | Action | A VAID050E message is generated and written to the service debug log. Contact your system administrator.
> 3432 | The database context could not be added to the context pool.
> | Cause | The database context could not be added to the context pool, because no virtual storage could be obtained.
> | Action | None.
> 3433 | The database context could not be switched.
> | Cause | The database context could not be switched.
> | Action | A VAID050E message is generated and written to the service debug log. Contact your system administrator.
> 3434 | Invalid literal.
> | Cause | A literal in the stored procedure is invalid.
> | Action | Make sure that the character literals are enclosed in quotes and that numeric literals have a valid value.
> 3435 | Literal cannot be an output parameter.
> | Cause | A literal cannot be used as an output parameter.
> | Action | Use a bind variable for the output parameter and re-issue the call procedure.
> 3436 | Datatype not supported for literals.
> | Cause | An unsupported data type was used for a literal. The stored procedure could not be executed.
> | Action | Use a bind variable for the literal and re-issue the call procedure.
> 3437 | Literals and bind variables cannot be mixed.
> | Cause | A combination of literals and bind variables cannot be used when calling a stored procedure.
> | Action | Make sure that you use only literals or only bind variables when calling a stored procedure.
> 3438 | The maximum size of a large object output parameter is exceeded.
> | Cause | A stored procedure was called that returns a LOB output parameter that exceeds the value set by the DataSourceDB2MaxLobSize service attribute for this data source. The data is not returned.
> | Action | Increase the value of the DataSourceDB2MaxLobSize service attribute or return a smaller LOB output parameter in the stored procedure.
> 3439 | The requested DB2 subsystem is not active.
> | Cause | The requested DB2 subsystem is not active.
> | Action | Contact your system administrator to start the DB2 subsystem.
> 3440 | A required service/data source attribute is not found; contact your system administrator.
> | Cause | A required service or data source attribute could not be found in the configuration file.
> | Action | A message that identifies the missing attribute is generated and sent to the service debug log. Contact your system administrator.
> 3441 | No Uidmap associated with service, anonymous logon denied.
> | Cause | The service is not configured correctly. A UIDMap is required to allow anonymous logon, but no UIDMap is associated with the service.
> | Action | Create a UIDMap and add the MVSServiceUIDMap service attribute to the service.
> 3442 | Uidmap does not contain wildchar entry, anonymous logon denied.
> | Cause | The UIDMap associated with the service does not contain a wild character entry (*).
> | Action | Add a wild character entry (*) to the UIDMap associated with the service.
> 3443 | Cannot logon to the database.
> | Cause | The logon to DB2 failed.
> | Action | See accompanying messages and the Server VAILOG for the DB2 reason code.
> 3444 | The maximum number of database Threads is reached.
> | Cause | The Service is exceeding the value set for the ServiceDB2MaxThread service attribute.
> | Action | Increase the value of the ServiceDB2MaxThread service attribute.
> 3445 | Virtual storage limits exceeded.
> | Cause | Insufficient storage was available at the server. No more DB2 connections could be accepted.
> | Action | Try the connection again.
> 3446 | DataSourceTransactionIsolation attribute has an unsupported value.
> | Cause | The DataSourceTransactionIsolation service attribute is missing.
> | Action | Ask the administrator to add the "DataSourceTransactionIsolation" service attribute.
> 3447 | Abend occurred due to an internal error in IBM DATABASE 2 (DB2) processing.
> | Cause | DB2 had been abended and trapped within the session.
> | Action | Ask the system operator to look for message VAI046 in VAILOG.
> 3448 | This functionality is not supported for this database version.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3449 | Maximum cputime limit has been exceeded, DB2 thread aborted.
> | Cause | The session has exceed its maximum CPU time as set by the DataSourceMaxCpuTime attribute.
> | Action | None.
> 3451 | No Mappinglist defined in Uidmap, anonymous logon denied.
> | Cause | There is no entry in Uidmap containing a wild card that represents any user: *=mapped_user. This entry is used to map anyone to this mapped user for authorization in DB2.
> | Action | Add an entry for any user in the UID map.
> 3452 | User has no authority to access the requested data source.
> | Cause | The resource-based authorization has been set up so that you do not have the required authority to access the requested data source.
> | Action | Contact your SequeLink administrator.
> 3453 | The mapped user failed authentication.
> | Cause | The mapped user is not defined in your Security Manager or does not have the required privileges to authenticate.
> | Action | Contact your SequeLink administrator.
> 3454 | The SQL statement length exceeds the value specified in MvsDataSourceMaxStmtLength.
> | Cause | The SQL statement length exceeds the maximum length defined in the SequeLink configuration of your data source.
> | Action | Contact your SequeLink administrator.
> 3501 | Unsupported transaction isolation level.
> | Cause | An attempt was detected to change the transaction isolation level to an isolation level that is unsupported by Informix.
> | Action | Use a transaction isolation level that is supported by the Informix database.
> 3502 | Internal error. Failed to translate the user specified statement to an Informix-specific format.
> | Cause | The SequeLink Server SQL Parser could not parse the SQL statement.
> | Action | Correct the syntax error in the SQL statement that you are trying to prepare or execute.
> 3503 | An Informix DECIMAL value can only be converted to a SequeLink decimal value.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3504 | A SequeLink decimal value can only be converted to an Informix NUMBER value.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3505 | Internal error. An unsupported action is encountered in a fetch callback routine.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3506 | Numeric value truncated.
> | Cause | The precision or scale of a numeric value is larger than Informix expects.
> | Action | Make sure the numeric value that you send to Informix corresponds to the columns definition.
> 3507 | An Informix timestamp value can only be converted to a SequeLink timestamp value.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3508 | A SequeLink timestamp value can only be converted to an equivalent Informix timestamp value.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3509 | Output and Input-Output variables not supported.
> | Cause | An attempt was detected to bind Output or Input/Output variables, which are not supported by Informix.
> | Action | SequeLink returns Informix return parameters as result sets. Fetch the result sets.
> 3510 | Data source not found.
> | Cause | An invalid server data source was specified at connection time.
> | Action | Make sure the server data source you want to connect to exists, or use the default server data source.
> 3511 | Get diagnostics failed.
> | Cause | SequeLink could not obtain the error message text from Informix.
> | Action | Contact DataDirect Technologies technical support.
> 3512 | Insertion of Smart BLOB failed.
> | Cause | SequeLink could not insert a smart BLOB (data type BLOB or CLOB).
> | Action | Make sure that a default sbspace has been created in Informix. Refer to the Informix documentation for information about onconfig.
> 3513 | Set catalog name not supported.
> | Cause | The application tried to switch the current database during the connection. This is not supported by Informix.
> | Action | Specify your database at connection time. Do not change databases after connection.
> 3514 | Invalid environment variables during establishing connection to database.
> | Cause | Either or both of the environment variables INFORMIXDIR or INFORMIXSERVER are not specified correctly in the DataSourceINFInformixDir and DataSourceINFInformixServer service attributes.
> | Action | Specify either or both of the INFORMIXDIR or INFORMIXSERVER environment variables in the "DataSourceINFInformixDir" and "DataSourceINFInformixServer" service attributes.
> 3515 | Database name not specified.
> | Cause | A connection was attempted without specifying a valid database name.
> | Action | Check the connection settings and make sure a valid database name is passed to the server.
> 3516 | Stat, ClsDb, Commit, Rollback functions not allowed for execution.
> | Cause | An attempt was made to execute the native Informix transaction functions.
> | Action | Use only the SequeLink Client's transaction functions for transaction handling.
> 3517 | Prepared statement is not described by Informix.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3518 | Informix function failed while reading smart LOB data.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 3519 | Select statements cannot be executed via NImmediate.
> | Cause | An attempt was made to execute statements that generate result sets in a batch of JDBC statements.
> | Action | Make sure that every statement in a statement batch is a DDL or a statement that generates RowCounts.
> 4301 | Operation Failed.
> | Cause | Never generated.
> | Action | None.
> 4302 | Error configuring the JDBC DataSource
> | Cause | The logWriter writer could not be set because the DataDirect Spy jar file was not on the class path.
> | Action | Verify that the spy.jar file is on the class path.
> 4303 | JDBC DataSource not defined.
> | Cause | The SequeLink Client for JDBC DataSource object used by the resource adapter was not initialized correctly.
> | Action | Contact DataDirect Technologies technical support. The subclasses of JCAManagedConnectionFactory should ensure that a SequeLink Client for JDBC DataSource object is passed to the JCAManagedConnectionFactory constructor. It is an internal resource adapter error if it does not.
> 4304 | The physical connection is invalid.
> | Cause | An operation was attempted on a ManagedConnection that has been closed.
> | Action | Try the connection using an open ManagedConnection. Do not use a ManagedConnection that has been closed.
> 4305 | Reauthorization of JDBC Connections is not allowed.
> | Cause | An attempt was made to reuse a ManagedConnection with a user ID and password that is different from the user ID and password used to create the ManagedConnection.
> | Action | Verify that the user ID and password supplied to the getConnection(String userId, String password) method of a particular ConnectionFactory instance is the same for each invocation.
> 4306 | The supplied connection handle is invalid.
> | Cause | An attempt was made to associate a ManagedConnection with a connection handle that is not an instance of JCAConnection.
> | Action | The Connection object passed to ManagedConnection.associateConnection must be an instance of a JCAConnection object.
> 4307 | Error fetching local transaction object.
> | Cause | Never generated.
> | Action | None.
> 4308 | Error fetching meta data from resource.
> | Cause | An error was generated while fetching information needed for the ManagedConnectionMetaData from the JDBC connection used by the resource adapter.
> | Action | The exception generated by the JDBC connection is chained to this exception. Use the method ResourceException.getLinkedException to retrieve the exception chained to this exception. The message of the chained exception will indicate the cause of the problem.
> 4309 | The object is closed.
> | Cause | An attempt was made to use a JCAConnection object that has already been closed.
> | Action | Do not use a JCAConnection object after it has been closed.
> 4310 | The Connection Factory is invalid.
> | Cause | An attempt was made to use a Connection Factory object that was not initialized correctly.
> | Action | Contact DataDirect Technologies technical support. A JCAManageConnectionFactory should never create a Connection Factory object that is invalid. It is an internal resource adapter error if it does.
> 4311 | Can not fetch XAResource. Resource adaptor does not support XA Transactions.
> | Cause | The resource adapter does not support XA Transactions.
> | Action | Do not use XA Transactions with the resource adapter.
> 4312 | The Managed Connection Factory is invalid.
> | Cause | A ManagedConnectionFactory was not specified when creating a new ManagedConnection while using the default connection manager included with the resource adapters.
> | Action | Contact DataDirect Technologies technical support. A JCAConnectionFactory should always specify a valid ManagedConnectionFactory when creating a new ManagedConnection. It is an internal resource adapter error if it does not.
> 4313 | Unsupported Method.
> | Cause | An attempt to call unlock on a connection handle that does not contain a valid physical connection. A connection handle will not contain a valid physical connection if the connection handle was closed.
> | Action | Do not call unlock on a connection handle that has been closed.
> 5001 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5002 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5003 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5004 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5011 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5012 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5013 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5014 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5015 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5021 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5022 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5023 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5024 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5031 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5033 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5034 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5043 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5044 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5045 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5046 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5047 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5052 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5058 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5059 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5060 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5061 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5065 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5067 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5069 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5070 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5071 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5101 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5102 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5103 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5104 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5105 | A memory allocation error occurred.
> | Cause | SequeLink was unable to allocate the necessary amount of memory.
> | Action | Increase the available memory for your application.
> 5106 | A memory allocation error occurred.
> | Cause | SequeLink was unable to allocate the necessary amount of memory.
> | Action | Increase the available memory for your application.
> 5107 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5108 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5109 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5110 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5111 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5112 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5113 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5150 | You cannot connect to a server that is not a SequeLink Server.
> | Cause | An attempt was detected to connect to a server that is not a SequeLink Server.
> | Action | Make sure that the connection information configured at the SequeLink Client is specified correctly to connect to the SequeLink Server.
> 5151 | A protocol error occurred during the connection setup.
> | Cause | The SequeLink Client is not compatible with the version of the SequeLink Server to which it is connecting.
> | Action | Verify that the versions of your SequeLink Client and SequeLink Server are compatible. Contact DataDirect Technologies technical support, if necessary.
> 5152 | You are trying to connect to a server that is not running the correct version of SequeLink Server.
> | Cause | An attempt was detected to connect to a SequeLink Server running an incompatible version of SequeLink.
> | Action | Verify that the versions of your SequeLink Client and SequeLink Server are compatible. Contact DataDirect Technologies technical support, if necessary.
> 5153 | The SequeLink Client failed to retrieve the connection parameters from the LDAP server.
> | Cause | The SequeLink Client failed to retrieve connection information from the LDAP server.
> | Action | Typically, this error is followed by other errors containing more detailed information. Use these details to troubleshoot the problem.
> 5154 | The TCP/IP host was not specified.
> | Cause | The TCP/IP host of the SequeLink Server was not specified in the connection information.
> | Action | Make sure that the connection information configured at the SequeLink Client specifies the TCP/IP host of the SequeLink Server.
> 5155 | The TCP/IP port was not specified.
> | Cause | The TCP/IP port of the SequeLink Server was not specified in the connection information.
> | Action | Make sure that the connection information configured at the SequeLink Client specifies the TCP/IP port of the SequeLink Server.
> 5156 | LDAP Distinguished Name is missing.
> | Cause | The LDAP Distinguished Name that identifies a unique LDAP entry was not specified in the connection information to the LDAP server.
> | Action | Make sure that the connection information configured at the SequeLink Client specifies the Distinguished Name of the LDAP entry.
> 5157 | The specified LDAP entry didn't specify all required attributes to connect to the SequeLink Server.
> | Cause | The specified LDAP entry, identified by the Distinguished Name, did not specify all the required attributes to connect to the SequeLink Server.
> | Action | Check the LDAP entry in the LDAP directory to make sure that the LDAP entry specifies the complete connection information for SequeLink connections. For information about configuring LDAP for SequeLink, refer to the SequeLink Administrator's Guide.
> 5158 | LDAP return code: xxxx (xxxx).
> | Cause | An LDAP return code was generated by the underlying LDAP implementation. The return code contains parameters that provide more detailed information.
> | Action | Refer to your LDAP product documentation to reference the return code generated by LDAP.
> 5159 | The initialization of the LDAP client failed. Possible cause: memory allocation failure.
> | Cause | The initialization of the LDAP client failed. A memory allocation failure may have occurred.
> | Action | Increase the available memory for your application.
> 5160 | The specified LDAP entry could not be found. Part of the Distinguished Name identifying the entry as "xxxx" was returned.
> | Cause | The specified LDAP entry, identified by the Distinguished Name, could not be found.
> | Action | Make sure that you specified a correct LDAP entry Distinguished Name.
> 5161 | Failed to load the LDAP library: xxxx.
> | Cause | SequeLink Client could not load the specified LDAP shared library.
> | Action | Check your SequeLink Client installation.
> 5162 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5163 | LDAP is not supported on this platform.
> | Cause | The attempted operation is supported only on platforms that support LDAP.
> | Action | Try the operation on a SequeLink Client running on a platform that supports LDAP.
> 5164 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5200 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5201 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5202 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5203 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5204 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5205 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5206 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5223 | An internal error occurred (SSP_ERR_PROV_INVALIDDIRECTION).
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5241 | An internal error occurred (SSP_ERR_NIMM_INVALIDNUMOFSTMTS).
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5270 | An internal error occurred (SSP_ERR_EXTDEF_INVALIDNUMOFVARS).
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5290 | An internal error occurred (SSP_ERR_FETCH_INVALIDROWCOUNT).
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5300 | Failed to load the transliteration file `xxxx'.
> | Cause | The transliteration file `xxxx' failed to load.
> | Action | Check your SequeLink Client installation.
> 5301 | The transliteration file `xxxx' is corrupt.
> | Cause | The transliteration file `xxxx' is damaged.
> | Action | Check your SequeLink Client installation.
> 5302 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5303 | Failed to load the transliteration file `xxxx'.
> | Cause | The transliteration file `xxxx' failed to load.
> | Action | Check your SequeLink Client installation.
> 5304 | The transliteration file `xxxx' is corrupt.
> | Cause | The transliteration file `xxxx' is corrupt.
> | Action | Check your SequeLink Client installation.
> 5305 | An internal error occurred. Failed to load XlatTransliterator for 'transliteration table'.
> | Cause | The creation of a transliteration table failed.
> | Action | Reduce the memory load of the application.
> 5306 | An internal error occurred. Failed to load IcuTransliterator for 'codepage'.
> | Cause | The creation of a transliteration code page handled by the ICU failed.
> | Action | Check the validity of the indicated code pages or encodings.
> 5320 | An internal error occurred (SSP_ERR_DEFDESC_INVALIDNUM).
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5321 | An internal error occurred (SSP_ERR_DEFDESC_MULTIPLE).
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5330 | An internal error occurred (SSP_ERR_GETDESC_INVALIDIDX).
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5331 | An internal error occurred (SSP_ERR_GETDESC_NODEFDESC).
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5340 | An internal error occurred (SSP_ERR_DOCONNECT_ACTIVE).
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 5350 | An authentication mechanism could not be successfully negotiated.
> | Cause | The SequeLink Server did not specify an authentication mechanism supported by the SequeLink Client.
> | Action | Make sure that the SequeLink Server specifies an authentication mechanism supported by the SequeLink Client. Refer to the SequeLink Administrator's Guide for information on configuring authentication.
> 5501 | Memory allocation failure.
> | Cause | The requested amount of memory could not be allocated.
> | Action | Free memory resources. If the problem persists, contact DataDirect Technologies technical support.
> 5502 | Failed to initialize SequeLink Manager.
> | Cause | The SequeLink Manager could not be initialized.
> | Action | Contact DataDirect Technologies technical support.
> 5503 | Internal SequeLink Manager error detected (I=xxxxd).
> | Cause | An internal error occurred in the SequeLink Manager.
> | Action | Contact DataDirect Technologies technical support.
> 5504 | Unknown command <name> entered.
> | Cause | An incorrect SequeLink Manager command was entered.
> | Action | Check the SequeLink Manager command help to verify the command.
> 5505 | Specified argument not valid for the given command.
> | Cause | An incorrect parameter for a SequeLink Manager command was entered.
> | Action | Check the SequeLink Manager command help to verify the command parameter.
> 5506 | Failed to open file <file name>.
> | Cause | The specified file could not be opened.
> | Action | Make sure that the specified file exists. If it does, make sure that you have sufficient privileges to open and read the file.
> 5507 | Argument out of range.
> | Cause | A parameter for a SequeLink Manager command was too long.
> | Action | Check the SequeLink Manager command help to verify the command parameter.
> 5508 | Required parameter <name> for command not specified.
> | Cause | A required parameter for the SequeLink Manager command was not specified.
> | Action | Check the SequeLink Manager command help to verify the required parameters for the command.
> 5509 | Command not available for current configuration.
> | Cause | The SequeLink Manager command entered is not supported for the current configuration.
> | Action | Check the SequeLink Manager command help to verify the command.
> 5510 | Failed to display help item.
> | Cause | SequeLink Manager help could not be displayed for the specified command. This is an internal error.
> | Action | Contact DataDirect Technologies technical support.
> 5511 | No configuration opened.
> | Cause | A SequeLink Manager command was entered that required an open configuration.
> | Action | Check the SequeLink Manager command help to verify the command.
> 5513 | Numeric value for parameter required.
> | Cause | A parameter for the specified SequeLink Manager command required a numeric value.
> | Action | Check the SequeLink Manager command help to verify the parameters for the command.
> 5514 | An invalid service template ID was specified.
> | Cause | An invalid SequeLink service template ID was specified.
> | Action | Make sure that you specify the correct SequeLink service template ID. For more information about template IDs, refer to the SequeLink Administrator's Guide.
> 5515 | Invalid option <name>.
> | Cause | An invalid option for the specified SequeLink Manager command was supplied.
> | Action | Check the SequeLink Manager command help to verify the specified command.
> 5516 | Invalid value for option <name>.
> | Cause | An invalid value for the specified SequeLink Manager command option was supplied.
> | Action | Check the SequeLink Manager command help to verify the command.
> 5517 | Help topic not found.
> | Cause | The topic specified with the SequeLink Manager help command could not be found.
> | Action | Specify help without arguments to see the topics for which help is available.
> 5518 | Invalid attribute index syntax.
> | Cause | The attribute array index specified with the attribute name has an incorrect syntax. The correct syntax for an attribute array index is, for example, AttributeName[25].
> | Action | Correct the syntax.
> 5519 | Invalid log level <name>.
> | Cause | The log level name in a SequeLink Manager command that was entered was invalid.
> | Action | Check the SequeLink Manager command help to verify log level names.
> 5520 | Invalid log value <name>.
> | Cause | The value specified with the log level name in a SequeLink Manager command that was entered was invalid.
> | Action | Check the SequeLink Manager command help to verify log level values.
> 5522 | Invalid numeric value <value>.
> | Cause | A value was specified in a SequeLink Manager command that could not be converted to a numeric value.
> | Action | Specify a valid numeric value for the SequeLink Manager command.
> 5523 | AutoSave option is already activated.
> | Cause | The SequeLink Manager command SaveConfig was issued when the AutoSave setting was activated.
> | Action | None. This message is informational only.
> 5524 | Quote mismatch.
> | Cause | Syntax error. No closing quote was typed.
> | Action | Correct the syntax.
> 5525 | System execution returned a non-zero return code (return code <value>).
> | Cause | An application or operating system command failed. The operating system command specified with the '!' command returned a non-zero return code.
> | Action | Refer to the command's documentation, typically the operating system command documentation, for more information.
> 5526 | Failed to open a pipe to <application>.
> | Cause | A pipe to the specified application could not be opened.
> | Action | Make sure that MoreExecPath is configured correctly. The following example is for HP-UX. Your path to the more command may be different, depending on the version of Linux or UNIX you are using. 1 Stop your SequeLink services. 2 Add the following lines to your swcla.ini file: [CLA Settings] MoreExePath=/usr/bin/more 3 Restart your SequeLink services.
> 5527 | When handling commands interactive, no output or error file can be specified.
> | Cause | An output or error file was specified on the command line, but no input file was specified.
> | Action | Correct the command line by adding the input file option or by removing the output or error file option.
> 5528 | Invalid flag <name>.
> | Cause | An invalid command-line flag was specified.
> | Action | Specify a valid command-line flag.
> 5529 | Invalid profile level <name>.
> | Cause | An invalid profile level in a SequeLink Manager command was specified.
> | Action | Check the SequeLink Manager command help to verify profile levels.
> 5530 | Invalid name or ID <value> for profile level <name>.
> | Cause | An invalid profile name or ID for the specified profile level in a SequeLink Manager command was supplied.
> | Action | Check the SequeLink Manager command help to verify profile levels and their names or IDs.
> 5531 | Too many parameters specified.
> | Cause | Too many arguments were provided with a SequeLink Manager command.
> | Action | Make sure that the SequeLink Manager command provides the correct number of parameters.
> 5532 | An attribute index must be specified for this attribute.
> | Cause | When deleting or replacing an array attribute with a SequeLink Manager command, an index must always be specified.
> | Action | Make sure that an index is specified and the syntax is correct.
> 5533 | Specified attribute is no array attribute.
> | Cause | An index was provided in a SequeLink Manager command with an attribute that is not an array attribute.
> | Action | Make sure that no index is specified and the syntax is correct.
> 6000 | Error loading error messages.
> | Cause | An unexpected error occurred while loading the error messages.
> | Action | Contact DataDirect Technologies technical support.
> 6001 | {0}
> | Cause | Generic error occurred. At runtime, an error message from the JDK will be displayed.
> | Action | Check the error message {0} for the appropriate action.
> 6002 | Specified parameter values not supported for method: {0}
> | Cause | The parameters specified for method {0} contain invalid values.
> | Action | Check your JDBC application.
> 6003 | Unsupported method: {0}
> | Cause | The method {0} is not supported by this version of the JDBC driver.
> | Action | Verify the method {0} in your JDBC application.
> 6004 | Invalid operation for the current cursor position.
> | Cause | This method invocation is only valid when the result set has a current row.
> | Action | Check your JDBC application.
> 6005 | Invalid column name: {0}
> | Cause | The specified column {0} was not found. An invalid column name was specified.
> | Action | Check your JDBC application.
> 6006 | Column index {0} is out of range.
> | Cause | Your JDBC application specified a column index {0} that is out of bounds.
> | Action | Check your JDBC application.
> 6007 | ResultSet can not re-read row data for column {0}.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6008 | Unsupported data conversion.
> | Cause | The requested data conversion is not supported by this version of the JDBC driver.
> | Action | Verify the requested conversion in your JDBC application.
> 6009 | Object has been closed.
> | Cause | Object is closed. The JDBC application used an illegal method on a closed object.
> | Action | Correct your JDBC application.
> 6010 | Invalid parameter binding(s).
> | Cause | The parameter must be registered prior to getXXX().
> | Action | Correct your JDBC application.
> 6011 | Invalid call Statement method: {0}
> | Cause | The methods on Statement that have a SQL statement as parameter, like execute(sql) and addBatch(sql), are not supported on PreparedStatements.
> | Action | Check your JDBC application.
> 6012 | No ResultSet set was produced.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6013 | No rows affected.
> | Cause | The statement did not generate a row count. executeUpdate() cannot be used on a statement that returns a result set.
> | Action | Correct your JDBC application.
> 6014 | Invalid operation. Statement not in an executed state.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6017 | Unexpected internal error.
> | Cause | An unexpected internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6018 | Invalid SQL specified.
> | Cause | The specified SQL statement is not valid.
> | Action | Correct your JDBC application.
> 6019 | Method not valid for read-only ResultSet : {0}
> | Cause | The method {0} can only be called on an updatable result set.
> | Action | Correct your JDBC application.
> 6020 | Method not valid for TYPE_FORWARD_ONLY ResultSet : {0}.
> | Cause | The method {0} can only be called on a scrollable result set.
> | Action | Correct your JDBC application.
> 6021 | Can't start a cloned connection while in manual transaction mode.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6022 | The specified SQL type is not supported by this driver.
> | Cause | Your application uses a SQL type that is not supported by this driver.
> | Action | Check your JDBC application.
> 6023 | Cannot obtain a connection to perform the operation.
> | Cause | The maximum number of statements are in use.
> | Action | Check your JDBC application.
> 6024 | Value can not be converted to requested type.
> | Cause | The data type conversion for the specified column failed.
> | Action | Correct your JDBC application.
> 6025 | Object has been closed.
> | Cause | Object is closed. The JDBC application used an illegal method on a closed object.
> | Action | Correct your JDBC application.
> 6026 | Can't start manual transaction mode because there are cloned connections.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6027 | Not in local manual transaction mode.
> | Cause | The application called a method that can only be used in manual transaction mode.
> | Action | Correct your JDBC application.
> 6029 | Unable to connect. DataSource property {0} must be specified.
> | Cause | Insufficient information to connect was supplied. Missing parameters are: {0}.
> | Action | Make sure that you specify all required connection properties. For more information about all possible connection properties, refer to the SequeLink Administrator's Guide.
> 6030 | Unable to connect. Invalid URL.
> | Cause | Insufficient information to connect was supplied. Missing parameters are: {0}.
> | Action | Make sure that you specify the connection URL completely. For information about the syntax of the connection URL, refer to the SequeLink Administrator's Guide.
> 6031 | The input stream contained a different number of bytes than specified.
> | Cause | The application requested more bytes than available in the input stream.
> | Action | Check your JDBC application.
> 6032 | The hexadecimal string is invalid.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6033 | Unable to determine the type of the specified object.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6036 | Syntax error at token {0}, line {1} offset {2}.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6037 | Unexpected end of escape.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6038 | Error setting up static cursor cache.
> | Cause | An unexpected error occurred while setting up the static cursor cache.
> | Action | Obtain the next exception for more information. If necessary, contact DataDirect Technologies technical support.
> 6039 | Error writing data to static cursor cache.
> | Cause | An unexpected error occurred while writing to the static cursor cache set up.
> | Action | Obtain the next exception for more information. If necessary, contact DataDirect Technologies technical support.
> 6040 | Error reading data from static cursor cache.
> | Cause | An unexpected error occurred while writing to the static cursor cache set up.
> | Action | Obtain the next exception for more information. If necessary, contact DataDirect Technologies technical support.
> 6041 | 0 is not a valid row parameter value for the ResultSet.Absolute method.
> | Cause | 0 is not a valid value for the row parameter of the method ResultSet/Absolute.
> | Action | Correct your application.
> 6042 | Invalid call to ResultSet.Relative because there is no current row.
> | Cause | This method invocation is only valid when the result set has a current row.
> | Action | Check your JDBC application.
> 6043 | An I/O error while manipulating the sort index.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6044 | The evaluation period for this driver has expired. Contact DataDirect Technologies SupportLink to purchase a valid license.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6045 | A table name must be supplied.
> | Cause | The application did not specify a table name for the DatabaseMetaData.getIndexInfo method.
> | Action | Correct your application.
> 6046 | Scrolling request was downgraded.
> | Cause | The result set type was downgraded.
> | Action | Refer to the SequeLink Developer's Reference for information about restrictions on scrollable cursors.
> 6047 | Updateable concurrency not supported, downgraded to readonly concurrency.
> | Cause | The result set concurrency was downgraded.
> | Action | Refer to the SequeLink Developer's Reference for information about restrictions on updatable cursors.
> 6048 | Pooled connection reclamation not supported.
> | Cause | The JDBC driver does not support reclaiming open connections.
> | Action | Check your JDBC application.
> 6049 | Login has timed out.
> | Cause | A timeout expired.
> | Action | Verify that the SequeLink Server is running and that you have specified the correct network address of the host. If your configuration is correct, increase the connection timeout value.
> 6050 | This driver is locked for use with embedded applications.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6052 | There was an error(s) in processing the batch command. Use getNextException() for details.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6053 | Statements that produce result sets are not allowed in batch commands.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6054 | ResultSet is not updateable.
> | Cause | The application issued a method on a read only result set that can only be called on an updatable result set.
> | Action | Check your JDBC application.
> 6055 | Can not update, the specified column is not writable.
> | Cause | The application tried to update a read only column.
> | Action | Check your JDBC application.
> 6056 | Row update actually caused {0} rows to be updated.
> | Cause | ResultSet.updateRow updated more than one row.
> | Action | Make sure that your application selects the primary key of the table.
> 6057 | Row update failed.
> | Cause | An exception occurred while updating the ResultSet.
> | Action | Obtain the next exception for more information. If necessary, contact DataDirect Technologies technical support.
> 6058 | Invalid operation while positioned on the insert row.
> | Cause | The application called a method {0} that cannot be called while positioned on the insert row.
> | Action | Correct your JDBC application.
> 6059 | Row delete actually caused {0} rows to be deleted.
> | Cause | ResultSet.deleteRow updated more than one row.
> | Action | Make sure that your application selects the primary key of the table.
> 6060 | Row delete failed.
> | Cause | An exception occurred while deleting a row from the ResultSet.
> | Action | Obtain the next exception for more information. If necessary, contact DataDirect Technologies technical support.
> 6061 | Must be on the insert row to insert.
> | Cause | This method invocation is only valid when the cursor is positioned on the insert row.
> | Action | Check your JDBC application.
> 6062 | Row insert failed.
> | Cause | An exception occurred while inserting a row into the ResultSet.
> | Action | Obtain the next exception for more information. If necessary, contact DataDirect Technologies technical support.
> 6063 | Error closing Blob or Clob object.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6064 | The search pattern specified is too large.
> | Cause | The search pattern used is too large.
> | Action | Try to reduce the size of the search pattern if possible.
> 6065 | The buffer supplied is too small.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6066 | The size of the Blob is too big to be cached.
> | Cause | The size of the Blob is too large to be cached.
> | Action | If possible, try to reduce the size of the Blob.
> 6068 | Can't search Blobs larger than 2 GB.
> | Cause | The size of the Blob is too large to be searched.
> | Action | If possible, try to reduce the size of the Blob.
> 6069 | One or more arguments supplied to method {0} are invalid.
> | Cause | The parameters specified for method {0} contain invalid values.
> | Action | Check your JDBC application.
> 6070 | Invalid character encoding for Clob.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6071 | Invalid position. The Clob data uses UCS2 character encoding and current position is odd.
> | Cause | This Clob data uses UCS-2 character encoding so the position cannot be an odd value.
> | Action | Check your JDBC application.
> 6072 | Can't set autocommit to true during global transaction.
> | Cause | You cannot set Autocommit to On for global transactions.
> | Action | Check your JDBC application.
> 6073 | Can't commit using XAConnection during global transaction.
> | Cause | You cannot call commit during a global transaction.
> | Action | Check your JDBC application.
> 6074 | Can't rollback using XAConnection during global transaction.
> | Cause | You cannot call rollback during a global transaction.
> | Action | Check your JDBC application.
> 6076 | Cannot insert an empty row into this ResultSet.
> | Cause | Your database does not support inserting an empty row into a result set.
> | Action | Check your JDBC application.
> 6077 | The position specified is past the end of the BLOB or CLOB.
> | Cause | One of the specified parameters contains an invalid value.
> | Action | Check your JDBC application.
> 6078 | The operation was cancelled at the user's request.
> | Cause | The user cancelled the execute on another thread.
> | Action | None.
> 6079 | All of the data supplied could not be written.
> | Cause | One of the specified parameters contains an invalid value.
> | Action | Check your JDBC application.
> 6080 | The specified Savepoint does not have a numeric ID.
> | Cause | This Savepoint does not have a numeric ID.
> | Action | Check your JDBC application.
> 6081 | The specified Savepoint is un-named.
> | Cause | This Savepoint does not have a name.
> | Action | Check your JDBC application.
> 6082 | The specified Savepoint is invalid.
> | Cause | The application specified an invalid Savepoint.
> | Action | Check your JDBC application.
> 6083 | Discarded ResultSet during executeUpdate.
> | Cause | The application used executeUpdate for a SQLStatement that also returns Result Sets.
> | Action | Check your JDBC application if you really want to discard the result sets. Otherwise, modify your application so that it uses 'execute' instead of 'executeUpdate'.
> 6084 | Discarded rows affected count during executeQuery.
> | Cause | The application used executeQuery for a SQLStatement that also returns update counts.
> | Action | Check your JDBC application if you really want to discard the update counts. Otherwise, modify your application so that it uses 'execute' instead of 'executeUpdate'.
> 6085 | Execution timeout expired.
> | Cause | A timeout expired.
> | Action | Check the SQL statement used by your application. If it is correct, increase the query timeout value.
> 6086 | Can't set a savepoint during global transaction.
> | Cause | You cannot set a savepoint during global transactions.
> | Action | Check your JDBC application.
> 6087 | Can't release a savepoint during global transaction.
> | Cause | You cannot release a savepoint during global transactions.
> | Action | Check your JDBC application.
> 6088 | The requested parameter metadata is not available for the current statement.
> | Cause | The requested parameter metadata is not available.
> | Action | Check your JDBC application.
> 6089 | On a deleted row. Can not perform operation.
> | Cause | The method invocation is only valid if not positioned on a deleted row.
> | Action | Check your JDBC application.
> 6501 | A required input parameter could not be read.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6502 | A required output parameter could not be written.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6503 | A parameter was malformed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6504 | An unsupported mechanism was requested.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6505 | An invalid name was supplied.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6506 | A supplied name was of an unsupported type.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6507 | Incorrect channel bindings were supplied.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6508 | An invalid status code was supplied.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6509 | A token had an invalid signature.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6510 | No credentials were supplied.
> | Cause | An error occurred during OSLogon processing because the client application did not provide a user name or password, and the application disabled prompting for this information.
> | Action | Make sure the connection information provided by the application contains all required attributes.
> 6511 | No context has been established.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6512 | A token was invalid.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6513 | A credential was invalid.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6514 | The referenced credentials have expired.
> | Cause | An error occurred during authentication processing because the password for the specified user has expired.
> | Action | Update the password on the server host.
> 6515 | The context has expired.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6516 | A generic error occurred. Minor MGGS state is xxxx.
> | Cause | An error occurred during authentication processing. The accompanying error message indicates the exact nature of the problem; for example, "User not found" or "Invalid password provided."
> | Message | No access to requested information.
> | Cause | The server process has insufficient privileges or permission for the authenticating operation.
> | Action | Check the server privileges and permissions. The server must be started with root access on Linux or UNIX, or as a SYSTEM service on Windows.
> | Message | Attribute not supported on this platform.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> | Message | Get/set attribute failed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> | Message | Problems with user context.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> | Message | The name provided is not a properly formed domain name.
> | Cause | The maximum length allowed for a domain name is 15 characters.
> | Action | Make sure that the logon information provided by your client application is correct.
> | Message | The name provided is not a properly formed account name.
> | Cause | The user name is too long.
> | Action | Make sure that the logon information provided by your client application is correct.
> | Message | Invalid password.
> | Cause | The password is incorrect.
> | Action | Make sure that the logon information is correct. If the password is case-sensitive, check whether Caps Lock is turned on.
> | Message | No data to enumerate.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> | Message | No authorization.
> | Cause | The terminal or application Id was not allowed by RACF security system.
> | Action | Refer to the DataDirect SequeLink Administrator's Guide for information about configuring SequeLink Security for z/OS and activating terminal security.
> | Message | Account locked or disabled.
> | Cause | Your account has been locked out or disabled by the security administrator.
> | Action | Contact your RACF security administrator.
> | Message | User account locked during this time of the day.
> | Cause | This user account can be used only during specified times of the day.
> | Action | Contact your security administrator.
> | Message | User account expired.
> | Cause | The user account has been expired.
> | Action | Contact your security administrator.
> | Message | User not found.
> | Cause | Invalid user information was supplied.
> | Action | Make sure that the logon information provided by your client application is correct.
> | Message | User not found or invalid password provided.
> | Cause | An invalid user or password was supplied.
> | Action | Make sure that the logon information provided by your client application is correct.
> | Message | User must change password.
> | Cause | The password must be changed.
> | Action | Change the password. Contact your security administrator for the security rules that apply to passwords.
> | Message | Process must have SE_TCB_NAME privilege.
> | Cause | The SequeLink Server is running on Windows with an account missing the SE_TCB_NAME ("Act As Part of the Operating System") privilege.
> | Action | Contact your security administrator.
> | Message | Buffer supplied not large enough.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> | Message | New password does not conform to system requirements.
> | Cause | The new password does not conform to security rules.
> | Action | Choose another password. Contact your security administrator for the security rules that apply to passwords.
> | Message | Internal error occurred.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> | Message | netapi32.dll not found, or module not supported.
> | Cause | The required module was not found.
> | Action | Contact DataDirect Technologies technical support.
> | Message | User account revoked.
> | Cause | The user is not allowed to access the system.
> | Action | Contact your security administrator.
> | Message | SAFR_TICKETSERV service failure.
> | Cause | z/OS callable service R_TICKETSERV failed.
> | Action | Contact your z/OS system administrator to look for message VAIL114E in the server's VAILOG.
> | Message | SAFR_USERMAP service failure.
> | Cause | z/OS callable service R_USERMAP failed.
> | Action | Contact your z/OS system administrator to look for message VAIL114E in the server's VAILOG
> | Message | Authorization call failure.
> | Cause | An authorization call failed with an unexpected error code.
> | Action | Contact DataDirect Technologies technical support.
> | Message | Pluggable Authentication Module failure.
> | Cause | A Pluggable Authentication Module (PAM) error occurred.
> | Action | Contact DataDirect Technologies technical support.
> | Message | SEC_E_TARGET_UNKNOWN : The specified target is unknown or unreachable.
> | Cause | The Kerberos service principal was not found in the KDC.
> | Action | Verify that the Kerberos service principal used in the server ServiceKerberosPrincipalName attribute exists in the Kerberos database. Refer to the SequeLink Administrator's Guide for information about the "ServiceKerberosPrincipalName" service attribute.
> | Message | SEC_E_INTERNAL_ERROR : The Local Security Authority cannot be contacted.
> | Cause | An error occurred that did not map to an SSPI error code.
> | Action | Contact DataDirect Technologies technical support.
> | Message | SEC_E_NO_AUTHENTICATING_AUTHORITY : No authority could be contacted for authentication.
> | Cause | No authority could be contacted for authentication.
> | Action | The domain name of the authenticating party could be wrong, the domain could be unreachable, or a trust relationship failure might have occurred.
> | Message | No principal in keytab matches desired name.
> | Cause | The Kerberos service principal used by the server was found in the KDC, but its secret key was not added to the keytab file on the server system.
> | Action | The system administrator should export the secret key of the service principal and add this key to the keytab file.
> | Message | A generic error occurred. Minor MGGS state is xxxx.
> | Cause | An error occurred during authentication processing. The accompanying error message indicates the exact nature of the problem.
> | Action | Contact DataDirect Technologies technical support.
> 6517 | The quality-of-protection requested could not be provided.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6518 | The operation is forbidden by local security policy.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6519 | The operation or option is unavailable.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6520 | The requested credential element already exists.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6521 | The provided name was not a mechanism name.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6522 | Failed to load MGSS mechanism.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6523 | Memory allocation failed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6524 | Context call failed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6525 | Prompt for authentication information aborted by user.
> | Cause | An error occurred during authentication processing because the user cancelled from the dialog box prompting for authentication information (user name and user password).
> | Action | None.
> 6526 | MGSS module version mismatch.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6527 | MGSS module returned an unknown major status code.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6801 | Name given to entity instance is longer than 8 characters.
> | Cause | An error occurred during the startup of the SequeLink Server because the service name assigned to a SequeLink service or DB2 Interface was longer than 8 characters.
> | Action | Make sure that the service name of the SequeLink service or DB2 interface does not exceed 8 characters. Change the configuration of the SequeLink service or DB2 interface, if necessary. Then, restart the SequeLink Server.
> 6802 | No unique agent service found.
> | Cause | An error occurred during the startup of the SequeLink Server because a SequeLink Agent service was not created for the SequeLink Server or more than one SequeLink Agent service had been created for the SequeLink Server. The SequeLink Server will not start.
> | Action | Create the missing SequeLink Agent service or delete any duplicate SequeLink Agent services in the SequeLink Server configuration.
> 6803 | Name given to the agent service is longer than 8 characters.
> | Cause | An error occurred during the startup of the SequeLink Server because the name of a z/OS SequeLink Agent service was longer than 8 characters. The SequeLink Server will not start.
> | Action | Change the name of the z/OS SequeLink Agent service to be 8 characters or less. Then, restart the SequeLink Server.
> 6851 | Memory allocation failure.
> Cause | The requested amount of memory could not be allocated.
> Action | Free memory resources. If the problem persists, contact DataDirect Technologies technical support.
> 6852 | Internal SequeLink Administration error detected (I=<number>).
> | Cause | An internal error occurred in the SequeLink Manager.
> | Action | Contact DataDirect Technologies technical support.
> 6853 | Failed to access configuration at <string>.
> | Cause | SequeLink failed to open the SequeLink configuration file because an invalid connection string to a SequeLink Agent was specified or an invalid path to a SequeLink configuration file was specified.
> | Action | Re-attempt to open the SequeLink configuration with a correct connection string or a correct path.
> 6854 | Failed to cache configuration information.
> | Cause | An error occurred while caching configuration information from a SequeLink Agent or from a SequeLink configuration file.
> | Action | Contact DataDirect Technologies technical support.
> 6855 | Invalid attribute ID <id>.
> | Cause | An invalid service attribute ID was specified.
> | Action | Specify a valid ID for the service attribute. For more information about specifying SequeLink service attributes, refer to the SequeLink Administrator's Guide.
> 6856 | Value for attribute <ID or name> is no numeric value.
> | Cause | The service attribute value specified requires a numeric value.
> | Action | Specify a numeric value for the service attribute value. For more information about specifying SequeLink service attributes, refer to the SequeLink Administrator's Guide.
> 6858 | Specified value <attribute value> for attribute <name or ID> is not valid. Values between <lower limit> and <upper limit> are valid.
> | Cause | The specified service attribute value was invalid.
> | Action | Specify the service attribute value, using a numeric value between <lower limit> and <upper limit>.
> 6859 | Specified value <attribute value> for attribute <ID or name> is not valid.
> | Cause | The specified service attribute value was invalid.
> | Action | Specify a valid value for the service attribute.
> 6861 | Invalid values for boolean attribute <ID or name>.
> | Cause | The specified service attribute value is not a valid boolean value.
> | Action | Specify a valid value for the service attribute.
> 6862 | Length of string attribute <ID or name> cannot be larger then <length> characters.
> | Cause | The specified service attribute value cannot exceed the maximum string length allowed.
> | Action | Specify a valid value for the service attribute.
> 6863 | Attribute type not supported.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 6864 | Unable to determine local host name.
> | Cause | SequeLink was unable to determine the name of the local host.
> | Action | Contact DataDirect Technologies technical support.
> 6865 | Invalid service name <service name>.
> | Cause | An invalid SequeLink service name was specified.
> | Action | Specify a valid SequeLink service name. Remember that service names are case sensitive.
> 6866 | Invalid service template ID.
> | Cause | An invalid SequeLink service template ID was specified.
> | Action | Specify a valid SequeLink service template ID. For more information about template IDs, refer to the SequeLink Administrator's Guide.
> 6867 | Only one agent service may be created.
> | Cause | An attempt was made to create a duplicate SequeLink Agent service.
> | Action | None.
> 6868 | Service <service name> is still active.
> | Cause | An attempt was made to delete a SequeLink service that was still running.
> | Action | Stop the SequeLink service before you delete it.
> 6869 | Failed to check if service <service name> is still active.
> | Cause | SequeLink could not check if the SequeLink service was active. The SequeLink service may have been experiencing heavy traffic or may have been in an incorrect state.
> | Action | Re-check the status of the SequeLink service. If the problem persists, contact DataDirect Technologies technical support.
> 6870 | Attribute <ID or name> is not valid <object> attribute.
> | Cause | The specified attribute is not valid for the SequeLink service or server data source.
> | Action | Specify a valid attribute for the SequeLink service or server data source. For more information about specifying SequeLink service attributes, refer to the SequeLink Administrator's Guide.
> 6871 | Attribute <ID or name> may be added only once.
> | Cause | An attempt to add an attribute that already existed in the SequeLink service or server data source configuration was detected.
> | Action | None.
> 6872 | Attribute <ID or name> is a primary key.
> | Cause | The specified attribute is required by the SequeLink service or server data source and cannot be deleted.
> | Action | None.
> 6873 | Attribute <ID or name> not found in <object>.
> | Cause | The specified attribute cannot be found in the SequeLink service or server data source.
> | Action | Check your SequeLink service or server data source configuration to verify that the specified attribute exists in the configuration. For more information about specifying SequeLink service attributes, refer to the SequeLink Administrator's Guide.
> 6874 | Attribute <ID or name> must at least exist once in <object>.
> | Cause | The specified attribute could not be found in the SequeLink service or server data source.
> | Action | Check your SequeLink service or server data source configuration to verify that the specified attribute exists in the configuration. For more information about specifying SequeLink service attributes, refer to the SequeLink Administrator's Guide.
> 6875 | Function not available for platform configuration.
> | Cause | The specified administrative function was not supported for the server operating system.
> | Action | None.
> 6877 | Monitor not available for service <service name>.
> | Cause | Monitoring has not been enabled for this SequeLink service.
> | Action | Enable a monitoring profile for the service, and make sure that the service is active. For more information about enabling profiles for a SequeLink service, refer to the SequeLink Administrator's Guide.
> 6878 | Invalid data source name <service name>.
> | Cause | An invalid server data source name was specified.
> | Action | Specify a correct server data source name. Server data source names are case-sensitive. For more information about creating server data sources, refer to the SequeLink Administrator's Guide.
> 6879 | Cannot create a data source for an agent service.
> | Cause | Server data sources cannot be created for SequeLink Agent services.
> | Action | Make sure that you are trying to create a server data source for a SequeLink data access service.
> 6880 | Only one <object> may exist.
> | Cause | Only one instance of the object may exist.
> | Action | Contact DataDirect Technologies technical support.
> 6881 | Invalid <object>.
> | Cause | An invalid SequeLink service name or server data source name was specified.
> | Action | Specify a correct SequeLink service name or server data source name.
> 6882 | No <object> exists.
> | Cause | No instance of the object exists.
> | Action | Contact DataDirect Technologies technical support.
> 6883 | <object> already exists.
> | Cause | The SequeLink service name or the server data source name already exists.
> | Action | Contact DataDirect Technologies technical support.
> 6884 | <object> still used by service <service name>.
> | Cause | The object is still used by the specified SequeLink service.
> | Action | Contact DataDirect Technologies technical support.
> 6885 | Cannot delete required attribute <ID or name>.
> | Cause | The attribute cannot be deleted because it is required.
> | Action | Contact DataDirect Technologies technical support.
> 6886 | Unable to determine event trace location for service <service name>.
> | Cause | An event trace file for the SequeLink service could not be located. Either SequeLink service information could not be retrieved or the ServiceEventTraceLocation service attribute could not be found in the service information.
> | Action | Make sure that the SequeLink service is active. If it is, check the "ServiceEventTraceLocation" service attribute to make sure that it is specified correctly. For more information about specifying SequeLink service attributes, refer to the SequeLink Administrator's Guide.
> 6887 | Event trace not available for service <service name>. Check if the service is running and an event trace profile is created.
> | Cause | Event tracing was not enabled for the specified SequeLink service.
> | Action | Enable an event tracing profile for the SequeLink service, and make sure that the SequeLink service is running. For more information about enabling profiles for a SequeLink service, refer to the SequeLink Administrator's Guide.
> 6888 | Failed to open event trace file <file name>.
> | Cause | The specified event trace file could not be opened.
> | Action | Make sure that you have sufficient privileges to open and read the file, and make sure that the file is not being used by another SequeLink service.
> 6890 | Invalid array index <number> for attribute <ID or name>.
> | Cause | An invalid attribute array index was specified.
> | Action | Specify a valid array index.
> 6892 | Invalid session ID <number>.
> | Cause | An invalid session ID was specified.
> | Action | Specify a correct session ID.
> 6893 | No configuration opened.
> | Cause | A SequeLink Manager request was made that required a connection to a SequeLink Agent or a SequeLink configuration file.
> | Action | Connect to a SequeLink Agent or open a SequeLink configuration file before making SequeLink Manager requests.
> 6894 | Invalid numeric value <value>.
> | Cause | A value was specified that could not be converted to a numeric value.
> | Action | Specify a valid numeric value.
> 6895 | Failed to prompt for user ID and password.
> | Cause | The callback function to prompt for a user ID and password failed.
> | Action | Contact DataDirect Technologies technical support.
> 6896 | Invalid attribute name <name>.
> | Cause | An invalid attribute name was specified.
> | Action | Specify a valid attribute. For more information about specifying SequeLink service attributes, refer to the SequeLink Administrator's Guide.
> 6897 | No agent service found in <file name>.
> | Cause | A SequeLink Agent service was not defined in the specified SequeLink configuration file.
> | Action | Create a SequeLink Agent service. For information about creating SequeLink services, refer to the SequeLink Administrator's Guide.
> 6898 | Unable to locate local SequeLink server configuration file.
> | Cause | A local SequeLink configuration file could not be located.
> | Action | Make sure that you have specified the local configuration file correctly.
> 6899 | SequeLink Administration library has not been initialized.
> | Cause | A call to the SequeLink Manager library was made before calling SLMAM_Init.
> | Action | Contact DataDirect Technologies technical support.
> 6900 | Service <service name> already exists.
> | Cause | A SequeLink service with the same service name already exists.
> | Action | Specify a unique service name for the SequeLink service.
> 6901 | Invalid token in service name.
> | Cause | The specified service name contains a token that is not allowed.
> | Action | Choose another name for your SequeLink service.
> 6902 | Service <service name> is already started.
> | Cause | An attempt was made to start a SequeLink service that was already started.
> | Action | None.
> 6903 | Service <service name> is not active.
> | Cause | The specified SequeLink service is not active.
> | Action | None.
> 6904 | No monitor profile available for service <service name>.
> | Cause | The specified SequeLink service does not have monitoring enabled.
> | Action | Enable a monitoring profile for the SequeLink service. For more information about enabling monitoring profiles, refer to the SequeLink Administrator's Guide.
> 6905 | A monitor profile already exists for service <service name>.
> | Cause | The specified SequeLink service already has monitoring enabled.
> | Action | None.
> 6906 | No event log profile available for service <service name>.
> | Cause | The specified SequeLink service does not have event tracing enabled.
> | Action | Enable an event tracing profile for the SequeLink service. For more information about enabling profiles for SequeLink services, refer to the SequeLink Administrator's Guide.
> 6911 | The default data source for service <service name> may not be destroyed.
> | Cause | An attempt to delete the default server data source was detected. The default server data source for the specified SequeLink service cannot be deleted.
> | Action | None.
> 6912 | Unable to find a default data source for service <service name>.
> | Cause | The default server data source for the specified SequeLink service could not be found.
> | Action | Contact DataDirect Technologies technical support.
> 6913 | Session monitoring has not been enabled for service <service name>.
> | Cause | The monitoring profile enabled for the specified SequeLink service does not provide session or statement counters.
> | Action | Enable a monitoring profile for the SequeLink service that uses session or statement counters. For more information about enabling profiles for SequeLink services, refer to the SequeLink Administrator's Guide.
> 6914 | Failed to start service <service name>.
> | Cause | The specified SequeLink service could not be started.
> | Action | Details about the failure are logged in the service debug log file, the event trace file, or the system logging facility. Examine these details to troubleshoot the problem.
> 7361 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7362 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7363 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7364 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7365 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7366 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7367 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7368 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7369 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7370 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7391 | Driver cannot perform requested operation: {0}.
> | Cause | The method {0} is not supported by this version of the JDBC driver.
> | Action | Verify the method {0} in your JDBC application.
> 7392 | Object is closed. The JDBC application used an illegal method on a closed object.
> | Cause | Object is closed. The JDBC application used an illegal method on a closed object.
> | Action | Correct your JDBC application.
> 7393 | The value specified for parameter `{0}` is invalid.
> | Cause | The value specified for parameter `{0}` is invalid.
> | Action | Verify the value of the parameter '{0}' in your JDBC application.
> 7394 | The method call `{0}' is not supported on a forward-only result set. The JDBC application used an illegal method on a forward-only result set.
> | Cause | The method `{0}' is not supported on a forward-only result set. The JDBC application used an illegal method on a forward-only result set.
> | Action | Correct your JDBC application.
> 7395 | Timeout expired.
> | Cause | A timeout expired.
> | Action | Verify that the SequeLink Server is running and that you have specified the correct network address of the host. If your configuration is correct, increase the connection timeout value.
> 7396 | The specified URL is not accepted: {0}.
> | Cause | The specified URL is not accepted: {0}.
> | Action | Verify the specified connection URL.
> 7397 | Insufficient information to connect. Missing parameters are: {0}.
> | Cause | Insufficient information to connect was supplied. Missing parameters are: {0}.
> | Action | Make sure that you specify the connection URL completely. For information about the syntax of the connection URL, refer to the SequeLink Administrator's Guide.
> 7398 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7399 | Method {0} cannot be called when a result set is open. The JDBC application used an illegal method on a Statement, which has an open result set.
> | Cause | Method {0} cannot be called when a result set is open. The JDBC application used an illegal method on a Statement, which has an open result set.
> | Action | Correct your JDBC application.
> 7400 | Error occurred while reading properties file.
> | Cause | An error occurred while reading the properties file.
> | Action | Contact DataDirect Technologies technical support.
> 7401 | Insufficient information to log on to the database. Missing parameters are: {0}.
> | Cause | Insufficient information was provided to log on to the database. Missing parameters are indicated by {0}.
> | Action | Re-attempt the connection, making sure that you specify the connection URL completely.
> 7402 | Unexpected error occurred during timed connection startup.
> | Cause | An unexpected error occurred during timed connection startup.
> | Action | Obtain the next exception for more information. If necessary, contact DataDirect Technologies technical support.
> 7403 | Statement did not generate a row count. executeUpdate() cannot be used on a statement that returns a result set.
> | Cause | The statement did not generate a row count. executeUpdate() cannot be used on a statement that returns a result set.
> | Action | Correct your JDBC application.
> 7404 | Statement did not generate a result set. executeQuery() cannot be used on a statement that does not return a result set.
> | Cause | The statement did not generate a result set. executeQuery() cannot be used on a statement that does not return a result set.
> | Action | Correct your JDBC application.
> 7405 | Conversion not supported: {0}() for SQL data type {1}. The specified method is illegal for a column of the specified SQL data type.
> | Cause | The specified method is invalid for a column of the specified SQL data type.
> | Action | Correct your JDBC application.
> 7406 | Conversion of value `{0}' at column `{1}' failed. The data type conversion for the specified column failed.
> | Cause | The data type conversion for the specified column failed.
> | Action | Correct your JDBC application.
> 7407 | An unsupported SQL data type has been specified: {0}. The specified SQL data type is invalid.
> | Cause | The specified SQL data type is invalid.
> | Action | Correct your JDBC application.
> 7408 | Invalid use of null string.
> | Cause | A null string is incorrectly used as a parameter or a method of DatabaseMetaData.
> | Action | Correct your JDBC application.
> 7409 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7410 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7411 | An internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7412 | Use register OutParameter (int, int, int) for SQL data type {0}. The method registerOutParameter (int, int) is not supported for DECIMAL data.
> | Cause | The method registerOutParameter (int, int) is not supported for DECIMAL data.
> | Action | Correct your JDBC application.
> 7413 | No output parameter is registered at parameter index {0}. registerOutParameter must be called prior to getXXX() on a CallableStatement.
> | Cause | registerOutParameter must be called prior to getXXX() on a CallableStatement.
> | Action | Correct your JDBC application.
> 7414 | Conversion not supported: {0}() used for SQL data type {1} at parameter index {2}. The specified method is illegal for a column of the specified SQL data type.
> | Cause | The specified method is invalid for a column of the specified SQL data type.
> | Action | Correct your JDBC application.
> 7415 | Illegal method call on a PreparedStatement. The methods on Statement that have a SQL statement as parameter, like execute(sql) and addBatch(sql), are not supported on PreparedStatements.
> | Cause | The methods on Statement that have a SQL statement as parameter, like execute(sql) and addBatch(sql), are not supported on PreparedStatements.
> | Action | Check your JDBC application.
> 7416 | The number of input parameters is different from the previous parameter set.
> | Cause | The number of input parameters is different from the previous parameter set.
> | Action | Check your JDBC application.
> 7417 | Output parameters with batch updates are not supported.
> | Cause | You cannot use output parameters with batch updates.
> | Action | Check your JDBC application.
> 7418 | An object of the unsupported class {0} has been specified. The JDBC application specified an object of the unsupported class as parameter for PreparedStatement.setObject().
> | Cause | The JDBC application specified an object of the unsupported class as parameter for PreparedStatement.setObject().
> | Action | Check your JDBC application.
> 7419 | The number of bytes in a unicode stream cannot be an odd value.
> | Cause | The number of bytes in a Unicode stream cannot be an odd value.
> | Action | Check your JDBC application.
> 7420 | Some parameters are not defined. The application did not call a setXXX() method for each parameter in the SQL statement.
> | Cause | Some parameters are not defined. The application did not call a setXXX() method for each parameter in the SQL statement.
> | Action | Check your JDBC application for undefined parameters.
> 7421 | Illegal method call. There is no current row. This method invocation is only valid when the result set has a current row.
> | Cause | This method invocation is only valid when the result set has a current row.
> | Action | Check your JDBC application.
> 7422 | Positioned updates are not supported.
> | Cause | Positional updates are not supported by this version of the JDBC driver.
> | Action | Check your JDBC application.
> 7423 | The column `{0}' is not found. An invalid column name has been specified.
> | Cause | The specified column was not found. An invalid column name was specified.
> | Action | Check your JDBC application.
> 7424 | The method {0}() does not apply to columns of type {1}.
> | Cause | The specified method does not apply to this type of column.
> | Action | Check your JDBC application.
> 7425 | A batch cannot contain SQL statements that return a result set.
> | Cause | A batch cannot contain SQL statements that return a result set.
> | Action | Check your JDBC application. Make sure that only row count generating statements are used in a batch.
> 7426 | Driver does not support batches containing stream variables.
> | Cause | The JDBC driver does not support large objects in batches.
> | Action | Check your JDBC application.
> 7427 | Handshake failure: You are trying to connect to a server that is not a SequeLink Server.
> | Cause | An attempt was made to connect to a server that is not a SequeLink Server.
> | Action | Make sure that the connection information configured at the SequeLink Client is specified correctly to connect to the SequeLink Server.
> 7428 | Handshake failure: You are trying to connect to a server that is not a SequeLink Server.
> | Cause | The SequeLink Client is incompatible with the version of the SequeLink Server to which it tried to connect.
> | Action | Verify that the versions of your SequeLink Client and SequeLink Server are compatible. Contact DataDirect Technologies technical support, if necessary.
> 7429 | Handshake failure: A protocol error occurred during the connection setup.
> | Cause | An attempt was detected to connect to a SequeLink Server running an incompatible version of SequeLink.
> | Action | Verify that the versions of your SequeLink Client and SequeLink Server are compatible. Contact DataDirect Technologies technical support, if necessary.
> 7430 | Driver does not support: different parameter target types. The JDBC driver does not allow you to change the type of parameters, once they are registered.
> | Cause | The JDBC driver does not allow you to change the type of parameters once they are registered.
> | Action | Check your JDBC application. Possibly, add a call to clearParameters().
> 7431 | Column index out of bounds. The column index your JDBC application specified is out of bounds.
> | Cause | Your JDBC application specified a column index that is out of bounds.
> | Action | Check your JDBC application.
> 7432 | Internal error: Invalid state of statement context `{0}'.
> | Cause | The state of statement context `{0}' was invalid.
> | Action | Contact DataDirect Technologies technical support.
> 7433 | Conversion not supported: setObject() with object type {0} used for SQL data type {1} at parameter index {2}.
> | Cause | This type of conversion not supported.
> | Action | Check your JDBC application.
> 7434 | An authentication mechanism could not be successfully negotiated.
> | Cause | The SequeLink Server did not specify an authentication mechanism supported by the SequeLink Client.
> | Action | Make sure that the SequeLink Server specifies an authentication mechanism supported by the SequeLink Client. Refer to the SequeLink Administrator's Guide for information about setting authentication.
> 7435 | Unable to resolve transliteration: {0}. The JDBC driver does not support the transliteration used by your server.
> | Cause | The JDBC driver does not support the transliteration used by your server.
> | Action | Contact DataDirect Technologies technical support.
> 7436 | Error occurred while processing transliteration table: {0}.
> | Cause | An error occurred while processing a transliteration table.
> | Action | Contact DataDirect Technologies technical support.
> 7437 | Transliteration table corrupt: {0}.
> | Cause | A transliteration table was corrupted.
> | Action | Contact DataDirect Technologies technical support.
> 7438 | NumberFormatException during setObject() with object type {0} used for SQL data type {1} at parameter index {2}.
> | Cause | A NumberFormatException occurred during setObject() with object type {0} used for SQL data type {1} at parameter index {2}.
> | Action | The subsequent exception will give you more information. Check your JDBC application.
> 7439 | XA-Open failed with return code {0}.
> | Cause | XA-Open failed with the specified return code.
> | Action | Refer to the X/Open XA Specification for more information about the return code.
> 7440 | XA-Close failed with return code {0}.
> | Cause | XA-Close failed with the specified return code.
> | Action | Refer to the X/Open XA Specification for more information about the return code.
> 7441 | An error occurred while processing the cache of the insensitive scrollable resultset.
> | Cause | An error occurred while processing the cache of the insensitive scrollable result set.
> | Action | Contact DataDirect Technologies technical support.
> 7442 | FetchSize must be less than maxRowSize.
> | Cause | FetchSize must be less than maxRowSize.
> | Action | Check your JDBC application.
> 7443 | Method {0} cannot be called when the statement is executed.
> | Cause | The JDBC driver cannot change the setmaxFieldSize when the statement is already executed.
> | Action | Check your JDBC application.
> 7444 | Value of setMaxFieldSize exceeds maximum limit.
> | Cause | The value of setMaxFieldSize exceeded the maximum limit. To avoid excessive memory use, the JDBC driver limits the maximum value of setMaxFieldSize.
> | Action | If you require higher values, contact DataDirect Technologies technical support.
> 7445 | Internal error occurred.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7446 | Error occurred while processing transliteration table: {0}.
> | Cause | An error occurred while processing a transliteration table.
> | Action | Contact DataDirect Technologies technical support.
> 7447 | An unsupported transliteration type has been specified: {0}.
> | Cause | An unsupported transliteration type has been specified.
> | Action | Contact DataDirect Technologies technical support.
> 7448 | You are attempting to use this DataDirect Technologies software from an application that is not licensed to use it.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7449 | Server asked for unknown encryption.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7450 | No initialization vector was sent when one was expected.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7451 | Initialization vector has wrong size ({0} bytes). Expected {1} bytes.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7452 | Error occurred during transliteration.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7481 | Result set type is changed from `{0}' to `{1}'. This is a SQL Warning.
> | Cause | The result set type is changed from `{0}' to `{1}'. This is a SQL Warning.
> | Action | Refer to the SequeLink Developer's Reference for information about restrictions on scrollable cursors.
> 7482 | Result set concurrency is changed from `{0}' to `{1}'. This is a SQL Warning.
> | Cause | Result set concurrency is changed from `{0}' to `{1}'. This is a SQL Warning.
> | Action | Refer to the SequeLink Developer's Reference for information about restrictions on scrollable cursors.
> 7483 | Finalization thread could not be started. This is a SQL Warning. The JDBC driver is unable to "finalize" Connection and Statement objects during garbage collection.
> | Cause | Finalization thread could not be started. The JDBC driver is unable to finalize Connection and Statement objects during garbage collection.
> | Action | Make sure that your application explicitly closes the Connection and Statement objects.
> 7491 | Object is closed.
> | Cause | The object is closed.
> | Action | Check your JDBC application.
> 7492 | Cannot set autocommit to `on' for global transaction.
> | Cause | You cannot set Autocommit to "on" for global transactions.
> | Action | Check your JDBC application.
> 7493 | Cannot commit for global transaction.
> | Cause | Global transaction could not be committed.
> | Action | Check your JDBC application.
> 7494 | Cannot rollback for global transaction.
> | Cause | Global transaction could not be rolled back.
> | Action | Check your JDBC application.
> 7495 | Reclaim of open connection is not supported.
> | Cause | The JDBC driver does not support the reclaim of open connections.
> | Action | Check your JDBC application.
> 7720 | [SSL]Illegal port number specified.
> | Cause | An invalid port number was specified for the Port parameter in the proxy server configuration file.
> | Action | Check the Port parameter in the proxy server configuration file.
> 7721 | [SSL]Illegal value for maximum number of connections.
> | Cause | An invalid value for the MaxConnections parameter in the proxy server configuration file was specified.
> | Action | Check the MaxConnections parameter in the proxy server configuration file.
> 7722 | [SSL]Illegal value for Packet size.
> | Cause | An invalid value for the InitialPacketSize parameter in the proxy server configuration file was specified.
> | Action | Check the InitialPacketSize parameter in the proxy server configuration file.
> 7723 | [SSL]Illegal transfer mode specified.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7724 | [SSL]Illegal log level specified.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7725 | [SSL]Illegal "sta16timeout" value specified.
> | Cause | An illegal value for the CloseWaitTime parameter in the proxy server configuration file was specified
> | Action | Check the CloseWaitTime parameter in the proxy server configuration file.
> 7726 | [SSL]Internal error: proxy server state error.
> | Cause | An unexpected error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7727 | [SSL]Cannot create server listener on given port.
> | Cause | The proxy server was unable to create a TCP/IP socket to listen for incoming connections. The proxy server may already be running or an incorrect port number was specified.
> | Action | Check the detailed exceptions. Check the Port parameter in the proxy server configuration file. Check the AdminPort parameter in the proxy server configuration file. Make sure that the proxy server is not already running at the host.
> 7728 | [SSL]Illegal server port number specified.
> | Cause | An invalid port number was specified for the ServerPort parameter in the proxy server configuration file.
> | Action | Check the ServerPort parameter in the proxy server configuration file.
> 7729 | [SSL]Configuration file not found.
> | Cause | The specified proxy server configuration file was not found in the current directory. The proxy server configuration file is formed by adding the extensions .cfg to the proxy server name. The name of the proxy server can be specified using the last command-line parameter of the SequeLink Manager command used to start the proxy server.
> | Action | Verify that the proxy server configuration file has the extension .cfg in its name and exists in the current directory.
> 7730 | [SSL]Cannot read configuration file.
> | Cause | The specified configuration file is not readable.
> | Action | Check the privileges of the specified configuration file.
> 7731 | [SSL]Cannot create file inputstream.
> | Cause | Internal error. An IOException occurred while trying to read from the proxy server configuration file.
> | Action | Check the console of the proxy server machine for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7732 | [SSL]Cannot read key/value pairs from stream into properties object.
> | Cause | Internal error. An IOException occurred when trying to interpret the proxy server configuration file as a properties object.
> | Action | Check the console of the proxy server machine for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7733 | [SSL]Non-numerical value for port specified.
> | Cause | A non-numeric value is specified for the Port parameter in the proxy server configuration file.
> | Action | Check the Port parameter in the proxy server configuration file.
> 7734 | [SSL]Non-numerical value for server port specified.
> | Cause | The proxy server configuration file specified an invalid value for the ServerPort parameter.
> | Action | Check the ServerPort parameter in the proxy server configuration file.
> 7735 | [SSL]Non-numerical value for maximum number of connections specified.
> | Cause | The proxy server configuration file specified an invalid value for the MaxConnections parameter.
> | Action | Check the MaxConnections parameter in the proxy server configuration file.
> 7736 | [SSL]Non-numerical value for maximum packet size specified.
> | Cause | The proxy server configuration file specified an invalid value for the InitialPacketSize parameter.
> | Action | Check the InitialPacketSize parameter in the proxy server configuration file.
> 7737 | [SSL]Illegal value for LogLevel specified.
> | Cause | The proxy server configuration file specified an invalid value for the LogLevel parameter.
> | Action | Check the LogLevel parameter in the proxy server configuration file.
> 7738 | [SSL]Illegal value for TransferMode specified.
> | Cause | The proxy server configuration file specified an invalid value for the TransferMode parameter.
> | Action | Check the TransferMode parameter in the proxy server configuration file.
> 7739 | [SSL]Illegal administration port number specified.
> | Cause | The proxy server configuration file specified an illegal port number for the AdminPort parameter.
> | Action | Check the AdminPort parameter in the proxy server configuration file.
> 7740 | [SSL]Non-numerical value for administration port specified.
> | Cause | The proxy server configuration file specified a non-numeric value for the AdminPort parameter.
> | Action | Check the AdminPort parameter in the proxy server configuration file.
> 7741 | [SSL]Non-numerical value for backlog specified.
> | Cause | The proxy server configuration file specified a non-numeric value for the BackLog parameter.
> | Action | Check the BackLog parameter in the proxy server configuration file.
> 7742 | [SSL]Illegal backlog value specified.
> | Cause | An illegal value for the BackLog parameter is specified in the proxy server configuration file.
> | Action | Check the BackLog parameter in the proxy server configuration file.
> 7743 | [SSL]Use different port number for administration port.
> | Cause | An attempt was made to use the same port number for the proxy server port (Port parameter) used for listening to incoming requests and the SequeLink Proxy Server administration port (AdminPort parameter).
> | Action | Check the Port parameter in the proxy server configuration file. Check the AdminPort parameter in the SequeLink Proxy Server configuration file.
> 7744 | [SSL]Fatal error occurred while receiving accept.
> | Cause | Internal error. An error occurred when accepting an incoming connection request.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7745 | [SSL]Host name not found or empty in configuration file.
> | Cause | A server that is not a SequeLink Server has been specified using the proxy server Host parameter.
> | Action | Check the Host parameter in the SequeLink Proxy Server configuration file. Make sure that it specifies a SequeLink Server.
> 7746 | [SSL]Non-numerical value for close wait time specified.
> | Cause | The proxy server configuration file specified a non-numeric value for the CloseWaitTime parameter.
> | Action | Check the CloseWaitTime parameter in the SequeLink Proxy Server configuration file.
> 7747 | [SSL]Network read error in client read message length operation.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file name for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7748 | [SSL]Network read error in client read message operation.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7749 | [SSL]End of input in client read message length operation.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7750 | [SSL]End of input in client read message operation.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7751 | [SSL]Network write error in client write operation.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7752 | [SSL]Client message decoding failed.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7753 | [SSL]Invalid client connection.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7754 | [SSL]Closing client connection failed.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7755 | [SSL]Internal error in client read message operation.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7756 | [SSL]Network write error in client write SSL/TLS Alert message.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7757 | [SSL]Network read error in server read message length operation.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7758 | [SSL]Network read error in server read message operation.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7759 | [SSL]Network read error in server read message length operation.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7760 | [SSL]End of input in server read message operation.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7761 | [SSL]Network write error in server write operation.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7762 | [SSL]Server message decoding failed.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7763 | [SSL]Invalid server connection.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7764 | [SSL]Connection to server failed.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7765 | [SSL]Closing server connection failed.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7766 | [SSL]Internal error in server read message operation.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7767 | [SSL]Network write error in server write SSL/TLS Alert message.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7768 | [SSL]Cannot add connection object to connection list.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7769 | [SSL]Graceful disconnection failed.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7770 | [SSL]Data transfer between client and server already active.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7771 | [SSL]State error.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7772 | [SSL]Internal error: no data to process.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7773 | [SSL]Could not allocate memory for send/receive buffer.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7774 | [SSL]Could not start new thread.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7775 | [SSL]Maximum number of simultaneous connections reached. Cannot add connection to connection list.
> | Cause | The maximum number of connections specified by the MaxConnections parameter in the SequeLink Proxy Server configuration file has been reached.
> | Action | Check the MaxConnections parameter in the SequeLink Proxy Server configuration file. Increase the value of this parameter, if necessary.
> 7776 | [SSL]Cannot create a connection list with a negative or zero number of maximum connections.
> | Cause | An illegal value is specified for the MaxConnections parameter in the proxy server configuration file.
> | Action | Check the MaxConnections parameter in the SequeLink Proxy Server configuration file.
> 7777 | [SSL]Internal error: connection list state error.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7778 | [SSL]Could not start new thread.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the SequeLink Proxy Server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7779 | [SSL]Cannot create a dictionary for log file.
> | Cause | The directory specified by the LogDir parameter in the proxy server configuration file does not exist. An error occurred in an attempt to create the missing directory.
> | Action | Check the LogDir parameter in the SequeLink Proxy Server configuration file. Verify that the required file privileges are set. If the previous actions do not resolve the problem, try to create the logging directory explicitly.
> 7780 | [SSL]Cannot access log file.
> | Cause | The proxy server log file already exists and an error occurred when trying to read from or write to this file.
> | Action | Check the console of the SequeLink Proxy Server machine for more detailed error messages. Verify that the required file privileges are set. Make sure that no other process is using the log file.
> 7781 | [SSL]Seek in log file failed.
> | Cause | An internal error occurred when processing an existing log file.
> | Action | Verify that the required file privileges are set. Make sure that no other process is using the log file. If the previous actions do not resolve the problem, contact DataDirect Technologies technical support.
> 7782 | [SSL]Get file descriptor failed.
> | Cause | An internal error occurred when processing an existing log file.
> | Action | Verify that the required file permission are set. Make sure that no other process is using the file. If the previous actions do not resolve the problem, contact DataDirect Technologies technical support.
> 7783 | [SSL]Cannot create file outputstream.
> | Cause | An error occurred when trying to write to the proxy server log file.
> | Action | Check the proxy server console for more detailed error messages. Verify that the required file permissions are set.
> 7784 | [SSL]Cannot create endpoint for proxy server administration.
> | Cause | The Proxy server was unable to create the TCP/IP socket to listen for incoming administration requests. The proxy server may already be running or an invalid TCP/IP port may have been specified.
> | Action | Check the detailed exceptions. Check the AdminPort parameter in the proxy server configuration file. Make sure that a proxy server is not already running at the host.
> 7785 | [SSL]Unknown operation requested by system administrator.
> | Cause | A non-fatal internal error occurred.
> | Action | Check the proxy server log file for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7786 | [SSL]Could not connect to proxy server: check if the proxy server was started.
> | Cause | An attempt was made to stop a proxy server, but a proxy server was not found. The proxy server may already be stopped.
> | Action | Make sure the proxy server is started before stopping it.
> 7787 | [SSL]Cannot create data output stream over socket.
> | Cause | An internal error occurred when trying to stop a running proxy server.
> | Action | Check the console of the proxy server machine for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7788 | [SSL]Write to data output stream failed.
> | Cause | An internal error occurred when trying to stop a running SequeLink Proxy Server.
> | Action | Check the console of the SequeLink Proxy Server machine for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7789 | [SSL]Write to data output stream failed.
> | Cause | An internal error occurred when trying to stop a running SequeLink Proxy Server.
> | Action | Check the console of the SequeLink Proxy Server machine for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7790 | [SSL]Write to data output stream failed.
> | Cause | An internal error occurred when trying to stop a running SequeLink Proxy Server.
> | Action | Check the console of the SequeLink Proxy Server machine for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7791 | [SSL]Unable to close end point.
> | Cause | An internal error occurred when trying to stop a running SequeLink Proxy Server.
> | Action | Check the console of the SequeLink Proxy Server machine for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7792 | [SSL]Non-numerical value for port specified.
> | Cause | A non-numeric value was specified for the AdminPort parameter in the SequeLink Proxy Server configuration file. The AdminPort parameter must have a numeric value.
> | Action | Check the AdminPort parameter in the SequeLink Proxy Server configuration file.
> 7793 | [SSL]Unknown local host.
> | Cause | An internal error occurred when trying to stop a running SequeLink Proxy Server.
> | Action | Contact DataDirect Technologies technical support.
> 7794 | [SSL]Supply name of proxyserver.
> | Cause | Internal error. No name is specified when starting a SequeLink Proxy Server.
> | Action | Contact DataDirect Technologies technical support.
> 7795 | [SSL]Cannot create data input stream over socket.
> | Cause | An internal error occurred when trying to stop a running SequeLink Proxy Server.
> | Action | Check the console of the SequeLink Proxy Server machine for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7796 | [SSL]Network read error in read message length.
> | Cause | An internal error occurred when trying to stop a running SequeLink Proxy Server.
> | Action | Check the console of the SequeLink Proxy Server machine for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7797 | [SSL]Network read error in read message length.
> | Cause | An internal error occurred when trying to stop a running SequeLink Proxy Server.
> | Action | Check the console of the SequeLink Proxy Server machine for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7798 | [SSL]Internal error: IOException in read token operation.
> | Cause | An internal error occurred when trying to stop a running SequeLink Proxy Server.
> | Action | Check the console of the SequeLink Proxy Server machine for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7799 | [SSL]Not an administration message.
> | Cause | The running SequeLink Proxy Server received an administration request, but the message was not recognized. You may be trying to connect to the administration port.
> | Action | Check the connection information configured at the SequeLink Client. Check the AdminPort parameter in the proxy server configuration file.
> 7800 | [SSL]Administration request only allowed from localhost.
> | Cause | An attempt was made to stop a SequeLink Proxy Server running on another host.
> | Action | You cannot stop a proxy server running on another host. Stop the SequeLink Proxy Server from the host on which it is running.
> 7801 | [SSL]Error while accepting incoming connection on administration port.
> | Cause | An internal error occurred when trying to stop a running SequeLink Proxy Server.
> | Action | Check the console of the SequeLink Proxy Server machine for more detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7802 | [SSL]No administration listener started: could not stop proxy server.
> | Cause | An attempt was made to stop a SequeLink Proxy Server that has no administration listener started.
> | Action | Check the AdminPort parameter in the SequeLink Proxy Server configuration file.
> 7803 | [SSL]Proxy server with the name "<proxy server name>" already running.
> | Cause | A remote administration internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7804 | [SSL]Proxy server with name "<proxy server name>" is not running.
> | Cause | A remote administration internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7805 | [SSL]Error while starting proxy server: <proxy server name>.
> | Cause | A remote administration internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7806 | [SSL]Error while stopping proxy server: <proxy server name>.
> | Cause | A remote administration internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7830 | [SSL]Failed to load authentication provider class.
> | Cause | Internal error. A fatal error occurred when loading a specified provider class. Providers must be specified in the com.ddtek.sequelink.slje.properties properties file. At startup, all authentication providers are loaded in the order they are specified. If the provider class is not found, this provider is not installed. When a provider class is found, but an error occurred when loading it, this error message is returned.
> | Action | Check the detailed error message. If necessary, contact DataDirect Technologies technical support.
> 7831 | [SSL]Authentication provider "<provider class name>" has wrong type.
> | Cause | Internal error. A provider specified in the com.ddtek.sequelink.slje.properties properties file is not a sub-class of com.ddtek.sequelink.auth.MGSSProvider.
> | Action | Check the com.ddtek.sequelink.slje.properties properties file. If necessary, contact DataDirect Technologies technical support.
> 7832 | [SSL]No authentication provider specified or found.
> | Cause | No provider specified in the com.ddtek.sequelink.slje.properties properties file can be found.
> | Action | Check the com.ddtek.sequelink.slje.properties properties file. Make sure that the provider classes specified in this properties file are defined in the classpath. If necessary, contact DataDirect Technologies technical support.
> 7833 | [SSL]An unsupported mechanism was requested.
> | Cause | Internal error (standard MGSS error). No installed provider could support the requested authentication mechanism.
> | Action | Check the com.ddtek.sequelink.slje.properties properties file. Make sure that the provider classes specified in this properties file are defined in the classpath. If necessary, contact DataDirect Technologies technical support.
> 7834 | [SSL]An invalid name was supplied.
> | Cause | An internal error (standard MGSS error) occurred. Not used by the standard SequeLink authentication modules.
> | Action | Contact DataDirect Technologies technical support.
> 7835 | [SSL]A supplied name was of an unsupported type.
> | Cause | Internal error (standard MGSS error) occurred. Not used by the standard SequeLink authentication modules.
> | Action | Contact DataDirect Technologies technical support.
> 7836 | [SSL]Incorrect channel bindings were supplied.
> | Cause | An internal error (standard MGSS error) occurred. Not used by the standard SequeLink authentication modules.
> | Action | Contact DataDirect Technologies technical support.
> 7837 | [SSL]An invalid status code was supplied.
> | Cause | An internal error (standard MGSS error) occurred. Not used by the standard SequeLink authentication modules.
> | Action | Contact DataDirect Technologies technical support.
> 7838 | [SSL]A token had an invalid MIC.
> | Cause | An internal error (standard MGSS error) occurred. Not used by the standard SequeLink authentication modules.
> | Action | Contact DataDirect Technologies technical support.
> 7839 | [SSL]No credentials were supplied, or the credentials were unavailable or inaccessible.
> | Cause | Authentication failed because the supplied credentials (for example, user name or password) were incorrect or missing. The required credentials depend on the selected authentication mechanism.
> | Action | Check the supplied authentication information (for example, user name or password). Check which credentials the selected authentication mechanism expects.
> 7840 | [SSL]Invalid context has been supplied.
> | Cause | Internal error (standard MGSS error). This is an internal error or an authentication state error.
> | Action | Contact DataDirect Technologies technical support.
> 7841 | [SSL]A supplied token was invalid.
> | Cause | An internal error (standard MGSS error) occurred. A token used during authentication between client and server was invalid. This is an internal error in the selected authentication mechanism or a mismatch between client and server authentication providers.
> | Action | Check the com.ddtek.sequelink.slje.properties properties file. If necessary, contact DataDirect Technologies technical support.
> 7842 | [SSL]A supplied credential was invalid.
> | Cause | An internal error (standard MGSS error) occurred. Not used by the standard SequeLink authentication modules.
> | Action | Contact DataDirect Technologies technical support.
> 7843 | [SSL]The referenced credentials have expired.
> | Cause | An internal error (standard MGSS error) occurred. Not used by the standard SequeLink authentication modules.
> | Action | Contact DataDirect Technologies technical support.
> 7844 | [SSL]The context has expired.
> | Cause | An internal error (standard MGSS error) occurred. Not used by the standard SequeLink authentication modules.
> | Action | Contact DataDirect Technologies technical support.
> 7845 | [SSL]Miscellaneous failure, unspecified at the MGSS level.
> | Cause | An internal error (standard MGSS error) occurred. Not used by the standard SequeLink authentication modules.
> | Action | Contact DataDirect Technologies technical support.
> 7846 | [SSL]The quality-of-protection requested could not be provided.
> | Cause | An internal error (standard MGSS error) occurred. Not used by the standard SequeLink authentication modules.
> | Action | Contact DataDirect Technologies technical support.
> 7847 | [SSL]The operation is forbidden by local security policy.
> | Cause | An internal error (standard MGSS error) occurred. Not used by the standard SequeLink authentication modules.
> | Action | Contact DataDirect Technologies technical support.
> 7848 | [SSL]The operation or option is unavailable.
> | Cause | An internal error (standard MGSS error) occurred. Not used by the standard SequeLink authentication modules.
> | Action | Contact DataDirect Technologies technical support.
> 7849 | [SSL]The requested credential element already exists.
> | Cause | An internal error (standard MGSS error) occurred. Not used by the standard SequeLink authentication modules.
> | Action | Contact DataDirect Technologies technical support.
> 7850 | [SSL]The provided name was not a mechanism name.
> | Cause | An internal error (standard MGSS error) occurred. Not used by the standard SequeLink authentication modules.
> | Action | Contact DataDirect Technologies technical support.
> 7851 | [SSl]Failed to create authentication provider instance.
> | Cause | A fatal error occurred when loading a specified provider class. Providers must be specified in the com.ddtek.sequelink.slje.properties properties file. At startup, all authentication providers are loaded in the order they are specified. If the provider class is not found, this provider is not installed. When a provider class is found, but an error occurred when instantiating this provider class, this message is returned.
> | Action | Check the detailed error messages and the com.ddtek.sequelink.slje.properties properties file. If necessary, contact DataDirect Technologies technical support.
> 7852 | [SSL]Server-side authentication is not supported by the authentication library.
> | Cause | Internal error. An attempt was made to use the Java authentication library in server mode.
> | Action | Contact DataDirect Technologies technical support.
> 7853 | [SSL]Authentication failed: <reason>.
> | Cause | An attempt to authenticate the client to a server has failed.
> | Action | Check the detailed exceptions.
> 7922 | [SSL]The symbolic host name could not be resolved to an IP address.
> | Cause | The supplied server host name is unknown.
> | Action | Check the server name. Check the detailed error message.
> 7925 | [SSL]Error creating SSL socket.
> | Cause | Internal error while setting up an SSL/TLS socket at the client (or proxy) server.
> | Action | Check the detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7926 | [SSL]Error closing SSL socket.
> | Cause | Internal error while closing up an SSL/TLS socket at the client (or proxy) server.
> | Action | Check the detailed error messages. If necessary, contact DataDirect Technologies technical support.
> 7927 | [SSL]Error receiving accept.
> | Cause | An internal error occurred while closing an SSL/TLS socket at the SequeLink Client (or proxy) server.
> | Action | Check the detailed error messages to troubleshoot the problem. If the error still occurs, contact DataDirect Technologies technical support.
> 7930 | [SSL]The cipher suite "<cipher suite>" is unknown.
> | Cause | The client or the proxy server specified an unknown cipher suite.
> | Action | Check the CipherSuites connection parameter at the client. Check the CipherSuites parameter in the SequeLink Proxy Server configuration file.
> 7931 | [SSL]No cipher suite has been specified.
> | Cause | No cipher suite has been specified by the client or the proxy server.
> | Action | Check the CipherSuites connection parameter. Check the CipherSuites parameter in the SequeLink Proxy Server configuration file.
> 7932 | [SSL]Problem reading files required for certificates.
> | Cause | An error occurred while reading the specified certificate by the SequeLink Proxy Server.
> | Action | Check the detailed error messages. Check the RSACertificate parameter in the SequeLink Proxy Server configuration file. Check the DSSCertificate parameter in the SequeLink Proxy Server configuration file.
> 7934 | [SSL]Certificate Checker class not found.
> | Cause | The user supplied class implementing the Certificate Checker interface was not found in the classpath by the SequeLink Client.
> | Action | Check the CertificateChecker connection parameter. Check if the specified certificate checker is in the client's classpath.
> 7937 | [SSL]Unexpected IOException occurred while reading the pass phrase.
> | Cause | An internal error occurred while reading the pass phrase from the console when starting the SequeLink Proxy Server.
> | Action | Supply the pass phrase using the pass phrase dialog. Contact DataDirect Technologies technical support.
> 7938 | [SSL]Unexpected Exception occurred while decrypting the private key, probable cause: invalid pass phrase.
> | Cause | An error occurred while reading an unencrypted pass phrase. When the pass phrase parameter in the SequeLink Proxy Server configuration file is empty, the private key is interpreted as unencrypted.
> | Action | Check the RSAPrivateKey parameter in the SequeLink Proxy Server configuration file. Check the DSSPrivateKey parameter in the SequeLink Proxy Server configuration file. Check the PassPhrase parameter in the SequeLink Proxy Server configuration file.
> 7939 | [SSL]Unexpected IOException occurred while reading the private key, probable cause: invalid pass phrase.
> | Cause | An error occurred when reading and decrypting the encrypted private key. A possible reason is that the supplied pass phrase with the SequeLink Proxy Server startup is different from the pass phrase used to encrypt the private key.
> | Action | Check the RASPrivateKey parameter in the SequeLink Proxy Server configuration file. Check the DSSPrivateKey parameter in the SequeLink Proxy Server configuration file. Check the PassPhrase parameter in the SequeLink Proxy Server configuration file.
> 7940 | [SSL]A ciphersuite that requires an RSA certificate and a ciphersuite that requires a DSS certificate cannot be supplied at the same time.
> | Cause | An attempt was made to start the SequeLink Proxy Server with a cipher suite list that contains both cipher suites that require an RSA certificate and cipher suites that require a DSS certificate. The two families of cipher suites cannot be mixed.
> | Action | Check the CipherSuites parameter in the SequeLink Proxy Server configuration file.
> 7942 | [SSL]A ciphersuite requires a DSS certificate that was not supplied.
> | Cause | An attempt was made to start the SequeLink Proxy Server with a cipher suite list that contains a cipher suite which requires a DSS certificate, but no such certificate file has been specified.
> | Action | Check the CipherSuites parameter in the SequeLink Proxy Server configuration file. Check the DSSCertificate parameter in the SequeLink Proxy Server configuration file.
> 7943 | [SSL]A ciphersuite requires a DSS privatekey that was not supplied.
> | Cause | An attempt was made to start the SequeLink Proxy Server with a cipher suite list that contains a cipher suite which requires a DSS private key, but no such private key file has been specified.
> | Action | Check the CipherSuites parameter in the SequeLink Proxy Server configuration file. Check the DSSPrivateKey parameter in the SequeLink Proxy Server configuration file.
> 7944 | [SSL]A ciphersuite requires an RSAA certificate that was not supplied.
> | Cause | An attempt was made to start the SequeLink Proxy Server with a cipher suite list that contains a cipher suite which requires an RSA certificate, but no such certificate file has been specified.
> | Action | Check the CipherSuites parameter in the SequeLink Proxy Server configuration file. Check the RSACertificate parameter in the SequeLink Proxy Server configuration file.
> 7945 | [SSL]A ciphersuite requires an RSA privatekey that was not supplied.
> | Cause | An attempt was made to start the SequeLink Proxy Server with a cipher suite list that contains a cipher suite which requires an RSA private key, but no such private key file has been specified.
> | Action | Check the CipherSuites parameter in the SequeLink Proxy Server configuration file. Check the RSAPrivateKey parameter in the SequeLink Proxy Server configuration file.
> 7946 | [SSL]An unnecessary RSA certificate was supplied.
> | Cause | An attempt was made to start the proxy server with an RSA certificate, but SSL is not enabled or no cipher suite from the specified cipher suite list requires an RSA certificate.
> | Action | Check the Network parameter in the SequeLink Proxy Server configuration file. Check the CipherSuites parameter in the SequeLink Proxy Server configuration file. Check the RSACertificate parameter in the SequeLink Proxy Server configuration file.
> 7947 | [SSL]An unnecessary RSA privatekey was supplied.
> | Cause | An attempt was made to start the SequeLink Proxy Server with an RSA private key, but SSL is not enabled or no cipher suite from the specified cipher suite list requires an RSA private key.
> | Action | Check the Network parameter in the SequeLink Proxy Server configuration file. Check the CipherSuites parameter in the SequeLink Proxy Server configuration file. Check the RSAPrivateKey parameter in the SequeLink Proxy Server configuration file.
> 7948 | [SSL]An unnecessary DSS certificate was supplied.
> | Cause | An attempt was made to start the SequeLink Proxy Server with a DSS certificate, but SSL is not enabled or no cipher suite from the specified cipher suite list requires a DSS certificate.
> | Action | Check the Network parameter in the SequeLink Proxy Server configuration file. Check the CipherSuites parameter in the SequeLink Proxy Server configuration file. Check the DSSCertificate parameter in the SequeLink Proxy Server configuration file.
> 7949 | [SSL]An unnecessary DSS privatekey was supplied.
> | Cause | An attempt was made to start the SequeLink Proxy Server with a DSS private key, but SSL is not enabled or no cipher suite from the specified cipher suite list requires a DSS private key.
> | Action | Check the Network parameter in the SequeLink Proxy Server configuration file. Check the CipherSuites parameter in the SequeLink Proxy Server configuration file. Check the DSSPrivateKey parameter in the SequeLink Proxy Server configuration file.
> 7950 | [SSL]An unnecessary value for the UsePassPhraseDialog was supplied.
> | Cause | The SequeLink Proxy Server is started without SSL enabled or only anonymous cipher suites; therefore, a pass phrase does not need to be supplied.
> | Action | Check the UsePassPhraseDialog parameter in the SequeLink Proxy Server configuration file. Check the Network parameter in the SequeLink Proxy Server configuration file. Check the CipherSuites parameter in the SequeLink Proxy Server configuration file.
> 7951 | [SSL]An unnecessary pass phrase was supplied.
> | Cause | The SequeLink Proxy Server is started without SSL enabled or only anonymous cipher suites; therefore, a pass phrase does not need to be supplied.
> | Action | Check the PassPhrase parameter in the SequeLink Proxy Server configuration file. Check the Network parameter in the SequeLink Proxy Server configuration file. Check the CipherSuites parameter in the proxy server configuration file.
> 7952 | [SSL]You cannot use PassPhrase and UsePassPhraseDialog together.
> | Cause | The pass phrase required to decrypt the private key from the proxy server is specified in the SequeLink Proxy Server configuration. It is unnecessary to prompt the user (using a dialog box or the console) for the pass phrase.
> | Action | Check the UsePassPhraseDialog parameter in the SequeLink Proxy Server configuration file. Check the PassPhrase parameter in the SequeLink Proxy Server configuration file.
> 7954 | [SSL]Unexpected InterruptedException occurred while reading the pass phrase.
> | Cause | An internal error occurred when requesting the user for the SequeLink Proxy Server pass phrase using a dialog box.
> | Action | Contact DataDirect Technologies technical support.
> 7955 | [SSL]SSL/TLS handshake failure.
> | Cause | The client attempted to make an SSL connection to the SequeLink Proxy Server, but an error occurred during the initial SSL connection setup.
> | Action | Check the CipherSuites client connection attribute and the corresponding parameter in the SequeLink Proxy Server configuration file. Check the CertificateChecker client connection attribute. Check the SequeLink Proxy Server log file for more detailed error information.
> 7956 | [SSL]Input of pass phrase interrupted by user.
> | Cause | Because the SequeLink Proxy Server is configured to use SSL with cipher suites that require access to the private key, the SequeLink Proxy Server prompts at startup for the pass phrase to use to decrypt the private key. This operation has been cancelled from the dialog by the user.
> | Action | Check the Network parameter in the Proxy Server configuration file. Check the CipherSuites parameter in the Proxy Server configuration file.
> 7981 | Unable to allocate memory.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7982 | SSL/TLS context already used to create connections so no changes to configuration allowed.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7983 | An unknown SSL/TLS version was chosen.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7984 | When supporting multiple SSL/TLS versions, SSL2, SSL3 and TLS1 must be enabled.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7985 | Unknown cipher suite.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7986 | Unsupported cipher suite.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7987 | Error while building list of cipher suites.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7988 | SSL/TLS context not fully initialized.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7989 | SSL/TLS context not fully initialized: specify enabled cipher suites.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7990 | SSL/TLS context not fully initialized: specify enabled SSL/TLS protocol versions.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7991 | Internal error: cipher suite has no certificate type defined.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7992 | You can not mix cipher suites which require RSA and DSA certificates together.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7993 | Cipher suite requires a certificate which isn't supplied.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7994 | Client or server authentication is enabled and no trust manager is specified.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7995 | Client authentication is enabled without server authentication.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7996 | Internal error when setting up SSL/TLS context.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7997 | Unable to access private key.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7998 | Unable to access certificate chain.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 7999 | Public key in certificate doesn't correspond with the provided private key.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8000 | Error while creating SSL/TLS connection.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8001 | Error while accepting SSL/TLS connection.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8002 | Error while connecting via SSL/TLS.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8003 | Error with SSL/TLS handshake: connection is in an unknown or error state.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8004 | Error with SSL/TLS handshake.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8005 | Unable to send: SSL/TLS handshake failure.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8006 | Error while sending via SSL/TLS.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8007 | Unable to receive: SSL/TLS handshake failure.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8008 | Error while receiving via SSL/TLS.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8009 | Unable to initialize SSL/TLS context.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8010 | Error with cipher suites.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8011 | Unknown SSL/TLS context attribute.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8012 | Error while initializing random number generator.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8013 | SSL/TLS connection is closed, operation not supported.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8014 | Unexpected EOF in SSL/TLS protocol.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8015 | TCP/IP error during SSL/TLS protocol.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8016 | Unknown SSL/TLS error.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8017 | Critical section error.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8018 | Error with client SSL/TLS session cache.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8019 | Size of the SSL/TLS session cache must be positive.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8020 | Time out value of a SSL/TLS session must be positive.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8021 | Error while filling in SSL/TLS connection info.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8022 | Error while generating temporary RSA key.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8023 | Certificate library error.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8024 | Key manager error.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8025 | Trust manager error.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8026 | Unknown cipher suite.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8027 | Unknown protocol suite.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8028 | Internal error, stub function called.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8476 | Memory allocation failure.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8477 | Open SSL error.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8478 | No certificates in certificate chain.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 8479 | No top level certificate found in certificate chain.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 9501 | Handshake failure: You are trying to connect to a server that is not a SequeLink Server.
> | Cause | An attempt was made to connect to a server that is not a SequeLink Server.
> | Action | Make sure that the connection information configured at the SequeLink Client is specified correctly to connect to the SequeLink Server.
> 9502 | Handshake failure: A protocol error occurred during the connection setup.
> | Cause | An attempt was detected to connect to a SequeLink Server running an incompatible version of SequeLink.
> | Action | Verify that the versions of your SequeLink Client and SequeLink Server are compatible. Contact DataDirect Technologies technical support, if necessary.
> 9503 | Handshake failure: You are trying to connect to a server running an incompatible version of SequeLink Server.
> | Cause | The SequeLink Client is incompatible with the version of the SequeLink Server to which it tried to connect.
> | Action | Verify that the versions of your SequeLink Client and SequeLink Server are compatible. Contact DataDirect Technologies technical support, if necessary.
> 9509 | Server asked for unknown encryption.
> | Cause | An internal error occurred.
> | Action | Contact DataDirect Technologies technical support.
> 9521 | Unsupported authentication mechanism.
> | Cause | The authentication mechanism specified in the server configuration is not supported by this version of the .NET data provider or no authentication mechanism is specified.
> | Action | Check the "ServiceAuthMethods" service attribute in your SequeLink Server configuration.
> 9522 | Invalid OEM id.
> | Cause | The OEM id specified was not valid.
> | Action | Contact DataDirect Technologies technical support.
> 9523 | Graphic data is not supported by this version of the .NET provider.
> | Cause | This version of the .NET data provider does not support graphic data.
> | Action | Check your .NET application.
> 9532 | Encryption algorithm not supported in this version.
> | Cause | The encryption algorithm specified in the server configuration is not supported by this version of the .NET data provider.
> | Action | Check the "ServiceEncryptionAlgorithm" service attribute in your SequeLink server configuration. Refer to the SequeLink Administrator's Guide for information about service attributes.
> 9535 | Connection timed out.
> | Cause | Establishing a connection to SequeLink server timed out.
> | Action | Specify a larger value for the Connection Timeout option in your connection string.
> 9536 | Command canceled.
> | Cause | The command was successfully canceled by the user.
> | Action | None.