You’re offline. This is a read only version of the page.
There is a short and long answer to this problem.
SHORT ANSWER
This is a Windows GDI core library issue that has been recently resolved in the following September 2020 update for Windows 10 (W10), Windows Server 2016 (WS2016), Windows Server 2019 (WS2019)
WS 2016
Hotfix September 8, 2020—KB4577015 (OS Build 14393.3930) (microsoft.com)
SSU Servicing stack update for Windows 10, version 1607: September 8, 2020 (microsoft.com)
W10 and WS 2019 : 2019
Hotfix August 20, 2020—KB4571748 (OS Build 17763.1432) Preview (microsoft.com)
SSU Servicing stack update for Windows 10, version 1809: August 11, 2020 (microsoft.com)
W10 and WS 2019 : 2020
Hotfix (Preview) September 3, 2020—KB4571744 (OS Build 19041.488) Preview (microsoft.com)
Hotfix https://support.microsoft.com/en-us/help/4571756/windows-10-update-kb4571756
SSU Servicing stack update for Windows 10, version 2004: August 11, 2020 (microsoft.com)
By deploying this update everywhere Report Viewer component is used, the issue will be gone once for all.
LONG ANSWER
This problem was reported to Dynamics 365 Business Central support last winter (December 2019).
This is the path followed to have this routed to the appropriate team for resolution.
Dynamics 365 Business Central support received a couple of requests within this subject and pointed out also to other existing as pure logs with no solution in community posts such as e.g.
https://forum.mibuso.com/discussion/57191/rdlc-invoice-report-cut-numbers
https://github.com/microsoft/AL/issues/5167
Support was able to replicate the issue in February 2020 and escalate to Dynamics 365 Business Central (D365BC) product group.
D365BC product group created a simple proof of concept based on the latest NuGet package Report Viewer (RV) control that showcase the issue lies on the control bits.
D365BC team then handshake the request to SQL Server Reporting Service (SSRS) team that owns the RV product management and bug fix process.
SSRS team dissected the problem and created another proof of concept for Windows core group that demonstrate an issue with the Windows Graphic Driver Interface (GDI) libraries.
Windows core group acknowledge the issue being in the W10, WS2016 and WS2019 libraries.
A fix has been created by windows core group to be distributed through the typical windows update channel between August and September 2020.
For example, the following preview KB article enlisted the hotfix for W10 2004 and 20H2 version
https://support.microsoft.com/en-us/help/4571744/windows-10-update-kb4571744
Since this was just a preview article, the fix has been included officially in the article listed below
https://support.microsoft.com/en-us/help/4571756/windows-10-update-kb4571756
and part of the following Servicing Stack Update (SSU)
Servicing stack update for Windows 10, version 2004: August 11, 2020 (microsoft.com)
Share
Report
All responses (
Answers (
3,010
