Cannot get MD5 check of TDB file, server may not connect you

[Carlo Santucci]

In our multiplayer sessions there is a problem affecting specifically one person who wants to act as dispatcher: with every route he gets in the logfile following error message:
Cannot get MD5 check of TDB file, server may not connect you
The complete logfile (OpenRailsLogdi fabio) is attached.er
So we have to start with another dispatcher, then the person having the problem successfully enters the game as play, and then the dispatcher enables him as assistant. But here a second problem arises: after some tens of minutes he is no more able to throw switches and/or signals.
(This report however focuses only on the first bug).

[Carlo Santucci (carlosanit1)]

Sorry, one sentence was mistyped. I repeat it here

 So we have to start with another dispatcher, then the person having the problem successfully enters the game as player, and then the dispatcher enables him as assistant. But here a second problem arises: after some tens of minutes he is no more able to throw switches and/or signals.

[Jijun Tang (jtang-h)]

Please check if 1794 fixed the problem.

[Carlo Santucci (carlosanit1)]

We had yesterday a MP session with the person that had the problem, and the problem was gone, thank you. However what happened to someone is that when he entered the session as client he got on the F5 HUD display the string "one player, one train" and only after some time he got the string with the amount of players effectively within the session. I'm not able to say if this issue was already present in previous sessions.

[Jijun Tang (jtang-h)]

What's the username he used to connect? I will check the log file to see if anything is wrong.

[Carlo Santucci (carlosanit1)]

I'm not sure I understood correctly your question, but the username of the critical person is Exp_1648. You can find it in the log file attached to the first post.

[Peter Gulyas (pzgulyas)]

According to http://www.elvastower.com/forums/index.php?/topic/24027-cleaning-up-old-assigned-bugs/page__view__findpost__p__147302

it is solved.