List of error messages

MDB Object Name exceeded maximum allowed length

You tried to create an MDB object with a name longer than 259 characters.

For Properties, the allowed length is 259 characters minus the length of the replacement suffix.

For example, the default replacement suffix is _Prop, which has 5 characters. With this setting, the maximum length of a Property name is 254 characters.

Broken Connection (- 10734)

A client application is unable to establish or maintain a session with PI Server due to a network issue or configuration problem.

1. Verify that the necessary network ports (for example, port 5450) are open and properly configured for both inbound and outbound connections.

2. Check firewall settings to ensure PI Server communication is not blocked.

3. Confirm that the PI Server and client applications are configured correctly for communication.

4. If the issue persists, contact Technical Support using the Customer Portal.

Linking these modules is prohibited

In MDB, you cannot create links between objects that are under the %OSI hierarchy and objects that are not under the %OSI hierarchy.

You cannot perform this action.

New effective date is inconsistent with effective dates on existing versions or it is newer than Obsolete Date

Effective dates and obsolete dates have to be consistent with dates on other versions.

Choose a date that is consistent with other versions.

At least one PI identity on the PI Module has zero mapped Windows principals

This means that PI MDB has access permissions for a PI identity (or PI user or PI group) that does not have a PI mapping. Every PI identity, user, or group that has MDB access permissions must have at least one PI mapping. If you delete the last mapping, you create a security conflict between MDB and AF.

Create a new mapping for the relevant identity, user, or group. Alternatively, delete the MDB access permissions for that identity, user, or group.

At least one Windows principal on AF Element is not mapped to any PI identity

This means that you added AF access permissions for a Windows account that does not have a PI mapping. This creates a security conflict between MDB and AF.

On the error messages that are related to migration and synchronization server, add a mapping for the Windows account. Alternatively, in PI AF, remove access permissions for that account.

At least one Windows principal is mapped to a PI identity on the PI Module but does not exist on AF Element security

This means that the PI module specifies access for a PI identity (or user or group) that is mapped to two or more Windows accounts; and one of those principals is not on the AF element security. This can happen if:

An AF element is added to AF with only one of those principals on the security descriptor

or

One of those principals was removed after AF and MDB were in synchronized state.

To fix (in order of preference):

• Add the missing principal(s) to the AF element.

• Remove the remaining principal(s) from the AF element.

• Edit the access permissions on the module to remove access for the PI identity. This will remove the remaining principals from AF element.

  Note: PI AF Link does not automatically pick up changes in mappings. The change does not take effect until you edit the element in some way; this triggers PI AF Link to update the settings in MDB.

Permissions for one or more Windows principals on the AF Element do not match permissions on the PI Module

This means that the AF element uses AF security options that are not reflected on the Data Archive server.

Manually edit the access permissions to match or reset the MDB.

Using default Acl for PI Module.

This means that PI AF Link is now using the default Access Control List (ACL) to control access to the Module. Two possible reasons:

• None of the Windows accounts that have access to the object in AF have PI mappings.

• For at least one Windows account that has access to the object in AF, you have used deny access.

If the problem is deny access in AF, remove the deny access. If the problem is no mappings, create a mapping.

Failed to Connect to AFServer

For some reason, PI AF Link was unable to connect to the AF Server.

Check that the AF Server is up and that the Data Archive server can connect to it. Check Windows EventViewer. It has a separate entry for AF and all messages for AF are logged here.

Module not yet created in AF. Retry.

Added module but it’s not yet in AF. This could happen if you added many modules and PI AF Link is trying to create them all in AF. It might take a while to process all the changes in AF.

Retry the operation.

If the problem doesn’t resolve itself within five minutes, contact Technical Support using the Customer Portal.

Failed to edit MDB-AF mapping table

You were running the offline piaflink mapping table command and the operation failed for some reason.

Wait a minute and retry the command.

If the problem doesn’t resolve itself within five minutes, contact Technical Support using the Customer Portal.

Failed to read module ids from AF

You were running the offline piaflink mapping table command and the operation failed for some reason.

Retry the command. Wait a minute and retry the command.

If the problem doesn’t resolve itself within five minutes, contact Technical Support using the Customer Portal.

Error during remigration. Current PI Server Element is different from the previous run. Perform the re-migration steps again.

When you did the remigration, you neglected to delete the mapping table. This old mapping table has configuration information that is no longer current.

Delete the mapping file from the PI\Dat directory (the file is pimdbafmapping.dat) and then restart PI AF Link.

AF Link subsystem is not ready to allow module edits

PI AF Link does not allow an MDB edit at this time. This could happen for any number of reasons, such as PI AF Link not running, unable to connect to AF Server, and so on.

This state always occurs when you start PI Base Subsystem or PI AF Link. It will take about 15-30 seconds after the later of the two subsystems starts before module database can be edited even if there are no problems.

If PI AF Link or PI Base Subsystem just started, then wait a few seconds after both are up and running, then retry.

If that is not the problem, then in the PI SMT AF Link tool, check synchronization status to find out what the problem is.

Attempted to connect to an unknown AF Server

Specified an AF Server and for some reason not found in the list of AF Systems.

Use the PI System Explorer to add it to the list:

• Click Database.

• Click …

• Right-click on any system in the list.

• Add the new system.

  See PI System Explorer help for details.

AF and MDB are out of sync

You cannot edit MDB when AF and MDB are out of sync.

In the PI SMT AF Link tool, check synchronization status to find out what the problem is.

Handshake already in progress. Will retry.

AF Link connects to the AF Server every 5 seconds (handshake), but can only do this once at a time.

Wait a while if possible. PI AF Link will re-try, so the error might go away with time.

If that does not work, try to restart PI AF Link Subsystem (you can do this in Windows Services)

If the problem persists, contact Technical Support using the Customer Portal.

Checkout of AF Object failed.

You are trying to edit an object in MDB but PI AF Link is not able to check out the corresponding AF Object. Someone else might have it checked out, or the same user has another version checked out, or the AF Object type is not supported for checkout. Could also be a connection or access permissions problem. If you get this message, then PI AF Link cannot determine the exact problem.

Wait and then retry. If you still have a problem, look at the suggestions for the following three errors in this table.

AF Object checked out by another user

You are trying to edit an object in MDB but PI AF Link is not able to check out the corresponding AF Object; someone else might have it checked out.

Wait until the AF object is checked in and then retry.

Another version of AF Object already checked out

You are trying to edit an object in MDB but another version of the object is already checked out.

Wait until the AF object is checked in and then retry.

AF Object type is not supported for checkout

You are trying to edit an object in MDB but PI AF Link is not able to check out the corresponding AF Object because it is not supported for checkout in AF. PI AF Link only checks out AF Elements, no other object type.

You cannot perform this type of edit in the MDB.

Required configuration is missing or incorrect

The preparation wizard says that it is complete, but PI AF Link cannot find some required configuration information.

Try again in five minutes. If that doesn’t work, check the message log to find out what is missing.

Run the wizard again.

Note: If you can figure out what is missing, you might be able to manually fix it.

AF Database CheckIn Failed

PI AF Link could not check in to the AF Database.

Do nothing. PI AF Link will retry the check in. The error should go away in time.

Complete the PI MDB to AF Preparation Wizard to initiate migration

You ran the preparation wizard but it is not complete. Either you didn’t put in all the information, or you need to analyze the Data Archive server again.

Run the preparation wizard and make sure the wizard is complete. You should see a success message on the final screen.

PI Server was moved from one machine to another.

Data Archive was moved from one machine to another.

If you intentionally moved the Data Archive server, and you want to keep the same target AF Server, then be sure to disable PI AF Link on the original Data Archive server. You can do this by disabling the PI AF Link Subsystem Windows service.

If you intentionally moved the Data Archive server, but you want to change the target AF Server, then re-migrate.

MDB AF synchronization encountered an error.

This could be for any number of reasons.

Do nothing. PI AF Link will retry. The error should go away in time. If not, look in the PI message log and in the Details tab of the AF Link tool in PI SMT for more information.

MDB migration in progress. MDB cannot be edited

PI AF Link is migrating MDB to AF.

Wait until the migration is complete and try again.

Processing changes made in AF Database. Retry later.

A large number of changes were made in AF and PI AF Link is busy processing the changes for MDB.

You should retry the operation later.

Another thread is still reading AF Changes. Will retry.

An internal error.

Do nothing. PI AF Link will retry. The error should go away in time. If not, contact Technical Support using the Customer Portal.

AF Link is busy making other AF changes. Retry later.

PI AF link is busy making other changes in AF and cannot process this operation.

Retry the operation later.

MDB cannot be reset from AF. Run the migration wizard to re-migrate MDB to AF.

The system is in a state where a re-migration is not allowed.

Run the migration wizard to re-migrate MDB to AF.

Failed to add AF Element

PI AF Link tried to add an element in AF and the operation failed.

Retry the operation. If that doesn’t work, look in the message log for more information.

Failed to edit AF Object

You added or edited something in MDB but PI AF Link could not create or edit the corresponding object in AF. The health goes out of sync when this happens and the error code for it will be this error number.

This is not an error you can fix. Retry the operation later. If that doesn’t work, look in the message log for more information. The reason for this failure will contain information on exactly which element failed and maybe why it failed.

Does not have required privileges on AF Object

PI AF Link does not have the necessary privileges to edit the object in AF.

Restart PI AF Link. If that does not work, then make sure that the AF Link to PI Windows group on the AF Server has the necessary permissions and that the account under which PI AF Link is running is a member of that group.

Target AF Database or the PI Server Element was deleted or not found.

The Data Archive element or the database to which it belongs, was deleted; or the configuration file doesn’t match.

The best solution is to run the MDB to AF preparation wizard. If you do not want to do that, you can:

• Manually recreate the database or element, then restart PI AF Link.

• Restore the database or element from a backup, then restart PI AF Link.

Target AF Database was not found.

The database to which the Data Archive element belongs was deleted or PI AF Link can’t find it.

The best solution is to run the MDB to AF preparation wizard. If you do not want to do that, you can:

• Manually recreate the database or element, then restart PI AF Link.

• Restore the database or element from a backup, then restart PI AF Link.

AF Element was derived from a template. PI Properties and PI Aliases cannot be edited in MDB. Edit the attributes in AF.

You are trying to edit properties or aliases on a module, but the corresponding AF element is derived from a template.

You cannot perform this operation. If an AF element is derived from a template, then you cannot edit the properties or aliases on the corresponding module in MDB. Your only option is to remove the template from the element in AF.

MDB and AF Database are not restored from the same backup

MDB and AF Database are not restored from the same backup.

Restore MDB and the AF Database from same backup or reset MDB.

PI_MDBAFPREP_COPYANDLOADFAILED

This indicates that we were unable to successfully make a backup copy of the files that the validation uses (pimoduledb.dat, piacl.dat, piidentity.dat, etc) and/or we were unable to load these files (possibly indicating they are corrupt).

Contact Technical Support using the Customer Portal.

PI_MDBAFPREP_VALIDATIONFAILED

This indicates that the validation of the module database unexpectedly quit. At this point, we don’t know if the MDB is actually ready or not for migration.

Contact Technical Support using the Customer Portal.

InSync

MDB and AF are in sync.

No action needed.

SyncInProgress

PI AF Link Subsystem is currently synchronizing the PI Module Database and the AF Server.

No action needed.

OutOfSync

The PI Module Database and the AF Server are out of sync.

Reset MDB.

BaseToAF LinkCommFailure

PI Base Subsystem has a communication error with PI AF Link Subsystem.

Start the PI AF Link Subsystem Windows service, if it is not running. If PI AF Link is running, then this error should resolve itself over time, typically within minutes.

AFLinkToBaseCommFailure

PI AF Link Subsystem has a communication error with PI Base Subsystem.

Start the PI Base Subsystem Windows service, if it is not running. If the service is running, then this error should resolve itself over time, typically within minutes.

AFLinkToAFCommFailure

PI AF Link Subsystem has a communication error with the AF Server.

If the PI AF server is not running, start it. If the SQL Server is not running, start it. If both are running, check the log file for any other error, such as incorrect access permissions, wrong AF Server name, and so on.

CheckinFailure

There was a check-in failure when checking in changes to the AF Server. Most likely another user has the object checked out.

Do nothing. PI AF Link will retry the check in. The error should go away in time.

PI AF Link Subsystem is not running.

This means that PI Base Subsystem is running but that PI AF Link is not.

Start the PI AF Link Subsystem Windows service.

Health status is bad for the Base subsystem

The PI AF Link subsystem status and the PI Base Subsystem status do not match. PI Base Subsystem has bad health status.

On the details pane, find the health status for PI Base Subsystem. Take the appropriate action for that health status message.

Health status is bad for the PI AF Link subsystem

PI AF Link Subsystem status and PI Base Subsystem status do not match. PI AF Link Subsystem has bad health status.

On the details pane, find the health status for PI AF Link Subsystem. Take the appropriate action for that health status message.

PIServerMoved

Data Archive server was moved from one machine to another.

• If you intentionally moved the Data Archive server, and you want to keep the same target AF Server, then be sure to disable PI AF Link on the original Data Archive server. You can do this by disabling the PI AF Link Subsystem Windows service.

• If you intentionally moved the Data Archive server, but you want to change the target AF Server, then re-migrate.

TargetDatabaseDeleted

Target AF Database or Data Archive element was deleted or not found.

You have a few options:

• Re-migrate MDB to AF.

• If it is the Data Archive element that is missing, create the element in the database and then wait for the synchronization to pick up the changes.

• Manually recreate the database or element, then reset MDB to match.

• Restore the database or element from a backup, then reset MDB to match.

DBAFRestoreInconsistent

MDB and AF Database are not restored from the same backup.

Restore MDB and the AF Database from same backup or reset MDB.

FailedToReadMDBEvents

Failed to read MDB Events from update queue.

Do nothing. PI AF Link will retry and this error should go away with time.

Failed to Reset MDB from AF Database

Failed to Reset MDB from AF Database

Try to reset MDB again. If it continues to fail, contact Technical Support using the Customer Portal.

GenericBadState

An error exists that does not fall into any category in this table.

Wait five or ten minutes if possible. PI AF Link will retry, so the error might go away with time. Otherwise:

• First look for possible causes of the problem. Check the Details pane. Open the Message Logs tool and look for error messages from piaflink or pibasess.

• If that does not help you find the problem, try to restart PI AF Link Subsystem (you can do this in Windows Services)

• If the problem persists, contact Technical Support using the Customer Portal.

InsufficientPermissionsToAF

PI AF Link Subsystem does not have enough permissions on AF Database to continue.

Check that the PI AF Link Subsystem service has the following access permissions:

• Read access on AF Databases collection and AF Elements collection on the target database.

• Read-write access on the target AF Database, Data Archive Element and AF Categories collection on the target database.

This PI Server is running a version earlier than PI Server 2010. The MDB to AF migration wizard has not yet been run.

This means that you have not yet run the PI MDB to AF preparation wizard on this Data Archive server.

If you want to upgrade this Data Archive, you must first complete the preparation wizard. The wizard is included in PI SMT 2010 and later versions, which you can download from the Customer Portal.

This PI Server is running a version earlier than PI Server 2010. The MDB to AF migration wizard has not yet been completed.

This means that you have run the PI MDB to AF preparation wizard on this Data Archive server but that you have not completed it.

If you want to upgrade this Data Archive, you must first complete the preparation wizard.

This PI Server is running a version earlier than PI Server 2010. Migration preparation is complete, upgrade to PI Server 2010 to enable PI AF Link.

This means that you have successfully run the preparation wizard on this Data Archive server and it is ready for upgrade.

Upgrade when you are ready.