Hi,

We're on Baan IV on NT 4.0 Sp6a, Oracle 8.0.5.
On of our end-user usually encountered disconnection of it's baan client quite frequently. The user is running on win98 OS. Her baan client is B40c.045. Only about 2 users have this problem.
A check on her bw.log indicated the following:-

102-03-12[14:40:51]dcc9643: ******* S T A R T of Log message *******
102-03-12[14:40:51]dcc9643: Log message called from ipc_fdio.c: #92 keyword: IPC
102-03-12[14:40:51]dcc9643: user_type S language 2 user_name dcc9643 tty s
102-03-12[14:40:51]dcc9643: Errno 0 bdb_errno 0
102-03-12[14:40:51]dcc9643: Windows error 317 (The system cannot find message for message number 0x%1

102-03-12[14:40:51]dcc9643: in message file for %2.)
102-03-12[14:40:51]dcc9643: Windows Sockets error 317
102-03-12[14:40:51]dcc9643: Log_mesg: 2 : Connection to server lost: fd_read 14: num_bytes -1 errno 0
102-03-12[14:40:51]dcc9643: ********** E N D of Log message **********

Has anyone encountered a similar situation?
The question is will the updating of porting set will not solve this problem? I doubt it..


Best Regards,
Zaid

Zaid,

First things I would change are BW client version (45 is pretty old!) and client OS (WinNT, W2k)

As Patrick mentioned, BW045 is old and it should be upgraded for those users.
Also, it should work fine with Win98, but probably a few fixes have been delivered for winsocks, so if you are not going to update the OS, at least search in the MS Knowledge Base for patches regarding winsocks (and make sure you use the 32 bits versions of it, I think windows allowed you to use a 16bit and a 32 bit in case of problems, maybe you using the 16 bit?!).