User's Manual

4. Right-click and select

Elevate without prompt.

DUP Fails on 64–bit Red Hat Enterprise Linux Operating System

If DUP fails to run on a 64-bit Red Hat Enterprise Linux operating system, manually install the following RPMs:

• compat-libstdc++-33.i686

• libstdc++-4.4.4-13.el6.i686

• libxml2.i686

• libXp.i686

• libXtst.i686

NOTE

: The RPMs are available on the Red Hat Enterprise Linux 6 x64 media.

Dell_PV_Utils_NASDUP.exe Fails to Initialize During the Invcol Execution

If you use Microsoft Windows Server 2003 operating system, you require .Net Framework 2.0 to run

Dell_PV_Utils_NASDUP.exe. If you do not have .Net Framework 2.0, the following error message may be displayed: The

application failed to initialize properly (0xc0000135).

Click on OK to terminate the application.

Enabling Operating System Devices

SUU does not inventory or update devices that are disabled in the operating system, though these devices may be

displayed in the Comparison Report. To update the disabled devices, make the appropriate changes in the operating

system and restart SUU.

Linux Systems Require the libstdc++-libc6.2-2.so.5 and libstdc++- libc6.2-2.so.3 Library to

run SUU

On Linux systems, libstdc++-libc6.2-2.so.5and libstdc++-libc6.2-2.so.3 libraries are required to run SUU. These libraries

are present if you have installed SUSE Linux Enterprise Server or supported versions of Red Hat Enterprise Linux on the

system. If the system does not have these libraries and you are running a supported version of Red Hat Enterprise Linux

or SUSE Linux Enterprise Server , install the compat-libstdc++ RPM from RedHat.com or from the Red Hat CD (for Red

Hat customers), or the SUSE Linux Enterprise Server CD (for SUSE Linux customers).

Running Linux Updates

SUU uses the Dell Update Packages (DUP) to update various system components. During a Linux update, the DUP

creates the /var/lock/.spsetup file using the Linux lockfile utility. This file is created when one of the following conditions

occur:

• A kernel panic

• A reboot command during a DUP procedure, preventing a TERM signal from interrupting or stopping a running

process

If one of these conditions occur, a

/var/lock/.spsetup file is created rather than deleted, causing SUU to report a

successful update and prompt the user to reboot the system. When you run SUU again and run the Comparison Report,

the comparison procedure reports no change in device status. If this situation occurs and you are not running an

update, delete the /var/lock/.spsetup file before running another update.