Troubleshooting the Installation of ZENworks for Servers
Novell Cool Solutions: Feature
Digg This -
Posted: 28 Jul 2003
Here are some handy tips from the good folks in Support that will help you troubleshoot any difficulties you may have when installing ZENworks for Servers.
Here are the important things to check before you start the Install.
1. Have all the 'Minimum requirements' been met as outlined in the documentation?
2. Is there a R/W replica for every partition that ZfS objects will be created in (during the install process) on the server? This is required for the Site Server (MMS) install, but not for other MMS components. For TED / POL, a replica may not be needed for the install but the Distributor reads DS for some of its processes, and Subscribers access DS when creating NAL Application Objects for NAL Application Distributions. A replica on the Distributor would benefit performance. A replica on Subscribers isn't necessary, but may also benefit performance if strategically placed, especially in WAN environments. If the initial ZfS (MMS) install was done before the appropriate NDS replica(s) was/were installed to the server, a re-install of ZfS (MMS) is most likely needed (see Note C below).
3. Is the user admin.root (or equivalent) to the tree? The user must have full control of and access to NDS. NDS forces the install of the new schema to the Master Root partition so the new schema can propagate to the rest of the tree and schema is synchronized across the tree. The propagation of the schema relies on a healthy NDS.
4. Has DSREPAIR, Advanced Repair, Repair local database, with all settings default, enable 'Rebuild operational schema' (no need to enable 'Rebuild operationa schema' on eDir servers; this will lock the local database and prevent logins, but will not disconnect users) been run till zero errors? [Not all versions of DSRepair.nlm should be used. Contact Novell DS Support if uncertain which ones to use.] This should be done before and after the NetWare Support Pack is installed and just before the ZfS 3 install (if there have been more than a few hours). Was it ran at the same time on on all servers in the ring till all reported zero errors? This should potentially be done in the Tree? TID 10062741 'Checking the OS and DS Health for Inconsistent ZENworks behavior' can and should be used before installing ZfS products. The TID's 'Cause' information may not always be relevant or has already been addressed, but the 'Fix' process must be done before the ZfS install to verify the health of the schema before the install. TID 10062741 has links to the OS Performance & Optimization and DS Health Check TIDs.
5. Was the SYS:JAVA directory ever re-named, and not re-named back, or restored with the original NW OS install of the 1.2 directories and files included? Do not re-name the SYS:JAVA directory to install a new JAVA version. The NW OS install installs items that are not installed with the JVMxxx.EXE install. Copy the \JAVA directory to a secure location and restore the original when needed.
6. Was the SYS:PUBLIC\MGMT\CONSOLEONE\1.2 directory ever renamed, and not re-named back, or restored with the original NW OS install of the 1.2 directories and files included? Do not re-name the SYS:PUBLIC\MGMT\CONSOLEONE\1.2 directory to install a new C1 version. The NW OS Install installs items that are not installed with the C1.EXE install. Copy the SYS:PUBLIC\MGMT\CONSOLEONE\1.2\*.* /s directory to a secure location and restore the original when needed. If problems occur with the SYS:PUBLIC\MGMT\CONSOLEONE\1.2\, delete it and restore the original directory structure and start fresh. The install path for C1 should always end with the \1.2 folder.
7. With an RCONSOLE or RCONJ session active during the install, activity or errors on the server can be monitored and captured to provide Novell Technical Support, if engaged.
8. During the install, choose 'NO' to starting services on the server. They can be started later.
9. After the install is complete but before restarting the server, which is recommended, remark out all the ZfS 3 Load commands that were installed. The 'search add' commands and BSTART.NCF need not be remarked out. Also confirm 'LOAD CONLOG.NLM MAXIMUM=100' (or greater if needed) is loading in the AUTOEXEC.NCF before INITSYS.NCF or the NIC drivers are loaded and bound. Do not unload CONLOG.NLM in the AUTOEXEC.NCF as it will miss the needed information. Specifically, be sure to remark out in the AUTOEXEC.NCF file the SLOADER.NCF to prevent it from loading when the server is re-started. Let MWSERVER.NCF and NETXPLOR.NCF run at least over night or for a weekend before running SLOADER.NCF. This allows the discovery modules to 'flesh out' the discovery database (NETXPLOR_0.DAT) file with the details of the discovered hardware before SLOADER.NCF starts moving the data to the SYBASE database that is viewed via ConsoleOne (see TID 10075469).
A. License (NLS) issues have been known to cause the install of ZfS to fail. Confirm all NLS issues have been addressed. A good TID to start with is TID 10013723.
B. Certificate Server issues have been known to cause the install of ZfS to fail. One symptom would be:
'An error occurred while attempting to create object: Distributor_Servername.context Return Code = 1610677670'.
The Distributor object was actually created, even though the error said it was not. The issue was the server had two cards and was connected to two networks. The CA grabbed the wrong IP address for the CertificateDNS object. PKIDIAG identified this problem. Deleting the SSL CertificateDNS object in ConsoleOne and running PKIDIAG again re-created the object with the proper IP address. The re-install was successful after that.
C. If the schema install is successful, but the schema verify fails, see TID 10058497 (NO_SCHEMA_CHECK switch).
Initial load of ZfS modules
1. All the steps in Before installing must be done first.
2. Login as the same user that did the install. This user is granted by the ZfS install ownership of all the RBS objects and must be used to assign-out or add/change roles and role ownership.
3. Were the ZfS snapins installed to the server's SYS:PUBLIC\MGMT\CONSOLEONE\1.2 directory structure? If not, they must be as the JAVA processes running on the server, and even C1 running on a local box, accesses files in the SYS:PUBLIC\MGMT\CONSOLEONE\1.2 directory structure. Once all the ZfS modules are loaded on the server, C1 must run correctly from SYS:PUBLIC\MGMT\CONSOLEONE\1.2 on a workstation. Once confirmed C1 works properly running in that manner, then C1 can be installed to a local w/s (to get all the local registry settings) and the ZfS snapins installed to the local w/s. ZENworks for Desktops provides the utility SYS:PUBLIC\ZENWORKS\C1UPDATE.EXE to move the C1 version and snapins from the server to the workstation. Once the SYS:PUBLIC\MGMT\CONSOLEONE\1.2\BIN\CONSOLEONE.EXE is working, make a backup of the directory.
4. Load the ZfS modules one at a time manually as listed in the AUTOEXEC.NCF (before loading modules, see TID 10075469). If done from a w/s and a RCONSOLE or RCONJ session is active, the first error (if any) generated on the server should be captured with a screen shot and should be investigated? If an error is returned when loading the modules manually, run 'java -show' on the server console, unload CONLOG.NLM shortly after. Confirm the data is in the SYS:ETC\CONSOLE.LOG file. Search support.novell.com, Knowledgebase for possible TIDs. If none, a copy of the CONSOLE.LOG file and screen shots can be provided to Novell Technical Support.
A. MGMTDBS.NCF must be loaded for both Management & Monitoring Services (MMS) and TED/POLICIES to have access to the Sybase database. If loading manually, run this MGMTDBS.NCF before starting either MMS or TED/POLICIES. If TED/POLICIES is installed first, MGMTDBS.NCF should be the first item to load in AUTOEXEC.NCF (for ZfS 3). If MMS is installed second, the MGMTDBS.NCF line can be moved to just before MWSERVER.NCF. If this is not loaded, the server will run out of memory as SLOADER.NCF is preparing Discovery data to be inserted into Sybase.
B. Is the server in the production tree or a test tree? Typically, the test tree works and the problems arise in the production tree. If all the above items are addressed, this issue should be minimized.
For more information see TID 10072684
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com