Error number 6 - page 13

New comment
 
I made specially an Expert (IsConnected) to track connection status to server - posted on "IsConnected - collecting statistics of terminal connection to server ;)".
Made specially for error #6 ;) result is not what I expected...
File _IsConnected.txt for today:
2005.09.15 17:22:14 - 04:45:15 + + + OnLine + +<br / translate="no"> 2005.09.16 04:45:15 - 04:46:24 - - - OffLine- - -
2005.09.16 04:46:24 - 09:11:22 + + + OnLine + + +
2005.09.16 09:11:22 - 09:11:23 - - - OffLine- - -
2005.09.16 09:11:23 - 10:35:42 + + + OnLine + +
2005.09.16 10:35:42 - 10:35:43 - - - OffLine- - -
2005.09.16 10:35:43 - 10:36:43 + + OnLine + +
2005.09.16 10:36:43 - 10:36:49 - - - OffLine- - -
2005.09.16 10:36:49 - 10:37:49 + + OnLine + +
2005.09.16 10:37:49 - 10:37:54 - - - OffLine- - -
2005.09.16 10:37:54 - 12:56:07 + + + OnLine + +
2005.09.16 12:56:07 - 12:56:09 - - - OffLine- - -
2005.09.16 12:56:09 - 12:57:09 + + + OnLine + +
2005.09.16 12:57:09 - 12:57:15 - - - OffLine- - -
2005.09.16 12:57:15 - 12:58:16 + + OnLine + +
2005.09.16 12:58:16 - 12:58:22 - - - OffLine- - -
2005.09.16 12:58:22 - 13:18:14 + + + OnLine + +
2005.09.16 13:18:14 - 13:18:15 - - - OffLine- - -
2005.09.16 13:18:15 -


Error time #6:
09:41:04
10:08:07
10:37:31
12:25:38
12:47:34
12:58:08


Both times are local, the difference with the server time (Alpari demo) is +hour. i.e. when Alpari has 15:00, I have 16:00

So, it turns out that errors are not due to connection failures, which I personally hoped for...


But a few questions arose along the way:
- how often does the terminal check connection status? I have suspicions that information about connection failures comes too late...
- Did Alpari have any problems at that time...? Although the question is certainly off the mark....
 
Caught this error again today on the Alpari server. Had it for a few hours. Who else has noticed it?
 
The day before yesterday, 20.09.05, I was testing how close to the market price a pending order can be placed. For this purpose I created a script, simple - only placing order and MessageBox after that with displaying results. However, error 6 has been constantly popping up after several unsuccessful attempts (too close to the market) followed by recompilation with parameters corrected. Restarting MT4 was the only way to help. When I started writing this post, I easily reproduced it twice (it took about a minute of running the script with wrong parameters) on the MQ server (although I think it was a terminal problem). After the first error, for about half an hour, until I restarted MT4, neither automatically nor manually I could place any orders - all the time error #6. Not a single!!! Expert Advisor worked for me during this testing. There were no orders placed either.
 
I think the truth is out there.
 
More fiddling with my script. No pattern. One and the same order of actions at first leads to error #6, after reloading MT4 the same order of actions works fine. The error was the same when working on both Alpari server and MQ.
 
Caught this error again today on the Alpari server. Had it for a few hours. Who else has it?

Alpari Demo - "no connection with trade server"

me the most =)))))))
 
I think Roman should "donate" his script to the developers, maybe it will speed up catching the bug.
 
Yes, frankly and unambiguously error number 6 is torturing, and very badly!!!! :( The same problem, after restarting MT4 it seems to work a little, but then it starts to fail, re-login does not help, only a restart. The only thing I would like to point out is that unlike many other EAs posting here, when my Expert Advisor blows up with error 6, my hand trades are going great... (Bild 182 dated 14.09.05, Alpari DC)

At my time I wrote a peculiar script for MT3 that checked how long there were no quotes, for example, if there were no quotes for 10 min then it considered that the connection was lost and made MT restart and the same operation was performed with xDSL reconnection.
Thought it wouldn't be a problem in MT4... Hopefully the bug will be caught and repaired soon!
 
I will repeat my post in the next thread (the problem is too serious to send a link)
===
in fact, "error number 6" is not a terminal error. we honestly report the lack of connection (pamping lives separately, a new connection is set for trades every time). but if the Expert Advisor (or script) constantly shows this error, but you can perform a trade operation, then yes, this is our error. and we need more information to catch it.
===
 
I will repeat my post in the next thread (the problem is too serious to send a link)<br / translate="no"> ===
Actually, "error number 6" is not a terminal error. We honestly report the absence of connection (pamping lives separately, each time a new connection is set for trade operations).
===

I can do it by hand as well... The communication indicator is green and IsConnected returns true...
And information - just tell us what it is - we'll help in any way we can...
1...67891011121314151617181920...32
New comment