v. 2023-02-08
Our client says it started to experience this:
When we click "cancel" in the login window in order to switch to another company a "blinking" window "Connecting" appears and we have to kill the client using Windows Task Manager. They have windows environment.

We tried to replicate it and succeeded in 1 of 5 times. At that time another user was running a long report (NL>>Reports>>Daily balances). We tried to replicate it more with the report running, but we failed.
We have windows clients, linux server.

Any ideas?

Client log when we succeeded to replicate:
2023-04-04 11:22:06 re-connect opening connection
2023-04-04 11:22:06 updating company 0 to use debesis2.stabilios-sistemos.lt:1200 as server
2023-04-04 11:22:06 replaying messages
2023-04-04 11:22:07 finished replaying 0 messages
2023-04-04 11:22:07 m4status: 13
2023-04-04 11:22:08 re-connect opening connection
2023-04-04 11:22:08 replaying messages
....

2023-04-04 11:22:09 finished replaying 0 messages

>>>Killed the client here<<<<


2023-04-04 11:22:25 *** running with new mail receiving and parsing ***
2023-04-04 11:22:25 *** Using Clock Replacement ***
2023-04-04 11:22:25 Last session was not properly terminated
2023-04-04 11:22:25 *** using a freelist to keep track of free space ***
2023-04-04 11:22:28 Database ID is: 31966F05E63788146E68FA5D4B22D2E5
2023-04-04 11:22:28 Waiting for HAL threads to finish
2023-04-04 11:22:28 updating company 0 to xxxxxxxxxx:1200 as server
2023-04-04 11:22:30 8.5 2023-02-08 (build 85510137)
2023-04-04 11:22:35 Waiting for HAL threads to finish
...
2023-04-04 11:23:01 replaying messages
2023-04-04 11:23:01 finished replaying 0 messages
2023-04-04 11:23:01 m4status: 13
2023-04-04 11:23:01 re-connect opening connection
2023-04-04 11:23:01 replaying messages
...same messages repeated here...
2023-04-04 11:24:45 re-connect opening connection
2023-04-04 11:24:45 replaying messages
2023-04-04 11:24:45 replaying message 642 mpMlistRowsAsync


Server log:
2023-04-04 11:22:08 (1) trying to use slot 4242882 which is in mode duringlogin for not allowed work: mpGetUserSIPData
2023-04-04 11:22:08 (1) SendDataSV(3,32,24,67,5,---,smNewReply,1)
2023-04-04 11:22:08 (1) receive message: mpReloadLangState packed size 63
2023-04-04 11:22:08 (1) trying to use slot 4242882 which is in mode duringlogin for not allowed work: mpReloadLangState
2023-04-04 11:22:08 (1) receive message: mpReRegisterAtSV packed size 60

2023-04-04 11:22:08 (1) Incoming Re-Connection from: 86.100.150.199:51894
2023-04-04 11:22:08 (1) SendDataSV(3,42,24,67,7,---,smNewReply,1)
2023-04-04 11:22:08 (1) receive message: mpGetUserSIPData packed size 48
2023-04-04 11:22:08 (1) trying to use slot 4242882 which is in mode duringlogin for not allowed work: mpGetUserSIPData
2023-04-04 11:22:08 (1) SendDataSV(3,32,24,67,8,---,smNewReply,1)
2023-04-04 11:22:08 (1) receive message: mpReloadLangState packed size 63
2023-04-04 11:22:08 (1) trying to use slot 4242882 which is in mode duringlogin for not allowed work: mpReloadLangState
2023-04-04 11:22:08 (1) receive message: mpReRegisterAtSV packed size 60
2023-04-04 11:22:08 (1) Incoming Re-Connection from: 86.100.150.199:51894
2023-04-04 11:22:08 (1) SendDataSV(3,42,24,67,10,---,smNewReply,1)
2023-04-04 11:22:09 (1) receive message: mpGetUserSIPData packed size 49
2023-04-04 11:22:09 (1) trying to use slot 4242882 which is in mode duringlogin for not allowed work: mpGetUserSIPData
2023-04-04 11:22:09 (1) SendDataSV(3,32,24,67,11,---,smNewReply,1)
2023-04-04 11:22:09 (1) receive message: mpReloadLangState packed size 63
2023-04-04 11:22:09 (1) trying to use slot 4242882 which is in mode duringlogin for not allowed work: mpReloadLangState
....same messages repeated here...