Log in to start a topic

C1.Web.Api.Report / Flex report - Error on Azure

Posted by: mary431982 on 23 May 2024, 4:01 am EST

  • mary431982

    Posted 23 May 2024, 4:01 am EST

    Hello, I use C1.Web.Api.Report and I created simple flex report which I show in report viewer. Everything is working in my dev environment (IIS express), but when I publish to Azure (WebApp) I get this error. I suppose it has something to do with DX. Please, can you help?

    Regards, Marija

    {System.Runtime.InteropServices.COMException (0x8876086A): Exception from HRESULT: 0x8876086A at C1.Util.DX.HResult.ThrowException()}

    void C1.Util.DX.HResult.ThrowException()

    void C1.Win.C1Document.Util.C1DXGraphics.C1DXGraphics()

    void C1.Win.C1Document.Util.C1DXExportGraphics.C1DXExportGraphics()

    void C1.Win.C1Document.Util.C1HtmlGraphics.C1HtmlGraphics(System.Xml.XmlWriter doc, C1.Win.C1Document.C1Page page, string imageFolder, bool singleFile)

    void C1.Win.C1Document.Export.HtmlFilterBase.ExportPage(C1.Win.C1Document.C1Page page)

    void C1.Win.C1Document.Export.GraphicsFilter.InternalExport(C1.Win.C1Document.IExecutionContext context)

    void C1.Win.C1Document.Export.ExportFilter.Export(C1.Win.C1Document.IExecutionContext context)

    void C1.Win.FlexReport.C1FlexReport.InternalExport(C1.Win.C1Document.Export.ExportFilter exporter, C1.Win.C1Document.IExecutionContext context)

    void C1.Win.C1Document.C1DocumentSource.Export(C1.Win.C1Document.Export.ExportFilter exportFilter)

    System.IO.Stream C1.Web.Api.Document.Models.Document.Export(C1.Win.C1Document.Export.ExportFilter exportFilter, C1.Web.Api.Document.Models.ExportFilterOptions exportFilterOptions)

    System.IO.Stream C1.Web.Api.Document.DocumentRequestContext<System.__Canon>.Export(C1.Win.C1Document.Export.ExportFilter exportFilter, C1.Web.Api.Document.Models.ExportFilterOptions exportFilterOptions)

    System.Web.Http.IHttpActionResult C1.Web.Api.Report.ReportController.#e2q.#d2q()

    System.Web.Http.IHttpActionResult C1.Web.Api.C1ApiController.ProcessAction(System.Func<System.Web.Http.IHttpActionResult> func)

    System.Threading.Tasks.Task System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.GetExecutor.AnonymousMethod__2(object instance, object methodParameters)

    System.Threading.Tasks.Task System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(System.Web.Http.Controllers.HttpControllerContext controllerContext, System.Collections.Generic.IDictionary<string, object> arguments, System.Threading.CancellationToken cancellationToken)

    System.Threading.Tasks.Task<System.Net.Http.HttpResponseMessage> System.Web.Http.Controllers.ApiControllerActionInvoker.InvokeActionAsyncCore(System.Web.Http.Controllers.HttpActionContext actionContext, System.Threading.CancellationToken cancellationToken)

    System.Threading.Tasks.Task<System.Net.Http.HttpResponseMessage> System.Web.Http.Controllers.ApiControllerActionInvoker.InvokeActionAsync(System.Web.Http.Controllers.HttpActionContext actionContext, System.Threading.CancellationToken cancellationToken)

    System.Threading.Tasks.Task<System.Net.Http.HttpResponseMessage> System.Web.Http.Controllers.ActionFilterResult.ExecuteAsync(System.Threading.CancellationToken cancellationToken)

    System.Threading.Tasks.Task<System.Net.Http.HttpResponseMessage> System.Web.Http.Controllers.ExceptionFilterResult.ExecuteAsync(System.Threading.CancellationToken cancellationToken)

  • brezodejan

    Posted 23 May 2024, 6:48 am EST

    I have the same problem when I update from:

    OriginalFilename : C1.Win.FlexReport.4.dll

    ProductName : C1.Win.FlexReport

    ProductVersion : 4.0.20193.393

    to version:

    ProductVersion : 4.0.20201.416

    I tried the last version for .netFrameow0rk 4.0 from NuGet (C1.Web.Api.Report 4.0.20212.302) and it’s the same problem/error.

    Best Regards,

    Dejan

  • akshay.rajput

    Posted 27 May 2024, 8:18 am EST

    Hi Mary,

    We are investigating on this issue. I will get back to you as soon as I have any updates on the case.

  • brezodejan

    Posted 28 May 2024, 10:06 am EST

    This is urgent!

    We need a hotfix for FlexReport for WinForms. Is there any way to get a hotfix for 2019v3 that includes the resolution for the issue: “Fixed the issue where the ForcePageBreak specified for SubSection of SubReport was ignored,” which was resolved in 2020v1?

    We have a license for every version of your components, but we are stuck. In 2019v3, we have this bug and need it fixed. If we use a newer version (like 2020v1), this bug is fixed, but nothing related to Reports works on Azure (Webpp). We have tried many solutions. We found that we could downgrade to 2018v2, and in that case, we do not have the bug, and everything on Azure works, but new problems arise, leaving us without a choice. We urgently need you to provide us with a hotfix as soon as possible.

    Best regards,

    Dejan Brezo

  • akshay.rajput

    Posted 29 May 2024, 5:44 am EST

    Hi Mary,

    Apologies for the delay in getting back to you. This seems to be a know issue[C1WEB-29534] and we are working on it.

    For now, I would suggest you to use Asp.Net Core instead.

    C1ReportService.zip

  • akshay.rajput

    Posted 29 May 2024, 5:44 am EST

    Hi Dejan,

    For the issue with the C1.Win.FlexReport package I have notified our WinForms Team for this issue and they will get back to you as soon as possible.

    For issues with the WinForms packages I would suggest you to post such issues on the following forum: https://developer.mescius.com/forums/winforms-edition

  • kartik.dua

    Posted 30 May 2024, 12:57 am EST

    Hi Dejan,

    Regarding the issue with using the C1.Win.FlexReport package, we have escalated it to the development team for their insights and will update you as soon as possible.

    [Internal Tracking ID: C1WIN-32212]

    Best Regards,

    Kartik

  • brezodejan

    Posted 30 May 2024, 1:28 am EST

    The most important thing is to provide me with a hotfix for 2019v3 that includes the resolution for the issue: “Fixed the issue where the ForcePageBreak specified for SubSection of SubReport was ignored,” which was resolved in 2020v1.

    We need this as soon as possible. Everything else is not as important at this moment.

    Best regards,

    Dejan Brezo

  • brezodejan

    Posted 30 May 2024, 1:38 am EST - Updated 30 May 2024, 1:42 am EST

    Additionally, is there any way to force a page break from a subreport? Can I achieve this via scripts or by using some other property? I only need to insert a page break before the group header (or some field) in subreport. Any tricks or alternative methods I can use in the meantime?

    Best regards,

    Dejan Brezo

  • kartik.dua

    Posted 31 May 2024, 7:58 am EST

    Hi Dejan,

    We completely understand your urgency regarding this matter and apologize for the inconvenience caused to you. As per our understanding of your description, here is our understanding of your scenario:

    1. The 2018v2 version works on Azure, but it has the “Fixed the issue where the ForcePageBreak specified for SubSection of SubReport was ignored” issue
    2. The 2019v3 version does not work on Azure and it has the “Fixed the issue where the ForcePageBreak specified for SubSection of SubReport was ignored” issue
    3. The 2020v1 version does not work on Azure, but the issue “Fixed the issue where the ForcePageBreak specified for SubSection of SubReport was ignored” is fixed.

    Now, you can want a hotfix for 2019v3 that includes the fix in “Fixed the issue where the ForcePageBreak specified for SubSection of SubReport was ignored”

    Could you please validate the following points?

    Although our policies dictate that all fixes and updates are provided in upcoming releases rather than old releases, we will discuss this with the development team to see if there is any possibility of making an exception.

    Thank you for your patience and understanding.

    Thanks, and Best Regards,

    Kartik

  • brezodejan

    Posted 31 May 2024, 8:22 am EST

    Yes, you understand correctly everything I need. At this moment, that is the only acceptable solution for us. The new version causes issues with other components in our very large projects. Migrating every component to completely new versions will take a long time.

  • brezodejan

    Posted 31 May 2024, 8:41 am EST

    What about this? Is there an alternative solution?

    Best regards

    Dejan Brezo

  • kartik.dua

    Posted 3 June 2024, 8:55 am EST

    Hi Dejan,

    Regarding

    Yes, you understand correctly everything I need. At this moment, that is the only acceptable solution for us. The new version causes issues with other components in our very large projects. Migrating every component to completely new versions will take a long time

    We are getting in touch with the development team to see if there is a possibility to provide a hotfix for the 2019v3 release. We will let you know the updates soon. [Internal Tracking ID: C1WIN-20119]

    Regarding

    Additionally, is there any way to force a page break from a subreport? Can I achieve this via scripts or by using some other property? I only need to insert a page break before the group header (or some field) in subreport. Any tricks or alternative methods I can use in the meantime?

    Unfortunately, we could not find a workaround for this issue by using scripts or some other property. We deeply regret the inconvenience this has caused you.

    Best Regards,

    Kartik

  • kartik.dua

    Posted 25 June 2024, 8:07 am EST

    Hi Dejan,

    Unfortunately, as per the product team, since this is a very old version, it won’t be possible for them to rebuild it with the fix and provide it. We apologize for the inconvenience this may cause, but you will need to upgrade to version 2020v1 to resolve the issue.

    Regarding FlexReport not working on Azure, the development team has informed us that the .NET Framework version of FlexReport is not supported in the Azure Windows environment. They suggest using the .NET 6/8 version of FlexReport, which does support the Azure Windows environment.

    Kind Regards,

    Kartik

  • brezodejan

    Posted 1 July 2024, 11:10 am EST

    I think you may not fully understand my situation. I have one library (project) that I use both on the Azure platform and for Windows Forms projects. I cannot use different libraries for these environments. I have two problems and need one version where both work.

    You can see my explanation of what works and what doesn’t in the versions I have tried in the message above. This is precisely why I believe the only way out of this situation is a hotfix for the appropriate older version. Honestly, as a developer, it seems very strange to me that it is difficult to create a hotfix for any version of such a serious project as yours.

    Best regards

    Dejan Brezo

  • kartik.dua

    Posted 2 July 2024, 8:08 am EST

    Hi Dejan,

    We completely understand your concerns and deeply regret the inconvenience this has caused.

    As you mentioned and as we’ve verified, the 2019v3 version is not supported on Azure. Therefore, we’re unsure why there is hesitation in upgrading to the 2020v1 version from your end. As per our policy, we do not provide hotfixes for such outdated versions. Therefore, we strongly recommend considering an upgrade to at least the 2020v1 version, which resolves the “Fixed the issue where the ForcePageBreak specified for SubSection of SubReport was ignored” issue.

    Furthermore, we advise migrating to the latest .NET 8 version of FlexReport to ensure seamless support in Azure environments. We apologize again for any inconvenience this situation may have caused.

    Kind Regards,

    Kartik

  • brezodejan

    Posted 2 July 2024, 9:25 am EST

    Now I understand the misunderstanding. I did not claim that version 2019v3 does not work on Azure; my issue is when I update to version 2020v1. Version 2019v3 works on the Azure platform, but it has not fixed the “PageBreak” bug. When I switch to 2020v1, the “PageBreak” bug is fixed, but Azure does not work. Therefore, I cannot find an acceptable solution.

    Best regards

    Dejan Brezo

  • kartik.dua

    Posted 3 July 2024, 6:59 am EST

    Hi Dejan,

    We understand your situation and sincerely apologize for the inconvenience this has caused. Unfortunately, as per our policy, we cannot provide hotfixes for such outdated versions. Therefore, the only option is to upgrade to the latest .NET 6/8 version of FlexReport, which offers both a fix for the “PageBreak” issue and support on Azure.

    Thank you for your patience and understanding

    Kind Regards,

    Kartik

  • brezodejan

    Posted 4 July 2024, 9:34 am EST

    I understand your point of view, but you must understand that your solution is not feasible in real-time. To migrate to .NET 6/8, I need to also migrate many other dependent projects. Some of these projects are dependent on other components that cannot yet be converted to .NET 6/8.

    This is a large project that does not rely solely on your libraries.

    Additionally, the migration process itself would take a long time…

    Best regards

    Dejan Brezo

  • kartik.dua

    Posted 5 July 2024, 3:44 am EST

    Hi Dejan,

    We are again getting in touch with the product team regarding your concerns and will get back to you as soon as possible.

    Best Regards,

    Kartik

  • brezodejan

    Posted 26 July 2024, 11:40 am EST

    Is there any information?

    Best regards,

    Dejan Brezo

  • kartik.dua

    Posted 29 July 2024, 1:53 am EST

    Hi Dejan,

    We apologize for the delayed response.

    We did our level best to get a private build for the 2019v3 HF release that includes the fix. However, the product team has expressed concerns about providing older builds. Since 2019, there have been three major releases and multiple hotfixes each year. The version you are using is quite old, with nearly 14-15 releases since then. Each build incorporates various changes, which might cause complications and breaks in older versions on doing any such fix. As a result, the product team won’t be able to provide the fix in this older build, as it would necessitate major build requirements.

    We deeply regret the inconvenience this has caused and hope you understand the constraints from the development team’s perspective. Therefore, we kindly request that you upgrade to the latest .NET 8 version of FlexReport.

    Kind Regards,

    Kartik

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels

  • © 2023 MESCIUS inc. All Rights Reserved.  ·  1.800.858.2739

    All product and company names herein may be trademarks of their respective owners.