Common Error codes that may be encountered during various operations.
(Last modified: 25May2001)
This document (10018286) is provided subject to the disclaimer at the end of this document.
fact
Telephony 2.21g
goal
Common Error codes that may be encountered during various operations.
fix
Error Codes
CSTA Universal Failure Events
The errors listed below are errors that occurred when an application requested a driver or server function and there was a failure. The first column gives the number identifying the error. The second column indicates the type of error (such as "State Incompatibility Errors" or "System Resource Availability Errors") and provides a description of the error.
Corrective action for some errors can be self-evident. For example, if a wrong number was called, or if a call was deleted or dropped before the requested action could take place, check the number and repeat the request. In other cases, the number of calls may have exceeded the capacity of the switch or the server. In these cases, call the driver or switch support number. To determine corrective action in the remaining cases, call the application support number.
Error Code DESCRIPTION
Operations Class
0 This is a generic, unspecified error.
1 Server has detected an error in the operations class that is not one of the defined errors. The server cannot be more specific.
2 The request is not compatible with the object.
3 The parameter has a value that is not in the range defined for the server.
4 The parameter has a value that is not known to the server.
5 The calling device is not valid.
6 The called device is not valid.
7 The request cannot be provided because the specified device is not authorized for the service.
8 The request cannot be provided because the specified device is not authorized for the service.
9 The request cannot be provided because the called device is not authorized for the service.
10 The request cannot be provided because the calling device is not authorized for the service.
11 The call identifier is not valid.
12 The CSTA device identifier is not valid.
13 The CSTA connection identifier is not valid.
14 The service request specified a destination that is invalid.
15 The service request specified a feature that is invalid.
16 The service request indicated an allocation condition that is not valid.
17 The service request specified a cross reference id that is not in use at this time.
18 The service request specified an object type that is outside the range of valid object types for the service.
19 The request violates a security requirement.
State Incompatibility Errors
21 The server is unable to be more specific.
22 The object is in an incorrect state for the service.
23 The connection Identifier specified in the active call parameter of the request is not in the correct state.
24 The requested service operates on an active call, but there is no active call.
25 The requested service operates on a held call, but the call is not in the held state.
26 There is no call associated with the CSTA connection identifier of the Clear call request.
27 There is no connection for the CSTA connection identifier specified as the connection to be cleared.
28 There is no call active for the CSTA connection identifier specified as the call to be answered.
29 There is no call active for the CSTA connection identifier specified as the call to be completed.
System Resource Availability Errors
31 The server is unable to be more specific.
32 The service is supported by the server, but is temporarily busy.
33 An internal resource is busy. There is a high probability that the service will succeed if retried.
34 The service requires a resource that is out of service.
35 The server sub-domain is busy.
36 The server sub-domain is out of service.
37 The request will exceed the servers overall limit of monitors.
38 The request will exceed the server's limit on the number of members of a conference.
Subscribed Resource Availability Errors
41 The server is unable to be more specific.
42 The request would exceed the server's limit of monitors for the specified object.
43 The limit of external trunks would be exceeded by this request.
44 The limit of outstanding requests would be exceeded by this request.
Performance Management Errors
51 The server is unable to be more specific.
52 A performance limit has been exceeded.
Security Errors
60 The server is unable to be more specific.
61 The server has detected an error in the sequence number of the operation.
62 The server has detected an error in the time stamp of the operation.
63 The server has detected an error in the PAC of the operation.
64 The server has detected an error in the seal of the operation.
70 This is a PBX Driver internal error, but it cannot be any more specific. A system administrator may find more detailed information about this error in the error logs. Report this error to the PBX driver vendor.
71 This is a PBX Driver internal error, but not a defined error. A system administrator should check the error logs for more detailed information about this error. Report this error to the PBX Vendor.
72 The invoke Id in the service request is being used by another outstanding service request. This service request is rejected. The outstanding service request with the same invoke Id is still valid.
73 The service request from a client application is not defined in the API. A CSTA request with a 0 or negative Invoke ID will receive this error.
75 The system lacks internal resources such as the memory or data records to process a service request. This failure may reflect a temporary situation. The application should retry the request.
76 An acsOpenStream session is terminating. This error is sent for every outstanding CSTA request of this ACS Handle. If the session is not closed in an orderly fashion, the application may not receive this error. For example, a user may power off the PC before the application issues an acsCloseStream request and waits for the confirmation event. In this case, the acsCloseStream is issued by the Tserver on behalf of the application and there is no application to receive this error. If an application issues an acsCloseStream request and waits for its confirmation event, the application will receive this error for every outstanding request.
77 The system detects that it cannot provide the service due to the failure or shutting down of the communication link between the Telephony Server and the PBX. This error is sent for every outstanding CSTA request for every ACS Handle affected. Although the link is down or the switch is out of service, the PBX remains loaded and advertised. When the PBX is in this state, all CSTA Service requests from a client will receive a negative acknowledgment with this unique error code.
78 The PBX Driver did not receive the response of a service request sent to the PBX in the allotted time. The timer of the request has expired. The request is canceled and negatively acknowledged with this unique error code. When this occurs, the communication link between the Telephony Server and the PBX switch may be congested. This can happen when the PBX and/or the Tserver exceeds their capacity.
79 For a device, the PBX processes one service request at a time. The PBX driver queues CSTA requests for a device. Only a limited number of CSTA requests can be queued on a device. If this number is exceeded, the incoming client request is negatively acknowledged with this unique error code.
ROSE Error Codes from CSTA Module
80 The type of the APDU, as evidenced by its Type Identifier, is not one of the four defined by Recommendation X.229.
81 The structure of the APDU does not conform to Recommendation X.229.
82 The structure of the APDU does not conform to the standard notation and encoding defined in Recommendation X.208 and X.209.
83 The association-initiator is not willing to perform the invoked operation because it is about to attempt to release the application -association.
84 There is no operation in progress with an Invoke-ID equal to the specified Linked-ID.
85 The invoked operation, referred to by the Link-ID, is not a parent-operation.
86 The invoked child operation, referred to by the Linked-ID, is not allowed by the invoked parent-operation.
87 The type of the Result parameter supplied is not that agreed between the ROSE-users.
88 The reported error is not one of those agreed between the ROSE-users.
89 The reported error is not one that the invoked operation may report.
90 The type of error parameter supplied is not that agreed between the ROSE-users.
ACS Universal Failure Events
These errors usually do not indicate a problem with the system and should be handled accordingly by the application.
ERROR CODE DESCRIPTION CORRECTIVE ACTION
-1 The API version requested is not supported by the existing API client library. This is an application error; contact the application developer.
-2 One or more of the parameters is invalid This is an application error; contact the application developer.
-5 This error code indicates the requested server is not present in the network. Is the server up? Was the wrong server name used? Are physical connections (wiring) intact?
-6 This return value indicates that there are insufficient resources to open an connection. Is the correct version of IPX being used? If yes, contact the application developer since the application is trying to open too many connections or is opening streams but not closing them.
-7 The user buffer size was smaller than the size of the next available event. This is an application error; contact the application developer.
-8 Following initial connection, the server has failed to respond within a specified amount of time (typically 10 seconds) Call your support number and report error.
-9 The connection has encountered an unspecified error. This is typically a version mismatch. Has some software been replaced or upgraded recently? If not, call your support number.
-10 The ACS handle is invalid. This is an application error; contact the application developer.
-11 The connection has failed due to network problems. No further operations are possible on this stream. A connection has been lost. Is the Tserver down? Is there physical connectivity?
-12 Not enough buffers were available to place an outgoing message on the send queue. No message has been sent. This could be either an application error or an overloaded Tserver. Use Tserver TSA to check traffic. If traffic reports show no overload, call application developer.
-13 The send queue is full. No message has been sent. This could be either an application error or an overloaded Tserver. Use Tserver TSA to check traffic. If traffic reports show no overload, call application developer.
0 The client library detected that the connection failed. 1. Other errors may have been sent by the Tserver before the connection was taken down. If so, follow the procedures for this error. 2. If no other errors were received from the Tserver first, then verify that the Tserver/server is still running and look for LAN problems.
1 The Tserver could not begin execution of a thread group which is necessary for it to run properly. There is a serious system problem. These errors will appear in the Tserver error logs. Consult the logs for the NetWare return code.
2 The Tserver has an internal system error. This error should never be returned to an application or appear in the Tserver error logs. If this event is generated by the Tserver, then there is a software problem with the Tserver. Call your support number.
3 The specified driver has not sent any heart beat messages to the Tserver for the last three minutes. The driver may be in an inoperable state. Look for driver error messages and/or contact the driver vendor to determine why it is no longer sending the heartbeat messages.
4 This error is no longer used. This error should never be returned to an application or appear in the Tserver error logs. If this event is generated by the Tserver, then there is a software problem with the Tserver. Call your support number.
5 The Tserver was unable to release Tserver driver interface (TSDI) memory back to NetWare. Consult the error log files for a corresponding error message. The error code associated with this error message should be one of the following: -1 - a corresponding FATAL error will be generated indicating the NetWare call, SetNLMID(), failed. Follow the description for this error message. -2, -9, or -10 - internal Tserver software error. Collect the error log files and message trace files and escalate the problem
6 The Tserver was unable to send a message to the specified driver. Consult the error log files for a corresponding error message. 1. This error can indicate that the driver unregistered while the Tserver was processing messages for it or that there is a software problem with the Tserver. Verify that the driver was loaded at the time of the error. 2. The error code (rc) should be one of the following: -2, -6, -9, -10. All these errors indicate an internal Tserver software error. Collect the error log files and message trace files and escalate the problem.
7 The Tserver was unable to receive a message from the specified driver. Consult the error log files for a corresponding error message. The error code (rc) should be one of the following: -1 - a corresponding FATAL error will be generated indicating the NetWare call, SetNLMID(), failed. Follow the description for this error message. -2 - internal Tserver software error. Collect the error log files and message trace files and escalate the problem.
8 A driver, internal to the Tserver, failed to register properly. The Tserver will not run properly without this driver. There is a serious system problem. These errors will appear in the Tserver error logs. Consult the logs for the NetWare return code.
9 A NetWare SPX call failed in the Tserver. There is a serious system problem. These errors will appear in the Tserver error logs. Consult the logs for the NetWare return code.
10 This error code has multiple meanings and should not be returned to the application. Consult the error log files for a corresponding error message.
11 The Tserver was unable to allocate a piece of memory. 1. Verify that the server has enough memory to run the driver and Tserver. 2. If the server has enough memory, then the driver has reached its limit of how much memory the Tserver will allocate. This limit is chosen by the driver when it registers with the Tserver. Call your support number.
12 The Tserver was unable to encode a message from a driver. This error should never be returned to an application. Consult the error log files for a corresponding error message. If the error appears in the error logs, it indicates that the Tserver does not recognize the message from the driver. Call your support number.
13 The Tserver was unable to decode a message from a client workstation. The application is most likely using an old version of the client library. Check the version to ensure that it supports this message. If you have the latest DLL, then call your support number.
14 The Tserver tried to process a request with a bad client connection ID number. 1. This error should never be returned to an application. If it appears in the Tserver error logs, it indicates that an application may have been terminated or the client workstation was disconnected from the network while the Tserver was processing messages for it. 2. Determine if either of these two cases is true. 3. If this error occurs repeatedly and these conditions are not true, call your support number.
15 The Tserver received a message from the client to be sent to a driver that is not a valid TSAPI request. Verify that the message the client is sending is a valid TSAPI request. If it is then there is a problem with the Tserver. Call your support number.
16 The Tserver received an ACSOpenStreamConfEvent from a driver which does not have one of the version fields set correctly. The confirmation event will still be sent to the client with the version field set to "UNKNOWN". This error will appear in the error log files and will indicate which field is invalid. Call your support number.
17 The Tserver received a message from the specified driver that is too large for it to process. Use the Telephony Services administrator to increase the number of Send ECBs for this driver.
18 The Tserver does not have the internal resources to process this request. This error should never be returned to an application or appear in the Tserver error logs. If this event is generated by the Tserver, then there is a software problem with the Tserver. Call your support number.
19 The Tserver was unable to initialize the Security Database when loading. Look for other errors that might indicate a data base initialization problem.
20 The Tserver determined that a particular TSAPI message did not require a Security Database validation. This code is an internal one and should never be returned to an application. This error should never be returned to an application or appear in the Tserver error logs. If this event is generated by the Tserver, then there is a software problem with the Tserver. Call your support number.
21 The Tserver determined that a particular TSAPI message did require a Security Database validation. This code is an internal one and should never be returned to an application. This error should never be returned to an application or appear in the Tserver error logs. If this event is generated by the Tserver, then there is a software problem with the Tserver. Call your support number.
22 The Tserver's internal table of API calls indicating which level of security to perform on a specific request is corrupted. This error should never be returned to an application or appear in the Tserver error logs. If this event is generated by the Tserver, then there is a software problem with the Tserver. Call your support number.
23 The Tserver rejected an ACSOpenStream request because the server ID in the message did not match a PBX driver supported by this Tserver. A software problem has occurred with the client library. Call your support number.
24 The stream type of an ACSOpenStream request was invalid. A software problem has occurred with the client library. Call your support number.
25 The password, login, or both from an ACSOpenStream request did pass the Tserver authentication checks. A Tserver running on a 3.x NetWare server (or on a 4.x NetWare server using TSRVBTRV.NLM for the SDB) uses the NetWare Bindery to authenticate users. The users must have a valid entry in the NetWare Bindery in order to use Telephony Services. A Tserver running on a 4.x NetWare server using TSRVNDS.NLM for the SDB uses NDS authentication mechanisms. A user must be logged into the NDS tree before using Telephony Services or the server must have Bindery Emulation on and the user must have a valid Bindery entry. 1. Validate that the user login and password were entered correctly into the application. 2. Using the syscon command, verify the user has a NetWare login on the NetWare file server where the Tserver is running. From the "Available Topics" menu in syscon choose "User Information." Validate that the user's login is in the list of "User Names." Use the "Insert" key to create a login and associated password for this user if none exists. 3. Verify the user has a user object in the Tserver security database by using the NetWare TSA Windows application: From the Admin option, select "Users." Validate that the user's login is in "User Information" and that the login in the security database exactly matches the login on the NetWare server. Use the Create option to create a login for this user if none exists. Note: Passwords are not kept in the Tserver security database.
26 No user object was found in the security database for the login specified in the ACSOpenStream request. Verify the user has a user object in the security database by using the NetWare TSA Windows application: Select "Users" from the "Admin" main menu. Validate that the user's login in the "User Information" list and the login in the security database exactly match the login on the NetWare Server. Create a login for this user if none exists. Note: Passwords are not kept in the Tserver security database.
27 No device object was found in the security database for the device specified in the API call. Create a device object for the device the user is trying to control in the Tserver security database by using the NetWare TSA Windows application: Select "Devices" from the "Admin" main menu. Use the Create option to create a device record for this device. Note: Make sure the assigned PBX for this device includes the telephony server being administered.
28 The specified device in an API call was not found on any device group administered for this user. The telephony server translates this error into more specific errors which indicate on which list the device is not listed. If this error is returned to an application, a software problem has occurred in the telephony server NLM. Call your support number.
30 The telephony server rejected a user's request to control a device because all of the following are true: The Primary Device ID of the User's Home Worktop Record does not match the device and the Secondary Device Group is empty, or The fields "Home Worktop Device ID" and "LAN Address" are blank in the user's record indicating the user is not associated with any Worktop. The access group in the "Classes of Service" administration in this user's record which corresponds to the action being attempted (Call Control, Device/Device Monitoring, Call/Device Monitoring or Routing) is empty. The user is not sitting at his or her home worktop (as defined by the LAN Address in the worktop object associated with this user) and the "Restrict User Access to Home Worktop" option is enabled. Change the user's administration so that the user has permission to control the device through either the user's worktop object (worktop administration) or through one of the Classes of Service (user administration).
31 An application issued the cstaGetDevices() call, requesting a list of the users away worktop devices, however, this user does not have a valid away worktop on this ACS stream. This error should never be returned to an application or appear in the Tserver error logs. If this event is generated by the Tserver, then there is a software problem with the Tserver. Call your support number.
32 The user has no home worktop in the Security database associated with their user record. This is a valid administration configuration. This error should never be returned to an application or appear in the Tserver error logs. If this event is generated by the Tserver, then there is a software problem with the Tserver. Call your support number.
33 The Tserver could not validate a device in a TSAPI request (i.e, cstaMakeCall()) against the users Security database entries. The device was not found in the users record, home worktop record or away worktop record. 1. If the user should have permission to control this device, add the device to the users record, worktop record or away worktop record. See the Network Managers guide for the appropriate administration.
34 The Tserver read a device object from the security database that contained corrupted information. The device object did not contain a PBX index value which is a violation of the SDB structure. This error should never be returned to an application or appear in the Tserver error logs. If this event is generated by the Tserver, then there is a software problem with the Tserver. Call your support number.
35 The PBX administered for this device does not contain the CTI link to which the user opened an connection. 1. Validate that the user opened the connection to the correct CTI link. 2. If the CTI link to which the stream was opened can support this device, then add this CTI link to the PBX by using the "PBX" option (on the "Admin" main menu) in the NetWare TSA Windows application.
36 This error is no longer used. This error should never be returned to an application or appear in the Tserver error logs. If this event is generated by the Tserver, then there is a software problem with the Tserver. Call your support number.
37 A NetWare memory allocation call failed in the Tserver. There is a serious system problem. These errors will appear in the Tserver error logs. Consult the logs for the NetWare return code.
38 The Tserver has received a message from the application or the driver that it does not recognize. Verify that the offending message is valid according to TSAPI. If it is a valid message then there may be a software problem with the Tserver. Call your support number.
39 The device in the API call is on an exception list which is administered as part of the information for this user. 1. The telephony server translates this error into more specific errors which indicate which list the device is not on. If this error is returned to an application, a software problem has occurred in the telephony server NLM. Call your support number.
40 The user login which is attempting to open an TSA stream to a PBX driver has an Admin Access group administered, but this Admin Access group does not contain this PBX driver. 1. If this user is allowed to perform TSA operations on a driver, then in the TSA Windows application, select the "TSA Access Groups" option under the "Admin" main menu. 2. Select the TSA Access Group to which this user should be added, or create a new group for this user via the "Create" button. Then, select the new group (you may have to use the "Advertised Services" option on the "Admin" main menu first to administer the CTI link names that will be added to this CTI link group). Add this user to the TSA Access Group via the "Allowed Users" option.
41 An attempt to open a TSA stream to TSA driver name was made but this advertised service is not in the security database. 1. If this user is allowed to perform TSA operations on this PBX driver, then, in the TSA Windows application, select "Advertised Services" under the "Admin" main menu. 2. Create the Tserver TSA or Tlink TSA advertised service. 3. Use the TSA Access Group option on the "Admin" main menu to select the TSA Access Group to which this user should be added or create a new group for this user with via the "Create" button and then select the new group. User the "Allowed Users" option to add this user to the TSA Access Group.
42 The user licenses maximum has been exceeded on this telephony server. No new User Licenses may be granted (that is, no new connection may be open; however, if a user/application has an existing connection open to a driver, they may open another connection to the same driver from the same Worktop using the same login). 1. Force current users off the system by using the Telephony Services TSA Windows application and selecting "Client" under the "Status" option on the "Admin" main menu. On the "Client Status Information" dialog box, highlight the client you wish to disconnect and select "View." On the "Client Detail Information" dialog box, use the "Drop Connections" option to drop all current connections for this client. This will free up one or more user licenses. 2. Or, obtain a larger user licensed copy of the NetWare NLM.
43 The TSA Windows application was used to drop the connection for this client. Determine why the Tserver administrator dropped the client connection.
44 The Tserver could not find a version stamp on the security database files. There is a serious problem with the files that make up the Tserver security database. Call your support number.
45 The Tserver found old, out of date version stamps on the security database files. There is a serious problem with the files that make up the Tserver security database. Call your support number.
46 The Tserver received a bad SPX packet so the client connection was dropped. SPX reported a problem on this connection; try again. If this happens repeatedly, call your support number.
47 The Tserver rejected a user's request to open a connection, so the connection was dropped. An error code should have been returned in response to the ACSOpenStream() request in the ACSUniversalFailureConfEvent. Follow the procedures defined for that error code.
48 An attempt was made to open a second TSA connection to the Tserver TSA driver when there was already an established stream to this driver. The Tserver only allows one open Tserver TSA driver stream at a time. NOTE: Multiple TSA streams to other drivers are allowed. Determine who else is running the Telephony Services TSA Windows application (without the aid of the Tserver).
49 The telephony server rejected a user's request to control a device because all of the following are true: The Primary Device ID of the user's Home Worktop Record does not match the device and the device is not a member of the Secondary Device Group of the Home Worktop Record. The Access Group in the "Classes of Service" administration in this user's record which corresponds to the action being attempted (Call Control or Device/Device Monitoring) is empty or the device is not a member of this access group. If the user is not working from his or her home worktop (that is, the connection has been opened from an "Away" Worktop), then the Primary Device ID of the "Away" Worktop Record does not match the device and the device is not a member of the Secondary Device Group (or this secondary group is blank) of the "Away" Worktop Record. Change the user's administration so that the user has permission to control the device through either the worktop object (worktop administration) or through one of the "Classes of Service" (user administration).
50 The telephony server rejected a user's request to control a device because all of the following are true: The Primary Device ID of the user's Home Worktop Record does not match the device and the Secondary Device Group is empty, or The "Home Worktop Device ID" and "LAN Address" fields are blank in the user's record indicating the user is not associated with any worktop. The device is not on the Call Control Access Group in the "Classes of Service" administration in this user's record. If the user is not working from his or her home worktop (that is, the connection has been opened from an "Away" Worktop), then the Primary Device ID of the "Away" Worktop Record does not match the device and the device is not a member of the Secondary Device Group (or this secondary group is blank) of the "Away" Worktop Record. Change the user's administration so that the user has permission to control the device through either the worktop object (worktop administration) or through the Call Control Access Group Classes Of Service (user administration).
51 The telephony server rejected a user's request to control a device because all of the following are true: The Primary Device ID of the user's Home Worktop Record does not match the device and the Secondary Device Group is empty, or The "Home Worktop Device ID" and "LAN Address" fields are blank in the user's record indicating the user is not associated with any worktop The Access Group in the "Classes of Service" administration in this user's record which corresponds to the action being attempted (Call Control or Device/Device Monitoring) is empty. The user is not working from his or her home worktop (that is, the connection has been opened from an "Away" Worktop as defined by the LAN Address fields), and the Primary Device ID of the "Away" Worktop Record does not match the device and the device is not a member of the Secondary Device Group of the "Away" Worktop Record. Change the user's administration so that the user has permission to control the device through either the user's worktop object (worktop administration) or through one of the "Classes of Service" (user administration).
52 The telephony server rejected a user's request to control a device because the device is not a member of the Routing Access Group in the Classes Of Service administration in this user's record. Change the user's administration so that the user has permission to control the device through the Routing Access Group "Classes of Service" (User administration).
53 The telephony server rejected a user's request to control a device because all of the following are true: The Primary Device ID of the user's Home Worktop Record does not match the device and the Secondary Device Group..
document
| Document Title: | Common Error codes that may be encountered during various operations. |
| Document ID: | 10018286 |
| Solution ID: | 1.0.33289222.2350537 |
| Creation Date: | 05Oct1999 |
| Modified Date: | 25May2001 |
| Novell Product Class: | Connectivity Products |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.