2017.06.14 18:06:34.498 Core 1 connecting to 127.0.0.1:30002017.06.14 18:06:45.522 Core 1 tester agent authorization error
this shit is already fucked up! Several times you have to poke to start testing! How to treat it?
tester agent authorization error
Share
gedd
same bug on the latest release 2363
to the pile … antivirus only Windows and it is disabled …
renat
Let’s check this situation
barabashkakvn
I have Kaspersky – earlier I added AppData with terminals to the exception, and a day ago I added the terminals themselves (from ProgramFiles) – now you can run testing directly from MetaEditor while the terminal itself will start and the test runs on the first attempt. Previously, it was a prerequisite to preload the terminal, but now it is not necessary – since the terminal will start and run the test from the first kick.
igorbel
I don’t have an antivirus. Only native Windows defender. And both files (terminal64.exe and metatester64.exe) have long been added to the exceptions (Settings – Excluded files and locations). Unfortunately, this does not help.
They are also added to Excluded processes.
This stuff appears even when real-time protection is disabled in Microsoft Defender.
renat
This is often due to the antivirus – it takes a long time to check the exe file of the tester before starting, and as a result, the terminal does not have time to wait for the tester to start.
Try to put metatester[64].exe in the antivirus skip mode and try it.