2 of 2 people found this helpful
To force the PI Web API service to stop you could restart your server.
Usually just the service PI Web API Crawler should have the start up type of Automatic (Delayed Start).
You can also check if the databases are indexed on your PI Vision Server at:
Please let me know how it goes.
After restarting server, PI Web API service is running and also I have checked databases by using shared link.
I can see standalone AF Servers added but Test connection is giving failure result.
Let me know how to add/remove AF Server from Coresight 2016 R2 and pre-requisite/steps to be done in order to get successful connection to it from CoreSight.
Kindly check below screenshot.
At the PI Web API databases https://localhost/piwebapi/admin/search/database.html
You could try removing the AF databases:
And adding them back:
The configuration for PI Vision can be checked on these videos:
The login failed message you pointed indicates that the PI Directory Publish service user does not have permission on the database, however this should not interfere on PI Web API operation.
Next Steps -
1 - Check PI AF security, as PI Web API is running under a machine account the PI Vision machine should have permissions (Video 1).
2 - Try changing PI Web API account to a service user through PI Web API Utility.
AF Servers connectivity to Coresight server issue has been resolved.
All three AF servers were in workgroup environment with different user and passwords, So I have created a new local accounts identically among the three servers (identical password) and changed the WebAPI / Crawler service and the Application pool to that account. Also added the account in AF Security permissions.