This is because the terminal hasn't connected yet. IsDemo returns false =) I asked developers why so, they reasonably answered "why, let it better say that it is a demo account?" =)
This morning I came to work, looked into 3 terminals (which work through the same data centre) - the connection indicator is green-blue in all of them, but the quotes are frozen at the end of Friday. In one of them I selected "Update" on the chart, connection icon disappeared, "Error" appeared, terminal hesitated for a minute. Then the quotes updated and the connection icon was blue-green again. I checked other 2 terminals - they have updated themselves, quotes are up to date. Hence the conclusions. 1. Loss of the connection is connected to the data center. 2. Pushing the data centre from the terminal leads to revival 3. Connection between data centre and terminals is restored automatically when the data center is working I am showing you the log from Friday:
20:45:03 Datafeed: symbol 'CHFJPY' updated<br / translate="no"> 20:45:27 Datafeed: symbol 'CHFJPY' updated 20:48:01 Datafeed: symbol '_DJI' updated 20:51:08 Datafeed: symbol '_DJI' updated 20:54:02 Datafeed: symbol '_SP500' updated 20:56:50 Datafeed: symbol '_NQCOMP' updated 20:58:34 Datafeed: symbol '_NQ100' updated 21:00:03 Datafeed: symbol '_NQ100' updated 21:01:04 Datafeed: wait for 0 sec 21:01:06 Datafeed: no connection 21:01:06 Datafeed: wait for 5 sec 21:01:12 Datafeed: no connection 21:01:12 Datafeed: wait for 10 sec 21:01:23 Datafeed: no connection 21:01:23 Datafeed: wait for 15 sec 21:01:40 Datafeed: no connection 21:01:40 Datafeed: wait for 20 sec 21:02:01 Datafeed: no connection 21:02:01 Datafeed: wait for 25 sec 21:02:27 Datafeed: no connection 21:02:27 Datafeed: wait for 30 sec 21:02:58 Datafeed: session #2838EF63 21:06:03 Datafeed: closed due -1384175195 sec timeout 21:06:03 Datafeed: checking new version failed 21:06:03 Datafeed: version check error 21:06:03 Datafeed: wait for 5 sec 21:06:09 Datafeed: session #2838EF63 21:06:10 Datafeed: has orders 21:06:10 Datafeed: pumping mode ok 21:06:12 Server: mapping disabled 21:10:59 Datafeed: wait for 0 sec 21:11:01 Datafeed: no connection 21:11:01 Datafeed: wait for 5 sec 21:11:07 Datafeed: no connection 21:11:07 Datafeed: wait for 10 sec 21:11:18 Datafeed: no connection 21:11:18 Datafeed: wait for 15 sec 21:11:35 Datafeed: no connection 21:11:35 Datafeed: wait for 20 sec 21:11:56 Datafeed: no connection 21:11:56 Datafeed: wait for 25 sec 21:12:22 Datafeed: no connection 21:12:22 Datafeed: wait for 30 sec 21:12:54 Datafeed: no connection 21:12:54 Datafeed: wait for 35 sec 21:13:30 Datafeed: no connection 21:13:30 Datafeed: wait for 40 sec 21:14:11 Datafeed: no connection 21:14:11 Datafeed: wait for 45 sec 21:14:57 Datafeed: login failed [2] 21:14:57 Datafeed: wait for 60 sec 21:15:57 Datafeed: login failed [2] 21:15:57 Datafeed: wait for 75 sec 21:17:12 Datafeed: login failed [2] 21:17:12 Datafeed: wait for 90 sec 21:18:43 Datafeed: login failed [2] 21:18:43 Datafeed: wait for 105 sec 21:20:29 Datafeed: closed due -1384175580 sec timeout 21:20:29 Datafeed: login failed [2] 21:20:29 Datafeed: wait for 120 sec 21:22:29 Datafeed: closed due -1384175700 sec timeout 21:22:29 Datafeed: login failed [2] 21:22:29 Datafeed: wait for 130 sec 21:24:40 Datafeed: closed due -1384175831 sec timeout 21:24:40 Datafeed: login failed [2] 21:24:40 Datafeed: wait for 140 sec 21:27:01 Datafeed: closed due -1384175972 sec timeout 21:27:01 Datafeed: login failed [2] 21:27:01 Datafeed: wait for 150 sec 21:29:32 Datafeed: closed due -1384176123 sec timeout 21:29:32 Datafeed: login failed [2] 21:29:32 Datafeed: wait for 160 sec 21:32:13 Datafeed: closed due -1384176284 sec timeout 21:32:13 Datafeed: login failed [2] 21:32:13 Datafeed: wait for 170 sec 21:35:04 Datafeed: closed due -1384176455 sec timeout 21:35:04 Datafeed: login failed [2] 21:35:04 Datafeed: wait for 180 sec 21:38:06 Datafeed: closed due -1384176637 sec timeout 21:38:06 Datafeed: login failed [2] 21:38:06 Datafeed: wait for 190 sec 21:41:17 Datafeed: closed due -1384176828 sec timeout 21:41:17 Datafeed: login failed [2] 21:41:17 Datafeed: wait for 200 sec 21:44:38 Datafeed: closed due -1384177029 sec timeout 21:44:38 Datafeed: login failed [2] 21:44:38 Datafeed: wait for 210 sec 21:48:10 Datafeed: closed due -1384177241 sec timeout 21:48:10 Datafeed: login failed [2] 21:48:10 Datafeed: wait for 220 sec 21:51:51 Datafeed: closed due -1384177462 sec timeout 21:51:51 Datafeed: login failed [2] 21:51:51 Datafeed: wait for 230 sec 21:55:42 Datafeed: closed due -1384177694 sec timeout 21:55:42 Datafeed: login failed [2] 21:55:42 Datafeed: wait for 240 sec 21:59:44 Datafeed: closed due -1384177935 sec timeout 21:59:44 Datafeed: login failed [2] 21:59:44 Datafeed: wait for 250 sec 22:03:56 Datafeed: closed due -1384178187 sec timeout 22:03:56 Datafeed: login failed [2] 22:03:56 Datafeed: wait for 260 sec 22:08:18 Datafeed: closed due -1384178449 sec timeout 22:08:18 Datafeed: login failed [2] 22:08:18 Datafeed: wait for 270 sec 22:12:49 Datafeed: closed due -1384178720 sec timeout 22:12:49 Datafeed: login failed [2] 22:12:49 Datafeed: wait for 280 sec 22:17:35 Datafeed: session #283C397D 22:17:37 Datafeed: 92 symbols 22:17:37 Datafeed: has orders 22:17:37 Datafeed: pumping mode ok 22:17:39 Server: mapping disabled
Today's log can't be posted, as it requires rebooting the computer (without it the log is zero length). Tomorrow I will do it.
This morning I came to work and looked into 3 terminals (which all work through the same data centre) - in all of them the connection icon is green-blue, but the quotes are frozen at the end of Friday. In one of them I selected "Update" on the chart, connection icon disappeared, "Error" appeared, terminal hesitated for a minute. Then the quotes updated and the connection icon was blue-green again. I checked other 2 terminals - they updated themselves, quotations were downloaded. Hence the conclusions - and
I still have one terminal hanging on the dc - I check. And check "successful" can not be called. Last night I started all the terminals, they started trading. So, 2 terminals that are connected directly work fine, but the one via dtz regularly gives errors #6 and #128. Something has not been done in it yet.
About 5 minutes ago, all the terminals are up again (Alpari Demo). The icon "No connection". Called "Update" => communication appeared for a minute, then "General Error" popped up. I tried again with refresh, the connection restored. Now I think I did the right thing, that I poked (woke up the DC) or for the purity of the experiment should I have waited for a couple of hours? Inet most likely disappeared briefly, because the spider is not available (although the mail was working), in theory, the data centre itself must somehow with the loss of signal from the server trying to restore communication. Now I don't know for sure if it could do it or not. On Monday, though, the datacenter was down for eight hours.
By the way, when opening a new account in the terminal connected via datacenter, a direct connection to the Alpari server is established for a short time, after opening the account it switches back to power from the dtz. Just in case.
Switched over to 5 mins on the Pound (I haven't watched them in a while). Something bumped up, took a closer look - breaks off around the 17th of October. Tried to do a "Refresh". No result. I can't view logs yet as they are not on my hard drive. Bild 285.
In general, it will not be possible to upload the missing data. I will try to do it directly.
I gave another try to the data centre. I closed the terminal and reopened it - I thought maybe when the terminal connected to the data centre, it would replenish its database of quotes. But it did not. I deleted broker from settings and reloaded MT4 and all missing quotes will be reloaded automatically. As far as I understand, there are no direct ways to replenish the histories in DTZ.
By the way, if anyone is interested, the Data Centre is NOT WORKING. Or requires super fine tuning, I don't know...
The average "advanced PC user" can't get Data Centre to work. Probably have to be a professional sys-admin and programmer. Psychic, too - not always possible to wait for an answer from the developers, you have to "read minds". New build of MT, auto-update of datacenter - and all in vain...
I conclude that it's just not finished and tested yet - can't find any other explanation. Well, or my incompetence...
Anyway, I have a request to the developers: when you change something globally in the configuration/use of dc, tell me about it - I'll try again.
I asked developers why so, they reasonably answered "why, let it better say that it is a demo account?" =)
1. Loss of the connection is connected to the data center.
2. Pushing the data centre from the terminal leads to revival
3. Connection between data centre and terminals is restored automatically when the data center is working
I am showing you the log from Friday:
20:48:01 Datafeed: symbol '_DJI' updated
20:51:08 Datafeed: symbol '_DJI' updated
20:54:02 Datafeed: symbol '_SP500' updated
20:56:50 Datafeed: symbol '_NQCOMP' updated
20:58:34 Datafeed: symbol '_NQ100' updated
21:00:03 Datafeed: symbol '_NQ100' updated
21:01:04 Datafeed: wait for 0 sec
21:01:06 Datafeed: no connection
21:01:06 Datafeed: wait for 5 sec
21:01:12 Datafeed: no connection
21:01:12 Datafeed: wait for 10 sec
21:01:23 Datafeed: no connection
21:01:23 Datafeed: wait for 15 sec
21:01:40 Datafeed: no connection
21:01:40 Datafeed: wait for 20 sec
21:02:01 Datafeed: no connection
21:02:01 Datafeed: wait for 25 sec
21:02:27 Datafeed: no connection
21:02:27 Datafeed: wait for 30 sec
21:02:58 Datafeed: session #2838EF63
21:06:03 Datafeed: closed due -1384175195 sec timeout
21:06:03 Datafeed: checking new version failed
21:06:03 Datafeed: version check error
21:06:03 Datafeed: wait for 5 sec
21:06:09 Datafeed: session #2838EF63
21:06:10 Datafeed: has orders
21:06:10 Datafeed: pumping mode ok
21:06:12 Server: mapping disabled
21:10:59 Datafeed: wait for 0 sec
21:11:01 Datafeed: no connection
21:11:01 Datafeed: wait for 5 sec
21:11:07 Datafeed: no connection
21:11:07 Datafeed: wait for 10 sec
21:11:18 Datafeed: no connection
21:11:18 Datafeed: wait for 15 sec
21:11:35 Datafeed: no connection
21:11:35 Datafeed: wait for 20 sec
21:11:56 Datafeed: no connection
21:11:56 Datafeed: wait for 25 sec
21:12:22 Datafeed: no connection
21:12:22 Datafeed: wait for 30 sec
21:12:54 Datafeed: no connection
21:12:54 Datafeed: wait for 35 sec
21:13:30 Datafeed: no connection
21:13:30 Datafeed: wait for 40 sec
21:14:11 Datafeed: no connection
21:14:11 Datafeed: wait for 45 sec
21:14:57 Datafeed: login failed [2]
21:14:57 Datafeed: wait for 60 sec
21:15:57 Datafeed: login failed [2]
21:15:57 Datafeed: wait for 75 sec
21:17:12 Datafeed: login failed [2]
21:17:12 Datafeed: wait for 90 sec
21:18:43 Datafeed: login failed [2]
21:18:43 Datafeed: wait for 105 sec
21:20:29 Datafeed: closed due -1384175580 sec timeout
21:20:29 Datafeed: login failed [2]
21:20:29 Datafeed: wait for 120 sec
21:22:29 Datafeed: closed due -1384175700 sec timeout
21:22:29 Datafeed: login failed [2]
21:22:29 Datafeed: wait for 130 sec
21:24:40 Datafeed: closed due -1384175831 sec timeout
21:24:40 Datafeed: login failed [2]
21:24:40 Datafeed: wait for 140 sec
21:27:01 Datafeed: closed due -1384175972 sec timeout
21:27:01 Datafeed: login failed [2]
21:27:01 Datafeed: wait for 150 sec
21:29:32 Datafeed: closed due -1384176123 sec timeout
21:29:32 Datafeed: login failed [2]
21:29:32 Datafeed: wait for 160 sec
21:32:13 Datafeed: closed due -1384176284 sec timeout
21:32:13 Datafeed: login failed [2]
21:32:13 Datafeed: wait for 170 sec
21:35:04 Datafeed: closed due -1384176455 sec timeout
21:35:04 Datafeed: login failed [2]
21:35:04 Datafeed: wait for 180 sec
21:38:06 Datafeed: closed due -1384176637 sec timeout
21:38:06 Datafeed: login failed [2]
21:38:06 Datafeed: wait for 190 sec
21:41:17 Datafeed: closed due -1384176828 sec timeout
21:41:17 Datafeed: login failed [2]
21:41:17 Datafeed: wait for 200 sec
21:44:38 Datafeed: closed due -1384177029 sec timeout
21:44:38 Datafeed: login failed [2]
21:44:38 Datafeed: wait for 210 sec
21:48:10 Datafeed: closed due -1384177241 sec timeout
21:48:10 Datafeed: login failed [2]
21:48:10 Datafeed: wait for 220 sec
21:51:51 Datafeed: closed due -1384177462 sec timeout
21:51:51 Datafeed: login failed [2]
21:51:51 Datafeed: wait for 230 sec
21:55:42 Datafeed: closed due -1384177694 sec timeout
21:55:42 Datafeed: login failed [2]
21:55:42 Datafeed: wait for 240 sec
21:59:44 Datafeed: closed due -1384177935 sec timeout
21:59:44 Datafeed: login failed [2]
21:59:44 Datafeed: wait for 250 sec
22:03:56 Datafeed: closed due -1384178187 sec timeout
22:03:56 Datafeed: login failed [2]
22:03:56 Datafeed: wait for 260 sec
22:08:18 Datafeed: closed due -1384178449 sec timeout
22:08:18 Datafeed: login failed [2]
22:08:18 Datafeed: wait for 270 sec
22:12:49 Datafeed: closed due -1384178720 sec timeout
22:12:49 Datafeed: login failed [2]
22:12:49 Datafeed: wait for 280 sec
22:17:35 Datafeed: session #283C397D
22:17:37 Datafeed: 92 symbols
22:17:37 Datafeed: has orders
22:17:37 Datafeed: pumping mode ok
22:17:39 Server: mapping disabled
Today's log can't be posted, as it requires rebooting the computer (without it the log is zero length). Tomorrow I will do it.
Something has not been done in it yet.
According to the log, the data was pumped around 6am, but the quotes on all three terminals showed Friday.
Inet most likely disappeared briefly, because the spider is not available (although the mail was working), in theory, the data centre itself must somehow with the loss of signal from the server trying to restore communication. Now I don't know for sure if it could do it or not.
On Monday, though, the datacenter was down for eight hours.
14:09:44 Datafeed: readable ping failed
14:09:44 Datafeed: waiting for 0 sec
14:10:05 Datafeed: no connection
14:10:05 Datafeed: waiting for 0 sec
14:10:09 Datafeed: session #283EC28C
14:10:09 Datafeed: check liveupdate 0
14:10:09 Datafeed: check liveupdate 4
14:10:09 Datafeed: check liveupdate 3
14:10:13 Datafeed: pumping mode ok
14:10:14 195.135.1.3: '105039' login [ver: 400.186]
14:10:14 195.135.1.3: '117245' login [ver: 400.186]
14:10:15 server: mapping disabled
14:10:17 195.135.1.3: '105040' login [ver: 400.186]
14:39:08 195.135.1.3: '117245' login [ver: 400.186]
14:39:08 195.135.1.3: '105039' login [ver: 400.186]
14:39:18 195.135.1.3: '105040' login [ver: 400.186]
14:48:14 Datafeed: readable ping failed
14:48:14 Datafeed: waiting for 0 sec
14:48:18 Datafeed: session #283EC28C
14:48:18 Datafeed: check liveupdate 0
14:48:18 Datafeed: check liveupdate 4
14:48:18 Datafeed: check liveupdate 3
14:48:20 Datafeed: pumping mode ok
14:48:22 Server: mapping disabled
14:48:25 195.135.1.3: '105039' login [ver: 400.186]
14:48:25 195.135.1.3: '105040' login [ver: 400.186]
14:48:25 195.135.1.3: '117245' login [ver: 400.186]
On the 19th,20,21,22,23rd no update attempts were seen. Such attempts appeared only on the 24th.
And on the 23rd I found many such records:
12:09:15 195.135.1.3: connect
12:09:15 195.135.1.3: connect disabled - no data connection
12:09:19 Datafeed: no connection
12:09:19 Datafeed: wait for 65 sec
12:09:20 195.135.1.3: connect
12:09:20 195.135.1.3: connect disabled - no data connection
12:09:25 195.135.1.3: connect
12:09:35 195.135.1.3: connect
12:09:35 195.135.1.3: connect
12:09:35 195.135.1.3: connect disabled - no data connection
12:09:35 195.135.1.3: connect disabled - no data connection
12:09:35 195.135.1.3: connect disabled - no data connection
12:09:40 195.135.1.3: connect
12:09:40 195.135.1.3: connect
12:09:40 195.135.1.3: connect
12:09:40 195.135.1.3: connect disabled - no data connection
12:09:40 195.135.1.3: connect disabled - no data connection
12:09:40 195.135.1.3: connect disabled - no data connection
12:09:45 195.135.1.3: connect
Internet on the 23rd seemed to be working, I can't remember what happened then.
In general, it will not be possible to upload the missing data. I will try to do it directly.
The average "advanced PC user" can't get Data Centre to work. Probably have to be a professional sys-admin and programmer. Psychic, too - not always possible to wait for an answer from the developers, you have to "read minds".
New build of MT, auto-update of datacenter - and all in vain...
I conclude that it's just not finished and tested yet - can't find any other explanation.
Well, or my incompetence...
Anyway, I have a request to the developers: when you change something globally in the configuration/use of dc, tell me about it - I'll try again.