How do I check the operation of the data centre? - page 8

New comment
 
On the terminal, which is operated by DC, I switched to the real account. Terminal is successfully copied to work via internet, but not received warnings about data centre not being connected to main server.
It looked like this:
2005.12.29 12:03:14 '105040': login (4.00, #285A433D)<br/ translate="no"> 2005.12.29 12:03:13 '105040': login (4.00, #285A433D)
2005.12.29 12:02:01 '105040': DataCenter does not correspond with MainServer
2005.12.12.29 12:02:01 '105040': DataCenter does not correspond with MainServer
2005.12.29 12:02:01 '105040': login (4.00, #285A433D)
2005.12.29 12:02:00 '16537': login (4.00, #285A67EE)

I may try to use my real account but I have nevertheless deleted it from the terminal.



I tried a couple more times, terminal says "Invalid account". Then I looked closely at the details of the account I was opening and it turned out that the server was Alpari's real server.
 
is the DC connected to the same server as the live account? (this is about the DataCenter does not correspond with MainServer) if not then it is ok:)
 
The DC is connected to the Alpari demo server and the real one to the Alpari real server.
 
Well, Alpari-Customers and Alpari-Demo are different servers (physically). That's why the terminal says "not correspond with MainServer" when switching. We should have one DC for each Alpari-Customer and one DC for each Alpari-Demo:).
For me by the way it works fine. When switching back, no "Invalid account" appears.
 
That's what I'm saying, when trying to connect to a demo account (the terminal stores the settings) it shouldn't substitute the real server. That's why "Invalid account".
 
If you just switch between the two servers, no disabled accounts are popping up...
can you describe your actions in more detail?
 
Strange situation - 2 out of four terminals connected via the data centre to Alpari are showing blue bars and two are showing red bars, with not a very good reading.
 
Found a lot of login attempts in non-working terminal logs, now it's working on its own (I didn't do anything).
2006.01.12 16:46:37 Old tick #T60 25.0500/25.0700<br / translate="no"> 2006.01.12 16:46:37 Publisher: ok
2006.01.12 16:46:34 Publisher: starting
2006.01.12 16:46:34 Old tick #T60 25.0500/25.0700
2006.01.12 16:46:34 '117245': login (4.00, #28659DCC)
2006.01.12 16:45:56 '117245': login (4.00, #28659DCC)
2006.01.12 16:43:49 '117245': login (4.00, #28659DCC)
2006.01.12 16:42:42 '117245': login (4.00, #28659DCC)
2006.01.12 16:41:30 '117245': login (4.00, #28659DCC)
2006.01.12 16:40:17 '117245': login (4.00, #28659DCC)
2006.01.12 16:38:10 '117245': login (4.00, #28659DCC)
2006.01.12 16:36:51 '117245': login (4.00, #28659DCC)


Last fourth logged with "General error"
 
The fourth also came out of the coma, the data centre logs went, I can't copy it head-on.
 
Fourth one also came out of coma, went data centre logs, can't copy head-on.

Better upgrade to build 188.
Alpari has brought in some new data centres and found network problems.
12345678910111213141516
New comment
Reason: