Forum - connection failed, goto L55:

connection failed, goto L55:

Aldevinas Katkus

9-21-22

Operating system: Windows

I did nothing and a client closed itself with this message in the client's hansa.log:

2022-09-21 16:37:02 AD/THREAD(7) service call: LOOKUP to: 54.195.252.100:443 failed with: communications error
2022-09-21 16:37:02 AD/THREAD(7) *** Cloud Service NCBANNER not found ***
2022-09-21 16:38:48 AD connection failed during call to server
2022-09-21 16:38:48 AD connection failed, goto L55:
2022-09-21 16:38:48 AD connection failed during call to server
2022-09-21 16:38:48 AD connection failed, goto L55:

2022-09-21 16:38:48 AD Close database

Why this happenned?

v. 8.5 2022-08-01 (build 85480132)

9-26-22

Hi,

Thank you for the question!

This might have to do with the server or some firewall between the client and the server dropped the connection. You should look in the server's hansa.log to see if it contains any information at the same times.

Best Regards,
Rasmus

Aldevinas Katkus

9-26-22

Server log does not contain anything interesting:

2022-09-21 16:38:48 (1) receive message: mpRemoteCallNonDest packed size 165
2022-09-21 16:38:48 (1) AD SendDataSV(4,746,24,13,313,---,smNewReply,1)
2022-09-21 16:38:48 (1) receive message: mpRemoteCallNonDest packed size 165
2022-09-21 16:38:48 (1) AD SendDataSV(4,746,24,13,314,---,smNewReply,1)
2022-09-21 16:38:49 (1) receive message: mpDisconnect packed size 39
2022-09-21 16:38:49 (1) AD Logoff @192.168.1.112
2022-09-21 16:38:49 (1) AD Logoff LogoutSlot Slot: 4242828

Christoffer Riska

9-27-22

Goto L55; looks like HAL code.
Maybe a programmer can comment on the error "AD connection failed, goto L55:"

Brittany McGrath

10-19-22

Hi Aldevinas & Christoffer,
Do you still require assistance with this or has it been resolved?
Thank you.

Aldevinas Katkus

10-19-22

Let's say this mistery is solved until the next occurence.

Back to the list

New Message
Open Questions My Questions