• (Question mark in yellow circle) The component is in an unknown state.
Note : Some connectors do not support discovery of data source contents. If you use a connector that does not support discovery, see the connector's user guide for details on collecting data.
For PI System Connector, the data source setting can directly be configured in the data source box. Please click your data source (source AF server) to configure your data hierarchy to be sent to destination.
If you have not seen below, please take your time to watch them through. 6th video show you how to configure PI System connector, relay using the PI Data Collection Manager.
Yes, I've done a correct setup and configured a data hierarchy, but the data source still stays in a undiscovered state.
Source AF Server and databases are getting discovered automatically so I think user rights are ok...
In Pi System Connectors log file there is a error message:
PI Relay: desktop-b11rce5 | PI Relay Client - Error sending PI System Connector message: No processor found at target 'PISystemQueueID'.
Any idea what's the cause of this? And is this related to the data source discourey issue?
Sorry for the delay. I would first check if your relay component shows ok before trying to add/configure PI System Connector. What errors do you see for the Relay component?
It appears that there is a bit of confusion on what steps need to performed where. The UI can be a bit confusing since it supports a number of connectors which don't support all of the features of the Data Collection Manager.
The data source configuration is performed on the node hosting the PI System Connector. You can browse to https://<PISystemConnectorMachine>:<port>/ui to configure the data source, not the Data Collection Manager since this connector does not support discovery from the DCM as indicated by the UI.
I would strongly suggest going through the Youtube playlist listed above and go step by step with it, it will get you up and running in no time. Then, if you have any additional issues reviews the Event Viewer logs on the nodes hosting the PI System Connector, the Relay, and the DCM.
At the moment I get a error from the Event Viewer logs:
FixUpPointDefinitions encountered error finding PI point definition list: [-10722] PINET: Timeout on PI RPC or System Call.
What can cause this? I already read this KB00232 - -10722: RPC Timeout on PI RPC or System Call but I still haven't found a solution...