SSRS 2019 failed to Generate Reports after installed to Windows Server 2019

Question

Hello,

I have got a problem to generate SSRS reports from SSRS 2019 on Windows Server 2019, but it starts to work after installed SSRS 2019 to Windows Server 2016.

Here is the exception messages:
[2021-01-19 12:26:23Z] [ERR] Report generation task threw an exception
Message = This operation is not supported on a report server that runs in native mode. ---> Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedNativeModeException: This operation is not supported on a report server that runs in native mode.
Source = System.Private.ServiceModel
Stacktrace = at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannelProxy.TaskCreator.<>c__DisplayClass1_0.<CreateGenericTask>b__0(IAsyncResult asyncResult)
--- End of stack trace from previous location where exception was thrown ---
at UserInterfaceBusinessObject.BusinessObjects.ReportingBackgroundTasks.SsrsReportBuilder.BuildSummaryReport(ReportExecutionServiceSoap reportingService, IReportRequestParameters request, String clientUiCulture) in E:\Jenkins\workspace-UiApiService-V3-CI\svn\UiApiService\UserInterfaceBusinessObject\BusinessObjects\ReportingBackgroundTasks\SsrsReportBuilder.cs:line 181
at UserInterfaceBusinessObject.BusinessObjects.ReportingBackgroundTasks.SsrsReportBuilder.CreateClinicalDataReport(String reportDirPath, String reportFilePathAndName, IReportRequestParameters request, String clientUiCulture, CancellationToken token) in E:\Jenkins\workspace-UiApiService-V3-CI\svn\UiApiService\UserInterfaceBusinessObject\BusinessObjects\ReportingBackgroundTasks\SsrsReportBuilder.cs:line 136

Many thanks,

Answer 1

Hi @Visakh ,

Thanks for your reply. They are rdl reports. These reports are developed from VS2012 SSDT, which have been used many years.

They have been programmatically deployed to SSRS 2016, SSRS 2017, SSRS 2019, but all OS are Windows Server 2016 downward.

The issue is only occurring after installed SSRS 2017 or SSRS 2019 to Windows Server 2019.

Answer 2

I know this is an old question, but I would just like to share the solution we found for the problem we had in case others encounter it.

In our case, we were testing with a SSRS server that did not have HTTPS enabled. We were calling the method "LoadReportAsync" from ReportExecution2005.asmx, passing a "new ReportExecutionTrustedUserHeader()" instance in the first parameter.

Apparently, with a newer window server version (or something else newer, i don't know for sure) this can only work if you call an HTTPS website.

If you call an HTTP website, you need to pass "null" instead.

This was not an issue on an older server. This is not an issue with ReportService2010.asmx (we can pass a trusted header without getting an OperationNotSupportedNativeModeException).

I would like to give credit and thank BJ Safdie whose answer pointed me in the right direction here : https://stackoverflow.com/questions/10922645/ssrs-2008-execution-service-loadreport-error

Not sure that it will help in all cases, but hope it will be useful to someone else too.

Answer 3

NOTE: The SSRS reports are generated programmtically throught API call.

Answer 4

The error message says
This operation is not supported on a report server that runs in native mode
May I know what type of report you're trying to generate? Does it have any unsupported features being used?

Answer 5

Hi @Pengxin Fan ,

Could you please help check below:

Create a simple report with VS or Report Builder.

Deploy the report directly to the report server with Windows Server 2019 to see if it could succeed or not.

If failed you may also show the error message to us.

In addition, here is the hardware and software requirements for SSRS2017 and later, just for reference.

hardware-and-software-requirements-for-installing-sql-server

Regards，
Zoe

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

What can I do if my transaction log is full?--- Hot issues November

How to convert Profiler trace into a SQL Server table -- Hot issues November