|
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 OpenAccess SDK Server failed.
Action: Free memory resources. If the problem persists, contact Progress DataDirect technical support.
|
|
|
354
|
An invalid argument is passed to an administration function.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
360
|
The requested node cannot be found in the monitor tree.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
361
|
Duplicate object identifier in the monitor tree.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
370
|
The specified entity type does not exist.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
371
|
The specified attribute does not exist.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
372
|
The specified entity instance could not be found.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
373
|
The specified attributes do not match.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
374
|
The specified attribute ID is not valid.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
375
|
The specified entity type is not valid.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
376
|
The specified entity type is read-only.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
377
|
The specified configuration file could not be opened.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
378
|
The syntax of the configuration file is incorrect.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
379
|
An unexpected duplicate entity was detected.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
380
|
The required primary key attributes were not provided.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
381
|
The provided attribute is a primary key attribute.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 OpenAccess SDK Administrators attempt to add the same attribute to the configuration at the same time. Using the OpenAccess SDK Manager, reconnect to the OpenAccess SDK Agent service to refresh the OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
391
|
The semaphore operation could not be completed within the timeout period specified.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect 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 OpenAccess SDK 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 OpenAccess SDK Administrator’s Guide for information about service attributes.
|
|
|
395
|
Request to create an IPC object failed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
397
|
A call to ftok failed. Check if the file xxx exists and is readable.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
398
|
Request to create or attach to shared memory (key=xxxx) failed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
399
|
Request to create a semaphore (key=xxxx) failed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
400
|
Request to create a message queue (key=xxxx) failed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
401
|
Failed to terminate the event queue cache because it is not empty.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
410
|
The specified parameter (xxxx) is invalid.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
412
|
The specified attribute (ID=xxxx) has an incorrect type.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
430
|
Failed to open event trace file because the file version was not recognized.
Cause: The server was stopped unexpectedly without flushing events to the events trace file (for example, the server went down because of a power failure).
Action: Remove or rename the event trace file. The file can be found at the location specified by the ServiceEventTraceLocation service attribute.
|
|
|
431
|
Failed to resize the event trace file.
Cause: An attempt to resize the event trace file failed, probably because OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
433
|
Failed to open the event trace file.
Cause: The event trace file could not be opened during service startup because the OpenAccess SDK service was not stopped properly, for example, because the server machine failed or the OpenAccess SDK 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 OpenAccess SDK services are stopped using the OpenAccess SDK 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 Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
1001
|
No more data available to read.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
1002
|
End of stream was detected on a read.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
1003
|
Error opening/loading com.ddtek.util.transliteration.properties.
Cause: An unexpected error occurred while accessing the transliteration properties file.
Action: Contact Progress DataDirect technical support.
|
|
|
1004
|
Resource com.ddtek.util.transliteration.properties is corrupt.
Cause: An unexpected error occurred while accessing the transliteration properties file.
Action: Contact Progress DataDirect technical support.
|
|
|
1005
|
Transliteration table {0} not found.
Cause: The OpenAccess SDK Server uses a Code page that is currently not supported by the OpenAccess SDK Client.
Action: Contact Progress DataDirect technical support.
|
|
|
1006
|
Transliteration class {0} not found.
Cause: The OpenAccess SDK Server uses a Code page that is currently not supported by the OpenAccess SDK Client.
Action: Contact Progress DataDirect technical support.
|
|
|
1007
|
Unsupported VM encoding {0}.
Cause: The OpenAccess SDK Server uses a Code page that is currently not supported by the OpenAccess SDK Client.
Action: Contact Progress DataDirect technical support.
|
|
|
1008
|
Transliteration table {0} is corrupt.
Cause: An unexpected error occurred while accessing the transliteration table.
Action: Contact Progress DataDirect technical support.
|
|
|
1009
|
Transliteration failed.
Cause: An unexpected error occurred while transliterating the String.
Action: Contact Progress DataDirect technical support.
|
|
|
1010
|
Invalid transliteration class {0}.
Cause: An unexpected error occurred while accessing the transliteration table.
Action: Contact Progress DataDirect technical support.
|
|
|
1011
|
Character set {0} not found in com.ddtek.util.transliteration.properties.
Cause: The OpenAccess SDK Server uses a Code page that is currently not supported by the OpenAccess SDK Client.
Action: Contact Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
1016
|
Error fetching data from temp buffer
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
1017
|
The object is closed
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
1018
|
{0}
Cause: An unexpected error occurred. At runtime, an error message from the JDK is displayed.
Action: Contact Progress DataDirect technical support.
|
|
|
1019
|
Error attempting to backup position in data stream
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
1020
|
Error establishing socket. {0}
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
1021
|
Error establishing socket. Unknown host: {0}
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
2109
|
Unexpected EOF in SSL/TLS protocol during cancel disconnect phase
Cause: The TCP/IP connection closed without closing the SSL/TCP connection first.
Action: No action required. This message occurs when a secure ADO.NET Client cancels a request.
|
|
|
2110
|
Unexpected EOF in SSL/TLS protocol during disconnect phase
Cause: The TCP/IP connection closed without closing the SSL/TCP connection first.
Action: No action required. This message occurs when a secure ADO.NET Client disconnects.
|
|
|
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 an OpenAccess SDK 7.0 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 Progress DataDirect technical support.
|
|
|
2202
|
Network resource problem, session aborted due to local buffer allocation failure, connection closed.
Cause: The OpenAccess SDK Client could not allocate internal buffers to read the reply sent from the OpenAccess SDK Server. The session was aborted and the connection was closed.
Action: Free memory resources. If the problem persists, contact Progress DataDirect technical support.
|
|
|
2203
|
Network resource problem, session aborted due to remote buffer allocation failure, connection closed.
Cause: The OpenAccess SDK Server could not allocate internal buffers to read the request coming from the OpenAccess SDK Client. The session was aborted and the connection was closed.
Action: Free memory resources. If the problem persists, contact Progress DataDirect technical support.
|
|
|
2204
|
Internal network error, session aborted due to local session protocol error, connection closed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
2205
|
Internal network error, session aborted due to remote session protocol error, connection closed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
2206
|
Network problem, cancel not allowed.
Cause: The cancel feature was disabled by the OpenAccess SDK 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 OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
2208
|
Internal network error, session aborted, connection closed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
2209
|
Network problem, no pending request to cancel.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
2211
|
Network problem, cancel not possible because session is killed.
Cause: The cancel operation failed because the session was killed on the OpenAccess SDK Server. The connection was closed.
Action: Contact Progress DataDirect technical support.
|
|
|
2213
|
Internal network error, connection closed because session key not found in remote session list.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 OpenAccess SDK Server.
Action: Contact Progress DataDirect technical support.
|
|
|
2217
|
Network problem, session aborted due to internal error in remote procedure call, connection closed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
2219
|
Network problem, invalid IIOP object key, connection closed.
Cause: The OpenAccess SDK service the OpenAccess SDK Client is connected to did not accept the IIOP object key sent.
Action: Contact Progress DataDirect technical support.
|
|
|
2221
|
Network problem, invalid IIOP operation target, connection closed.
Cause: The OpenAccess SDK service the OpenAccess SDK Client is connected to did not accept the IIOP operation target sent.
Action: Contact Progress DataDirect technical support.
|
|
|
2223
|
Internal network error, session aborted due to remote procedure call failure, connection closed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
2249
|
Internal network error.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
2251
|
Connection closed due to session kill.
Cause: The session was killed on the OpenAccess SDK Server. The connection was closed.
Action: None.
|
|
|
2252
|
Connection closed due to service shutdown.
Cause: The session was killed on the OpenAccess SDK Server because the OpenAccess SDK service was shutting down.
Action: None.
|
|
|
2253
|
Connection closed, non OpenAccess SDK IIOP user exception received.
Cause: An IIOP user exception reply was received from a server that was not an OpenAccess SDK Server. The session was aborted, and the connection was closed.
Action: Contact Progress DataDirect technical support.
|
|
|
2254
|
Connection closed, non OpenAccess SDK IIOP system exception received.
Cause: An IIOP system exception reply was received from a server that was not an OpenAccess SDK Server. The session was aborted, and the connection was closed.
Action: Contact Progress DataDirect technical support.
|
|
|
2255
|
Connection closed, non OpenAccess SDK IIOP message format error received.
Cause: An IIOP message format error was received from a server that was not an OpenAccess SDK Server. The session was aborted, and the connection was closed.
Action: Make sure the client application is connecting to an OpenAccess SDK Server. If the problem persists, contact Progress DataDirect 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 is 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 an OpenAccess SDK Server. If the problem persists, contact Progress DataDirect 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 OpenAccess SDK Server host because no route to the OpenAccess SDK Server was found.
Action: Make sure that:
The network configuration is correct
A network route to the OpenAccess SDK Server is available
The OpenAccess SDK 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 OpenAccess SDK 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 OpenAccess SDK Server is available
The OpenAccess SDK 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 Progress DataDirect 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 OpenAccess SDK Server host at the specified port or the OpenAccess SDK Server was experiencing too many simultaneous connection attempts.
Action: Contact Progress DataDirect 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 OpenAccess SDK 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 Progress DataDirect 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-OpenAccess SDK 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 OpenAccess SDK Server stopping unexpectedly, contact Progress DataDirect technical support.
|
|
|
2311
|
TCP/IP network error, connection closed.
Cause: An unexpected TCP/IP error occurred. The connection was closed.
Action: Contact Progress DataDirect 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 OpenAccess SDK Server, but no data was received by the OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
2314
|
Internal network problem, connection closed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
2315
|
Network problem, unknown session conversation protocol.
Cause: An attempt was made to connect to an OpenAccess SDK Server with an incompatible version of OpenAccess SDK.
Action: Check the version of the OpenAccess SDK Server to make sure it is compatible with the current version of the installed OpenAccess SDK software. If the problem persists, contact Progress DataDirect 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 OpenAccess SDK service was being used by another application.
Action: Stop the application that is using the port or reconfigure the OpenAccess SDK service to use another port.
|
|
|
2321
|
Network problem, listener could not be started because port is already in use.
Cause: The port specified for the OpenAccess SDK service was being used by another application.
Action: Stop the application that is using the port or reconfigure the OpenAccess SDK service to use another port.
|
|
|
2322
|
Network problem, Ssl packet received on non secure server.
Cause: A client connected using SSL, but the server is not enabled for SSL.
Action: Enable encryption on the Client or enable SSL on the Server. For more information, refer to the OpenAccess SDK Administrator’s Guide.
|
|
|
2323
|
No support for the specified address family.
Cause: The operating system does not support IPv6.
Action: Install IPv6 or use an IPv4 address.
|
|
|
2324
|
Protocol not supported.
Cause: The operating system does not support IPv6.
Action: Install IPv6 or use an IPv4 address.
|
|
|
2325
|
Transport layer security end failure
Cause: A problem was encountered while closing the SSL session after the logon packet exchange.
Action: Contact Progress DataDirect technical support.
|
|
|
2326
|
TCP/IP error, connection reset by peer.
Cause: The TCP/IP connection unexpectedly closed, causing the server to rollback any uncommitted transactions. This occurs when an application does not close a Connection object before the application is exited.
Action: Make sure that all Connection objects are closed before an application is exited.
|
|
|
2403
|
Network resource problem, session refused, connection closed.
Cause: The OpenAccess SDK 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 OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
2455
|
Internal network error, missing separator.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
2460
|
Internal network error during parsing host and port.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
2464
|
Internal network error during parsing host and port.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
2465
|
Internal network error during parsing host and port.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
2467
|
Internal network error during parsing host and port.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
2468
|
Internal network error, no host and port specified.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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.
|
|
|
2471
|
Hostname empty or blank.
Cause: An empty hostname or a hostname containing only blanks was received.
Action: Correct the hostname connection parameter.
|
|
|
2472
|
Port empty or blank.
Cause: An empty port or a port containing only blanks was received.
Action: Correct the port connection parameter.
|
|
|
2687
|
Invalid ss_family
Cause: getsockname or getpeername returned an address family that was different from AF_INET or AF_INET6.
Action: Contact Progress DataDirect technical support.
|
|
|
2688
|
No support for the specified address family
Cause: The operating system does not support IPv6.
Action: Install IPv6 or specify an IPv4 hostname or address.
|
|
|
2690
|
Hostname empty or blank.
Cause: An empty hostname or a hostname containing only blanks was received.
Action: Correct the hostname connection parameter.
|
|
|
2691
|
Port empty or blank.
Cause: An empty port or a port containing only blanks was received.
Action: Correct the port connection parameter.
|
|
|
3001
|
Internal error, memory allocation failed.
Cause: Memory allocation error occurred in the server.
Action: Free memory resources. If the problem persists, contact Progress DataDirect technical support.
|
|
|
3002
|
Internal error, corrupt context.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3003
|
Internal error, invalid request received from the client application.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3004
|
Internal error, an unexpected exception was detected.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3005
|
Internal error, a fatal server error was detected.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3006
|
Internal error, a fatal error was detected during event processing.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3007
|
Internal error, an invalid argument was specified.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3008
|
OSLogon authentication mechanism requires root privilege.
Cause: An attempt was made to authenticate a connection to a UNIX OpenAccess SDK Server using the OSLogon mechanism, but the UNIX OpenAccess SDK Server is not running as root.
Action: Make sure that the UNIX OpenAccess SDK 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 OpenAccess SDK 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 only uses the number of threads allowed by the operating system.
Action: Correct the value of the ServiceMaxThreads service attribute. Refer to the OpenAccess SDK Administrator’s Guide for information about service attributes.
|
|
|
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 uses 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 OpenAccess SDK 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 does not start.
Action: Make sure that the value of the ServiceMinThreads service attribute is at least 6. Refer to the OpenAccess SDK 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 Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect 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 OpenAccess SDK Server was unable to accept a new connection request because of insufficient network resources. The OpenAccess SDK Server waits 1 second before accepting new OpenAccess SDK Client connections.
Action: Re-attempt the connection.
|
|
|
3046
|
Internal error, unable to access the monitor tree.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 OpenAccess SDK service attributes, refer to the OpenAccess SDK 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 Progress DataDirect 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 Progress DataDirect 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 OpenAccess SDK service attributes, refer to the OpenAccess SDK Administrator’s Guide.
|
|
|
3054
|
Found syntax error(s) within the DataSourceSessionToken attribute.
Cause: Syntax error in DataSourceSessionToken service attribute.
Action: Verify that the DataSourceSessionToken service 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 service 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 Progress DataDirect technical support.
|
|
|
3058
|
Internal error, error detected in the event processor.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 OpenAccess SDK service.
Action: Specify a valid server data source for the OpenAccess SDK service.
|
|
|
3060
|
Internal error, the specified authentication mechanism is not accepted.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 OpenAccess SDK administrator for details.
|
|
|
3062
|
Internal error, unknown provide ID.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3063
|
Maximum number of shared counter instances reached.
Cause: OpenAccess SDK 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 OpenAccess SDK service attributes, refer to the OpenAccess SDK Administrator’s Guide.
|
|
|
3064
|
Internal error, an invalid monitor object was specified while processing an event.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3066
|
Configuration file is in use by another connection, please retry.
Cause: An attempt to update the OpenAccess SDK configuration file was refused because another OpenAccess SDK Manager application has locked the OpenAccess SDK configuration file.
Action: Wait for the other OpenAccess SDK Manager application to release the lock on the OpenAccess SDK configuration file. Then, re-attempt the OpenAccess SDK 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 OpenAccess SDK service.
Action: Make sure that the application is specifying the correct application ID, or change the DataSourceAutoApplId service attribute of the OpenAccess SDK service to accept the application ID. For information about application IDs or changing OpenAccess SDK service attributes, refer to the OpenAccess SDK 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 are refused.
Action: Make sure that the application is specifying the correct application ID, or change the DataSourceApplID service attribute of the OpenAccess SDK service to accept the application ID. For information about application IDs or changing OpenAccess SDK service attributes, refer to the OpenAccess SDK Administrator’s Guide.
|
|
|
3070
|
License verification failed.
Cause: The OpenAccess SDK Server could not locate the required license to execute the client request. The request is refused.
Action: Make sure a valid OpenAccess SDK license is registered. If the problem persists, contact Progress DataDirect 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.
|
|
|
3075
|
No valid cipher suites specified...
Cause: A valid cipher suite was not specified.
Action: Check the service debug log file for the reason why the cipher suite was rejected. Make sure that a valid cipher suite is specified.
|
|
|
3076
|
Unknown cipher suite: <cipher_suite>
Cause: A specified cipher suite was not recognized by SSL.
Action: Remove the cipher suite from the ServicesSSLCipherSuites list.
|
|
|
3077
|
Unknown SSL/TLS version: <version>
Cause: A specified SSL/TLS version was not recognized by SSL.
Action: Verify the SSL/TLS version specified in ServiceSSLVersions. Only TLS 1.0 is supported.
|
|
|
3078
|
Internal error, invalid search argument type specified.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
3082
|
Access to data source is disabled.
Cause: Access to the data source is rejected as specified in the DataSourceEnableAccess service attribute. Refer to the OpenAccess SDK Administrator’s Guide for more information on the DataSourceEnableAccess service attribute.
Action: If access is needed, contact your OpenAccess SDK administrator to change the DataSourceEnableAccess setting.
|
|
|
3084
|
This system includes a licensed version of DataDirect OpenAccess SDK 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 Progress DataDirect within the next 15 days to upgrade the license.
|
|
|
3085
|
The OpenAccess SDK features that you have licensed are running in evaluation mode and will expire.
Cause: Some client components are running in evaluation mode and will expire.
Action: Contact Progress DataDirect to obtain a permanent license.
|
|
|
3086
|
OEM verification failed.
Cause: The OEM signature cannot be verified. The OEM verification looks for a prefix.SHA file in the installdir\ipe. The prefix.SHA file is used to ensure that a branded driver can communicate only with a server from the same OEM.
Action: Brand your ODBC or JDBC driver and place the generated xxOA.SHA file in the installdir\ipe folder of the Server or the Local Client for ODBC.
|
|
|
3087
|
SSL is enabled and active, but not licensed for security. Client license verification will fail.
Cause: You configured SSL in your service configuration, but the license key does not support SSL. A connection from the OpenAccess SDK Client will fail.
Action: Upgrade your license to support SSL.
|
|
|
3088
|
Not licensed to use the Kerberos ServiceAuthMethod.
Cause: You configured Kerberos in your service configuration, but the license key does not support Kerberos. A connection from the OpenAccess SDK Client using Kerberos will fail.
Action: Upgrade your license to support Kerberos.
|
|
|
3089
|
Invalid cipher suites
Cause: One or more invalid cipher suites was specified in the ServiceSSLCipherSuites list, but valid cipher suites specified in the list were sufficient for the server to start.
Action: Check the Service debug log file for the reason why one or more cipher suites was rejected. Correct the cipher suites specified in the ServiceSSLCipherSuites list.
|
|
|
3101
|
Error detected while processing an administration request.
Cause: The administration request could not be processed by the OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
3103
|
Unexpected error detected while processing an administration request.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3104
|
The requested administration function is not implemented on this platform.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3105
|
Memory allocation failed while processing an administration request.
Cause: A request to the operating system to allocate memory for the OpenAccess SDK Server failed.
Action: Free memory resources. If the problem persists, contact Progress DataDirect technical support.
|
|
|
3106
|
A collection library function failed while processing an administration request.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3107
|
An operation on the server configuration file failed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3108
|
An operation on the NT registry failed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3110
|
Failed to open the server configuration file for reading.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3111
|
Failed to open the server configuration file for writing.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3112
|
Failed to open the server configuration file because its syntax is incorrect.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3113
|
Failed to open the server configuration file because the file does not exist.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3114
|
Failed to save the server configuration file.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3115
|
Failed to save the server configuration file because the file backup failed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3116
|
Failed to attach to the event queue.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3117
|
Failed to send event to event queue.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3118
|
Failed to access the event queue.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3119
|
Failed to send an event because a wait operation timed out.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3120
|
Failed to process the administration request because the specified handle has not been opened.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3122
|
Failed to process the administration request because the version of the configuration file is not supported by this version of OpenAccess SDK.
Cause: An attempt was detected to open an OpenAccess SDK configuration file with an OpenAccess SDK version that is incompatible with the current version of the installed OpenAccess SDK software.
Action: Use a compatible version of the installed OpenAccess SDK software to open the OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
3132
|
The requested attribute was not found in the server configuration file.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3133
|
The specified attribute ID is not valid.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3134
|
An unexpected duplicate entity was detected.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3137
|
Failed to open the Service Control Manager.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3138
|
Failed to open the specified OS service.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3139
|
Failed to create the specified OS service.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3140
|
Failed to delete the specified OS service.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 OpenAccess SDK Manager lists the OpenAccess SDK service as inactive, the OpenAccess SDK service may be in the process of stopping. Wait for the OpenAccess SDK 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 an OpenAccess SDK service with a name that was already used by another operating system service.
Action: Make sure the name you choose for your OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
3144
|
Requested operation on the specified OS service failed because a wait operation timed out.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3145
|
The TCP port for the service could not be registered because it is registered for another network service.
Cause: The OpenAccess SDK 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 is not possible to start the OpenAccess SDK 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 OpenAccess SDK service you created, you can continue. If unsure, change the TCP/IP port for the OpenAccess SDK 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 Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
3148
|
Failed to unregister the OS service because it is not an OpenAccess SDK Service.
Cause: An attempt to unregister an OpenAccess SDK service failed because the OpenAccess SDK service name was being used by another operating system service.
Action: Make sure that the name you choose for your OpenAccess SDK 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 OpenAccess SDK service.
Cause: The OpenAccess SDK 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 OpenAccess SDK service.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3153
|
Failed to obtain the status of the specified OS Service.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3154
|
Failed to start the specified service because it is already running.
Cause: An attempt to start an OpenAccess SDK service that is already running was detected.
Action: If the OpenAccess SDK Manager lists the OpenAccess SDK service as inactive, the OpenAccess SDK service may be in the process of stopping. Wait for the OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
3156
|
Failed to open the Service. The OpenAccess 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 Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
3172
|
Failed to open the event trace.
Cause: The OpenAccess SDK 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 Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
3186
|
Failed to open the Service Control Manager. The OpenAccess 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 OpenAccess SDK layer.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3202
|
Unable to retrieve warning message from backend OpenAccess SDK layer.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
3203
|
Required user name is missing.
Cause: The OpenAccess SDK service has been configured to require a database user name, but the OpenAccess SDK 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.
|
|
|
3220
|
Username is too long, maximum 512 characters are allowed.
Cause: OpenAccess user names are limited to a maximum of 512 characters.
Action: Verify the user name specified in the LoginID connection attribute.
|
|
|
3221
|
Password is too long, maximum 512 characters are allowed.
Cause: OpenAccess passwords are limited to a maximum of 512 characters.
Action: Verify the password specified in the Password connection attribute.
|
|
|
3222
|
Database name is too long, maximum 64 characters are allowed.
Cause: OpenAccess database names are limited to a maximum of 64 characters.
Action: Verify the database name specified in the Database connection attribute.
|
|
|
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. This error occurs only in releases prior to OpenAccess SDK version 8.1.
Action: Verify that the oajc.jar file is on the class path.
|
|
|
4303
|
JDBC DataSource not defined.
Cause: The OpenAccess SDK Client for JDBC DataSource object used by the resource adapter was not initialized correctly.
Action: Contact Progress DataDirect technical support. The subclasses of JCAManagedConnectionFactory should ensure that an OpenAccess SKD 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 metadata 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 indicates 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 Progress DataDirect 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 Progress DataDirect 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 does 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 Progress DataDirect technical support.
|
|
|
5002
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5003
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5004
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5011
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5012
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5013
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5014
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5015
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5021
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5022
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5023
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5024
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5031
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5033
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5034
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5043
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5044
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5045
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5046
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5047
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5052
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5058
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5059
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5060
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5061
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5065
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5067
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5069
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5070
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5071
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5101
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5102
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5103
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5104
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5105
|
A memory allocation error occurred.
Cause: OpenAccess SDK was unable to allocate the necessary amount of memory.
Action: Increase the available memory for your application.
|
|
|
5106
|
A memory allocation error occurred.
Cause: OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
5108
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5109
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5110
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5111
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5112
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5113
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5150
|
You cannot connect to a server that is not an OpenAccess SDK Server.
Cause: An attempt was detected to connect to a server that is not an OpenAccess SDK Server.
Action: Make sure that the connection information configured at the OpenAccess SDK Client is specified correctly to connect to the OpenAccess SDK Server.
|
|
|
5151
|
A protocol error occurred during the connection setup.
Cause: The OpenAccess SDK Client is not compatible with the version of the OpenAccess SDK Server to which it is connecting.
Action: Verify that the versions of your OpenAccess SDK Client and OpenAccess SDK Server are compatible. Contact Progress DataDirect technical support, if necessary
|
|
|
5152
|
You are trying to connect to a server that is not running the correct version of OpenAccess SDK Server.
Cause: An attempt was detected to connect to an OpenAccess SDK Server running an incompatible version of OpenAccess SDK.
Action: Verify that the versions of your OpenAccess SDK Client and OpenAccess SDK Server are compatible. Contact Progress DataDirect technical support, if necessary.
|
|
|
5153
|
The OpenAccess Client failed to retrieve the connection parameters from the LDAP server.
Cause: The OpenAccess SDK 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 OpenAccess SDK Server was not specified in the connection information.
Action: Make sure that the connection information configured at the OpenAccess SDK Client specifies the TCP/IP host of the OpenAccess SDK Server.
|
|
|
5155
|
The TCP/IP port was not specified.
Cause: The TCP/IP port of the OpenAccess SDK Server was not specified in the connection information.
Action: Make sure that the connection information configured at the OpenAccess SDK Client specifies the TCP/IP port of the OpenAccess SDK 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 OpenAccess SDK Client specifies the Distinguished Name of the LDAP entry.
|
|
|
5157
|
The specified LDAP entry didn’t specify all required attributes to connect to the OpenAccess SDK Server.
Cause: The specified LDAP entry, identified by the Distinguished Name, did not specify all the required attributes to connect to the OpenAccess SDK Server.
Action: Check the LDAP entry in the LDAP directory to make sure that the LDAP entry specifies the complete connection information for OpenAccess SDK connections. For information about configuring LDAP for OpenAccess SDK, refer to the OpenAccess SDK 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: OpenAccess SDK Client could not load the specified LDAP shared library.
Action: Check your OpenAccess SDK Client installation.
|
|
|
5162
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect 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 an OpenAccess SDK Client running on a platform that supports LDAP.
|
|
|
5164
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5169
|
The data access features that you've licensed are running in evaluation mode and will expire.
Cause: The data access features that you have licensed are running in evaluation mode and will expire.
Action: Upgrade your evaluation license to a permanent license.
|
|
|
5200
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5201
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5202
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5203
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5204
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5205
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5206
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5223
|
An internal error occurred (SSP_ERR_PROV_INVALIDDIRECTION).
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5241
|
An internal error occurred (SSP_ERR_NIMM_INVALIDNUMOFSTMTS).
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5270
|
An internal error occurred (SSP_ERR_EXTDEF_INVALIDNUMOFVARS).
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5290
|
An internal error occurred (SSP_ERR_FETCH_INVALIDROWCOUNT).
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5300
|
Failed to load the transliteration file ‘xxxx’.
Cause: The transliteration file ‘xxxx’ failed to load.
Action: Check your OpenAccess SDK Client installation.
|
|
|
5301
|
The transliteration file ‘xxxx’ is corrupt.
Cause: The transliteration file ‘xxxx’ is damaged.
Action: Check your OpenAccess SDK Client installation.
|
|
|
5302
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5303
|
Failed to load the transliteration file ‘xxxx’.
Cause: The transliteration file ‘xxxx’ failed to load.
Action: Check your OpenAccess SDK Client installation.
|
|
|
5304
|
The transliteration file ‘xxxx’ is corrupt.
Cause: The transliteration file ‘xxxx’ is corrupt.
Action: Check your OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
5321
|
An internal error occurred (SSP_ERR_DEFDESC_MULTIPLE).
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5330
|
An internal error occurred (SSP_ERR_GETDESC_INVALIDIDX).
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5331
|
An internal error occurred (SSP_ERR_GETDESC_NODEFDESC).
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5340
|
An internal error occurred (SSP_ERR_DOCONNECT_ACTIVE).
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
5350
|
An authentication mechanism could not be successfully negotiated.
Cause: The OpenAccess SDK Server did not specify an authentication mechanism supported by the OpenAccess SDK Client. The OpenAccess SDK Server is configured for Kerberos/Integrated_nt but is not licensed for security.
Action: Make sure that the OpenAccess SDK Server specifies an authentication mechanism supported by the OpenAccess SDK Client. Refer to the OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
5502
|
Failed to initialize Command Line Administrator.
Cause: The OpenAccess SDK Manager could not be initialized.
Action: Contact Progress DataDirect technical support.
|
|
|
5503
|
Internal Command Line Administrator error detected (I=xxxxd).
Cause: An internal error occurred in the OpenAccess SDK Manager.
Action: Contact Progress DataDirect technical support.
|
|
|
5504
|
Unknown command <name> entered.
Cause: An incorrect OpenAccess SDK Manager command was entered.
Action: Check the OpenAccess SDK Manager command help to verify the command.
|
|
|
5505
|
Specified argument not valid for the given command.
Cause: An incorrect parameter for an OpenAccess SDK Manager command was entered.
Action: Check the OpenAccess SDK 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 an OpenAccess SDK Manager command was too long.
Action: Check the OpenAccess SDK Manager command help to verify the command parameter.
|
|
|
5508
|
Required parameter <name> for command not specified.
Cause: A required parameter for the OpenAccess SDK Manager command was not specified.
Action: Check the OpenAccess SDK Manager command help to verify the required parameters for the command.
|
|
|
5509
|
Command not available for current configuration.
Cause: The OpenAccess SDK Manager command entered is not supported for the current configuration.
Action: Check the OpenAccess SDK Manager command help to verify the command.
|
|
|
5510
|
Failed to display help item.
Cause: OpenAccess SDK Manager help could not be displayed for the specified command. This is an internal error.
Action: Contact Progress DataDirect technical support.
|
|
|
5511
|
No configuration opened.
Cause: An OpenAccess SDK Manager command was entered that required an open configuration.
Action: Check the OpenAccess SDK Manager command help to verify the command.
|
|
|
5513
|
Numeric value for parameter required.
Cause: A parameter for the specified OpenAccess SDK Manager command required a numeric value.
Action: Check the OpenAccess SDK Manager command help to verify the parameters for the command.
|
|
|
5514
|
An invalid service template ID was specified.
Cause: An invalid OpenAccess SDK service template ID was specified.
Action: Make sure that you specify the correct OpenAccess SDK service template ID. For more information about template IDs, refer to the OpenAccess SDK Administrator’s Guide.
|
|
|
5515
|
Invalid option <name>.
Cause: An invalid option for the specified OpenAccess SDK Manager command was supplied.
Action: Check the OpenAccess SDK Manager command help to verify the specified command.
|
|
|
5516
|
Invalid value for option <name>.
Cause: An invalid value for the specified OpenAccess SDK Manager command option was supplied.
Action: Check the OpenAccess SDK Manager command help to verify the command.
|
|
|
5517
|
Help topic not found.
Cause: The topic specified with the OpenAccess SDK 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 an OpenAccess SDK Manager command that was entered was invalid.
Action: Check the OpenAccess SDK Manager command help to verify log level names.
|
|
|
5520
|
Invalid log value <name>.
Cause: The value specified with the log level name in an OpenAccess SDK Manager command that was entered was invalid.
Action: Check the OpenAccess SDK Manager command help to verify log level values.
|
|
|
5522
|
Invalid numeric value <value>.
Cause: A value was specified in an OpenAccess SDK Manager command that could not be converted to a numeric value.
Action: Specify a valid numeric value for the OpenAccess SDK Manager command.
|
|
|
5523
|
AutoSave option is already activated.
Cause: The OpenAccess SDK 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 the 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.
Stop your OpenAccess SDK services.
Add the following lines to your swcla.ini file:
[CLA Settings]
MoreExePath=/usr/bin/more
Restart your OpenAccess SDK services.
|
|
|
5527
|
When handling commands interactively, 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 an OpenAccess SDK Manager command was specified.
Action: Check the OpenAccess SDK 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 an OpenAccess SDK Manager command was supplied.
Action: Check the OpenAccess SDK Manager command help to verify profile levels and their names or IDs.
|
|
|
5531
|
Too many parameters specified.
Cause: Too many arguments were provided with an OpenAccess SDK Manager command.
Action: Make sure that the OpenAccess SDK 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 an OpenAccess SDK 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 not an array attribute.
Cause: An index was provided in an OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
6001
|
{0}
Cause: Generic error occurred. At runtime, an error message from the JDK is 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 Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
6017
|
Unexpected internal error.
Cause: An unexpected internal error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect 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 OpenAccess SDK 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 OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
6033
|
Unable to determine the type of the specified object.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6036
|
Syntax error at token {0}, line {1} offset {2}.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6037
|
Unexpected end of escape.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
6044
|
The evaluation period for this driver has expired. Contact Progress DataDirect SupportLink to purchase a valid license.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect 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 OpenAccess SDK Client 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 OpenAccess SDK Client 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 OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
6052
|
There was an error(s) in processing the batch command. Use getNextException() for details.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6053
|
Statements that produce result sets are not allowed in batch commands.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
6063
|
Error closing Blob or Clob object.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
6502
|
A required output parameter could not be written.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6503
|
A parameter was malformed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6504
|
An unsupported mechanism was requested.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6505
|
An invalid name was supplied.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6506
|
A supplied name was of an unsupported type.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6507
|
Incorrect channel bindings were supplied.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6508
|
An invalid status code was supplied.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6509
|
A token had an invalid signature.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
6512
|
A token was invalid.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6513
|
A credential was invalid.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
6516
|
A generic error occurred. Minor MGGS state is xxxx.
Cause: An error occurred during authentication processing.
Action: Reference the following messages for the specific action to perform.
|
|
|
|
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.
|
|
|
|
Attribute not supported on this platform.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
|
Get/set attribute failed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
|
Problems with user context.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
No data to enumerate.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6516 (cont.)
|
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.
|
|
|
|
User account expired.
Cause: The user account has been expired.
Action: Contact your security administrator.
|
|
|
|
User not found.
Cause: Invalid user information was supplied.
Action: Make sure that the logon information provided by your client application is correct.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
Process must have SE_TCB_NAME privilege.
Cause: The OpenAccess SDK 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.
|
|
|
|
Buffer supplied not large enough.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
|
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.
|
|
|
|
Internal error occurred.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
|
netapi32.dll not found, or module not supported.
Cause: The required module was not found.
Action: Contact Progress DataDirect technical support.
|
|
|
|
User account revoked.
Cause: The user is not allowed to access the system.
Action: Contact your security administrator.
|
|
|
|
Authorization call failure.
Cause: An authorization call failed with an unexpected error code.
Action: Contact Progress DataDirect technical support.
|
|
|
|
Pluggable Authentication Module failure.
Cause: A Pluggable Authentication Module (PAM) error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6516 (cont.)
|
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 OpenAccess SDK Administrator’s Guide for information about the ServiceKerberosPrincipalName service attribute.
|
|
|
|
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 Progress DataDirect technical support.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
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 Progress DataDirect technical support.
|
|
|
6517
|
The quality-of-protection requested could not be provided.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6518
|
The operation is forbidden by local security policy.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6519
|
The operation or option is unavailable.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6520
|
The requested credential element already exists.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6521
|
The provided name was not a mechanism name.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6522
|
Failed to load MGSS mechanism.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6523
|
Memory allocation failed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6524
|
Context call failed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
6527
|
MGSS module returned an unknown major status code.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
6851
|
Memory allocation failure.
Cause: The requested amount of memory could not be allocated.
Action: Free memory resources. If the problem persists, contact Progress DataDirect technical support.
|
|
|
6852
|
Internal Administration, Monitoring and Management API error detected (I=<number>).
Cause: An internal error occurred in the OpenAccess SDK Manager.
Action: Contact Progress DataDirect technical support.
|
|
|
6853
|
Failed to access configuration at <string>.
Cause: OpenAccess SDK failed to open the OpenAccess SDK configuration file because an invalid connection string to an OpenAccess SDK Agent was specified or an invalid path to an OpenAccess SDK configuration file was specified.
Action: Re-attempt to open the OpenAccess SDK 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 an OpenAccess SDK Agent or from an OpenAccess SDK configuration file.
Action: Contact Progress DataDirect 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 OpenAccess SDK service attributes, refer to the OpenAccess SDK 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 OpenAccess SDK service attributes, refer to the OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
6864
|
Unable to determine local host name.
Cause: OpenAccess SDK was unable to determine the name of the local host.
Action: Contact Progress DataDirect technical support.
|
|
|
6865
|
Invalid service name <service name>.
Cause: An invalid OpenAccess SDK service name was specified.
Action: Specify a valid OpenAccess SDK service name. Remember that service names are case sensitive.
|
|
|
6866
|
Invalid service template ID.
Cause: An invalid OpenAccess SDK service template ID was specified.
Action: Specify a valid OpenAccess SDK service template ID. For more information about template IDs, refer to the OpenAccess SDK Administrator’s Guide.
|
|
|
6867
|
Only one agent service may be created.
Cause: An attempt was made to create a duplicate OpenAccess SDK Agent service.
Action: None.
|
|
|
6868
|
Service <service name> is still active.
Cause: An attempt was made to delete an OpenAccess SDK service that was still running.
Action: Stop the OpenAccess SDK service before you delete it.
|
|
|
6869
|
Failed to check if service <service name> is still active.
Cause: OpenAccess SDK could not check if the OpenAccess SDK service was active. The OpenAccess SDK service may have been experiencing heavy traffic or may have been in an incorrect state.
Action: Re-check the status of the OpenAccess SDK service. If the problem persists, contact Progress DataDirect technical support.
|
|
|
6870
|
Attribute <ID or name> is not valid <object> attribute.
Cause: The specified attribute is not valid for the OpenAccess SDK service or server data source.
Action: Specify a valid attribute for the OpenAccess SDK service or server data source. For more information about specifying OpenAccess SDK service attributes, refer to the OpenAccess SDK 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 OpenAccess SDK 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 OpenAccess SDK 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 OpenAccess SDK service or server data source.
Action: Check your OpenAccess SDK service or server data source configuration to verify that the specified attribute exists in the configuration. For more information about specifying OpenAccess SDK service attributes, refer to the OpenAccess SDK 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 OpenAccess SDK service or server data source.
Action: Check your OpenAccess SDK service or server data source configuration to verify that the specified attribute exists in the configuration. For more information about specifying OpenAccess SDK service attributes, refer to the OpenAccess SDK 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 OpenAccess SDK service.
Action: Enable a monitoring profile for the service, and make sure that the service is active. For more information about enabling profiles for an OpenAccess SDK service, refer to the OpenAccess SDK 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 OpenAccess SDK Administrator’s Guide.
|
|
|
6879
|
Cannot create a data source for an agent service.
Cause: Server data sources cannot be created for OpenAccess SDK Agent services.
Action: Make sure that you are trying to create a server data source for an OpenAccess SDK data access service.
|
|
|
6880
|
Only one <object> may exist.
Cause: Only one instance of the object may exist.
Action: Contact Progress DataDirect technical support.
|
|
|
6881
|
Invalid <object>.
Cause: An invalid OpenAccess SDK service name or server data source name was specified.
Action: Specify a correct OpenAccess SDK service name or server data source name.
|
|
|
6882
|
No <object> exists.
Cause: No instance of the object exists.
Action: Contact Progress DataDirect technical support.
|
|
|
6883
|
<object> already exists.
Cause: The OpenAccess SDK service name or the server data source name already exists.
Action: Contact Progress DataDirect technical support.
|
|
|
6884
|
<object> still used by service <service name>.
Cause: The object is still used by the specified OpenAccess SDK service.
Action: Contact Progress DataDirect technical support.
|
|
|
6885
|
Cannot delete required attribute <ID or name>.
Cause: The attribute cannot be deleted because it is required.
Action: Contact Progress DataDirect technical support.
|
|
|
6886
|
Unable to determine event trace location for service <service name>.
Cause: An event trace file for the OpenAccess SDK service could not be located. Either OpenAccess SDK service information could not be retrieved or the ServiceEventTraceLocation service attribute could not be found in the service information.
Action: Make sure that the OpenAccess SDK service is active. If it is, check the ServiceEventTraceLocation service attribute to make sure that it is specified correctly. For more information about specifying OpenAccess SDK service attributes, refer to the OpenAccess SDK 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 OpenAccess SDK service.
Action: Enable an event tracing profile for the OpenAccess SDK service, and make sure that the OpenAccess SDK service is running. For more information about enabling profiles for an OpenAccess SDK service, refer to the OpenAccess SDK 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 OpenAccess SDK 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: An OpenAccess SDK Manager request was made that required a connection to an OpenAccess SDK Agent or an OpenAccess SDK configuration file.
Action: Connect to an OpenAccess SDK Agent or open an OpenAccess SDK configuration file before making OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
6896
|
Invalid attribute name <name>.
Cause: An invalid attribute name was specified.
Action: Specify a valid attribute. For more information about specifying OpenAccess SDK service attributes, refer to the OpenAccess SDK Administrator’s Guide.
|
|
|
6897
|
No agent service found in <file name>.
Cause: An OpenAccess SDK Agent service was not defined in the specified OpenAccess SDK configuration file.
Action: Create an OpenAccess SDK Agent service. For information about creating OpenAccess SDK services, refer to the OpenAccess SDK Administrator’s Guide.
|
|
|
6898
|
Unable to locate local OpenAccess Server configuration file.
Cause: A local OpenAccess SDK configuration file could not be located.
Action: Make sure that you have specified the local configuration file correctly. The [SWANDM] section of the oacla.ini file must contain the location of the local OpenAccess Server configuration file.
|
|
|
6899
|
Administration, Monitoring and Management library has not been initialized.
Cause: A call to the OpenAccess SDK Manager library was made before calling SLMAM_Init.
Action: Contact Progress DataDirect technical support.
|
|
|
6900
|
Service <service name> already exists.
Cause: An OpenAccess SDK service with the same service name already exists.
Action: Specify a unique service name for the OpenAccess SDK 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 OpenAccess SDK service.
|
|
|
6902
|
Service <service name> is already started.
Cause: An attempt was made to start an OpenAccess SDK service that was already started.
Action: None.
|
|
|
6903
|
Service <service name> is not active.
Cause: The specified OpenAccess SDK service is not active.
Action: None.
|
|
|
6904
|
No monitor profile available for service <service name>.
Cause: The specified OpenAccess SDK service does not have monitoring enabled.
Action: Enable a monitoring profile for the OpenAccess SDK service. For more information about enabling monitoring profiles, refer to the OpenAccess SDK Administrator’s Guide.
|
|
|
6905
|
A monitor profile already exists for service <service name>.
Cause: The specified OpenAccess SDK service already has monitoring enabled.
Action: None.
|
|
|
6906
|
No event log profile available for service <service name>.
Cause: The specified OpenAccess SDK service does not have event tracing enabled.
Action: Enable an event tracing profile for the OpenAccess SDK service. For more information about enabling profiles for OpenAccess SDK services, refer to the OpenAccess SDK 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 OpenAccess SDK 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 OpenAccess SDK service could not be found.
Action: Contact Progress DataDirect technical support.
|
|
|
6913
|
Session monitoring has not been enabled for service <service name>.
Cause: The monitoring profile enabled for the specified OpenAccess SDK service does not provide session or statement counters.
Action: Enable a monitoring profile for the OpenAccess SDK service that uses session or statement counters. For more information about enabling profiles for OpenAccess SDK services, refer to the OpenAccess SDK Administrator’s Guide.
|
|
|
6914
|
Failed to start service <service name>.
Cause: The specified OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
7362
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7363
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7364
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7365
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7366
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7367
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7368
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7369
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7370
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect 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 OpenAccess SDK 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 OpenAccess SDK Administrator’s Guide.
|
|
|
7398
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
7410
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7411
|
An internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect 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 an OpenAccess Server.
Cause: An attempt was made to connect to a server that is not an OpenAccess SDK Server.
Action: Make sure that the connection information configured at the OpenAccess SDK Client is specified correctly to connect to the OpenAccess SDK Server.
|
|
|
7428
|
Handshake failure: You are trying to connect to a server that is not an OpenAccess Server.
Cause: The OpenAccess SDK Client is incompatible with the version of the OpenAccess SDK Server to which it tried to connect.
Action: Verify that the versions of your OpenAccess SDK Client and OpenAccess SDK Server are compatible. Contact Progress DataDirect technical support, if necessary.
|
|
|
7429
|
Handshake failure: A protocol error occurred during the connection setup.
Cause: An attempt was detected to connect to an OpenAccess SDK Server running an incompatible version of OpenAccess SDK.
Action: Verify that the versions of your OpenAccess SDK Client and OpenAccess SDK Server are compatible. Contact Progress DataDirect 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 Progress DataDirect 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 OpenAccess SDK Server did not specify an authentication mechanism supported by the OpenAccess SDK Client.
Action: Make sure that the OpenAccess SDK Server specifies an authentication mechanism supported by the OpenAccess SDK Client. Refer to the OpenAccess SDK 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 Progress DataDirect technical support.
|
|
|
7436
|
Error occurred while processing transliteration table: {0}.
Cause: An error occurred while processing a transliteration table.
Action: Contact Progress DataDirect technical support.
|
|
|
7437
|
Transliteration table corrupt: {0}.
Cause: A transliteration table was corrupted.
Action: Contact Progress DataDirect 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 Progress DataDirect 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 Progress DataDirect technical support.
|
|
|
7445
|
Internal error occurred.
Cause: An unexpected error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7446
|
Error occurred while processing transliteration table: {0}.
Cause: An error occurred while processing a transliteration table.
Action: Contact Progress DataDirect technical support.
|
|
|
7447
|
An unsupported transliteration type has been specified: {0}.
Cause: An unsupported transliteration type has been specified.
Action: Contact Progress DataDirect technical support.
|
|
|
7448
|
You are attempting to use this Progress DataDirect software from an application that is not licensed to use it.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7449
|
Server asked for unknown encryption.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7450
|
No initialization vector was sent when one was expected.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7451
|
Initialization vector has wrong size ({0} bytes). Expected {1} bytes.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7452
|
Error occurred during transliteration.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 OpenAccess SDK Client 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 OpenAccess SDK Client 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.
|
|
|
7830
|
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.OpenAccess SDK.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 Progress DataDirect technical support.
|
|
|
7831
|
Authentication provider "<provider class name>" has wrong type.
Cause: Internal error. A provider specified in the com.ddtek.OpenAccess SDK.slje.properties properties file is not a sub-class of com.ddtek.OpenAccess SDK.auth.MGSSProvider.
Action: Check the com.ddtek.OpenAccess SDK.slje.properties properties file. If necessary, contact Progress DataDirect technical support.
|
|
|
7832
|
No authentication provider specified or found.
Cause: No provider specified in the com.ddtek.OpenAccess SDK.slje.properties properties file can be found.
Action: Check the com.ddtek.OpenAccess SDK.slje.properties properties file. Make sure that the provider classes specified in this properties file are defined in the classpath. If necessary, contact Progress DataDirect technical support.
|
|
|
7833
|
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.OpenAccess SDK.slje.properties properties file. Make sure that the provider classes specified in this properties file are defined in the classpath. If necessary, contact Progress DataDirect technical support.
|
|
|
7834
|
An invalid name was supplied.
Cause: An internal error (standard MGSS error) occurred. Not used by the standard OpenAccess SDK authentication modules.
Action: Contact Progress DataDirect technical support.
|
|
|
7835
|
A supplied name was of an unsupported type.
Cause: Internal error (standard MGSS error) occurred. Not used by the standard OpenAccess SDK authentication modules.
Action: Contact Progress DataDirect technical support.
|
|
|
7836
|
Incorrect channel bindings were supplied.
Cause: An internal error (standard MGSS error) occurred. Not used by the standard OpenAccess SDK authentication modules.
Action: Contact Progress DataDirect technical support.
|
|
|
7837
|
An invalid status code was supplied.
Cause: An internal error (standard MGSS error) occurred. Not used by the standard OpenAccess SDK authentication modules.
Action: Contact Progress DataDirect technical support.
|
|
|
7838
|
A token had an invalid MIC.
Cause: An internal error (standard MGSS error) occurred. Not used by the standard OpenAccess SDK authentication modules.
Action: Contact Progress DataDirect technical support.
|
|
|
7839
|
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
|
Invalid context has been supplied.
Cause: Internal error (standard MGSS error). This is an internal error or an authentication state error.
Action: Contact Progress DataDirect technical support.
|
|
|
7841
|
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.OpenAccess SDK.slje.properties properties file. If necessary, contact Progress DataDirect technical support.
|
|
|
7842
|
A supplied credential was invalid.
Cause: An internal error (standard MGSS error) occurred. Not used by the standard OpenAccess SDK authentication modules.
Action: Contact Progress DataDirect technical support.
|
|
|
7843
|
The referenced credentials have expired.
Cause: An internal error (standard MGSS error) occurred. Not used by the standard OpenAccess SDK authentication modules.
Action: Contact Progress DataDirect technical support.
|
|
|
7844
|
The context has expired.
Cause: An internal error (standard MGSS error) occurred. Not used by the standard OpenAccess SDK authentication modules.
Action: Contact Progress DataDirect technical support.
|
|
|
7845
|
Miscellaneous failure, unspecified at the MGSS level.
Cause: An internal error (standard MGSS error) occurred. Not used by the standard OpenAccess SDK authentication modules.
Action: Contact Progress DataDirect technical support.
|
|
|
7846
|
The quality-of-protection requested could not be provided.
Cause: An internal error (standard MGSS error) occurred. Not used by the standard OpenAccess SDK authentication modules.
Action:: Contact Progress DataDirect technical support.
|
|
|
7847
|
The operation is forbidden by local security policy.
Cause: An internal error (standard MGSS error) occurred. Not used by the standard OpenAccess SDK authentication modules.
Action: Contact Progress DataDirect technical support.
|
|
|
7848
|
The operation or option is unavailable.
Cause: An internal error (standard MGSS error) occurred. Not used by the standard OpenAccess SDK authentication modules.
Action: Contact Progress DataDirect technical support.
|
|
|
7849
|
The requested credential element already exists.
Cause: An internal error (standard MGSS error) occurred. Not used by the standard OpenAccess SDK authentication modules.
Action: Contact Progress DataDirect technical support.
|
|
|
7850
|
The provided name was not a mechanism name.
Cause: An internal error (standard MGSS error) occurred. Not used by the standard OpenAccess SDK authentication modules.
Action: Contact Progress DataDirect technical support.
|
|
|
7851
|
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.OpenAccess SDK.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.OpenAccess SDK.slje.properties properties file. If necessary, contact Progress DataDirect technical support.
|
|
|
7852
|
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 Progress DataDirect technical support.
|
|
|
7853
|
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 server.
Action: Check the detailed error messages. If necessary, contact Progress DataDirect technical support.
|
|
|
7926
|
[SSL]Error closing SSL socket.
Cause: Internal error while closing up an SSL/TLS socket at the client server.
Action: Check the detailed error messages. If necessary, contact Progress DataDirect technical support.
|
|
|
7927
|
[SSL]Error receiving accept.
Cause: An internal error occurred while closing an SSL/TLS socket at the OpenAccess SDK Client server.
Action: Check the detailed error messages to troubleshoot the problem. If the error still occurs, contact Progress DataDirect technical support.
|
|
|
7930
|
[SSL]The cipher suite "<cipher suite>" is unknown.
Cause: The client server specified an unknown cipher suite.
Action
Check the CipherSuites connection parameter at the client.
Check the CipherSuites parameter in the OpenAccess SDK Server configuration file.
|
|
|
7931
|
[SSL]No cipher suite has been specified.
Cause: No cipher suite has been specified by the client server.
Action
Check the CipherSuites connection parameter.
Check the CipherSuites parameter in the OpenAccess SDK Server configuration file.
|
|
|
7932
|
[SSL]Problem reading files required for certificates.
Cause: An error occurred while reading the specified certificate by the OpenAccess SDK Server.
Action
Check the detailed error messages.
Check the RSACertificate parameter in the OpenAccess SDK Server configuration file.
Check the DSSCertificate parameter in the OpenAccess SDK 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 OpenAccess SDK 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 OpenAccess SDK Server.
Action
Supply the pass phrase using the pass phrase dialog.
Contact Progress DataDirect 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 OpenAccess SDK Server configuration file is empty, the private key is interpreted as unencrypted.
Action
Check the RSAPrivateKey parameter in the OpenAccess SDK Server configuration file.
Check the DSSPrivateKey parameter in the OpenAccess SDK Server configuration file.
Check the PassPhrase parameter in the OpenAccess SDK 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 OpenAccess SDK Server startup is different from the pass phrase used to encrypt the private key.
Action
Check the RASPrivateKey parameter in the OpenAccess SDK Server configuration file.
Check the DSSPrivateKey parameter in the OpenAccess SDK Server configuration file.
Check the PassPhrase parameter in the OpenAccess SDK 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 OpenAccess SDK 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 OpenAccess SDK Server configuration file.
|
|
|
7942
|
[SSL]A ciphersuite requires a DSS certificate that was not supplied.
Cause: An attempt was made to start the OpenAccess SDK 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 OpenAccess SDK Server configuration file.
Check the DSSCertificate parameter in the OpenAccess SDK Server configuration file.
|
|
|
7943
|
[SSL]A ciphersuite requires a DSS privatekey that was not supplied.
Cause: An attempt was made to start the OpenAccess SDK 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 OpenAccess SDK Server configuration file.
Check the DSSPrivateKey parameter in the OpenAccess SDK Server configuration file.
|
|
|
7944
|
[SSL]A ciphersuite requires an RSAA certificate that was not supplied.
Cause: An attempt was made to start the OpenAccess SDK 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 OpenAccess SDK Server configuration file.
Check the RSACertificate parameter in the OpenAccess SDK Server configuration file.
|
|
|
7945
|
[SSL]A ciphersuite requires an RSA privatekey that was not supplied.
Cause: An attempt was made to start the OpenAccess SDK 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 OpenAccess SDK Server configuration file.
Check the RSAPrivateKey parameter in the OpenAccess SDK Server configuration file.
|
|
|
7946
|
[SSL]An unnecessary RSA certificate was supplied.
Cause: An attempt was made to start the 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 OpenAccess SDK Server configuration file.
Check the CipherSuites parameter in the OpenAccess SDK Server configuration file.
Check the RSACertificate parameter in the OpenAccess SDK Server configuration file.
|
|
|
7947
|
[SSL]An unnecessary RSA privatekey was supplied.
Cause: An attempt was made to start the OpenAccess SDK 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 OpenAccess SDK Server configuration file.
Check the CipherSuites parameter in the OpenAccess SDK Server configuration file.
Check the RSAPrivateKey parameter in the OpenAccess SDK Server configuration file.
|
|
|
7948
|
[SSL]An unnecessary DSS certificate was supplied.
Cause: An attempt was made to start the OpenAccess SDK 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 OpenAccess SDK Server configuration file.
Check the CipherSuites parameter in the OpenAccess SDK Server configuration file.
Check the DSSCertificate parameter in the OpenAccess SDK Server configuration file.
|
|
|
7949
|
[SSL]An unnecessary DSS privatekey was supplied.
Cause: An attempt was made to start the OpenAccess SDK 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 OpenAccess SDK Server configuration file.
Check the CipherSuites parameter in the OpenAccess SDK Server configuration file.
Check the DSSPrivateKey parameter in the OpenAccess SDK Server configuration file.
|
|
|
7950
|
[SSL]An unnecessary value for the UsePassPhraseDialog was supplied.
Cause: The OpenAccess SDK 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 OpenAccess SDK Server configuration file.
Check the Network parameter in the OpenAccess SDK Server configuration file.
Check the CipherSuites parameter in the OpenAccess SDK Server configuration file.
|
|
|
7951
|
[SSL]An unnecessary pass phrase was supplied.
Cause: The OpenAccess SDK 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 OpenAccess SDK Server configuration file.
Check the Network parameter in the OpenAccess SDK Server configuration file.
Check the CipherSuites parameter in the server configuration file.
|
|
|
7952
|
[SSL]You cannot use PassPhrase and UsePassPhraseDialog together.
Cause: The pass phrase required to decrypt the private key from the server is specified in the OpenAccess SDK 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 OpenAccess SDK Server configuration file.
Check the PassPhrase parameter in the OpenAccess SDK Server configuration file.
|
|
|
7954
|
[SSL]Unexpected InterruptedException occurred while reading the pass phrase.
Cause: An internal error occurred when requesting the user for the OpenAccess SDK Server pass phrase using a dialog box.
Action: Contact Progress DataDirect technical support.
|
|
|
7955
|
[SSL]SSL/TLS handshake failure.
Cause: The client attempted to make an SSL connection to the OpenAccess SDK Server, but an error occurred during the initial SSL connection setup.
Action
Check the CipherSuites client connection attribute and the corresponding parameter in the OpenAccess SDK Server configuration file.
Check the CertificateChecker client connection attribute.
Check the OpenAccess SDK Server log file for more detailed error information.
|
|
|
7956
|
[SSL]Input of pass phrase interrupted by user.
Cause: Because the OpenAccess SDK Server is configured to use SSL with cipher suites that require access to the private key, the OpenAccess SDK 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 Server configuration file.
Check the CipherSuites parameter in the Server configuration file.
|
|
|
7981
|
Unable to allocate memory.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7982
|
SSL/TLS context already used to create connections so no changes to configuration allowed.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7983
|
An unknown SSL/TLS version was chosen.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7984
|
When supporting multiple SSL/TLS versions, SSL2, SSL3 and TLS1 must be enabled.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7985
|
Unknown cipher suite.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7986
|
Unsupported cipher suite.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7987
|
Error while building list of cipher suites.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7988
|
SSL/TLS context not fully initialized.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7989
|
SSL/TLS context not fully initialized: specify enabled cipher suites.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7990
|
SSL/TLS context not fully initialized: specify enabled SSL/TLS protocol versions.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7991
|
Internal error: cipher suite has no certificate type defined.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7992
|
You can not mix cipher suites which require RSA and DSA certificates together.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7993
|
Cipher suite requires a certificate which isn't supplied.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7994
|
Client or server authentication is enabled and no trust manager is specified.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7995
|
Client authentication is enabled without server authentication.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7996
|
Internal error when setting up SSL/TLS context.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7997
|
Unable to access private key.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7998
|
Unable to access certificate chain.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
7999
|
Public key in certificate doesn't correspond with the provided private key.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8000
|
Error while creating SSL/TLS connection.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8001
|
Error while accepting SSL/TLS connection.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8002
|
Error while connecting via SSL/TLS.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8003
|
Error with SSL/TLS handshake: connection is in an unknown or error state.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8004
|
Error with SSL/TLS handshake.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8005
|
Unable to send: SSL/TLS handshake failure.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8006
|
Error while sending via SSL/TLS.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8007
|
Unable to receive: SSL/TLS handshake failure.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8008
|
Error while receiving via SSL/TLS.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8009
|
Unable to initialize SSL/TLS context.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8010
|
Error with cipher suites.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8011
|
Unknown SSL/TLS context attribute.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8012
|
Error while initializing random number generator.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8013
|
SSL/TLS connection is closed, operation not supported.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8014
|
Unexpected EOF in SSL/TLS protocol.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8015
|
TCP/IP error during SSL/TLS protocol.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8016
|
Unknown SSL/TLS error.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8017
|
Critical section error.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8018
|
Error with client SSL/TLS session cache.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8019
|
Size of the SSL/TLS session cache must be positive.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8020
|
Time out value of a SSL/TLS session must be positive.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8021
|
Error while filling in SSL/TLS connection info.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8022
|
Error while generating temporary RSA key.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8023
|
Certificate library error.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8024
|
Key manager error.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8025
|
Trust manager error.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8026
|
Unknown cipher suite.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8027
|
Unknown protocol suite.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8028
|
Internal error, stub function called.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8029
|
No peer certificate
Cause: The Client was configured with a truststore and the Client expects the Server to send the certificate during the SSL handshake.
Action: Check the SSL configuration of your Client and Server.
|
|
|
8030
|
Subject DNS mismatch.
Cause: The Client was configured with a truststore and "hostname in certificate." A hostname mismatch was detected during the SSL handshake.
Action: Check the SSL configuration of your Client and Server.
|
|
|
8031
|
Cipher suite<cipher_suite> can not be used with the current certificate.
Cause: The keytype of the private key specified in ServiceSSLKeyStore is not the same type as the specified cipher suite. For example, an RSA private key can only be used with the RSA cipher suite, not with a DSA cipher suite. Although an error is generated, the server uses the next valid cipher suite specified in ServiceSSLCipherSuites.
Action: Check the SSL configuration of your Client and Server.
|
|
|
8032
|
SSL/TLS handshake failure due to a packet with a wrong header.
Cause: A Client with encryption disabled attempted to connect to an SSL-enabled Server.
Action: Enable encryption on the Client.
|
|
|
8033
|
SSL/TLS handshake failure due to no shared ciphers.
Cause: No cipher suites of the Client matched those configured for the Server. For example, if the Server was configured with anonymous cipher suites and the Client was configured with a truststore, the Client sends a list of cipher suites supporting only certificates.
Action: Add the required cipher suites to ServiceSSLCipherSuites. For more information, refer to the OpenAccess SDK Administrator’s Guide.
|
|
|
8080
|
Open SSL <error>.
Cause: An OpenSSL error occurred.
Action: Enable encryption on the Client.
|
|
|
8081
|
Open SSL <error>.
Cause: An OpenSSL error occurred.
Action: Add the required cipher suites to ServiceSSLCipherSuites. For more information, refer to the OpenAccess SDK Administrator’s Guide.
|
|
|
8139
|
No peer address to compare certificate.
Cause: The Client was configured with a truststore and "hostname in certificate" contains the special value #SERVERNAME# so a peer address could not be found.
Action: Contact Progress DataDirect technical support.
|
|
|
8458
|
Problem obtaining trusted CA certificates from Truststore.
Cause: The truststore file is not a valid truststore or the truststore password is incorrect.
Action: Make sure the truststore file is a valid truststore or correct the truststore password.
|
|
|
8459
|
There are no trusted CA certificates in the Truststore.
Cause: The truststore does not contain a valid CA certificate.
Action: Use a truststore with a valid CA certificate.
|
|
|
8476
|
Memory allocation failure.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8477
|
Open SSL error.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8478
|
No certificates in certificate chain.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
8479
|
No top level certificate found in certificate chain.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
9501
|
Handshake failure: You are trying to connect to a server that is not an OpenAccess Server.
Cause: An attempt was made to connect to a server that is not an OpenAccess SDK Server.
Action: Make sure that the connection information configured at the OpenAccess SDK Client is specified correctly to connect to the OpenAccess SDK Server.
|
|
|
9502
|
Handshake failure: A protocol error occurred during the connection setup.
Cause: An attempt was detected to connect to an OpenAccess SDK Server running an incompatible version of OpenAccess SDK.
Action: Verify that the versions of your OpenAccess SDK Client and OpenAccess SDK Server are compatible. Contact Progress DataDirect technical support, if necessary.
|
|
|
9503
|
Handshake failure: You are trying to connect to a server running an incompatible version of OpenAccess Server.
Cause: The OpenAccess SDK Client is incompatible with the version of the OpenAccess SDK Server to which it tried to connect.
Action: Verify that the versions of your OpenAccess SDK Client and OpenAccess SDK Server are compatible. Contact Progress DataDirect technical support, if necessary.
|
|
|
9509
|
Server asked for unknown encryption.
Cause: An internal error occurred.
Action: Contact Progress DataDirect 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 OpenAccess SDK Server configuration.
|
|
|
9522
|
Invalid OEM id.
Cause: The OEM id specified was not valid.
Action: Contact Progress DataDirect 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 OpenAccess SDK Server configuration. Refer to the OpenAccess SDK Administrator’s Guide for information about service attributes.
|
|
|
9535
|
Connection timed out.
Cause: Establishing a connection to OpenAccess SDK 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.
|
|
|
10101
|
Invalid database name:<database>. Error looking up database information.
Cause: An invalid database name caused an error while looking up database information.
Action: Correct the database name and try the operation again.
|
|
|
10102
|
OpenAccess SDK SQL engine is unable to load the IP module. Verify that IP Module:(<module>) is installed correctly.
Cause: OpenAccess SDK SQL engine is unable to load the specified IP module.
Action:
Check your ServiceEnvironmentVariable to make sure the IP module and the dependencies can be loaded.
Verify that the IP module was compiled.
Verify that the compiler flags used to compile the IP module are correct.
For ADO.NET, use the 32-bit server instead of the 64-bit server.
For further suggestions, search the Progress DataDirect Knowledgebase at http://knowledgebase.progress.com/articles/Article/6974.
|
|
|
10103
|
Error un-initializing the cache for disk storage
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10104
|
Syntax Error in the SQL statement.
Cause: A SQL statement contained a syntax error.
Action: Check your application. Correct the syntax of the SQL statement.
|
|
|
10105
|
Invalid parameter value for parameter:<parameter>.
Cause: An invalid value for the specified parameter was used.
Action: Check your application. Correct the invalid parameter value.
|
|
|
10106
|
IP did not register the DDL function.
Cause: The IP did not register the DDL function.
Action: Register the DDL function in the IP to handle DDL requests. Refer to the OpenAccess SDK Programmer’s Reference for more information.
|
|
|
10107
|
IP did not register the Stored Procedure function.
Cause: The IP did not register the stored procedure function.
Action: Register the PROCEDURE function in the IP to handle stored procedure requests. Refer to the OpenAccess SDK Programmer’s Reference for more information.
|
|
|
10108
|
IP did not register the DCL function.
Cause: The IP did not register the DCL function.
Action: Register the DCL function in the IP to handle DCL requests. Refer to the OpenAccess SDK Programmer’s Reference for more information.
|
|
|
10109
|
IP did not register the Privilege function.
Cause: The IP did not register the Privilege function.
Action: Register the PRIVILEGE function in the IP to handle privilege requests. Refer to the OpenAccess SDK Programmer’s Reference for more information.
|
|
|
10110
|
Insufficient privilege on object:<object>
Cause: The user did not have the correct privileges to perform the requested operation on this object.
Action: Verify the privileges. Consult your system administrator for the correct privileges.
|
|
|
10111
|
Insufficient privilege for command
Cause: The user did not have the correct privileges to execute the command.
Action: Verify the privileges. Consult your system administrator for the correct privileges.
|
|
|
10112
|
IP did not register the Native command function.
Cause: The IP did not register the NATIVE command function.
Action: Register the NATIVE function in the IP to handle native command requests. Refer to the OpenAccess SDK Programmer’s Reference for more information.
|
|
|
10113
|
Pushdown query processing requires support for Dynamic Schema.
Cause: The IP did not enable dynamic schema.
Action: Enable dynamic schema in the IP by defining GETSUPPORT(IP_SUPPORT_SCHEMA). Refer to the OpenAccess SDK SQL Engine Programmer’s Guide for more information.
|
|
|
10114
|
Invalid Statement type:<statement_type>.
Cause: The type of statement that was executed is not supported.
Action: Check your application. Verify that you are executing the correct statement type.
|
|
|
10115
|
Functionality is not supported.
Cause: The requested functionality is not supported.
Action: Contact Progress DataDirect technical support.
|
|
|
10116
|
Only SELECT queries are supported on Schema Tables.
Cause: A statement type other than a SELECT statement was executed on a schema table.
Action: Check your application. Correct the statement.
|
|
|
10117
|
IP did not register the Dynamic Schema function.
Cause: The IP did not register the dynamic schema function.
Action: Enable dynamic schema in the IP by defining GETSUPPORT(IP_SUPPORT_SCHEMA). Refer to the OpenAccess SDK SQL Engine Programmer’s Guide for more information.
|
|
|
10118
|
Cannot open view data file:<data_file>
Cause: The IP cannot open the data file for the specified view?
Action: Verify that the location configured in the DataSourceIPSchemaPath attribute exists. Also make sure that the user has permissions to create files in this directory.
|
|
|
10119
|
<statement_type>(): Unsupported Statement type:<statement_type>.
Cause: The type of statement that was executed is not supported.
Action: Check your application. Correct the statement.
|
|
|
10120
|
FOR UPDATE clause is not supported in a JOIN.
Cause: A JOIN clause contained a FOR UPDATE clause.
Action: Check your application. Correct the invalid JOIN clause. Refer to the OpenAccess SDK SQL Reference for more information.
|
|
|
10121
|
<join> OUTER JOIN is not supported.
Cause: An OUTER JOIN clause was executed.
Action: Check your application. Refer to the OpenAccess SDK SQL Reference for more information.
|
|
|
10122
|
Insert value list does not match column list.
Cause: The number of values provided by an INSERT statement did not match the number of columns.
Action: Check your application. Correct the INSERT statement.
|
|
|
10123
|
Integrity constraint violation. Value is not specified for NON-NULLABLE column:<column>.
Cause: A value was not specified for a non-nullable column. Non-nullable columns require a value.
Action: Check your application. Make sure that a value is specified for each non-nullable column in statements.
|
|
|
10124
|
Cannot insert or update value for Pseudo Column:<column>.
Cause: The application attempted to insert or update the value for a pseudo column.
Action: Check your application.
|
|
|
10125
|
Column:<column> not found.
Cause: The specified column could not be located.
Action: Check your application. Make sure the correct column was specified.
|
|
|
10126
|
Invalid number of input parameters: <x>. The correct number is <x>.
Cause: The number of specified values did not match the number of input parameters.
Action: Check your application. Make sure the number of specified values matches the number of input parameters.
|
|
|
10127
|
The number of result columns of the queries in UNION do not match.
Cause: A UNION subquery did not specify the same number of columns for the union as the query. For example, the following query contains a UNION subquery that specifies only one column when the main query specifies two columns:
SELECT c1, c3 FROM T1 UNION SELECT c3 FROM T2
Action: Modify all UNION subqueries to specify the same number of columns as specified by the query.
|
|
|
10128
|
The type of the result columns of the queries in UNION do not match. Mismatch with select-item number <x>.
Cause: The data type of the columns specified in the UNION subquery did not match the data type of the columns specified in the query. For example, the following query contains a UNION subquery that specifies a DATE data type when the query specifies an INTEGER data type.
SELECT empno FROM emp UNION SELECT hiredate FROM emp
Action: Modify all UNION subqueries to specify columns with the same data type as the columns specified by the query.
|
|
|
10129
|
Base table:<table> not found.
Cause: The specified base table could not be located.
Action: The CONNECT operation requires a base table name. Check the OAIP_connect value.
|
|
|
10130
|
Unsupported query syntax. Query result as source table is not supported.
Cause: A query result was specified as a source table.
Action: Check your application. Correct the query. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10131
|
Could not find any column information for table:<table>.
Cause: Column information for the specified table could not be found.
Action: Check your application. Make sure that you specified the correct table.
|
|
|
10132
|
Invalid column:<column> in <table>.
Cause: A statement contained the specified column, which was invalid for the specified table.
Action: Check your application. Make sure that you specified the correct column.
|
|
|
10133
|
Invalid column number:<x> in ORDER BY with result column count:<x>.
Cause: The ORDER BY clause contained an invalid column number.
Action: Check your application. Verify the specified column number in the ORDER BY clause.
|
|
|
10134
|
Invalid SQL Syntax. Columns in ORDER BY should be part of result set when SELECT DISTINCT is specified.
Cause: The columns in the ORDER BY clause were not part of the result set.
Action: Check your application. Verify the specified columns in the ORDER BY clause.
|
|
|
10135
|
Invalid SQL Syntax. Columns in ORDER BY should be part of result set in a UNION query
Cause: The columns in the ORDER BY clause were not part of the result set.
Action: Check your application. Verify the specified columns in the ORDER BY clause.
|
|
|
10136
|
Invalid SQL Syntax. All columns of the select list & order by should have set functions or be part of GROUP BY clause.
Cause: The specified columns in the SELECT list or the ORDER BY clause did not have set functions or were not part of a GROUP BY clause.
Action: Check your application. Verify that the columns in the SELECT list or ORDER BY clause have set functions or are part of the GROUP BY clause.
|
|
|
10137
|
Invalid SQL Syntax. All columns of the select list & order by should have set functions.
Cause: The columns in the SELECT list or the ORDER BY clause did not have set functions.
Action: Check your application. Verify that the columns in the SELECT list or ORDER BY clause have set functions.
|
|
|
10138
|
Invalid SQL syntax. Set functions (AVG, SUM, VAR_SAMP, VAR_POP, STDDEV_SAMP, STDDEV_POP) are applicable to integer-based fields and numeric data types
Cause: A set function was used incorrectly.
Action: Check your application. Verify that the set functions are used correctly. For more information, refer to the OpenAccess SDK SQL Reference.
|
|
|
10139
|
Invalid SQL Syntax. Set functions in expressions are not supported.
Cause: A set function was used in an expression.
Action: Check your application. Verify that the set function is used correctly. For more information, refer to the OpenAccess SDK SQL Reference.
|
|
|
10140
|
Invalid SQL Syntax. Nested set functions are not supported.
Cause: A statement contained a nested set function.
Action: Check your application. Verify that a nested set function is not used. For more information, refer to the OpenAccess SDK SQL Reference.
|
|
|
10141
|
Invalid SQL Syntax. Parameters/SubQueries are not supported as part of select list.
Cause: A SELECT list contained a parameter or subquery.
Action: Check your application. Verify that SELECT lists do not contain a parameter of subquery. For more information, refer to the OpenAccess SDK SQL Reference.
|
|
|
10142
|
Invalid SQL Syntax. Interval literal can only be used in a datetime expression.
Cause: An interval literal was used in an expression other than a datetime expression.
Action: Check your application. Verify that interval literals are used only in datetime expressions. For more information, refer to the OpenAccess SDK SQL Reference.
|
|
|
10143
|
Invalid Interval Literal:'<literal>' in query. <field> field not found.
Cause: A statement contained an invalid interval literal.
Action: Check your application. Correct any invalid interval literals.
|
|
|
10144
|
Invalid SQL Syntax. Set functions are not supported in Search Condition.
Cause: The search condition contained a set function.
Action: Check your application. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10145
|
Invalid Interval Literal:'<literal>' in query. <field> field not found.
Cause: A statement contained an invalid interval literal.
Action: Check your application. Correct any invalid interval literals.
|
|
|
10146
|
Invalid SQL syntax. Columns in HAVING clause can reference grouping columns or used in set functions.
Cause: A HAVING clause was invalid. Columns in a HAVING clause can reference columns or can be used in set functions.
Action: Check your application. Correct any invalid HAVING clauses. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10147
|
Invalid SQL Syntax. Set functions are not valid in insert list.
Cause: An INSERT list contained a set function.
Action: Check your application. Do not use set functions in an INSERT list. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10148
|
Invalid SQL Syntax. Column names are not valid in insert list.
Cause: An INSERT list contained a column name.
Action: Check your application. Do not use column names in an INSERT list. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10149
|
Unsupported scalar function:<function>.
Cause: The specified scalar function is not supported.
Action: Check your application. Correct the specified scalar function. Refer to the OpenAccess SDK SQL Reference for more information.
|
|
|
10150
|
Invalid syntax used with scalar function:<function>. Function expects a maximum of <x> arguments.
Cause: The number of arguments provided for the specified scalar function is incorrect.
Action: Check your application. Correct the specified scalar function. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10151
|
Invalid syntax used with scalar function:<function>. Function expects <x> arguments.
Cause: The number of arguments provided for the specified scalar function is incorrect.
Action: Check your application. Correct the specified scalar function. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10152
|
Invalid Stmt. Iincompatible expression value types:<type>, <type>.
Cause: The statement contained incompatible expression value types.
Action: Check your application. Correct any incompatible expression value types.
|
|
|
10153
|
Generating arithmetic result with new xo type:<type> for expressions of xo type:<type>, <type> is not supported.
Cause: The query contained an expression that specified a data type that is not supported.
Action: Check your application. Verify that all expressions specify a supported data type.
|
|
|
10154
|
Arithmetic operations on data type:<type> not supported.
Cause: The specified data type does not support arithmetic operations.
Action: Check your application.
|
|
|
10155
|
Invalid column name:<column> in statistics information for table:<table>.
Cause: Statistics information for the table contained an invalid column name.
Action: Check your application.
|
|
|
10156
|
Error deciding the order of tables for processing the query. Table count mismatch
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10157
|
Unable to decide the table process order for JOIN. Tables will be processed using the order given in the Query.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10158
|
Incomplete HINT specified for JOIN order. No order specified for table:<table>
Cause: The HINT clause did not specify all the tables specified in the Select list.
Action: Check your application. Make sure the HINT clause specifies all the tables specified in the Select list.
|
|
|
10159
|
Found no matching columns for the tables.
Cause: The table did not contain any of the columns specified in the statement.
Action: Check your application. Verify the columns that are specified in the statement.
|
|
|
10160
|
Invalid Procedure:<procedure> in query.
Cause: A procedure called in the statement was invalid.
Action: Check your application. Correct the invalid procedure.
|
|
|
10161
|
Integrity constraint violation. NULL value specified for NON-NULLABLE column:<column>.
Cause: A NULL value was specified for a non-nullable column.
Action: Check your application. Correct the statement to specify a non-null value.
|
|
|
10162
|
Invalid Value. XoType:<type> specified for column:<column> with XoType:<type>.
Cause: A value or data type was specified that was not compatible with the data type of the column.
Action: Check your application. Correct the invalid value or data type.
|
|
|
10163
|
Unexpected value type:<type> specified for column:<column>.
Cause: A value or data type was specified that was not compatible with the data type of the column.
Action: Check your application. Correct the invalid value or data type.
|
|
|
10164
|
View:<view> already exists.
Cause: The application attempted to create a view that already exists.
Action: Check your application. Correct the name of the view to create.
|
|
|
10165
|
CREATE VIEW Functionality is not supported.
Cause: The version of OpenAccess SDK does not support CREATE VIEW functionality.
Action: Install a newer version of OpenAccess SDK.
|
|
|
10166
|
Degree of the derived table does not match the column list.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10167
|
Error converting the result of scalar function:<function> from type:<type> to <type>.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10168
|
Error getting the literal value of left operand.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10169
|
Error getting the literal value of right operand.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10170
|
View:<view> not found.
Cause: The specified view was not found.
Action: Check your application.
|
|
|
10171
|
Compare function is not set for the condition.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10172
|
Invalid arguments passed for getting LEFT Value.
Cause: An invalid argument was passed for getting the left value.
Action: Check your application. Correct the invalid argument.
|
|
|
10173
|
Invalid arguments passed for getting RIGHT Value.
Cause: An invalid argument was passed for getting the right value.
Action: Check your application. Correct the invalid argument.
|
|
|
10174
|
Invalid value passed for column:<column>. The length:<x> is not valid for data type:<type>.
Cause: The value passed for the specified column does not have the correct length for the data type of the column.
Action: Check your application. Make sure that there is not a mismatch between the value and the length of the data type.
|
|
|
10175
|
Error converting the value for column:<column>.
Cause: An error occurred while converting the value for the specified column.
Action: Contact Progress DataDirect technical support.
|
|
|
10176
|
Incompatible value type specified for column:<column>. Column Type = <type> and Value Type = <type>.
Cause: The statement specifies an incompatible data type for the specified column.
Action: Check your application. Make sure that there is not a mismatch between the value data type and the column data type.
|
|
|
10177
|
Incompatible data for LONG field type. Data is being specified as type <type> for a column of type <type>.
Cause: The statement specifies an incompatible value for the LONG data type.
Action: Check your application. Correct the incompatible value.
|
|
|
10178
|
Could not retrieve the search index for search column:<column>.
Cause: The search index for the specified column could not be retrieved.
Action: Contact Progress DataDirect technical support.
|
|
|
10179
|
Syntax error in SQL statement. <x> line <x> at or after token <token>.
Cause: The SQL statement contains a syntax error.
Action: Check your application. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10180
|
Invalid column list in FOREIGN KEY clause.
Cause: An invalid column list was specified in the FOREIGN KEY clause.
Action: Check your application. Correct the invalid column list.
|
|
|
10181
|
Invalid parameters. Cannot handle query to table:<table>.
Cause: The statement contained an invalid parameter.
Action: Check your application. Correct the invalid parameter.
|
|
|
10182
|
Invalid parameters. Cannot handle Search Column.
Cause: The statement contained an invalid parameter.
Action: Check your application. Correct the invalid parameter.
|
|
|
10183
|
Only SELECT queries are supported on Schema Tables. Invalid StmtType=<statement_type>
Cause: An invalid operation was attempted on a schema table.
Action: Check your application. Only SELECT queries are supported on schema tables.
|
|
|
10184
|
Invalid Object Type:<object_type>.
Cause: Invalid System table name in the SQL statement.
Action: Correct the system table name in the SQL statement.
|
|
|
10185
|
Error with dynamic schema query. Could not get one of the column handles.
Cause: An error occurred because the dynamic schema could not get a column handle.
Action: Make sure that the column name specified in dam_getCol is correct. If the error persists, contact Progress DataDirect technical support.
|
|
|
10186
|
Error initializing the disk cache
Cause: An error occurred while initializing the disk cache.
Action: Verify that the directory referenced by ServiceSQLDiskCachePath exists.
|
|
|
10187
|
Unsupported conditional operator:<operator> used with long data type field.
Cause: The statement contained a conditional operator that was not supported with the LONG data type.
Action: Check your application. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10188
|
Invalid LIKE syntax. LIKE operator supported only for CHAR & VARCHAR fields.
Cause: The SQL statement contained a syntax error for a LIKE operator. LIKE operators are supported only for CHAR and VARCHAR fields.
Action: Check your application. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10189
|
Error in external sort process.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10190
|
Invalid input to scalar function <function>.
Cause: The specified scalar function contained an invalid input value.
Action: Check your application. Correct the invalid input value. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10191
|
Invalid input to scalar function <function>. Null value specified for non-Null argument.
Cause: The specified scalar function used a NULL value for a non-NULL argument.
Action: Check your application. Correct the input value. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10192
|
Division by zero. Invalid input to scalar function <function>. Second parameter is zero.
Cause: The specified scalar function contained an invalid input value. The second parameter must be 0.
Action: Check your application. Correct the input value. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10193
|
Syntax Error in the SQL statement.
Cause: The SQL statement that was executed contained a syntax error.
Action: Check your application. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10194
|
Invalid value (value type=<type>) passed. Cannot convert.
Cause: The OpenAccess SDK SQL Engine cannot convert the value that was passed.
Action: Check your application. Correct the invalid value.
|
|
|
10195
|
dam_isRowComplete() Value for column:<column> is not specified.
Cause: A required column value was not specified.
Action: Check your application.
|
|
|
10196
|
Invalid index information for index:<index>. seq_in_index(<x>) value for column:<column> does not match the expected(<x>).
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10197
|
Invalid statement. Incompatible expression value types in condition:<type>, <type>.
Cause: The statement that was executed was invalid because it contained incompatible expression value types.
Action: Check your application. Make sure that the data types used for the expression value of the condition are compatible.
|
|
|
10198
|
Invalid statement. Error assigning compare function for data type:<type>.
Cause: The statement that was executed was invalid because of an error processing the specified data type.
Action: Check your application. Make sure that the data type used is valid for the statement.
|
|
|
10199
|
Division by zero.
Cause: The value of an expression in the denominator resulted in 0.
Action: Check your application. Make sure the expression in the denominator is correct.
|
|
|
10200
|
General error.
Cause: A general error occurred.
Action: Check the error message and follow the suggested action. If the problem persists, contact Progress DataDirect technical support.
|
|
|
10201
|
Error processing the data file. Error Code:<error_code>
Cause:An error occurred while processing the data file.
Action: Refer to the specified error code for more information.
|
|
|
10202
|
Cannot open file '<file>'. Error Code <error_code>.
Cause: The specified file could not be opened.
Action: Refer to the specified error code for more information.
|
|
|
10203
|
Cannot close file. Error Code <error_code>
Cause: The file could not be closed.
Action: Refer to the specified error code for more information.
|
|
|
10204
|
Cannot start append to the data file. Error Code <error_code>
Cause: An append to the data file could not be started.
Action: Refer to the specified error code for more information.
|
|
|
10205
|
Cannot append record to the data file. Error Code <error_code>
Cause: A record could not be appended to the data file.
Action: Refer to the specified error code for more information.
|
|
|
10206
|
<table> table is missing one of the required columns.
Cause: A column specified in the statement cannot be located in the table.
Action: Check your application. Make sure that the column list for statements accessing the specified table is correct.
|
|
|
10207
|
Error processing the <file> file. Error Code:<error_code>
Cause: An error occurred while processing the specified file.
Action: Refer to the specified error code for more information.
|
|
|
10208
|
Columns of Table <table> could not be found in OA_COLUMNS.
Cause: The columns in the specified table could not be found in OA_COLUMNS.
Action: Check whether columns info is added while creating the table or in the ipSchema function.
|
|
|
10209
|
Internal error. Could not locate Result for the query.
Cause: An internal error occurred.
Action: Contact Technical Support.
|
|
|
10210
|
Error converting value from type:<type> to type:<type>
Cause: An error occurred while converting the value from the specified data type to another data type.
Action: Check your application. Perform the following actions:
Make sure that no non-numeric characters have been specified in numeric fields.
Make sure that no Unicode characters have been specified in ASCII fields.
If the problem persists, contact Progress DataDirect technical support.
|
|
|
10211
|
Error opening disk cache file <file>
Cause: An error occurred while opening the specified disk cache file.
Action: Contact Progress DataDirect technical support.
|
|
|
10212
|
Error from fseek in the disk cache file:<file>
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10213
|
Disk cache error. Cannot allocate memory
Cause: An error occurred while trying to allocate memory to the disk cache.
Action: Check the space available on the hard disk. If the problem persists, contact Progress DataDirect technical support.
|
|
|
10214
|
Disk Cache file write error
Cause: An error occurred while trying to write a file to the disk cache.
Action: Check the space available on the hard disk. If the problem persists, contact Progress DataDirect technical support.
|
|
|
10215
|
Disk Cache file size limit has reached
Cause: The disk cache generated an error because its maximum file size limit was reached.
Action: Increase the value of ServiceSQLDiskCacheMaxSize. If the problem persists, contact Progress DataDirect technical support.
|
|
|
10216
|
Disk cache error. Unique identifier <id> not found
Cause: The specified identifier could not be found in the disk cache.
Action: Contact Progress DataDirect technical support.
|
|
|
10217
|
Error closing disk cache file <file>
Cause: An error occurred while closing the specified disk cache.
Action: Contact Progress DataDirect technical support.
|
|
|
10218
|
Disk Cache File read error
Cause: An error occurred while reading the disk cache.
Action: Contact Progress DataDirect technical support.
|
|
|
10219
|
Disk cache error. Unique identifier <id> already exist
Cause: A unique identifier already existed in the disk cache.
Action: Contact Progress DataDirect technical support.
|
|
|
10220
|
Disk cache error. Invalid value nodetype (<type>)
Cause: The specified node type was invalid in the disk cache.
Action: Contact Progress DataDirect technical support.
|
|
|
10221
|
Disk cache error. Invalid xo datatype (<type>)
Cause: A value with an invalid data type was written to the disk cache.
Action: Contact Progress DataDirect technical support.
|
|
|
10222
|
Disk cache error. Invalid record length: <x>
Cause: A value with an invalid length for its data type was written to the disk cache.
Action: Contact Progress DataDirect technical support.
|
|
|
10223
|
Disk cache error. Invalid number of columns: <x>
Cause: The specified number of columns was invalid for the disk cache.
Action: Contact Progress DataDirect technical support.
|
|
|
10224
|
Disk cache error. Record length:<x> is large for sorting
Cause: The specified record length was too large to allow sorting the contents of the disk cache.
Action: Contact Progress DataDirect technical support.
|
|
|
10225
|
Disk cache error. Field id:<id> is large for sorting
Cause: The specified field ID is too large to allow sorting the contents of the disk cache.
Action: Contact Progress DataDirect technical support.
|
|
|
10226
|
Disk cache error. Field length is large for sorting
Cause: The field length is too large to allow sorting the contents of the disk cache.
Action: Contact Progress DataDirect technical support.
|
|
|
10227
|
Disk cache error. Invalid number of blocks (<x>)
Cause: The specified number of blocks is invalid for the disk cache.
Action: Contact Progress DataDirect technical support.
|
|
|
10228
|
Disk cache error. Invalid number of passes
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10229
|
Disk cache error. Data blocks chain corrupted
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10230
|
Disk cache error. Invalid file size parameter
Cause: A file size parameter was invalid in the disk cache.
Action: Contact Progress DataDirect technical support.
|
|
|
10231
|
Disk cache error. Invalid index for column:<column>. No value found
Cause: An invalid index for the specified column resulted in not finding the value.
Action: Contact Progress DataDirect technical support.
|
|
|
10232
|
Disk cache error. Field length:<x> exceeds maximum limit of 65535.
Cause: The length of the specified field exceeds the maximum limit of the disk cache.
Action: Contact Progress DataDirect technical support.
|
|
|
10233
|
Disk cache error. Field length:<x> exceeds maximum limit of 0x7fffffffffffffff.
Cause: The length of the specified long field exceeds the maximum limit of the disk cache.
Action: Reduce the length of the long data field.
|
|
|
10235
|
ORDER BY clause is invalid in views, derived tables, and subqueries unless TOP is also specified
Cause: An ORDER BY clause was used in views, derived tables, or subqueries without a TOP clause.
Action: Check your application. Verify that ORDER BY is used in views, derived tables, or subqueries with TOP clause.
|
|
|
10236
|
Invalid SQL Syntax. ORDER BY is not supported in UNION subqueries.
Cause: A statement has ORDER BY in a UNION subquery.
Action: Check your application. Verify that ORDER BY is not used in a UNION subquery.
|
|
|
10237
|
Invalid SQL Syntax. Rank functions and Queries are not valid in insert list.
Cause: A statement has Rank functions/Queries in an insert list.
Action: Check your application. Verify that Rank functions/Queries are used in the insert list.
|
|
|
10238
|
IP Does not support TableFunctions.
Cause: Support for TableFunctions is not enabled in the IP.
Action: Check your IP implementation. Verify that the IP GETSUPPORT function/method is returning 1 for IP_SUPPORT_TABLE_FUNCTIONS.
|
|
|
10239
|
Invalid escape character '%ls' was specified in a LIKE predicate.
Cause: The specified escape character is invalid.
Action: Check your application. Correct the invalid escape character.
|
|
|
10240
|
Table function:%ls not found.
Cause: The specified Table function was not found.
Action: Check your application.
|
|
|
10241
|
Invalid data. Value for result column:<x> is not compatible. Expected:<x> instead of <x>.
Cause: The value for the specified column was invalid.
Action: Check your application. Correct the invalid value.
|
|
|
10242
|
Parameter value not specified for input argument:<parameter>
Cause: A value was not specified for the specified input parameter.
Action: Check your application. Make sure that a value is specified for the input parameter.
|
|
|
10243
|
Stored procedure does not support return value
Cause: The stored procedure that was called does not support return values
Action: Contact Progress DataDirect technical support.
|
|
|
10244
|
Invalid date/time literal.
Cause: A date/time literal in a statement was invalid.
Action: Check your application. Correct the invalid date/time literal. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10245
|
Invalid numeric literal.
Cause: A numeric literal in a statement was invalid.
Action: Check your application. Correct the invalid numeric literal. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10246
|
Query Timeout expired
Cause: A timeout expired.
Action: Verify that the OpenAccess SDK Server is running and that you have specified the correct network address of the host. If your configuration is correct, increase the query timeout value.
|
|
|
10247
|
Error computing date arithmetic. Result date may be prior to January 1, 1970
Cause: An error occurred while computing the date. Only dates after January 1, 1970 are supported for certain arithmetic operations.
Action: Contact Progress DataDirect technical support.
|
|
|
10248
|
Invalid date/time expression.
Cause: A date/time expression in a statement was invalid.
Action: Check your application. Correct the invalid date/time expression. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10249
|
Only Addition and Subtraction operations are supported with Interval Literals
Cause ; An interval literal was used in an unsupported operation. Interval literals can only be used to add an interval to a datetime (or add a datetime to an interval) or subtract an interval from a datetime.
Action: Check your application. Correct the invalid interval literal. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10250
|
Invalid usage. Cannot subtract datetime from interval literal.
Cause: An interval literal was used incorrectly. Interval literals can only be used to add an interval to a datetime (or add a datetime to an interval) or subtract an interval from a datetime.
Action: Check your application. Correct the invalid interval literal. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10251
|
Conversion of data from type:<type> to type:<type> is not supported.
Cause: A statement was executed that required an unsupported data type conversion.
Action: Check your application. Make sure that the specified values and data types are correct.
|
|
|
10252
|
Data exception-array element error. Column:<column>.
Cause: An array element error occurred while processing the specified column.
Action: Contact Progress DataDirect technical support.
|
|
|
10253
|
Array element reference is not valid for column:<column>.
Cause: A referenced array element was invalid for the specified column.
Action: Check your application. Make sure that the array element reference is correct.
|
|
|
10254
|
Invalid operation on non-array column:<column>
Cause: The requested operation was invalid for a non-array column.
Action: Check your application. Make sure that the requested operation for the non-array column is correct.
|
|
|
10256
|
Array element reference is not valid.
Cause: A reference to an array element was invalid.
Action: Check your application. Make sure that the array element reference is correct.
|
|
|
10257
|
Invalid cardinality:<x> for array column:<column>
Cause: The specified cardinality for the specified array column was invalid.
Action: Check your application. Correct the invalid cardinality for the specified array column.
|
|
|
10258
|
Invalid dynamic stored procedure schema. Schema did not expose result column.
Cause: The dynamic stored procedure schema used did not expose the requested column.
Action: Expose the result column of the dynamic procedure in the ipSchema function.
|
|
|
10259
|
Invalid stored procedure schema. Column:<column> has unsupported/invalid column type:<type>.
Cause: The requested stored procedure schema exposed the requested column, but the specified column is an unsupported data type.
Action: Contact Progress DataDirect technical support.
|
|
|
10260
|
Type:<type> is not a defined system type.
Cause: The specified data type is not supported.
Action: Contact Progress DataDirect technical support.
|
|
|
10261
|
IP Schema function returned error. No error message was provided.
Cause: The OpenAccess SDK SQL engine encountered an error while processing the ipSchema function.
Action: Contact Progress DataDirect technical support.
|
|
|
10262
|
IP SchemaEx function returned error. No error message was provided.
Cause: The OpenAccess SDK SQL engine encountered an error while processing the ipSchemaEx function.
Action: Contact Progress DataDirect technical support.
|
|
|
10263
|
IP Execute function returned error. No error message was provided.
Cause: The OpenAccess SDK SQL engine encountered an error while processing the ipExecute function.
Action: Contact Progress DataDirect technical support.
|
|
|
10264
|
IP DDL function returned error. No error message was provided.
Cause: The OpenAccess SDK SQL engine encountered an error while processing the ipDDL function.
Action: Contact Progress DataDirect technical support.
|
|
|
10265
|
IP Procedure function returned error. No error message was provided.
Cause: The OpenAccess SDK SQL engine encountered an error while processing the ipProcedure function.
Action: Contact Progress DataDirect technical support.
|
|
|
10266
|
IP ProcedureDynamic function returned error. No error message was provided.
Cause: The OpenAccess SDK SQL engine encountered an error while processing the ipProcedureDynamic function.
Action: Contact Progress DataDirect technical support.
|
|
|
10267
|
Query is cancelled
Cause: The query was cancelled by the user.
Action: No action required.
|
|
|
10268
|
Scalar function:<function> returned error.
Cause: The specified scalar function returned an error.
Action: Check the parameters passed to the scalar function. If the problem persists, contact Progress DataDirect technical support.
|
|
|
10269
|
Schema modifications are not allowed
Cause: A schema modification was attempted, but schema modifications are not enabled.
Action: Set the SQL Engine ServiceSQLSchemaUpdateAllowed parameter to enabled to enable schema modifications.
|
|
|
10270
|
dam_getOrderByCol() ORDER BY expression is not a simple column.
Cause: The value expression for the dam_getOrderByCol() ORDER BY expression was not a simple column.
Action: Check your application. Make sure the value for the dam_getOrderByCol() ORDER BY expression is a simple column.
|
|
|
10271
|
Driver:<driver> did not register the getInfo function.
Cause: The driver did not register the ipGetInfo function.
Action: Implement the ipGetInfo function in the IP.
|
|
|
10272
|
Invalid escape sequence. Valid characters after ESC are: an ESC pair, underscore, percent sign. Parsing error at offset <x>, offending character '<character>'
Cause: The specified escape sequence is invalid.
Action: Check your application. Correct the invalid escape sequence. Valid characters after ESC are: an ESC pair, underscore, percent sign.
|
|
|
10273
|
Invalid index information for Table:<table>. Index Name:<index>. <index>
Cause: The specified index contained invalid information for the specified table.
Action: Check the index information for the specified table.
|
|
|
10274
|
Percent values must be between 0 and 100
Cause: A percent value was specified that was invalid. Percent values must be an integer from 0 to 100.
Action: Check your application. Correct the invalid percent value.
|
|
|
10275
|
Syntax error. Column alias can be an identifier or literal
Cause: An alias specified in the statement was invalid. A column alias can be an identifier or a literal.
Action: Check your application. Correct the invalid alias. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10276
|
Correlated column:<column> is not part of a condition
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10277
|
Conversion of DataType:<type> to INTERVAL is not supported
Cause: The specified data type conversion is not supported.
Action: Check your application. Make sure the data type is correct.
|
|
|
10278
|
Interval Operations require one operand to be date/time and the other to be Interval literal
Cause: One or both operands in the interval operation were invalid. The first operand must be a date/time operand and the second must be an interval literal.
Action: Check your application. Correct any invalid operands.
|
|
|
10279
|
Dynamic SQL error - 'using-clause' does not match dynamic parameters. Value for Parameter:<parameter> is not specified.
Cause: A value for the specified parameter was not specified in the USING clause.
Action: Check your application. Specify a value for the parameter.
|
|
|
10280
|
Unsupported query syntax. Identifier exceeds limit.
Cause: An identifier in the statement exceeded its maximum limit.
Action: Check your application. Correct the identifier.
|
|
|
10281
|
Query exceeds MAX_TABLE_NAME_LEN limit of <x>
Cause: A table name specified in the statement exceeded the maximum length limit.
Action: Check your application. Correct the table name.
|
|
|
10282
|
Query exceeds MAX_COLUMNS_IN_TABLE limit of <x>
Cause: The number of columns specified in the statement exceeded the maximum limit.
Action: Check your application. Correct the number of table columns.
|
|
|
10283
|
Query exceeds MAX_COLUMN_NAME_LEN limit of <x>
Cause: A column name specified in the statement exceeded the maximum length limit.
Action: Check your application. Correct the column name.
|
|
|
10284
|
Query exceeds MAX_COLUMNS_IN_INDEX limit of <x>
Cause: The number of columns specified in the index exceeded the maximum limit.
Action: Check your application. Correct the number of index columns.
|
|
|
10285
|
Query exceeds MAX_TABLES_IN_SELECT limit of <x>
Cause: The number of tables specified in the statement exceeded the maximum limit.
Action: Check your application. Correct the number of tables.
|
|
|
10286
|
Subquery returned more than 1 value. This is not permitted when the subquery is used as an expression.
Cause: A subquery that was used as an expression returned more that one value.
Action: Check your application.Correct the expression. A subquery that is used as an expression must return only one value.
|
|
|
10287
|
Only one expression can be specified in the select list when the subquery is not introduced with EXISTS or UNIQUE.
Cause: A subquery was not introduced with either the EXISTS or UNIQUE clause and the SELECT list contained more than one expression.
Action: Check your application. Correct the SELECT list.
|
|
|
10288
|
Driver:<driver> did not register the XA function.
Cause: The driver could not register the XA function.
Action: Implement the XA function in the IP.
|
|
|
10289
|
Invalid or missing XID
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10290
|
XA error: <error>
Cause: An error occurred while processing a distributed transaction.
Action: Contact Progress DataDirect technical support.
|
|
|
10291
|
Table Rowset(Rows=<x>) has exceeded memory limit. Aborting operation.
Cause: The table rowset exceeded the memory limit
Action: Increase the value for the ServiceSQLDiskCacheMemSize service attribute.
|
|
|
10292
|
Invalid parameter value for parameter:<parameter>. Could not convert value from type:<x> to type:<x>
Cause: The value for the specified parameter was invalid because the data type conversion was not supported.
Action: Check your application. Correct the invalid parameter value.
|
|
|
10293
|
Query length of <x> exceeds supported limit of <x>. Please configure QueryMaxSize to support the query.
Cause: The value set for the ServiceSQLQueryMaxSize service attribute is too small. This service attribute specifies the maximum size of the query (in bytes) that the OpenAccess SDK SQL engine handles.
Action: Check the ServiceSQLQueryMaxSize service attribute in your OpenAccess SDK Server configuration. Refer to the OpenAccess SDK Administrator’s Guide for information about service attributes.
|
|
|
10294
|
Unicode feature is not licensed. Query with unicode results cannot be processed.
Cause: You are not licensed to use the Unicode feature.
Action: Contact Progress DataDirect technical support.
|
|
|
10295
|
Connection is not alive
Cause: The connection is no longer active, possibly because it timed out.
Action: Retry the connection. If the problem persists, contact Progress DataDirect technical support.
|
|
|
10296
|
dam_getGroupByCol() GROUP BY expression is not a simple column.
Cause: The value used for dam_getGroupByCol() GROUP BY expression was not a simple column.
Action: Check your application. Make sure that the value for the dam_getGroupByCol() GROUP BY expression is a simple column.
|
|
|
10297
|
Internal error. dam_expand_blockjoin_intersect_set_of_cond_list(): pListofCondList owner is not SQL_SET_CONDLIST_OWNS_NONE
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10298
|
Internal error. dam_remove_blockjoin_intersect_set_of_cond_list(): pListofCondList owner is not SQL_SET_CONDLIST_OWNS_NONE
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10299
|
Internal error. dam_generate_block_join_split_exp() Error splitting the WHERE expression
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10300
|
Error reported by IP Interface
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10301
|
License Error: Pass Through mode feature is not licensed.
Cause: The OpenAccess SDK Server could not locate the required license to execute the client request. The request is refused.
Action: Make sure a valid OpenAccess SDK license is registered. If the problem persists, contact Progress DataDirect technical support.
|
|
|
10302
|
License Error: DQP feature is not licensed.
Cause: The OpenAccess SDK Server could not locate the required license to execute the client request. The request is refused.
Action: Make sure a valid OpenAccess SDK license is registered. If the problem persists, contact Progress DataDirect technical support.
|
|
|
10303
|
License Error: Binary Schema feature is not licensed.
Cause: The OpenAccess SDK Server could not locate the required license to execute the client request. The request is refused.
Action: Make sure a valid OpenAccess SDK license is registered. If the problem persists, contact Progress DataDirect technical support.
|
|
|
10304
|
Column(Table:<table>:ColumnNumber:<x>) does not belong to the current table(<table>) being processed
Cause: The specified column was not located in the current table.
Action: Check your application. Verify the specified column.
|
|
|
10305
|
Internal error. dam_generate_table_pushdown_exp() Error splitting the WHERE expression.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10306
|
Internal error. dam_generate_table_pushdown_exp() Error splitting the Join expression.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10307
|
Internal error. dam_generate_table_pushdown_exp() Error filtering the join expression.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10308
|
Internal error. dam_generate_table_pushdown_exp() Error filtering the table expression.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10309
|
Internal error. dam_generate_split_exp(): Error splitting the WHERE expression.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10310
|
Internal error. dam_generate_split_exp(): Error splitting the TableExp.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10311
|
dam_evaluate_val_exp() Error converting value to type of the expression.
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10312
|
<join>Invalid syntax. Multiple outer join conditions on same table:<table>
Cause: Multiple outer join conditions were specified for the same table. Joins must be performed on separate tables.
Action: Check your application. Correct the invalid join syntax. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10313
|
<table>Could not find matching table
Cause: The specified table could not be located.
Action: Check your application. Verify that you have specified the table correctly.
|
|
|
10314
|
<join> Invalid usage of outer join condition
Cause: The specified outer join was invalid.
Action: Check your application. Correct the invalid outer join. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10315
|
Invalid length passed to the SUBSTRING function
Cause: A length used for the SUBSTRING function was invalid.
Action: Check your application. Correct the invalid length. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10316
|
Invalid start location passed to the INSERT function
Cause: A start location used for the INSERT function was invalid.
Action: Check your application. Correct the invalid start location. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10317
|
Invalid replace length passed to the INSERT function
Cause: A replace length used for the INSERT function was invalid.
Action: Check your application. Correct the invalid replace length. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10318
|
DayOfYear datepart specification is not currently supported.
Cause: A function contained a dayofyear datepart that was not supported.
Action: Check your application. Correct the invalid datepart. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10319
|
Millisecond datepart specification is not currently supported.
Cause: A function contained a millisecond datepart that was not supported.
Action: Check your application. Correct the invalid datepart. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10320
|
Fractional second datepart specification is not currently supported.
Cause: A function contained a fractional second datepart that was not supported.
Action: Check your application. Correct the invalid datepart. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10321
|
decode() Error converting value of input expression to XoType:<type>
Cause: A data type conversion error occurred while processing the input expression of the DECODE function.
Action: Check your application. Verify that the data types are correct. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10322
|
decode() Error converting value of result expression to XoType:<type>
Cause: A data type conversion error occurred while processing the result expression of the DECODE function.
Action: Check your application. Verify that the data types are correct. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10323
|
decode() Error converting value of search expression to XoType:<type>
Cause: A data type conversion error occurred while processing the search expression of the DECODE function.
Action: Check your application. Verify that the data types are correct. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10324
|
Invalid input to scalar function ifnull().
Cause: An IFNULL function contained an invalid input expression.
Action: Check your application. Correct the invalid input expression. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10325
|
Invalid input to scalar function convert().
Cause: A CONVERT function contained an invalid input expression.
Action: Check your application. Correct the invalid input expression. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10326
|
Invalid input to scalar function cast().
Cause: A CAST function contained an invalid input expression.
Action: Check your application. Correct the invalid input expression. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10327
|
cardinality() Could not get the input value.
Cause: The cardinality of the index could not be determined.
Action: Contact Progress DataDirect technical support.
|
|
|
10328
|
Invalid start location passed to the INSERT function
Cause: A INSERT function contained an invalid start location.
Action: Check your application. Correct the invalid start location. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10329
|
Invalid replace length passed to the INSERT function
Cause: A INSERT function contained an invalid replace length.
Action: Check your application. Correct the invalid replace length. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10330
|
Invalid length passed to the SUBSTRING function
Cause: A SUBSTRING function contained an invalid length.
Action: Check your application. Correct the invalid length. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10331
|
Translation of query exceeds the FROM clause buffer limit of <x>
Cause: The FROM clause expression exceeded the buffer limit.
Action: Reduce the size of the FROM clause expression.
|
|
|
10332
|
Translation of query exceeds the WHERE clause buffer limit of <x>
Cause: The WHERE clause expression exceeded the buffer limit.
Action: Reduce the size of the WHERE clause expression.
|
|
|
10333
|
Translation of query exceeds the GROUP BY clause buffer limit of <x>
Cause: The GROUP BY clause expression exceeded the buffer limit.
Action: Reduce the size of the GROUP BY clause expression.
|
|
|
10334
|
Translation of view query fails. Result column count is not set for view query.
Cause: The result column count was not set for the view query.
Action: Contact Progress DataDirect technical support.
|
|
|
10335
|
Translation of query exceeds the select-list-exp buffer limit of <x>
Cause: The SELECT list exceeded the buffer limit.
Action: Reduce the size of the SELECT list.
|
|
|
10336
|
Unsupported syntax. CASE expression is not allowed in GROUP BY
Cause: A GROUP BY clause contained a CASE expression.
Action: Check the SQL statement used by your application. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10337
|
Unsupported syntax. CASE expression is not allowed in ORDER BY
Cause: A CASE expression is not allowed in an ORDER BY clause.
Action: Check your application. Correct the invalid ORDER BY clause. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10338
|
Invalid syntax. Nested Aggregate functions are not allowed in ORDER BY
Cause: An ORDER BY clause contained a nested aggregate function.
Action: Check your application. Correct the invalid ORDER BY clause. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10339
|
Invalid schema passed for column:<column>. The length:<length> or precision:<precision> are not valid for data type:<type>
Cause: A statement contained an invalid schema name for the specified column.
Action: Check your application. Correct the invalid schema name. Refer to the OpenAccess SDK SQL Reference for the correct syntax.
|
|
|
10340
|
Translated query exceeds the query limit size of <x>
Cause: The query exceeded the maximum limit.
Action: Reduce the size of the query.
|
|
|
10341
|
Memory allocation error. Unable to allocate <x>
Cause: A request to the operating system to allocate memory failed.
Action: Free memory resources. If the problem persists, contact Progress DataDirect technical support.
|
|
|
10342
|
Invalid SQL Syntax. Rank functions do not support integer indices as ORDER BY clause expressions.
Cause: A Rank function in the SQL statement specified an integer index in its ORDER BY expression.
Action: Correct the SQL statement.
|
|
|
10343
|
Invalid SQL Syntax. The ranking function must have an ORDER BY clause.
Cause: A Rank function in the SQL statement was specified without an ORDER BY clause.
Action: Correct the SQL statement.
|
|
|
10344
|
Unsupported syntax. Rank functions can only appear in the SELECT or ORDER BY clauses.
Cause: A Rank function in the SQL statement was used in a clause other than a SELECT or ORDER BY.
Action: Correct the SQL statement.
|
|
|
10345
|
Invalid SQL Syntax. Rank functions in expressions are not supported.
Cause: A Rank function in the SQL statement was used in an expression.
Action: Correct the SQL statement.
|
|
|
10346
|
Invalid SQL Syntax. Rank functions are not supported in Search Condition.
Cause: A Rank function in the SQL statement was used in a search condition.
Action: Correct the SQL statement.
|
|
|
10347
|
Queries are not supported on OA_INFO table.
Cause: The SQL statement queried the OA_INFO table.
Action: Correct the SQL statement.
|
|
|
10348
|
Invalid operation on LOB Locators.
Cause: A SQL statement specified an operation on LOB data that was unsupported.
Action: Correct the SQL statement.
|
|
|
10349
|
Invalid arguments passed to the table function.
Cause: The parameters specified for the table function contain invalid values. Valid parameters are literals.
Action: Check your application. Correct the parameters specified for the table function.
|
|
|
10350
|
Data Source initialization has failed.
Cause: The data source initialization failed.
Action: Contact Progress DataDirect technical support.
|
|
|
10351
|
Main TLS retrieval has failed.
Cause: The client attempted to make a TLS connection to the OpenAccess SDK Server, but an error occurred when retrieving the data source TLS information.
Action: Contact Progress DataDirect technical support.
|
|
|
10352
|
Data Source tracing initialization has failed.
Cause: The data source tracing initialization failed.
Action: Contact Progress DataDirect technical support.
|
|
|
10353
|
IP initialization has failed.
Cause: The IP initialization failed.
Action: Contact Progress DataDirect technical support.
|
|
|
10354
|
IP exit has failed.
Cause: The IP exit failed.
Action: Contact Progress DataDirect technical support.
|
|
|
10355
|
Data Source thread initialization has failed.
Cause: The data source thread initialization failed.
Action: Contact Progress DataDirect technical support.
|
|
|
10356
|
Data Source TLS retrieval has failed.
Cause: The client attempted to make a TLS connection to the OpenAccess SDK Server, but an error occurred when retrieving the data source TLS information.
Action: Contact Progress DataDirect technical support.
|
|
|
10357
|
Unsupported query syntax. PERCENT option is not supported in TOP clause.
Cause: A TOP clause contained the PERCENT option.
Action: Check your application. Correct the invalid TOP clause. Refer to the OpenAccess SDK SQL Reference for the supported syntax.
|
|
|
10358
|
Invalid operation on non-LOB column: <column>.
Cause: A SQL statement specified a LOB operation on non-LOB data in the specified column.
Action: Correct the SQL statement.
|
|
|
10359
|
IP did not register the Get LongData function.
Cause: The IP did not register the ipGetLongData function.
Action: Implement the ipGetLongData function in the IP.
|
|
|
10360
|
Adding a value to a ’datetime’ column caused overflow.
Cause: The integer value in the DATEADD function caused a date overflow.
Action: Correct the integer value in the DATEADD function.
|
|
|
10361
|
IP Execute cannot return DAM_SUCCESS_WITH_RESULT_PENDING for UPDATE, INSERT, and DELETE statements.
Cause: The ipExecute function returned DAM_SUCCESS_WITH_RESULT_PENDING for an UPDATE, INSERT, or a DELETE statement. The ipExecute function can return this only for SELECT statements.
Action: Correct the ipExecute function in the IP to not return DAM_SUCCESS_WITH_RESULT_PENDING for UPDATE, INSERT, or DELETE statements.
|
|
|
10362
|
ORDER BY is not supported on LONG TYPES. XoType: <type>.
Cause: The SQL statement contained an ORDER BY clause that operated on Long types.
Action: Correct the SQL statement.
|
|
|
10363
|
Custom condition list not evaluated by IP.
Cause: The IP did not evaluate the custom conditions.
Action: Correct the IP to evaluate the custom conditions. For detailed information, refer to the section on using custom scalar functions in the OpenAccess SDK SQL Engine Programmer’s Reference for C/C++ or OpenAccess SDK SQL Engine Programmer’s Reference for Java.
|
|
|
10364
|
Unable to generate condition lists, Query has custom conditions.
Cause: The custom conditions list that the IP requested was not generated.
Action: Increase the normalization limit set by IP_INFO_COND_LIST_NORMALIZATION_LIMIT.
|
|
|
10365
|
Custom Scalars with JOIN expressions having OR operator are not supported.
Cause: A statement contained a custom scalar function in a JOIN expression that was not supported with the OR operator.
Action: Check your application. Correct the statement. Refer to the Programmer’s Reference for your API for the correct syntax for custom scalar functions.
|
|
|
10366
|
Custom Scalars in WHERE clause within an expression are not supported.
Cause: A statement contained a custom scalar function within an expression that was not supported.
Action: Check your application. Correct the statement. Refer to the Programmer’s Reference for your API for the correct syntax for custom scalar functions.
|
|
|
10367
|
Invalid syntax. Custom Scalar functionality is only supported on single column.
Cause: A statement contained a custom scalar function on zero or multiple columns. Custom scalar functions are only supported on a single column.
Action: Check your application. Correct the statement. Refer to the Programmer’s Reference for your API for the correct syntax for custom scalar functions.
|
|
|
10368
|
Invalid syntax. Custom Scalar in WHERE clause accepts only LITERAL values as arguments.
Cause: A custom scalar function was used with a non literal value as an argument.
Action: Check your application. Correct the statement. Refer to the Programmer’s Reference for your API for the correct syntax for custom scalar functions.
|
|
|
10369
|
Invalid syntax. Custom Scalars are not support in clause.
Cause: A custom scalar function was used in the specified clause. Custom scalar functions are not supported in SELECT, GROUP BY, HAVING, ORDER BY, or INSERT clauses.
Action: Check your application. Correct the statement. Refer to the Programmer’s Reference for your API for the correct syntax for custom scalar functions.
|
|
|
10370
|
Invalid syntax. Ambiguous column name: column.
Cause: A statement specified columns from different tables using ambiguous column names. For example, the column names may need to be qualified with the table name.
Action: Check your application. Correct the statement.
|
|
|
10371
|
Unsupported query syntax. TOP clause is not supported in UNION queries and subqueries.
Cause: A statement contained a TOP clause in a UNION clause or a subquery.
Action: Check your application. Correct the statement.
|
|
|
10372
|
Invalid value passed for column:{0}
Cause: The value passed for the column exceeds the column specification range.
Action: Check the value passed for the column.
|
|
|
10373
|
Unsupported query syntax. Set functions in RANK are not supported.
Cause: A statement contained a RANK with SET function.
Action: Check your application. Correct the statement.
|
|
|
10374
|
Invalid schema passed for column: {0} NUMERIC ({1}, {2}). Invalid precision. Invalid scale. Scale is greater than precision. Exceeds supported range.
Cause: There is an issue with the numeric column specification.
Action: Check the numeric column specification.
|
|
|
10375
|
Error occurred during arithmetic operation on NUMERIC data.
Cause: There is either an issue with numeric arithmetic or the result is out of range.
Action: Check the numeric value and the supported range.
|
|
|
10376
|
MINIMUM SCALE for NUMERIC,DECIMAL types is out of range.
Cause: The minimum scale value of the numeric data type is either less than zero or greater than 127.
Action: Check your application and correct the minimum scale of the numeric data type.
|
|
|
10378
|
Required memory is too large to allocate.
Cause: OpenAccess SDK is unable to allocate enough memory for sorting rows.
Action: Contact Progress DataDirect technical support.
|
|
|
10379
|
Error processing scalar function:%ls. Unsupported value type:%d for input field.
Cause: The value of the input column that is of long data type is not in the data chain format.
Action: Check the long data type column value that is exposed/added in the IP.
|
|
|
10388
|
Error reported by IP Interface
Cause: An internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
10389
|
Error reported by IP Interface
Cause: And internal error occurred.
Action: Contact Progress DataDirect technical support.
|
|
|
103XX
|
MINIMUM SCALE for NUMERIC, DECIMAL types is out of range.
Cause: Value specified for IP_INFO_MINIMUM_NUMERIC_SCALE is out of range.
Action: Check the value and the supported range.
|
|
|
103XX
|
Overflow occurred during an arithmatic operation on NUMERIC data.
Cause: Result is out of range.
Action: Check the value and the supoorted range.
|
|
|
21000
|
Cardinality violation
Single row select statement produces more than one row.
Cause: Nested query used is expected to return a single record.
Action: Check the query.
|
|
|
22000
|
Data exception.
Cause: The error message contains details of the cause.
Action: Check the specific error reported for corrective action.
|
|
|
22003
|
Numeric value out of range
Numeric value incompatible with conversion to Integer.
Numeric value incompatible with conversion to Small integer.
Numeric value incompatible with conversion to Unsigned integer.
Conversion from Integer to Unsigned integer is incompatible.
Integer value incompatible with conversion to Small integer.
Integer: value incompatible with conversion to Small integer.
Double value incompatible with conversion to integer.
Incompatible float sizes.
Cause: Data types are incompatible with conversion.
Action: Use the data type conversions supported by the driver.
|
|
|
24000
|
Invalid cursor state
SetCursorName: cursor is already open .
Pending results still exist.
Cursor is already open .
Pending results still exist .
Cursor is not open .
Cause: Cursor is already open or there are pending results when the operation is performed.
Action: Check the specific error reported. Use a valid sequence of operations.
|
|
|
25000
|
Invalid transaction state
Unable to PREPARE_TO_COMMIT transaction.
Unable to set information.
Cause: An invalid transaction state was detected. The database may have returned a failure for the PREPARE_TO_COMMIT operation or it returned an error for the special SET_INFO command.
Action: Check for any additional errors reported by the database and correct them.
|
|
|
25502
|
Transaction is still active.
Cause: Low-level error.
Action: Contact Progress DataDirect technical support.
|
|
|
25503
|
Transaction is rolled back.
Cause: Low-level error.
Action: Contact Progress DataDirect technical support.
|
|
|
26000
|
Invalid SQL statement identifier.
Cause: Low-level error.
Action: Contact Progress DataDirect technical support.
|
|
|
34000
|
Invalid cursor name.
Cause: Low-level error.
Action: Contact Progress DataDirect technical support.
|
|
|
40000
|
Transaction rollback.
Cause: The COMMIT operation caused a ROLLBACK.
Action: Contact Progress DataDirect technical support.
|
|
|
42000
|
Syntax error or access violation.
Cause: Low-level error.
Action: If problem occurs repeatedly, generate logs and contact Progress DataDirect technical support.
|
|
|
44000
|
WITH CHECK OPTION violation.
Cause: Low-level error.
Action: If problem occurs repeatedly, generate logs and contact Progress DataDirect technical support.
|
|