ReportViewer 16.2.41 Does Not Work After Publish My Solution

[Sergio Sant'Anna]

Hi,

I recently upgraded my Asp.Net Core 2.1 solution that worked perfectly in version 16.1.37, to version 16.2.41 and now when I open my reports, the ReportViewer control does not display the report and does not indicate any errors in the browser console.

This problem only occurs when my solution is published on the customer's computer, regardless of whether I publish with Framework-dependent / Portable or Self Contained modes.

Strangely, the problem does not occur on my development computer when I run the solution in Debug, Release or even in the publishing folder (with Framework-dependent / Portable), with the command line: "dotnet mysolution.dll".

The only way to reproduce the problem in my development environment is to do a Self Contained Publish.

I suspect that some dependency is not being solved during the assembly of the solution.

These are the dependencies I use in my package.json:

...

"dependencies": {

    "@types/ej.web.all": "^16.2.0",

    "@types/jquery": "3.3.4",

    "@types/jsrender": "0.0.29",

    "syncfusion-javascript": "16.2.41",

    "syncfusion-ej-global-all": "16.2.41",

    "bootstrap": "3.3.7",

    "jquery": "3.3.1",

    "jquery-validation": "1.17.0",

    "jquery-validation-unobtrusive": "3.2.10",

    "jsrender": "0.9.90"

  },

...

This is a screenshot of what is displayed:

But if I force a browser refresh F5 sometimes, then I get a 502 error, as screenshot below:

..and sometimes this message:

I also found the following exception in my logs:

Unhandled Exception: System.ArgumentNullException: Value cannot be null.

   at System.Threading.Monitor.ReliableEnter(Object obj, Boolean& lockTaken)

   at SkiaSharp.SKObject.Dispose(Boolean disposing)

   at SkiaSharp.SKPaint.Dispose(Boolean disposing)

   at SkiaSharp.SKNativeObject.Finalize()

Regards,

Sérgio Sant'Anna

[Lingaraj S]

Hi Sérgio Sant'Anna,

 

Thanks for using our Syncfusion products,

 

In our Volume 2,2018 release, we have included support with Reportviewer to increase the size of the text box report item based on content by using third party SkiaSharp library to measure the text size. Based on the below article, SkiaSharp may causes the issue with self-contained deployments

 

https://stackoverflow.com/questions/47436789/understanding-net-core-and-mono

(You can still run into problems if a used DLL references a native-dll (that it provides as embedded resource), but does not provide the necessary C-Runtime-libraries (e.g. when the native-dll/.so is dynamically linked - such as in SkiaSharp).

 

As of now, you can avoid this issue by changing Cangrow property as false for Textbox report item. We will check the possible cases and address this issue in our Volume 2,2018 Service Pack release and can be expected in end of this month.

 

Regards,

Lingaraj S.

[Sergio Sant'Anna]

Hello Lingaraj ,

Thank you for information. 

With the information about SkiaSharp I was able to determine the problem and found the solution.

My suspicion that some dependence was not being resolved was correct.

Although SkiaSharp does not indicate any dependencies, on the page for this product there is a note about the need for the Microsoft Visual C ++ 2015 Redistributable package.

I checked that the production computer had this package, but only the x86 version. So I installed the Microsoft Visual C ++ 2017 Redistributable package (x86 and x64), which also exists on my development computer, and now my reports are displayed as expected even with CanGrow = true.

There is still the problem of the incorrect rendering of CanGrow, but this subject I am already treating in another topic of this forum.

Regards,

Sérgio Sant'Anna

[Mageshyadav M]

Hi Sergio, 

Thanks for the update. We are happy to hear that “SkiaSharp dependent library issue” is resolved at your end. 

For CanGrow issue, we will follow-up in incident created under your account. Please log on to our support website to check for further updates. 

https://www.syncfusion.com/account/login?ReturnUrl=%2fsupport%2fdirecttrac%2fincidents 

Regards, 

Mageshyadav M