You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i built successfully from source code the entire solution in visual studio 2019.
Then i run the MtApiInstaller.msi and, also, the MtApi_Setup.exe in a VPS where i have an instance of MT4.
I followed all the instructions and i put the .ex4 in the right folder and also the other files like "json.mqh", for example, in the include folder.
If i try to insert the Expert in a chart i get the attached error.
If i look at the chart window i can see the smile face for a while and then it disappers and, also, the 8222 port is not open.
Since today i had the 1.14 release installed and everything worked fine (same VPS).
The OS is a Windows 7 Professional edition 64 bit.
Do you have any suggestions, please?
Thank you very much and best regards
The text was updated successfully, but these errors were encountered:
Hi, i had the same problem but with the exe of your link now i can attach mtapi to chart.
The problem now is that i can't connect. The function apiClient_ConnectionStateChanged is never call and the state is disconnected. Call to connect don't throw any exception.
Hello,
i built successfully from source code the entire solution in visual studio 2019.
Then i run the MtApiInstaller.msi and, also, the MtApi_Setup.exe in a VPS where i have an instance of MT4.
I followed all the instructions and i put the .ex4 in the right folder and also the other files like "json.mqh", for example, in the include folder.
If i try to insert the Expert in a chart i get the attached error.
If i look at the chart window i can see the smile face for a while and then it disappers and, also, the 8222 port is not open.
Since today i had the 1.14 release installed and everything worked fine (same VPS).
The OS is a Windows 7 Professional edition 64 bit.
Do you have any suggestions, please?
Thank you very much and best regards
The text was updated successfully, but these errors were encountered: