Environment
Novell
ZENworks for Desktops 3.2
Novell ZENworks for Desktops 3.0
Novell ZENworks for Desktops 3.0
Novell
ZENworks for Desktops 4.0.1 - ZfD4.0.1
Novell
ZENworks 6.5 Desktop Management Support Pack 2 - ZDM6.5
SP2
Novell
ZENworks 7 Desktop Management Support Pack 1 - ZDM7
SP1
Novell ZENworks
Workstation InventorySituation
Inventory Service
Manager is exiting with a status of -1
Error: "java: Class com.novell.zenworks.desktop.inventory.servercommon.ZENWorksInventoryServiceManager exited with a status -1"
The Inventory Service Manager can be stopped by running the command"stopser *" at the NetWare console.
The Inventory Service Manager is started by the ZENINVSTART.NCF file that is called by the ZFDSTART.NCF program.
Error: "java: Class com.novell.zenworks.desktop.inventory.servercommon.ZENWorksInventoryServiceManager exited with a status -1"
The Inventory Service Manager can be stopped by running the command"stopser *" at the NetWare console.
The Inventory Service Manager is started by the ZENINVSTART.NCF file that is called by the ZFDSTART.NCF program.
Resolution
Things to
check:
1. In ConsoleOne, check the ZENworks Inventory Service Object.
It will be in the same container as the server object, and will be named "ServerName_ZenInvService". Go to the second tab on the properties of that object, and look at the Server Status under Status Report. The most current information is presented at the top. Double clicking on an error message will provide more details as to what is causing the service to fail. If errors exist that have an error message that starts with a number from 602 to 626. Then, the full detail of the error can be found at the ZENworks for Desktops section of theNovell Documentation Website, under Error Messages -> Workstation Inventory.
2. Check the JVM running on NetWare.
ZENworks for Desktops 3.x on NetWare was designed and tested on JVM 1.1.7b. There are many releases of this JVM (1.1.7b) and they can only be differentiated by the date of the JVM (can check by doing"MODULES JAVA" on server console). NetWare 4.x and 5.0 can only use JVM 1.1.7b, NetWare 5.1 can also use JVM 1.2.2_006 and 1.3.3, NetWare 6 comes with JVM 1.3.x only. If you need to use ZfD 3.x on NetWare with a JVM that is different from 1.1.7b, make sure you follow the instructions inGetting Workstation Inventory to work with JVM 1.2.2_006 or JVM 1.3.xin order to get the Inventory Service Manager to work correctly. The latest publicly available JVM can be found on theNovell Product Download Webpage.
3. Check to make sure that the objects in the Directory have been properly configured in ConsoleOne.
The errors returned in the first step above will usually specifically describe problems with configuration. Common configuration problems are:
- If the inventory server was installed with a local database, make sure that the Database Location Policy in the Service Location Package has been configured and associated to the server object correctly.
- Check the properties on the "ZfD3InventoryDatabase" object to ensure that the Server's DN/IP has been configured and that the object is using the correct connection strings on the JDBC tab (Sybase v. Oracle).
- If the server is an intermediate or leaf server, make sure that a zeninvRollUpPolicy in the Server Package has been defined and configured. Sometimes you need to change the default Rollup Schedule for this package to work correctly.
- Check the ServerName_ZenInvService object to confirm that the Scan Directory Path on the Inventory Service Object Properties tab is pointing to a valid directory.
- Check the ServerName_ZenInvService object to confirm that the Discard Scan Data Time hasn't been set to sometime in the future (and that the server time is correct that the java process is running on).
- Make sure that the database is up and available for the Inventory Service Manager to connect to.
- Make sure that another instance of the Inventory Service Manager isn't already running. Check the java processes by doing "java -show" or look for a screen on the server console.
- Make sure that the Naming Server is running. Check the java process by doing "java -show".
4. Make sure that you are on the latest public patches for ZENworks for Desktops 3.x. There have been some changes to the .JAR files that the Inventory Service Manager uses.
5. Make sure that the ServerName_ZenInvService object hasn't been corrupted in the Directory. Doing a full DS Health Check can fix some problems. In some rare cases, this object needs to be recreated. It can't be created through ConsoleOne. You need to delete the existing object, and then do the ZENworks for Desktops 3.x product install again, doing a custom install choosing only inventory and telling it to only install the DS objects (don't need to do files).
6. Using the integrated install from theZENworks Cool Solutions Webpageto overlay SP1a onto the ZfD 3.0 CD has been known to cause problems with the Inventory Service Manager on Windows Servers with eDirectory. If you install ZfD 3.0 off of the original CD, and then install SP1a in the regular manner, these problems will not manifest themselves.
1. In ConsoleOne, check the ZENworks Inventory Service Object.
It will be in the same container as the server object, and will be named "ServerName_ZenInvService". Go to the second tab on the properties of that object, and look at the Server Status under Status Report. The most current information is presented at the top. Double clicking on an error message will provide more details as to what is causing the service to fail. If errors exist that have an error message that starts with a number from 602 to 626. Then, the full detail of the error can be found at the ZENworks for Desktops section of theNovell Documentation Website, under Error Messages -> Workstation Inventory.
2. Check the JVM running on NetWare.
ZENworks for Desktops 3.x on NetWare was designed and tested on JVM 1.1.7b. There are many releases of this JVM (1.1.7b) and they can only be differentiated by the date of the JVM (can check by doing"MODULES JAVA" on server console). NetWare 4.x and 5.0 can only use JVM 1.1.7b, NetWare 5.1 can also use JVM 1.2.2_006 and 1.3.3, NetWare 6 comes with JVM 1.3.x only. If you need to use ZfD 3.x on NetWare with a JVM that is different from 1.1.7b, make sure you follow the instructions inGetting Workstation Inventory to work with JVM 1.2.2_006 or JVM 1.3.xin order to get the Inventory Service Manager to work correctly. The latest publicly available JVM can be found on theNovell Product Download Webpage.
3. Check to make sure that the objects in the Directory have been properly configured in ConsoleOne.
The errors returned in the first step above will usually specifically describe problems with configuration. Common configuration problems are:
- If the inventory server was installed with a local database, make sure that the Database Location Policy in the Service Location Package has been configured and associated to the server object correctly.
- Check the properties on the "ZfD3InventoryDatabase" object to ensure that the Server's DN/IP has been configured and that the object is using the correct connection strings on the JDBC tab (Sybase v. Oracle).
- If the server is an intermediate or leaf server, make sure that a zeninvRollUpPolicy in the Server Package has been defined and configured. Sometimes you need to change the default Rollup Schedule for this package to work correctly.
- Check the ServerName_ZenInvService object to confirm that the Scan Directory Path on the Inventory Service Object Properties tab is pointing to a valid directory.
- Check the ServerName_ZenInvService object to confirm that the Discard Scan Data Time hasn't been set to sometime in the future (and that the server time is correct that the java process is running on).
- Make sure that the database is up and available for the Inventory Service Manager to connect to.
- Make sure that another instance of the Inventory Service Manager isn't already running. Check the java processes by doing "java -show" or look for a screen on the server console.
- Make sure that the Naming Server is running. Check the java process by doing "java -show".
4. Make sure that you are on the latest public patches for ZENworks for Desktops 3.x. There have been some changes to the .JAR files that the Inventory Service Manager uses.
5. Make sure that the ServerName_ZenInvService object hasn't been corrupted in the Directory. Doing a full DS Health Check can fix some problems. In some rare cases, this object needs to be recreated. It can't be created through ConsoleOne. You need to delete the existing object, and then do the ZENworks for Desktops 3.x product install again, doing a custom install choosing only inventory and telling it to only install the DS objects (don't need to do files).
6. Using the integrated install from theZENworks Cool Solutions Webpageto overlay SP1a onto the ZfD 3.0 CD has been known to cause problems with the Inventory Service Manager on Windows Servers with eDirectory. If you install ZfD 3.0 off of the original CD, and then install SP1a in the regular manner, these problems will not manifest themselves.
7. Use the
easy to use Site Names utility referenced in TID2957773to determine if the
Site Name and number was ever written to the database. If the
utility returns the message: " No Inventory Sites Present in the
specified list of IP addresses! " then try reinstalling the
inventory service again, only do it in two parts:
1- Install only Sybase.
2- Install the Inventory Service and don't check the box to install
Sybase.
Additional Information
The Inventory
Service Manager exits when it cannot get proper information from DS
or has some trouble starting up and contacting the appropriate
database (if one is being used).
The inventory service has found an incomplete configuration on the server or in NDS, which can be captured in a verbose log created by changing the files TracerMedia.properties, and TracerFilter.properties to DEBUG5 mode. Refer to KB 3543750 for information where these files are located and where the log is written.
One of the causes is that it failed to get Site name and information because the site information was never written to the database.
Formerly known as TID# 10070417
The inventory service has found an incomplete configuration on the server or in NDS, which can be captured in a verbose log created by changing the files TracerMedia.properties, and TracerFilter.properties to DEBUG5 mode. Refer to KB 3543750 for information where these files are located and where the log is written.
One of the causes is that it failed to get Site name and information because the site information was never written to the database.
Formerly known as TID# 10070417