Inspecting the import log

One indicator of a successful database import is the absence of import errors in the \DeltaV\DVData\ImportExportProgress.log file. This verifies that all configuration data imported into the new database. If errors exist, the restored database can be missing configuration data and therefore should not be used.

In general, warning messages are harmless and can be the result of schema changes in the database or from configuration-related issues that were already in the database before importing. Regardless, it is highly advised to review and understand all the warning messages in the log file prior to performing any kind of download after importing your FHX file.

Listed below are typical warning messages that can appear in the ImportExportProgress.log file after importing an FHX file.

HART Device Revision <Device DD revision> does not exist…

Examples:

WARNING: The HART Device Revision 'Rosemount Inc./3051ERS/1' does not exist. The HART Device Revision 'Conventional./Generic/1' has been used instead.

WARNING: The HART Device Revision 'Detector-Electronics./UD10/1' does not exist. The HART Device Revision 'Conventional./Generic/1' has been used instead.

Reason for the warning:

Device Descriptors for these HART devices were not imported prior to the main FHX file. Because of this, the devices were imported with a Generic type. To preserve the use of these custom devices, the database should be re-imported according to the guidelines stated in this article.

Warnings for Parse Errors

Examples:

1: WARNING: Expression "" on path "FB_TEST_COMP/T1" has 1 parse error(s).

2: WARNING: Parse errors are Row 0, Column 0: A blank expression was supplied.

1: WARNING: Expression "" on path "FB_TEST_COMP/T3" has 1 parse error(s).

2: WARNING: Parse errors are Row 0, Column 0: SYNTAX ERROR while reading ENDOFEXPRESSION

Reason for the warning:

The parse error indicates that the expression being used in a module is either blank, commented out, or invalid. This issue is pre-existing and not a result of the database import. Its main purpose is to provide information about the blocks/modules that contain the invalid expression, so that such can be corrected at a later time, if necessary.

Warning on Unassigned Fieldbus Function Block

Example:

1: WARNING: Function block 'LOOP_TEST/AI1' is not bound to a Fieldbus function block

Reason for the warning:

This warning could be due to either of the following: the function block in the module has not been assigned to any valid Fieldbus function block; or, the scan rate of the module is different from the module template where it was derived. The warning is a nuisance alert if the latter is true.

Warning for Unresolved References

Examples:

1: WARNING: There are unresolved references to 'LOOP2210_SQ/MONITOR/COMP_SQ_STT' or its components.

1: WARNING: There are unresolved references to 'PROCESS_101AT' or its components.

Reason for warning:

This warning indicates that one or more reference(s) from a module to another parameter does not resolve to a valid path. This is pre-existing in the database and is not a result of the database import. Its main purpose is to provide information about the blocks/modules that contain the invalid references, so that such can be corrected at a later time.

Unresolved references should not exist during normal operation due to their impact on performance. However, unresolved references do not prevent the successful export/import of the database.