Diagnostic flowcharts
88
Restoring to a backed-up version
If you recently upgraded the operating system or software and cannot resolve the problem, you can try
restoring a previously saved version of the system. Before restoring the backup, make a backup of the
current system. If restoring the previous system does not correct the problem, you can restore the current set
to be sure you do not lose additional functionality.
See the documentation provided with the backup software.
When to reconfigure or reload software
If all other options have not resolved the problem, consider reconfiguring the system. Before this step, do
the following:
1.
Weigh the projected downtime of a software reload against the time spent troubleshooting
intermittent problems. It might be advantageous to start over by removing and reinstalling the problem
software.
2.
Be sure the server has adequate resources (processor speed, hard drive space, and memory) for the
software.
3.
Be sure the server ROM is current and the configuration is correct.
4.
Be sure you have printed records of all troubleshooting information you have collected to this point.
5.
Be sure you have two good backups before you start. Test the backups by using a backup utility.
6.
Check the operating system and application software resources to be sure you have the latest
information.
7.
If the last-known functioning configuration does not work, try to recover the system with operating
system recovery software. For more information, see the operating system documentation.
Application software problems
Software locks up
1.
Check the application log and operating system log for entries indicating why the software failed.
2.
Check for incompatibility with other software on the server.
3.
Check the support website of the software vendor for known problems.
4.
Review log files for changes made to the server which might have caused the problem.
5.
Scan the server for viruses with an updated virus scan utility.
Utility run failures
1.
Check the run environment and execute it in the supported OS and platforms.
2.
Track the detailed test items with the
-by-step.
3.
“
readme
”
file.
Errors that occur after a software setting is changed
Check the system logs to determine what changes have been made, and then change settings to the
original configuration.
Summary of Contents for CL2100 G3 407S
Page 64: ...Configuration 64 ...
