Novell is now a part of Micro Focus

ZENworks Installation Problems

Articles and Tips: tip

01 Sep 2001

Adapted from Technical Information Document #10057371

Let's say you are getting some strange errors when trying to start up ZENworks for Desktops. Some of these problems include getting Java errors on the server after ZFDStart is loaded, inventory data that is not getting to the database server, or inventory data that is being rolled up to the Root server by the wrong Rollup server and therefore the inventory policy wasn't appearing in the scheduler, and wasn't running.

Some of the questions you may be having might be:

  • How do I troubleshoot the ZENworks for Desktops 3 Inventory Process?

  • Is a NDS replica required on a ZENworks Inventory and/or Database Server?

  • How do I properly configure the ZENworks for Desktops 3 Inventory Process?

When troubleshooting ZENworks problems, it's a good idea to narrow the scope for a solution. For this troubleshooting exercise, let's assume that you are using the following:

  • Novell ZENworks for Desktops 3

  • ZENworks Inventory

  • Novell ConsoleOne v1.2d.1

Proper Installation

By design, the replica doesn't have to be on the Inventory Server. But since the Inventory modules depend on Novell Directory Services for configuration information, the Inventory NDS Policy information needs to be always available either from a primary replica or from a secondary replica in case the primary is down. Also in the case of the latter, the Policy information should have been synchronized between the Primary and the Secondary replicas. (Redundancy is always good!)

It would be good to verify that you have properly setup and installed ZENworks. Do the following to verify this:

Was JAVA unloaded from the server and re-installed from the Companion CD?

Java errors may occur if the correct version of Java was not loaded on the server, or Java was not unloaded during the initial install of ZENworks for Desktops. To correct this problem, re-install Java from the Companion CD. To do this, perform the following steps:

  • At the server prompt, type JAVA -exit

  • Run JVM.EXE from the companion CD.

  • Re-load JAVA on the server


Note: A newer version of the 1.1.7B JVM is available on the URL.

Was an Inventory Role selected for the server?

Was the server installed as an Inventory Database server?

Was the Site ID and Site name selected for the Database server? Note that Site IDs have to be between 0-255 ( you cannot use 0 or 255). Also, does the Site name have underscores in it? This is not supported.

Have you installed Sybase?

Was this installed on a NetWare v4.11 or on a NetWare 5.1 server? If the server is NetWare 4.11, was ORB.EXE installed on the server? If the server is NetWare 5.1, ensure that the following entries exist in the JAVA.CFG file in the SYS:\ETC directory:



These changes will be in effect only if you also perform the following steps:




  • Are you installing on a Clustering server?

You must install the Clustering Snap-in. This can be downloaded from Novell ZENworks CoolSolutions Home Page at the following URL:

Were the Clients upgraded to v3.3 and v4.8?

The older clients are not compatible with ZENworks for Desktops 3.

Note: ALL INVENTORY SERVICES MUST BE STOPPED on the server before you create or modify the Inventory policies or configure the objects. IF THEY ARE LOADED AT THIS POINT, KILL THE INVENTORY SERVICE ON THE SERVER.

To stop inventory services, perform the following steps:

To reload the Inventory services, go to the server console Prompt and type the following:

JAVA -show

This will show you all of the Java processes that are currently running.

The following processes will need to be stopped and restarted.


You can stop these processes by typing the following:

JAVA -kill(process ID#)

For example:

JAVA -kill190

After you have verified the Installation of ZENworks, load ConsoleOne and check the following:

  • Service Location Policy Package

  • Server Package/Roll-up Policy

  • ZfD3InventoryDatabase Object

  • ZenInvService Object

  • Workstation Package

Service Location Policy Package

Is there a Service Location Policy Package in the same container as the Inventory Database Server's NCP object? There must be a Service Location Package for every server identified as a database server.

Make sure the Service Location Package is associated to the containers where the servers which will be using this Inventory database exists.

In the Service Location Policy package, is the Zenworks Database option enabled?

Click on the properties for the ZENworks Database option to check that the ZENworks Database DN is pointing to the correct object.

Server Package/Roll-up Policy

Is the Inventory Server Associated to a Server Package? Does the Server Package Exist? If not, create one and associate the NCP server object or the container where the NCP server object exists.

In the Server Package, Is the "zeninvRollUpPolicy" enabled? If so, go into the properties for the zeninvRollUpPolicy. The Inventory Role on this server will determine what "Destination Service Object" will be used.

  • If the server is set up to be a Root Server or a StandAlone server, you will not need to specify a Destination Server Object, but the RollUp Policy will still need to be enabled.

  • If the server is the only server in the tree and was installed as a Root Server and a "Destination Server" already, Inventory may fail. If this happens, it may be necessary to delete the inventory objects from ConsoleOne, unload the inventory services from the server, and reinstall the database again.

  • Note: Do not define the "Destination Server" as it is not valid for a Root Server to have a "Destination Server" to roll up to.

  • If the server is set up as a Leaf Server or an Intermediate server, you will need to specific the next level Destination Server Object, where the Inventory data will be sent to.

  • If you are in a WAN environment, you may want to set up a Schedule when the server will "Roll Up" the inventory data to the Destination Server.

ZfD3InventoryDatabase OBJECT

Is there a ZfD3InventoryDatabase Object for the Inventory Database Server?

  • If there is not, create one.

  • If there is, go into the properties of this object. Make sure the correct server DN name is added on the first line.

ZenInvService OBJECT

Is there an ZenInvService Object? The name of this object should be


  • To view the Rollup diagram for this server, double-click on this object.

  • To view the properties for this object, right click, then click on Properties. In the Properties, you will see the Inventory Role for this server. Make sure it is configured properly.

  • This object also holds the Roll -Up Status reports. If the Inventory data is not being sent to the next level Inventory server, check the Roll-Up status logs to determine the following:
  • When the last Roll-up occurred.

  • The name of the Roll-up Zip file that was sent to the next level server should be the SiteID of the correct database server.

  • The size of the Roll-up file.

  • What server sent the file and what server received the file.

Workstation Package

Has a workstation Package been created?

  • If yes, has it been configured properly? See below for more details.

  • If No, create the workstation package.

Perform the following to Configure the Workstation Inventory Package:

  • Right click on the Workstation Package, click on Properties.

  • Under the Association Tab, make sure you have added the containers, workstations, or workstation groups that will need to use this Policy package.

  • Under the Policy tab, make sure the Workstation Inventory policy is enabled for each platform in your environment.

  • After it is enabled, go into to the properties of the Workstation Inventory policy. Make sure the <servername>_ZenInvService object is listed. Also make sure the "Enable software scan" box is checked. Otherwise, only minimal inventory information will be scanned and then sent to NDS.

  • Make sure the Policy schedule is set up to meet your needs.

  • Check the "Other" tab and verify that the WMSCHED class is present. If recreating the workstation object does not provide this class attribute, the ZFD 3 schema is not properly in place and a reinstall of the schema should be done and then verify all replicas and partitions are updated properly. Recreation of the policies that can manually be recreated would be recommended after the schema is properly populated in the NDS.

  • Note: Once all of the objects are created, and configured properly, load the Java Processes by typing STARTINV at the server prompt. Also, if you are modifying the Inventory policies or configuring the objects, always stop the Inventory Services. Configure the policies and properties of the objects. Restart the Inventory Services again.

To reload the Inventory services, go to the server console Prompt and type the following:

JAVA -show

This will show you all of the Java processes that are currently running. The following processes will need to be stopped and restarted.

  • com.novell.orb.service.naming.NamingServer

  • com.novell.application.zenworks.autowsmanagerment.wsinmport.Imp

  • com.novell.zenworks.desktop.inventory.servercommon.ZENworksInv

Stop the processes by typing the following:

JAVA -kill(process ID#)

As an example:

JAVA -kill190

Restart the Inventory processes by running the ZFDSTART.NCF file with the following command:


Once the processes are running again, go to the container where the <servername>ZenInvService object is located, go to Tools, Configure DB

Configuring the Database

On the server, check the following:

Are the following Java processes loaded? Type Java -show, you should see the following services loaded:

  • com.novell.zenworks.desktop.inventory.servercomman.ZENWorksInv

  • com.novell.application.zenworks.autowsmanagement.wsimport.Imp

  • com.novell.orb.service.naming.NamingServer

  • Are the following modules loaded on the server?


Does the MGMTDB.LOG file exist in the SYS\SYSTEM directory?

If this file does not exist or has been deleted, the Database will not load on this server.

Has the Inventory Database been installed on an NFS volume?

This is not supported. This is documented in the ZENworks for Desktops 3 Readme, section 7.5.

On the Workstations, check the following:

  • Were the workstations imported properly?

  • Is Workstation Manager Installed and running on the workstation?

From the desktop menu, right-click the Workstation Manager - Display NDS Information. The workstation object and the tree should be displayed. Alternatively, verify using the Registry Key:

HKEY-local machine\software\novell\\workstation manager\identification.

You should see the following settings under the Identification Key. If these settings do not exist, or have the wrong information, the workstation has not been properly imported.

  • Last registered Tree

  • Registered in

  • Registration Object

  • Tree

  • Workstation Object

Inventory Log Files and Scan Status Reports to help with troubleshooting.

ZENERRORS.LOG -This is a log of the workstation scanner errors. File is stored in Windows\Temp on Win95/98 machine, or Temp directory on the WindowsNT or Windows2000 machines.

HIST.INI - This is located on the local drive of the workstation.

CONSOLE.LOG - Load CONLOG as near to the top of your AUTOEXEC.NCF file as possible. Next, unloaded CONLOG after all of the NLMs are loaded on the server. This will allow you to conduct useful troubleshooting to detect any errors loading the Java Processes or the Database NLMs during the initial boot up of the server.

Under the SYS:PUBLIC\ZENWORKS\WMINV\LOGS directory, there are several useful trace files and log files that may help you to locate the problem.

To view the scan status for the workstation, go to the Workstation Object, Click on ZENworks Inventory Tab, Click on the arrow, go to Scan Status.

To View the Roll-Up Policy status and the Roll-up Server Status, go to the ZenInvService object, right click on the object, go to Properties, Status Report Tab.

To increase the verbosity of the log files, edit the SYS:PUBLIC\ZENWORKS\WMINV\PROPERTIES\ and the files In the file, add a semi-colon in front of the *default*=BRIEF line. Then add an additional line *default*=DEBUG5 below it. Save the file.

In the file, on the second line, you will see the word "INFORMATION" at the end of the line. Remove "INFORMATION" and add DEBUG5. Save the file. After the files have been saved, go into the SYS:PUBLIC\ZENWORKS\WMINV\LOGS\InvServerLog.txt folder and delete all of the old log files. There will be one that is still in use; this is ok. After you stop the Inventory processes on the server, then restart them, a new file will be created. It will have a lot more information in the file than before.

Hopefully after completing all of these troubleshooting steps, your ZENworks of Desktops and ZENworks Inventory will be up and working correctly.

Oops: Clarification on July's "Starting the Conlog NLM from the STARTUP.NCF File"

On the Tip and Trick piece entitled "Starting the Conlog NLM from the STARTUP.NCF File," one of our readers, Robert Horgan, wrote the following:

"When trying this the 5.1 sp3 server reported that conlog could not be loaded from the startup.ncf file. clib and conlog were copied to the c:\nwserver directory. Did I miss something, or can this actually work?"

In reply to this query, Kevin Burnett, our intrepid finder of unusual problems, discovered the following:

"What you are seeing with trying to load CONLOG.NLM in Startup.NCF is correct. It is not possible to load CONLOG in Startup.NCF due to dependancies of CLIB. CLIB requires a mounted SYS volume in order to load.

"There is a TID out on Novell support site at the following URL:

"This URL points you to TID #1002953. This Technical Information Document, although a little dated, confirms the above information.

"Then wanting to verify that this TID had not been outdated, I talked to one of our premier CLIB engineers. He verified for me that CLIB can not be loaded in Startup.NCF due to thr requirements of a SYS volume being available.

"Lastly, I verified the problem by trying to load CONLOG in my server's Startup.NCF file. My test system failed.

"Best Regards, "Kevin Burnett"

We apologize if this has caused you any problems.

* Originally published in Novell AppNotes


The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.

© Copyright Micro Focus or one of its affiliates