Monitoring and Alerting Server (MAS) would not run a workspace which connected to a OSI PI database, using any of the built-in PI nodes, when scheduled to run. It would run successfully when ran interactively.
Cause:
When submitting a scheduled task in MAS, if the account which runs the service (MAS service account) does not have permissions to access the database or the PI database login is different from the MAS service account, the task will fail.
For example, when using the PI Asset Framework node, credentials are required to access the OSI PI database. However, the credentials used are the MAS service account, which may not have permissions to access the OSI PI database or the account with permissions to access the OSI PI database is different than the MAS service account.
In the case, the PI Asset framework node does connect, interactively, but the OSI PI user credentials must be added in the prompt below:
These credentials are stored in the Credential Manager:
However, when the task is scheduled, the task fails as the MAS service doesn't access the Credentail Manager.