Hi,
Did someone find the root cause of this issue ?
We are also facing identical errors, when importing TRACE files originated on an AX2009 AOS into the latest Traceparser.
From some AOS servers we are still able to import the files, but from others we get the arithmetic overflow.
This seems to have started about 2 years ago. More and more of our customers are facing this issue. Especially on newly (re)installed servers.
We couldn't link it to any specific AX build, OS build .
Remark : old trace files can still be imported. Only the newer ones give an issue.
Analyzing the data in the SQL database, I found that the data in
Table : Tracelines
Columns : inclusivedurationnano , databasedurationnano , binddurationnano, exclusivedurationnano , prepdurationnano , rowfetchdurationnano
are out of range, and causes the Traceparser afterwards to fail.
It seems to us the problem occurs when the tracefile is created by the AOS.
And I suspect some recent update of a system component ( like odbc-driver , .... ) could be the root cause.
Is there a tool or app to view the content of these .trc files directly ?
rgds
P Louis
