3.4 Troubleshooting the Inventory Scanner or Inventory Agent on NetWare Servers

Is the Inventory Agent installed?

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Action: Check to see if the invnatve.nlm file was properly copied to sys:\java\bin. If invnatve.nlm is not copied, reinstall the Inventory Agent. For more information, see Policy-Enabled Server Management Installation in Installation in the Novell ZENworks 7 Server Management Installation Guide.

The Inventory Agent has not been properly installed

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Action: Check to see if the following files have been properly copied at the inventoried server:
  • sys:\java\bin\invnatve.nlm
  • sys:\system\invaid.nlm
  • sys:\system\mpkscan.nlm

If any of the files have not been copied, reinstall the Inventory Agent. For more information, see Policy-Enabled Server Management Installation in Installation in the Novell ZENworks 7 Server Management Installation Guide.

Action: Check to see if the Inventory Agent jar files are properly copied to the ZENworks_path\pds\smanager\plugins and ZENworks_path\inv\agent directories.

If any of the scanner's .ini files (invsetup.ini and hwinvsrc.ini) or the .map files (nwapi.map, smile.map, and suppl.map) files have been accidentally tampered with or deleted, reinstall the Inventory Agent. For more information, see Policy-Enabled Server Management Installation in Installation in the Novell ZENworks 7 Server Management Installation Guide.

The Inventory Agent is not being enforced by the policy engine

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Action: Check to see if the Inventory Agent plug-in (invagentnw.jar) was installed in the ZENworks_path\pds\smanager\plugins directory.
Action: At the ZENworks Server Management console prompt, enter policy plugins and ensure that invagentexecutenw.jar is loaded as a registered entry.
Action: Refresh the distribution if the Server Inventory policy has been configured, then re-execute policy plug-ins after ensuring that the new distribution has been received.

If the problem persists, reinstall the Inventory Agent. For more information, see Policy-Enabled Server Management Installation in Installation in the Novell ZENworks 7 Server Management Installation Guide.

How to stop or replace the current instance of the Inventory Agent

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Action: Do the following:

  1. Stop the ZENworks service by entering exit at the ZENworks console prompt. Wait till it is stopped completely

  2. Stop the current instance of Inventory Agent by executing sys:system\invagentstop.ncf.

    The invagentstop.ncf stops the Inventory Agent, resets internal references and also uploads mpkscan.nlm and invalid.nlm

    To replace any of the Inventory Agent files, enter java -exit or unload java at the console prompt after executing invagentstop.ncf.

  3. Start the ZENworks service by entering sys:\zenworks\zfs at the server console prompt.

The Inventory scan results are not available

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Action: Refer to the following log files for additional details:

  • The status information about the Inventory scan is logged into the invagent.log and invnatve.log files, located in the sys:\etc directory.

  • If the Inventory scan is being enforced by the policy engine, refer to the invagentpolicyenforcer.log file to know the status of the current installation.

Action: In the sys:\system\invsetup.ini file, set the value of the forceDebug parameter to True. Re-execute the inventory agent. For more information, see Immediately rescheduling the Inventory Agent using the policy engine.

Refer to the sys:\system\invscan\invagentstrtransfer.log file for more information about the .str transfer.

The initialization of the Inventory Agent failed

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Action: Check to see if the Inventory Agent was properly installed by referring to the sys:\etc\invagent.log file. If the log file reports a message that “The previous instance of the Inventory Agent is still active...”, this indicates that the previous instance of Inventory agent execution has not yet been completed and the new instance does not run.
Action: Do the following:

  1. Stop the ZfS service by entering exit at the ZENworks Server Management console prompt.

  2. Stop the current instance of the Inventory Agent by executing sys:\system\invagentstop.ncf.

  3. Start the ZfS service by entering sys:\zenworks\zfs at the server's main console prompt.

  4. Re-execute the Inventory Agent. For more information, see Immediately rescheduling the Inventory Agent using the policy engine.

Action: Do the following:

  1. Verify whether ZENworks Server Management and Inventory Server services are running on this server by executing the java -show command.

  2. Stop the various ZENworks services running on this server.

  3. At the server console prompt, enter java -killall or java -exit.

  4. Execute invagentstop.ncf to reset the Inventory Agent.

  5. Ensure that invnatve.nlm is not loaded. If loaded, execute java -unload invnatve or unload invnatve at the server console prompt.

    If the Inventory Agent has been successfully stopped and invnatve.nlm has been successfully unloaded, the Inventory Agent is ready for the next schedule. For more information, see Immediately rescheduling the Inventory Agent using the policy engine.

Action: Reinstall the Inventory Agent. For more information, see Policy-Enabled Server Management Installation in Installation in the Novell ZENworks 7 Server Management Installation Guide.
Action: If the problem persists, contact Novell Support.

The Inventory scanning procedure failed

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Action: Check to see if the Inventory Agent was properly installed.
Action: Ensure that sufficient system resources such as disk space and memory are available.
Action: Ensure that you have the Write rights to the sys:\etc and sys:\system directories.
Action: If the problem persists, refer to the sys:\etc\invagent.log and sys:\etc\invnatve.log files for additional information.
Action: In the sys:\system\invsetup.ini file, set the value of the forceDebug parameter to True. Re-execute the Inventory Agent. For more information, see Immediately rescheduling the Inventory Agent using the policy engine.

Refer to the sys:\system\invscan\invagentstrtransfer.log file for additional information. The invagentstrtransfer.log file provides information about the .str transfer.

Action: If the problem persists, contact Novell Support.

Troubleshooting the guid.zfs file

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Explanation: The sys:\system\guid.zfs file is created and used by the Inventory Agent to report the scan data.
Action: If there is a problem in writing to guid.zfs, ensure that there is sufficient disk space and you have the Write rights to the sys:\system directory.
Action: If there is a problem in reading guid.zfs, delete the existing guid.zfs and re-execute the Inventory Agent. For more information, see Immediately rescheduling the Inventory Agent using the policy engine.

Successful scans are not being transferred to the Inventory server

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Action: In the sys:\system\invsetup.ini file, set the value of the forceDebug parameter to True. Re-execute the inventory agent. For more information, see Immediately rescheduling the Inventory Agent using the policy engine.

Refer to the sys:\system\invscan\invagentstrtransfer.log file for additional information. The invagentstrtransfer.log file provides information about the .str transfer.

Action: Ensure that the Scan Collector service is running on the Inventory server.

If the Scan Collector service is not running, start the service. For more information, see Understanding the Inventory Service Manager in Server Inventory in the Novell ZENworks 7 Server Management Administration Guide. Then, re-execute the Inventory Agent. For more information, see Immediately rescheduling the Inventory Agent using the policy engine.

If the Scan Collector service is running and the problem persists, refer to Error Messages and Troubleshooting .Str and .Zip File Transfer.

Successful scans are not reaching the Inventory server

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Action: Ensure that Scan Collector service is running on the Inventory server. For more information, see Understanding the Inventory Service Manager in Server Inventory in the Novell ZENworks 7 Server Management Administration Guide.
Action: Ensure that the Scan Collector service is creating the .str files in the scandir directory on the Inventory server.
Action: Check the status log for any messages indicating failure in transfer of .str files. See Troubleshooting .Str and .Zip File Transfer to resolve .str file transfer problems.

Successful scans are not reaching the Inventory database

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Action: Ensure that the Scan Collector service is running on the Inventory server. For more information, see Understanding the Inventory Service Manager in Server Inventory in the Novell ZENworks 7 Server Management Administration Guide.
Action: Verify whether Selector and Storer are processing the .str files.

Immediately rescheduling the Inventory Agent using the policy engine

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Action: To reschedule the Inventory Agent immediately without waiting for an elapse of the scheduled time:

  • At the ZENworks Server Management console prompt, enter policy refresh or policy enforce all or policy enforce policy_number.

  • Ensure that the Inventory Agent is enforced immediately.

How do I test the Inventory scanner without using the policy engine?

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Explanation: You can execute or test the Inventory scanner without using the policy engine to verify whether the installed software can report hardware and software inventory of the inventoried server.
Action: Do the following:

  1. If ZENworks 7 Server Management is not running the Inventory Agent or if the Inventory Agent is not enforced, execute sys:\system\invagentstart.ncf.

    NOTE:Invagentstart.ncf should not be used if the Inventory Agent is scheduled to be enforced by the policy engine.

  2. Review sys:\etc\invagent.log to ensure that it reports the message “The Inventory Agent's scanning procedure successfully completed.” This message indicates that Inventory scanning is successful on the inventoried server.

Explicitly executing the Inventory scanner without using the policy engine

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Explanation: You can explicitly execute the Inventory scanner without using the policy engine to verify whether the installed software can report hardware and software inventory of the inventoried server.
Action: Do the following:

  1. If the ZENworks 7 Server Management is not running the Inventory Agent or if the Inventory Agent is not enforced, execute sys:\system\invagentstart.ncf.

  2. Verify whether sys:\etc\invagent.log reports the message “The Inventory Agent's scanning procedure successfully completed.” This message indicates that Inventory scanning is successful on the inventoried server.

The Inventory Agent failed after an abnormal shutdown or abend or when the server is restarted

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Action: Check if sys:\etc\invagent.log reports the message “The previous instance of the Inventory Agent is still active. The Inventory Agent will not be scheduled.”

If the message has been logged, do the following:

  1. Stop the ZENworks service by entering exit at the ZENworks console prompt. Wait till it is stopped completely.

  2. Stop the current instance of the Inventory Agent by executing sys: system\invagentstop.ncf

  3. Start the ZENworks service by entering sys:\zenworks\zfs at the server console prompt.

    The Inventory Agent resets the previous execution settings and prepares for new schedules.

The Inventory Agent failed after guid.zfs was accidentally deleted when the ZENworks Server Management service was running

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Explanation: If sys:\system\guid.zfs is accidentally deleted when the ZENworks Server Management service is running, the Inventory Agent fails.
Action: Do the following:

  1. Stop the ZENworks service by entering exit at the ZENworks Server Management console prompt.

  2. Stop the Inventory Agent by entering sys:\system\invagentstop.ncf at the server console prompt.

  3. Start the ZENworks service by entering sys:\zenworks\zfs at the server console prompt.

The next schedule that enforces the Inventory Agent is launched successfully and guid.zfs is automatically created.

IMPORTANT:Do not edit or delete guid.zfs.

Unsatisfied link error in referencing sys:\java\bin\invnatve.nlm

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Action: Do the following:

  1. Check the various ZENworks services running on the server by entering java -show at the server console prompt.

  2. Stop all the ZENworks services running on this server.

  3. At the server console prompt, enter java -killall or java -exit.

  4. Ensure that invnatve.nlm is not loaded.

    If invnatve.nlm is loaded, unload the NLM™ by entering java -unload invnatve or unload invnatve at the server console prompt.

  5. Reset the Inventory Agent by entering invagentstop.ncf at the server console prompt.

  6. Check the execution results to ensure that the execution is successful and the Inventory Agent is ready for the next schedule.

How do I turn off the scanning of Windows .exe version information?

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Action: Edit sys:\system\invsetup.ini to add the following entry: 
invSWScanMode=1

This setting turns off the scanning of Windows .exe version information only if the software scan has been enabled. The Windows .exe version information is not reported in the software inventory results.

If you encounter problems in the Inventory Agent after adding this entry in invsetup.ini, send the Inventory Agent log files to Novell Support. For more information about the Inventory log files, see Monitoring Server Inventory Using Status Logs in Server Inventory in the Novell ZENworks 7 Server Management Administration Guide.

The Inventory Agent will not work if you have installed the ZENworks 7 Inventory Agent on the inventoried server using the ZENworks 7 Server Management Program CD, and then reinstalled the ZENworks 7 Inventory Agent using the software package

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers
Possible Cause: The ZENworks 7 Server Management Program CD installation creates or updates the value of InvAgentPath to sys:\zenworks\inv instead of sys:\zenworks\inv\agent in the sys:\system\zenworks.properties file.
Action: Do the following:

  1. Stop the ZENworks service by entering exit at the ZENworks Server Management console prompt.

  2. Stop the Inventory Agent by entering sys:\system\invagentstop.ncf at the server console prompt.

  3. Move the following files from sys:\zenworks\inv to sys:\zenworks\inv\agent:

    • invxmlrpcservices.jar
    • zeninvserver.jar
    • desktopcommonutility.jar
    • zenutility.jar

  4. Edit sys:\zenworks\zfs.ncf to add the following lines after the line containing smplugin.jar:

    envset tedpath=$tedpath;sys:\zenworks\inv\agent\ZenInvServer.jar

    envset tedpath=$tedpath;sys:\zenworks\inv\agent\DesktopCommonUtility.jar

    envset tedpath=$tedpath;sys:\zenworks\inv\agent\ZenUtility.jar

    envset tedpath=$tedpath;sys:\zenworks\inv\agent\InvXmlRpcServices.jar

  5. Ensure that the value of InvAgentPath in sys:\system\zenworks.properties is volume_name:\zenworks\inv\agent.

  6. Start the ZENworks service by entering sys:\zenworks\zfs at the server console prompt.

Memory allocation errors on the server

Source: ZENworks Server Management; Server Inventory; Inventory Scanner or Inventory Agent on NetWare Servers.
Action: If you face any Server memory related issues in the NetWare server screen, see NetWare 6.5 Troubleshooting the NetWare Server > Memory Problems and Managing the NetWare Server > Using the Novell Java Virtual Machine (NJVM) on the Server for more details to resolve the same.