I'm in the same situation, the same error is raised from a page with an EjsGrid:
[2020-01-07T11:29:21.331Z] Error: System.NullReferenceException: Object reference not set to an instance of an object.
As with Dino, the app works on development machine but does not work on production server.
BCBerly Christopher Syncfusion Team January 7, 2020 08:47 AM
Greetings from Syncfusion Support.
We have validated your scenario. Unfortunately, we could not able to reproduce the reported issue at our end. We have made sample for your convenience, please check the attached sample. If you are still facing the issue or if we misunderstood your query, please share below details to proceed further.
Issue reproducing sample
If possible, try to reproduce the issue in the attached sample.
at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)
SNSevvandhi Nagulan Syncfusion Team January 9, 2020 09:19 AM
We have checked hosting the sample in Azure and we are unable to reproduce the reported issue at our end. On the first page if you click on Login button, DatePicker will be rendered. On FetchData page, you can find the Grid. Kindly refer the below hosted link.
I faced the same issue. Reading the reply about identifying SignalR as a potential problem, I remembered that VisualStudio after publishing the solution is showing a dialog box that states that the SignalR service is not used with my Azure host and if WebSocket should be turned on. As I deployed another Blazor app using Syncfusion components successfully in the past, I was not paying attention and clicked 'No'. Motivated by the hint about SignalR, I was re-publishing and this time answering the dialog with 'Yes' to turn on WebSocket. Et voila, my app starts with no problem. I will research this in more detail to figure out if something with the default config of the App Service changed causing this problem. But I also remember that for some reason the original deployment was using .Net stack instead of .Net Core stack, not sure if I missed a setting as configuring the App Service or if this was an Azure glitch during deployment. I recognized the issue as I did review the config and manually corrected the stack. So there is another potential cause for the failing SignalR if it gets screwed up by manually switch the stack. I have no experience with server-side Blazor hosting yet and need to dive deeper into it.
RCRoberto ContiJanuary 17, 2020 03:14 PM
More than 10 days after the issue has been reported and still no useful response from Support.
Everything tried has been unsuccessful and company decided Syncfusion components are not viable as they do not work at all.
That's a true pity.
DNDino NovakJanuary 17, 2020 03:29 PM
We had a same case, now moved to Redzen Blazor componetns and have a working form.
JAJesus Arockia Sankaran S Syncfusion Team January 22, 2020 09:26 AM
Sorry for the long delay.
We have checked your query with windows server and azure but it was not reproduced. Could you please refer the deployment steps in below link.
Also ensure that the latest hosting bundle/sdks installed in your production machine.
Meanwhile, we are checking in windows server with your queries.
Jesus Arockia Sankaran S
JAJesus Arockia Sankaran S Syncfusion Team January 23, 2020 08:55 AM
We are deeply regret for the long delay in getting back to you.
We have validated the reported runtime exception in various production server environment like Azure, Windows server 2016, etc.. And we suspect that the issue occurred due to below cause when deployed in production server.
1. The production server may have outdated configuration like .NET Core SDK and .NET Core runtime hosting bundle.
Solution: Update your dotnet hosting bundle with latest version in your production machine.
Please find the link below for latest hosting bundle and install it in your hosting machine to resolve this.
2. Under the Application Development Roles in your production/deployment machine, ensure the following options are checked
Meanwhile we have handled the runtime null exception in our source and the fix is available in the below NuGet package. This will be included in our upcoming SP1 Release which is expected at the end of January 2020.