Category list

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 agents report their current status, including any errors they encounter in the SYS:\ETC\INVAGENT.LOG log file, on NetWare Servers. The log file is located in the Windows temp directory on Windows NT/2000 inventory servers.

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

CODE	TEXT	DESCRIPTION
0x8901	`INSUFFICIENT SPACE`	The station does not have sufficient disk space. Make certain that the minimum free disk space requirements are set up for the application object being used.
0x8980	`FILE IN USE`	An attempt was made to open or create a file that is already open . Set the shareable attribute if you want multiple users to access the file at the same time.
0x8983	`DISK IO ERROR`	A hard drive I/O error occurred on a NetWare volume. Typically, a bad sector has been encountered and could not be migrated to the hot fix area. Replace the drive.
0x8999	`DIR FULL`	An attempt was made to write to a volume without available directory space. Make certain that you are not exceeding the maximum number of directory entries for the volume.
0x899C	`INSUFFICIENT RIGHTS INVALID` `PATH`	An attempt was made to access a path with invalid rights to the path or with an invalid path name . Make certain that the user has appropriate rights to the path and that the pathname is correct.
0x89A8	`ACCESS DENIED`	Access has been denied. Make certain that the user has appropriate rights to the file.
0x89BF	`NAME SPACE INVALID`	An invalid namespace was used. Make sure the correct namespaces are loaded on the volume being used.

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.

NOTE

eDirectory returns the positive numerical error code rather than the negative error code normally used by eDirectory to return to application to prevent any incompatibility . Therefore, any occurrence of an error code within the range of 1 through 255 or -1 through -255 should be treated as the same error.

eDirectory Client Error Codes

The next class of eDirectory error codes is the client error codes. Some eDirectory background processes require the functionality provided by other eDirectory servers. Use of these functions, such as bindery services, requires that an eDirectory server act as an eDirectory client to the server providing the functionality. Therefore, these functions often result in client-specific error codes being returned to the eDirectory background processes and operations.

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).

NOTE

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.

The DSREPAIR Utility . The DSREPAIR utility enables you to work from the server console to monitor and repair problems with the eDirectory database on a single-server basis. It does not correct problems on other servers from a single, centralized location. It must be run on each server on which you want to correct eDirectory database errors.
The DSTRACE Utility . The DSTRACE utility enables you to work from the server console to diagnose eDirectory errors. These errors might appear when you are manipulating eDirectory objects with the administration utilities. eDirectory errors also show up on the DSTRACE screen.

Table 15.2 lists common NDS errors.

Table 15.2. Common eDirectory Errors

CODE	TEXT	DESCRIPTION
-601 FDA7	`NO SUCH ENTRY`	The specified eDirectory object could not be found on the eDirectory server that is responding to a request.
-603 FDA5	`NO SUCH ATTRIBUTE`	The requested attribute could not be found. In NDS, if an attribute does not contain a value, the attribute does not exist for the specific object.
-625 FD8F	`TRANSPORT FAILURE`	The source server is unable to communicate with the target server. This error is almost always LAN- related .
-626 FD8E	`ALL REFERRALS FAILED`	The object could not be found; however, it is still possible that the object does exist. It is likely that the server could not communicate with another server that is holding a copy of the object.
-634 FD86	`NO REFERRALS`	The source server has no objects that match the request and has no referrals on which to search for the object. This is not a serious error, but just a response. This error usually resolves itself.