General Problems and Solutions
Table 5-2 describes some common problems with custom actions.
Table 5-2. Troubleshooting: Custom Actions
Error | Action |
|
|
The executable | Ensure that the executable file associated with your custom |
filename does not | action is located in the directory you specified during the |
exist. | configuration process. Also, ensure that the custom action is |
| located on a system disk, otherwise the Upgrade Side loses |
| access to the executable file while the system is in split |
| mode. |
Custom action | Check the output for the custom action for errors. See |
failed with exit | “Viewing Standard Output and Error Stream” on page |
value n | 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 cannot continue until the executable file for your |
| custom action runs successfully. |
| If possible, test and debug the executable file outside of the |
| Active Upgrade process. Ensure that it terminates with exit |
| value 0 and that it completes in a timely manner. |
Table 5-3 describes miscellaneous problems.
Table 5-3. Troubleshooting: Miscellaneous Problems
Error/Problem | Action |
|
|
Active Upgrade console | Wait a minute, and try to start Active Upgrade console again. |
fails to start | 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 |