Request you to check PI server mapped in AF attributes. Looks like host name is not resolved /does not exist or no permission.
I think that is exactly what is going on. We have a collective for our live Data Archive so we have a DR and a Prod server setup. There is an alias for the Data Archive. Suppose the alias is Bob. When I look at the properties for the server connections for the users having issues with their client tools, Pi Builder or PSE, they had the alias as the Host. I did not. I had the host as the actual production server name. When the other users pointed the connection to Production, the issues they were seeing went away. So it sounds like we have an issue with the resolution of that host name when the connection to that collective has actually been cached on the user machine to be pointing to DR.
Does that sound like a valid description of what is likely going on?