Connection terminated abnormally

[former_SQLA_member1694891]

Hi,

We are using the version 17.0.8.4003 of SQLAnywhere and some of our client have these error message :

I. 09/14 13:38:38. Connection terminated abnormally; error code 65
I. 09/14 13:38:38. Disconnected TCPIP client's AppInfo: IP=192.168.1.96;HOST=Ludovic-CESSAC.local;OSUSER=l.cessac;OS='Darwin 17.6.0 x86_64';EXE='/Applications/8sens sybase/8XRM.app/Contents/MacOS/8XRM';PID=0x1bd;THREAD=0xa983c1c0;VERSION=17.0.8.4003;API=CAPI_SQLAPI;TIMEZONEADJUSTMENT=120

I. 09/14 13:2

6:04. Connection terminated abnormally; error code 60
I. 09/14 13:26:04. Disconnected TCPIP client's AppInfo: IP=192.168.1.132;HOST=Yvan-LARA.local;OSUSER=y.lara;OS='Darwin 17.7.0 x86_64';EXE='/Applications/8sens sybase/8XRM.app/Contents/MacOS/8XRM';PID=0x283;THREAD=0xa98561c0;VERSION=17.0.8.4003;API=CAPI_SQLAPI;TIMEZONEADJUSTMENT=120

I search in the documentation for error code 60 or 65, but I find nothing.

So if someone know what does it mean or the cause of the issue.

[former_SQLA_member1694891 · Accepted solution]

I succeeded to reproduce the error 60 and 65. It happen when our application crash under certains circonstances.

Thanks all for your help.

[MarkCulp]

The error messages are telling you that the connection to the client was terminated because of an error that was raised by the OS when the server was doing an operation on the socket (e.g. read). The error code (60 and 65 in this case) is the OS error code.

It looks like your client is running on Mac OS, but Mac OS error codes 60 and 65 are disk related so I am going to presume that your server is not running on a Mac? [Edit: see comments - error codes 60/65 are ETIMEOUT and EHOSTUNREACH!]

For a similar reason I am going to assume that your service is not running on Linux (since these error codes don't make sense in your scenario).

Therefore I am going to presume that your server is running on Windows. The Windows error codes 60 and 65 are network related ("remote adapter not compatible" and "network access denied") - it seems to be a bit strange to be getting these errors after a successful connect ... but you may be having other network issues that is causing these errors as a side effect.

If my analysis is correct, I would check your network adapter hardware and/or system log for network related errors. Your hardware is likely failing intermittently. (but this is just a guess)

[former_SQLA_member1694891]

Thanks for your reply.

Ok so the error code is the OS error code, and unfortunately in this case the server is running on macOS.

[Breck_Carter]

DuckDuckGo says this...

http://krypted.com/lists/comprehensive-list-of-mac-os-x-error-codes/

badMDBErr = -60, /bad master directory block/

fontNotDeclared = -65, /font not declared/

offLinErr = -65, /r/w requested for an off-line drive/

[johnsmirnios]

On OSX, error 60 is ETIMEDOUT (operation timed out) and error 65 is EHOSTUNREACH (no route to host).

[VolkerBarth]

@Breck: Let John Google That For You:)

[Breck_Carter]

@Volker: I seriously doubt John googled anything, since this google search

osx error code 60

gives hits like this

http://fixmacissue.com/fix-error-code-60-on-mac.html What is error code 60, and how does it happen?

which says stuff like this

adMDBErr = -60, /bad master directory block/

which means this: Mac docs suck, or I'm an idiot, so I won't ever try to answer a Mac question again 🙂

[VolkerBarth]

I seriously doubt that, too, because he certainly has the according header files.

But searching for "errno max osx" should give some clues for us non-Mac experts, too:) - as long as "errno" comes to mind. (It did not for me, obviously.)

[MarkCulp]

Well, I did google it and hit the same info that you saw Breck... which is why I wrote what I wrote. I was obviously wrong. (I should have looked at the header files! 🙂 ETIMEOUT and EHOSTUNREACH makes way more sense in this scenario. It still means that the client/server communications are getting network errors.