NEC Express5800/320Fd-MR, User Manual

Page: 368 / 484

5-170 Installing and Using Utilities
The following tables describes some common problems with custom actions.
Troubleshooting: Custom Actions
Error Action
The executable filename does not
exist.
Ensure that the executable file associated with your
custom action is located in the directory you specified
during the configuration process. Also, ensure that the
custom action is located on a system disk, otherwise the
Upgrade Side will lose access to the executable while the
system is in split mode.
Custom action failed with exit value n
Check the output for the custom action for errors. See
“Viewing Standard Output and Error Stream” on page
5-128 for more information.
You must correct the problem and click Retry in the Active
Upgrade Console to retry the current upgrade request
(which also runs the custom action again). The Active
Upgrade process will not continue until the executable for
your custom action runs successfully.
If possible, test and debug the executable outside of the
Active Upgrade process. Ensure that it terminates with exit
value 0 and that it completes in a timely manner.
Troubleshooting: Miscellaneous Problems
Problem Action
Active Upgrade Console
fails to start
Wait a minute, and try to start Active Upgrade Console again.
If the problem persists, it might mean that the Active Upgrade
Console cannot communicate with related services on your local
system. If your system is running a network firewall solution, check
the firewall logs for blocked communications and explicitly add
these items to your trusted zone. For information about configuring
Windows Firewall, see “Configuring Windows Firewall for the Active
Upgrade Process” on page 5-98.
Remote KVM browser
window appears, but does
not open connection Ensure that Java™ 2 Runtime Environment (JRE) is installed and
running. Also ensure that you have added the VTM console Web
address to your Trusted Sites list, and that you have allowed
blocked Web-based content. See
“ Connecting to the Upgrade Side
with Remote KVM ” on page 5-139 for more information.