How to resolve this "Microsoft.ReportingServices.WmiProvider.WMIProviderException:...." error?

CharlieLor 561

I keep getting this error.

Microsoft.ReportingServices.WmiProvider.WMIProviderException: An error occurred when attempting to connect to the report server remote procedure call (RPC) end point. Verify that the Report Server Windows service is running, and then retry the operation.  
  
 ---> System.Runtime.InteropServices.COMException: The RPC server is not listening. (Exception from HRESULT: 0x800706B3)  
   --- End of inner exception stack trace ---  
   at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.ThrowOnError(ManagementBaseObject mo)  
   at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.ListReportServersInDatabase(String[]& installationIDs, String[]& instanceNames, String[]& machineNames, Boolean[]& isInitialized, Int32& length)  
   at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ListReportServersInDatabase(RSReportServerInfo[]& serverInfos)

I'm setting up a remote Report Service that points to a SQL Server 2019 server in another box. I went through the whole process of "Change Database" in the Report Server Configuration Manager. I'm able to connect to the remote SQL Server 2019 Standard Edition fine.

However, when I tried to restore the database encryption keys, I get this error.

In the Event Log, I also see these errors.

I have similar errors to this thread, https://social.msdn.microsoft.com/Forums/sqlserver/en-US/c535ebf3-18a0-430d-9a1a-9184182dd946/ssrs-2017-rc-1-cant-start-up, but the SQL Server I'm running is 2019 Standard not 2017.

Some background information. The Report Server database was migrated from SQL Server 2014 Enterprise Edition to a SQL Server 2019 Standard Edition. Since 2014 allowed more than one instances of Report Service, on SQL Server 2019 we have no choice but to put this RS on another box and connect to the Report Server database remotely. This is where I run into a ton of issues and errors. Any help is much appreciated!

Hilal Bhat 10 Reputation points

2023-09-06T09:23:01.7066667+00:00
I recently encountered a similar issue while attempting to create a database using Reporting Services Configuration Manager 2019. The problem stemmed from another application occupying the default port (8082) used by Reporting Services.

Here's how I resolved it:

Navigate to the Reporting Services installation folder, typically located at C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\RSHostingService.

Locate and open the 'config.json' file within this directory.

In the 'config.json' file, you'll find references to 'managementURL' and 'listenerURL,' both using port 8082. Update both of these to a different port, such as 8083 (or any other available port you prefer).

Execute the following commands in your command prompt:

The first command is designed to release any applications using port 8083:

netsh int ipv4 add excludedportrange protocol=tcp startport=8083 numberofports=1 ``` - The second command registers the new URL and assigns it to the SQL Server Reporting Services user: ```powershell netsh http add urlacl url=http://+:8083/ user="NT SERVICE\SQLServerReportingServices" ``` I hope this solution proves helpful!"

7 answers

CharlieLor 561 Reputation points

2021-05-12T03:33:48.4+00:00

I also see this error in the SSRS log file name: ReportingServicesService_2021_05__.log once I clicked the Web Service URL. This is probably a dumb question but, is SQL Server 2019 Standard Edition able to serve two instances of RS? I already have the local RS instance setup and running. The issue I'm having right now is the remote RS instance.

rshost!rshost!21e4!05/11/2021-22:17:17:: i INFO: Currently registered url http://+:80/ReportServer/ on endpoint 2 resourceutilities!DefaultDomain!120c!05/11/2021-22:17:17:: i INFO: Maximum memory limit is 65536Mb rshost!rshost!120c!05/11/2021-22:17:17:: i INFO: Derived memory configuration based on physical memory as 8387564 KB servicecontroller!DefaultDomain!21e4!05/11/2021-22:17:17:: i INFO: Total Physical memory: 8588865536 rpcserver!DefaultDomain!27bc!05/11/2021-22:17:17:: i INFO: Process monitoring started. appdomainmanager!DefaultDomain!26c4!05/11/2021-22:18:10:: i INFO: Registering AppDomain: type='ReportServer'; id='3'; Name='ReportServer_SSRS_0-1-132652630897207519' appdomainmanager!DefaultDomain!26c4!05/11/2021-22:18:10:: i INFO: Creating a new AppDomainLifeCycleManagementEntry for AppDomain id '3' appdomainmanager!DefaultDomain!26c4!05/11/2021-22:18:10:: i INFO: Appdomain STARTED: id='3'; name='ReportServer_SSRS_0-1-132652630897207519' appdomainmanager!ReportServer_0-1!26c4!05/11/2021-22:18:12:: i INFO: RS authentication mode is 4; effective ASP.NET authentication mode is Windows. vdir=/ReportServer. appdomainmanager!DefaultDomain!26c4!05/11/2021-22:18:12:: i INFO: Appdomain:3 ReportServer_SSRS_0-1-132652630897207519 initialized (#1). appdomainmanager!DefaultDomain!26c4!05/11/2021-22:18:12:: i INFO: SetInitialized AppDomain id '3': initialized = 1 library!WindowsService_0!24d8!05/11/2021-22:18:28:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.; library!WindowsService_0!24d8!05/11/2021-22:18:28:: e ERROR: ServiceStartThread: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. ---> System.Data.SqlClient.SqlException: Transaction (Process ID 69) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. library!WindowsService_0!24d8!05/11/2021-22:18:28:: e ERROR: ServiceStartThread: Attempting to start service again... rpcserver!DefaultDomain!24d8!05/11/2021-22:18:28:: i INFO: RPC Server started. servicecontroller!DefaultDomain!24d8!05/11/2021-22:18:28:: i INFO: RPC Server started. Endpoint name ='ReportingServices$SSRS' webserver!ReportServer_0-1!26c4!05/11/2021-22:19:17:: i INFO: Reporting Web Server started library!ReportServer_0-1!26c4!05/11/2021-22:19:17:: i INFO: SQLDump flags: ReferencedMemory, AllThreads, SendToWatson library!ReportServer_0-1!26c4!05/11/2021-22:19:17:: i INFO: MiniDump flags: DataSegs, UnloadedModules, ProcessThreadData library!ReportServer_0-1!26c4!05/11/2021-22:19:17:: i INFO: Dump on: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogExceptionMicrosoft.ReportingServices.Modeling.InternalModelingExceptionMicrosoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException library!ReportServer_0-1!26c4!05/11/2021-22:19:17:: i INFO: Do not dump on: Microsoft.PowerBI.ReportServer.WebApi.Catalog.CatalogAccessExceptionSystem.Threading.ThreadAbortExceptionSystem.Web.UI.ViewStateExceptionSystem.OutOfMemoryExceptionSystem.Web.HttpExceptionSystem.IO.IOExceptionSystem.IO.FileLoadExceptionMicrosoft.SharePoint.SPExceptionMicrosoft.ReportingServices.WmiProvider.WMIProviderExceptionSystem.AppDomainUnloadedException library!ReportServer_0-1!26c4!05/11/2021-22:19:17:: i INFO: Minidump location: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\Logfiles resourceutilities!ReportServer_0-1!26c4!05/11/2021-22:19:17:: i INFO: SKU: SQL Server Standard resourceutilities!ReportServer_0-1!26c4!05/11/2021-22:19:17:: i INFO: Maximum memory limit is 65536Mb library!ReportServer_0-1!26c4!05/11/2021-22:19:18:: i INFO: Call to GetItemTypeAction(/). User: domain\userName. library!ReportServer_0-1!26c4!05/11/2021-22:19:18:: i INFO: Catalog SQL Server Edition = Standard
Please sign in to rate this answer.
Joyzhao-MSFT 15,596 Reputation points

2021-05-12T06:59:07.077+00:00

Have you purchased two licenses？
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
CharlieLor 561 Reputation points

2021-05-12T16:06:46.887+00:00

At this point, I think the main error is this one. This error will show up right after the RS is started and running.

library!WindowsService_0!1b5c!05/12/2021-11:01:13:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.;
library!WindowsService_0!1b5c!05/12/2021-11:01:13:: e ERROR: ServiceStartThread: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. ---> System.Data.SqlClient.SqlException: Transaction (Process ID 71) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
library!WindowsService_0!1b5c!05/12/2021-11:01:13:: e ERROR: ServiceStartThread: Attempting to start service again...
rpcserver!DefaultDomain!1b5c!05/12/2021-11:01:13:: i INFO: RPC Server started.
servicecontroller!DefaultDomain!1b5c!05/12/2021-11:01:13:: i INFO: RPC Server started. Endpoint name ='ReportingServices$SSRS'

If there is an connection issue, I should see it in the Windows Event log of either the RS remote instance or the SQL Server ReportServer but I don't. Regarding this line "Transaction (Process ID 71) was deadlocked on lock resources with another process and has been chosen as the deadlock victim.", how do I find out which app or process is was deadlocked and how to resolve this issue?
Please sign in to rate this answer.
Joyzhao-MSFT 15,596 Reputation points

2021-05-24T02:00:17.377+00:00

Because the forum does not support viewing your server environment, I suggest you use Microsoft's telephone support service (it will cost a fee), and this type of issue will usually be resolved properly.
https://support.microsoft.com/en-us/help/4051701/global-customer-service-phone-numbers ;
https://support.microsoft.com/en-us/supportforbusiness/productselection
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to resolve this "Microsoft.ReportingServices.WmiProvider.WMIProviderException:...." error?

7 answers

Your answer