Installation Error Codes and Troubleshooting

Machine may become unresponsive during driver upgrade from WinOF v4.70 or earlier.

Upgrade requires unloading the old driver first, and this is when the machine may become unresponsive.

There are two solutions for this issue:

• If possible, load an OS image with the new driver installed.

• Reboot the machine prior to the upgrade operation to reduce the probability of hitting the machine freeze issue.

The installation of WinOF fails with the following error message:

“This installation package is not supported by this processor type. Contact your product vendor".

An incorrect driver version might have been installed, e.g., you are trying to install a 64-bit driver on a 32-bit machine (or vice versa).

Use the correct driver package according to the CPU architecture.

The installation of WinOF fails and reads as follows: "The installation cannot be done while the RDSH service is enabled, please disable it. You may re-enable it after the installation is complete."

A known issue in windows installer when using the chain MSI feature, as described in the following link: https://rcmtech.wordpress.com/2013/08/27/server-2012-remote-desktop-session-host-installation-hangs-at-windows-installer-coordinator/

Follow the recommendation in the article.

After driver upgrade, The ND state might be invalid, and the following event might appear in the event viewer: "Ndfltr: ND is in invalid state as a result of a mismatch between the ndfltr.sys driver version and mlx4_bus.sys driver version."

Upgrading the driver while the ND applications are active will hold the current ndfltr driver loaded, and prevent the loading of the updated driver.

Close all applications that use the ND, and restart the bus driver.

1603

Fatal error during installation

Contact support

1633

The installation package is not supported on this platform.

Make sure you are installing the right package for your platform

1004

Failed to open the device

Contact support

1005

Could not find an image for at least one device.

The firmware for your device was not found. Please try to manually burn the firmware.

1006

Found one device that has multiple images.

Burn the firmware manually and select the image you want to burn.

1007

Found one device for which force update is required.

Burn the firmware manually with the force flag.

1008

Found one device that has mixed versions.

The firmware version or the expansion rom version does not match.

3

Failed to restore the configuration

Please see log for more details and contact the support team