Service call 121 fatal error

service call 121 fatal error

Please contact customer support. RGEE Fatal error: high priority receive queue overrun. High priority receive queue in master module got overrun. This fatal error suggests that something is wrong on the network which is causing network packets to drop. The error which is captured in the. SMTP errors and reply codes ; An error of your mail server, often due to an issue of the local anti-spam filter. Contact your SMTP service provider to fix. service call 121 fatal error

Service call 121 fatal error - are

Fatal error: Uncaught Error: Class "SoapClient" not found

Hello I am trying to build with the UPS API for CANADA. The documentation is pretty rugged and i am having a hard time understanding it

My code is as follows:

and i am getting the following error:

Fatal error: Uncaught Error: Class "SoapClient" not found in C:\xampp\htdocs\upsapi\RatingPACKAGE\PACKAGEWebServices\CodeSamples\Rate\PHP\sprers.eu Stack trace: #0 {main} thrown in C:\xampp\htdocs\upsapi\RatingPACKAGE\PACKAGEWebServices\CodeSamples\Rate\PHP\sprers.eu on line

Any help would be greatly appreciated.

It appears soap client was not on server but I believe that is resolved as I am now getting

SoapFault Object ( [message:protected] => SOAP-ERROR: Parsing WSDL: Couldn't load from ' ' : failed to load external entity " " [string:Exception:private] => [code:protected] => 0 [file:protected] => C:\xampp\htdocs\upsapi\ShippingPACKAGE\PACKAGEWebServices\CodeSamples\Ship\PHP\sprers.eu [line:protected] => [trace:Exception:private] => Array ( [0] => Array ( [file] => C:\xampp\htdocs\upsapi\ShippingPACKAGE\PACKAGEWebServices\CodeSamples\Ship\PHP\sprers.eu [line] => [function] => __construct [class] => SoapClient [type] => -> [args] => Array ( [0] => [1] => Array ( [soap_version] => SOAP_1_1 [trace] => 1 ) ) ) ) [previous:Exception:private] => [faultstring] => SOAP-ERROR: Parsing WSDL: Couldn't load from ' ' : failed to load external entity " " [faultcode] => WSDL [faultcodens] => [faultactor] => [detail] => [_name] => [headerfault] => )

Fixing SQL Server fatal error

By: Manvendra Singh   

Im using your service + plugin, but lately we have been getting an error when saving the product page, when we checked the log, the error is coming from your plugin:

Fatal error: Uncaught Error: Call to undefined method Normalizer::isNormalized() in /home/techlabcoil/public_html/wp-content/plugins/cloudflare/vendor/symfony/polyfill-intl-idn/sprers.eu Stack trace: #0 /home/techlabcoil/public_html/wp-content/plugins/cloudflare/vendor/symfony/polyfill-intl-idn/sprers.eu(): Symfony\Polyfill\Intl\Idn\Idn::process(&#;sprers.eu&#;, Array, Object(Symfony\Polyfill\Intl\Idn\Info)) #1 /home/techlabcoil/public_html/wp-content/plugins/cloudflare/vendor/symfony/polyfill-intl-idn/bootstrapphp(): Symfony\Polyfill\Intl\Idn\Idn::idn_to_ascii(&#;sprers.eu&#;, Array, 1, NULL) #2 /home/techlabcoil/public_html/wp-content/plugins/cloudflare/src/WordPress/sprers.eu(18): idn_to_ascii(&#;sprers.eu&#;, 0, 1) #3 /home/techlabcoil/public_html/wp-content/plugins/cloudflare/src/WordPress/sprers.eu(): CF\WordPress\WordPressClientAPI->getZoneTag(&#;sprers.eu&#;) #4 /home/techlabcoil/public_html/wp-content/plugins/cloudflare/src/WordPress/sprers.eu(): CF\WordPress\Hooks->purgeCacheByRelevantURLs() #5 /home/techlabcoil/public_html/wp-includes/sprers.eu(): CF\WordPress\Hooks->purgeCacheOnPostStatusChange(&#;publish&#;, &#;publish&#;, Object(WP_Post)) #6 /home/techlabcoil/public_html/wp-includes/sprers.eu(): WP_Hook->apply_filters(Array, Array) #7 /home/techlabcoil/public_html/wp-includes/sprers.eu(): WP_Hook->do_action(Array) #8 /home/techlabcoil/public_html/wp-includes/sprers.eu(): do_action(&#;transition_post&#;&#;, &#;publish&#;, &#;publish&#;, Object(WP_Post)) #9 /home/techlabcoil/public_html/wp-includes/sprers.eu(): wp_transition_post_status(&#;publish&#;, &#;publish&#;, Object(WP_Post)) #10 /home/techlabcoil/public_html/wp-includes/sprers.eu(): wp_insert_post(Array, false, true) #11 /home/techlabcoil/public_html/wp-admin/includes/sprers.eu(): wp_update_post(Array) #12 /home/techlabcoil/public_html/wp-admin/sprers.eu(): edit_post() #13 {main} thrown in /home/techlabcoil/public_html/wp-content/plugins/cloudflare/vendor/symfony/polyfill-intl-idn/sprers.eu on line

18 Reference Guide to BRM Error Codes

PIN_ERR_NONE

0

No error.

This error code indicates a general condition, not a specific error. Some BRM routines use this error code to indicate that the routine was successful.

PIN_ERR_NO_MEM

1

There was insufficient memory to complete the attempted operation.

Check system memory. Also check the shmsize and bigsize values in the Data Manager configuration file (sprers.eu). If you see this error code with a custom application, check for memory leaks.

Solaris: Check that the shared memory for the system is at least as great as the shared memory set for BRM.

PIN_ERR_NO_MATCH

2

BRM could not find the value it was looking for.

From the Data Manager, this error indicates a bad search template from the qm_flist.

From the SDK FM, this error means that the FM cannot find the object it was told to modify.

PIN_ERR_NOT_FOUND

3

BRM could not find a value.

This error code does not always indicate an error. For example, some opcodes look for a value in the configuration file, but if the value is not there, a default value can be used.

PIN_ERR_BAD_ARG

4

A required field in an flist is incorrect.

This is always a serious error because the system will not work until the argument is fixed. The problem is usually a programming or data entry error.

PIN_ERR_BAD_XDR

5

The application unexpectedly lost the connection to the BRM database.

Usually, this error means that the connection to the network was lost. If the network is working correctly, the BRM server might have stopped working. Look for errors in the CM log file. Also check for CM or DM core files.

PIN_ERR_BAD_FIRST_READ

6

No longer used.

PIN_ERR_BAD_READ

7

BRM could not read from the network or some other IO device, probably because the connection was cut off unexpectedly.

PIN_ERR_NO_SOCKET

8

BRM could not create a socket.

The machine or process might be overloaded and have reached a limit on socket/file descriptors. The networking part of the operating system might have failed.

Try restarting the machine. If that does not work, report the problem to the OS vendor.

PIN_ERR_BAD_TYPE

9

BRM encountered an erroneous field or object type.

This error usually results from programming errors in custom applications and FMs, but the error might also result from a mismatch between a field and its corresponding field type.

If seen when pcpxdr_fld_list is called, it means a down-level version of the libraries saw incompatible wire protocols or a new field type.

PIN_ERR_DUPLICATE

10

BRM could not create a storable object because the requested ID is already used by another object.

PIN_COMPARE_EQUAL

11

This code does not indicate an error. The billing FM uses this code for internal operations.

PIN_COMPARE_NOT_EQUAL

12

This code does not indicate an error. The billing FM uses this code for internal operations.

PIN_ERR_MISSING_ARG

13

A required argument is missing.

If the log file does not indicate the field, see the specification for the opcode.

PIN_ERR_BAD_POID_TYPE

14

BRM encountered an erroneous object type.

This is similar to error 9, but it is more specific to object type. For example, BRM was expecting an account object but encountered an event object.

PIN_ERR_BAD_CRYPT

15

Packet header failed encryption/decryption. Possible corruption of data.

PIN_ERR_BAD_WRITE

16

Error while attempting to send data on the IP socket.

PIN_ERR_DUP_SUBSTRUCT

17

Information not available.

PIN_ERR_BAD_SEARCH_ARG

18

A required field in a search template or flist is incorrect.

This is always a serious error because the system will not work until the argument is fixed. The problem is usually a programming or data entry error.

PIN_ERR_BAD_SEARCH_ARG_RECID

19

Invalid automatic number identification (ANI) in the search operation.

PIN_ERR_DUP_SEARCH_ARG

20

There are duplicate entries in the search argument list.

PIN_ERR_NONEXISTANT_POID

21

BRM cannot find the storable object in the database.

PIN_ERR_POID_DB_IS_ZERO

22

The database number is specified as zero.

Make sure the routine is passing a valid database number that matches the number in the configuration file.

PIN_ERR_UNKNOWN_POID

23

The POID does not contain valid information, or the format is incorrect.

PIN_ERR_NO_SOCKETS

24

BRM could not create a socket.

The machine or process might be overloaded and have reached a limit on socket/file descriptors. The networking part of the operating system might have failed.

Try restarting the machine. If that does not work, report the problem to the OS vendor.

PIN_ERR_DM_ADDRESS_LOOKUP

_FAILED

25

The Connection Manager could not find the Data Manager.

The Bind (or DNS) service is pointing to the wrong TCP/IP address, or the network is having problems.

Try pinging the DM to verify the network connection. Check the DM pointer specified in the configuration file for the CM.

PIN_ERR_DM_CONNECT_FAILED

26

BRM could not connect to the Data Manager.

The configuration file for the CM might be pointing to the wrong DM, or the DM might not be running.

PIN_ERR_NAP_CONNECT_FAILED

27

An application could not connect to the Connection Manager.

The configuration file for the application might be pointing to the wrong CM. The CM might not be running, or there might not be any more available connections. Also check for network errors between the application and the CM. For example, no more TCP sockets might be available on the client or CM machine.

PIN_ERR_INVALID_RECORD_ID

28

The ID of the specified element in the array is not valid.

The specified ID might be greater than the maximum record ID.

PIN_ERR_STALE_CONF

29

BRM found outdated values in sprers.eu entries.

PIN_ERR_INVALID_CONF

30

Configuration data is missing or in an invalid format in the sprers.eu files.

PIN_ERR_WRONG_DATABASE

31

The database number in the POID is not valid.

PIN_ERR_DUP_ARG

32

The flist has duplicate fields or elements.

PIN_ERR_BAD_SET

33

BRM could not assign a storable object ID.

PIN_ERR_BAD_CREATE

34

A routine could not create an object.

PIN_ERR_BAD_FIELD_NAME

35

Mapping error from field home to type.

PIN_ERR_BAD_OPCODE

36

Undefined opcode used.

PIN_ERR_TRANS_ALREADY_OPEN

37

An application attempted to open a transaction when one was already open on the same storable object.

This error usually results from a programming error in a custom application or FM. The error sometimes appears in a series of cascading errors; look for a predecessor error.

PIN_ERR_TRANS_NOT_OPEN

38

An application attempted to commit or stop a transaction, but none had been opened.

This error usually results from a programming error in a custom application or FM. The error sometimes shows up in a series of cascading errors; look for a predecessor error.

PIN_ERR_NULL_PTR

39

A routine could not get a value because it was set to ”null”.

This error usually results from a programming error in a custom application or FM.

PIN_ERR_BAD_FREE

40

A routine tried, but failed, to free memory that was no longer needed.

This error usually results from a programming error in a custom application or FM. This problem might cause memory leaks.

PIN_ERR_FILE_IO

41

Error while attempting to do an IO operation on a file.

PIN_ERR_NONEXISTANT_ELEMENT

42

The array in the specified storable object does not have the specified element.

PIN_ERR_STORAGE

43

The database returned an error.

Check the Data Manager log file for database-specific error messages. Also check the database server error logs.

PIN_ERR_TRANS_TOO_MANY_POIDS

44

BRM attempted transactions to too many Data Managers.

PIN_ERR_TRANS_LOST

45

The transaction was lost. The Data Manager failed during a transaction.

PIN_ERR_BAD_VALUE

46

BRM could not interpret data from the database.

The data is not valid in the current context, and BRM cannot resolve the conflict.

PIN_ERR_PARTIAL

47

When sending a batch of transactions to the credit card Data Managers, some of the credit cards were processed, but others were not.

PIN_ERR_NOT_YET_DONE

48

BRM has not yet completed an operation (such as an opcode or transaction).

This is typically an internal debugging error code that is not displayed.

PIN_ERR_STREAM_IO

49

The application encountered an error while sending data to or from the BRM database.

Usually, this error means that the connection to the network was lost. If the network is working correctly, the server might have stopped working. Look for errors in the CM log file. Also check for CM or DM core files.

PIN_ERR_STREAM_EOF

50

The application unexpectedly lost the connection to the BRM database.

Usually, this error means that the connection to the network was lost. If the network is working correctly, the server might have stopped working. Look for errors in the CM log file. Also check for CM or DM core files.

PIN_ERR_OP_NOT_OUTSTANDING

51

No operation is in progress under this context.

PIN_ERR_OP_ALREADY_BUSY

52

There is an operation already in progress within this context.

PIN_ERR_OP_ALREADY_DONE

53

Certain operations can be done only once. This error indicates that an operation of this type is being attempted a second time.

PIN_ERR_NO_DATA_FIELDS

54

The Data Manager received an flist with no data fields.

Check the input flist.

PIN_ERR_PROHIBITED_ARG

55

BRM could not create an object because one or more values were invalid or fields do not allow updating.

PIN_ERR_BAD_LOGIN_RESULT

56

The application could not connect to the CM.

Check the login name and password.

PIN_ERR_CM_ADDRESS_LOOKUP

_FAILED

57

The application could not find the computer running the CM. The Bind (or DNS) service is pointing to the wrong TCP/IP address, or the network is having problems.

Try pinging the CM to verify the network connection. Check the CM host name specified in the configuration file for the application.

PIN_ERR_BAD_LOGIN_REDIRECT_INFO

58

The redirection information received from the CMMP is incorrect.

PIN_ERR_TOO_MANY_LOGIN

_REDIRECTS

59

Too many connect login redirects from the CMMP.

This error might have resulted from a loop in the configuration. Check the configuration files for the application, CM, and DM.

PIN_ERR_STEP_SEARCH

60

The step search operation did not find an expected STEP_NEXT or STEP_END.

PIN_ERR_STORAGE_DISCONNECT

61

BRM lost the connection with the database during the middle of a transaction and could not reestablish the connection.

See "Configuring Oracle Databases" in BRM Installation Guide.

PIN_ERR_NOT_GROUP_ROOT

62

Not the root of a group.

PIN_ERR_BAD_LOCKING

63

Error while attempting to lock/unlock a heap storage.

PIN_ERR_AUTHORIZATION_FAIL

64

No information available.

PIN_ERR_NOT_WRITABLE

65

Tried to write a field that cannot be modified.

PIN_ERR_UNKNOWN_EXCEPTION

66

Unknown C++ exception.

PIN_ERR_START_FAILED

67

BRM could not start the process.

PIN_ERR_STOP_FAILED

68

BRM could not stop the process.

PIN_ERR_INVALID_QUEUE

69

No information available.

PIN_ERR_TOO_BIG

70

No information available.

PIN_ERR_BAD_LOCALE

71

BRM does not understand the locale. Check the locale of the computer running the client application.

PIN_ERR_CONV_MULTIBYTE

72

A client application had a problem converting data from UTF8 format, as it is stored in the BRM database, to multibyte format. Either the client has the wrong locale or the data is corrupted.

PIN_ERR_CONV_UNICODE

73

A client application had a problem converting data from UTF8 format, as it is stored in the BRM database, into Unicode format. Either the client has the wrong locale or the data is corrupted.

PIN_ERR_BAD_MBCS

74

The input flist includes a string that is not in valid multibyte format.

PIN_ERR_BAD_UTF8

75

The input flist includes a string that is not in valid Unicode format.

PIN_ERR_CANON_CONV

76

No information available.

PIN_ERR_UNSUPPORTED_LOCALE

77

BRM does not support canonicalization for the locale of the client application.

PIN_ERR_CURRENCY_MISMATCH

78

A subordinate bill unit or sponsored account has a different account currency than the parent or sponsor account.

PIN_ERR_DEADLOCK

79

Two or more database sessions attempted to access the same database resource. Each session waits for another session to release locks on the resource. The database detects the deadlock and stops one of the session's operations. If you receive this error, retry the transaction or operation.

PIN_ERR_BACKDATE_NOT_ALLOWED

80

BRM cannot backdate the adjustment, write-off, or other transaction because the G/L report has already been posted.

PIN_ERR_CREDIT_LIMIT_EXCEEDED

81

No information available.

PIN_ERR_IS_NULL

82

The value is Null (not set).

PIN_ERR_DETAILED_ERR

83

A detailed error message uses an enhanced buffer (errbuf).

PIN_ERR_PERMISSION_DENIED

84

The attempted operation is not allowed; data is not viewable.

PIN_ERR_PDO_INTERNAL

85

An internal error occurred in the BRM data objects.

PIN_ERR_IPT_DNIS

86

The Dialed Number Identification Service (DNIS) is not authorized.

PIN_ERR_DB_MISMATCH

87

The database numbers do not match.

PIN_ERR_NO_CREDIT_BALANCE

88

No credit balance is available.

PIN_ERR_NOTHING_TO_BILL

89

There are no new items to bill.

PIN_ERR_MASTER_DOWN

90

The main BRM system is down.

PIN_ERR_OPCODE_HNDLR_INIT_FAI

91

The opcode handler initialization at JS failed.

PIN_ERR_STMT_CACHE

92

There is a problem with the statement cache.

PIN_ERR_CACHE_SIZE_ZERO

93

Tried to initialize cm_cache with zero size.

PIN_ERR_INVALID_OBJECT

94

The POID is invalid.

This error occurs when an object is accessed whose database_number field of the POID is NULL.

PIN_ERR_VALIDATE_ADJUSTMENT

95

The validate adjustment policy opcode fails.

PIN_ERR_SYSTEM_ERROR

96

A generic system error occurred while the application was running.

PIN_ERR_BILLING_ERROR

97

An error occurred during the billing run.

PIN_ERR_AUDIT_COMMIT_FAILED

98

Commit for the audit tables failed.

PIN_ERR_NOT_SUPPORTED

99

The operation is not supported.

PIN_ERR_INVALID_SER_FORMAT

The serialized format received from the database is incorrect.

PIN_ERR_READ_ONLY_TXN

Cannot insert or update in a read-only transaction.

PIN_ERR_VALIDATION_FAILED

Deals or plans validation failed.

PIN_ERR_PROC_BIND

The binding for the Procedure arguments failed.

PIN_ERR_PROC_EXEC

The procedure returned an application-specific error.

PIN_ERR_STORAGE_FAILOVER

An Oracle RAC failover message.

PIN_ERR_RETRYABLE

A failover error occurred and is retryable if needed.

PIN_ERR_NOT_PRIMARY

Not the primary instance.

PIN_ERR_TIMEOUT

Request timeout.

PIN_ERR_CONNECTION_LOST

The connection has been lost.

PIN_ERR_FEATURE_DISABLED

The feature is disabled.

PIN_ERR_INVALID_STATE

The state is invalid.

PIN_ERR_NO_SECONDARY

No secondary instance exists.

PIN_ERR_ACCT_CLOSED

The account is in the Closed state.

PIN_ERR_EM_CONNECT_FAILED

The connection between the CM and EM failed.

PIN_ERR_FAST_FAIL

A fast fail occurred in dual timeout.

PIN_ERR_BAD_ENC_SCHEME

The MD5 encryption scheme is configured; however, the AES encryption library is being used.

PIN_ERR_MAX_BILL_WHEN

The value in the bill_when field exceeds the maximum number of months allowed in billing cycles.

PIN_ERR_PERF_LIMIT_REACHED

The performance limit has been reached.

PIN_ERR_ACTIVE_NOT_READY

The TIMOS passive instance is switching over to active, but it is not active yet.

PIN_ERR_POID_ALREADY_LOCKED

The POID is already locked.

PIN_ERR_SERVICE_LOCKED

This error code is used by SOX.

PIN_ERR_XAER_RMFAIL

The extended architecture (XA) transaction resource manager (JCA Resource Adapter) is unavailable.

PIN_ERR_XAER_RMERR

An XA transaction resource manager (JCA Resource Adapter) error occurred in the transaction branch.

PIN_ERR_XAER_PROTO

An XA transaction protocol error has occurred; a routine was started in an improper context.

PIN_ERR_XAER_OUTSIDE

The resource manager (JCA Resource Adapter) is doing work outside the XA transaction.

PIN_ERR_XAER_NOTA

The global transaction ID (XID) for the XA transaction is invalid.

PIN_ERR_XAER_INVAL

An invalid argument was passed during the XA transaction.

PIN_ERR_XAER_DUPID

The global transaction ID (XID) for the XA transaction already exists.

PIN_ERR_XAER_ASYNC

An asynchronous operation is outstanding.

PIN_ERR_XA_RDONLY

The XA transaction branch was read-only and has been committed.

PIN_ERR_XA_RETRY

The routine returned without having any effect. It can be reissued.

PIN_ERR_XA_HEURHAZ

The XA transaction branch might have been manually committed to the BRM database. Some parts of the transaction are known to have been manually committed or rolled back, but the outcome of the entire transaction is unknown.

PIN_ERR_XA_HEURCOM

The XA transaction branch has been manually committed to the BRM database.

BRM returns this error code to JCA Resource Adapter during the recovery process of a failed two-phase commit transaction.

PIN_ERR_XA_HEURRB

The XA transaction branch has been manually rolled back.

BRM returns this error code to JCA Resource Adapter during the recovery process of a failed two-phase commit transaction.

PIN_ERR_XA_HEURMIX

Part of the XA transaction branch has been manually committed to the BRM database, and part has been manually rolled back.

BRM returns this error code to JCA Resource Adapter during the recovery process of a failed two-phase commit transaction.

PIN_ERR_XA_RBCOMMFAIL

The XA transaction was rolled back because of a communications failure.

PIN_ERR_XA_RBDEADLOCK

The XA transaction was rolled back because a deadlock was detected.

PIN_ERR_XA_RBINTEGRITY

The XA transaction was rolled back because a condition that violates the integrity of the resource was detected.

PIN_ERR_XA_RBOTHER

The XA transaction was rolled back for a reason not specified by an error code in this table.

PIN_ERR_XA_RBPROTO

The XA transaction was rolled back because of a protocol error in the resource manager.

PIN_ERR_XA_RBROLLBACK

The XA transaction was rolled back for an unspecified reason.

PIN_ERR_XA_RBTIMEOUT

The XA transaction was rolled back because it timed out.

PIN_ERR_XA_RBTRANSIENT

The XA transaction was rolled back because of a brief malfunction. The transaction branch can be retried.

Fatal error when putting iOS app in the background #

(if anything is wrong with the way I'm doing this, please tell me: I am very new to programing in general and trying to report bugs to the community in particular).

This occurs when testing an iOS app made with Capacitor on the simulator of xCode.

The options used for camera-preview are:

cameraPreviewOptions: CameraPreviewOptions = {
position: 'rear',
enableHighResolution: true,
storeToFile: true,
parent: 'cameraPreview',
className: 'livePreview',
disableAudio: true
}

The app will crash when put into background if the plugin has been called at least once (in my case if the component using the plugin has been used).

In xCode the reported error reads as follows:

Following this error, I have made a fix pull request but it needs to be looked at to make sure everything I added there is necessary (as I am unsure about how everything works) Also I think we might need to add the same fix line 30 of the same file for other cases.

Service call 121 fatal error - think already

Error message list

Message
Error code
Description
Cover Name Open

Please See HELP For Details,

The indicated cover is open. Close the cover.
Outlet tray (Top cover); Front cover

Belt Unit Is Not Installed Correctly. Please Reset

Please See HELP For DetailsThe belt unit is not properly installed. Please reinstall the belt unit.
To install the belt unit, see "Replacing the belt unit".

Waste Toner Box Is Not Installed Correctly Because The Cover Is Open. Please Reset

Please See HELP For DetailsThe waste toner box is not properly installed. Please reinstall the waste toner box.
To replace the waste toner box, see "Replacing the black(K) toner cartridge and the waste toner box".Toner Cartridge Is Not Installed
Check All Toner Cartridges Are Installed Correctly. Please See HELP For DetailsOne of the four color toner cartridges is not properly installed. Please reinstall the toner cartridge that is not properly installed.
To install the toner cartridge, see "Replacing the black(K) toner cartridge and the waste toner box" or "Replacing the toner cartridge (C/M/Y)".Color Name Image Drum Is Not Installed Correctly. Please Reset

Please See HELP For Details, , , The image drum of the displayed color is not properly installed. Please reinstall the image drum.
To install the image drum, see "Replacing the image drum".
Yellow; Magenta; Cyan; BlackFuser Unit Is Not Installed Correctly. Please Reset

Please See HELP For DetailsThe fuser unit is not properly installed. Please reinstall the fuser unit.
To install the fuser unit, see "Replacing the fuser unit".
If the error persists, replace the fuser unit with a new one.Fuser Unit Is Not Installed Correctly. Reset Fuser Unit

Please See HELP For DetailsThe fuser unit is not properly installed. Please reinstall the fuser unit.
To install the fuser unit, see "Replacing the fuser unit".
If the error persists, replace the fuser unit with a new one.Color Name Image Drum End Of Life. Replace With A New Color Name Image Drum

Please See HELP For Details, , , The image drum of the displayed color has reached the end of its service life. You can continue printing for a while by opening and closing the front cover, but please replace the image drum with a new one promptly.
To replace the image drum, see "Replacing the image drum".
Yellow; Magenta; Cyan; BlackFuser Unit End Of Life. Replace With A New Fuser Unit

Please See HELP For DetailsThe fuser unit has reached the end of its service life. Please replace the fuser unit with a new one.
You can continue printing for a while by opening and closing the front cover.
To replace the fuser unit, see "Replacing the fuser unit".Belt Unit End Of Life. Replace With A New Belt Unit

Please See HELP For DetailsThe belt unit has reached the end of its service life. Please replace the belt unit with a new one.
You can continue printing for a while by opening and closing the front cover.
To replace the belt unit, see "Replacing the belt unit".

Belt Unit End Of Life. Replace With A New Belt Unit

Please See HELP For DetailsThe waste toner area of the belt unit is full. Please replace the belt unit with a new one.
To replace the belt unit, see "Replacing the belt unit".

Waste Toner Full. Install New Waste Toner Box

Please See HELP For Details

See "Replacing the black(K) toner cartridge and the waste toner box".

Waste Toner Transfer Error. Please Reset Waste Toner Box

Please See HELP For Details

See "Replacing the black(K) toner cartridge and the waste toner box".Paper Size Error. Reset Paper In Tray Name

Please See HELP For DetailsMultiple sheets of paper are fed at a time from the displayed tray. Or, the paper of a size different from the paper size setting of the tray is fed.
Remove the jammed paper.
Remove the paper temporarily from the tray when multiple sheets of paper are fed at a time. Shuffle the paper well, horizontally align the edge of paper, and load the paper in the tray again.
Otherwise, check the size of paper to print on and the paper size setting of the tray, and match the paper settings.
Multiple Sheets Of Paper Have Been Fed. Reset Paper In Tray Name

Please See HELP For DetailsMultiple sheets of paper are fed at a time from the displayed tray. Or, the paper of a size different from the paper size setting of the tray is fed.
Remove the jammed paper.
Remove the paper temporarily from the tray when multiple sheets of paper are fed at a time. Shuffle the paper well, horizontally align the edge of paper, and load the paper in the tray again.
If overlapping paper is not fed, check the size of the paper to print on and the paper size setting of the tray, and match the paper settings.Printing Stopped Because The Rear Output Tray Is Opened During The Printing Job. Please Remove Paper

Please See HELP For DetailsOpen the front cover, and remove the paper left in the machine if any. Then, close the front cover.Rear Output Tray Open. Duplex Not Available

Please See HELP For DetailsPlease close the rear output tray.Color Name Toner Is Empty
Replace With A New Toner Cartridge. Please See HELP For Details, , The toner of the displayed color is empty.
You can continue using the device for a while by opening and closing the front cover, but the image drum may be damaged. Therefore, please replace the toner cartridge with a new one promptly. To replace the toner cartridge, see "Replacing the toner cartridge (C/M/Y)".
Yellow; Magenta; Cyan

Black(K)Toner Is Empty
Replace With A New Toner Cartridge And A New Waste Toner Box At The Same Time. Please See HELP For Details

The black (K) toner is empty.
You can continue using the device for a while by opening and closing the front cover, but the image drum may be sprers.euore, please replace the toner cartridge with a new one promptly. To replace the toner cartridge, see "Replacing the black(K) toner cartridge and the waste toner box".

Check That The Waste Toner Box Has Been Replaced, And Press OK

Please See HELP For Details

If you have not replaced the waste toner box, press «OK».
If you have already replaced it, just press «OK».

Press OK After Replacing The Black(K) Toner Cartridge

Please See HELP For Details

Replace the black(K) toner and press «OK».

Printing Data Is Large. Memory Is Not Enough

Press OK To Hide This Message. Please See HELP For DetailsThe memory is insufficient.
Print again after lowering the printing quality in the printer driver.No Cassette In Tray Name. Remove The Tray And Re-insert

Please See HELP For Details, , , , , , The printing has stopped because the displayed paper cassette is not properly installed.
Pull the paper cassette out, and insert it back.
, Tray 1; , Tray 2; , Tray 3; Tray4Data (Media Size, Media Type) Doesn't Match Paper In Tray Name
Press OK To Continue Printing. Please See HELP For Details, , , , The size of paper loaded in the displayed tray does not match the size of paper you are trying to print on. Check the paper size settings of the application you are trying to print from and the paper size settings of the tray, and match the paper size settings.
If the paper size can be loaded in portrait/landscape, please note the vertical/horizontal orientation.
MP tray; Tray 1; Tray 2; Tray 3; Tray 4No Paper In Tray Name. Set Media Size

Please See HELP For DetailsThere is no paper in the indicated tray.
Please load paper.
MP trayNo Paper In Tray Name.
Set Media Size. Please See HELP For Details, , , There is no paper in the indicated tray.
Please load paper.
Tray 1; Tray 2; Tray 3; Tray 4Wireless Settings Are Incomplete

Press OK To Hide This Message. Please See HELP For DetailsThe wireless LAN settings are not correct.
Please reset the wireless LAN from the beginning. For details, see "Connecting via a wireless LAN".
If the problem still persists, initialize the network settings and reset the wireless LAN settings. To initialize the network settings, see "Initializing network settings".Not Connected To Wireless Access Point

Press OK To Hide This Message. Please See HELP For DetailsNot connected to the wireless LAN access point. Or, the wireless communication may be poor.
Check that the power of the wireless LAN access point is turned on.
Check that the wireless LAN settings are correct.
For details, see "Connecting via a wireless LAN".Wireless Startup Failed

Press OK To Hide This Message. Please See HELP For DetailsRestart this machine.
If the problem still persists even after the reboot, power off this machine and check that the model name of the wireless LAN module is applicable to this machine.
If the model name is incorrect, replace the wireless LAN module with the one suitable for this machine.
If the model name is correct, consult your dealer.Receiving Data Timeout

Press OK To Hide This Message. Please See HELP For Details

The data could not be received within the correct time.
When the print result is not as good as expected, extend the time for network timeout. The factory default setting is 90 seconds.
Press the scroll buttons on the operator panel several times to change the settings in [Menus] - [System Setup] - [Timeout InJob].

Image Drum Sensor Error. Check And Reset Color Name Image Drum

Please See HELP For Details, , , A sensor error has occurred to the image drum of the indicated color.
Please reinstall the image drum. To install the image drum, see "Replacing the image drum".
If the error persists, contact your dealer.
Yellow; Magenta; Cyan; BlackColor Name Toner Cartridge Is Not Installed Correctly
Reset It Correctly. Please See HELP For Details, , , The toner cartridge of the displayed color is not installed properly. Reinstall the toner cartridge. To install the toner cartridge, see "Replacing the black(K) toner cartridge and the waste toner box" or "Replacing the toner cartridge (C/M/Y)".
Yellow; Magenta; Cyan; Black

Color Name Toner Cartridge Is Not Installed Correctly
Reset It Correctly. Please See HELP For Details

The above message has been displayed multiple times.

Change the settings to the following: Moisture Control: Mode 2; Quiet Mode: On.
To print with low toner consumption, please restore the settings. (The factory default settings are as follows: Moisture Control: Off; Quiet Mode: Off)

Color Name Image Drum End Of Life. Replace With A New Color Name Image Drum

Please See HELP For Details, , , The image drum of the displayed color has reached the end of its service life.
Please replace the image drum with a new one.
To replace the image drum, see "Replacing the image drum".
Yellow; Magenta; Cyan; BlackColor Name Image Drum End Of Life. Replace With A New Color Name Image Drum

Press OK to ignore service life and continue printing. Please See HELP For Details, , , The image drum of the displayed color has reached the end of its service life.
Please replace the image drum with a new one. You can continue printing for a while by pressing «OK» on the operator panel, but the print quality is not guaranteed.
To replace the image drum, see "Replacing the image drum".
Yellow; Magenta; Cyan; BlackFuser Unit Is Not Installed Correctly. Or The Handle Of Fuser Is In Standing Position

Please See HELP For DetailsThe fuser unit is not properly installed. Or, the handle of the fuser unit is not locked.
Please reinstall the fuser unit. To install the fuser unit, see "Replacing the fuser unit".Color Name Toner Cartridge Is Not Installed
Please See HELP For Details, , , The toner cartridge of the displayed color is not installed.
Install the toner cartridge. To install the toner cartridge, see "Replacing the black(K) toner cartridge and the waste toner box" or "Replacing the toner cartridge (C/M/Y)".
Yellow; Magenta; Cyan; BlackNon Recommended Color Name Toner
Please See HELP For Details, , , , , , , , , , , , , , , , The toner cartridge of the displayed color is not optimal for this machine. It is recommended to use the toner cartridge that is optimal for this machine.

, , , Yellow;
, , , Magenta;
, , , Cyan;
, , , , Black

Paper Jam Occurred. Paper Jam Number Place(s). Remove The Paper

Please See HELP For Details, , , , , , , , , , , ,

A paper jam has occurred.
Multiple sheets of paper remain inside this machine. When the scroll button on the operator panel is pressed, the lamp for the place where paper is jammed blinks. Remove all the paper from where the lamp blinks.
For how to clear paper jams, see "When paper is jammed".

Please Change Paper In MPTray
Media Size
Media Type

Press OK To Start Printing. Please See HELP For DetailsThe paper loaded in the MP tray does not match the paper you are trying to print on. Check the paper settings of the application you are trying to print from and the paper settings of the MP tray, and match the paper settings.Please Change Paper In Tray Name
Confirm Media Size, Media Type Is Set And Then Press OK. Please See HELP For Details, , , The paper loaded in the displayed tray does not match the paper you are trying to print on. Check the paper settings of the application you are trying to print from and the paper settings of the tray, and match the paper settings.
Tray 1; Tray 2; Tray 3; Tray 4Printing Stopped Because Color Name Image Drum End Of Life. Replace With A New Color Name Image Drum

Please See HELP For Details, , , The printing has stopped because the image drum of the displayed color has reached the end of its service life.
Please replace the image drum with a new one. To replace the image drum, see "Replacing the image drum".
Yellow; Magenta; Cyan; BlackNon Recommended Belt Unit

Please See HELP For Details, , , The belt unit is not optimal for this machine. It is recommended to use the belt unit that is optimal for this machine.Belt Unit Not Installed

Please See HELP For DetailsThe belt unit is not properly installed.
Remove the belt unit and install it properly. To replace the belt unit, see "Replacing the belt unit".Color Name Image Drum Is Not Installed

Please See HELP For Details, , , The image drum of the displayed color is not properly installed.
Please reinstall the image drum. To install the image drum, see “Replacing the image drum".
Yellow; Magenta; Cyan; BlackNon Recommended Fuser Unit

Please See HELP For Details, , , , The fuser unit is not optimal for this machine. It is recommended to use the fuser unit that is optimal for this machine.Fuser Unit Not Installed

Please See HELP For DetailsThe fuser unit is not properly installed in this machine.
Please reinstall the fuser unit. To replace the fuser unit, see "Replacing the fuser unit".Non Recommended Color Name Image Drum

Please See HELP For Details, , , , , , , , , , , , , , , The image drum of the displayed color is not optimal for this machine. It is recommended to use the image drum that is optimal for this machine.

, , , Yellow;
, , , Magenta;
, , , Cyan;
, , , Black

Caution: Non-Genuine consumable detected. Check User's Manual "Trouble Shooting" to restore machine operationYou can use any consumables/maintenance parts, but the print quality may be lowered and the optimum performance may not be obtained.
If the use of non-genuine consumables/maintenance parts causes damage to the product or results in your product not functioning to its full specification, such damage or effects on the product are not covered by warranty.
When you understand the above points and use non-genuine consumables/maintenance parts, follow the procedure below.
  1. Power off the main unit.
  2. Power on this machine while pressing «CANCEL» on the operator panel.
  3. When [Ready To Print] appears, release «CANCEL».
The above operation will be recorded inside this machine.Error While Initializing Settings

Press OK To Hide This Message

The initial value set with the NFC Setting Tool is not properly reflected in the device settings. Please check a setting value.

Power Off and Wait for a while.

Condensing Error

Fatal

Condensation has occurred inside this machine.
Turn off the power, and then turn the power back on after a while.
If the same error message is displayed, contact your dealer.Recovered from the error nnn

Print again if the printing result does not come as expected
Press OK To Hide This Message-An error has occurred inside this machine, and the machine has restarted. Check that the print result comes as expected, since the machine may restart during printing.
Print again if the printing result does not come as expected.Service Call
nnn:Error-

An error has occurred inside this machine.
Please contact your dealer.

Communication Error-An error has occurred in this machine. Restart this machine.
If the error persists, contact your dealer.Detected An Abnormality Of Internal Database
The Data Must Be Deleted
After Pressing [OK], The Data Will Be Deleted, And Then Reboot-An error has occurred in the internal database of this machine. Press «OK» on the operator panel to delete the database and restart this machine.Language Change Failed. Error num: Code-Failed to change the display language on the display.
Restart this machine, and reset the language setting.Firmware Update Error. Perform Firmware Update Again

If The Same Error Message Appears, Please Contact Our Customer Service Center-Firmware update has failed.
Please update the firmware again. For details, see "Firmware update".PU Flash Error-An error has occurred in this machine.
Please contact your dealer. Memory Is Not Enough. Please Reduce Resolution Or Finish The Function

Press OK To Hide This Message-

The memory is insufficient.
Print again after lowering the printing quality in the printer driver.

Manual Printing. Set Media Size In MPTray

Press OK To Start Printing-The print mode has been specified in which paper is loaded in the MP tray and fed one by one.
Load proper paper in the MP tray, and press «OK» on the operator panel.
If you are printing a multi-page document, the same massage appears each time after one page is printed. Press «OK» each time.Install New Image Drum. For Maximum Performance Always Use OKI Original-The image drum of the displayed color has reached the end of its service life. Please replace the image drum with a new one.
It is recommended to use the image drum that is optimal for this machine.Color Name Toner Empty.
For Maximum Performance Always Use OKI Original.-The toner of the displayed color is empty.
Please replace the toner cartridge with a new one.
It is recommended to use the toner cartridge that is optimal for this machine.
Can Not Read The File

Press OK To Hide This Message-Canceled because the USB memory is unplugged during printing from the USB memory.
To print it again, plug the USB memory in this machine.
Color Name Image Drum Sensor Error. Search Keyword: P-The image drum of the displayed color is not properly installed in this machine.
Please reinstall the image drum of the displayed color.
Color Name Image Drum Near Life. Search Keyword: P-The image drum is approaching its service life.
Please prepare a new image drum.
After the message of replacement is displayed, please replace it with a new one.
Color Name Image Drum Life. Print Quality Not Guaranteed. Search Keyword: P-

The image drum of the displayed color has reached the end of its service life.
Print quality is not guaranteed. Please replace the image drum with a new one as soon as possible. To replace the image drum, see "Replacing the image drum".


Color Name Image Drum Life. Search Keyword: P-The image drum of the displayed color has reached the end of its service life.
Please replace the image drum with a new one. To replace the image drum, see "Replacing the image drum".
Color Name Image Drum Life. Pages Pages Left. Search Keyword: P-The image drum of the displayed color has reached the end of its service life.
Unable to print after the displayed number of pages. Please replace the image drum with a new one as soon as possible.
To replace the image drum, see "Replacing the image drum".
Color Name Toner Not Installed. Search Keyword: P-The toner cartridge of the displayed color is not installed.
Please install the toner cartridge. To install the toner cartridge, see "Replacing the black(K) toner cartridge and the waste toner box" or "Replacing the toner cartridge (C/M/Y)".
Color Name Toner Empty. Search Keyword: P-The toner of the displayed color is empty.
Please replace the toner cartridge with a new one.
Replace The black(K) Toner Cartridge And Waste Toner Box At The Same Time. Search Keyword: P-The black(K) toner is empty.
Replace the black(K) toner cartridge and the waste toner box with new ones.
Color Name Toner Empty. Search Keyword: P-The toner of the displayed color is empty.
Please replace the toner cartridge with a new one.
Color Name Toner Low. Search Keyword: P-The toner of the displayed color is low. Please prepare a new toner cartridge.
After the message of replacement is displayed, please replace it with a new one.
Tray Name Empty-There is no paper in the indicated tray.
Please load paper.
Tray Name Cassette Missing-The displayed tray is not properly installed.
Please install the tray.
E-mail Receiving Has Been Cancelled

Press OK To Hide This Message-The e-mail printing is canceled.
The file attached to the e-mail is canceled under the following conditions.
  1. The format is not PDF, JPEG or TIFF
  2. No file is attached
  3. The size exceeds 8 MB
Check the file format and size of the attached file.
IPv4 Address Is Conflicted
Change IPv4 Address-The IPv4 Address conflicts with that of another machine.
Please change the IPv4 address.
Getting Target IP Failed. Please Check DHCP Settings-The DHCP server was not detected.
Check that the DHCP server is connected to the same network of this machine.
Error PDF

Press OK To Hide This Message-Unable to print because an error has occurred to the PDF file you tried to print.
Print again by using the printer driver from the application.
PDF Cache Write Error

Press OK To Hide This Message-Failed to cache the PDF file.
Print again after increasing the free space of the flash memory.
PDL Error Occurred-A PDL error has occurred.
Press «OK» to clear the error display.
No Communication With The SNTP Server-

Failed to retrieve the time from the SNTP server.
Press the scroll buttons on the operator panel several times to check that the setting of [SNTP server] is correct in [Admin Setup] - [Time Setup].


USB Hub Unsupported

Please Detach It-A USB hub which is not applicable to this machine is connected.
Please detach the USB hub.
Incompatible USB Device Connected

Please Detach It-Failed to recognize the USB device.
Please re-connect the USB device.
Color Toner Empty. Job Cancelled

Press OK To Hide This Message-Printing of the received color data is canceled because the color toner is empty.
Please replace the empty toner cartridge with a new one.
Color Restricted. Job Rejected

Press OK To Hide This Message-The print data from an user unauthorized to print in color was deleted.
To print in color, contact the administrator of this machine.
Color Restricted. Mono Printed

Press OK To Hide This Message-The print data from an user unauthorized to print in color was printed in mono.
To print in color, contact the administrator of this machine.
Color Name Non Recommended Image Drum Detected. Search Keyword: P-The image drum of the displayed color is not optimal for this machine.
It is recommended to use the image drum that is optimal for this machine.
Color Name Non Recommended Toner Detected. Search Keyword: P-The toner cartridge of the displayed color is not optimal for this machine.
It is recommended to use the toner cartridge that is optimal for this machine.
Non Recommended Belt Unit. Search Keyword: P-The belt unit is not optimal for this machine.
It is recommended to use the belt unit that is optimal for this machine.
Non Recommended Fuser Unit. Search Keyword: P-The fuser unit is not optimal for this machine.
It is recommended to use the fuser unit that is optimal for this machine.
Job Log Database Error
Contact The Device Administrator
Press OK To Hide This Message-A database access error has occurred to writing or reading of print data logs. Turn off this machine and then turn it back on. If the same error message is displayed again, contact your dealer.
Decode Error Occurred

Press OK To Hide This Message-Unable to print because an error has occurred to the image data.
Please check the image data.
Password Required To Print

Press OK To Hide This Message-

Printing restrictions have been imposed on the PDF file. Please input the password required to print.


Invalid Password

Press OK To Hide This Message-Unable to print because the password set in the PDF file does not match the password you input.
Please input the correct password.
File System Operation Failed <nnn>

Press OK To Hide This Message-A file system error has occurred.
Press «OK» on the operator panel to hide the message.
Belt Unit Near Life. Search Keyword: P-The belt unit is approaching the end of its service life.
Please prepare a new belt unit.
After the message of replacement is displayed, please replace it with a new one.
Change Belt Unit. Search Keyword: P-The belt unit has reached the end of its service life.
Please replace the belt unit with a new one. To replace the belt unit, see "Replacing the belt unit".
Error Postscript-An error has occurred to Postscript data.
Please check the print result.
If there is a problem with the print result, print again.
The problem may be solved if you select [Optimize for Portability] in the Postscript output option of the PS printer driver.
Log Buffer Is Full. Job Rejected

Press OK To Hide This Message-

The print data was deleted because the log buffer is full.
Please contact the printer administrator and delete the log.


Print Restricted. Job Rejected

Press OK To Hide This Message-The print data from an user unauthorized to print was deleted.
To print, contact the administrator of this machine.
Job Type Restricted
Job Rejected
Press OK To Hide This Message-The print data was canceled because only Private Print is enabled with restrictions.
Select Private Print from Job Type in the printer driver. See "Printing with print data encrypted and password set (Private Print)".
Expired Saved Files Have Been Deleted

Press OK To Hide This Message-The private print document whose retention date has passed was deleted.


NFC Unit Error. NFC Function Is Not Available

Press OK To Hide This Message

-

An error has occurred to the NFC unit.
NFC-specific functions are not available.
Power off/on this machine.

You can hide this message by selecting [Disable] for [Admin Setup] - [Others Setup] - [NFC Setup].


Incompatible USB Device Connected

Please Detach It-A USB device that is not supported by this machine is connected.
Please detach the USB device.
Fuser Unit Near Life. Search Keyword: P-The fuser unit is approaching the end of its service life.
Prepare a new fuser.
After the message of replacement is displayed, please replace it with a new one.
Change Fuser Unit. Search Keyword: P-The fuser unit has reached the end of its service life.
Please replace the fuser unit with a new one. To replace the fuser unit, see "Replacing the fuser unit".
Waste Toner Near Full. Search Keyword: P-The free space of the waste toner box is low.
Please prepare a new waste toner box.
After the message of replacement is displayed, please replace it with a new one.
Change Waste Toner Box. Search Keyword: P-The waste toner box is full. Please replace the waster toner box with a new one.
For the method, see "Replacing the black(K) toner cartridge and the waste toner box".
Collate Fail:Too Many Pages

Press OK To Hide This Message-The memory is full with the collation data.
Reduce the number of pages of the print data.
Invalid Print Data Received

Press OK To Hide This Message-

If you were printing a private job, the data was deleted because it was not complete.
Please print it again.

Or, the received PLD command data is not supported.

Please check the printer driver in use.


Duplex Print Failed

Press OK To Hide This Message-Printed on one side because the paper setting is not applicable to duplex printing.
To print on both sides, print again from the tray with paper suitable for duplex printing. For paper settings applicable to duplex printing, see "Applicable paper".
Wait Timeout Is Disabled-

Timeout Injob is set to [Off].
When the USB cable is connected, you may not be able to print from the network.

Please Wait
Executing Maintenance
Please Do Not Power Off

-

Firmware update is in progress.
If the power is turned off halfway, this machine may not be able to start.
When update is completed, the machine restarts automatically.

Windows Sockets Error Codes

WSA_INVALID_HANDLE
6
Specified event object handle is invalid.
An application attempts to use an event object, but the specified handle is not valid.
WSA_NOT_ENOUGH_MEMORY
8
Insufficient memory available.
An application used a Windows Sockets function that directly maps to a Windows function. The Windows function is indicating a lack of required memory resources.
WSA_INVALID_PARAMETER
87
One or more parameters are invalid.
An application used a Windows Sockets function which directly maps to a Windows function. The Windows function is indicating a problem with one or more parameters.
WSA_OPERATION_ABORTED
Overlapped operation aborted.
An overlapped operation was canceled due to the closure of the socket, or the execution of the SIO_FLUSH command in WSAIoctl.
WSA_IO_INCOMPLETE
Overlapped I/O event object not in signaled state.
The application has tried to determine the status of an overlapped operation which is not yet completed. Applications that use WSAGetOverlappedResult (with the fWait flag set to FALSE) in a polling mode to determine when an overlapped operation has completed, get this error code until the operation is complete.
WSA_IO_PENDING
Overlapped operations will complete later.
The application has initiated an overlapped operation that cannot be completed immediately. A completion indication will be given later when the operation has been completed.
WSAEINTR
Interrupted function call.
A blocking operation was interrupted by a call to WSACancelBlockingCall.
WSAEBADF
File handle is not valid.
The file handle supplied is not valid.
WSAEACCES
Permission denied.
An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST).
Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT  with SP4 and later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT  with SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.
WSAEFAULT
Bad address.
The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument, which is a sockaddr structure, is smaller than the sizeof(sockaddr).
WSAEINVAL
Invalid argument.
Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket—for instance, calling accept on a socket that is not listening.
WSAEMFILE
Too many open files.
Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread.
WSAEWOULDBLOCK
Resource temporarily unavailable.
This error is returned from operations on nonblocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established.
WSAEINPROGRESS
Operation now in progress.
A blocking operation is currently executing. Windows Sockets only allows a single blocking operation—per- task or thread—to be outstanding, and if any other function call is made (whether or not it references that or any other socket) the function fails with the WSAEINPROGRESS error.
WSAEALREADY
Operation already in progress.
An operation was attempted on a nonblocking socket with an operation already in progress—that is, calling connect a second time on a nonblocking socket that is already connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already been canceled or completed.
WSAENOTSOCK
Socket operation on nonsocket.
An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.
WSAEDESTADDRREQ
Destination address required.
A required address was omitted from an operation on a socket. For example, this error is returned if sendto is called with the remote address of ADDR_ANY.
WSAEMSGSIZE
Message too long.
A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram was smaller than the datagram itself.
WSAEPROTOTYPE
Protocol wrong type for socket.
A protocol was specified in the socket function call that does not support the semantics of the socket type requested. For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM.
WSAENOPROTOOPT
Bad protocol option.
An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.
WSAEPROTONOSUPPORT
Protocol not supported.
The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call requests a SOCK_DGRAM socket, but specifies a stream protocol.
WSAESOCKTNOSUPPORT
Socket type not supported.
The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all.
WSAEOPNOTSUPP
Operation not supported.
The attempted operation is not supported for the type of object referenced. Usually this occurs when a socket descriptor to a socket that cannot support this operation is trying to accept a connection on a datagram socket.
WSAEPFNOSUPPORT
Protocol family not supported.
The protocol family has not been configured into the system or no implementation for it exists. This message has a slightly different meaning from WSAEAFNOSUPPORT. However, it is interchangeable in most cases, and all Windows Sockets functions that return one of these messages also specify WSAEAFNOSUPPORT.
WSAEAFNOSUPPORT
Address family not supported by protocol family.
An address incompatible with the requested protocol was used. All sockets are created with an associated address family (that is, AF_INET for Internet Protocols) and a generic protocol type (that is, SOCK_STREAM). This error is returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, for example, in sendto.
WSAEADDRINUSE
Address already in use.
Typically, only one usage of each socket address (protocol/IP address/port) is permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that was not closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt (SO_REUSEADDR). Client applications usually need not call bind at all—connect chooses an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is committed. This could happen with a call to another function later, including connect, listen, WSAConnect, or WSAJoinLeaf.
WSAEADDRNOTAVAIL
Cannot assign requested address.
The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local computer. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote computer (for example, address or port 0).
WSAENETDOWN
Network is down.
A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets DLL runs over), the network interface, or the local network itself.
WSAENETUNREACH
Network is unreachable.
A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host.
WSAENETRESET
Network dropped connection on reset.
The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. It can also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed.
WSAECONNABORTED
Software caused connection abort.
An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.
WSAECONNRESET
Connection reset by peer.
An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.
WSAENOBUFS
No buffer space available.
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
WSAEISCONN
Socket is already connected.
A connect request was made on an already-connected socket. Some implementations also return this error if sendto is called on a connected SOCK_DGRAM socket (for SOCK_STREAM sockets, the to parameter in sendto is ignored) although other implementations treat this as a legal occurrence.
WSAENOTCONN
Socket is not connected.
A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. Any other type of operation might also return this error—for example, setsockopt setting SO_KEEPALIVE if the connection has been reset.
WSAESHUTDOWN
Cannot send after socket shutdown.
A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving, or both have been discontinued.
WSAETOOMANYREFS
Too many references.
Too many references to some kernel object.
WSAETIMEDOUT
Connection timed out.
A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.
WSAECONNREFUSED
Connection refused.
No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running.
WSAELOOP
Cannot translate name.
Cannot translate a name.
WSAENAMETOOLONG
Name too long.
A name component or a name was too long.
WSAEHOSTDOWN
Host is down.
A socket operation failed because the destination host is down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT.
WSAEHOSTUNREACH
No route to host.
A socket operation was attempted to an unreachable host. See WSAENETUNREACH.
WSAENOTEMPTY
Directory not empty.
Cannot remove a directory that is not empty.
WSAEPROCLIM
Too many processes.
A Windows Sockets implementation may have a limit on the number of applications that can use it simultaneously. WSAStartup may fail with this error if the limit has been reached.
WSAEUSERS
User quota exceeded.
Ran out of user quota.
WSAEDQUOT
Disk quota exceeded.
Ran out of disk quota.
WSAESTALE
Stale file handle reference.
The file handle reference is no longer available.
WSAEREMOTE
Item is remote.
The item is not available locally.
WSASYSNOTREADY
Network subsystem is unavailable.
This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. Users should check:
  • That the appropriate Windows Sockets DLL file is in the current path.
  • That they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one Winsock DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded.
  • The Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly.
WSAVERNOTSUPPORTED
sprers.eu version out of range.
The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Check that no old Windows Sockets DLL files are being accessed.
WSANOTINITIALISED
Successful WSAStartup not yet performed.
Either the application has not called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times.
WSAEDISCON
Graceful shutdown in progress.
Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence.
WSAENOMORE
No more results.
No more results can be returned by the WSALookupServiceNext function.
WSAECANCELLED
Call has been canceled.
A call to the WSALookupServiceEnd function was made while this call was still processing. The call has been canceled.
WSAEINVALIDPROCTABLE
Procedure call table is invalid.
The service provider procedure call table is invalid. A service provider returned a bogus procedure table to Ws2_dll. This is usually caused by one or more of the function pointers being NULL.
WSAEINVALIDPROVIDER
Service provider is invalid.
The requested service provider is invalid. This error is returned by the WSCGetProviderInfo and WSCGetProviderInfo32 functions if the protocol entry specified could not be found. This error is also returned if the service provider returned a version number other than
WSAEPROVIDERFAILEDINIT
Service provider failed to initialize.
The requested service provider could not be loaded or initialized. This error is returned if either a service provider's DLL could not be loaded (LoadLibrary failed) or the provider's WSPStartup or NSPStartup function failed.
WSASYSCALLFAILURE
System call failure.
A system call that should never fail has failed. This is a generic error code, returned under various conditions.
Returned when a system call that should never fail does fail. For example, if a call to WaitForMultipleEvents fails or one of the registry functions fails trying to manipulate the protocol/namespace catalogs.
Returned when a provider does not return SUCCESS and does not provide an extended error code. Can indicate a service provider implementation error.
WSASERVICE_NOT_FOUND
Service not found.
No such service is known. The service cannot be found in the specified name space.
WSATYPE_NOT_FOUND
Class type not found.
The specified class was not found.
WSA_E_NO_MORE
No more results.
No more results can be returned by the WSALookupServiceNext function.
WSA_E_CANCELLED
Call was canceled.
A call to the WSALookupServiceEnd function was made while this call was still processing. The call has been canceled.
WSAEREFUSED
Database query was refused.
A database query failed because it was actively refused.
WSAHOST_NOT_FOUND
Host not found.
No such host is known. The name is not an official host name or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database.
WSATRY_AGAIN
Nonauthoritative host not found.
This is usually a temporary error during host name resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful.
WSANO_RECOVERY
This is a nonrecoverable error.
This indicates that some sort of nonrecoverable error occurred during a database lookup. This may be because the database files (for example, BSD-compatible HOSTS, SERVICES, or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error.
WSANO_DATA
Valid name, no data record of requested type.
The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable.
WSA_QOS_RECEIVERS
QoS receivers.
At least one QoS reserve has arrived.
WSA_QOS_SENDERS
QoS senders.
At least one QoS send path has arrived.
WSA_QOS_NO_SENDERS
No QoS senders.
There are no QoS senders.
WSA_QOS_NO_RECEIVERS
QoS no receivers.
There are no QoS receivers.
WSA_QOS_REQUEST_CONFIRMED
QoS request confirmed.
The QoS reserve request has been confirmed.
WSA_QOS_ADMISSION_FAILURE
QoS admission error.
A QoS error occurred due to lack of resources.
WSA_QOS_POLICY_FAILURE
QoS policy failure.
The QoS request was rejected because the policy system couldn't allocate the requested resource within the existing policy.
WSA_QOS_BAD_STYLE
QoS bad style.
An unknown or conflicting QoS style was encountered.
WSA_QOS_BAD_OBJECT
QoS bad object.
A problem was encountered with some part of the filterspec or the provider-specific buffer in general.
WSA_QOS_TRAFFIC_CTRL_ERROR
QoS traffic control error.
An error with the underlying traffic control (TC) API as the generic QoS request was converted for local enforcement by the TC API. This could be due to an out of memory error or to an internal QoS provider error.
WSA_QOS_GENERIC_ERROR
QoS generic error.
A general QoS error.
WSA_QOS_ESERVICETYPE
QoS service type error.
An invalid or unrecognized service type was found in the QoS flowspec.
WSA_QOS_EFLOWSPEC
QoS flowspec error.
An invalid or inconsistent flowspec was found in the QOS structure.
WSA_QOS_EPROVSPECBUF
Invalid QoS provider buffer.
An invalid QoS provider-specific buffer.
WSA_QOS_EFILTERSTYLE
Invalid QoS filter style.
An invalid QoS filter style was used.
WSA_QOS_EFILTERTYPE
Invalid QoS filter type.
An invalid QoS filter type was used.
WSA_QOS_EFILTERCOUNT
Incorrect QoS filter count.
An incorrect number of QoS FILTERSPECs were specified in the FLOWDESCRIPTOR.
WSA_QOS_EOBJLENGTH
Invalid QoS object length.
An object with an invalid ObjectLength field was specified in the QoS provider-specific buffer.
WSA_QOS_EFLOWCOUNT
Incorrect QoS flow count.
An incorrect number of flow descriptors was specified in the QoS structure.
WSA_QOS_EUNKOWNPSOBJ
Unrecognized QoS object.
An unrecognized object was found in the QoS provider-specific buffer.
WSA_QOS_EPOLICYOBJ
Invalid QoS policy object.
An invalid policy object was found in the QoS provider-specific buffer.
WSA_QOS_EFLOWDESC
Invalid QoS flow descriptor.
An invalid QoS flow descriptor was found in the flow descriptor list.
WSA_QOS_EPSFLOWSPEC
Invalid QoS provider-specific flowspec.
An invalid or inconsistent flowspec was found in the QoS provider-specific buffer.
WSA_QOS_EPSFILTERSPEC
Invalid QoS provider-specific filterspec.
An invalid FILTERSPEC was found in the QoS provider-specific buffer.
WSA_QOS_ESDMODEOBJ
Invalid QoS shape discard mode object.
An invalid shape discard mode object was found in the QoS provider-specific buffer.
WSA_QOS_ESHAPERATEOBJ
Invalid QoS shaping rate object.
An invalid shaping rate object was found in the QoS provider-specific buffer.
WSA_QOS_RESERVED_PETYPE
Reserved policy QoS element type.
A reserved policy element was found in the QoS provider-specific buffer.

Appendix A: ODBC Error Codes

General warningAll ODBC functions except:

SQLError

SQLGetDiagField

SQLGetDiagRecCursor operation conflictSQLExecDirect

SQLExecute

SQLParamData

SQLSetPosDisconnect errorSQLDisconnectNULL value eliminated in set functionSQLExecDirect

SQLExecute

SQLParamDataString data, right-truncatedSQLBrowseConnect

SQLBulkOperations

SQLColAttribute

SQLDataSources

SQLDescribeCol

SQLDriverConnect

SQLDrivers

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetConnectAttr

SQLGetCursorName

SQLGetData

SQLGetDescField

SQLGetDescRec

SQLGetEnvAttr

SQLGetInfo

SQLGetStmtAttr

SQLNative

Sql SQLParamData

SQLPutData

SQLSetCursorNamePrivilege not revokedSQLExecDirect

SQLExecute

SQLParamDataPrivilege not grantedSQLExecDirect

SQLExecute

SQLParamData01S00Invalid connection string attributeSQLBrowseConnect

SQLDriverConnec01S01Error in rowSQLBulkOperations

SQLExtendedFetch

SQLSetPos01S02Option value changedSQLBrowseConnect

SQLConnect

SQLDriverConnect

SQLExecDirect

SQLExecute

SQLParamData

SQLPrepare

SQLSetConnectAttr

SQLSetDescField

SQLSetEnvAttr

SQLSetStmtAttr01S06Attempt to fetch before the result set returned the first rowsetSQLExtendedFetch

SQLFetchScroll01S07Fractional truncationSQLBulkOperations

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLParamData

SQLSetPos01S08Error saving File DSNSQLDriverConnect01S09Invalid keywordSQLDriverConnectWrong number of parametersSQLExecDirect

SQLExecuteCOUNT field incorrectSQLExecDirect

SQLExecute

SQLParamDataPrepared statement not a cursor-specificationSQLColAttribute

SQLDescribeColRestricted data type attribute violationSQLBindCol

SQLBindParameter

SQLBulkOperations

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLParamData

SQLPutData

SQLSetPosInvalid descriptor indexSQLBindCol

SQLBindParameter

SQLBulkOperations

SQLColAttribute

SQLDescribeCol

SQLDescribeParam

SQLFetch

SQLFetchScroll

SQLGetData

SQLGetDescField

SQLGetDescRec

SQLParamData

SQLSetDescField

SQLSetDescRecSQLSetPos07S01Invalid use of default parameterSQLExecDirect

SQLExecute

SQLParamData

SQLPutDataClient unable to establish connectionSQLBrowseConnect

SQLConnect

SQLDriverConnectConnection name in useSQLBrowseConnect

SQLConnect

SQLDriverConnect

SQLSetConnectAttrConnection not openSQLAllocHandle

SQLDisconnect

SQLEndTran

SQLGetConnectAttr

SQLGetInfo

SQLNativeSql

SQLSetConnectAttrServer rejected the connectionSQLBrowseConnect

SQLConnect

SQLDriverConnectConnection failure during transactionSQLEndTran08S01Communication link failureSQLBrowseConnect

SQLColumnPrivileges

SQLColumns

SQLConnect

SQLCopyDesc

SQLDescribeCol

SQLDescribeParam

SQLDriverConnect

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLGetConnectAttr

SQLGetData

SQLGetDescField

SQLGetDescRec

SQLGetFunctions

SQLGetInfo

SQLGetTypeInfo

SQLMoreResults

SQLNativeSql

SQLNumParams

SQLNumResultCols

SQLParamData

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLPutData

SQLSetConnectAttr

SQLSetDescField

SQLSetDescRec

SQLSetEnvAttr

SQLSetStmtAttr

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTables21S01Insert value list does not match column listSQLExecDirect

SQLPrepare21S02Degree of derived table does not match column listSQLBulkOperations

SQLExecDirect

SQLExecute

SQLParamData

SQLPrepare

SQLSetPosString data, right-truncatedSQLBulkOperations

SQLExecDirect

SQLExecute

SQLFetch

SQLFetchScroll

SQLParamData

SQLPutData

SQLSetDescField

SQLSetPosIndicator variable required but not suppliedSQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLParamDataNumeric value out of rangeSQLBulkOperations

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLGetInfo

SQLParamData

SQLPutData

SQLSetPosInvalid datetime formatSQLBulkOperations

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLParamData

SQLPutData

SQLSetPosDatetime field overflowSQLBulkOperations

SQLExecDirect

QLParamData

SQLPutDataDivision by zeroSQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLPutDataInterval field overflowSQLBulkOperations

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLParamData

SQLPutData

SQLSetPosInvalid character value for cast specificationSQLBulkOperations

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLParamData

SQLPutData

SQLSetPosInvalid escape characterSQLExecDirect

SQLExecute

SQLPrepareInvalid escape sequenceSQLExecDirect

SQLExecute

SQLPrepareString data, length mismatchSQLParamDataIntegrity constraint violationSQLBulkOperations

SQLExecDirect

SQLExecute

SQLParamData

SQLSetPosInvalid cursor stateSQLBulkOperations

SQLCloseCursor

SQLColumnPrivileges

SQLColumns

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLGetData

SQLGetStmtAttr

SQLGetTypeInfo

SQLNativeSql

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLSetConnectAttr

SQLSetCursorName

SQLSetPos

SQLSetStmtAttr

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesInvalid transaction stateSQLDisconnect25S01Transaction stateSQLEndTran25S02Transaction is still activeSQLEndTran25S03Transaction is rolled backSQLEndTranInvalid authorization specificationSQLBrowseConnect

SQLConnect

SQLDriverConnectInvalid cursor nameSQLExecDirect

SQLPrepare

SQLSetCursorName3CDuplicate cursor nameSQLSetCursorName3DInvalid catalog nameSQLExecDirect

SQLPrepare

SQLSetConnectAttr3FInvalid schema nameSQLExecDirect

SQLPrepareSerialization failureSQLBulkOperations

SQLColumnPrivileges

SQLColumns

SQLEndTran

SQLExecDirect

SQLExecute

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLGetTypeInfo

SQLMoreResults

SQLParamData

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLSetPos

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesIntegrity constraint violationSQLEndTranStatement completion unknownSQLBulkOperations

SQLColumnPrivileges

SQLColumns

SQLExecDirect

SQLExecute

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLGetTypeInfo

SQLMoreResults

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLParamData

SQLSetPos

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesSyntax error or access violationSQLBulkOperations

SQLExecDirect

SQLExecute

SQLParamData

SQLPrepare

SQLSetPos42S01Base table or view already existsSQLExecDirect

SQLPrepare42S02Base table or view not foundSQLExecDirect

SQLPrepare42S11Index already existsSQLExecDirect

SQLPrepare42S12Index not foundSQLExecDirect

SQLPrepare42S21Column already existsSQLExecDirect

SQLPrepare42S22Column not foundSQLExecDirect

SQLPrepareWITH CHECK OPTION violationSQLBulkOperations

SQLExecDirect

SQLExecute

SQLParamData

SQLSetPosHYGeneral errorAll ODBC functions except:

SQLError

SQLGetDiagField

SQLGetDiagRecHYMemory allocation errorAll ODBC functions except:

SQLError

SQLGetDiagField

SQLGetDiagRecHYInvalid application buffer typeSQLBindCol

SQLBindParameter

SQLGetDataHYInvalid SQL data typeSQLBindParameter

SQLGetTypeInfoHYAssociated statement is not preparedSQLCopyDesc

SQLGetDescField

SQLGetDescRecHYOperation canceledAll ODBC functions that can be processed asynchronously:

SQLBrowseConnect

SQLBulkOperations

SQLColAttribute

SQLColumnPrivileges

SQLColumns

SQLConnect

SQLDescribeCol

SQLDescribeParam

SQLDisconnect

SQLDriverConnect

SQLEndTran

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLGetData

SQLGetTypeInfo

SQLMoreResults

SQLNumParams

SQLNumResultCols

SQLParamData

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLPutData

SQLSetConnectAttr

SQLSetPos

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesHYInvalid use of null pointerSQLAllocHandle

SQLBindParameter

SQLBulkOperations

SQLColumnPrivileges

SQLColumns

SQLExecDirect

SQLForeignKeys

SQLGetCursorName

SQLGetData

SQLGetFunctions

SQLNativeSql

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLPutData

SQLSetConnectAttr

SQLSetCursorName

SQLSetEnvAttr

SQLSetStmtAttr

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesHYFunction sequence errorSQLAllocHandle

SQLBindCol

SQLBindParameter

SQLBulkOperations

SQLCloseCursor

SQLColAttribute

SQLColumnPrivileges

SQLColumns

SQLCopyDesc

SQLDescribeCol

SQLDescribeParam

SQLDisconnect

SQLEndTran

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLFreeHandle

SQLFreeStmt

SQLGetConnectAttr

SQLGetCursorName

SQLGetData

SQLGetDescField

SQLGetDescRec

SQLGetFunctions

SQLGetStmtAttr

SQLGetTypeInfo

SQLMoreResults

SQLNumParams

SQLNumResultCols

SQLParamData

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLPutData

SQLRowCount

SQLSetConnectAttr

SQLSetCursorName

SQLSetDescField

SQLSetEnvAttr

SQLSetDescRec

SQLSetPos

SQLSetStmtAttr

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesHYAttribute cannot be set nowSQLBulkOperations

SQLParamData

QLSetPos

SQLSetStmtAttrHYInvalid transaction operation codeSQLEndTranHYMemory management errorAll ODBC functions except:

SQLGetDiagField

SQLGetDiagRecHYLimit on the number of handles exceededSQLAllocHandleHYNo cursor name availableSQLGetCursorNameHYCannot modify an implementation row descriptorSQLCopyDesc

SQLSetDescField

SQLSetDescRecHYInvalid use of an automatically allocated descriptor handleSQLFreeHandle

SQLSetStmtAttrHYServer declined cancel requestSQLCancelHYNon-character and non-binary data sent in piecesSQLPutDataHYAttempt to concatenate a null valueSQLPutDataHYInconsistent descriptor informationSQLBindParameter

SQLCopyDesc

SQLGetDescField

SQLSetDescField

SQLSetDescRecHYInvalid attribute valueSQLSetConnectAttr

SQLSetEnvAttr

SQLSetStmtAttrHYInvalid string or buffer lengthSQLBindCol

SQLBindParameter

SQLBrowseConnect

SQLBulkOperations

SQLColAttribute

SQLColumnPrivileges

SQLColumns

SQLConnect

SQLDataSources

SQLDescribeCol

SQLDriverConnect

SQLDrivers

SQLExecDirect

SQLExecute

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLGetConnectAttr

SQLGetCursorName

SQLGetData

SQLGetDescField

SQLGetInfo

SQLGetStmtAttr

SQLNativeSql

SQLParamData

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLPutData

SQLSetConnectAttr

SQLSetCursorName

SQLSetDescField

SQLSetDescRec

SQLSetEnvAttr

SQLSetStmtAttr

SQLSetPos

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesHYInvalid descriptor field identifierSQLColAttribute

SQLGetDescField

SQLSetDescFieldHYInvalid attribute/option identifierSQLAllocHandle

QLBulkOperations

SQLCopyDesc

SQLDriverConnect

SQLEndTran

SQLFreeStmt

SQLGetConnectAttr

SQLGetEnvAttr

QLParamData

SQLSetConnectAttr

SQLSetDescField

SQLSetEnvAttr

SQLSetPos

SQLSetStmtAttrHYFunction type out of rangeSQLGetFunctionsHYInvalid information typeSQLGetInfoHYColumn type out of rangeSQLSpecialColumnsHYScope type out of rangeSQLSpecialColumnsHYNullable type out of rangeSQLSpecialColumnsHYUniqueness option type out of rangeSQLStatisticsHYAccuracy option type out of rangeSQLStatisticsHYInvalid retrieval codeSQLDataSources

SQLDriversHYInvalid precision or scale valueSQLBindParameterHYInvalid parameter typeSQLBindParameter

SQLExecDirect

SQLExecute

SQLParamData

SQLSetDescFieldHYFetch type out of rangeSQLExtendedFetch

SQLFetchScrollHYRow value out of rangeSQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLSetPosHYInvalid cursor positionSQLExecDirect

SQLExecute

SQLGetData

SQLGetStmtAttr

SQLNativeSql

SQLParamData

SQLSetPosHYInvalid driver completionSQLDriverConnectHYInvalid bookmark valueSQLExtendedFetch

SQLFetchScrollHYC00Optional feature not implementedSQLBindCol

SQLBindParameter

SQLBulkOperations

SQLColAttribute

SQLColumnPrivileges

SQLColumns

SQLDriverConnect

SQLEndTran

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLGetConnectAttr

SQLGetData

SQLGetEnvAttr

SQLGetInfo

SQLGetStmtAttr

SQLGetTypeInfo

SQLParamData

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLSetConnectAttr

SQLSetEnvAttr

SQLSetPos

SQLSetStmtAttr

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesHYT00Timeout expiredSQLBrowseConnect

SQLBulkOperations

SQLColumnPrivileges

SQLColumns

SQLConnect

SQLDriverConnect

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLForeignKeys

SQLGetTypeInfo

SQLParamData

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLSetPos

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesHYT01Connection timeout expiredAll ODBC functions except:

SQLDrivers

SQLDataSources

SQLGetEnvAttr

SQLSetEnvAttrIMDriver does not support this functionAll ODBC functions except:

SQLAllocHandle

SQLDataSources

SQLDrivers

SQLFreeHandle

SQLGetFunctionsIMData source name not found and no default driver specifiedSQLBrowseConnect

SQLConnect

SQLDriverConnectIMSpecified driver could not be loadedSQLBrowseConnect

SQLConnect

SQLDriverConnectIMDriver's SQLAllocHandle on SQL_HANDLE_ENV failedSQLBrowseConnect

SQLConnect

SQLDriverConnectIMDriver's SQLAllocHandle on SQL_HANDLE_DBC failedSQLBrowseConnect

SQLConnect

SQLDriverConnectIMDriver's SQLSetConnectAttr failedSQLBrowseConnect

SQLConnect

SQLDriverConnectIMNo data source or driver specified; dialog prohibitedSQLDriverConnectIMDialog failedSQLDriverConnectIMUnable to load translation DLLSQLBrowseConnect

SQLConnect

SQLDriverConnect

SQLSetConnectAttrIMData source name too longSQLBrowseConnect

SQLConnect

SQLDriverConnectIMDriver name too longSQLBrowseConnect

SQLDriverConnectIMDRIVER keyword syntax errorSQLBrowseConnect

SQLDriverConnectIMTrace file errorAll ODBC functions.IMInvalid name of File DSNSQLDriverConnectIMCorrupt file data sourceSQLDriverConnect
   Related: More > Error Logs


Problem

One of our SQL Servers was experiencing fatal errors on a frequent basis during batch processing. This was a SQL Server on Windows operating system. Here are some details of the error log which were captured:

A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: , output error: 0). Error: , Severity: 20, State:


Fatal error shot captured in error log file
Solution

This fatal error suggests that something is wrong on the network which is causing network packets to drop. The error which is captured in the SQL Server error log can be due to different reasons. I searched this error on the web and found some MSDN forums where similar issues were discussed. Some responses suggested disabling the TCP/IP Chimney Offload feature, so I decided to research this further. Let's start with TCP/IP Chimney offloading, RSS features and NetDMA.

Microsoft released the Scalable Networking Pack (SNP) that consists of three main features. These three features are TCP/IP Chimney, Receive Side Scaling (RSS) and NetDMA.

  • TCP/IP Chimney Offload, as per TechNet, is designed to take processing of the network such as packet segmentation and reassembly processing tasks, from a computer's CPU to a network adapter that supports TCP Chimney Offload. This has the effect of reducing the workload on the host CPU and moving it to the NIC, allowing both the Host OS to perform quicker and also speed up the processing of network traffic.
  • Receive Side Scaling (RSS) enables the network load from a network adapter to be distributed across multiple CPUs in a multiprocessor computer.
  • Network Direct Memory Access (NetDMA) provides services for offloading the memory copy operation that is performed by the networking subsystem to a dedicated direct memory access (DMA) engine when receiving network packets.

Now let's check these settings on our impacted system. We ran the below command to check the existing values of these SNP settings:

netsh int tcp show global

Checked TCP chimney offload

As we can see, all these settings were enabled as shown in the above screenshot. By default, TCP Chimney Offload is disabled in Windows and later versions, but sometimes vendor applications can turn them on. We can also check whether TCP Chimney Offload is working or not by running the netstat -t command.

I checked these settings on other production servers for the same application and found that these settings were disabled on those servers. See the below output of SNP settings on two production servers:

SERVER: DELHISQL01 TCP Global Parameters Receive-Side Scaling State : disabled Chimney Offload State : disabled NetDMA State : disabled Direct Cache Access (DCA) : disabled Receive Window Auto-Tuning Level : normal Add-On Congestion Control Provider : ctcp ECN Capability : disabled RFC Timestamps : disabled SERVER: DELHISQL02 TCP Global Parameters Receive-Side Scaling State : disabled Chimney Offload State : disabled NetDMA State : disabled Direct Cache Access (DCA) : disabled Receive Window Auto-Tuning Level : normal Add-On Congestion Control Provider : ctcp ECN Capability : disabled RFC Timestamps : disabled

The problem is that many NICs report to the OS that they support these features, which they indeed do, but many didn't perform these functions very well in reality. These SNP options looks good from an OS perspective, but due to misbehaving NIC drivers they turn into lot of weird issues so it is better to turn them off to fix such issues, get an update from the NIC vendor or use a better NIC driver that can use these features in an effective way.

We should disable these SNP features in Windows and NIC hardware setting as well with the vendor's firmware tools if we don’t have an update for  the NIC driver or NIC drivers are not compatible with these features. We can check these settings in network adaptors by launching device manager and then expanding the network adaptors section as shown in the below screenshot.

SNP settings in netowork adaptors

Steps to Disable NIC Settings

So we decided to replicate the same settings (which were on other production servers) into our impacted server where the fatal errors were reported. We used this Microsoft article to disable the TCP/ IP Chimney, RSS and NetDMA state by using the below steps.

1: Open a command prompt with administrative privileges.

2: Run the below command to disable TCP/IP Chimney Offload.

netsh int tcp set global chimney=disabled

3: Run the below command to disable RSS.

netsh int tcp set global rss=disabled

4: NetDMA will be disabled through the registry, so make sure to backup your registry before doing the next steps. To open the Registry Editor, click Start, click Run, type regedit, and then click OK.

5: Locate the registry sub-key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters and click on it.

6: Locate the EnableTCPA registry entry. If this registry entry does not exist, right-click the Parameters sub-key, point to New, and then click DWORD Value.

7: Replace the New Value #1 by typing EnableTCPA, and then press ENTER. Double-click the EnableTCPA registry value you just created and type 0 in the Value to disable NetDMA, and then click OK.

8: TCP Chimney Offload and RSS will be disabled just after executing the above commands, but NetDMA requires a system reboot after making changes to the registry.

After the above changes and the reboot we can run the below command to check whether all these settings are disabled, which they are as shown below.

netsh int tcp show global

SNP settings disabled on windows

After we made these changes we no longer received any fatal errors. These features are made to enhance the capability of Windows, but unfortunately it is not always useful if your NIC drivers do not support these features.

Next Steps
  • If you run into these errors, use the steps in this tip to see if these features are enabled for your NICs.
  • If you have advanced NIC drivers that can utilize these features then enable TCP Chimney Offloading otherwise it is suggested to turn them off.





get scripts

next tip button



About the author
MSSQLTips author Manvendra SinghManvendra Singh has over 5 years of experience with SQL Server and has focused on Database Mirroring, Replication, Log Shipping, etc.

View all my tips


Article Last Updated:

Fixing SQL Server fatal error

By: Manvendra Singh   

System Error Messages for Cisco Unified Communications Manager (1)

Note

Optional parameter is indicated with the notation {Optional}. Application or Component may decide not to use that parameter in the alarm message.

Order of the parameters in an alarm message can change and it is decided by the Application or Component.

If the error message contains UNKNOWN_PARAMNAME, the parameter immediately following the UNKNOWN_PARAMNAME has not yet been updated in the alarm catalog. If this occurs, the error message is given a severity-level of 3, irrespective of the default severity-level for that error message.


Error Message

%: %[Priority=String][AppID=String][ClusterID=String][NodeID=String]: Service is running and working properly.

Explanation   CMI service is running and working properly

Recommended Action   Informational purpose only; no action is required

Error Message

%: %[StopBit=String][AppID=String][ClusterID=String][NodeID=String]: The Cisco Messaging Interface service parameter, Stop Bits, has an invalid configuration.

Explanation   An invalid stop bit has been configured for the serial port that CMI uses to connect to the voice messaging system. It is possible that the Stop Bits value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.

Recommended Action   Verify that the Cisco Messaging Interface service parameter Stop Bits is set to a valid (allowable) value

Error Message

%: %[Parity=String][AppID=String][ClusterID=String][NodeID=String]: The CMI service parameter, Parity, has an invalid configuration.

Explanation   An invalid parity has been configured for the serial port that CMI uses to connect to the voice messaging system. It is possible that the parity value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.

Recommended Action   Verify that the Cisco Messaging Interface service parameter Parity is set to a valid (allowable) value

Error Message

%: %[InvalidDN=String][AppID=String][ClusterID=String][NodeID=String]: SMDI message contains invalid DN.

Explanation   Some voice messaging systems send SMDI messages to Cisco Unified Communications Manager (Unified CM) with an invalid DN specifically for the purpose of verifying that Unified CM is functioning properly. In such cases, if the Validate DNs service parameter is set to True, CMI triggers this alarm because the DN cannot be found in the Unified CM database.

Recommended Action   Verify that the Cisco Messaging Interface service parameter Validate DNs is set to false

Error Message

%: %[SMDICmd=String][AppID=String][ClusterID=String][NodeID=String]: CMI receives an invalid incoming SMDI message.

Explanation   There are two kinds of incoming messages that Cisco Unified Communications Manager can accept from the voice messaging system; they are OP:MWI(SP)nnnnnnn!(D) and RMV:MWI(SP)nnnnnnn!(D) (where:nnnnnnnnnn = station number (can be 7 or 10 digits), (D) = End Of Transmission, (SP) = space). The first message activates the message waiting indicator (MWI). The second deactivates the message waiting indicator. CMI triggers this alarm if the received MWI message doesn't have one of the acceptable formats as described.

Recommended Action   Contact the vendor of the third-party voice messaging system and discover why it is sending SMDI message with an invalid format

Error Message

%: %[OpeningError=String][AppID=String][ClusterID=String][NodeID=String]: When CMI tries to open the serial port, the operating system returns an error.

Explanation   For a system running CMI, the serial port through which the voice messaging system is connected is always USB0, and that value is configured in the Cisco Messaging Interface service parameter, Serial Port. It is possible that the Serial Port value has been updated via AXL or a CLI command where validation of the value was not performed. CMI triggers this alarm if the value in the Serial Port service parameter is anything other than USB0.

Recommended Action   Ensure that USB0 is configured in the Cisco Messaging Interface service parameter Serial Port. Also, physically confirm that the cable is firmly connected to the USB0 port.

Error Message

%: %[GetStatusError=String][AppID=String][ClusterID=String][NodeID=String]: When CMI tries to get the status of serial port, the operating system returns an error.

Explanation   CMI triggers this alarm when it can't get the status of the serial port. An inability to receive serial port status information could be caused by a loose or disconnected USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%: %[SetStatusError=String][AppID=String][ClusterID=String][NodeID=String]: When CMI tries to set the status of serial port, the operating system returns an error.

Explanation   CMI triggers this alarm when it can't set the status of the serial port. An inability to receive serial port status information could be caused by a loose or disconnected USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: CMI failed to write SMDI messages to the serial port.

Explanation   CMI opened the serial port, however it failed to successfully write data to the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: CMI failed to read SMDI messages from the serial port.

Explanation   CMI opened the serial port, however it failed to successfully read data from the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: The handle for the opened serial port is invalid.

Explanation   CMI cannot read/write to the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Recommended Action   Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message

%: %[VoiceMailDN=String][AppID=String][ClusterID=String][NodeID=String]: The Voice Mail DN for CMI is invalid.

Explanation   CMI can't register with Cisco Unified Communications Manager because of an invalid Voice Mail DN. This alarm occurs because the Cisco Messaging Interface service parameter, Voice Mail DN, is empty or has invalid characters other than digits (). It is possible that the Voice Mail DN value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.

Recommended Action   Check the CMI service parameter Voice Mail DN to confirm that a valid directory number has been configured.

Error Message

%: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: An error occurred when CMI tried to stop the CMI service.

Explanation   As a normal part of the process of stopping the CMI service, open threads are closed (killed). This alarm indicates that a timeout occurred which means that the shutdown process is taking longer than expected, causing the operating system to return an error.

Recommended Action   Try restarting the CMI service. If the problem persists, collect the system/application event logs and the performance (perfmon) logs and report to Cisco Technical Assistance Center (TAC).

Error Message

%: %[MemAllocFailure=String][AppID=String][ClusterID=String][NodeID=String]: CMI tried to allocate memory and failed.

Explanation   Cisco Unified Communications Manager tried to read the Cisco Messaging Interface service parameters but not enough memory was allocated for the task and so the information could not be read.

Recommended Action   Use the Real-Time Monitoring Tool to check performance counters related to system memory to learn whether any memory leaks or spikes in CPU are occurring. Correct any anomalous memory issues you find. If you do not find any issues with memory, collect the system/application event logs and the performance (perfmon) logs and report this alarm to the Cisco Technical Assistance Center (TAC).

Error Message

%: %[DBLException=String][AppID=String][ClusterID=String][NodeID=String]: Unable to connect to the DB.

Explanation   When CMI service is started, it tries to read CMI Service Parameters from DB. During this, if CMI cannot connect to the database, it triggers this alarm.

Recommended Action   Check Database connection, then restart CMI.

Error Message

%: %[CMIException=String][AppID=String][ClusterID=String][NodeID=String]: Error while reading the database.

Explanation   This alarm is always associated with other alarms, which are triggered due to configuring CMI service parameter with invalid values or due to invalid handle value returned by the serial port.

Recommended Action   Refer to the associated alarm for further information.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Unknown error while connecting to DB.

Explanation   When CMI service is started, it tries to read CMI service parameters from DB. During this, if there is an unknown error, CMI triggers this alarm.

Recommended Action   Report to Customer Service representative.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Service is now running.

Explanation   CMI service has been started and running

Recommended Action   Informational purpose only; no action is required

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Service is now stopping..

Explanation   CMI Service has been stopped.

Recommended Action   Informational purpose only; no action is required.

Error Message

%: %[DebugMsg=String][AppID=String][ClusterID=String][NodeID=String]: This alarm is generated only for the purpose of debugging.

Explanation   CMI has several debug messages which simulate the real-time situations

Recommended Action   Report to Customer Service representative

Error Message

%: %[Cisco Unified Communications Manager Name=String][AppID=String][ClusterID=String][NodeID=String]: CMI can't establish connection with the Cisco Unified Communications Manager.

Explanation   CMI can't establish connection with the Unified Communications Manager

Recommended Action   Check the address/status of the CallManager and the network

Error Message

%: %[Cisco Unified Communications Manager Name=String][AppID=String][ClusterID=String][NodeID=String]: CMI loses the connection with Unified Communications Manager.

Explanation   CMI loses the connection with the Cisco Unified Communications Manager

Recommended Action   Check the status of the Unified Communications Manager and the Network

Error Message

%: %[ErrorInfo=String][AppID=String][ClusterID=String][NodeID=String]: Windows Socket startup failed.

Explanation   WinSock could not be started

Recommended Action   Report to Customer Service representative.

Error Message

%: %[ParaNameInfo=String][AppID=String][ClusterID=String][NodeID=String]: CMI service configuration parameter is not found in Database.

Explanation   CMI cannot find this process configuration parameter in process configuration table.

Recommended Action   Report to Customer Service representative to get the database upgrade

Error Message

%: %[COMException=String][AppID=String][ClusterID=String][NodeID=String]: CMI catches an COM exception..

Explanation   CMI cannot find this process configuration parameter in process configuration table.

Recommended Action   Check system setting and resource, then restart system.

Error Message

%: %[LastPDUNumber=Long][AppID=String][ClusterID=String][NodeID=String]: Application has dropped the connection to CTIManager.

Explanation   TCP or TLS connection between CTIManager and Application is disconnected

Recommended Action   Possible causes include Application server power outage, network power outage, network configuration error, network delay, packet drops or packet corruption. It is also possible to get this error if the Unified CM node or application server is experiencing high CPU usage. Verify the application is up and running, verify network connectivity between the application server and Unified CM, and verify the CPU utilization is in the safe range for application server and Unified CM (this can be monitored using RTMT via CPU Pegging Alert)

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Maximum number of application connections is reached; application connection rejected.

Explanation   Maximum number of CTI connections has been reached, no new connection will be accepted unless an existing connection is closed

Recommended Action   Check the CTI Manager service parameter Maximum CTI Connections for the maximum number of connections. Carefully consider increasing the service parameter value or disconnecting CTI applications that are unnecessary. Refer to Unified CM Solution Reference Network Design document in sprers.eu based on the version you are using for maximum number of applications and devices supported by CTI

Error Message

%: %[CTIConnectionType=String][InstanceNumber=Long][PDUNumber=Long][AppID=String][ClusterID=String][NodeID=String]: An invalid QBE PDU is received.

Explanation   QBE PDU from application is invalid

Recommended Action   This alarm indicates that TSP/JTAPI has reported a QBE PDU that cannot be recognized by CTIManager. Contact the support organization for the affected application, install the JTAPI or TSP plugin and restart the application. JTAPI/TSP plugins are available from the Find and List Plugins window in Cisco Unified CM Administration (Application > Plugins)

Error Message

%: %[CTIconnectionId=Long][LoginUserId=String][Reason=Enum][IPaddress=String][IPv6address=String][AppID=String][ClusterID=String][NodeID=String]: CTI application failed to open provider; application startup failed.

Explanation   The application is unable to open provider. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode

Recommended Action   Review the reason code and the recommended action within the reason code

Reason Code - Enum Definitions

Enum Definitions - Reason

ValueDefinition
0Unknown
0x8CCC ()Login request to authenticate user has timed out. Possible causes include LDAP server misconfiguration such as LDAP server referrals misconfiguration or Unified CM node experiencing high CPU usage. Recommended action is to verify the CPU utilization is in the safe range for Unified CM (this can be monitored using RTMT via CPU Pegging Alert)
0x8CCC ()Directory login failed. Verify that credentials are not misconfigured, check the userID and password configured in the application matches with what is configured in Unified CM Admin under (User Management > End User or Application User)
0x8CCCE ()Directory is unavailable. Verify that the LDAP server is reachable from Unified CM node, make sure that the network connectivity between Unified CM and the LDAP server by pinging the LDAP server host from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost
0x8CCC00D1 ()Application is connecting to a non secure port but has security priviledges enabled for the user associated with the application. Check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information
0x8CCCF ()Standard CTI Use permission is not enabled. Users associated with applications are required to be included in "Standard CTI Enabled" user group. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information
0x8CCC00D0 ()User is not enabled for a secure connection but the application connecting to secure port. Consider the application configuration and security configuration for the user, for TAPI applications review the Control Panel >Phone and Modem Options > Advanced > select a CiscoTSP > Configure > Security and disable "Secure Connection to CTIManager". For JTAPI applications from JTPrefs choose Security and disable "Enable Secure Connection". Also check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information
0x8CCCD ()Directory login failed - Password expired. The user's login credentials have expired. The user can change the password by logging into the Cisco Unified CM User Options website using his/her existing credentials. The Cisco Unified CM User Options website will display the logon status indicating that the password has expired and will prompt the user to enter a new password
0x8CCCF ()Directory login failed - Account locked. A user has been locked out of his or her account. Lockouts can occur for one of the following reasons: 1) Too many tries: a user made too many login attempts using invalid credentials. Contact the user to confirm that he or she has been attempting to login. You can verify a user's login credential in Cisco Unified CM Administration (User Management > End User/Application User), select the User and click the Edit Credential button, then, under Credential Information, enable the Reset Hack Count checkbox to reset the hack count for this user and clear the Time Locked Due to Failed Login Attempts field. After the counter resets, notify the user that he or she can try logging in again. 2) Account locked by administrator: when warranted, an administrator can lockout a user's access. To do so, go to Cisco Unified CM Administration and click User Management > End User/Application User, select the user and click the Edit Credential button, then . To lock or unlock a user's account, under the Credential Information page, select or deselect the Locked by Administrator checkbox. 3) Account locked due to an extended period of inactivity: the Administrator must notify the user that his or her account has been locked due to inactivity. To unlock the user's account, the Administrator must change the password in Cisco Unified CM Administration by clicking under (User Management > End User/Application User), selecting the User and modifying the password in the End User/Application User Configuration window. After changing the password, notify the user about of his or her new password and encourage the user to change the password in Cisco Unified CM User Options to a new password of the user's choosing

Error Message

%: %[ErrorCode=ULong][SeqNumber=Long][ErrorMessageString=String][AppID=String][ClusterID=String][NodeID=String]: Requested operation from the application has failed.

Explanation   The requested operation from the application could not be performed because of a normal or abnormal condition

Recommended Action   Verify whether the affected application is experiencing a problem. Contact the support organization for the affected application if the problem persists and provide sequence number and error message for further investigation

Error Message

%: %[LoginUserId=String][SeqNumber=Long][CTIconnectionId=Long][IPAddress=String][IPv6Address=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: CTI application connection has been closed.

Explanation   Application closed the provider. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode

Recommended Action   This alarm is for informational purposes only; no action is required.

Reason Code - Enum Definitions

Enum Definitions - Reason

ValueDefinition
0Unknown
1Heart beat from application missed. Possible causes include network connectivity issues or Unified CM node experiencing high CPU usage. Make sure that the network connectivity between Unified CM and the application by pinging the application server host from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost. Also check for and fix any network issues or high CPU usage on the application server
2Unexpected shutdown; possibly cause is application disconnected the TCP connection. Also check for and fix any network issues or high CPU usage on the application server
3Application requested provider close
4Provider open failure; application could not be initialized
5User deleted. User associated with the application is deleted from the Unified CM Administration
6SuperProvider permission associated with the application is removed. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information
7Duplicate certificate used by application. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information
8CAPF information unavailable. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information
9Certificate compromised. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information
11User is not authorized to connect to CTI using TLS. Consider the application configuration and security configuration for the user, for TAPI applications review the Control Panel >Phone and Modem Options > Advanced > select a CiscoTSP > Configure > Security and disable "Secure Connection to CTIManager". For JTAPI applications from JTPrefs choose Security and disable "Enable Secure Connection". Also check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information
12Standard CTI Use permission removed. Users associated with applications are required to be included in "Standard CTI Enabled" user group. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information

Error Message

%: %[LoginUserId=String][SeqNumber=Long][Version=String][CTIconnectionId=Long][IPAddress=String][IPv6Address=String][CmAssignedAppID=Long][AppID=String][ClusterID=String][NodeID=String]: CTI application connection opened..

Explanation   Application opened the provider successfully. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode.

Recommended Action   This alarm is for informational purposes only; no action is required.

Error Message

%: %[CmNodeID=Long][AppID=String][ClusterID=String][NodeID=String]: Unable to communicate with the Cisco CallManager service.

Explanation   CTI cannot communicate with Cisco CallManager service to register supplementary service features

Recommended Action   Check the status of the Cisco CallManager service in Cisco Unified Serviceability > Tools > Control Center - Featured Services. At least one Cisco CallManager service should be running in the cluster for CTIManager to register feature managers. Restart the CTIManager service if the problem persists. If CallManager service is active, verify network connectivity between the Unified CM node that hosts CTIManager service and Unified CM node that hosts CallManager service

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: CTI heartbeat timed out; application disconnected.

Explanation   CTI heartbeat timeout occurred causing CTIManager to close the application connection

Recommended Action   Heartbeat timeout could occur due to high CPU usage or network connectivity problems. Check for and fix any network issues or high CPU usage on the application server. If the application server is running the Microsoft Windows OS use Task Manager or Perfmon to determine the CPU usage. For applications in Linux use the top command to review CPU usage

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: CTI Peer Certificate Expired; Application Disconnected.

Explanation   CTI Peer certificate expired causing CTIManager to close the application connection

Recommended Action   The validity period of the peer certificate used for making SSL connection is expired. Please update the certificate

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: CTI Peer Certificate will expire soon; If expired, application will disconnect.

Explanation   CTI Peer certificate expire soon.

Recommended Action   The validity period of the peer certificate used for making SSL connection will expire soon. Please update the new certificate for getting continous service

Error Message

%: %[MsgVersion=VoidPtr][CompatibleVersions=VoidPtr][CurrentVersion=VoidPtr][CMVersion=String][IPAddress=String][IPv6Address=String][AppID=String][ClusterID=String][NodeID=String]: Incompatible protocol version.

Explanation   The JTAPI/TAPI application version is not compatible with this version of CTIManager, so the received message has been rejected. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode

Recommended Action   Verify that the correct version of the application is being used. If you're unsure of the correct version, contact the application vendor and upgrade the JTAPI/TSP to the version provided by Cisco Unified Communications Manager. JTAPI/TSP plugins are available in Cisco Unified CM Administration (Application > Plugins)

Error Message

%: %[DeviceName=String][SeqNumber=Long][DeviceId=Long][DeviceType=Long][CTIconnectionId=Long][MediaControlled=Bool][AssociatedCMIPAddr=String][CmAssignedAppID=Long][AppID=String][ClusterID=String][NodeID=String]: Device opened.

Explanation   Application opened a device

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%: %[DeviceName=String][DeviceId=Long][DeviceType=Long][CTIconnectionId=Long][MediaControlled=Bool][AssociatedCMIpAddr=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: Device closed.

Explanation   Application closed a device

Recommended Action   This alarm is for informational purposes only; no action is required

Reason Code - Enum Definitions

Enum Definitions - Reason

ValueDefinition
0Unknown
1CallManager service is not available to process request; verify that the CallManager service is active. Check the Cisco Unified Serviceability Control Center section in Cisco Unified CM Administration (Tools > Control Center - Feature Services)
2Device has unregistered with Cisco Unified Communications Manager
3Device failed to rehome to Cisco Unified Communications Manager; verify that the device is registered
4Device is removed from the Unified CM database
5Application controlling the device has closed the connection
6Route Point already registered by another application
7CTI Port already registered by another application
8CTI Port/Route Point already registered with dyamic port media termination
9Enabling softkey failed for device; verify that the device is registered
10Multiple applications have registered the device with media capability that do not match
11This device is already controlled by another application
12Protocol used by the device is not supported
13Device is restricted for control by any application
14Unable to communicate with database to retrieve device information
15Device is resetting
16Unable to register the device as specified media type is not supported
17Unsuppported device configuration
18Device is being reset
19IPAddress mode does not match what is configured in Unified CM

Error Message

%: %[CTIconnectionId=Long][DeviceName=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: Device Open failed.

Explanation   Application is unable to open the device

Recommended Action   Check the reason code and take appropriate action to resolve the issue

Reason Code - Enum Definitions

Enum Definitions - Reason

ValueDefinition
0x8CCC ()Device is already opened by another application; identify the application that is controlling this device. You can determine this information from RTMT (CallManager->CTI Manager and CallManager->CTI Search)
0x8CCC00DA ()Unable to communicate with database; verify the CPU utilization is in the safe range for (this can be monitored using RTMT via CPU Pegging Alert)
0x8CCCA ()Device is unregistering; wait for the device to register. Due to user initiated reset or restart of the device from Unified CM. Device should automatically register wait for few moments for the device to register
0x8CCC ()Device is not in the user control list; verify whether the device is configured for control by this application. For the application to control the device it should be included in the user control list. To check whether the device is in the user control list, if the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User)
0x8CCC00F3 ()IPAddress mode (IPv4 or IPv6 or both) specified by the application does not match with IP Addressing mode that is configured in Unified CM Administration; check the IP addressing mode of the device in Cisco Unified CM Administration (Device > Device Settings > Common Device Configuration)

Error Message

%: %[DeviceId=Long][CTIconnectionId=Long][DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Device is out of service.

Explanation   Device is out of service

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%: %[DeviceId=Long][CTIconnectionId=Long][DeviceName=String][callManagerId=Long][AppID=String][ClusterID=String][NodeID=String]: Device in service..

Explanation   Device is back in service

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%: %[SeqNumber=Long][DirNum=String][Partition=String][DeviceName=String][CTIconnectionId=Long][AppID=String][ClusterID=String][NodeID=String]: Line opened.

Explanation   Application opened the line

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%: %[CTIconnectionId=Long][DeviceName=String][DirNum=String][Partition=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: Unable to open the line.

Explanation   Application is unable to open the line

Recommended Action   Review the reason code and take appropriate action to resolve the issue

Reason Code - Enum Definitions

Enum Definitions - Reason

ValueDefinition
0Unknown
0x8CCC ()Device is not in the user control list; verify whether the device is configured for control by this application. For the application to control the device it should be included in the user control list. To check whether the device is in the user control list, if the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User)
0x8CCC ()Line is not found in the device; possible cause could be that the line that previously existed on this device is not available. This could be due to a extension mobility login or logout
0x8CCC00D3 ()Administrator has restricted the Line to be controllable by application. If the intent of the Administrator is to allow control of this line, enable the check box labelled Allow control of Device from CTI, in Unified CM Administration under Call Routing > Directory Number and choose the line that should be controlled by this application

Error Message

%: %[DirNum=String][Partition=String][CTIconnectionId=Long][DeviceName=String][Reason=Enum][AppID=String][ClusterID=String][NodeID=String]: Line closed..

Explanation   Application closed the line

Recommended Action   This alarm is for informational purposes only; no action is required

Reason Code - Enum Definitions

Enum Definitions - Reason

ValueDefinition
0Unknown
1CallManager failure
2Device has unregistered with Cisco Unified Communications Manager; wait for the device to register
3CTI failed to rehome the line; verify that the device is registered
4Undefined line, possible cause could be that line is no more active on that device due to extension mobility login or logout
5Device removed
6Provider controlling the device is closed
7Protocol used by the device is not supported
8Application cannot control this line as CTI Allow Control is not enabled. Administrator has restricted the Line to be controllable by application. If the intent of the Administrator is to allow control of this line, enable the check box labelled Allow control of Device from CTI, in Unified CM Administration under Call Routing > Directory Number and choose the line that should be controlled by this application
9Unable to register the device; application specified media type is not supported
10Device is being reset; verify that the device is registered before opening the line
11Unsuppported device configuration

Error Message

%: %[DirNum=String][Partition=String][CTIconnectionId=Long][DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Line is out of service.

Explanation   Line is going out of service

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%: %[LineId=Long][CTIconnectionId=Long][AppID=String][ClusterID=String][NodeID=String]: Line in service.

Explanation   Line is back in service

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%: %[DirNum=String][AppID=String][ClusterID=String][NodeID=String]: Error in setting message waiting indicator.

Explanation   An error occurred when setting the message waiting indication (MWI) lamp

Recommended Action   The line issuing the request to set the MWI lamp on the target line might not have the proper partitions/calling search space settings to allow it to reach the target line. Check the partitions and calling search space of the line that is requesting to set MWI on the target line. The target line should be able to receive a call from the line that is attempting to set MWI

Error Message

%: %[SeqNumber=Long][DirNum=String][Partition=String][AppID=String][ClusterID=String][NodeID=String]: Request from application to redirect a call has failed.

Explanation   CTIManager is unable to redirect a call

Recommended Action   This alarm is for informational purposes only; no action is required

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Application has opened more devices than allowed.

Explanation   An application has opened more devices than the limit set in the CTIManager service parameter, Maximum Devices Per Provider

Recommended Action   The application is controlling more devices than the CTI support allows. Review the application configuration and remove devices that are not required to be controlled. The stability of the system will be impacted if the application does not restrict support to the device limit specified by CTI in the CTIManager service parameter, Maximum Devices Per Provider

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Application has opened more devices than the limit for each node.

Explanation   An application has opened more devices than the limit set in the CTIManager service parameter, Maximum Devices Per Node.

Recommended Action   One or more applications are controlling more devices than the CTI support allows on the specified Unified CM node. Review the application configuration and remove devices that are not required to be controlled. The stability of the system will be impacted if the total number of devices controlled by applications is not properly restricted to the device limit specified by the CTIManager service parameter, Maximum Devices Per Node

Error Message

%: %[CTIConnectionType=String][InstanceNumber=Long][AppID=String][ClusterID=String][NodeID=String]: CTIManager is unable to allow connections from Applications..

Explanation   CTIManager is unable to accept connections from applications

Recommended Action   CTIManager has encountered problems initializing TCP connections. Restart the CTIManager service to resolve this problem

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: OutputQbeMessage: length mismatch..

Explanation   QBE header length mismatch exists.

Recommended Action   This alarm indicates that TSP/JTAPI is incompatible with the version of CTIManager. Contact the support organization for the affected application, install the JTAPI or TSP plugin and restart the application. JTAPI/TSP plugins are available from the Find and List Plugins window in Cisco Unified CM Administration (Application > Plugins).

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: InvalidQBESizeAndOffsets; QBE message decoding encountered illegal size or offset..

Explanation   QBE Packet received from the application is not encoded correctly.

Recommended Action   A TSP/JTAPI interface error occurred; the QBE message may not be formatted correctly. TSP/JTAPI might be incompatible with the version of CTIManager. Install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Unable to register CtiLine with SSAPI..

Explanation   CTI cannot register CtiLine with SSAPI.

Recommended Action   Check the status of the Cisco CallManager service in Cisco Unified Serviceability > Tools > Control Center - Featured Services. At least one Cisco CallManager service should be running in the cluster for CTIManager to register feature managers. Restart the CTIManager service if the problem persists.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Socket connection has been broken..

Explanation   The TCP connection has been lost.

Recommended Action   Although connection to the application is lost, no action is required if lost connection was intentional. If loss of connectivity was unintentional, investigate what might have caused connectivity to be lost and restore the connection.

Error Message

%: %[SeqNumber=Long][AppID=String][ClusterID=String][NodeID=String]: CTI directory login failure..

Explanation   CTI Manager is unable to login to directory. As a result, the application may not be able to access the controlled device list.

Recommended Action   In Cisco Unified CM Administration, verify that the correct username and password has been configured and is being used for CTIManager login. If LDAP is used for authentication, check to confirm that the LDAP synchronization is configured and is working.

Error Message

%: %[LoginUserId=String][DeviceName=String][DeviceType=Long][AppID=String][ClusterID=String][NodeID=String]: DeviceOpenRequest failure..

Explanation   Application is trying to access a device that is not in its control.

Recommended Action   Check the application sending the request or add the device to the user control list.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Illegal QBE header..

Explanation   Because of illegal QBE header, QBE message has been rejected.

Recommended Action   QBE header could be fragmented due to TCP fragmentation. Review your network configuration to fix any TCP fragmentation issue.

Error Message

%: %[SeqNumber=Int][DirNum=String][Partition=String][DeviceName=String][UserName=String][AppID=String][ClusterID=String][NodeID=String]: Line open failed..

Explanation   Application failed to open a line.

Recommended Action   Add the device associated with the line to the user device control list.

Error Message

%: %[EnumHandle=Long][EnumObjectType=String][AppID=String][ClusterID=String][NodeID=String]: Enumeration handle is not valid..

Explanation   The enumeration handle associated with the process of enumerating devices, lines or DNs is invalid.

Recommended Action   Check whether all devices, lines or DNs configured for the application are available to the application. If the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User).

Error Message

%: %[CTIConnectionType=String][InstanceNumber=Long][QBEMessageLength=Long][AppID=String][ClusterID=String][NodeID=String]: Incoming QBE message exceeds input buffer size.

Explanation   An incoming QBE message exceeds the input buffer size and then gets dropped.

Recommended Action   The size of the QBE packet could exceed the suggested size when the JTAPI/TSP version is not compatible with the version of CTIManager. Contact the application vendor and verify that the application is compatible with the version of Cisco Unified Communications Manager (Unified CM). If the application vendor requests you to, install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.

Error Message

%: %[PDU_Number=Long][AppID=String][ClusterID=String][NodeID=String]: TranslateCtiQbeInputMessage: NULL TCP HANDLE!!! (QBE packet is dropped).

Explanation   A null TCP handle is preventing the QBE packets to be reported to applications.

Recommended Action   This problem typically happens due to a network connectivity failure. Check for and resolve any connectivity issues in your network.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Directory change notification request time out..

Explanation   CTIManager registration request to EnvProcDevList timed out; CTIManager will send another registration request.

Recommended Action   Check and resolve network connectivity problems between Cisco Unified Communications Manager nodes.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: MYTCP_Send: send error..

Explanation   TCP socket connection has been broken.

Recommended Action   This problem occurs when an application is abruptly shut down or has lost network connectivity to CTIManager. Review your application and network connectivity and resolve any issues.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to create an internal process that is required to service CTI applications..

Explanation   An unexpected internal SDL error caused a failure in creating CTIManager Service SDL Process.

Recommended Action   An internal CTIManager error has occurred. Try Restarting the CTIManager service to resolve this problem, if it does resolve the problem restart the Unified CM Server.

Error Message

%: %[ErrorCode=Int][AppID=String][ClusterID=String][NodeID=String]: CTIManager service is unable to initialize TCP connection.

Explanation   CTIManager service is unable to initialize TCP connection

Recommended Action   CTIManager has encountered difficulty initializing TCP connections. Restart the CTIManager service to resolve this problem.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: ProviderOpenRequest; illegal filter size..

Explanation   ProviderOpenRequest has an illegal filter size.

Recommended Action   The application is using an incompatible version of JTAPI/TSP and Cisco Unified Communications Manager. Install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Possible internal array overflow condition while generating CTI NewCall event..

Explanation   An unexpected internal error occurred.

Recommended Action   Restart the CTIManager service if the problem persists.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Possible internal array overflow condition while generating CTI ExistingCall event..

Explanation   An unexpected internal error occurred.

Recommended Action   Restart the CTIManager service if the problem persists.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Possible internal array overflow condition while generating response to application request for call information..

Explanation   An unexpected internal error occurred.

Recommended Action   Restart the CTIManager service if the problem persists.

Error Message

%: %[CTIConnectionType=String][InstanceNumber=Long][AppID=String][ClusterID=String][NodeID=String]: Connection handle is not valid..

Explanation   A message has been received from an unknown connection, and then dropped.

Recommended Action   This alarm occurs when a QBE packet is received from a connection that is already disconnected. This packet will be ignored by CTIManager and no action is required.

Error Message

%: %[UserNameSize=Long][AppID=String][ClusterID=String][NodeID=String]: Invalid userName size in ProviderOpen request..

Explanation   User name length is invalid.

Recommended Action   Ask user of CTI application to use correct userName and to check the user name in configuration. It should not be more than 31 characters.

Error Message

%: %[AdditionalInfo=String][AppID=String][ClusterID=String][NodeID=String]: Database connection failed..

Explanation   An attempt to connect to database failed.

Recommended Action   Enable trace for the database layer monitor to get specific error information.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: No database connection available..

Explanation   Database layer could not find any working database connection.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Check network connectivity and operation of SQL Server services.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: A change notification client is busy (blocked). If the change notification client continues to be blocked for 10 minutes, the system automatically clears the block and change notification should resume successfully..

Explanation   Changes made to the database are not being consumed by one of the recipients. This does not always represent an issue. However, if the change notification client continues to be blocked for 10 minutes, the system automatically clears the block for all clients except the blocked one, which means that change notifications should resume successfully for all other clients. To clear the blocked client, you must restart the server.

Recommended Action   At the command line interface (CLI) on the database server, execute the following command: show tech notify. The CLI command output will provide information about the block. Use Cisco Unified Serviceability to restart the server that was indicated in the alarm. You may also want to gather traces to examine them for anomalous activity during the time that client was blocked. In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Could not read installed RPMs to populate component version table.

Explanation   The function that reads the rpm version information and populates database failed

Recommended Action   Please report this error to the administrator.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: A change notification client was responding slowly and has been removed..

Explanation   A change notification recipient hasn't responded to change notification in several minutes and was thus removed. This may delay call processing features, such as call forwarding and so on.

Recommended Action   Rebooting the box will clear this situation. Alternatively, dbnotify trace could be analyzed to find the client that was removed and that service could be restarted in Cisco Unified Serviceability.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: A change notification shared memory reconciliation has occurred..

Explanation   The change notification buffers in shared memory have been rebuilt due to conflicts.

Recommended Action   This problem may have been already corrected. If unexpected behavior is observed, restart all Cisco services in the cluster.

Error Message

%: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Indicates debug events from IDS database engine..

Explanation   This alarm provides low-level debugging information from IDS database engine. System administrator can disregard this alarm.

Recommended Action   This is for debug information purposes only; no action is required.

Error Message

%: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: No error has occurred but some routine event completed in IDS database engine..

Explanation   This alarm is informational. No error has occurred but some routine event completed in IDS database engine.

Recommended Action   This is for information purposes only; no action is required.

Error Message

%: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Pay Attention. This alarm does not compromise data or prevent the use of the system..

Explanation   Pay Attention. This alarm does not compromise data or prevent the use of the system.

Recommended Action   This alarm needs monitoring by the db admin

Error Message

%: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause IDS to fail.

Explanation   This alarm indicates combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause IDS to fail

Recommended Action   Requires db admin intervention

Error Message

%: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Information about IDS replication.

Explanation   This alarm provides information about IDS replication.

Recommended Action   Informational purposes only; no action is required

Error Message

%: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Combined alarm for emergency and error situations. IDS Replication has failed.

Explanation   This alarm indicates combined alarm for emergency and error situations. It indicates failure in IDS Replication

Recommended Action   Requires db admin intervention

Error Message

%: %[class_id=String][class_msg=String][specific_msg=String][AppID=String][ClusterID=String][NodeID=String]: Combined alarm for Integration, CUP import files has failed.

Explanation   Combined alarm for Integration, CUP import files has failed

Recommended Action   Check the network and files in the CUP server

Error Message

%: %[user=String][AppID=String][ClusterID=String][NodeID=String]: An application or endpoint is using too many database resources.

Explanation   This alarm indicates an error situation. Resources are not exhausted. The application will not be granted more connections to the database until the ones used are freed up.

Recommended Action   Collect the trace using file get activelog cm/trace/dbl/sdi/limitexceeded*sprers.eu or by collecting the Cisco Database Layer Monitor trace in RTMT to determine the application or endpoint causing issues.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Out of memory..

Explanation   The process has requested memory from the operating system, and there was not enough memory available.

Recommended Action   No action is required.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Permission has been denied..

Explanation   An operation could not be completed because the process did not have authority to perform it.

Recommended Action   This alarm is for information purposes only; no action is required.

Error Message

%: %[ServiceName=String][AppID=String][ClusterID=String][NodeID=String]: Service is not installed..

Explanation   An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s.

Recommended Action   Reinstall the service.

Error Message

%: %[IPAddress=String][Hostname=String][ServiceName=String][ProcessID=ULong][AppID=String][ClusterID=String][NodeID=String]: Service stopped..

Explanation   A service has stopped.

Recommended Action   This alarm is for information purposes only; no action is required.

Error Message

%: %[ProcessID=ULong][IPAddress=String][IPV6Address=String][Hostname=String][ServiceName=String][VersionInfo=String][AppID=String][ClusterID=String][NodeID=String]: Service started..

Explanation   A service has started.

Recommended Action   This alarm is for information purposes only; no action is required.

Error Message

%: %[ServiceName=String][AppID=String][ClusterID=String][NodeID=String]: Service startup failure..

Explanation   An attempt to start the specified service failed.

Recommended Action   Restart the service.

Error Message

%: %[PrimaryFilePath=String][AppID=String][ClusterID=String][NodeID=String]: Cannot write into a file..

Explanation   Failed to write into the primary file path.

Recommended Action   Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Error reading enterprise default user locale configuration.

Explanation   A database exception was encountered when reading the default Enterprise User Locale setting. Default of US English will be used.

Recommended Action   Verify that the Enterprise parameter setting for User Locale is configured using the CCM Admin web page. Restart the Cisco IP Voice Media Streaming App service.

Error Message

%: %[CID=ULong][PID=ULong][IP=String][Port=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN stream ICMP port unreachable error..

Explanation   An announcement RTP stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This ICMP error is a result of the destination end-point not having the receiving UDP/RTP port open to receive packets.

Recommended Action   No action is required. This may occur at times when connections are being stopped or redirected.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: ANN device record not found..

Explanation   A device record for the announcer device was not found in the database. The ANN device is normally automatically added when the server is added to the database.

Recommended Action   To add the ANN device to database you will need to remove/delete the server and re-add the server. WARNING: This may result in having to manually reconfigure many different settings such as Media Resource Groups, CallManager Groups and many others.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: WAV playing manager thread creation failed.

Explanation   The process component used for playing WAV files failed to start, possibly due to low system resources.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart server.

Error Message

%: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: ANN device recovery create failure..

Explanation   The ANN device startup failed, possibly due to lack of memory. If the error code is non-zero it may help determine the cause of the error. The announcement device will not be available.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart server.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read ANN device Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read ANN device Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read ANN device Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read ANN device configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read ANN device configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read ANN device configuration information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Enterprisewide configuration exception.

Explanation   An unknown exception occured reading Enterjprisewide configuration settings.

Recommended Action   Verify the enterprise configuration settings and restart the IP Media Streaming Service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Unknown Configuration Exception.

Explanation   An exception error was generated reading the service parameter settings.

Recommended Action   Restart the server.

Error Message

%: %[Description=String][AppID=String][ClusterID=String][NodeID=String]: Configuration COM Exception.

Explanation   A COM exception error was generated reading the service parameter settings for devices.

Recommended Action   Verify that service parameters can be viewed using CCM Administration. If they can then restart the service or server.

Error Message

%: %[Description=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Configuration DBL Exception.

Explanation   An exception error was generated reading the service parameter settings for devices.

Recommended Action   Verify that service parameters can be viewed using CCM Administration. If they can then restart the service or server.

Error Message

%: %[Field=String][Value=String][AppID=String][ClusterID=String][NodeID=String]: ANN device configuration not found.

Explanation   A service parameter for Cisco IP Voice Media Streaming App service related to the ANN device configuration was not found. The system will start with the given default setting.

Recommended Action   Review the service parameter settings and configure the ANN device settings properly using the CUCM Administration.

Error Message

%: %[Requested=ULong][Allocated=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN requested streams failure..

Explanation   The requested resources for the configured number of annunciator calls (Call Count service parameter) was not available. If the value shown as "Allocated" is non-zero

Recommended Action   Verify the ANN Call Count service parameter is correct. A server restart may be needed to recover resources.

Error Message

%: %[Error=ULong][ErrorText=String][Path=String][AppID=String][ClusterID=String][NodeID=String]: ANN create local path error.

Explanation   Unable to create a subdirectory to contain announcement files. This may be caused by insufficient disk storage. Announcements may not play correctly as a result of this error.

Recommended Action   Check for available free space on the common data storage area. If full, take action to remove old trace files to free space. Restart the Cisco IP Voice Media Streaming App service.

Error Message

%: %[Error=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP event wait error.

Explanation   An error was reported while waiting for a list of events. Announcement files will not be automatically updated.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service. If the error continues, restart the serverr.

Error Message

%: %[ExceptionCode=ULong][AXReg=ULong][BXReg=ULong][CXReg=ULong][DXReg=ULong][SIReg=ULong][DIReg=ULong][IPReg=ULong][SPReg=ULong][BPReg=ULong][Flags=ULong][CSSeg=ULong][DSSeg=ULong][ESSeg=ULong][SSSeg=ULong][FSSeg=ULong][GSSeg=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP transfer exception failure.

Explanation   An unknown program exception has caused the background TFTP file transfer processing for announcement files to terminate. Announcement files will not be automatically updated.

Recommended Action   Restart the Cisco IP Media Streaming App service and if the problem continues, report it to Cisco. Include CMS traces and Application Event log.

Error Message

%: %[Error=ULong][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP transfer thread creation failed.

Explanation   The ANN background TFTP file transfer processing thread failed to create possibly due to low system resources.

Recommended Action   Reboot server.

Error Message

%: %[Filename=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP COM exception.

Explanation   A COM exception occured while processing the specified file.

Recommended Action   Review the file for possible format errors or missing elements.

Error Message

%: %[Filename=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: ANN XML parsing error.

Explanation   There is a syntax error in the specified file.

Recommended Action   Correct the syntax error.

Error Message

%: %[Filename=String][AppID=String][ClusterID=String][NodeID=String]: ANN XML invalid element .

Explanation   There is an invalid element in the specified file.

Recommended Action   Correct the error.

Error Message

%: %[Filename=String][AppID=String][ClusterID=String][NodeID=String]: ANN TFTP file missing.

Explanation   A file was not found on the TFTP server to be downloaded to the announcement server.

Recommended Action   Correct the error.

Error Message

%: %[FileName=String][AppID=String][ClusterID=String][NodeID=String]: TFTP start file transfer failed.

Explanation   Unable to start transfering a file from TFTP server.

Recommended Action   Verify the file name exists on the TFTP server.

Error Message

%: %[TFTPServer=String][AppID=String][ClusterID=String][NodeID=String]: Unable to create TFTP client.

Explanation   Unable to create a client TFTP session with the TFTP server.. This may be due to the server not running, or an incorrect server name configuration setting in service paramenters. This operation will be retried periodically.

Recommended Action   Verify the TFTP server is operating and configuration settings are correct.

Error Message

%: %[Error=ULong][ErrorText=String][FileName=String][AppID=String][ClusterID=String][NodeID=String]: Open announcement file failed.

Explanation   An error was reported when attempting to open an announcement file for reading.

Recommended Action   Verify the file exists and the Cisco IP Voice Media Streaming App service has proper access rights to open the file for reading.

Error Message

%: %[LocaleID=ULong][Type=String][AppID=String][ClusterID=String][NodeID=String]: Unknown ANN Locale.

Explanation   The requested Locale for an announcement is not installed. For network locale you use the platform CLI interface to run (run sql select * from typecountry where enum = #), #=locale. This will tell you what country locale is being requested.

Recommended Action   Install the locale package or check device settings for an incorrect locale value.

Error Message

%: %[Locale=ULong][AnnID=ULong][AppID=String][ClusterID=String][NodeID=String]: Requested announcement not found.

Explanation   The requested announcement is unknown. This may be caused by using an incorrect announcement identifier for a custom announcement. Use the CUCM Admin to view a list of custom announcement identifiers and verify the correct one is being used.

Recommended Action   Correct the announcement identifier chosen from the custom announcement list.

Error Message

%: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: CFB device recovery create failure..

Explanation   The CFB device startup failed, possibly due to lack of memory. If the error code is non-zero it may help determine the cause of the error. The conference bridge device will not be available.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart server.

Error Message

%: %[MohAudioSourceFileName=String][MohAudioSourceId=UInt][Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Music On Hold Audio Source file cannot be opened.

Explanation   This alarm occurs when Music On Hold fails because the MOH audio source file cannot be opened. The caller will hear silence instead of the desired Music on Hold audio.

Recommended Action   Use the CUCM Administration interface for "MOH Audio File Management" on this specific MOH CUCM server to check that the Music On Hold Audio Source file has been uploaded to this specific server. Note that MOH audio files must be uploaded using the CUCM Administration page of each MOH server in the cluster before that server can play the audio file. If you need to upload the file you will need to reset this MOH device after the upload so it will be accessable by the MOH device.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: CFB device record not found..

Explanation   A device record for the software conference bridge device was not found in the database. The CFB device is normally automatically added when the server is added to the database.

Recommended Action   To add the CFB device to database you will need to remove/delete the server and re-add the server. WARNING: This may result in having to manually reconfigure many different settings such as Media Resource Groups, CallManager Groups and many others.

Error Message

%: %[Field=String][Value=String][AppID=String][ClusterID=String][NodeID=String]: CFB device configuration not found..

Explanation   A service parameter for Cisco IP Voice Media Streaming App service related to the CFB device configuration was not found. The system will use the given default setting.

Recommended Action   Review the service parameter settings and configure the CFB device settings properly using the CUCM Administration.

Error Message

%: %[CID=ULong][PID=ULong][IP=String][Port=ULong][AppID=String][ClusterID=String][NodeID=String]: CFB stream ICMP error..

Explanation   A SW CFB RTP stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This ICMP error is a result of the destination end-point does not have the receiving UDP/RTP port open to receive packets.

Recommended Action   No action is required. This may occur at times when connections are being stopped or redirected.

Error Message

%: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Database change notification subsystem not starting..

Explanation   The background process to activate database changes has failed to start. Database changes affecting the Cisco IP Voice Media Streaming App service will not automatically take effect.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service to get the DB notification reenabled.

Error Message

%: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Invalid notification event returned by database change notification..

Explanation   The change notification subsystem returned an invalid notification event. The Cisco IP Voice Media Streaming App service will terminate. The SW media devices (ANN, CFB, MOH, MTP) will be temporarily out of service and calls in progress may be dropped.

Recommended Action   Check the current status of the Cisco IP Voice Media Streaming App service and monitor for repeated occurances.

Error Message

%: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Database change notification restart failure..

Explanation   The change notification subsystem failed to restart.

Recommended Action   This service has change notification disabled, it may be reenabled at a later time or restart Cisco IP Voice Media Streaming App service to reenable immediately.

Error Message

%: %[Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creating audio source class failed..

Explanation   Unable to create audio source subcombonent to provide audio for streaming. This may be due to lack of memory.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%: %[AudioSourceID=ULong][CodecType=String][Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Stream Control create failure..

Explanation   Create stream control subcomponent. The error may possibly be due to lack of memory.

Recommended Action   Reset the MOH device. If continues to fail restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: IP TOS MediaResource to Cm value not found..

Explanation   The IP Type-of-Service Media Resource To Call Manager service parameter value was not found in the database. Defaulting its value to 0x60 for CS3(precedence 3) DSCP ().

Recommended Action   Set the Ip Type-of-Service Media Resource To Call Manager service parameter for the Cisco IP Voice Media Streaming App service.

Error Message

%: %[Error=String][AppID=String][ClusterID=String][NodeID=String]: IP voice media streaming device driver error..

Explanation   The IP voice media streaming device driver returned an error. This may indicate a significant media error or resource shortage.

Recommended Action   Restarting the Cisco IP Voice Media Streaming App service or possibly restarting the server may resolve the error condition.

Error Message

%: %[DeviceName=String][ServerNumber=ULong][ServerName=String][AppID=String][ClusterID=String][NodeID=String]: Device connection manager failed to start..

Explanation   The device controller was unable to start a connection to control device registration with CallManager. This is possibly due to lack of memory.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.

Error Message

%: %[DeviceName=String][TraceName=String][Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of device manager exit event failed..

Explanation   An error was reported when allocating an exit-control event for a SW media device. The device will not be registered with CallManager or active.

Recommended Action   This error may be due to a memory resource shortage. Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.

Error Message

%: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Unified Communications Manager in lockout..

Explanation   The specified Cisco Unified Communications Manager has failed to respond to control messages. The TCP control connection to CUCM is being suspended. This will cause a switch to another CUCM if one is available otherwise the device will be unavailable. There may be a shortage of CPU resource or some other error condition on the CUCM server.

Recommended Action   Check the status of the Cisco Unified Communications Manager service. You may have to restart the CUCM service or the CUCM server.

Error Message

%: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: More than 50 events returned from TCP link..

Explanation   The specified Cisco Unified Communications Manager TCP link has returned a large number of TCP events. This indicates an unexpected flood of events.

Recommended Action   No action is required. Monitor for reoccurance. This could be an indication of a security issue.

Error Message

%: %[TraceName=String][CID=ULong][PID=ULong][AppID=String][ClusterID=String][NodeID=String]: Open receive failure..

Explanation   The open receive channel failed. This may indicate a missmatch of media resources between Cisco Unified Call Manager and the Cisco IP Voice Media Streaming App service.

Recommended Action   Check the performance monitor counters for resource availability on CUCM and on Cisco IP Voice Media Streaming App. Also, you might run the Platform CLI command "Show Media Streams" to identify possible media connection resource leaks. Possibly reset the media device or restart Cisco IP Voice Media Streaming App or restart the CUCM server.

Error Message

%: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Cisco Unified Communications Manager not responding..

Explanation   The specified Cisco Unified Communications Manager is not responding to the keepalive messages. The connection with CUCM is being terminated and the media device will reregister with another Cisco Unified Call Manager if a secondary is configured. Otherwise, the media device will be unavailable until the device is able to reregister with CUCM.

Recommended Action   Cisco Unified Communications Manager may have gone down or is unable to respond. Check status of CUCM. The media device should automatically reregister.

Error Message

%: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Registered with Cisco Unified Communications Manager..

Explanation   The software media device registered with the specified Cisco Unified Communications Manager.

Recommended Action   No action is required.

Error Message

%: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Connection error with Cisco Unified Communications Manager..

Explanation   The media device was registered with the specified Cisco Unified Communications Manager and received a socket error or disconnect. This may occur normally when Cisco Unified Communications Manager is stopped.

Recommended Action   No action is required. The media device will reregister.

Error Message

%: %[DeviceName=String][TraceName=String][Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Create driver notification event failure..

Explanation   An error was returned when creating a signaling event for communication with the media streaming kernel driver. This may be due to memory or system resource shortage.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.

Error Message

%: %[DeviceName=String][TraceName=String][Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation socket event failure..

Explanation   An error was reported when creating a notification event for a socket interface. This may be due to a resource shortage. The media device will remain unavailable.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service and monitor for reoccurance or restart the CUCM server.

Error Message

%: %[TraceName=String][CID=ULong][PID=ULong][AppID=String][ClusterID=String][NodeID=String]: Start transmission failure..

Explanation   An error was encountered while starting an RTP transmission audio stream. This may indicate a missmatch of resources between Cisco Unified Communications Manager and Cisco IP Voice Media Streaming App service.

Recommended Action   Check the performance counters for the media resources on CUCM and Cisco IP Voice Media Streaming App to determine if there is a resource leak. You should also use the platform CLI command "Show Media Streams" to check for orphaned media RTP connections.

Error Message

%: %[TraceName=String][Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Wait call failure in device manager thread..

Explanation   An error was reported during a system request to wait on an event, the media device will be restarted.

Recommended Action   No action is required.

Error Message

%: %[DeviceName=String][TraceName=String][Error=Int][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of thread failure..

Explanation   An error was reported when starting a process for the specified media device. This may be due to a system resource shortage.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server to recover from this error.

Error Message

%: %[TraceName=String][AppID=String][ClusterID=String][NodeID=String]: Unregister with Cisco Unified Communications Manager..

Explanation   A media device has unregistered with the specified Cisco Unified Communications Manager.

Recommended Action   No action is required. The media device will automatically reregister.

Error Message

%: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Fixed MOH stream control failed to start..

Explanation   The audio stream control subsystem for the Fixed MOH audio source failed to start. Audio from the MOH Fixed audio source will not be provided for streaming out. This may be due to resource shortage such as memory or availability of the Fixed MOH audio source device.

Recommended Action   Reset MOH device, if failure continues restart the server. Monitor for errors in trace files and system log.

Error Message

%: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Fixed stream sound card interface failed to start..

Explanation   An error was encountered when starting the interface to access the sound card for providing MOH fixed audio. The audio source will not play possibly due to shortage of memory.

Recommended Action   Reset MOH device, or restart the Cisco IP Voice Media Streaming App service, or restart the server. Check the system log and possibly the traces for Cisco IP Voice Media Streaming App service.

Error Message

%: %[AudioSourceID=ULong][ErrorCode=ULong][ErrorCodeText=String][DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Fixed stream sound card interface initialization failure..

Explanation   Initialization of sound card failed. Fixed audio source will not play possibly due to missing or unconfigured USB sound device.

Recommended Action   Check that the USB sound is installed. Reset MOH device, or restart Cisco IP Voice Media Streaming App service, or restart the server. The system log and traces from Cisco IP Voice Media Streaming App may contain additionsl information.

Error Message

%: %[AudioSourceID=ULong][ErrorCode=ULong][ErrorCodeText=String][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Fixed input codec stream initialization failure..

Explanation   Initialization of sound card codec source transcoding process failed. The fixed audio source will not play possibly due to memory or resource shortage.

Recommended Action   Reset MOH device, or restart Cisco IO Voice Media Streaming App service, or restart server.

Error Message

%: %[AudioSourceID=ULong][ErrorCode=ULong][ErrorCodeText=String][AppID=String][ClusterID=String][NodeID=String]: Fixed input audio stream transcoder failure..

Explanation   An error was encountered while transcoding audio from the sound card. The audio source will not play possibly due an error accessing the sound card.

Recommended Action   Check that the USB sound device is properly installed. Unplug the USB sound device and replug back into the USB connector. Reset MOH device, restart Cisco IP Voice Media Streaming App service, or restart the server.

Error Message

%: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Get audio source file name failure..

Explanation   The Music-on-Hold audio source is not assigned to an audio file.

Recommended Action   Assign the audio source to an audio file or change the value of the MOH audio source to a value that has been configured.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Cisco IP voice media streaming driver not found..

Explanation   The Cisco IP voice media streaming driver was not found or is not installed. The Cisco IP Voice Media Streaming App service cannot run until this error is resolved. All software media devices (ANN, CFB, MOH, MTP) for this server will not be available.

Recommended Action   Check the system log for an error when the system attempted to load IpVms driver at the last server startup. A server restart is required to cause the driver to be loaded.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of required signaling event failed..

Explanation   An error was encountered when creating a signaling event component. This may be due to a resource shortage. The Cisco IP Voice Media Streaming App service will terminate.

Recommended Action   Check the trace files for more information. The service should automatically be restarted. If this error continues to reoccur the server may need to be restarted.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Error while waiting for asynchronous notifications of events..

Explanation   An error was reported while the primary control process for Cisco IP Voice Media Streaming App was waiting on asynchronous events to be signaled. The service will terminate and should automatically be restarted. This will cause a temporary loss of availability for the software media devices (ANN, CFB, MOH, MTP).

Recommended Action   Monitor the service and status of the software media devices. The service should automatically restart. If the problem continues, review the trace files for additional information. A server restart may be required if this repeats.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Unable to retrieve the local host server name..

Explanation   Unable to obtain the local host server name. The Cisco IP Voice Media Streaming App service will terminate. No software media devices (ANN, CFB, MOH, MTP) will be available while the service is stopped.

Recommended Action   Check the configuration settings for the server name, DHCP, or DNS. Monitor the status of Cisco IP Voice Media Streaming App service. The service will not operate without a valid server name.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Unable to retrieve the network IP address for host server..

Explanation   Unable to obtain the network IP (dotted) address. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while this service is stopped.

Recommended Action   Monitor the status of the Cisco IP Voice Media Streaming App service. It should be automatically restarted. If the error occurs again, check the server IP configuration (DHCP, IP address).

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of the IPVMSMgr thread failed..

Explanation   An error was encountered while starting a process thread. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while the service is stopped.

Recommended Action   Monitor the status of the Cisco IP Voice Media Streaming App service. It should automatically be restarted. If the error reoccurs, restart the server.

Error Message

%: %[Found=ULong][Need=ULong][AppID=String][ClusterID=String][NodeID=String]: Wrong version of device driver..

Explanation   An incompatible device driver was found. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while the service is stopped.

Recommended Action   Restart the server to ensure the most recent driver is started. If the error continues, then reinstall Cisco Unified Communications Manager to get the proper driver version installed.

Error Message

%: %[Version=String][IPAddress=String][Hostname=String][ServiceName=String][ProcessID=ULong][AppID=String][ClusterID=String][NodeID=String]: IP voice media streaming application starting..

Explanation   The Cisco IP Voice Media Streaming App service is starting.

Recommended Action   No action is required.

Error Message

%: %[Version=String][IPAddress=String][Hostname=String][ServiceName=String][ProcessID=ULong][AppID=String][ClusterID=String][NodeID=String]: The IP voice media streaming application shutting down..

Explanation   The Cisco IP Voice Media Streaming App service is shutting down.

Recommended Action   No action is required.

Error Message

%: %[AudioSourceID=ULong][ConferenceID=ULong][CodecType=String][IPAddress=String][Port=ULong][AppID=String][ClusterID=String][NodeID=String]: Invalid multicast IP address..

Explanation   An invalid multicast IP address (out of range) was found.

Recommended Action   Correct the setting on the Music-on-Hold device configuration for multicast address.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: MOH device record not found..

Explanation   A Music-on-Hold device was not found for this server. This device is normally automatically added when a server is added to the configuration.

Recommended Action   If Music-on-Hold functionality is required, you will need to remove and readd server to the database. WARNING: This may impact many other configuration settings (CM Groups, Media Resource Groups, etc).

Error Message

%: %[CID=ULong][PID=ULong][IP=String][Port=ULong][AppID=String][ClusterID=String][NodeID=String]: MOH stream ICMP error..

Explanation   A Music-on-Hold transmission stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This may occur occasionally depending on call termination sequences.

Recommended Action   No action is required.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Error starting MOH Audio source subcomponent..

Explanation   A error was encountered by the Music-on-Hold device while starting the sub-component that provides audio from files or sound card. This may be due to shortage of resources (memory).

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Creation of MOH manager exit event failed..

Explanation   An error was encountered when allocating a signaling event. This may be caused by a resource shortage.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Synchronization error detected in MOH audio manager..

Explanation   A synchronization error was detected. Condition has been resolved automatically.

Recommended Action   No action is required.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Wait call failure in MOH manager thread..

Explanation   An error was encountered in Music-on-Hold audio manager subcomponent while waiting for aynchronous event signaling. The MOH device will be restarted.

Recommended Action   No action is required.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Starting of MOH audio manager failed..

Explanation   An error was encountered when starting the Music-on-Hold audio manager subcomponent. Music-on-Hold audio services will not be avaliable.

Recommended Action   Restart the Cisco IP Voice Media Streaming App service.

Error Message

%: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Attempted to rewind an inactive MOH audio source..

Explanation   An attempt was made to rewind or restart the Music-on-Hold audio source that is inactive. This has been ignored.

Recommended Action   No action required.

Error Message

%: %[AudioSourceID=ULong][CodecType=String][AppID=String][ClusterID=String][NodeID=String]: Error rewinding MOH audio source that is not playing..

Explanation   An attempt was made to rewind or restart a Music-on-Hold wav file that was not being played. This has been ignored.

Recommended Action   No action is required.

Error Message

%: %[ErrorText=String][File=String][SrcPath=String][DstPath=String][OSError=Int][OSErrorText=String][AppID=String][ClusterID=String][NodeID=String]: Transfer of MOH source file to working path failed..

Explanation   An error was encountered when trying to copy or update a Music-on-Hold audio source file.

Recommended Action   Use the Platform CLI to verify the source path and file exist. If the file does not exist then use CUCMAdmin to reupload the missing audio source to this specific server. Reinstall the Cisco Unified Communications Manager to have all required paths created.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: MTP device record not found..

Explanation   A device record for the software media termination point device was not found in the database. This is normally automatically added to the database when a server is added to the database. The software MTP device will be disabled.

Recommended Action   If MTP functionality is required, you will need to delete the server and re-add the server back to the database using CCMAdmin. WARNING: This may require many additional configuration settings to be reapplied such as CallManager Groups, Media Resource groups and more.

Error Message

%: %[CallCount=ULong][RunFlag=String][AppID=String][ClusterID=String][NodeID=String]: MTP device configuration not found, starting with defaults..

Explanation   One or more Cisco IP Voice Media Streaming App service parameter settings for the MTP device were not found in the database. The default values are included here.

Recommended Action   Configure the service parameter settings for the MTP device.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read CFB configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read CFB configuration information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read CFB Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read CFB Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read CFB Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read CFB configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Get change notification port failure..

Explanation   The database layer was unable to find change notification port and is using default.

Recommended Action   If default change notification is incorrect or change notification does not work, add value into database and restart service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Database layer select my process node failed..

Explanation   The database layer was unable to find/determine the current node on which this service is running.

Recommended Action   Make sure the database is configured properly.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MOH audio sources.

Recommended Action   Audio sources will be disabled; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MOH audio sources.

Recommended Action   Audio sources will be disabled; fix database problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MOH audio sources.

Recommended Action   Audio sources will be disabled; fix problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MOH configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MOH configuration information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: MOH enabled codecs not found..

Explanation   The Music-on-Hold service parameter for codec selection could not be read from database. Defaulting to G mu-law codec.

Recommended Action   Set the Music-on-Hold service parameter for Cisco IP Voice Media Streaming App service.

Error Message

%: %[Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read clsterwide service parameters.

Recommended Action   MOH or ANN audio sources may be unavailable; fix problem and restart service.

Error Message

%: %[ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read clusterwide service parameters.

Recommended Action   MOH or ANN audio sources may be unavailable; fix database problem and restart service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while tring to read clusterwide service parameters.

Recommended Action   MOH or ANN audio sources may be unavailable; fix problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MOH Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MOH Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MOH Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MOH device information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MOH device information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MOH device information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: MOH TFTP IP address not found..

Explanation   The default MOH TFTP IP address was not found in the database.

Recommended Action   Audio sources may be unavailable; create proper value in database and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MOH configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MTP configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MTP configuration information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[DeviceName=String][Description=String][AppID=String][ClusterID=String][NodeID=String]: COM error..

Explanation   A COM error occurred while trying to read MTP Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][ExceptionStr=String][ExceptionID=ULong][AppID=String][ClusterID=String][NodeID=String]: Database exception..

Explanation   A database exception occurred while trying to read MTP Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix database problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MTP Cisco Unified Communications Manager list information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[DeviceName=String][AppID=String][ClusterID=String][NodeID=String]: Unknown exception..

Explanation   An unknown exception occurred while trying to read MTP configuration information.

Recommended Action   Device will not start; fix problem and restart service.

Error Message

%: %[Requested=ULong][Allocated=ULong][AppID=String][ClusterID=String][NodeID=String]: CFB requested streams failure..

Explanation   The resources for the number of requested full-duplex streams was not available.

Recommended Action   Verify the Cisco IP Voice Media Streaming App service parameter for number of CFB calls. Restart the server to reset the stream resources.

Error Message

%: %[Requested=ULong][Allocated=ULong][AppID=String][ClusterID=String][NodeID=String]: MOH requested streams failure..

Explanation   The resources for the number of requested streams was not available.

Recommended Action   Verify the number of calls configuration setting for Music-on-Hold device. Restart the server to reset the resources.

Error Message

%: %[Requested=ULong][Allocated=ULong][AppID=String][ClusterID=String][NodeID=String]: MTP requested streams failure..

Explanation   The resources for the number of requested full-duplex Media Termination Point streams was not available.

Recommended Action   Verify the Cisco IP Voice Media Streaming App service parameter setting for number of MTP calls is correct. Restart the server to reset the available resources.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: MOH device recovery create failure..

Explanation   An error was encountered restarting the Music-on-Hold device. This may be caused by a shortage of memory resources.

Recommended Action   Check the status of the Music-on-Hold device. If the MOH device is not registered and available, Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message

%: %[Error=ULong][ErrorText=String][AppID=String][ClusterID=String][NodeID=String]: MTP device recovery create failure..

Explanation   An error was encountered trying to restart the Media Termination Point device. This may be due to a shortage of application memory.

Recommended Action   Restart the IP Voice Media Streaming App service or restart the server.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Invalid Software License..

Explanation   There is no valid software license; the Cisco IP Voice Media Streaming App service requires a valid software license to operate.

Recommended Action   Install a valid software license and restart Cisco IP Voice Media Streaming App service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Valid Software License Found..

Explanation   A valid software license has been detected by the IP Voice Media Streaming App service.

Recommended Action   No action required. This informational message indicates alarm SoftwareLicenseNotValid is cleared.

Error Message

%: %[Filename=String][AnnouncementID=ULong][UserLocale=ULong][NetworkLocale=ULong][AppID=String][ClusterID=String][NodeID=String]: Announcement file not found..

Explanation   The annunciator was unable to access an announcement audio file. This may be caused by not uploading a custom announcement to each server in the cluster or a locale has not been installed on the server.

Recommended Action   Upload the custom announcement to the server or install the missing locale package.

Error Message

%: %[Devicename=String][AppID=String][ClusterID=String][NodeID=String]: Failed to initialize sRTP crypto..

Explanation   The media device shown in this alarm attempted to load and initialize crypto capabilities within the operating system kernel, however, a failure, such as the OS lacking encryption configuration, a memory shortage, or crypto self-test failure, occurred during initialization. Secure media encryption for this device has been disabled as a result, but unencrypted media is still supported. All media streams are non-secure (unencrypted) for this device. This alarm is capable of occurring when the crypto failure occurs because the Cisco IP Voice Media Streaming App service parameter Force Annunciator to be Non-secure or Force MOH to be Non-secure is enabled.

Recommended Action   Use the Cisco Unified Real-Time Monitoring Tool (RTMT) to retrieve the system log. Review the system log and respond to error messages containing sRTP or IpVms.

Error Message

%: %[ReasonCode=ULong][Identifier=String][Locale=String][AnnouncementEnum=ULong][FileName=String][CustomFileName=String][AppID=String][ClusterID=String][NodeID=String]: Unable to play a requested announcement or tone.

Explanation   Reason code explanations: [1] Announcement requested is undefined. The announcement enum number is unknown. [2] Locale requested is unknown. The requested locale has not been installed on this node. [3] The customized announcement file does not exist on this server node for the locale. If a default system announcement is assigned, it will be used in place of the customized announcement. [4] Internal annunciator resource shortage has caused the announcement to fail. [5] System announcement or tone file not found.

Recommended Action   Recommendations based on reason code: [1] this is usually a system design issue and cannot be resolved by normal means; [2] Be sure the requested locale is installed on each CUCM server node; [3] Upload the customized announcement wav file to this server node using CCM Administration on this node; [4] Review the annunciator device configuration for maximum number of calls and/or schedule an annunciator device reset as a temporary workaround to ensure orphanned resources are released or restart the Cisco IP Voice Media Streaming App service; [5] Check locale is installed on CUCM server node or possible missing file not installed properly.

Error Message

%: %[Error=Int][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Failed to create a new thread. See Reason string for where it failed..

Explanation   This usually happens when there are system issues such as running out of memory resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%: %[Error=Int][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Failed to update trace logging or alarm subsystem for new settings..

Explanation   This usually indicates a lack of system resources or a failure in database access by the trace logging or alarm subsystem.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm. Ensure that the database server is running, and that the Cisco Database Layer Monitor service is running without problems. If this alarm persists, contact the Cisco Technical Assistance Center (TAC) with TFTP service and database trace files.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to retrieve enterprise parameter values from database at TFTP service startup..

Explanation   This is usually caused by database access failure.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to build all device configuration files at TFTP service startup..

Explanation   This is usually caused by database access failure.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to allocate resources to handle configuration change notification from database..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to allocate resources to handle configuration change notification from database..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to start listening to configuration change notification from database..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to rebuild configuration files for changes in Cisco Unified Communications Manager Group settings..

Explanation   This is usually caused by a failure to access the Cisco Unified Communications Manager database.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to rebuild configuration files for changes at group level settings such as Device Pool or Common Device Config settings..

Explanation   This is usually caused by a failure to access the Cisco Unified Communications Manager database.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: An exception is caught in the main processing routine..

Explanation   This alarm is sent in conjunction with other alarms for failure when building configuration files or when the TFTP service is attempting to retrieve the values in the system's enterprise parameters.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP service. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: An exception is caught while retrieving enterprise parameters value from database at TFTP service startup..

Explanation   This is usually caused by a failure to access the Cisco Unified Communications Manager database.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Failed to retrieve enterprise parameter values from database when rebuilding all configuration files..

Explanation   This is usually caused by a failure to access the Cisco Unified Communications Manager database.

Recommended Action   In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: A complete rebuild of all device configuration files has failed..

Explanation   Probable causes of this alarm could be failure to access the Cisco Unified Communications Manager database, or misconfiguration of some devices.

Recommended Action   In Cisco Unified Serviceability, enabled Detailed level traces in the Trace Configuration window for TFTP and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message

%: %[nError=Int][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Failed to open network connection for receiving file requests..

Explanation   This usually happens when the IP address that the TFTP service uses to open the network connection is invalid.

Recommended Action   Verify that the TFTP service parameter, TFTP IP Address, accurately specifies the IP address of the NIC card to use for serving files via TFTP. See the help for the (advanced) TFTP IP Address service parameter for more information. If the problem persists, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%: %[nError=Int][IPAddress=String][Port=Int][AppID=String][ClusterID=String][NodeID=String]: Failed to increase the size of the network buffer for receiving file requests..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%: %[nError=Int][IPAddress=String][Port=Int][AppID=String][ClusterID=String][NodeID=String]: Fail to connect to the network port through which file requests are received..

Explanation   This usually happens if the network port is being used by other applications on the system or if the port was not closed properly in the last execution of TFTP server.

Recommended Action   Verify that the port is not in use by other application. After stopping the TFTP server, at the command line interface (CLI) on the TFTP server, execute the following command: show network status listen. If the port number specified in this alarm is shown in this CLI command output, the port is being used. Restart the Cisco Unified Communications Manager system, which may help to release the port. If the problem persists, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%: %[Error=String][AppID=String][ClusterID=String][NodeID=String]: No Cisco Unified Communications Manager (Unified CM, formerly known as Cisco Unified CallManager) node has been configured..

Explanation   A Cisco Unified Communications Manager Group exists but it has no Unified CM node configured as its group member.

Recommended Action   In Cisco Unified CM Administration (System > Cisco Unified CM Group), configure at least one Unified CM node for the Unified CM Group referenced in this alarm. The Unified CM Group is part of the device pool to which the specified phone belongs.

Error Message

%: %[FileName=String][AppID=String][ClusterID=String][NodeID=String]: Failed to create Config File on disk or update existing Config File on disk..

Explanation   This may happen if disk is full or the file is in use.

Recommended Action   Using RTMT, check the disk utilization and correct any issue discovered. If you do not discover a disk space issue, try restarting the TFTP service from Cisco Unified Serviceability (Tools > Control Center - Feature Services). Stopping and restarting the TFTP service is useful because the Config File that the TFTP service is trying to save might be an existing file that is in use. If you still get this error, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%: %[FileName=String][AppID=String][ClusterID=String][NodeID=String]: Failed to save Config File to disk..

Explanation   This may happen if disk is full or the file is in use.

Recommended Action   Using RTMT, check the disk utilization and correct any issue discovered. If you do not discover a disk space issue, try restarting the TFTP service from Cisco Unified Serviceability (Tools > Control Center - Feature Services). Stopping and restarting the TFTP service is useful because the Config File that the TFTP service is trying to save might be an existing file that is in use. If you still get this error, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%: %[ErrorNumber=Int][FileName=String][IPAddress_Port=String][Mode=String][OpCode=Int][Reason=String][AppID=String][ClusterID=String][NodeID=String]: There was an error during processing of file request..

Explanation   This could happen if the requested file is not found by the server, or other error indicated by the "Reason" clause when processing the file request.

Recommended Action   You can safely ignore this alarm if the reason shown in this alarm is "File not found" and if that file is the MAC address-based file name for a phone that you are auto-registering; in that case, the phone is not yet registered with the database and so it is normal for the phone's file not be found. In the case that auto-registration is disabled, this alarm shows that the phone or device is not added to Cisco Unified Communications Manager (Unified CM). Either add the phone to Unified CM or remove the phone from the network. If you still get this error after removing the phone(s), go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TFTP service and contact the Cisco Technical Assistance Center (TAC).

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Unknown exception was caught while processing file request..

Explanation   This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%: %[DeviceCount=Int][DeviceTime=Int][UnitCount=Int][UnitTime=Int][SoftkeyCount=Int][SoftkeyTime=Int][FeatureControlPolicyTime=Int][FeatureControlPolicyCount=Int][DialruleCount=Int][DialruleTime=Int][TotalTime=Int][BuildStatus=String][AppID=String][ClusterID=String][NodeID=String]: Device configuration files are being built..

Explanation   This alarm provides information about the BUILD ALL operation to build all types of configuration files.

Recommended Action   This alarm is for information purposes only; no action is required.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: IPv6 network interface is not installed..

Explanation   IPv6 option is enabled for TFTP service but the IPv6 network interface/address has not been configured on the system. Until the IPv6 network is functioning, devices that have been configured with IPv6-only will not be able to register. Devices that have been configured to use either IPv6 or IPv4 will register using IPv4. When the IPv6 network is online, IPv6-capable devices that have registered as IPv4 will remain IPv4 until they are reset, at which time they will use IPv6 if available.

Recommended Action   Install IPv6 network interface and then restart TFTP service.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: ITL file regeneration.

Explanation   This is for regeneration of ITLFile

Recommended Action   Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message

%: %[HostName=String][AppID=String][ClusterID=String][NodeID=String]: The IP Address for host was NOT RESOLVED.

Explanation   The IP Address for host was NOT RESOLVED

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There are no CallManager entries in the database..

Explanation   There are no CallManager entries in the database.

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was timeout during wait for DeActivateLoadShare acknowledgement.

Explanation   There was timeout during wait for DeActivateLoadShare acknowledgement

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the LineStateSrvEng Creation.

Explanation   There was an error during the LineStateSrvEng Creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the GlobalSPUtils creation.

Explanation   There was an error during the GlobalSPUtils creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the TapiLinesTable creation.

Explanation   There was an error during the TapiLinesTable creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the HuntGroupController creation.

Explanation   There was an error during the HuntGroupController creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the Hunt Group creation.

Explanation   There was an error during the Hunt Group creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the CallDirector creation.

Explanation   There was an error during the CallDirector creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the SysController creation.

Explanation   There was an error during the SysController creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the TimerServices creation.

Explanation   There was an error during the TimerServices creation

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: DBL GetVersionInfo function returned NULL.

Explanation   DBL GetVersionInfo function returned NULL

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Exception occured in InitSDIConfiguration function.

Explanation   Exception occured in InitSDIConfiguration function

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: There was an error during the SyncDB creation in SysController.

Explanation   There was an error during the SyncDB creation in SysController

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Connection to CallManager was lost.

Explanation   Connection to CallManager was lost

Recommended Action   NONE

Error Message

%: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: User successfully logged in..

Explanation   User successfully logged in.

Recommended Action   NONE

Error Message

%: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: User log in failed because of bad user id or password..

Explanation   User log in failed because of bad user id or password.

Recommended Action   NONE

Error Message

%: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: User is already logged in.

Explanation   User is already logged in

Recommended Action   NONE

Error Message

%: %[UserID=String][AppID=String][ClusterID=String][NodeID=String]: User logged out.

Explanation   User logged out

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Agent online.

Explanation   Agent online

Recommended Action   NONE

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Agent offline.

Explanation   Agent offline

Recommended Action   NONE

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application started .

Explanation   Application started successfully

Recommended Action   No action required.

Error Message

%: %[Userid=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: User is not Synced.

Explanation   While updating the data in db for User Db gave exception

Recommended Action   Check the reason for exception and proceed accordingly.

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application stopped.

Explanation   Application was unloaded from Tomcat

Recommended Action   Check if Tomcat service is up.

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application not started.

Explanation   Error occurred while starting application

Recommended Action   See application logs for error

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application error.

Explanation   IPMA application error

Recommended Action   See application logs for details

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Manager Logged out.

Explanation   IPMA Manager Logged out by application

Recommended Action   To re-login the user, click update in the CCMAdmin IPMA Service configuration page for this user.

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application overloaded.

Explanation   IPMA application overloaded

Recommended Action   See application logs for details

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Application filtering is down.

Explanation   IPMA Application filtering is down

Recommended Action   Restart Cisco IP Manager Assistant Service

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: IPMA Information .

Explanation   Application information

Recommended Action   No action required.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: BDI Application started .

Explanation   Application started successfully

Recommended Action   No action required.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: BDI Application stopped.

Explanation   Application was unloaded from Tomcat

Recommended Action   Check if Tomcat service is up.

Error Message

%: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: BDI Application not started.

Explanation   Error occurred while starting application

Recommended Action   See application logs for error

Error Message

%: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: BDI Application error.

Explanation   BDI application error

Recommended Action   See application logs for details

Error Message

%: %[Reason=String][AppID=String][ClusterID=String][NodeID=String]: BDI Application overloaded.

Explanation   BDI application overloaded

Recommended Action   See application logs for details

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer Application started .

Explanation   Application started successfully

Recommended Action   No action required.

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer Application stopped.

Explanation   Application was unloaded from Tomcat

Recommended Action   Check if Tomcat service is up.

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: Failed to startup WebDialer application.

Explanation   Error occurred while starting application

Recommended Action   See application logs for error

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer Application error.

Explanation   WebDialer application error

Recommended Action   See application logs for details

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer Application overloaded.

Explanation   WebDialer application overloaded

Recommended Action   See application logs for details

Error Message

%: %[ServletName=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: WebDialer informational alarm.

Explanation   WebDialer application informational alarm

Recommended Action   No action required

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Cisco DirSync Application started .

Explanation   Application started successfully

Recommended Action   No action required.

Error Message

%: %[AppID=String][ClusterID=String][NodeID=String]: Cisco DirSymc application failed to start successfully.

Explanation   Error occurred while starting application

Recommended Action   See application logs for error, may require restarting the application

Error Message

%: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process started on particular sync agreement.

Explanation   LDAPSync process started to sync user data on the configured agreement id

Recommended Action   No action required

Error Message

%: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed to start on particular sync agreement.

Explanation   LDAPSync process failed to start on the configured agreement id

Recommended Action   See application logs for error

Error Message

%: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process completed on particular sync agreement.

Explanation   LDAPSync process completed to sync user data on the configured agreement id

Recommended Action   No action required

Error Message

%: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process stopped manually on particular sync agreement.

Explanation   LDAPSync process stopped manually on the configured agreement id

Recommended Action   No action required

Error Message

%: %[AgreementId=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process stopped automatically on particular sync agreement.

Explanation   LDAPSync process stopped automatically on the configured agreement id, it will be restarted automatically

Recommended Action   No action required

Error Message

%: %[AgreementId=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed on particular sync agreement.

Explanation   LDAPSync process failed to sync user data on the configured agreement id

Recommended Action   No action required. The sync process will automatic retry See application logs for details

Error Message

%: %[AgreementId=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed on particular sync agreement.

Explanation   LDAPSync process failed to sync user data on the configured agreement id

Recommended Action   See application logs for details, the application will try to sync again in the next scheduled time

Error Message

%: %[AgreementId=String][LDAPHost=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed to connect to LDAP server.

Explanation   LDAPSync process failed to connect to LDAP host

Recommended Action   Please make sure the LDAP server is online. If SSL is used, please make sure the required certificate is available on local CM server. The application will automatically retry

Error Message

%: %[AgreementId=String][Reason=String][AppID=String][ClusterID=String][NodeID=String]: LDAPSync process failed to access local database.

Explanation   CiscoDirSync failed to access local database

Recommended Action

   Related: More > Error Logs


Problem

One of our SQL Servers was experiencing fatal errors on a frequent basis during batch processing. This was a SQL Server on Windows operating system. Here are some details of the error log which were captured:

A fatal error occurred while reading the input stream from the network. The session will be terminated (input error:output error: 0). Error:Severity: 20, State:


Fatal error shot captured in error log file
Solution

This fatal error suggests that something is wrong on the network which is causing network packets to drop. The error which is captured in the SQL Server error log can be due to different reasons. I searched this error on the web and found some MSDN forums where similar issues were discussed. Some responses suggested disabling the TCP/IP Chimney Offload feature, service call 121 fatal error, so I decided to research this further. Let's start with TCP/IP Chimney offloading, RSS features and NetDMA.

Microsoft released the Scalable Networking Pack (SNP) that consists of three main features. These three haspflt cant start driver error 1275 are TCP/IP Chimney, Receive Side Scaling (RSS) and NetDMA.

  • TCP/IP Chimney Offload, as per TechNet, is designed to take processing of the network such as packet segmentation and reassembly processing tasks, from a computer's CPU to a network adapter that supports TCP Chimney Offload. This has the effect of reducing the workload on the host CPU and moving it to the NIC, allowing both the Host OS to perform quicker and also speed up the processing of network traffic.
  • Receive Side Scaling (RSS) enables the network load from a network adapter to be distributed across multiple CPUs in a multiprocessor computer.
  • Network Direct Memory Access (NetDMA) provides services for offloading the memory copy operation that is performed by the networking subsystem to a dedicated direct memory access (DMA) engine when receiving network packets.

Now let's check these settings on our impacted system. We ran the below command to check the existing values of these SNP settings:

netsh int tcp show global

Checked TCP chimney offload

As we can see, all these settings were enabled as shown in the above screenshot. By default, TCP Chimney Offload is disabled in Windows and later versions, but sometimes vendor applications can turn them on. We can also check whether TCP Chimney Offload is working or not by running the netstat -t command.

I checked these settings on other production servers for the same application and found that these settings were disabled on those servers. See the below output of SNP settings on two production servers:

SERVER: DELHISQL01 TCP Global Parameters Receive-Side Scaling State : disabled Chimney Offload State : disabled NetDMA State : disabled Direct Cache Access (DCA) : disabled Receive Window Auto-Tuning Level : normal Add-On Congestion Control Provider : ctcp ECN Capability : disabled RFC Timestamps : disabled SERVER: DELHISQL02 TCP Global Parameters Receive-Side Scaling State : disabled Chimney Offload State : disabled NetDMA State : disabled Direct Cache Access (DCA) : disabled Receive Window Auto-Tuning Level : normal Add-On Congestion Control Provider : ctcp ECN Capability : disabled RFC Timestamps : disabled

The problem is that service call 121 fatal error NICs report to the OS that they support these features, which they indeed do, but many didn't perform these functions very well in reality. These SNP options looks good from an OS perspective, but due to misbehaving NIC drivers they turn into lot of weird issues so it is better to turn them off to fix such issues, get an update from the NIC scardtransmit error 22 or use a better NIC driver that can use these features in an effective way.

We should disable these SNP features in Windows and NIC hardware setting as well with the vendor's firmware tools if we don’t have an update for  the NIC driver or NIC drivers are not compatible with these features. We can check these settings in network adaptors by launching device manager and then expanding the network adaptors section as shown in the below screenshot.

SNP settings in <i>service call 121 fatal error</i> adaptors

Steps to Disable NIC Settings

So we decided to replicate the same settings (which were on other production servers) into our impacted server where the fatal errors were reported. We used this Microsoft article to disable the TCP/ IP Chimney, RSS and NetDMA state by using the below steps.

1: Open a command prompt with administrative privileges.

2: Run the below command to disable TCP/IP Chimney Offload.

netsh int tcp set global chimney=disabled

3: Run the below command to disable RSS.

netsh int tcp set global rss=disabled

4: NetDMA will be disabled through the registry, so make sure to backup your registry before doing the next service call 121 fatal error. To open the Registry Editor, click Start, click Run, type regedit, and then click OK.

5: Locate the registry sub-key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters and click on it.

6: Locate the EnableTCPA registry entry. If this registry entry does not exist, right-click service call 121 fatal error Parameters sub-key, point to New, and then click DWORD Value.

7: Replace the New Value #1 by typing EnableTCPA, and then press ENTER. Double-click the EnableTCPA registry value you just created and type 0 in the Value to disable NetDMA, service call 121 fatal error, and then click OK.

8: TCP Chimney Offload and Service call 121 fatal error will be disabled just after executing the above commands, but NetDMA requires a system reboot after making changes to the registry.

After the above changes and the reboot we can run the below command to check whether all these settings are disabled, which they are as shown below.

netsh int tcp show global

SNP settings disabled on windows

After we made these changes we no longer received any fatal errors. These features are error sil only 3/4 metadata to enhance the capability of Windows, but unfortunately it is not always useful if your NIC drivers do not support these features.

Next Steps
  • If you run into these errors, use the steps in this tip to see if these features are enabled for your NICs.
  • If you have advanced NIC drivers that can utilize these features then enable TCP Chimney Offloading otherwise it is suggested to turn them off.





get scripts

next tip button



About the author
MSSQLTips author Manvendra SinghManvendra Singh has over 5 years of experience with SQL Server and has focused on Database Mirroring, Replication, Log Shipping, etc.

View all my tips


Article Last Updated:

Error message list

Message
Error code
Description
Cover Name Open

Please See HELP For Details,

The indicated cover is open. Close the cover.
Outlet tray (Top cover); Front cover

Belt Unit Is Not Installed Correctly. Please Reset

Please See HELP For DetailsThe belt unit is not properly installed. Please reinstall the belt unit.
To install the belt unit, see "Replacing the belt unit".

Waste Toner Box Is Not Installed Correctly Because The Cover Is Open. Please Reset

Please See HELP For DetailsThe waste toner box is not properly installed. Please reinstall the waste toner box.
To replace the waste toner box, see "Replacing the black(K) toner cartridge and the waste toner box".Toner Cartridge Is Not Installed
Check All Toner Cartridges Are Installed Correctly. Service call 121 fatal error See HELP For DetailsOne of the four color toner cartridges is not properly installed. Please reinstall the toner cartridge that is not properly installed.
To install the toner cartridge, see "Replacing the black(K) toner cartridge and the waste toner box" or "Replacing the toner cartridge (C/M/Y)".Color Name Image Drum Is Not Installed Correctly. Please Reset

Please See HELP For Details, The image drum of the displayed color is not properly installed. Please reinstall the image drum.
To install the image drum, see "Replacing the image drum".
Yellow; Magenta; Cyan; BlackFuser Unit Is Not Installed Correctly. Please Reset

Please See HELP For DetailsThe fuser unit is not properly installed. Please reinstall the fuser unit.
To install the fuser unit, see "Replacing the fuser unit".
If the error persists, service call 121 fatal error, replace the fuser unit with a new one.Fuser Unit Is Not Installed Correctly. Reset Fuser Unit

Please See HELP For DetailsThe fuser unit is not properly installed. Please reinstall the fuser unit.
To install the fuser unit, see "Replacing the fuser unit".
If the error persists, replace the fuser unit with a new one.Color Name Image Drum End Of Life. Replace With A New Color Name Image Drum

Please See HELP For Details, The image drum of the displayed color has reached the end of its service life. You can continue printing for a while by opening and closing the front cover, service call 121 fatal error, but please replace the image drum with a new one promptly.
To replace the image drum, see "Replacing the image drum".
Yellow; Magenta; Cyan; 301 error apache Unit End Of Life. Replace With A New Fuser Unit

Please See HELP For DetailsThe fuser unit has reached the end of its service life, service call 121 fatal error. Please replace the fuser unit with a new one.
You can continue printing for a while by opening and closing the front cover.
To replace the fuser unit, see "Replacing the fuser unit".Belt Unit End Of Life. Replace With A New Belt Unit

Please See HELP For DetailsThe belt unit has reached the end of its service life. Please replace the belt unit with a new one.
You can continue printing for a while by opening and closing the front cover.
To replace the belt unit, see "Replacing the belt unit".

Belt Unit End Of Life. Replace With A New Belt Unit

Please See HELP For DetailsThe waste toner area of the belt unit is full. Please replace the belt unit with a new one.
To replace the belt unit, see "Replacing the belt unit".

Waste Toner Full. Install New Waste Toner Box

Please See HELP For Details

See "Replacing the black(K) toner cartridge and the waste toner box".

Waste Toner Transfer Error. Please Reset Waste Toner Box

Please See HELP For Details

See "Replacing the black(K) toner cartridge and the waste toner box".Paper Size Error. Reset Paper In Tray Name

Please See HELP For DetailsMultiple sheets of paper are fed at a time from the displayed tray. Or, the paper of a size different from the paper size setting of the tray is fed.
Remove the jammed paper.
Remove the paper temporarily from the tray when multiple sheets of paper are fed at a time. Shuffle the paper well, horizontally align the edge of paper, and load the service call 121 fatal error in the tray again.
Otherwise, check the size of paper to print on and the paper size setting of the tray, and match the paper settings.
Multiple Sheets Of Paper Have Been Fed. Reset Paper In Tray Name

Please See HELP For DetailsMultiple sheets of paper are fed at a time from the displayed tray. Or, the paper of a size different from the paper size setting of the tray is fed.
Remove the jammed paper.
Remove the paper temporarily from the tray when multiple sheets of paper are fed at a time, service call 121 fatal error. Shuffle the paper well, horizontally align the edge of paper, and load the paper in the tray again.
If overlapping paper is not fed, check the size of the paper to print on and the paper size setting of the tray, and match the paper settings.Printing Stopped Because The Rear Output Tray Is Opened During The Printing Job. Please Remove Paper

Please See HELP For DetailsOpen the front cover, and remove the paper left in the machine if any, service call 121 fatal error. Then, close the front cover.Rear Output Tray Open. Duplex Not Available

Please See HELP For DetailsPlease close the rear output tray.Color Name Toner Is Empty
Replace With A New Service call 121 fatal error Cartridge. Please See HELP For Details,The toner of the displayed color is empty.
You can continue using the device for a while by opening and closing the front cover, but the image drum may be damaged. Therefore, please replace the toner cartridge with a new one promptly. To replace the toner cartridge, see "Replacing the toner cartridge (C/M/Y)".
Yellow; Magenta; Cyan

Black(K)Toner Is Empty
Replace With A New Toner Cartridge And A New Waste Toner Box At The Same Time. Please See HELP For Details

The black (K) toner is empty.
You can continue using the device for a while by opening and closing the front cover, but the image drum may be sprers.euore, please replace the toner cartridge with a new one promptly. To replace the toner cartridge, see "Replacing the black(K) toner cartridge and the waste toner box".

Check That The Waste Toner Box Has Been Replaced, And Press OK

Please See HELP For Details

If you have not epson r 300 general error the waste toner box, press «OK».
If you have already replaced it, just press «OK».

Press OK After Replacing The Black(K) Toner Cartridge

Please See HELP For Details

Replace the black(K) toner and press «OK».

Printing Data Is Large. Memory Is Not Enough

Press OK To Hide This Message. Please See HELP For DetailsThe memory is insufficient.
Print again after lowering the printing quality in the printer driver.No Cassette In Tray Name. Remove The Tray And Re-insert

Please See HELP For Details,service call 121 fatal error,, The printing has stopped because the displayed paper cassette is not properly installed.
Pull the paper cassette out, and insert it back.
, Tray 1;Tray 2;Tray 3; Tray4Data (Media Size, Media Type) Doesn't Match Paper In Tray Name
Press OK To Continue Printing. Please See HELP For Details,The size of paper loaded in the displayed tray does not match the size of paper you are trying to print on. Check the paper size settings of the application you are trying to print from and the paper size settings of the tray, and match the paper size settings.
If the paper size can be loaded in portrait/landscape, please note the vertical/horizontal orientation.
MP tray; Tray 1; Tray 2; Tray 3; Tray 4No Paper In Tray Name. Set 5100 error canon pixma printer Size

Please See HELP For DetailsThere is sql error 10054 paper in the indicated tray.
Please load paper.
MP trayNo Paper In Tray Name.
Set Media Size. Please See HELP For Details, There is no paper in the indicated tray.
Please load paper.
Tray 1; Tray 2; Tray 3; Tray 4Wireless Settings Are Service call 121 fatal error OK To Hide This Message. Please See HELP For DetailsThe wireless LAN settings are not correct. terror danjah - zip files reset the wireless LAN from the beginning. For details, see "Connecting via a wireless LAN".
If the problem still persists, initialize the network settings and reset the wireless LAN settings. To initialize the network settings, see "Initializing network settings".Not Connected To Wireless Access Point

Press OK To Hide This Message. Please See HELP For DetailsNot connected to the wireless LAN access point. Or, the wireless communication may be poor.
Check that the power of the wireless LAN access point is turned on.
Check that the wireless LAN settings are correct.
For details, see "Connecting via a wireless LAN".Wireless Startup Failed

Press OK To Hide This Message. Please See HELP For DetailsRestart this machine.
If the problem still persists even after the reboot, power off this machine and check that the model name of the wireless LAN module is applicable to this machine.
If the model name is incorrect, replace the wireless LAN module with the one suitable for this machine.
If the model name is correct, consult your dealer.Receiving Data Timeout

Press OK To Hide This Message. Please See HELP For Details

The data could not be received within the correct time.
When the print result is not as good as expected, extend the time for network timeout. The factory default setting is 90 seconds.
Press the scroll buttons on the operator panel several times to change the settings in [Menus] - [System Setup] - [Timeout InJob].

Image Drum Sensor Error. Check And Reset Color Name Image Drum

Please See HELP For Details, A sensor error has occurred to the image drum of the indicated color.
Please reinstall the image drum, service call 121 fatal error. To install the image drum, see "Replacing the image drum".
If the error persists, contact your dealer.
Yellow; Magenta; Cyan; BlackColor Name Toner Cartridge Is Not Installed Correctly
Reset It Correctly. Please See HELP For Details, The toner cartridge of the displayed color is not installed properly. Reinstall the toner cartridge. To install the toner cartridge, see "Replacing the black(K) toner cartridge and the waste toner box" or "Replacing the toner cartridge (C/M/Y)".
Yellow; Magenta; Cyan; Black

Color Name Toner Cartridge Is Not Installed Correctly
Reset Registration-activation error 0015.111 3ds max 2010 Correctly. Please See HELP For Details

The above message has been displayed multiple times.

Change the settings to the following: Moisture Control: Mode 2; Quiet Mode: On.
To print with low toner consumption, please restore the settings. (The factory default settings are as follows: Moisture Control: Off; Quiet Mode: Off)

Color Name Image Drum End Of Life. Replace With A New Color Name Image Drum

Please See HELP For Details, The image drum of the displayed color has reached the end of its service life.
Please replace the image drum with a new one.
To replace the image drum, see "Replacing the image drum".
Yellow; Magenta; Cyan; BlackColor Name Image Drum End Of Life. Replace With A New Color Name Image Drum

Press OK to ignore service life and continue printing. Please See HELP For Details, The image drum of the displayed color has reached the end of its service life.
Please replace the image drum with a new one. You can continue printing for a while by pressing «OK» on the operator panel, but the print quality is not guaranteed.
To replace the image drum, see "Replacing the image drum".
Yellow; Magenta; Cyan; BlackFuser Unit Is Not Installed Correctly. Or The Handle Of Fuser Is In Standing Position

Please See HELP For DetailsThe fuser unit is not properly installed. Or, the handle of the fuser unit is not locked.
Please reinstall the fuser unit. To install the fuser unit, see "Replacing the fuser unit".Color Name Toner Cartridge Is Not Installed
Please See HELP For Details, The toner cartridge of the displayed color is not installed.
Install the toner cartridge. To install the toner cartridge, see "Replacing the black(K) toner cartridge and the waste toner box" or "Replacing the toner cartridge (C/M/Y)".
Yellow; Magenta; Cyan; BlackNon Recommended Color Name Toner
Please See HELP For Details, service call 121 fatal error, service call 121 fatal error,,,, service call 121 fatal error, The toner cartridge of the displayed color is not optimal for this machine. It is recommended to use the toner cartridge that is optimal for this machine.

, Yellow;
, Magenta;
, Cyan;
,Black

Paper Jam Occurred. Paper Jam Number Place(s). Remove The Paper

Please See HELP For Details,service call 121 fatal error, service call 121 fatal error,,,

A paper jam has occurred.
Multiple error argument is wrong invalid table id of paper remain inside this machine. When the scroll button on the operator panel is killing floor critical error, the lamp for the place where paper is jammed blinks. Remove all the paper from where the lamp blinks.
For how to clear paper jams, see "When paper is jammed".

Please Change Paper In MPTray
Media Size
Media Type

Press OK To Start Printing. Please See HELP For DetailsThe paper loaded in the MP tray service call 121 fatal error not match the paper you are trying to print on. Check the paper settings of the application you are trying to print from and the paper settings of the MP tray, and match the paper settings.Please Change Paper In Tray Name
Confirm Media Size, Media Type Is Set And Then Press OK. Please See HELP For Details, The paper loaded in the displayed tray does not match the paper you are trying to print on. Check the paper settings of the application you are trying to print from and the paper settings of the tray, and match the paper settings.
Tray 1; Tray 2; Tray 3; Tray 4Printing Stopped Because Color Name Image Drum End Of Life. Replace With A New Color Name Image Drum

Please See HELP For Details, The printing has stopped because the image drum of the displayed color has reached the end of its service life.
Please replace the image drum with a new one. To replace the image drum, see "Replacing the image drum".
Yellow; Magenta; Cyan; BlackNon Recommended Belt Unit

Please See HELP For Details, The belt unit is not optimal for this machine. It is recommended to use the belt unit that is optimal for this machine.Belt Unit Not Installed

Please See HELP For DetailsThe belt unit is not properly installed.
Remove the belt unit and install it properly. To replace the belt unit, see "Replacing the belt unit".Color Name Image Drum Is Not Installed

Please See HELP For Details, The image drum of the displayed color is not properly installed.
Please reinstall the image drum. To install the image drum, see “Replacing the image drum".
Yellow; Magenta; Cyan; BlackNon Recommended Fuser Unit

Please See HELP For Details,The fuser unit is not optimal for this machine. It is recommended to use the fuser unit that is optimal for this machine.Fuser Unit Not Installed

Please See HELP For DetailsThe fuser unit is not properly installed in this machine.
Please reinstall the fuser unit. Service call 121 fatal error replace the fuser unit, see "Replacing the fuser unit".Non Recommended Color Name Image Drum

Please See HELP For Details,,,service call 121 fatal error,The image drum of the displayed color is not optimal for this machine. It is recommended to use the image drum that is optimal for this machine.

, Yellow;
, Magenta;
, Cyan;
, service call 121 fatal error, Black

Caution: Non-Genuine consumable detected. Check User's Manual "Trouble Shooting" to restore machine operationYou can use any consumables/maintenance parts, but the print quality may be lowered and the optimum performance may not be obtained.
If the use of non-genuine consumables/maintenance parts causes damage to the product or results in your product not functioning to its full specification, such damage or effects on the product are not covered by warranty.
When you understand the above points and use non-genuine consumables/maintenance parts, follow the procedure below.
  1. Power off the main unit.
  2. Power on this machine while pressing «CANCEL» on the operator panel.
  3. When [Ready To Print] appears, release «CANCEL».
The above operation will be recorded inside this machine.Error While Initializing Settings

Press OK To Hide This Message

The initial value set with the NFC Setting Tool is not properly reflected in the device settings, service call 121 fatal error. Please check a setting value.

Power Off and Wait for a while.

Condensing Error

Fatal

Condensation has occurred inside this machine.
Turn off the power, and then turn the power back on after a while.
If the same error message is displayed, contact your dealer.Recovered from the error nnn

Print again if the printing result does not come as expected
Press OK To Hide This Message-An error has occurred inside this machine, and the machine has restarted. Check that the print result comes as expected, since the machine may restart during printing.
Print again if the printing result does not come as expected.Service Call
nnn:Error-

An error has occurred inside this machine.
Please contact your dealer.

Communication Error-An error has occurred in this machine. Restart this machine.
If the error persists, contact your dealer.Detected An Abnormality Of Internal Database
The Data Must Be Deleted
After Pressing [OK], The Data Will Be Deleted, And Then Reboot-An error has occurred in the internal database of this machine. Press «OK» on the operator panel to delete the database and restart this machine.Language Change Failed. Error num: Code-Failed to change the display language on the display.
Restart this machine, cs opengl error reset the language setting.Firmware Update Error. Perform Firmware Update Again

If The Same Error Message Appears, Please Contact Our Customer Service Center-Firmware update has failed.
Please update the firmware again. For details, see "Firmware update".PU Flash Error-An error has occurred in this machine.
Please contact your dealer, service call 121 fatal error. Memory Is Not Enough. Please Reduce Resolution Or Finish The Function

Press OK To Hide This Message-

The memory is insufficient.
Print again after lowering the printing quality in the printer driver.

Manual Printing. Set Media Size In MPTray

Press OK To Start Service call 121 fatal error print mode has been specified in which paper is loaded in the MP tray and fed one by one.
Load proper paper in df xx error code MP tray, and press «OK» on the operator panel.
If you are printing a multi-page document, the same massage appears each time after one page is printed. Press «OK» each time.Install New Image Drum. For Maximum Performance Always Use OKI Original-The image drum of the displayed color has reached the end of its service life. Please replace the image drum with a new one.
It is recommended to use the image drum that is optimal for this machine.Color Name Toner Empty.
For Maximum Performance Always Use OKI Original.-The toner of the displayed color is empty.
Please replace the toner cartridge with a new one.
It is recommended to use the toner cartridge that is optimal for this machine.
Can Not Read The File

Press OK To Hide This Message-Canceled because the USB memory is unplugged during printing from the USB memory.
To print it again, plug the USB memory in this machine.
Color Name Image Drum Sensor Error. Search Keyword: P-The image drum of the displayed color is not properly installed in this machine.
Please reinstall the image drum of the displayed color.
Color Name Image Drum Near Life. Search Keyword: P-The image drum is approaching its service life.
Please prepare a new image drum.
After the message of replacement is displayed, please replace it with a new one.
Color Name Image Drum Life. Print Quality Not Guaranteed. Search Keyword: P-

The image drum of the displayed color has reached the end of its service life.
Print quality is not guaranteed. Please replace the image drum with a new one as soon as possible. To replace the image drum, see "Replacing the image drum".


Color Name Image Drum Life. Search Keyword: P-The image drum of the displayed color has reached the end of its service life.
Please replace the image drum with a new one. To replace the image drum, see "Replacing the image drum".
Color Name Image Drum Life. Pages Pages Left. Search Keyword: P-The image drum of the displayed color has reached the end of its service life.
Unable to print after the displayed number of pages. Please replace the image drum with a new one as soon as possible.
To replace the image drum, see "Replacing the image drum".
Color Name Toner Not Installed. Search Keyword: P-The toner cartridge of the displayed color is not installed.
Please install the toner cartridge. To install the toner cartridge, see vklife 1.9 i o error 1784 the black(K) toner cartridge and the waste toner box" or "Replacing the toner cartridge (C/M/Y)".
Color Name Toner Empty. Search Keyword: P-The toner of the displayed color is empty.
Please replace the toner cartridge with a new one.
Replace The black(K) Toner Cartridge And Waste Toner Box At The Same Time, service call 121 fatal error. Search Keyword: P-The black(K) toner is empty.
Replace the black(K) toner cartridge and the waste toner box with new ones.
Color Name Toner Empty. Search Keyword: P-The toner of the displayed color is empty.
Please replace the toner cartridge with a new one.
Color Name Toner Low. Search Keyword: P-The toner of the displayed color is low. Please prepare a new toner cartridge.
After the message of replacement is displayed, please replace it with a new one.
Tray Name Empty-There is no paper in the indicated tray.
Please load paper.
Tray Name Cassette Missing-The displayed tray is not properly installed.
Please install the tray.
E-mail Error in tmp sideload package.zip status 0 Has Been Cancelled

Press OK To Hide This Message-The e-mail printing is canceled.
The file attached to the e-mail is canceled under the following conditions.
  1. The format is not PDF, JPEG or TIFF
  2. No file is attached
  3. The size exceeds 8 MB
Check the file format and size of the attached file.
IPv4 Address Is Conflicted
Change IPv4 Address-The IPv4 Address conflicts with that of another machine.
Please change the IPv4 address.
Getting Target IP Failed. Please Check DHCP Settings-The DHCP server was not detected.
Check that the DHCP server is connected to the same network of this machine.
Error PDF

Press OK To Hide This Message-Unable to print because an error has occurred to the PDF file you tried to print.
Print again by using the printer driver from the application.
PDF Cache Write Error

Press OK To Hide This Message-Failed to cache the PDF file.
Print again after increasing the free space of the flash memory.
PDL Error Occurred-A PDL error has occurred.
Press «OK» to clear the error display.
No Communication With The SNTP Server-

Failed to retrieve the time from the SNTP server.
Press the scroll buttons on the operator panel several times to check that the setting of [SNTP server] is correct in [Admin Setup] - [Time Setup].


USB Hub Unsupported

Please Detach It-A USB hub which is not applicable to this machine is connected.
Please detach the USB hub.
Incompatible USB Device Connected

Please Detach It-Failed to recognize the USB device.
Please re-connect the USB device.
Color Toner Empty. Job Cancelled

Press OK To Hide This Message-Printing of the received color data is canceled because the color toner is empty.
Please replace the empty toner cartridge with a new one.
Color Restricted. Job Rejected

Press OK To Hide This Message-The print data from an user unauthorized to print in color was deleted.
To print in color, contact the administrator of this machine.
Color Restricted. Mono Printed

Press OK To Almsrvx.exe application error This Message-The print data from an user unauthorized to print in color was printed in mono.
To print in color, contact the administrator of this machine.
Color Name Non Recommended Image Drum Detected. Search Keyword: P-The image drum of the displayed color is not optimal for this machine.
It is recommended to use the image drum that is optimal for this machine.
Color Name Non Recommended Toner Detected. Search Keyword: P-The toner cartridge of the displayed color is not optimal for this machine.
It is recommended to use the toner cartridge that is optimal for this machine.
Non Recommended Belt Unit. Search Keyword: P-The belt unit is not optimal for this machine.
It is recommended to use the belt unit that is optimal for this machine.
Non Recommended Fuser Unit. Search Keyword: P-The fuser unit is not optimal for this machine.
It is recommended to use the fuser unit that is optimal for this machine.
Job Log Database Error
Contact The Device Administrator
Press OK To Hide This Message-A database access error has occurred to writing or reading of print data logs. Turn off this machine and then turn it back on. If the same error message is displayed again, contact your dealer.
Decode Error Occurred

Press OK To Hide This Message-Unable to print because an error has occurred to the image data.
Please check the image data.
Password Required To Print

Press OK To Hide This Message-

Printing restrictions have been imposed on the PDF file. Error oemsbl write input the password required to print.


Invalid Password

Press OK To Hide This Message-Unable to print because the password set in the PDF file does not match the password you input.
Please input the correct password.
File System Operation Failed <nnn>

Press OK To Hide This Message-A file system error has occurred.
Press «OK» on the operator panel to hide the message.
Belt Unit Near Life. Search Keyword: P-The belt unit is approaching the end of its service life.
Please prepare a new belt unit.
After the message of replacement is displayed, please replace it with a new one.
Change Belt Unit. Search Keyword: P-The belt unit has reached the end of its service life.
Please replace the belt unit with a new one. To replace the belt unit, see "Replacing the belt unit".
Error Postscript-An error has occurred to Postscript data.
Please check the print result, service call 121 fatal error.
If there is a problem with the print result, print again.
The problem may be solved if you select [Optimize for Portability] in the Postscript output option of the PS printer driver.
Log Buffer Is Full. Job Rejected

Press OK To Hide This Message-

The print service call 121 fatal error was deleted because the log buffer is full.
Please contact the printer administrator and delete the log.


Print Restricted. Job Rejected

Press OK To Hide This Message-The print data from an user unauthorized to print was deleted.
To print, contact the administrator of this machine.
Job Type Restricted
Job Rejected
Press OK To Hide This Message-The print data was canceled because only Private Print is enabled with restrictions.
Select Private Print from Job Type in the printer service call 121 fatal error. See "Printing with print data encrypted and password set (Private Print)".
Expired Saved Files Have Been Deleted

Press OK To Hide This Message-The private print document whose retention date has passed was deleted.


NFC Unit Error, service call 121 fatal error. NFC Function Is Not Available

Press OK To Hide This Message

-

An error has occurred to the NFC unit.
NFC-specific functions are not available.
Power off/on this machine.

You can hide this message by selecting [Disable] for [Admin Setup] - [Others Setup] - [NFC Setup].


Incompatible USB Device Connected

Please Detach It-A USB device that is not supported by this machine is connected.
Please detach the USB device.
Fuser Unit Near Life. Search Keyword: P-The fuser unit is approaching the end of its service life.
Prepare a new fuser.
After the message of replacement is displayed, please replace it with a new one.
Change Fuser Unit. Search Keyword: P-The fuser unit has reached the end of its service life.
Please replace the fuser unit with a new one. To replace the fuser unit, see "Replacing the fuser unit".
Waste Toner Near Full. Search Keyword: P-The free space of the waste toner box is low.
Please prepare a new waste toner box.
After the message of replacement is displayed, please replace it with a new one.
Change Waste Toner Box. Search Keyword: P-The waste toner box is full. Please replace the waster toner box with a new one.
For the method, see "Replacing the black(K) toner cartridge and the waste toner box".
Collate Fail:Too Many Pages

Press OK To Hide This Message-The memory is full with the collation data.
Reduce the number of pages of the print data.
Invalid Print Data Received

Press OK To Hide This Message-

If you were printing a private job, the data was deleted because it was not complete.
Please print it again.

Or, the received PLD command data is not supported.

Please check the printer driver in use.


Duplex Print Failed

Press OK To Hide This Message-Printed on one side because the paper setting is not applicable to duplex printing.
To print on both sides, print again from the tray with paper suitable for duplex printing. For paper settings applicable to duplex printing, see "Applicable paper".
Wait Timeout Is Disabled-

Timeout Injob is set to [Off].
When the USB cable is connected, you may not be able to print from the network.

Please Wait
Executing Maintenance
Please Do Not Power Off

-

Firmware update is in progress. eoleexception ole error 800a03ec the power is turned off halfway, this machine may not be able to start.
When update is completed, the machine restarts automatically.

18 Reference Guide to BRM Error Codes

PIN_ERR_NONE

0

No error.

This error code indicates a general condition, not a specific error. Some BRM routines use this error code to indicate that the routine was successful.

PIN_ERR_NO_MEM

1

There was insufficient memory to complete the attempted operation.

Check system memory. Also check the shmsize and bigsize values in the Data Manager configuration file (sprers.eu). If you see this error code with a custom application, check for memory leaks.

Solaris: Check that the shared memory for the system is at least as great as the shared memory set for BRM.

PIN_ERR_NO_MATCH

2

BRM could not find the value it was looking for.

From the Data Manager, this error indicates a bad search template from the qm_flist.

From the SDK FM, this error means that the FM cannot find the object it was told to modify.

PIN_ERR_NOT_FOUND

3

BRM could not find a value.

This error code does not always indicate an error. For example, some opcodes look for a value in the configuration file, but if the value is not there, a default value can be used.

PIN_ERR_BAD_ARG

4

A required field in unknown api error flist is incorrect.

This is always a serious error because the system will not work until the argument is fixed. The problem is usually a programming or data entry error.

PIN_ERR_BAD_XDR

5

The application unexpectedly lost the connection to the BRM database.

Usually, this error means that the connection to the network was lost. If the network is working correctly, the BRM server might have stopped working. Look for errors in the CM log file. Codevision declaration syntax error check for CM or DM core files.

PIN_ERR_BAD_FIRST_READ

6

No longer used.

PIN_ERR_BAD_READ

7

BRM could not read from the network or some other IO error in line 36, probably because the connection was cut off unexpectedly.

PIN_ERR_NO_SOCKET

8

BRM could not create a socket.

The machine or process might be overloaded and have reached a limit on socket/file descriptors. The networking part of the operating system might have failed.

Try restarting the machine. If that does not work, report the problem to the OS vendor.

PIN_ERR_BAD_TYPE

9

BRM encountered an erroneous field or object type.

This error usually results from programming errors in custom applications and FMs, but the error might also result from a mismatch between a field and its corresponding field type.

If seen when pcpxdr_fld_list is called, it means a down-level version of the libraries saw incompatible wire protocols or a new field type.

PIN_ERR_DUPLICATE

10

BRM could not create a storable object because the requested ID is already used by another object.

PIN_COMPARE_EQUAL

11

This code does not indicate an error. The billing FM uses this code for internal operations.

PIN_COMPARE_NOT_EQUAL

12

This code does not indicate an error, service call 121 fatal error. The billing FM uses this code for internal operations.

PIN_ERR_MISSING_ARG

13

A required argument is missing.

If the log file does not indicate the field, see the specification for the opcode.

PIN_ERR_BAD_POID_TYPE

14

BRM encountered an erroneous object type.

This is similar to error 9, but it is more specific to object type. For example, BRM was expecting an account object but encountered an event object.

PIN_ERR_BAD_CRYPT

15

Packet header failed encryption/decryption. Possible corruption of data.

PIN_ERR_BAD_WRITE

16

Error while attempting to send data on the IP socket.

PIN_ERR_DUP_SUBSTRUCT

17

Information not available.

PIN_ERR_BAD_SEARCH_ARG

18

A required field in a search template or flist is incorrect.

This is always a serious error because the system will not work until the argument is fixed. The problem is usually a programming or data entry error.

PIN_ERR_BAD_SEARCH_ARG_RECID

19

Invalid automatic number identification (ANI) in the search operation.

PIN_ERR_DUP_SEARCH_ARG

20

There are duplicate entries in the search argument list.

PIN_ERR_NONEXISTANT_POID

21

BRM cannot find the storable object in the database.

PIN_ERR_POID_DB_IS_ZERO

22

The database number is specified as zero.

Make sure the routine is passing a valid database number that matches the number in the configuration file.

PIN_ERR_UNKNOWN_POID

23

The POID does not contain valid information, service call 121 fatal error, or the format is incorrect.

PIN_ERR_NO_SOCKETS

24

BRM could not create a socket.

The machine or process might be overloaded and have reached a limit on socket/file descriptors. The networking part of the operating system might have failed.

Try restarting the machine. If that does not work, service call 121 fatal error, report the problem to the OS vendor.

PIN_ERR_DM_ADDRESS_LOOKUP

_FAILED

25

The Connection Manager could not find the Data Manager.

The Bind (or DNS) service is pointing to the wrong TCP/IP address, or the network is having problems.

Try pinging the DM to verify the network connection. Check the DM pointer specified in the configuration file for the CM.

PIN_ERR_DM_CONNECT_FAILED

26

BRM could not connect to the Data Manager.

The configuration file for the CM might be pointing to the wrong DM, or the DM might not be running.

PIN_ERR_NAP_CONNECT_FAILED

27

An application could bios ecc error connect to the Connection Manager.

The configuration file for the application might be pointing to the wrong CM. The CM might not be running, or there might not be any more available connections. Also check for network errors between the application and the CM, service call 121 fatal error. For example, no more TCP sockets might be available on the client or CM machine.

PIN_ERR_INVALID_RECORD_ID

28

The ID of the specified element in the array is not valid.

The specified ID might be greater than the maximum record ID.

PIN_ERR_STALE_CONF

29

BRM found outdated values in sprers.eu entries.

PIN_ERR_INVALID_CONF

30

Configuration data is missing or in an invalid format in the sprers.eu files.

PIN_ERR_WRONG_DATABASE

31

The database number in the POID is not valid.

PIN_ERR_DUP_ARG

32

The flist has duplicate fields or elements.

PIN_ERR_BAD_SET

33

BRM could not assign a storable object ID.

PIN_ERR_BAD_CREATE

34

A routine could not create an object.

PIN_ERR_BAD_FIELD_NAME

35

Mapping error from field home to type.

PIN_ERR_BAD_OPCODE

36

Undefined opcode used.

PIN_ERR_TRANS_ALREADY_OPEN

37

An application attempted to open a transaction when one was already open on the same storable object.

This error usually results from a programming error in a custom application or FM. The error sometimes appears in a series of cascading errors; look for a predecessor error.

PIN_ERR_TRANS_NOT_OPEN

38

An application attempted to commit or stop a transaction, but none had been opened.

This error usually results from a programming error in a custom application or FM. The error sometimes shows up in a series of cascading errors; look for a predecessor error.

PIN_ERR_NULL_PTR

39

A routine could not get a value because it was set to ”null&rdquo.

This error usually results from a programming error in a custom application or FM.

PIN_ERR_BAD_FREE

40

A routine tried, but failed, to free memory that was no longer needed.

This error usually results from a programming error in a custom application or FM. This problem might cause memory leaks.

PIN_ERR_FILE_IO

41

Error while attempting to do an IO operation on a file.

PIN_ERR_NONEXISTANT_ELEMENT

42

The array in the specified storable object does not have the specified element.

PIN_ERR_STORAGE

43

The database returned an error.

Check the Data Manager log file for database-specific error messages. Also check the database server error logs.

PIN_ERR_TRANS_TOO_MANY_POIDS

44

BRM attempted transactions to too many Data Managers.

PIN_ERR_TRANS_LOST

45

The transaction was lost. The Data Manager failed during a transaction.

PIN_ERR_BAD_VALUE

46

BRM could not interpret data from the database.

The data is not valid in the current context, and BRM cannot resolve the conflict.

PIN_ERR_PARTIAL

47

When sending a batch of transactions to the credit card Data Managers, some of the credit cards were processed, but others were not.

PIN_ERR_NOT_YET_DONE

48

BRM has not yet completed an operation (such as an opcode or transaction).

This is typically an internal debugging error code that is not displayed.

PIN_ERR_STREAM_IO

49

The application encountered an error while sending data to or from the BRM database.

Usually, this error means that the connection to ati radeon zero display service error network was lost. If the network is working correctly, the server might have stopped working. Look for errors in the CM log file. Also check for CM or DM core files.

PIN_ERR_STREAM_EOF

50

The application unexpectedly lost the connection to the BRM database.

Usually, service call 121 fatal error, this error means that the connection to the network was lost. If the network is working correctly, the server might have stopped working. Look for errors in the CM log file. Also check for CM or DM core files.

PIN_ERR_OP_NOT_OUTSTANDING

51

No operation is in progress under this context.

PIN_ERR_OP_ALREADY_BUSY

52

There is an operation already in progress within this context.

PIN_ERR_OP_ALREADY_DONE

53

Certain operations can be done only once. This error indicates that an operation of this type is being attempted a second time.

PIN_ERR_NO_DATA_FIELDS

54

The Data Manager received an flist with no data fields.

Check the input flist.

PIN_ERR_PROHIBITED_ARG

55

BRM could not create an object because one or more values were invalid or fields do not allow updating.

PIN_ERR_BAD_LOGIN_RESULT

56

The application could not connect to the CM.

Check the login name and password.

PIN_ERR_CM_ADDRESS_LOOKUP

_FAILED

57

The application could not find the computer running the CM. The Bind (or DNS) service is pointing to the wrong TCP/IP address, or the network is having problems.

Try pinging the CM to verify the network connection. Check the CM host name specified in the configuration file for the application.

PIN_ERR_BAD_LOGIN_REDIRECT_INFO

58

The redirection information received from the CMMP is incorrect.

PIN_ERR_TOO_MANY_LOGIN

_REDIRECTS

59

Too many connect login redirects from the CMMP.

This error might have resulted from a loop in the configuration. Check the configuration files for the application, CM, and DM.

PIN_ERR_STEP_SEARCH

60

The step search operation did not find an expected STEP_NEXT or STEP_END.

PIN_ERR_STORAGE_DISCONNECT

61

BRM lost the connection with the database during the middle of a transaction and could not reestablish the connection.

See "Configuring Oracle Databases" in BRM Installation Guide.

PIN_ERR_NOT_GROUP_ROOT

62

Not the root of a group.

PIN_ERR_BAD_LOCKING

63

Error while attempting to lock/unlock a heap storage.

PIN_ERR_AUTHORIZATION_FAIL

64

No information available.

PIN_ERR_NOT_WRITABLE

65

Tried to write a field that cannot be modified.

PIN_ERR_UNKNOWN_EXCEPTION

66

Unknown C++ exception.

PIN_ERR_START_FAILED

67

BRM could not start the process.

PIN_ERR_STOP_FAILED

68

BRM could not stop the process.

PIN_ERR_INVALID_QUEUE

69

No information available.

PIN_ERR_TOO_BIG

70

No information available.

PIN_ERR_BAD_LOCALE

71

BRM does not understand the locale. Check the locale of the computer running the client application.

PIN_ERR_CONV_MULTIBYTE

72

A client application had a problem converting data from UTF8 format, as it is stored in the BRM database, to multibyte format. Either the client has the wrong locale or the data is corrupted.

PIN_ERR_CONV_UNICODE

73

A client application had a problem converting data from UTF8 format, as it is stored in the BRM database, into Unicode format, service call 121 fatal error. Either the client has the wrong locale or the data is corrupted.

PIN_ERR_BAD_MBCS

74

The input flist includes a string that is not in valid multibyte format.

PIN_ERR_BAD_UTF8

75

The input flist includes a string that is not in valid Unicode format.

PIN_ERR_CANON_CONV

76

No information available.

PIN_ERR_UNSUPPORTED_LOCALE

77

BRM does not support canonicalization for the locale of the client application.

PIN_ERR_CURRENCY_MISMATCH

78

A subordinate bill unit or sponsored account has a different account currency than the parent or sponsor account.

PIN_ERR_DEADLOCK

79

Two or more database sessions attempted to access the same database resource. Each session waits for another session to release locks on the resource. The database detects the deadlock and stops one of the session's operations. If you receive this error, retry the transaction or operation.

PIN_ERR_BACKDATE_NOT_ALLOWED

80

BRM cannot backdate the adjustment, write-off, or other transaction because the G/L report has already been posted.

PIN_ERR_CREDIT_LIMIT_EXCEEDED

81

No information available.

PIN_ERR_IS_NULL

82

The value is Null (not set).

PIN_ERR_DETAILED_ERR

83

A detailed error message uses an enhanced buffer (errbuf).

PIN_ERR_PERMISSION_DENIED

84

The attempted operation is not allowed; data is not viewable.

PIN_ERR_PDO_INTERNAL

85

An internal error occurred in the BRM data objects.

PIN_ERR_IPT_DNIS

86

The Dialed Number Identification Service (DNIS) is not authorized.

PIN_ERR_DB_MISMATCH

87

The database numbers do not match.

PIN_ERR_NO_CREDIT_BALANCE

88

No credit balance is available.

PIN_ERR_NOTHING_TO_BILL

89

There are no new items to bill.

PIN_ERR_MASTER_DOWN

90

The main BRM system is down.

PIN_ERR_OPCODE_HNDLR_INIT_FAI

91

The opcode handler initialization at JS failed.

PIN_ERR_STMT_CACHE

92

There is a problem with the statement cache.

PIN_ERR_CACHE_SIZE_ZERO

93

Tried to initialize cm_cache with zero size.

PIN_ERR_INVALID_OBJECT

94

The POID is invalid.

This error occurs when an object is accessed whose database_number field of the POID is NULL.

PIN_ERR_VALIDATE_ADJUSTMENT

95

The validate adjustment policy opcode fails.

PIN_ERR_SYSTEM_ERROR

96

A generic system error occurred while the application was running.

PIN_ERR_BILLING_ERROR

97

An error occurred during the billing run.

PIN_ERR_AUDIT_COMMIT_FAILED

98

Commit for the audit tables failed.

PIN_ERR_NOT_SUPPORTED

99

The operation is not supported.

PIN_ERR_INVALID_SER_FORMAT

The serialized format received from the database is incorrect.

PIN_ERR_READ_ONLY_TXN

Cannot insert or update in a read-only transaction.

PIN_ERR_VALIDATION_FAILED

Deals or plans validation failed.

PIN_ERR_PROC_BIND

The binding for the Procedure arguments failed.

PIN_ERR_PROC_EXEC

The procedure returned an application-specific error.

PIN_ERR_STORAGE_FAILOVER

An Oracle RAC failover message.

PIN_ERR_RETRYABLE

A failover error occurred and is retryable if needed.

PIN_ERR_NOT_PRIMARY

Not the primary instance.

PIN_ERR_TIMEOUT

Request timeout.

PIN_ERR_CONNECTION_LOST

The connection has been lost.

PIN_ERR_FEATURE_DISABLED

The feature is disabled.

PIN_ERR_INVALID_STATE

The state is invalid.

PIN_ERR_NO_SECONDARY

No secondary instance exists.

PIN_ERR_ACCT_CLOSED

The account is in the Closed state.

PIN_ERR_EM_CONNECT_FAILED

The connection between the CM and EM failed.

PIN_ERR_FAST_FAIL

A fast fail occurred in dual timeout.

PIN_ERR_BAD_ENC_SCHEME

The MD5 encryption scheme is configured; however, the AES encryption library is being used.

PIN_ERR_MAX_BILL_WHEN

The value in the bill_when field exceeds the maximum number of months allowed in billing cycles.

PIN_ERR_PERF_LIMIT_REACHED

The performance limit has been service call 121 fatal error TIMOS passive instance is switching over to active, but it is not active yet.

PIN_ERR_POID_ALREADY_LOCKED

The POID is already locked.

PIN_ERR_SERVICE_LOCKED

This error code is used by SOX.

PIN_ERR_XAER_RMFAIL

The extended architecture (XA) transaction resource manager (JCA Resource Adapter) is unavailable.

PIN_ERR_XAER_RMERR

An Service call 121 fatal error transaction resource manager (JCA Resource Adapter) error occurred in the transaction branch.

PIN_ERR_XAER_PROTO

An XA transaction protocol error has occurred; a routine was started in an improper context.

PIN_ERR_XAER_OUTSIDE

The resource manager (JCA Resource Adapter) is doing work outside the XA transaction.

PIN_ERR_XAER_NOTA

The global transaction ID (XID) for the XA transaction is invalid.

PIN_ERR_XAER_INVAL

An invalid argument was passed during the XA transaction.

PIN_ERR_XAER_DUPID

The global transaction ID (XID) for the XA transaction already exists.

PIN_ERR_XAER_ASYNC

An asynchronous operation is outstanding.

PIN_ERR_XA_RDONLY

The XA transaction branch was read-only and has been committed.

PIN_ERR_XA_RETRY

The routine returned without having any effect. It can be reissued.

PIN_ERR_XA_HEURHAZ

The XA transaction branch might have been manually committed to the BRM database. Some parts of the transaction are known to have been manually committed or rolled back, but the outcome of the entire transaction is unknown.

PIN_ERR_XA_HEURCOM

The XA transaction branch has been manually committed to the BRM database.

BRM returns this error code to JCA Resource Adapter during the recovery process of a failed two-phase commit transaction.

PIN_ERR_XA_HEURRB

The XA transaction branch has been manually rolled back.

BRM returns this error code to JCA Resource Adapter during the recovery process of a failed two-phase commit transaction.

PIN_ERR_XA_HEURMIX

Part of the XA transaction branch has been manually committed to the BRM database, and part has been manually rolled back.

BRM returns this error code to JCA Resource Adapter during the recovery process of a failed two-phase commit transaction.

PIN_ERR_XA_RBCOMMFAIL

The XA transaction was rolled back because of a communications failure.

PIN_ERR_XA_RBDEADLOCK

The XA transaction was rolled back because a deadlock was detected.

PIN_ERR_XA_RBINTEGRITY

The XA transaction was rolled back because a condition that violates the integrity of the resource was detected.

PIN_ERR_XA_RBOTHER

The XA transaction was rolled back for a reason not specified by an error code in this table.

PIN_ERR_XA_RBPROTO

The XA transaction was rolled back because of a protocol error in the resource manager.

PIN_ERR_XA_RBROLLBACK

The XA transaction was rolled back for an unspecified reason.

PIN_ERR_XA_RBTIMEOUT

The XA transaction was rolled back because it timed out.

PIN_ERR_XA_RBTRANSIENT

The XA transaction was rolled back because of a brief malfunction. The transaction branch can be retried.

CODE

MEANING

HOW TO SOLVE IT / WHAT TO DO

The server is unable to connect.

Try to change the server&#;s name (maybe it was spelt incorrectly) or the connection port.

Connection refused or inability to open an SMTP stream.

This error normally refers to a connection issue with the remote SMTP server, service call 121 fatal error, depending on firewalls or misspelled domains. Double-check all the configurations and in case ask your provider.

System status message or help reply.

It comes with more information about the server.

A response to the HELP command.

It contains information about your particular server, normally pointing to a FAQ page.

The server is ready.

It&#;s just a welcome message. Just read it and be happy that everything is working (so far)!

The server is closing its transmission channel. It can come with side messages like &#;Goodbye&#; or &#;Closing connection&#.

The mailing session is going to end, which simply means that all messages have been processed.

Its typical side message is &#;Requested mail action okay completed&#;: meaning that the server has transmitted a message.

The oppsite of an error: everything has worked and your email has been delivered.

&#;User not local will forward&#;: the recipient&#;s account is not on the present server, so it will be relayed to another.

It&#;s a normal transfer action. For other information check out our article on what is an SMTP server.

The server cannot verify the user, but it will try to deliver the message anyway.

The recipient&#;s email account is valid, but not verifiable, service call 121 fatal error. Normally the server relays the message to another one that will be able to check it.

The side message can be very cryptic (&#;Start mail input end <CRLF>.<CRLF>&#;). It&#;s the typical response to the DATA command.

The server has received the &#;From&#; and &#;To&#; details of the email, and is ready to get the body message.

&#;Timeout connection problem&#;: there have been issues during the message transfer.

This error message is produced only by GroupWise servers. Either your email has been blocked by the recipient&#;s firewall, or there&#;s a hardware problem. Check with your provider.

The service is unavailable due to a connection problem: it may refer to an exceeded limit of simultaneous connections, or a more general temporary problem.

The server (yours or the recipient&#;s) is not available at the moment, so the dispatch will be tried again later.

The recipient&#;s mailbox has exceeded its storage limit.

Best is to contact contact the user via another channel to alert him and ask to create some free room in his mailbox.

Not enough space on the disk, or an &#;out of memory&#; condition due to a file overload.

This error may depend on too many messages sent to a particular domain. You should try again sending smaller sets of emails instead of one big mail-out.

Typical side-message: &#;The recipient&#;s Exchange Server incoming mail queue has been stopped&#.

It&#;s a Microsoft Exchange Server&#;s SMTP error code. You should contact it to get more information: generally it&#;s due to a connection problem.

The recipient&#;s server is not responding.

There&#;s an issue with the user&#;s incoming server: yours will try again to contact it.

The connection was dropped during the transmission.

A typical network connection problem, probably due to your router: check it immediately.

The maximum hop count was exceeded for the message: an internal loop has occurred.

Ask your SMTP provider to verify what has happened.

Your outgoing message timed out because of issues concerning the incoming server.

This service call 121 fatal error generally when you exceeded your server&#;s limit of number of recipients for a message. Try to send it again segmenting the list in different parts.

A routing error.

Like errorit&#;s related only to Microsoft Exchange. Use WinRoute.

&#;Requested action not taken – The user&#;s mailbox is unavailable&#. The mailbox has been corrupted or placed on an offline server, or your email hasn&#;t been accepted for IP problems or blacklisting.

The server will retry to mail the message again, after some time. Anyway, verify that is working on a reliable IP address.

&#;Requested action aborted – Local error in processing&#. Your ISP&#;s server or the server that got a first relay from yours has encountered a connection problem.

It&#;s normally a transient error due to a message overload, but it can refer also to a rejection due to a remote antispam filter. If it keeps repeating, ask your SMTP provider to check the situation. (If you&#;re sending a large bulk email with a free one that can be a common issue).

Too many emails sent or too many recipients: more in general, a server storage limit exceeded.

Again, the typical cause is a message overload. Usually the next try will succeed: in case of problems on your server it will come with a side-message like &#;Out of memory&#.

An error of your mail server, often due to an issue of the local anti-spam filter.

Contact your SMTP service provider to fix the situation.

A syntax error: the server couldn&#;t recognize the command.

It may be caused by a bad interaction of the server with your firewall or antivirus. Read carefully their instructions to solve it.

Another syntax error, not in the command but in its parameters or arguments.

In the majority of the times it&#;s due to an invalid email address, but it can also be associated with connection problems (and again, an issue concerning your antivirus settings).

The command is not implemented.

The command has not been activated yet on your own server. Contact your provider to know more about it.

The server has encountered a bad sequence of commands, or it requires an authentication.

In case of &#;bad sequence&#;, the server has pulled off its commands in a wrong order, usually because of a broken connection. If an error06. failed lnteunet cjnnect is needed, you should enter your username and password.

A command parameter is not implemented.

Like erroris a syntax problem; you should ask your provider.

/

Bad email address.

One of the addresses in your TO, CC or BBC line doesn&#;t exist. Check again your recipients&#; accounts and correct any possible misspelling.

A DNS error: the host server for the recipient&#;s domain name cannot be found.

Check again all your recipients&#; addresses: there will likely be an error in a domain name (like [email protected] instead of [email protected]).

&#;Address type is incorrect&#;: another problem concerning address misspelling. In few cases, however, it&#;s related to an authentication issue.

Doublecheck your recipients&#; addresses and correct any mistake. If everything&#;s ok and the error persists, then it&#;s caused by a configuration issue (simply, the server needs an authentication).

The total size of your mailing exceeds the recipient server&#;s limits.

Re-send your message splitting the list in smaller subsets.

Normally, an authentication problem. But sometimes it&#;s about the recipient&#;s server blacklisting yours, or an invalid email address.

Configure your settings providing a username+password authentication. If the error persists, check all your recipients&#; addresses and if you&#;ve been blacklisted.

The recipient address rejected your service call 121 fatal error normally, it&#;s an error caused by an anti-spam filter.

Your message has been detected and labeled as spam. You must ask the recipient to whitelist you.

It usually defines a non-existent email address on the remote side.

Though it can be returned also by the recipient&#;s firewall (or when the incoming server is down), the great majority of errors simply tell that the recipient email address doesn&#;t exist. You should contact the recipient otherwise and get the right address.

&#;User not local or invalid address – Relay denied&#. Meaning, if both your address and the recipient&#;s are not locally hosted by the server, a relay can be interrupted.

It&#;s a (not very clever) strategy to prevent spamming. You should contact your ISP and ask them to allow you as a certified sender. Of course, with a professional SMTP provider like turboSMTP you won&#;t ever deal with this issue.

&#;Requested mail actions aborted – Exceeded storage allocation&#;: simply put, the recipient&#;s mailbox has exceeded its limits.

Try to send a lighter message: that usually happens when you dispatch emails with big attachments, service call 121 fatal error check them first.

&#;Requested action not taken – Mailbox name invalid&#. That is, there&#;s an incorrect email address into the recipients line.

Check all the addresses in the TO, CC and BCC field. There should be an error or a misspelling somewhere.

This means that the transaction has failed. It&#;s a permanent error and the server will not try to send the message again.

The incoming server thinks that your email is spam, or your IP has been blacklisted. Check carefully if you ended up in some spam lists, or rely on a professional SMTP service like turboSMTP that will nullify this problem.

Appendix A: ODBC Error Codes

General warningAll ODBC functions except:

SQLError

SQLGetDiagField

SQLGetDiagRecCursor operation conflictSQLExecDirect

SQLExecute

SQLParamData

SQLSetPosDisconnect errorSQLDisconnectNULL value eliminated in set functionSQLExecDirect

SQLExecute

SQLParamDataString data, right-truncatedSQLBrowseConnect

SQLBulkOperations

SQLColAttribute

SQLDataSources

SQLDescribeCol

SQLDriverConnect

SQLDrivers

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetConnectAttr

SQLGetCursorName

SQLGetData

SQLGetDescField

SQLGetDescRec

SQLGetEnvAttr

SQLGetInfo

SQLGetStmtAttr

SQLNative

Sql SQLParamData

SQLPutData

SQLSetCursorNamePrivilege not revokedSQLExecDirect

SQLExecute

SQLParamDataPrivilege not grantedSQLExecDirect

SQLExecute

SQLParamData01S00Invalid connection string attributeSQLBrowseConnect

SQLDriverConnec01S01Error in rowSQLBulkOperations

SQLExtendedFetch

SQLSetPos01S02Option value changedSQLBrowseConnect

SQLConnect

SQLDriverConnect

SQLExecDirect

SQLExecute

SQLParamData

SQLPrepare

SQLSetConnectAttr

SQLSetDescField

SQLSetEnvAttr

SQLSetStmtAttr01S06Attempt to fetch before the result set returned the first rowsetSQLExtendedFetch

SQLFetchScroll01S07Fractional truncationSQLBulkOperations

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLParamData

SQLSetPos01S08Error saving File DSNSQLDriverConnect01S09Invalid keywordSQLDriverConnectWrong number of parametersSQLExecDirect

SQLExecuteCOUNT field incorrectSQLExecDirect

SQLExecute

SQLParamDataPrepared statement not a cursor-specificationSQLColAttribute

SQLDescribeColRestricted data type attribute violationSQLBindCol

SQLBindParameter

SQLBulkOperations

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLParamData

SQLPutData

SQLSetPosInvalid descriptor indexSQLBindCol

SQLBindParameter

SQLBulkOperations

SQLColAttribute

SQLDescribeCol

SQLDescribeParam

SQLFetch

SQLFetchScroll

SQLGetData

SQLGetDescField

SQLGetDescRec

SQLParamData

SQLSetDescField

SQLSetDescRecSQLSetPos07S01Invalid use of default parameterSQLExecDirect

SQLExecute

SQLParamData

SQLPutDataClient unable to establish connectionSQLBrowseConnect

SQLConnect

SQLDriverConnectConnection name in useSQLBrowseConnect

SQLConnect

SQLDriverConnect

SQLSetConnectAttrConnection not openSQLAllocHandle

SQLDisconnect

SQLEndTran

SQLGetConnectAttr

SQLGetInfo

SQLNativeSql

SQLSetConnectAttrServer rejected the connectionSQLBrowseConnect

SQLConnect

SQLDriverConnectConnection failure during transactionSQLEndTran08S01Communication link failureSQLBrowseConnect

SQLColumnPrivileges

SQLColumns

SQLConnect

SQLCopyDesc

SQLDescribeCol

SQLDescribeParam

SQLDriverConnect

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLGetConnectAttr

SQLGetData

SQLGetDescField

SQLGetDescRec

SQLGetFunctions

SQLGetInfo

SQLGetTypeInfo

SQLMoreResults

SQLNativeSql

SQLNumParams

SQLNumResultCols

SQLParamData

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLPutData

SQLSetConnectAttr

SQLSetDescField

SQLSetDescRec

SQLSetEnvAttr

SQLSetStmtAttr

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTables21S01Insert value list does not match column listSQLExecDirect

SQLPrepare21S02Degree of derived table does not match service call 121 fatal error listSQLBulkOperations

SQLExecDirect

SQLExecute

SQLParamData

SQLPrepare

SQLSetPosString data, right-truncatedSQLBulkOperations

SQLExecDirect

SQLExecute

SQLFetch

SQLFetchScroll

SQLParamData

SQLPutData

SQLSetDescField

SQLSetPosIndicator variable required but not suppliedSQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLParamDataNumeric value service call 121 fatal error of rangeSQLBulkOperations

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLGetInfo

SQLParamData

SQLPutData

SQLSetPosInvalid datetime formatSQLBulkOperations

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLParamData

SQLPutData

SQLSetPosDatetime field overflowSQLBulkOperations

SQLExecDirect

QLParamData

SQLPutDataDivision by zeroSQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLPutDataInterval field overflowSQLBulkOperations

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLParamData

SQLPutData

SQLSetPosInvalid character value for cast specificationSQLBulkOperations

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLGetData

SQLParamData

SQLPutData

SQLSetPosInvalid escape characterSQLExecDirect

SQLExecute

SQLPrepareInvalid escape sequenceSQLExecDirect

SQLExecute

SQLPrepareString data, length mismatchSQLParamDataIntegrity constraint violationSQLBulkOperations

SQLExecDirect

SQLExecute

SQLParamData

SQLSetPosInvalid cursor stateSQLBulkOperations

SQLCloseCursor

SQLColumnPrivileges

SQLColumns

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLGetData

SQLGetStmtAttr

SQLGetTypeInfo

SQLNativeSql

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLSetConnectAttr

SQLSetCursorName

SQLSetPos

SQLSetStmtAttr

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesInvalid transaction stateSQLDisconnect25S01Transaction stateSQLEndTran25S02Transaction is still activeSQLEndTran25S03Transaction is rolled backSQLEndTranInvalid authorization specificationSQLBrowseConnect

SQLConnect

SQLDriverConnectInvalid cursor nameSQLExecDirect

SQLPrepare

SQLSetCursorName3CDuplicate cursor nameSQLSetCursorName3DInvalid catalog nameSQLExecDirect

SQLPrepare

SQLSetConnectAttr3FInvalid schema nameSQLExecDirect

SQLPrepareSerialization failureSQLBulkOperations

SQLColumnPrivileges

SQLColumns

SQLEndTran

SQLExecDirect

SQLExecute

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLGetTypeInfo

SQLMoreResults

SQLParamData

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLSetPos

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesIntegrity constraint violationSQLEndTranStatement completion unknownSQLBulkOperations

SQLColumnPrivileges

SQLColumns

SQLExecDirect

SQLExecute

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLGetTypeInfo

SQLMoreResults

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLParamData

SQLSetPos

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesSyntax error or access violationSQLBulkOperations

SQLExecDirect

SQLExecute

SQLParamData

SQLPrepare

SQLSetPos42S01Base table or view already existsSQLExecDirect

SQLPrepare42S02Base table or view not foundSQLExecDirect

SQLPrepare42S11Index already existsSQLExecDirect

SQLPrepare42S12Index not foundSQLExecDirect

SQLPrepare42S21Column already existsSQLExecDirect

SQLPrepare42S22Column not foundSQLExecDirect

SQLPrepareWITH CHECK OPTION violationSQLBulkOperations

SQLExecDirect

SQLExecute

SQLParamData

SQLSetPosHYGeneral errorAll ODBC functions except:

SQLError

SQLGetDiagField

SQLGetDiagRecHYMemory allocation errorAll ODBC functions except:

SQLError

SQLGetDiagField

SQLGetDiagRecHYInvalid application buffer typeSQLBindCol

SQLBindParameter

SQLGetDataHYInvalid SQL data typeSQLBindParameter

SQLGetTypeInfoHYAssociated statement is not preparedSQLCopyDesc

SQLGetDescField

SQLGetDescRecHYOperation canceledAll ODBC functions that can be processed asynchronously:

SQLBrowseConnect

SQLBulkOperations

SQLColAttribute

SQLColumnPrivileges

SQLColumns

SQLConnect

SQLDescribeCol

SQLDescribeParam

SQLDisconnect

SQLDriverConnect

SQLEndTran

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLGetData

SQLGetTypeInfo

SQLMoreResults

SQLNumParams

SQLNumResultCols

SQLParamData

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLPutData

SQLSetConnectAttr

SQLSetPos

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesHYInvalid use of null pointerSQLAllocHandle

SQLBindParameter

SQLBulkOperations

SQLColumnPrivileges

SQLColumns

SQLExecDirect

SQLForeignKeys

SQLGetCursorName

SQLGetData

SQLGetFunctions

SQLNativeSql

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLPutData

SQLSetConnectAttr

SQLSetCursorName

SQLSetEnvAttr

SQLSetStmtAttr

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesHYFunction sequence errorSQLAllocHandle

SQLBindCol

SQLBindParameter

SQLBulkOperations

SQLCloseCursor

SQLColAttribute

SQLColumnPrivileges

SQLColumns

SQLCopyDesc

SQLDescribeCol

SQLDescribeParam

SQLDisconnect

SQLEndTran

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLFreeHandle

SQLFreeStmt

SQLGetConnectAttr

SQLGetCursorName

SQLGetData

SQLGetDescField

SQLGetDescRec

SQLGetFunctions

SQLGetStmtAttr

SQLGetTypeInfo

SQLMoreResults

SQLNumParams

SQLNumResultCols

SQLParamData

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLPutData

SQLRowCount

SQLSetConnectAttr

SQLSetCursorName

SQLSetDescField

SQLSetEnvAttr

SQLSetDescRec

SQLSetPos

SQLSetStmtAttr

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesHYAttribute cannot be set nowSQLBulkOperations

SQLParamData

QLSetPos

SQLSetStmtAttrHYInvalid transaction operation codeSQLEndTranHYMemory management errorAll ODBC functions except:

SQLGetDiagField

SQLGetDiagRecHYLimit on the number of handles exceededSQLAllocHandleHYNo cursor name availableSQLGetCursorNameHYCannot modify an implementation row descriptorSQLCopyDesc

SQLSetDescField

SQLSetDescRecHYInvalid use of an automatically allocated descriptor handleSQLFreeHandle

SQLSetStmtAttrHYServer declined cancel requestSQLCancelHYNon-character and non-binary data sent in piecesSQLPutDataHYAttempt to concatenate a null valueSQLPutDataHYInconsistent descriptor informationSQLBindParameter

SQLCopyDesc

SQLGetDescField

SQLSetDescField

SQLSetDescRecHYInvalid attribute valueSQLSetConnectAttr

SQLSetEnvAttr

SQLSetStmtAttrHYInvalid string or buffer lengthSQLBindCol

SQLBindParameter

SQLBrowseConnect

SQLBulkOperations

SQLColAttribute

SQLColumnPrivileges

SQLColumns

SQLConnect

SQLDataSources

SQLDescribeCol

SQLDriverConnect

SQLDrivers

SQLExecDirect

SQLExecute

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLGetConnectAttr

SQLGetCursorName

SQLGetData

SQLGetDescField

SQLGetInfo

SQLGetStmtAttr

SQLNativeSql

SQLParamData

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLPutData

SQLSetConnectAttr

SQLSetCursorName

SQLSetDescField

SQLSetDescRec

SQLSetEnvAttr

SQLSetStmtAttr

SQLSetPos

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesHYInvalid descriptor field identifierSQLColAttribute

SQLGetDescField

SQLSetDescFieldHYInvalid attribute/option identifierSQLAllocHandle

QLBulkOperations

SQLCopyDesc

SQLDriverConnect

SQLEndTran

SQLFreeStmt

SQLGetConnectAttr

SQLGetEnvAttr

QLParamData

SQLSetConnectAttr

SQLSetDescField

SQLSetEnvAttr

SQLSetPos

SQLSetStmtAttrHYFunction type out of rangeSQLGetFunctionsHYInvalid information typeSQLGetInfoHYColumn type out of rangeSQLSpecialColumnsHYScope type out of rangeSQLSpecialColumnsHYNullable type out of rangeSQLSpecialColumnsHYUniqueness option type out of rangeSQLStatisticsHYAccuracy option type out of rangeSQLStatisticsHYInvalid retrieval codeSQLDataSources

SQLDriversHYInvalid precision or scale valueSQLBindParameterHYInvalid parameter typeSQLBindParameter

SQLExecDirect

SQLExecute

SQLParamData

SQLSetDescFieldHYFetch type out of rangeSQLExtendedFetch

SQLFetchScrollHYRow value out of rangeSQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLSetPosHYInvalid cursor positionSQLExecDirect

SQLExecute

SQLGetData

SQLGetStmtAttr

SQLNativeSql

SQLParamData

SQLSetPosHYInvalid driver completionSQLDriverConnectHYInvalid bookmark valueSQLExtendedFetch

SQLFetchScrollHYC00Optional feature not implementedSQLBindCol

SQLBindParameter

SQLBulkOperations

SQLColAttribute

SQLColumnPrivileges

SQLColumns

SQLDriverConnect

SQLEndTran

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLFetch

SQLFetchScroll

SQLForeignKeys

SQLGetConnectAttr

SQLGetData

SQLGetEnvAttr

SQLGetInfo

SQLGetStmtAttr

SQLGetTypeInfo

SQLParamData

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLSetConnectAttr

SQLSetEnvAttr

SQLSetPos

SQLSetStmtAttr

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesHYT00Timeout expiredSQLBrowseConnect

SQLBulkOperations

SQLColumnPrivileges

SQLColumns

SQLConnect

SQLDriverConnect

SQLExecDirect

SQLExecute

SQLExtendedFetch

SQLForeignKeys

SQLGetTypeInfo

SQLParamData

SQLPrepare

SQLPrimaryKeys

SQLProcedureColumns

SQLProcedures

SQLSetPos

SQLSpecialColumns

SQLStatistics

SQLTablePrivileges

SQLTablesHYT01Connection timeout expiredAll ODBC functions except:

SQLDrivers

SQLDataSources

SQLGetEnvAttr

SQLSetEnvAttrIMDriver does not support this functionAll ODBC functions except:

SQLAllocHandle

SQLDataSources

SQLDrivers

SQLFreeHandle

SQLGetFunctionsIMData source name not found and no default driver specifiedSQLBrowseConnect

SQLConnect

SQLDriverConnectIMSpecified driver could not be loadedSQLBrowseConnect

SQLConnect

SQLDriverConnectIMDriver's SQLAllocHandle on SQL_HANDLE_ENV failedSQLBrowseConnect

SQLConnect

SQLDriverConnectIMDriver's SQLAllocHandle on SQL_HANDLE_DBC failedSQLBrowseConnect

SQLConnect

SQLDriverConnectIMDriver's SQLSetConnectAttr failedSQLBrowseConnect

SQLConnect

SQLDriverConnectIMNo data source or driver specified; dialog prohibitedSQLDriverConnectIMDialog failedSQLDriverConnectIMUnable to load translation DLLSQLBrowseConnect

SQLConnect

SQLDriverConnect

SQLSetConnectAttrIMData source name too longSQLBrowseConnect

SQLConnect

SQLDriverConnectIMDriver name too longSQLBrowseConnect

SQLDriverConnectIMDRIVER keyword syntax errorSQLBrowseConnect

SQLDriverConnectIMTrace file errorAll ODBC functions.IMInvalid name of File DSNSQLDriverConnectIMCorrupt file data sourceSQLDriverConnect

0 Comments

Leave a Comment