Learn About Configuration File Errors

The configuration file could have any of these three types of errors.

Types of Configuration Errors

Dialog Description
Configuration File Startup Error Either (emwdata.bin and emwback.bin) is detected to have a read permission problem or a write permission problem when you start a management session. Follow the instructions in the dialog to recover from the error.


Important:

When you click OK, the Enterprise Management Window closes. You must correct this error before you can successfully open a management session.

Configuration File Write Error Either configuration file (emwdata.bin and emwback.bin) is detected to have a read permission problem or a write permission problem during a management session, or the write fails because the local disk is full. Follow the instructions in the dialog to recover from the error.


Important:

If you click Cancel rather than correcting the problem, and then you click Retry, any configuration data generated during your management session will be temporarily reflected but will not be saved for future management sessions.

Configuration File Corruption Error Both configuration files (emwdata.bin and emwback.bin) are corrupted and cannot be recovered, or one of the configuration files is corrupted and the other one is missing.

Record the location of the directory path listed on the error dialog. You might need this directory path in the recovery procedure.


Important:

When a configuration file corruption error occurs, the only action you can take initially is to click OK because the current configuration files cannot be recovered. Clicking OK replaces the configuration files and resets them to empty files. As a result, the Enterprise Management Window shows no devices. After clicking OK, you are given an opportunity to perform an automatic discovery to add devices and to rebuild your files. You can do so either by using alternate configuration files or by rebuilding your original configuration files.

Related Links: