we have on PI data archive, when i create the trust for other machine, it wont come in effect till we restart the PI server.
Not sure why?
What is the trust used for? After you change security, you need to restart whatever application/service you are using so it re-authenticates with the PI server.
A reboot of the PI Server should not be needed. After creating the trust, what messages do you see for the connecting application in the PI Message log?
PS: Trusts are not really recommended anymore, in favor of using mappings to windows credentials
Yes, it is not recommended to use trust.
But still, i am facing this issue.
And i am getting msg logs as RPC resolver.
Not sure why only this archive is having this issue.
An answer to Kevin's question would be helpful - what this trust should allow?
Moreover, the full message would also help. If you see a message saying RPC Resolver is offline, it usually means that the service/application is not running, so I am not sure it is relevant here.
When you create a trust you need to restart the client application (not the PI Data Archive). The reason for this is once the client attempts to connect and fails authentication it will not try to reconnect again. So if you add a trust, the client won't authenticate through it until a new connection is attempted and this is done by stopping / starting the client.
If you stop the PI Data Archive, most clients have reconnection code. One the client, what is most likely happening is that the connection is dropped due to the PI Data Archive reboot and connections are attempted afterwards. If the PI Data Archive is back online in time (before the client times out) then the client will try to connect again and now since there is a trust the connection will succeed.
As the others have said, you should use PI Mappings. The idea is the same though, after creating a mapping clients must reconnect to try authentication again...
Retrieving data ...