Hi jcl.

I have 1.34 Z12 and Z3 running on a VPS. Over the weekend something happened and they hung - apparently Z3 hung badly. When I checked after the weekend neither was running. I had to force-close both instances. Now when I try to start Z3 it never completes the FXCM login. If I start Z12 first it starts up OK, but when Z3 tries to start Z12 hangs. If I force-close Z3, Z12 functions normally again.

How do I fix Z3?!

Thanks.

Hmm, if Z12 works then it is not some connection issue. Maybe the Z3.trd file is damaged? Delete that file and start again.

Renamed z3.trd to z3.trd.damaged & tried to start - same result - FXCM login hangs just producing dots. No new z3.trd created.

Z3_<asset>diag.txt shows:



Now what?

Thanks.

The .trd file is the only file that could be affected by a previous session. If it's not the .trd, then something else happened with your Zorro installation at the weekend crash, or maybe with the whole VPS. Next step would be installing the latest Zorro version and starting Z3 again.

I have reinstalled 1.34 and the problem persists. I can login fine to the account via TS. If I put a bad password into Zorro the login fails as expected. The only problem is using the correct login information in Zorro.

Besides the .trd file, is Zorro maintaining API info somewhere else which could be causing the problem? Does Zorro produce any API logs?

Thanks.

Also, in the diag.txt snippet above, what does the "ses st" after "Login Real" signify? Normally "Login Real" is followed by a colon, a number, & a ms count...

Thanks.

FXCM reports successful logins on their side. So Zorro evidently isn't recognizing this success. Perhaps something unexpected is being returned causing the "ses st"?

No, the "ses st" is a normal debug message indicating initialisation of the FXCM API. The login is also executed, otherwise you would not see any dots, but some subsequent API call hangs.

The next step, when damaged Zorro and FXCM files can be really excluded as the reason of the problem, would be looking for damage in the Windows system. Check in the event log what really happened with your VPS last weekend. Ask your VPS provider if he has a backup and can reset your VPS to the state of last week.

Thanks jcl.

I will look, but actually don't expect to find anything...

Also, don't understand how it could be a Windows/server level problem given that Z12 is working fine on the same VPS (installed in a different folder).

After the successful login is the next step price download? Could a history file be damaged?

The only other thing I remember is clicking the Zorro window during Weekend when the connection box was grey - could this have hung something up?

Thanks.

No, a damaged history file has no effect on logging in to the broker. And I don't see how it matters anyway - if Zorro A does not work anymore and Zorro B does, then obviously some file of Zorro A is broken. So a simple reinstallation solves that problem, or even just copying Zorro B over to Zorto A. I do not really see what other advice I could give you here.