| PowerChute Network Shutdown Release Notes |
||
| These release notes provide important information about PowerChute Network Shutdown, including known software problems and their solutions (if any). For any additional troubleshooting and background help, see the PowerChute Network Shutdown Product Center. |
| Table of Contents |
| Note: After clicking on a link directly below, press the Back button on your Web browser to return to these contents. Alternatively, press the Ctrl + Home keys. |
| General Problems On All Operating Systems |
|
Problem/Issue: A PowerChute Network Shutdown (PCNS) Parallel-UPS Configuration is shutting down on only one critical event Solution: PCNS should not shut down for critical events when they occur on only one UPS in a Parallel Redundant Configuration. This is a known issue that occurs when the Configuration Wizard is run again after the initial configuration for a Parallel UPS. If you run the Configuration Wizard again after the initial configuration you should re-start the PCNS service. Problem/Issue:PowerChute Network Shutdown (PCNS) does not support Parallel Smart-UPS VT, prior to firmware v5.0. Solution: Contact APC to obtain the latest UPS firmware for Parallel Smart-UPS VT. Problem/Issue: After a power failure, your PCNS server shuts down repeatedly for no apparent reason. Solution: This only happens with a Multiple-UPS configuration and when using the Network Management Card (NMC) firmware v3.2.x through v3.5.5. Several things can trigger this problem after a power failure. For example, it could start happening after you manually turn off the power to one UPS in a configuration. Or it could start after a UPS has gone on battery and is turned off based on settings chosen on the Advanced Configuration page of the PCNS user interface. To avoid this problem, disable the option to turn off a UPS when it goes on battery on the Advanced Configuration page of the PCNS user interface. In addition, you should not turn off a UPS manually, that is, using the UPS power switch. To resolve this problem once it has started happening, you should reboot the NMC:
Problem/Issue:
Problem/Issue: Remote Authentication Dial In User Service (RADIUS) is not supported by PowerChute Network Shutdown. Solution: None.
Problem/Issue:
Problem/Issue: To make sure any PCNS command file has enough running time, the value in "The command file needs this much time to complete (seconds):" should not exceed the "Low Battery Duration" value set in the NMC user interface. Solution: When setting the PCNS command file running time, check it against the NMC value.
Problem/Issue:
Problem/Issue:
Problem/Issue:
Problem/Issue:
Problem/Issue:
Problem/Issue:
For a) no workaround. For b) you need to re-start the service or daemon.
Problem/Issue:
Problem/Issue:
Problem/Issue: |
| User Interface on Internet Explorer and Other Web Browsers |
|
Problem/Issue:
Problem/Issue:
Problem/Issue:
Problem/Issue: |
| Network Configuration | ||||||
|
Problem/Issue:
Problem/Issue: | ||||||
| Event Configuration and Logging | ||||||
|
Problem/Issue:
Problem/Issue:
Problem/Issue:
Problem/Issue:
Problem/Issue: | ||||||
| Windows | ||||||
|
Problem/Issue: Workaround "<path to Java install folder>\java.exe" -cp "C:\<PCNS folder name>\Jexpress\JexpressUninstaller.jar;JExpress\uninstaller com.denova.JExpress.Uninstaller.JExpressUninstaller" Quotes ( " ") are required because the paths contain spaces. Examples of the location of the java.exe file are C:\Program Files\Java\jre6\bin or C:\Program Files\APC\jre\bin. Note: After running the command above, some files might remain. These can be deleted manually. Problem/Issue:Command files do not run properly when called by PowerChute Network Shutdown. The command file stops before all of the statements have executed. Solution: The command file must use the @START command to run executable programs, and use the full path name of the program. Path names that include spaces must be enclosed in quotes. Arguments for the executable must be outside the quotes. For example, if you must run HyperTerminal and Backup in your command file, use the syntax:
Problem/Issue:
Problem/Issue:
Problem/Issue: Due to changes in the power management feature in Windows XP SP1 and
Windows 2003, some servers with an ACPI (Advanced Configuration and Power
Interface) BIOS will not turn on when utility power is restored after an
outage. The following is an example of what may occur:
Problem/Issue:
Problem/Issue:
Problem/Issue:
Problem/Issue:
Problem/Issue: | ||||||
| Mac OS X | ||||||
|
Problem/Issue:
Problem/Issue: | ||||||
| UNIX | ||||||
|
Problem/Issue:
Problem/Issue (AIX): | ||||||
| SUSE Linux Enterprise Server 10 | ||||||
|
Problem/Issue:
| ||||||
| Red Hat Enterprise Linux server | ||||||
|
Problem/Issue:
Problem/Issue: | ||||||
| VMware | ||||||
|
Problem/Issue: | ||||||
|
Entire contents copyright ©1999-2012 by Schneider Electric. All rights reserved. Reproduction in whole or in part without permission is prohibited. All trademarks, product names, and corporate names are the property of their respective owners and are used for informational purposes only. 990-2468E
|