AX2012 client crash

(0) Share

Report

Posted on by JPROBBE

Hi,

We experience a problem with our current AX 2012 set-up. AOS are behind a firewall. Default TCP timeout is set to 3600 seconds. If the client is left untouched forat least this amount of time, when you try to use again AX, it will crashes, whatever you call.

After some investigation, it seems AX client fails to keep alive the TCP connection, hence the firewall drops the connection from its session table.

I think we have here two very bad coding practices :

1/ Leaving a socket open without activity

2/ Crashing without a clear error message (only says AX32.exe has crashed, giving faulting dll and module)

Anyone experienced the same behavior ? We are using 2012 R2.

Setting 14400 sec timeout on the firewall is what we did as a workaround, satisfying for users but not for techies...

Will appreciate your feedback.

*This post is locked for comments

I have the same question (0)

All responses (2)

Answers (0)

Sort by

JPROBBE 60 on at

Like (0)

Report
Copy link

Link copied!

Hi,

My concern is between the client and AOS. What I understand is that the settings you're pointed me at are regarding DB time at the AOS level.

Was this reply helpful? Yes No
dolee 11,279 on at

Like (0)

Report
Copy link

Link copied!

Hi,

There is a "Automatic shutdown" option per user (in mins) that can be set in AX. You can set AX client to automatically shutdown before the TCP timeout value to avoid the error.

Was this reply helpful? Yes No