{"title":"Troubleshooting report errors","url":"https://jonas-paprotka.de/docs/dev-itpro/developer/devenv-reports-troubleshooting/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-reports-troubleshooting, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-reports-troubleshooting","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Learn about how to troubleshoot Business Central reports","date":"2025-01-28","meta":{"topic":"troubleshooting-general"},"outline":[{"level":1,"title":"Troubleshooting report errors","slug":"troubleshooting-report-errors","at":0,"chars":30861},{"level":2,"title":"Ways a report can fail","slug":"ways-a-report-can-fail","at":259,"chars":579},{"level":2,"title":"Report limits","slug":"report-limits","at":838,"chars":436},{"level":2,"title":"Fonts don't show in the PDF/print","slug":"fonts-dont-show-in-the-pdfprint","at":1274,"chars":338},{"level":2,"title":"Troubleshooting report datasets and layouts","slug":"troubleshooting-report-datasets-and-layouts","at":1612,"chars":1752},{"level":3,"title":"Troubleshooting RDL report layouts","slug":"troubleshooting-rdl-report-layouts","at":1772,"chars":478},{"level":3,"title":"Troubleshooting Excel/Word report layouts","slug":"troubleshooting-excelword-report-layouts","at":2250,"chars":1114},{"level":2,"title":"Troubleshooting report AL code","slug":"troubleshooting-report-al-code","at":3364,"chars":976},{"level":2,"title":"Reporting telemetry","slug":"reporting-telemetry","at":4340,"chars":2837},{"level":2,"title":"Reporting exceptions","slug":"reporting-exceptions","at":7177,"chars":21707},{"level":3,"title":"<a name=Canceled></a>Canceled","slug":"a-namecanceledacanceled","at":11341,"chars":285},{"level":3,"title":"<a name=ConnectionLostException></a>ConnectionLostException","slug":"a-nameconnectionlostexceptionaconnectionlostexception","at":11626,"chars":188},{"level":3,"title":"<a name=DeadSqlConnectionException></a>DeadSqlConnectionException","slug":"a-namedeadsqlconnectionexceptionadeadsqlconnectionexception","at":11814,"chars":194},{"level":3,"title":"<a name=InconsistentReadException></a>InconsistentReadException","slug":"a-nameinconsistentreadexceptionainconsistentreadexception","at":12008,"chars":329},{"level":3,"title":"<a name=IOException></a>IOException","slug":"a-nameioexceptionaioexception","at":12337,"chars":164},{"level":3,"title":"<a name=NavAdministratorMadeChangesException></a>NavAdministratorMadeChangesException","slug":"a-namenavadministratormadechangesexceptionanavadministratormadechangesexception","at":12501,"chars":399},{"level":3,"title":"<a name=NavALException></a>NavALException","slug":"a-namenavalexceptionanavalexception","at":12900,"chars":269},{"level":3,"title":"<a name=NavCompanyPermissionException></a>NavCompanyPermissionException","slug":"a-namenavcompanypermissionexceptionanavcompanypermissionexception","at":13169,"chars":311},{"level":3,"title":"<a name=NavCreateScheduledTasksNotAllowedException></a>NavCreateScheduledTasksNotAllowedException","slug":"a-namenavcreatescheduledtasksnotallowedexceptionanavcreatescheduledtasksnotallowedexception","at":13480,"chars":469},{"level":3,"title":"<a name=NavCSideDataException></a>NavCSideDataException","slug":"a-namenavcsidedataexceptionanavcsidedataexception","at":13949,"chars":306},{"level":3,"title":"<a name=NavCSideDuplicateKeyException></a>NavCSideDuplicateKeyException","slug":"a-namenavcsideduplicatekeyexceptionanavcsideduplicatekeyexception","at":14255,"chars":397},{"level":3,"title":"<a name=NavCSideException></a>NavCSideException","slug":"a-namenavcsideexceptionanavcsideexception","at":14652,"chars":354},{"level":3,"title":"<a name=NavCSideFilterException></a>NavCSideFilterException","slug":"a-namenavcsidefilterexceptionanavcsidefilterexception","at":15006,"chars":1008},{"level":3,"title":"<a name=NavCSideRecordNotFoundException></a>NavCSideRecordNotFoundException","slug":"a-namenavcsiderecordnotfoundexceptionanavcsiderecordnotfoundexception","at":16014,"chars":771},{"level":3,"title":"<a name=NavCSideSQLLockTimeoutException></a>NavCSideSQLLockTimeoutException","slug":"a-namenavcsidesqllocktimeoutexceptionanavcsidesqllocktimeoutexception","at":16785,"chars":476},{"level":3,"title":"<a name=NavCSideSqlTimeoutException></a>NavCSideSqlTimeoutException","slug":"a-namenavcsidesqltimeoutexceptionanavcsidesqltimeoutexception","at":17261,"chars":196},{"level":3,"title":"<a name=NavCSideValidateTableRelationException></a>NavCSideValidateTableRelationException","slug":"a-namenavcsidevalidatetablerelationexceptionanavcsidevalidatetablerelationexception","at":17457,"chars":303},{"level":3,"title":"<a name=NavEntitlementPermissionException></a>NavEntitlementPermissionException","slug":"a-namenaventitlementpermissionexceptionanaventitlementpermissionexception","at":17760,"chars":334},{"level":3,"title":"<a name=NavFilterException></a>NavFilterException","slug":"a-namenavfilterexceptionanavfilterexception","at":18094,"chars":980},{"level":3,"title":"<a name=NavNCLArgumentException></a>NavNCLArgumentException","slug":"a-namenavnclargumentexceptionanavnclargumentexception","at":19074,"chars":281},{"level":3,"title":"<a name=NavNCLCallbackNotAllowedException></a>NavNCLCallbackNotAllowedException","slug":"a-namenavnclcallbacknotallowedexceptionanavnclcallbacknotallowedexception","at":19355,"chars":487},{"level":3,"title":"<a name=NavNCLConversionCastException></a>NavNCLConversionCastException","slug":"a-namenavnclconversioncastexceptionanavnclconversioncastexception","at":19842,"chars":324},{"level":3,"title":"<a name=NavNCLDateInvalidException></a>NavNCLDateInvalidException","slug":"a-namenavncldateinvalidexceptionanavncldateinvalidexception","at":20166,"chars":422},{"level":3,"title":"<a name=NavNCLDebuggerActivityAbortedException></a>NavNCLDebuggerActivityAbortedException","slug":"a-namenavncldebuggeractivityabortedexceptionanavncldebuggeractivityabortedexception","at":20588,"chars":190},{"level":3,"title":"<a name=NavNCLDialogException></a>NavNCLDialogException","slug":"a-namenavncldialogexceptionanavncldialogexception","at":20778,"chars":445},{"level":3,"title":"<a name=NavNCLDocumentServiceException></a>NavNCLDocumentServiceException","slug":"a-namenavncldocumentserviceexceptionanavncldocumentserviceexception","at":21223,"chars":202},{"level":3,"title":"<a name=NavNCLEvaluateException></a>NavNCLEvaluateException","slug":"a-namenavnclevaluateexceptionanavnclevaluateexception","at":21425,"chars":281},{"level":3,"title":"<a name=NavNCLFieldNotFoundException></a>NavNCLFieldNotFoundException","slug":"a-namenavnclfieldnotfoundexceptionanavnclfieldnotfoundexception","at":21706,"chars":503},{"level":3,"title":"<a name=NavNclHttpRequestException></a>NavNclHttpRequestException","slug":"a-namenavnclhttprequestexceptionanavnclhttprequestexception","at":22209,"chars":611},{"level":3,"title":"<a name=NavNCLInvalidPathException></a>NavNCLInvalidPathException","slug":"a-namenavnclinvalidpathexceptionanavnclinvalidpathexception","at":22820,"chars":431},{"level":3,"title":"<a name=NavNCLMissingFileNameException></a>NavNCLMissingFileNameException","slug":"a-namenavnclmissingfilenameexceptionanavnclmissingfilenameexception","at":23251,"chars":374},{"level":3,"title":"<a name=NavNCLRecordNotOpenedException></a>NavNCLRecordNotOpenedException","slug":"a-namenavnclrecordnotopenedexceptionanavnclrecordnotopenedexception","at":23625,"chars":368},{"level":3,"title":"<a name=NavNCLReportDefinitionInvalidException></a>NavNCLReportDefinitionInvalidException","slug":"a-namenavnclreportdefinitioninvalidexceptionanavnclreportdefinitioninvalidexception","at":23993,"chars":305},{"level":3,"title":"<a name=NavNCLReportNoLayoutException></a>NavNCLReportNoLayoutException","slug":"a-namenavnclreportnolayoutexceptionanavnclreportnolayoutexception","at":24298,"chars":469},{"level":3,"title":"<a name=NavNCLReportResultEmptyException></a>NavNCLReportResultEmptyException","slug":"a-namenavnclreportresultemptyexceptionanavnclreportresultemptyexception","at":24767,"chars":460},{"level":3,"title":"<a name=NavNCLStringLengthExceededException></a>NavNCLStringLengthExceededException","slug":"a-namenavnclstringlengthexceededexceptionanavnclstringlengthexceededexception","at":25227,"chars":452},{"level":3,"title":"<a name=NavNCLXmlException></a>NavNCLXmlException","slug":"a-namenavnclxmlexceptionanavnclxmlexception","at":25679,"chars":237},{"level":3,"title":"<a name=NavOfficeDocumentRenderMaxRowsExceededException></a>NavOfficeDocumentRenderMaxRowsExceededException","slug":"a-namenavofficedocumentrendermaxrowsexceededexceptionanavofficedocumentrendermaxrowsexceededexception","at":25916,"chars":589},{"level":3,"title":"<a name=NavPermissionException></a>NavPermissionException","slug":"a-namenavpermissionexceptionanavpermissionexception","at":26505,"chars":356},{"level":3,"title":"<a name=NavReportingServiceException></a>NavReportingServiceException","slug":"a-namenavreportingserviceexceptionanavreportingserviceexception","at":26861,"chars":198},{"level":3,"title":"<a name=NavSqlException></a>NavSqlException","slug":"a-namenavsqlexceptionanavsqlexception","at":27059,"chars":172},{"level":3,"title":"<a name=NavTestFieldException></a>NavTestFieldException","slug":"a-namenavtestfieldexceptionanavtestfieldexception","at":27231,"chars":348},{"level":3,"title":"<a name=OpenXmlPackageException></a>OpenXmlPackageException","slug":"a-nameopenxmlpackageexceptionaopenxmlpackageexception","at":27579,"chars":292},{"level":3,"title":"<a name=OutOfMemoryException></a>OutOfMemoryException","slug":"a-nameoutofmemoryexceptionaoutofmemoryexception","at":27871,"chars":288},{"level":3,"title":"<a name=SqlException></a>SqlException","slug":"a-namesqlexceptionasqlexception","at":28159,"chars":166},{"level":3,"title":"<a name=XmlException></a>XmlException","slug":"a-namexmlexceptionaxmlexception","at":28325,"chars":270},{"level":3,"title":"<a name=XPathException></a>XPathException","slug":"a-namexpathexceptionaxpathexception","at":28595,"chars":289},{"level":2,"title":"Report performance","slug":"report-performance","at":28884,"chars":1864},{"level":2,"title":"Related information","slug":"related-information","at":30748,"chars":113}],"text":"# Troubleshooting report errors\nIf reports fail to generate or take too long time to generate, you might need to investigate why. This article contains strategies for analyzing report telemetry to find possible root cases for such errors or slow performance.\n## Ways a report can fail\nAs described in the devenv-report-object article, a report has code for its dataset, typically a layout used for rendering a document (Excel, Word, or PDF) and a request page. When the report runs, your AL code might call methods on the report object (static or on the report instance) and/or run code in triggers/event subscribers on report events.\nA report in Business Central can fail in either of these phases:\n In the request page\n When generating the report dataset\n When rendering the report with a layout\n In any of the OnAfterDocument triggers\n## Report limits\nThe Business Central platform has built-in limits to protect the stability of the system from a single report consuming too many resources. Examples of limits are:\n The maximum number of rows that can be processed in a report.\n The maximum number of documents that can be merged in a report using a Word layout.\n The maximum execution time that it can take to generate a report.\nSee devenv-report-object#report-limits.\n## Fonts don't show in the PDF/print\nIf a report renders correctly with fonts in an on-premises environment or a local sandbox but renders without the font in Business Central online, the layout might use an unsupported font.\nSee Available Fonts in Business Central online</ui-fonts?toc=/dynamics365/business-central/dev-itpro/toc.json>.\n## Troubleshooting report datasets and layouts\nIf a report layout isn't working as expected, you might need to investigate whether the issue is in the dataset.\n### Troubleshooting RDL report layouts\nWhen you're developing and debugging an RDL report layout, it can be useful to get a copy of the report dataset in the XML format used by the RDL engine.\n> TIP\n> From the Business Central client, you can export report results as raw data to an XML file. Use the file to help validate that the report returns the expected data. To export a report dataset to XML, run the report and select the Send to > XML (data only) on the request page.\n### Troubleshooting Excel/Word report layouts\nWhen you're developing and debugging an Excel/Word report layout, it can be useful to get a copy of the report dataset in Excel to see the actual data values in there.\n> TIP\n> From the Business Central client, you can export report results as raw data to a Microsoft Excel file. The file contains all columns of the dataset, but without the layout applied. Use the file to help validate that the report returns the expected data, and to ensure that the report layout controls match the dataset value types. To export a report dataset to Excel, run the report and select the Send to > Microsoft Excel Document (data only) on the request page. See /ui-work-report#send-to-excel.\nIf the user sees this error message when running a report with a Word layout: `You cannot run the report because the {0} layout contains section breaks that conflict with the sections in the report. Remove the section breaks from the report layout, and then run the report.` then see this section to learn more: devenv-using-word-to-author-your-report-layout#using-sections-in-a-word-layout\n## Troubleshooting report AL code\nWhen you're looking at the AL stacktrace from a report error message, it might not be obvious in which of these components the error was triggered. This is especially true for code failing in event subscribers on report events.\nYou can troubleshoot report errors using a debugger or with telemetry:\n If the error occurs when running AL code, the most effective way to troubleshoot might be to attach a debugger.\n If the error occurs in the Business Central platform or if you want to investigate an error that was reported by a user a few days ago, the most effective way to troubleshoot the report error is using telemetry. Report telemetry has information not available in the AL stacktrace, namely the Business Central server exception that triggered the error.\nIn the paragraphs that follow, you can read more about report error telemetry and how to use that to identify the cause and possible solutions or mitigations for report errors.\n## Reporting telemetry\nReport telemetry gathers data about which reports are run on the environment. It provides information about whether the report succeeded, failed, or was canceled. For each report, it tells you how long it ran, how many SQL statements it executed, and how many rows it consumed.\nYou use this data to gather statistics on report usage, find failures in reports, or to help identify slow-running reports.\nWhen you run a report, either from the UI, in a background session, or from a web service call, it might fail. The failure can either be in the AL code of the report or in the layout. When a report fails to generate, you get an RT0006 event in telemetry and the result column in the customDimensions includes the title of the exception thrown by the service or the AL code.\nThis KQL code can help you get started analyzing report failures:\n```kql\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where operation_Name == \"Failed report generation\" // Note that in a later version of the schema, this field will not be used\n  or customDimensions.eventId == 'RT0006'            // introduced in version 16.1\n| where customDimensions.result <> \"Success\"\n| project timestamp\n// in which environment/company did it happen\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n// in which extension/app\n, extensionId = customDimensions.extensionId\n, extensionName = customDimensions.extensionName\n, extensionVersion = customDimensions.extensionVersion\n, extensionPublisher = customDimensions.extensionPublisher\n// in which object\n, alObjectId = customDimensions.alObjectId\n, alObjectName = customDimensions.alObjectName\n, alObjectType = customDimensions.alObjectType\n// what did the user do\n, documentFormat = customDimensions.documentFormat   // documentFormat dimension was added in version 20.0\n, LayoutAppId = customDimensions.layoutAppId         // layoutAppId was added in version 20.0\n, LayoutName = customDimensions.layoutName           // layoutName dimension was added in version 20.0\n, LayoutType = customDimensions.layoutType           // layoutType dimension was added in version 20.0\n, reportAction = customDimensions.reportAction       // reportAction dimension was added in version 20.0\n, reportingEngine = customDimensions.reportingEngine // reportingEngine dimension was added in version 17.3\n// which user ran the report\n, usertelemetryId = case(\n  toint( substring(customDimensions.componentVersion,0,2)) >= 20, user_Id // usertelemetryId was added to the platform in version 20.0\n, 'N/A'\n)\n// what happened\n, alStackTrace = customDimensions.alStackTrace\n, failureReason = customDimensions.result\n```\nSee ../administration/telemetry-reports-trace.\n## Reporting exceptions\nIn the following table, we list some common report exceptions thrown by the Business Central server and suggestions to how to fix them.\nThe different exceptions in the table are grouped by the following severities:\n Error (this severity is likely an error in the report or the code around the report invocation)\n TransientError (this severity was likely due to a transient issue in the infrastructure running Business Central and can likely be resolved by a retry)\n Warning (this severity is likely not an error in the report. The issue can likely be resolved by fixing something in the environment, such as changing the permissions for a user/role)\nException|Severity|Explanation\nCanceled|Warning|Read more<#Canceled>\nConnectionLostException|TransientError|Read more<#ConnectionLostException>\nDeadSqlConnectionException|TransientError|Read more<#DeadSqlConnectionException>\nInconsistentReadException|Warning|Read more<#InconsistentReadException>\nIOException|TransientError|Read more<#IOException>\nNavAdministratorMadeChangesException|Error|Read more<#NavAdministratorMadeChangesException>\nNavALException|Error|Read more<#NavALException>\nNavCompanyPermissionException|Warning|Read more<#NavCompanyPermissionException>\nNavCreateScheduledTasksNotAllowedException|Error|Read more<#NavCreateScheduledTasksNotAllowedException>\nNavCSideDataException|Error|Read more<#NavCSideDataException>\nNavCSideDuplicateKeyException|Error|Read more<#NavCSideDuplicateKeyException>\nNavCSideException|Error|Read more<#NavCSideException>\nNavCSideFilterException|Error/Warning|Read more<#NavCSideFilterException>\nNavCSideRecordNotFoundException|Error|Read more<#NavCSideRecordNotFoundException>\nNavCSideSQLLockTimeoutException|Warning|Read more<#NavCSideSQLLockTimeoutException>\nNavCSideSqlTimeoutException|TransientError|Read more<#NavCSideSqlTimeoutException>\nNavCSideValidateTableRelationException|Error|Read more<#NavCSideValidateTableRelationException>\nNavEntitlementPermissionException|Warning|Read more<#NavEntitlementPermissionException>\nNavFilterException|Error/Warning|Read more<#NavFilterException>\nNavNCLArgumentException|Error|Read more<#NavNCLArgumentException>\nNavNCLCallbackNotAllowedException|Error|Read more<#NavNCLCallbackNotAllowedException>\nNavNCLConversionCastException|Error|Read more<#NavNCLConversionCastException>\nNavNCLDateInvalidException|Error|Read more<#NavNCLDateInvalidException>\nNavNCLDebuggerActivityAbortedException|Warning|Read more<#NavNCLDebuggerActivityAbortedException>\nNavNCLDialogException|Error|Read more<#NavNCLDialogException>\nNavNCLDocumentServiceException|TransientError|Read more<#NavNCLDocumentServiceException>\nNavNCLEvaluateException|Error|Read more<#NavNCLEvaluateException>\nNavNCLFieldNotFoundException|Error|Read more<#NavNCLFieldNotFoundException>\nNavNclHttpRequestException|Error|Read more<#NavNclHttpRequestException>\nNavNCLInvalidPathException|Error|Read more<#NavNCLInvalidPathException>\nNavNCLMissingFileNameException|Error|Read more<#NavNCLMissingFileNameException>\nNavNCLRecordNotOpenedException|Error|Read more<#NavNCLRecordNotOpenedException>\nNavNCLReportDefinitionInvalidException|Error|Read more<#NavNCLReportDefinitionInvalidException>\nNavNCLReportNoLayoutException|Error|Read more<#NavNCLReportNoLayoutException>\nNavNCLReportResultEmptyException|Warning|Read more<#NavNCLReportResultEmptyException>\nNavNCLStringLengthExceededException|Error|Read more<#NavNCLStringLengthExceededException>\nNavNCLXmlException|Error|Read more<#NavNCLXmlException>\nNavOfficeDocumentRenderMaxRowsExceededException|Error|Read more<#NavOfficeDocumentRenderMaxRowsExceededException>\nNavPermissionException|Warning|Read more<#NavPermissionException>\nNavReportingServiceException|TransientError|Read more<#NavReportingServiceException>\nNavSqlException|Error|Read more<#NavSqlException>\nNavTestFieldException|Warning|Read more<#NavTestFieldException>\nOpenXmlPackageException|Error|Read more<#OpenXmlPackageException>\nOutOfMemoryException|Error|Read more<#OutOfMemoryException>\nSqlException|TransientError|Read more<#SqlException>\nXmlException|Error|Read more<#XmlException>\nXPathException|Error|Read more<#XPathException>\n### <a name=Canceled></a>Canceled\nThe report was cancelled either by the user or by the platform.\nSuggested solution<br>\nThis is not an error per se, but if you do not see any successful renderings of the report, you might have a bug in the AL code that generates the dataset.<br><br>\n### <a name=ConnectionLostException></a>ConnectionLostException\nThis is a transient error in the Business Central service.\nSuggested solution<br>\nAsk the user to re-run the report<br><br>\n### <a name=DeadSqlConnectionException></a>DeadSqlConnectionException\nThis is a transient error in the Business Central service.\nSuggested solution<br>\nAsk the user to re-run the report<br><br>\n### <a name=InconsistentReadException></a>InconsistentReadException\nReports read data with UNCOMMITTED level. For this instance of the report, there was a conflict where data was modified by another session while reading the data in the session running the report\nSuggested solution<br>\nAsk the user to re-run the report<br><br>\n### <a name=IOException></a>IOException\nThis is a transient error in the Business Central service.\nSuggested solution<br>\nAsk the user to re-run the report<br><br>\n### <a name=NavAdministratorMadeChangesException></a>NavAdministratorMadeChangesException\nThe NavAdministratorMadeChangesException error typically occurs when an administrator has installed or updated an extension that have impact on the report (directly or via dependencies).\nSuggested solution<br>\nAsk the user to re-run the report. Also, avoid installing extensions during working hours.<br><br>\n### <a name=NavALException></a>NavALException\nThis typically happens if there is an error in the AL code generating the report dataset, not in the report layout\nSuggested solution<br>\nYou need a developer to debug the report code or the code running the report<br><br>\n### <a name=NavCompanyPermissionException></a>NavCompanyPermissionException\nThe user running the report did not have access to the company.\nSuggested solution<br>\nThis is not an error in the report, but you might want to look into which users experience this and sort out the permission issue for them.<br><br>\n### <a name=NavCreateScheduledTasksNotAllowedException></a>NavCreateScheduledTasksNotAllowedException\nThe report code is trying to start a background session, which is not allowed.\nSuggested solution<br>\nThis is usually due to the executing user not having sufficient rights to execute tasks.\nIt can be due to the report being executed by\n A delegated admin,\n An application which does not have API access,\n A guest user without sufficient system entitlements.<br><br>\n### <a name=NavCSideDataException></a>NavCSideDataException\nLegacy error related to invalid data in the current context\nSuggested solution<br>\nYou need a developer to debug the report or the code running the report. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavCSideDuplicateKeyException></a>NavCSideDuplicateKeyException\nThe report code is trying to insert data into a table and there is already data there with the supplied key (either primary or unique)\nSuggested solution<br>\nYou need a developer to debug the report or the code running the report. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavCSideException></a>NavCSideException\nThere is an error in the report code (likely in the code generating the dataset) or in the code running the report.\nSuggested solution<br>\nYou need a developer to debug the report or the code running the report. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavCSideFilterException></a>NavCSideFilterException\nThe NavCSideFilterException error typically occurs when there's an issue with a filter in a report, either when generating the dataset or when a user provides data in a request page. This could be due to a variety of reasons, such as an incorrect filter value, a problem with the filter syntax, or a data type mismatch.\nSuggested solution<br>\nHere are some potential solutions:<br><br>Check the filter values (with the user): Make sure the filter values being used in the report are correct and valid.<br>Check the filter syntax: Ensure that the filter syntax is correct in the report dataset generation code. This includes the use of filter tokens, such as .. for ranges and | for alternatives.<br>Check for data type mismatches: Make sure that the data type of the filter value matches the data type of the field being filtered.<br><br>If the report is run in the background or from a web service call, then this is not a user error.<br><br>\n### <a name=NavCSideRecordNotFoundException></a>NavCSideRecordNotFoundException\nThe NavCSideRecordNotFoundException error typically occurs when the server tries to access a record that doesn't exist. This can happen in a report if the report is trying to access data from a table, but the specific record it's looking for doesn't exist in that table, or if the user is not allowed to access that record.\nSuggested solution<br>\nHere are some potential solutions:<br> Check the data: Make sure the data the report is trying to access actually exists in the database.<br> Check the report code: There might be an issue with how the report is trying to access the data. You might need to modify the report code to correctly handle cases where a record doesn't exist.<br><br>\n### <a name=NavCSideSQLLockTimeoutException></a>NavCSideSQLLockTimeoutException\nThe report code tried to get a lock on data, but another process had a lock on the same data. After 30 seconds, the report process had to timeout and give up getting a lock on the data.\nSuggested solution<br>\nThe user should retry running the report. If the issue persists, then the administrator might need to look into telemetry for lock timeouts to find which process is locking data.<br><br>\n### <a name=NavCSideSqlTimeoutException></a>NavCSideSqlTimeoutException\nThis is a transient error in the Business Central service.\nSuggested solution<br>\nAsk the user to re-run the report<br><br>\n### <a name=NavCSideValidateTableRelationException></a>NavCSideValidateTableRelationException\nA field table relation cannot be validated\nSuggested solution<br>\nMissing data in the related table or incorrect data in the current field that does not match the required fields in the related table.<br><br>\n### <a name=NavEntitlementPermissionException></a>NavEntitlementPermissionException\nThe user running the report has a license that does not allow running the report.\nSuggested solution<br>\nThis is not an error in the report, but you might want to look into which users experience this and sort out the license issue for them.<br><br>\n### <a name=NavFilterException></a>NavFilterException\nThe NavFilterException error typically occurs when there's an issue with a filter in a report, either when generating the dataset or when a user provides data in a request page. This could be due to a variety of reasons, such as an incorrect filter value, a problem with the filter syntax, or a data type mismatch.\nSuggested solution<br>\nHere are some potential solutions:\n Check the filter values (with the user): Make sure the filter values being used in the report are correct and valid.\n Check the filter syntax: Ensure that the filter syntax is correct in the report dataset generation code. This includes the use of filter tokens, such as .. for ranges and | for alternatives.\n Check for data type mismatches: Make sure that the data type of the filter value matches the data type of the field being filtered.\n<br>If the report is run in the background or from a web service call, then this is not a user error.<br><br>\n### <a name=NavNCLArgumentException></a>NavNCLArgumentException\nInvalid parameter has been passed on to an AL runtime method.\nSuggested solution<br>\nYou need a developer to debug the report. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavNCLCallbackNotAllowedException></a>NavNCLCallbackNotAllowedException\nThe report is running in the background or triggered from a webservice and the code is trying to open UI from any function in AL that requires the client , for example confirmation, a file upload, opening a page etc.\nSuggested solution<br>\nYou need a developer to debug the report or the code running the report. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavNCLConversionCastException></a>NavNCLConversionCastException\nThere is an error in the report AL code (not the layout) related to invalid type conversion.\nSuggested solution<br>\nYou need a developer to debug the report. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavNCLDateInvalidException></a>NavNCLDateInvalidException\nA string cannot be converted to a date type.\nSuggested solution<br>\nIncorrect string format that cannot be converted to a date in the current regional setup. Inspect the data behind the report or change the regional settings to fit report requirements. In BC 23 and later, try to set the format region in the request page and rerun the report.<br><br>\n### <a name=NavNCLDebuggerActivityAbortedException></a>NavNCLDebuggerActivityAbortedException\nThis happens when a developer is debugging a report\nSuggested solution<br>\nNot an error<br><br>\n### <a name=NavNCLDialogException></a>NavNCLDialogException\nThe NavNCLDialogException error happens when an error function has been called in the report.\nSuggested solution<br>\nThe error messages will in most cases provide the necessary information to mitigate the problem. If not, you need a developer to debug the report or the code running the report. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavNCLDocumentServiceException></a>NavNCLDocumentServiceException\nThis is a transient error in the Business Central service.\nSuggested solution<br>\nAsk the user to re-run the report<br><br>\n### <a name=NavNCLEvaluateException></a>NavNCLEvaluateException\nUnabler to evaluate the input string to the desired database.\nSuggested solution<br>\nYou need a developer to debug the report. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavNCLFieldNotFoundException></a>NavNCLFieldNotFoundException\nThe NavNCLFieldNotFoundException typically occurs when a field that the report is trying to access is not found. This is typically due to outdated field refs in AL code that try to address a table field using an index that is no longer valid.\nSuggested solution<br>\nYou need a developer to debug the report or the code running the report. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavNclHttpRequestException></a>NavNclHttpRequestException\nThe NavNclHttpRequestException error in AL code for Microsoft Dynamics 365 Business Central typically occurs when there's an issue with the HTTP request made to a web service. This could be due to a variety of reasons such as network issues, incorrect endpoint URL, or issues with the request parameters.\nSuggested solution<br>\nAn error in (third-party) extension code being called from report triggers. You need a developer to debug the report code. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavNCLInvalidPathException></a>NavNCLInvalidPathException\nThis typically happens in processing-only reports. Some typical scenarios are code that tries to read or write a file using an invalid path (OnPrem) or a path outside of the users allowed temp area (SaaS).\nSuggested solution<br>\nYou need a developer to debug the report. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavNCLMissingFileNameException></a>NavNCLMissingFileNameException\nThis typically happens in processing-only reports\nSuggested solution<br>\nFirst check the parameters on the request page. Could be a missing file name in field that does not have a proper field validation. You might need a developer to debug the report code or the code running the report<br><br>\n### <a name=NavNCLRecordNotOpenedException></a>NavNCLRecordNotOpenedException\nAL runtime error caused by programming error when the code does not open a record reference before use.\nSuggested solution<br>\nYou need a developer to debug the report or the code running the report. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavNCLReportDefinitionInvalidException></a>NavNCLReportDefinitionInvalidException\nInvalid RDLC layout which need a review by a developer.\nSuggested solution<br>\nYou need a developer to debug the report. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavNCLReportNoLayoutException></a>NavNCLReportNoLayoutException\nThere is an error in the report code or layout setup in the application if the selected has been set to a user defined layout or the layout selection points to an uninstalled layout from a report extension.\nSuggested solution<br>\nYou need a developer to debug the report or the code running the report. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavNCLReportResultEmptyException></a>NavNCLReportResultEmptyException\nWhen the report dataset does not have any data, we show a dialog to the user.\nSuggested solution<br>\nThis is not an error per se, but if you do not see any successful renderings of the report, you might have a bug in the AL code that generates the dataset. The typical root cause for this error is incorrect filters on the request page that result in an empty data set.<br><br>\n### <a name=NavNCLStringLengthExceededException></a>NavNCLStringLengthExceededException\nThis can happen when you assign an unlimited string to a string with a fixed length. The error will occur if the source string is longer than the allocated length in the target.\nSuggested solution<br>\nYou need a developer to debug the report or the code running the report. If the report was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=NavNCLXmlException></a>NavNCLXmlException\nThis typically happens if there is an error in the XML of the request page\nSuggested solution<br>\nYou need a developer to debug the report code or the code running the report<br><br>\n### <a name=NavOfficeDocumentRenderMaxRowsExceededException></a>NavOfficeDocumentRenderMaxRowsExceededException\nThe Business Central service cannot process the report because the dataset contains too many rows.\nSuggested solution<br>\nUpdate the filter on the report to limit the number of rows. The maximum number of rows can be controlled in the Report Limits page or in the advanced tab on the request page. Notice that setting the limit too high, can put the node at risk due to high memory usage (can result in Out-of-memory exception) and constrain other users on the system.<br><br>\n### <a name=NavPermissionException></a>NavPermissionException\nThe user running the report was missing permissions to run the report or to some of the data needed in the report dataset.\nSuggested solution<br>\nThis is not an error in the report, but you might want to look into which users experience this and sort out the permission issue for them.<br><br>\n### <a name=NavReportingServiceException></a>NavReportingServiceException\nThis is a transient error in the Business Central service.\nSuggested solution<br>\nAsk the user to re-run the report<br><br>\n### <a name=NavSqlException></a>NavSqlException\nThis is a transient error in the Business Central service.\nSuggested solution<br>\nAsk the user to re-run the report<br><br>\n### <a name=NavTestFieldException></a>NavTestFieldException\nThis happens when the TESTFIELD function test a value in a field and it does not match the expected value.\nSuggested solution<br>\nThis is not an error per se, but if you do not see any successful renderings of the report, you might have a bug in the AL code for the request page.<br><br>\n### <a name=OpenXmlPackageException></a>OpenXmlPackageException\nThis typically happens if there is an error in a Word layout\nSuggested solution<br>\nYou need a developer to debug the Word report layout. If the layout was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=OutOfMemoryException></a>OutOfMemoryException\nThe Business Central service cannot process the report because the memory needed to do that exceeds the limit on the platform\nSuggested solution<br>\nSet a filter in the report to limit the number of rows in the data set. <br><br>\n### <a name=SqlException></a>SqlException\nThis is a transient error in the Business Central service.\nSuggested solution<br>\nAsk the user to re-run the report<br><br>\n### <a name=XmlException></a>XmlException\nThis typically happens if there is an error in a Word layout\nSuggested solution<br>\nYou need a developer to debug the Word report layout. If the layout was supplied by Microsoft or an ISV, then create a support request.<br><br>\n### <a name=XPathException></a>XPathException\nThis typically happens if there is an error in the XML of the request page or if the xml data set for Word based reports is corrupted.\nSuggested solution<br>\nYou need a developer to debug the report code or the code running the report<br><br>\n## Report performance\nReports generally fall into two categories. They can be specific to a single instance of an entity, like an invoice. Or, they can be of a more analytical nature that joins data from multiple instances of multiple entities. Typically, performance issues in reports lie in the latter category. The following articles contain advice about implementing faster reports:\n Use Read Scale-Out to read data from a read-only copy of the database, see Using Read Scale-Out for Better Performance<../administration/database-read-scale-out-overview> for more information.\n Use Partial Records to reduce the data loaded from the database, see Using Partial Records<devenv-partial-records> for more information.\n Use AL queries to optimize the way data is read from the database, see Queries in Business Central<devenv-query-overview> for more information.\n Compared to Word layouts, RDL layouts can result in slower performance with document reports, especially for actions related to the user interface (like sending emails). See Creating an RDL Layout Report<devenv-howto-rdl-report-layout>.\n Can you run the report in the background? It will not make it run faster, but the user might feel this way (as they are not blocked in the UI while waiting on the report to finish). See /ui-work-report#ScheduleReport.md.\n> TIP\n> From the Business Central client, you can export report results as raw data to a Microsoft Excel file. The file contains all columns of the dataset, but without the layout applied. Use the file to help validate that the report returns the expected data, and to ensure that the report layout controls match the dataset value types. To export a report dataset to Excel, run the report and select the Send to > Microsoft Excel Document (data only) on the request page. See /ui-work-report#send-to-excel.\nSee devenv-report-performance.\n## Related information\ndevenv-testing-reports\ndevenv-report-performance\n../administration/telemetry-reports-trace"}