I 'm trying to create a new RTQP with PI SQL Commander Lite to retrieve data, but show this error.
It appears the PI System you are attempting to connect is installed in the Azure cloud. Is this the case?
Can you connect the AF Server using PI System Explorer on your client machine?
If this works, can you confirm which ports are open / exposed by the Azure environment to allow incoming connections?
Please note that the screenshot you posted above, together with the information which ports are open can be used by an attacker trying to break in or attempting a Denial Of Service (DOS) attack or similar. For this reason, please always obfuscate information about public endpoints.
You've also created a Discussion about your issue. Please avoid creating duplicate threads. We will be deleting the Discussion.
Edit: Correction: We have locked the other thread.
Yes, this is the case. I'm can connect AF Server using PI System Explorer on my client, and all ports are open.
Only works on the same domain, or trust required?
Error 10060 indicates the connection attempt has timed out. Reasons for this could be that a firewall is blocking communication or there is no service listening on the specific port. Please see Which firewall ports should be opened for PI SQL Data Access Server products. For PI SQL Data Access Server (RTQP Engine) port 5464 is used for https and port 5465 is used for net tcp communication. According to the details you see when testing the connection, both protocols fail. With all firewall ports open, please make sure the PI SQL Data Access Server (RTQP Engine) service is running.
You could use telnet.exe to confirm there is an endpoint listening. The thing which is a little ugly with this is that you need to close the command prompt to stop the telnet process if the connection is successful. If telnet doesn't work, you may have to enable it first. For Windows 10 this can be done through Programs and Features -> Turn Windows Features on or off. Execute telnet in a command prompt as follows:
telnet <host> <port>
At this point I do not believe your issue is due to a problem with authentication. However, in a cross domain environment, domain trusts are required to allow Kerberos delegation. When configuring security for an account that exists in the other domain, the fact that you cannot see / find the account indicates the other domain is not trusted. What you can try is removing the checkmark for "Trusted connection" and enter valid credentials.
If you are using a self signed certificate, your client machine may not trust it and decide to not send the request. For this reason, it will be useful to know if the server receives the request. I suggest you enable debugging for the client (P SQL Client OLEDB) and for the server (RTQP Engine) according to the troubleshooting section in Playbook - PI SQL Client and RTQP Engine.
Retrieving data ...