Baan client

blanchap · #1 15th February 2023, 16:54

Hi,

we're experiencing issues with the Baan client. for some unknown reason, users are getting dicsconnected from time to time.
No error message in the logs.
We're using the B40c.102 client and we're starting to think it might be a problem related to all the updates done on windows 10 that might be the cause of that.

Anybody else had the same type of issue?
is there a new version of the client?

Thanks.
PB

mark_h · #2 15th February 2023, 20:07

We have been on B40c.110 for a long time. Not sure if something more current or not. Any network blips have always caused us to get dropped. We used to have multiple sites running out of a regional data center. We always have had some network drops - I can't say for sure we ever had any windows issues related to the client - at least none I can recall.

blanchap · #3 15th February 2023, 21:37

Thanks Mark.
Do you know where i can get that version?

PB

mark_h · #4 15th February 2023, 21:57

The only place I know of is from infor itself.

GaryEd · #5 20th February 2023, 22:28

We are also on version 110. I believe it was the last baan IV version released.

blanchap · #6 23rd February 2023, 19:16

Hi all,

thanks for the info. We're testing the 110 client at the moment.
We'll see if it fix the issue.
Regards.

blanchap · #7 23rd February 2023, 21:15

Hi,

when looking at the bshell log i was able to see the error message.

''Detected Display Server Termination''

anybody knows what this points to?

kbarthelt · #8 24th February 2023, 16:19

Hi. I'm not sure if you are interested in any outside consulting help, but if you are, please feel free to email me at kbarthelt@crossroadsrmc.com.

mark_h · #9 27th February 2023, 15:06

Those remind me of the errors we got when we had network issues. I can't say they are the same, but that is what it reminds me.

OmeLuuk · #10 21st March 2023, 10:49

Somewhat late response but it may give some more insight in what is happening... as you will know the bw client is talking to the bshell process where the actual actions (running sessions) is done. The bshell "talks" to the BW client every once in a while and requires response. When this response is inadequate or not present at all, the connection with the client is terminated with that error.

There are settings you can use when starting the bshell process, that influence this call-response mechanism.
-set DS_MAX_WAIT=value the timeout duration [seconds] in which BW has to respond to the sync message, and override the default of 30 seconds
-set DS_TIMEOUT_DETECT=value the timeout duration [minutes] before the bshell starts sending a sync message to BW

And - but you did not mention your settings - there is also a setting that terminates the idle BW instances:
-set SESSION_TIMEOUT=value the number of minutes the bshell can be inactive before it terminates itself, when the timeout is triggered a message is sent to the UI and the bshells stops

In case you are curious of this Client-Server communication, there is this option in the client:
Right Click the BW icon in the systray, opt for Debugging/Tracing. Choose Output to Console and set the other options
- Show Events
- Show Messages
- Show Socket Notifications