Operating System- Related DS Error Codes Error codes -1 through -255 are operating system “related errors (such as from the file system, IPX, the bindery NCP, and other operating system services) returned through DS. The operating system error codes are 1 byte in size and are mapped to -1 to -255 when returned as DS errors. For example, when an application makes a DS API call but didn't allocate a large enough buffer for the data to be returned by the server, it results in a -119 error (buffer too small). You normally do not come across these operating system “related DS error codes because the applications should trap them and take appropriate action; however, if the application fails to trap the error, you may encounter these error codes. NOTE In general, the error codes listed in this section are of more interest to programmers writing DS -aware applications than they are to network administrators. Table 5.1 lists the operating system “related errors that you are most likely to see and what they mean. You can find a complete list of all the operating system “related errors in Appendix A. Table 5.1. Common Operating System “Related DS Error Codes DECIMAL | HEXADECIMAL | CONSTANT | -131 | 0xFFFFFF7D | DSERR_HARD_IO_ERROR | -149 | 0xFFFFFF6B | DSERR_FILE_DETACHED | -150 | 0xFFFFFF6A | DSERR_NO_ALLOC_SPACE | -188 | 0xFFFFFF44 | DSERR_LOGIN_SIGNING_REQUIRED | -189 | 0xFFFFFF43 | DSERR_LOGIN_ENCRYPT_REQUIRED | -190 | 0xFFFFFF42 | DSERR_INVALID_DATA_STREAM | -191 | 0xFFFFFF41 | DSERR_INVALID_NAME_SPACE | -192 | 0xFFFFFF40 | DSERR_NO_ACCOUNTING_PRIVILEGES | -193 | 0xFFFFFF3F | DSERR_NO_ACCOUNT_BALANCE | -194 | 0xFFFFFF3E | DSERR_CREDIT_LIMIT_EXCEEDED | -195 | 0xFFFFFF3D | DSERR_TOO_MANY_HOLDS | -196 | 0xFFFFFF3C | DSERR_ACCOUNTING_DISABLED | -197 | 0xFFFFFF3B | DSERR_LOGIN_LOCKOUT | -198 | 0xFFFFFF3A | DSERR_NO_CONSOLE_RIGHTS | -239 | 0xFFFFFF11 | DSERR_ILLEGAL_NAME | You should pay special attention if you encounter error -149. It is an internal auditing error that should generally not happen in the first place unless there's internal system corruption. If you encounter it, you need to contact Novell to resolve this error. Error -150 is important because it suggests that the server doesn't have sufficient dynamic memory to process the current auditing request; this error could be due to RAM shortage or memory fragmentation on the server. If you encounter a -239 error, it means the server received a request made with an object or a property name containing illegal characters , such as a control character, a comma, a colon , a semicolon, a slash, a backslash, a question mark, an asterisk, or a tilde. This error may also be due to the fact that the DS module can't map the supplied object or attribute name to its Unicode representation and could be a result of missing or corrupted Unicode files in the SYS:LOGIN\NLS directory on a NetWare server ( \winnt\system32\nls on Windows or /usr/share/nwlocale on Unix/Linux). Some of these operating system “related error codes (such as -254 and -255) have multiple meanings. And because -001 to -255 are mostly server operating system error codes reported as DS errors, you need to be aware of the context under which the error code is returned in order to correctly interpret the cause of the error. NOTE Some of the error codes in the range of “001 through “255 may be caused by Secure Authentication Services (SAS), the Authentication Tool Box (ATB) library (on a NetWare server), or even the Novell SecureLogin product. Therefore, knowing the condition under which the error occurred will help you to correctly interpret the error code, thus helping you find the proper fix to the problem. NOTE Interestingly, error code “25 is used by a number of applications (including eMBox), but its use is not clearly documented. |