Azure web service issue with v18.3.0.x

Hi,
This exception is thrown for all three components I have tried (toast, spinner, listBox) only when the application is published to Azure web service.
When it is being run locally, there is no issues.

Error: System.NullReferenceException: Object reference not set to an instance of an object. at Syncfusion.Blazor.Internal.ResourceManager.IsIE() at Syncfusion.Blazor.Internal.ResourceManager.BuildRenderTree(RenderTreeBuilder builder) at Microsoft.AspNetCore.Components.ComponentBase.<.ctor>b__6_0(RenderTreeBuilder builder) at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment) at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry) at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()

12 Replies 1 reply marked as answer

SU Sridurgha Uthayakumaran Syncfusion Team October 21, 2020 01:21 PM UTC

Hi Mateo, 
 
Thank you for contacting Syncfusion support. 
 
We have analyzed the reported issue by preparing a sample with v18.3.0.40 and we are unable to reproduce the reported issue at our end. For your convenience, we have created the sample and hosted them in azure for your reference. Refer to the below link,  
 
 
For your convenience, we are sharing the publishing method which we follow in our end. Please refer to the below steps. 
  1. We are using vs2019's publish
2.  Settings – Kindly find the settings details which are maintained in our end. 
 
 
 
3. The published folder is shipped to the hosted machine 

After referring the sample if you are still facing the issue, please get back to us with the below details.
 
 
  • Share the complete code use in your end.
  • Share the Edge browser version details
  • Visual studio version
  • .NET SDK version details
  • Publish settings

Please get back to us with the requested details which will help us to resolve the reported issue as early as possible.
 
 
Regards, 
Sridurgha U 


Marked as answer

MA Mateo October 21, 2020 07:11 PM UTC

Hi thank you for the tested solution.

Can you please try host it on linux container?

I'm publishing it using docker file via continuous integration (DevOps).

Here is the dockerfile:


FROM mcr.microsoft.com/dotnet/core/aspnet:3.1-buster-slim AS base
WORKDIR /app
EXPOSE 80
EXPOSE 443

FROM mcr.microsoft.com/dotnet/core/sdk:3.1-buster AS build
WORKDIR /src
COPY ["MyApp/MyApp.csproj", "MyApp/"]
RUN dotnet restore "MyApp/MyApp.csproj"
COPY . .
WORKDIR "/src/MyApp"
RUN dotnet build "MyApp.csproj" -c Release -o /app/build

FROM build AS publish
RUN dotnet publish "MyApp.csproj" -c Release -o /app/publish

FROM base AS final
WORKDIR /app
COPY --from=publish /app/publish .
ENTRYPOINT ["dotnet", "MyApp.dll"]



KI Kirk October 22, 2020 05:39 AM UTC

I'm seeing the same thing, both in Edge Beta (Chromium) and in Google Chrome.

Also, this happens when running locally, not deployed into Azure App Service.  Using 'netcoreapp3.1', VS 2019 preview (latest), debugging in IIS Express.

System.NullReferenceException: Object reference not set to an instance of an object.
   at Syncfusion.Blazor.Internal.ResourceManager.IsIE()
   at Syncfusion.Blazor.Internal.ResourceManager.BuildRenderTree(RenderTreeBuilder builder)
   at Microsoft.AspNetCore.Components.ComponentBase.<.ctor>b__6_0(RenderTreeBuilder builder)
   at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()

Using 18.3.0.42, and 18.3.0.40 doesn't exhibit the problem.  Did the implementation of IsIE change between these builds?


AS Alen Salk October 22, 2020 08:51 AM UTC

I'm havimg the same problem when hosting on hosting provider. Running local works fine. Also running on 18.3.0.40 works fine but on 18.3.0.42 throw exception no matter which browser. Server is Windows server 2008 running Asp Net Core 3.1.9

Error: System.NullReferenceException: Object reference not set to an instance of an object.
   at Syncfusion.Blazor.Internal.ResourceManager.IsIE()
   at Syncfusion.Blazor.Internal.ResourceManager.BuildRenderTree(RenderTreeBuilder builder)
   at Microsoft.AspNetCore.Components.ComponentBase.<.ctor>b__6_0(RenderTreeBuilder builder)
   at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()


FE Fergus October 22, 2020 12:23 PM UTC

I am also having this problem even with your selected publishing method.
Only when deploying to Azure. Works fine locally.
V18.3.0.42

[2020-10-22T12:20:09.631Z] Error: System.NullReferenceException: Object reference not set to an instance of an object.
   at Syncfusion.Blazor.Internal.ResourceManager.IsIE()
   at Syncfusion.Blazor.Internal.ResourceManager.BuildRenderTree(RenderTreeBuilder builder)
   at Microsoft.AspNetCore.Components.ComponentBase.<.ctor>b__6_0(RenderTreeBuilder builder)
   at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()


MD Michael Dwyer October 22, 2020 01:58 PM UTC

I am also getting the same error in Azure, runs fine locally:

System.NullReferenceException: Object reference not set to an instance of an object.
   at Syncfusion.Blazor.Internal.ResourceManager.IsIE()
   at Syncfusion.Blazor.Internal.ResourceManager.BuildRenderTree(RenderTreeBuilder builder)
   at Microsoft.AspNetCore.Components.ComponentBase.<.ctor>b__6_0(RenderTreeBuilder builder)
   at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()


PL Paolo Labellarte October 22, 2020 04:51 PM UTC

Same problem both in azure and in a production server running Windows server 2019 and IIS 10

Steps to reproduce:
- create a project in vs 2019 using syncfusion template for Blazor server mode, using syncfusion 18.2.0.59
- deploy the application in a windows 2019 IIS 10 server without syncfusion library installed or deploy in azure, the app works
- updated using nuget to 18.3.0.42
- deploy the application in a windows 2019 IIS 10 server without syncfusion library installed or deploy in azure, the app fails



Attachment: Screenshot_1_9b314036.zip


RH Ralph Hope October 23, 2020 08:02 AM UTC

Same problem here, you have looked at the wrong version with your analysis.  v18.3.0.40 is fine.  v18.3.0.42 crashes everywhere.


RC Ricardo Chaidez October 23, 2020 06:33 PM UTC

Having the same problem when deploying to Azure App Services. Syncfusion needs to fix this ASAP.


RA Rich Armstrong October 24, 2020 11:07 PM UTC

Same problem, only when deploying to Azure. V18.3.0.40 works fine, locally and on Azure; 18.3.0.42 works locally, fails when deployed to Azure.


MK Muthukumar Kannan Syncfusion Team October 26, 2020 04:45 PM UTC

Hi All,

Thanks for your patience.

We are fixed this reported issue which occurs in azure hosting. This has been included in the v18.3.0.44 package which will be available tomorrow( 27th Oct 2020).

We will let you know once it is in live.

Regards,
Muthukumar K


MK Muthukumar Kannan Syncfusion Team October 27, 2020 01:03 PM UTC

Hi All, 

The fix included package has been published now for live. So, we would suggest you upgrade our 'Syncfusion.Blazor' package to the latest version v18.3.0.44 and check again whether your reported issue is fixed or not.

https://www.nuget.org/packages/Syncfusion.Blazor/18.3.0.44

Please get back to us if you have further queries.

Regards,
Muthukumar K


Loader.
Up arrow icon