In Development
Last Updated: 22 Apr 2024 07:27 by ADMIN
Scheduled for 2024 Q2
I have a problem with the current version in a Linux container using 2024.1.30 and 18.0.24.305 version of reporting. I only get this when I'm attempting to produce multiple reports at the same time.  It's the same issue regardless of whether it's running as a hosted web service or if I'm running as a server based blazor app.

DockerBlazorApp Error: 0 : An error has occurred while rendering the report: System.InvalidOperationException: Operations that change non-concurrent collections must have exclusive access. A concurrent update was performed on this collection and corrupted its state. The collection's state is no longer correct.
   at System.Collections.Generic.Dictionary`2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)
   at System.Collections.Generic.Dictionary`2.set_Item(TKey key, TValue value)
   at Telerik.Drawing.SKIA.Text.FontMapper.LoadPrivateFont(SKTypeface typeface, String familyName)
   at Telerik.Drawing.Skia.Graphics.MeasureTextBlock(String text, Single widthConstraint, Single heightConstraint, StringFormatBase stringFormat, IFont font)
   at Telerik.Drawing.Skia.Graphics.MeasureString(String text, IFont font, SizeF layoutArea, StringFormatBase stringFormat, Int32& charactersFitted, Int32& linesFilled)
   at Telerik.Reporting.Processing.WindowsTextMeasureProvider.MeasureString(IGraphics graphics, String text, GdiFontInfo fontInfo, SizeF layoutArea, StringFormatBase stringFormat, Int32& charactersFitted, Int32& linesFilled)
   at Telerik.Reporting.Processing.MeasureContext.MeasureString(String text, IFont font, SizeF layoutArea, TextFormat textFormat, Int32& charactersFitted, Int32& linesFilled)
   at Telerik.Reporting.Processing.TextRenderer.MeasureText(IMeasureContext context, String text, IFont font, RectangleF layoutRectangle, TextFormat textFormat, Boolean multiline, Int32& charactersFitted)
   at Telerik.Reporting.Processing.TextBoxUtil.MeasureTextContainer(ITextContainer textContainer, RectangleF layoutBounds, IMeasureContext context)
   at Telerik.Reporting.Processing.TextBox.MeasureItem(IMeasureContext context, SizeLU availableClientSize, Boolean canGrow)
   at Telerik.Reporting.Processing.TextBox.MeasureItem(IMeasureContext context, SizeLU availableClientSize)
   at Telerik.Reporting.Processing.TextBox.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
   at Telerik.Reporting.Processing.LayoutElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
   at Telerik.Reporting.Processing.VisualElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
   at Telerik.Reporting.Processing.ProcessingElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
   at Telerik.Reporting.Processing.LayoutElement.Measure(IMeasureContext context, SizeLU availableSize)
   at Telerik.Reporting.Processing.AbsolutePositionLayout.MeasureChildItems(IMeasureContext context, SizeLU availableClientSize)
   at Telerik.Reporting.Processing.AbsolutePositionLayout.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
   at Telerik.Reporting.Processing.ReportSectionBase.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
   at Telerik.Reporting.Processing.PageSection.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
   at Telerik.Reporting.Processing.LayoutElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
   at Telerik.Reporting.Processing.VisualElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
   at Telerik.Reporting.Processing.ProcessingElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
   at Telerik.Reporting.Processing.LayoutElement.Measure(IMeasureContext context, SizeLU availableSize)
   at Telerik.Reporting.Paging.PageCompositionBase.MeasurePageSection(PageSection section)
   at Telerik.Reporting.Paging.PageCompositionBase.ProcessPageSectionsForPaging()
   at Telerik.Reporting.Paging.PageCompositionBase.MoveToNextPageArea()
   at Telerik.Reporting.Paging.PageCompositionBase.NextVerticalPage()
   at Telerik.Reporting.Paging.PageCompositionBase.CreatePages()
   at Telerik.Reporting.Paging.PagerBase.Telerik.Reporting.Paging.IPager.CreatePages(IPageHandler handler, LayoutElement root)
   at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(LayoutElement root, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback, PageSettings pageSettings
In Development
Last Updated: 28 Mar 2024 15:07 by ADMIN
Scheduled for 2024 Q2

When the input data of a pie chart is such that some of the series are insignificant enough not to be drawn on the surface area, a DocumentRenderException with the message "The operation was canceled" is thrown by the Reporting engine.

Enlarging the pie chart or hiding/removing its data point labels clears the error. 

In Development
Last Updated: 31 Jan 2024 11:11 by ADMIN
Scheduled for 2024 Q2

If I use an HTML5-based Report Viewer with the default CONTINUOUS_SCROLL page mode and I start scrolling to the next page, the Get Document Page request is made multiple times for the same page.

If I move to the next page via the toolbar buttons or if I use the SINGLE_PAGE page mode, then problem is not reproduced.

In Development
Last Updated: 31 Jan 2024 11:11 by ADMIN
Scheduled for 2024 Q2
If the password of the SQL user contains the percentage symbol (%) before a number, the last three steps of the SQL Data Source Configuration Wizard cannot be completed.
In Development
Last Updated: 29 Jan 2024 16:22 by ADMIN
Scheduled for 2024 Q2

Hi,

HTML viewer is showing Arabic words correctly while 
PDF Export shows splitted characters.

Correct word :  فاتورة
Wrong word with splitted characters :  ةروتاف

Please find attached screenshots for reference.  The issue is appearing only with Linux container. 

Telerik support ticket (
https://www.telerik.com/account/support-center/view-ticket/1623687) was created and got reply that it is because of libgdiplus library and we were expecting that this issue will be resolved in R2 2023 but it still persists.