did you check the user which is running the PI Crawler service.
Is it a domain user? If so
- does it have a mapping to the PI Server?
- does it have permissions on the %programdata%\OSIsoft\WebAPI\Search folder?
If it is a service account, you will have to check the same for the machine where the Crawler is installed
Thank you for your reply. These basic steps are set correct. That's why I mentioned it in my post. I can get the values of all piponts and values of all elements attributes of all AF databases by clicking on the links from the .../piwebapi/ url.
I'm using WIS(windows integrated security) only with Kerberos. I can see that it is using WIS successfully in the message log in SMT.
To be sure the domain service account can authenticate and has the correct authorization I started IE(elevated) on the coresight server node and logged in with the domain service account in the piwebapi URL.
I did these checks prior to my first posting here.
It's not a requirement to run PI Web API service or the Index Search Crawler service under a specific service account. Also logging on with the service account isn't required.
The Index Search Crawler doesn't pick up databases automatically. It's intended that you configure the source that you like to become crawled.
The first resources to check in case of configuration issues is the PI Coresight Administration Page at http://<yourserver.host.fqdn>/Coresight/Admin
In addition please check the PI Web API and the Index Search Crawler logs in Windows Event Viewer (eventvwr.exe) under Applications and Se4rvice Logs. The one for the Search Crawler is named OSIsoft-PISystemSearch.
If you require further assistance, please contact OSIsoft Technical Support.
Found a solution.
Uninstall the PI WEB API 2015 R3 and install the PI WEB API R2. Now you have the option back to create a self signed certificate. In R3 the only option is to choose one from the list. The ones available were not valid for the FQDN. (this tip is also sort of mentioned here: KB01318 - Self-signed certificate created by PI Web API 2015 R3 admin utility may fail for FQDN )
After update from PI WEB API 2015 R2 to R3 and choosing the selfsigned OSIsoft certificate created when installing R2 everything works likes a charm.
I didn't assume a certificate issue from what you described before. I definitely learned something today
Thank you for letting us know that your issue is resolved and for providing additional insights! You marked your answer as success which unfortunately is not the action that would turn your question into one showing as answered. Please allow me marking your answer as Correct Answer.