You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
there are 2 possibilities:
1. the first order is executed (but you will learn about this by changing the list of open positions or by checking the terminal logs), the second order is not even sent to the server;
2. the second order is in any case not sent to the server. the first order will not be executed. see the reason in the logs
1. the first order is executed (but you will know this by changing the list of open positions or by checking the terminal logs), the second order will not even go to the server;
2. the second order is in any case not transmitted to the server. the first order is not executed.
Ok. Then explain to me, and others as well, what the meaning of the lines :
1. 2005.11.29 16:59:52 '82991': login (4.00, #2841B56A)
2. 2005.11.29 17:00:33 'TradeContext: ping error
3. 2005.11.29 17:02:25 '82991': cannot login [No connection]
4. 2005.11.29 17:03:33 '82991': request was accepted by server
5. 2005.11.29 17:03:33 '82991': request in process
6. 2005.11.29 19:11:44 '82991': close order #2076385 sell 0.10 EURUSD at 1.1759 sl: 0.0000 tp: 0.0000 at price 1.1743
7.2005.11.29 18:36:29 '82991': instant order sell 0.10 EURUSD at 1.1785 sl: 0.0000 tp: 0.0000
I'm asking you not to take it as aggression, I'm just tired to analyze why orders are not executed and I don't understand everything in logs, this kind of entries are most frequently used in logs.
And what does the following line mean:
2005.11.30 09:38:40 Old tick EURUSD5 1.1779/1.1782
also no answer ?
Where can I read what the log entries mean ?
2 options are possible:
1. the first order is executed (but you can find this out by changing the list of open positions or by checking the terminal logs), the second order will not even go to the server;
2. the second order is in any case not transmitted to the server. the first order is not executed.
Let's go back to where we started. There are already 50 of us in Kharkov and we are trying to solve this problem and "pyrodex" is not the first and alas not the last. Every day people come to the Kharkiv dealing centre of Ukrsotsbank and do not work as experts (Ukrsotsbank by default prohibits the use of experts on real accounts), but use pens on real money and ask when this x-..... will end. Some people thought they had computer problems. Called the Kiev office of Ukrsotsbank (MT4 buyer), and they answer verbatim the following ".... this program is demanding to communication channels, deal with providers .....", to the question ".... why it works very badly in your Kharkiv branch" answer, "...... they have problems with the local network in Kharkiv....". And it should be noted the following, the problems with the local network of Kharkiv dealing centre started the day they switched to MT4 on Monday and lasted for the fourth week without a break, on Friday on MT3 two days before that there was no problem for some reason and for the whole year before that too. It is difficult to assume that Ukrsotsbank suddenly started cheating, because before the introduction of MT4 it did not give any reason for suspicion. There were a couple of misunderstandings during the year, but within reason. We got to the deputy chairman of the bank (and Ukrsotsbank is one of the ten largest banks in Ukraine) he gave us the head of automation and computerization department. Two days later he gave us the answer that he was not going to sacrifice the security of the bank to make MT4 work. Judging by the fact that the developers did not say anything intelligible, except to negotiate with providers and other nonsense, there is no solution to the problem yet.
Back to where we started...
The specialists at the Kharkiv dealing centre have not contacted us.
The thing is that when I contacted my brokerage company about the connection problem, they sent me back to the developer, i.e. you.
Since MT4 is very picky about communication channels, could you please specify requirements for these channels?
I am not sure what to do if I want to use these channels, but I don't know their parameters.
I asked my provider, but he has a counter question: what quality do you need? What can I tell him?
What should I do then in order to use mobile trading, not Wap, but the full-fledged MT version via GPRS?
And not all cities in Russia and the CIS have such an amazing quality of Internet as in Moscow?
And to spare you the head, please upload the decrypted log files.
But the meaning of such clear, and the reasons for such records as:
1. 2005.11.29 16:59:52 '82991': login (4.00, #2841B56A)
2. 2005.11.29 17:00:33 'TradeContext: ping error
3. 2005.11.29 17:02:25 '82991': cannot login [No connection]
4. 2005.11.29 17:03:33 '82991': request was accepted by server
5. 2005.11.29 17:03:33 '82991': request in process
6. 2005.11.29 19:11:44 '82991': close order #2076385 sell 0.10 EURUSD at 1.1759 sl: 0.0000 tp: 0.0000 at price 1.1743
7.2005.11.29 18:36:29 '82991': instant order sell 0.10 EURUSD at 1.1785 sl: 0.0000 tp: 0.0000
not really.
So that you can argue with the provider as well as with you.
The specialists of Kharkiv dealing centre did not contact us.
So that's who is to blame for all the problems! Kharkiv dealing center!!! And who else has to come to you to bow down so that you finally get to grips with the issue?
Now to the point. I repeat myself. There are problems with connection. While waiting for the dense stream of quotes (news, market activity) the delays in delivery of information (quotes, news feeds) are up to 3 minutes. Visually, this is expressed in the fact that the flow of quotes "stops", "accumulates", and then the "accumulated" portion of quotes comes to the client's side in a single moment. After a few seconds, the situation repeats until the market settles down.
Your advice about preferring a specific provider may be valid. Indeed, through the provider A routing goes through 15 servers - American, through Germany goes back to Ukraine. The problem is present. Through ISP B, the routing goes exclusively through "Ukrainian" servers. The problem is not observed. However!!! Latency in ms at provider A is 2-3 times less than at provider B. Is MT product so nationalized-privileged that it has an aversion to bourgeois communication channels?
Again, before the introduction of MT4 there was NO problem at all. The problem with connectivity is ONLY with MT4 software (no provider distinction). IE, ICQ and all the rest works without problems.
Please make it a priority to solve the connectivity issue at last.
Thank you.
So that's who is to blame for all the problems!!! Kharkiv DC!!!
Please read all the previously posted messages in this thread carefully, so that the subsequent posts are logically related, and not separated from the context of the discussion.
A quote from one post earlier: "...We got to the deputy head of the bank's board (and Ukrsotsbank is one of Ukraine's top ten banks) he gave us the head of the automation and computerisation department to tear down. Two days later he told us that he was not going to sacrifice the bank's computer security for the sake of one MT4.
Let's stop using words! It's not the goal to annoy you. Make sure that MT4 is not worse than MT3 in terms of communication quality and you will get as many deferments as you want.
You said yourself 23.11.05 20:15 "The problem is being studied carefully" and what was the outcome of this study?
And if it did not, when will it end?
And if it is no secret, you are in Moscow ? So you have full brilliance with the connection, which can not be said about the regions.
If you need help in checking the quality of communication from different regions, just tell me what to do, there are at least 10 people from different parts of the CIS who are willing to do any work to investigate the problem, just to accelerate its solution.
You are going the right way !!!
Can't we change "some more settings on the broker side" to make the orders execute even better?
Checked it on an Alpari demo.