Troubleshooting

This topic describes situations you might encounter and provides tips for addressing them.

The installation wizard does not launch when .Net Framework v4.0 is not installed
Issue
.Net Framework 4.0 or a later version is not installed on this computer.
Possible solution
Before attempting to start the installation wizard, install .Net Framework 4.0. You can download it from Microsoft .NET Framework 4 (Standalone Installer) website.
The installation wizard will neither install nor launch due to limited disk space
Issue
An error message is displayed indicating that there is not enough disk space to install the components.
Possible solution
Clear space on your hard disk drive so that you have enough disk space to install the components.
The installation wizard will fail on Windows 2003 server if .Network Framework 4.0 or later is not installed
Issue
The installation wizard either cannot be started or fails if .Network Framework 4.0 or later is not installed on Windows 2003 server. It is a known limitation.
Possible solution
Install .Net Framework 4.0 or a later version on the target server before running the installation wizard.
Lenovo Hardware PRO Pack can be uninstalled while leaving Lenovo Hardware Management Pack
Issue

Lenovo Hardware PRO Pack functionality depends on Lenovo Hardware Management Pack being installed. If you uninstall the Lenovo Hardware PRO Pack using the Lenovo Integrator Installer installation wizard, it prompts you to uninstall Lenovo Hardware Management Pack as well.

If you uninstall Lenovo Hardware Management Pack from the Start menu or from the Control Panel, the Management Pack can be uninstalled while leaving the PRO Pack installed on the system. However, when you remove the Lenovo Hardware Management Pack from the SCOM console, you must uninstall the PRO Pack first. The PRO Pack cannot work without the Lenovo Hardware Management Pack being installed.

Possible solution

Uninstall the Lenovo Hardware PRO Pack before uninstalling the Lenovo Hardware Management Pack.

The Installation wizard installs components to a network mapped drive, but components cannot be started
Issue

Although components are installed to a network mapped drive, the components cannot be started normally. When the installation wizard installs components to a network mapped drive, only the component files are copied.

The information generated when a component is running is recorded on the local machine. So the component cannot be started from a remote server directly.