Using the Call Stack to Report Business Central Errors

Modified on Sun, Dec 29, 2024 at 5:28 AM

When an error is raised in Business Central, the system will generate a Call Stack to help diagnosis.

The call stack is provided in several places:

On the Preview Posting page
Within the error message in the middle of the page by using the “Share Details” line.
From the Help and Support menu to view the last known error

Once the call stack is displayed, please copy and paste the entire contents to show the entire call stack.

Example call stack.

"Gen. Jnl.-Check Line"(CodeUnit 11).CheckZeroAmount line 10 - Base Application by Microsoft
 "Gen. Jnl.-Check Line"(CodeUnit 11).RunCheck line 51 - Base Application by Microsoft
 "Gen. Jnl.-Post Batch"(CodeUnit 13).CheckLine line 19 - Base Application by Microsoft
 "Gen. Jnl.-Post Batch"(CodeUnit 13).ProcessLines line 48 - Base Application by Microsoft
 "Gen. Jnl.-Post Batch"(CodeUnit 13).Code line 38 - Base Application by Microsoft
 "Gen. Jnl.-Post Batch"(CodeUnit 13).OnRun(Trigger) line 9 - Base Application by Microsoft
 "Gen. Jnl.-Post"(CodeUnit 231).Code line 67 - Base Application by Microsoft
 "Gen. Jnl.-Post"(CodeUnit 231).OnRun(Trigger) line 5 - Base Application by Microsoft
 "Gen. Jnl.-Post"(CodeUnit 231).OnRunPreview line 8 - Base Application by Microsoft
 "Gen. Jnl.-Post Preview"(CodeUnit 19).OnRunPreview(Event) line 2 - Base Application by Microsoft
 "Gen. Jnl.-Post Preview"(CodeUnit 19).RunPreview line 4 - Base Application by Microsoft
 "Gen. Jnl.-Post Preview"(CodeUnit 19).PreviewStart line 17 - Base Application by Microsoft
 "Gen. Jnl.-Post Preview"(CodeUnit 19).Preview line 3 - Base Application by Microsoft
 "Gen. Jnl.-Post"(CodeUnit 231).Preview line 6 - Base Application by Microsoft
 "General Journal"(Page 39)."Preview - OnAction"(Trigger) line 4 - Base Application by Microsoft

Also, please note the application raising the error on the top line. As Business Central allows many extensions to be implemented by Microsoft, Tangicloud as well as other partners and customers, it’s important to identify which company was responsible for the error.

if the error was not raised by Tangicloud or Microsoft, please contact the company in question.

User can also copy the error from the icon marked below. And the user can paste the error and send it to us.

For example, we have an error in the screenprint below, and pasted the call stack below:

If requesting support, please provide the following details to help troubleshooting:

G/L Account No. must be equal to '' in Auto-fill: Code=GENERAL. Current value is '1010'.

Internal session ID:
aa0d47a6-122e-441e-81e8-853f6712d647

Application Insights session ID:
518784b4-b295-4e2f-9fc8-f6f75b46193b

Client activity id:
bfcbb85d-2d4b-4e4b-ba7c-d43570e5543e

Time stamp on error:
2024-04-03T21:35:03.7095300Z

User telemetry id:
61aecf1d-efd3-41ee-8fe5-275fb6303d80

AL call stack:
"tct Purchase Line"(TableExtension 70274110)."No. - OnAfterValidate"(Trigger) line 29 - Tangicloud Fundamentals by Tangicloud Technologies, Inc.

Was this article helpful?