PI AF uses a Windows account that has no mapping

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

Consequences: The corresponding module can be viewed and accessed in PI MDB only by accounts that have the necessary mappings.

Fix: On the Data Archive server, add a mapping for the Windows account. Alternatively, in PI AF, remove access permissions for that account.

Note: 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 AF Link to update the settings in PI MDB.