Analysis error report
- Last UpdatedOct 04, 2024
- 5 minute read
- PI System
- PI Server 2023
- PI Server
|
Category |
Severity |
Description |
Possible action |
Sample message |
|---|---|---|---|---|
|
PIArchss Subsystem Shutdown |
Error |
PI Archive Subsystem is shutting down, analysis is aborted. |
Start the PI Archive Subsystem. |
|
|
Invalid HA Batch Database Access |
Error |
Unable to access batch records on a secondary Data Archive server. Analysis is not initiated. |
Analysis is not allowed on a secondary Data Archive server. |
|
|
Batch Database Not Supported |
Error |
The batch database is not supported in future archive sets, so no analysis can be done. |
Analysis is only allowed for historical archive sets. |
|
|
Point Error |
Error |
Failed to get the point IDs for batch (PIBatch, PICampaign, PIUnitBatch), analysis stops. |
If the analysis fails to get point IDs for batch points, there is a serious issue in Data Archive. Check if the Data Archive server is functioning properly. |
|
|
Invalid BDB Type |
Warning |
PI Batch Database (BDB). If a PI point obtained for analysis is not for a PIBatch, PICampaign, or PIUnitBatch, analysis skips it and continues with the next point. |
None. |
|
|
Unable to Get Event |
Warning |
An error occurred while getting an event for a batch database point. If this event is the first event of this point, analysis skips all events for this point and continues with the next point. Otherwise, analysis skips this event and continues with the next event. |
None. |
|
|
Invalid UID |
Warning |
Failed to read UID for a batch database record. |
None. |
|
|
Invalid BatchID |
Warning |
Failed to get Batch ID for a batch database record. |
None. |
|
|
Invalid Procedure |
Warning |
Failed to obtain a procedure name for a PIUnitBatch. |
None. |
|
|
Invalid PISubBatch Name |
Warning |
Failed to get a PISubBatch name. |
None. |
|
|
Invalid PIProperties |
Warning |
Failed to get PIProperties for PIBatch or PICampaign. |
None. |
|
|
UID Mismatch |
Warning |
The UID stored in the event does not match the UID stored in the annotation. |
None. |
|
|
Invalid Child Reference |
Warning |
The child reference of a Batch Database record cannot be found or verified. The message logged in the analysis report shows details about the failure. If a child reference is not accessible due to an archive gap, it is logged under the "Archive Off-line" category. The child's stored parent UID might not match the actual parent UID, or the system may have failed to get the child's:
|
None. |
|
|
Invalid Parent Reference |
Warning |
The parent reference of a batch database record cannot be found or verified. The analysis report message shows details of the failure. If a parent reference is not accessible due to an archive gap, it is logged under the "Archive Off-line" category. The parent might not contain the reference to the child, or the system may have failed to get the parent's:
|
None. |
|
|
PIUnit Deleted |
Warning |
Some PIUnits were deleted, but their related PIUnitBatches and child PISubBatches still exist and can be found through a child reference from PIBatch. These PIUnitBatches and PISubBatches are not migrated. |
None. |
|
|
IsPIUnit False |
Warning |
In some PIUnits, the IsPIUnit flag is set to , but their related PIUnitBatches and child PISubBatches still exist and can be found through a child reference from the PIBatch. These PIUnitBatches and PISubBatches are not migrated unless their IsPIUnit flag is set back to . |
To migrate these PIUnitBatches and child PISubBatches, set the IsPIUnit flag to for these PIUnits. |
|
|
Archive Off-Line |
Warning |
Failed to get a child or parent object due to the target archive being offline. |
Bring the archive back online. |
|
|
Null Name |
Info |
For a PIBatch or a PICampaign, the BatchID is used as the element name in the event frame. If the BatchID is null:
|
Migration automatically names a null name with the string: in the event frame. Or you can set a BatchID or procedure name in the batch database before migration. |
|
|
Length Exceeds Limit |
Info |
The maximum length for a name in PI AF is 259 characters. |
Migration automatically truncates the name. Or you can shorten the name in the batch database before migration. |
|
|
Disallowed Characters |
Info |
The following characters are allowed in MDB but not in AF: |
Disallowed characters are automatically replaced with the migration replacement characters that were set for the module database to AF migration. Alternatively, replace them in the batch database before migration. |
|
|
Control Characters |
Info |
Control characters are not allowed in the name. |
Control characters are automatically replaced with a . Alternatively, remove or replace them in the batch database before migration. |
|
Note: When the Possible action is None, you do not need to do anything before migration because the batch data is not migrated. This generally occurs when those unit batches or batches are either deleted or missing.
You can try to recover the batch data by reloading the data through the interface. Not all interfaces can recover partial batches or unit batches. Even after recovery, these same warnings are reported. Before proceeding, migrate into a test system and evaluate the specific migrated unit batch data.
We do not recommend manually altering PI Event Frames after migration, other than deleting verified duplicates (as can be encountered, for example, when moving from PIBaGen to EFGen).