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:

  1. Access the NMC user interface by using the NMC IP address as the URL.
  2. Click on the Administration tab.
  3. Click on the General button.
  4. Click the Reset/Reboot option on left.
  5. Select Reboot Management Interface on the Reset/Reboot Network Interface page and click Apply.

Problem/Issue:
When several actions are selected for the same event, and the actions all have the same delay time, some actions do not occur.
Solution:
Threading issues in Java occasionally cause the actions to interfere with each other. Use different delay times for each action.

Problem/Issue:
During the installation, you receive an error message that PowerChute Network Shutdown (PCNS) is unable to register with the Network Management Card (NMC).
Solution:
In some cases, the installation program registers PCNS with the NMC, but is unable to confirm that it is registered. Check the IP address list on the NMC by opening the NMC user interface and selecting the menu that relates to PCNS. If your computer IP address does not appear on the list of client IP addresses, add it.

Problem/Issue:
Remote Authentication Dial In User Service (RADIUS) is not supported by PowerChute Network Shutdown.
Solution:
None.

Problem/Issue:
PowerChute Network Shutdown does not recognize a temperature or humidity probe on the AP9631 Network Management Card.
Solution:
Switch the probe from the AP9631 Universal I/O port on the right (labelled 2) to the port on the left (labelled 1). PCNS will then recognize the probe.

Problem/Issue:
PCNS does not support an SMX or SMT UPS device that is part of a Synchronized Control Group (SCG). An SCG is set up using the Network Management Card (NMC) user interface.
Solution:
Disable the SCG option for these devices using the NMC UI.

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:
With Switched Outlet Groups, PCNS periodically checks the "Power Off Delay" value set in the NMC user interface. This value is increased if it's less than the total time PCNS needs to run any command file and shut down its operating system. When this happens, PCNS should generate a "Runtime: Exceeded" event but it does not.
Solution:
No workaround.

Problem/Issue:
The PCNS user interface is not available immediately after restarting a service or daemon. The delay is caused by PCNS carrying out background validations and checks.
Solution:
Wait a few minutes.

Problem/Issue:
PCNS does not allow you to log on again if you exit the Configuration Wizard by closing the Web browser rather than selecting the Finish or Cancel buttons.
Solution:
Use the Cancel or Finish buttons to exit the Wizard. If you accidentally close the browser, re-start the PCNS service or daemon.

Problem/Issue:
If you change an existing command file path for an event in the pcnsconfig.ini file (e.g. event_PowerFailed_commandFilePath) by typing an invalid path, PCNS will subsequently log an invalid value when it starts. However, it does not restore the previous valid path from the pcnsconfig.ini.bak file.
Solution:
Change the path, either in the INI file or by using the PCNS web user interface.

Problem/Issue:
If you upgrade from PCNS v2.2.x to v3.x, and have not entered the path to a valid shutdown command file on the Configure Shutdown page in v2.2.x, then PCNS logs the following in the event log:
ERROR: Event ShutdownStarting is enabled for command file execution, but an invalid value for shutdownCommandFile is specified.
WARNING: Disabling command file execution for event ShutdownStarting due to bad parameters. Please validate the configuration.
Solution:
Ignore this error and warning.

Problem/Issue:
After an initial configuration, if you subsequently change the IP address of any NMC using the Configuration Wizard:

  1. the establishment of communications with the card is not recorded in the event log, and
  2. when the IP address is for a different UPS model type, the PCNS list of events does not automatically update.
Solution:
For a) no workaround. For b) you need to re-start the service or daemon.

Problem/Issue:
If PCNS is re-installed without having initially completed the Configuration Wizard, a user name and password are required to access it.
Solution:
Log on using "apc" as the user name and password. It is recommended that you change the user name and password afterwards using the Configuration Wizard.

Problem/Issue:
When the PCNS service or daemon starts, it validates the Pcnsconfig.ini value named localHostAddress. (This is the PCNS IP address that is registered with the NMC).
If PCNS has not already acquired an IP address when this check occurs, PCNS will report an invalid value. It will also attempt to replace the existing value with another IP if possible.
Solution:
Run the Configuration Wizard to set the correct PCNS IP address.

Problem/Issue:
In a Parallel Redundant UPS configuration, PCNS might incorrectly report Lost communications while on Battery when communications are lost and only one UPS has been on battery. The event log does not record the On Battery event prior to this.
Solution:
No workaround.

 User Interface on Internet Explorer and Other Web Browsers

Problem/Issue:
Occasionally, after you enter the user name and password, the user interface does not respond.
Solution:
Select Stop and then Refresh.

Problem/Issue:
When launching the PowerChute Network Shutdown user interface using Internet Explorer 6 or 7 (or Firefox or Safari), you get a security or certification error.
Solution:
You can ignore the error and continue safely.

Problem/Issue:
When you are running PCNS, this message displays in the Information bar (just below the Address bar) of Internet Explorer: "An add-on for this web site failed to run. Check the security settings in Internet Options for potential conflicts".
Solution:
Add the PCNS URL to the trusted sites list in your Internet Explorer settings.

Problem/Issue:
On the 64-bit version of Internet Explorer 9, if you access PCNS online help it might not open at the correct place in the text.
Solution:
Use the links at the top of the help to find your text.

 
 Network Configuration

Problem/Issue:
After you remove PowerChute Network Shutdown, the Network Management Card (NMC) still has the server IP address.
Solution:
Check the IP address list on the NMC by opening the NMC user interface and selecting the menu that relates to PCNS. If your computer IP address appears on the list of configured client IP addresses, remove it.

Problem/Issue:
PowerChute Network Shutdown is already installed, and you want to monitor a different Network Management Card.
Solution:
For PCNS v3.0.x, use the configuration wizard in the user interface or use the INI file: pcnsconfig.ini (see the PowerChute Network Shutdown Product Center).

 
 Event Configuration and Logging

Problem/Issue:
PowerChute Network Shutdown does not use the configured delay time for the Battery Discharged shutdown event for some UPS models.
Solution:
No workaround.

Problem/Issue:
When you switch PCNS to connect to a different type of UPS device the list of configurable events is not updated in the UI: the old list of events still displays. (Different UPS devices can have different configurable events).
Solution:
Restart the PCNS service to display the correct list of events.

Problem/Issue:
On MGE Galaxy 300/ 7000 UPS devices ONLY: sometimes the Runtime: Exceeded event is incorrectly cleared in the event log.
Solution:
With the MGE Galaxy devices, on the NMC user interface ensure that the Maximum Required Delay is always equal to or greater than the Maximum Negotiated Delay.

Problem/Issue:
The event log should report that PCNS has started when the service or daemon has started. Instead it reports it after all other start-up events are logged, for example, the communication has been established event.
Solution:
No workaround.

Problem/Issue:
With a service or daemon start-up on a Parallel UPS system, PCNS does not log the overall establishment of communications with the Parallel system until ALL the NMCs are in communication.
In contrast with this, when PCNS is running and it loses communications with all the NMCs in a Parallel system, it logs the overall re-establishment when just one NMC in the system is in communication (this is how it should work).
Solution:
No workaround.

 
 Windows

Problem/Issue:
PowerChute Network Shutdown (PCNS) v3.x is failing to uninstall.
Solution:
If you have installed to a folder other than the default folder, the folder name has spaces AND your computer has 8.3 file naming disabled, then the uninstaller will not launch.
Enabling 8.3 file naming and rebooting your computer will not get the uninstallation to work.

Workaround
Go to the Windows command prompt with Start - Run, and type "cmd" and select OK.
In the command prompt window, type the following and then press Enter.

"<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:

@START "c:\Program Files\Windows NT\hypertrm.exe" arguments
@START c:\Winnt\system32\backup  arguments

Problem/Issue:
A PowerChute Network Shutdown client that acquires its IP address through DHCP will lose communications with the Network Management Card when the client renews its DHCP address lease and acquires a different IP address.
Solution:
Each system using PowerChute Network Shutdown must have a permanent IP address. Reserve IP addresses in DHCP by using the MAC address, so that they never change for specified machines.

Problem/Issue:
After installing PowerChute Network Shutdown, a directory called tmpjex01 (or a similar name) is in the Temp directory or at the root.
Solution:
Delete this directory.

Problem/Issue:
After a graceful shutdown by PowerChute Network Shutdown, the server fails to turn on when utility power is restored.

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:

  • A server is attached to a UPS and running PowerChute Network Shutdown. PowerChute Network Shutdown is configured to shut down the operating system when the UPS has been on battery for a specific time.
  • When the utility power fails, causing the on-battery event, PowerChute Network Shutdown commands the operating system to shut down gracefully.
  • Because ACPI power management is controlled by the operating system rather than by the BIOS, when the operating system completes its graceful shutdown, it commands the server to turn off.
  • The UPS remains on battery until its shutdown delay time has expired. When utility power is restored, the UPS provides power; the server does not turn on.
Solution:
At this time, there are no updates available for this issue. Check Windows Update for the latest updates and service packs for your operating system.

Problem/Issue:
You are unable to install the software, or the software is not working properly.
Solution:
Both of these problems can be caused by not having Administrator privileges for the network while installing the software. You need Administrator privileges to install the software properly.

Problem/Issue:
If you run the installer for 64-bit Windows on a 32-bit system, no error message is displayed and the installation does not proceed.
Solution:
Use the 32-bit installation program.

Problem/Issue:
On Windows 2003 (without SP1 installed), when a "Low Battery" event occurs or any event with "Shut Down System" enabled, the operating system should shut down but it does not.
Solution:
Install the SP1 update for Windows 2003.

Problem/Issue:
After uninstalling PCNS, some folders and a file remain on disk and the Uninstall option remains in the Windows start menu.
Solution:
You can delete a menu item in the Windows start menu by right-clicking on it and selecting Delete.
You can also delete the folders and file, which are under "C:\Program Files" in a typical installation:

  • "\APC\Jexpress"
  • "\APC\PowerChute\uninstall.exe"
  • "\APC\PowerChute\jre" (if the private JRE option was selected)

Problem/Issue:
The UDP and TCP exceptions for PCNS are only applied to the active profile in the Windows Firewall (and only one profile can be active at a time). If the active profile is changed you will need to manually add exceptions for TCP ports 3052 and 6547 and UDP port 3052.
Solution:
See http://technet.microsoft.com/en-us/library/cc722141%28WS.10%29.aspx and Firewall in the PCNS Installation help.

 
 Mac OS X

Problem/Issue:
The PowerChute Network Shutdown (PCNS) Web user interface sometimes opens without asking for a user name and password.
Solution:
Quit Safari every time you log off the PCNS user interface to prevent this security issue.

Problem/Issue:
When installing PCNS, the command window remains open after the installation.
Solution:
Close the command window manually.

 
 UNIX

Problem/Issue:
A PCNS silent upgrade will fail if Java 5 is specified for JAVA_DIR in the silent installation file (silentInstall.INI or silentInstall.sample).
Solution:
User the path for Java 6 in the JAVA_DIR line in the silent installation file or just comment out the whole JAVA_DIR line in order to use the bundled JRE.

Problem/Issue (AIX):
You cannot access PowerChute Network Shutdown using a Secure Socket Layer (SSL) connection.
Solution:
Enable the Use TLS 1.0 option in your browser. Like SSL, TLS 1.0 is an encryption protocol and is usually found under the Advanced set of options for both Internet Explorer and Firefox. Searching your browser help contents will enable you to find it. On Internet Explorer 6, for example, it is found under Tools - Internet Options - Advanced tab - Security section.

 
 SUSE Linux Enterprise Server 10

Problem/Issue:
With HTTPS enabled, you cannot access the PowerChute Network Shutdown (PCNS) user interface remotely using the HTTP port. This can occur when trying to access through a Web browser or when using the Connected Servers page on another PCNS interface.
 
Solution:
Edit the /etc/hosts file and put a comment mark before each 127.X.X.X loop back address EXCEPT the 127.0.0.1 address. Alternatively, you can move all the 127.X.X.X loop back addresses EXCEPT the 127.0.0.1 address to below the line that contains the actual system IP address.
 
For example, in a /etc/hosts file which has both 127.0.0.2 and 127.0.0.1, do one of the following:

  • Put a a # symbol at the start of the 127.0.0.2 line while leaving the 127.0.0.1 line.
  • Move the line containing 127.0.0.2 to below the actual system IP address line (containing an actual address such as 192.168.2.200).
 Red Hat Enterprise Linux server

Problem/Issue:
The PowerChute Network Shutdown Configuration Utility does not work on Red Hat Enterprise Linux 5 server (v5.0, v5.1, v5.2).
 
Solution:
Install the appropriate rpm package for your system, as shown in the table below. These packages are available on the Red Hat installation CD or DVD and on the Red Hat Network, https://rhn.redhat.com/.

Itanium systems libXp-1.0.0-8.1.el5.ia64.rpm
32-bit systems libXp-1.0.0-8.1.el5.i386.rpm
64-bit systems libXp-1.0.0-8.1.el5.x86_64.rpm

 

Problem/Issue:
PCNS does not install on Red Hat Enterprise Linux x64 when using the JRE bundled with the PCNS installation package (that is you select the Private JRE option).
Solution:
The PCNS Linux installer uses a bundled 32-bit JRE. For a 64-bit system, glibc.i686 needs to be installed. This package is included in the Red Hat installation media.

 VMware

Problem/Issue:
Your virtual machine does not shut down gracefully or the shutdown does not initiate.
 
Solution:
This is an issue that is recognized by the VMware® company. You need to configure your virtual machines to shut down. Please refer to the workaround published by VMware (KB Article 1008182) on their Web site.

 

 

 

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