Troubleshooting Server Inventory
ZENworks for Servers 3 keeps a detailed log file that includes the status of the inventory agents. This log file enables you to troubleshoot Server Inventory issues very effectively. The ZENworks for Servers 3 inventory
Another Server Inventory log file you can use to troubleshoot inventory issues is the INVAGENTPOLICYENFORCER.LOG log file. This file maintains the status of the current invocation of the policy engine, enabling you to see the time, type, description, and severity of any errors that occur in the policy enforcer.
Troubleshooting NetWare Errors
When troubleshooting ZENworks for Servers 3, you should always be aware of any NetWare error messages that are occurring. ZENworks for Servers 3 is heavily tied into the NetWare operating system, eDirectory, and file system. Therefore, any error occurring in NetWare possibly affects ZENworks for Servers 3 as well.
NetWare Server File System Errors
When ZENworks for Servers 3 is having problems distributing on the server, you should always look for errors in the NetWare or NT file system. These errors often help you narrow down the problem to a specific cause and resolution.
Table 15.1 lists common file system errors.
Table 15.1. Common File System Errors
Troubleshooting eDirectory Errors
Another area you should always review when troubleshooting ZENworks for Servers 3is the eDirectory error messages. ZENworks for Servers 3 uses eDirectory not only for normal authentication and access, but also as a service for controlling ZENworks for Servers 3 objects.
eDirectory errors can be categorized as described in the following sections.
eDirectory Operating System Error Codes
Some eDirectory background processes require the functionality provided by the NetWare operating system. These processes, such as communication and transaction servers, can return operating system-specific error codes to eDirectory. These error codes are then passed on to the eDirectory background process that initiated a request.
Usually, operating system error codes that are generated by eDirectory have a negative numerical representation, whereas normal operating system error codes have a positive numerical representation. The numerical range for operating system error codes generated by NDS is -1 through -255; inversely, the numerical range for operating system error codes is 1 through 255.
eDirectory returns the positive numerical error code rather than the negative error code normally used by eDirectory to return to application to prevent any
eDirectory Client Error Codes
eDirectory client error codes are generated by the eDirectory client that is built into eDirectory. The eDirectory client error codes fall in the range of codes numbered -301 through -399.
eDirectory Agent Error Codes
eDirectory agent error codes represent errors that originated in the eDirectory agent software in the server and that are returned through eDirectory. These codes are numbered -601 through -799 (or FDA7 through F9FE).
Temporary errors are normal, because the eDirectory database is designed as a loosely consistent database. You should not be alarmed if eDirectory error conditions exist temporarily. Some errors might persist, however, until the error condition is resolved.
Other eDirectory Error Codes
Some eDirectory background processes require the functionality provided by other NLM programs, such as timesync.nlm or unicode.nlm. If any of these modules encounter an error, it can be passed on to the ds.nlm. Unicode.nlm and other errors in this category range from -400 through -599.
Tools for Troubleshooting eDirectory Errors
To effectively troubleshoot eDirectory errors that affect ZENworks for Servers 3, you should be familiar with the tools available to troubleshoot eDirectory problems. The following tools are provided to monitor and repair error conditions with eDirectory.
Table 15.2 lists common NDS errors.
Table 15.2. Common eDirectory Errors