Troubleshooting installation of the PSP for NetWare

The following issues might be encountered with the NetWare PSPs. The issues are in bold and their resolutions follow.

• I used the /r flag to reboot the server, and one of the packages installed required a reboot, but the server did not reboot. What is happening?

  If any of the packages chosen for installation fails the installation, a reboot will not occur. This enables the administrator to examine a server to determine and resolve a software installation failure before activating any changes.

• When I examine the package contents, the version of the driver in the package is newer than what I have on my server. However, one of the support files is older than the version that is contained in the package. What happens during installation?

  The key file version within each package is checked before the file is installed on the server. If the key file is newer than the file on the server, then the version in the package will be installed. Otherwise, the version currently installed on the server is retained, and the package is not installed.

  If the /force flag is used, then no version checking is done. All files in the package will be installed, even if one of the files on the server is newer than the one in the package.

• When I install a driver and then run the installation utility a second time before rebooting the server, the version shown in the installation utility does not match the version loaded from the MODULES console command.

  After an installation has occurred, the installation utility will check against the installed version on the fixed disk. Even if the version loaded is different, the version compared against it for installations is the version on the physical media.

• When I perform a command line install and pass the /r parameter, the server does not reboot.

  This usually occurs because the version of the software to be installed is the same or older than the version installed on the server, or a failure occurred during the installation (a prerequisite was not met). Check the SYS:\ETC\CPQLOG.LOG file to determine the cause of the failure.

• During installation, I get the following error message:

  Unable to read xxx from an XML file.

  This condition is usually caused by a corrupted package, which can occur during download. If a package XML file cannot be parsed correctly, the installation of that package will terminate with an error. To resolve this issue, try downloading the package again at the HP software and drivers website.

• When I try to install the PSP, I get the following error message:

  The software in this package is not intended for this version of NetWare.

  The package you have chosen to install might not be intended for the version of NetWare that is currently installed on the server.

• When I start CPQDPLOY.NLM, I get a prompt asking me to enter a path to a supported Support Pack XML file.

  This prompt is caused by having CPQDPLOY.NLM in a directory without a valid Support Pack XML file. A valid Support Pack XML file is of the format BP000XXX.XML and must support the installed version of NetWare on the target system. CPQDPLOY.NLM might be in a directory with a Support Pack file, but if the Support Pack file does not provide support for the currently installed version of NetWare, you will be prompted to enter a path to a valid Support Pack XML file. Press the F1 key to view an example of a valid path.

  If you are prompted for a path to an XML file, the new path will be used as the default for locating components.

  IMPORTANT: All components that make up a PSP must be present in the same directory as the Support Pack File.