shamrock
8th January 2009, 16:02
Hello,
I am new to Baan and this company that is having issues. If anyone can offer some insight into whether this problem is baan related or network related it would be greatly appreciated.

Clients keep getting disconnect from two branch locations of this company. The message the clients receive in event viewer is this.
___________________________________________________________
Event Type: Error
Event Source: Baan
Event Category: Bw
Event ID: 1000
Date: 1/7/2009
Time: 2:06:56 PM
User: S-1-5-21-861567501-1801674531-1606980848-1184
Computer: TX-PCLEMENT
Description:
Env Baan IV (c:\program files\baan)
Prog BW file sockdata.cpp # 732
Keyword SocketData::send(SOCKET , const char * , int )
Username pclement type S language 2
Process 0x8c8
Lasterror 10054 (An existing connection was forcibly closed by the remote host.)
Errno 0
bdberrno 0
Message 3 : ::send(200, 0x4fec20, 30) returned -1, error=10054
________________________________________________________________

The baan server is getting a lot of this error in the event viewer.
--------------------------------------------------------------------
Event Type: Error
Event Source: Baan
Event Category: Bshell
Event ID: 1000
Date: 1/7/2009
Time: 3:40:42 PM
User: SHAMROCK-INC\ehays
Computer: NOC-BAANAPP
Description:
Env : Bse (C:\baan)
Program : bshell file li_init.c # 410
Keyword : ds_close_server
Username : ehays type:N language:2
Process : 1720
ProcessSet : ehays@NOC-BAANAPP:1720
Lasterror : 0
Errno : 0
BdbErrno : 0
Message : Detected Display Server Termination
--------------------------------------------------------------
If anyone has any ideas please share them.

Thank you

norwim
8th January 2009, 17:44
Hi there,

most obviously the server is terminating the connection.
There is a parameter you can set to influence the servers behaviour when a client is idle for a certain period of time.

Do a search on the board for "idle". You could test this hypothesis by putting
-- -set session_timeout=0
as an option in the GUI - if the problem doesn't occur any more for this user, you found the reason.

good luck and welcome to baan board :-)

Norbert

toolswizard
22nd January 2009, 15:18
Check with the people responsible for the router/modem that connects the remote location to the local. There may be a mandatory connect time limit on the router. I once had remote warehouses that would time out every two hours. We were not able to disable it, but were able to change it to 10 hours to cover a shift.

dave_23
26th January 2009, 09:12
Lasterror 10054 (An existing connection was forcibly closed by the remote



that, to me, looks like there is a firewall between the sites and it is terminating idle connections.

you may be able to disable timeouts on the baan port in the firewall, or you may need to find a way to do a keepalive.

edit: if it was session timeout it would/should say "session timed out" in the log file.
so i think it's more of a hard disconnect.

Dave