mickbaan
16th June 2002, 14:55
I am running Baan on NT, as well as a VB application on the same server that connects to Baan via CreateObject(...).
I recently installed the latest tools object for ttstpstandard and ttstpapihand, but after installation the Baan connection from VB gives me the following error:
"Windows Sockets error 10053"
"Connection with server broken"

When running the BWclient.exe (BECS) connecting to Baan still works fine.

Does anybody know what has caused this problem or more importantly: how to solve it?

Thank you,
Mick

alejandro
16th June 2002, 23:20
This error is mainly Windows related. Although you have updated your software, have you done it too with the BW client?

If not, try latest BW version too. See solution number: 13743. Latest BW version is 065, for BaaN IV.

Also take a look at solutions numbers:

- 105481, 109800, 109807, 110755 and 150883.

Try to connect from different PC's in order to see if is a local problem like I suggest.

Good Luck.

ksthakur
17th June 2002, 06:42
Hi mickbaan,

During implementation stage, we also faced this problem but were not able to diagnose. Later it was discovered that the problem was neither of BaaN nor of Windows, it was the LAN (switch 3com) which needed to be reconfigured for optimal flow rates etc. etc.

I am sure you also need the same methodology, just give it a try.

all the best.

Regards,

mickbaan
17th June 2002, 12:36
For your information:

I solve the problem above:
it had to do with a new version of ottstpoledaemon that didn't communicate with my (old: 6.01c.04.05) portingset.

I copied my old ottstpoledaemon object over the new one which solved my windows sockets problem.

Regards, Mick