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

Question

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

CharlieLor 566

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!"

2 answers

Your answer

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!"

Answer 1

Alexandre Azevedo Filho 10

I have faced the same problem recently. In my case, the error would show while creating the database from the Reporting Services Configuration Manager 2019.

The problem was caused because another application was making use of port 8082 which is the default port for reporting services.

the fix was the following:

On the Reporting Services installation folder, go to directory: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\RSHostingService

Then, open file config.json
Notice that the managementURL and listenerURL uses port 8082. I updated both to 8083 (it can be any other port you are sure is not being used).

Then, I ran the commands:

(The first command is just to remove any application that could have been using 8083)
netsh int ipv4 add excludedportrange protocol=tcp startport=8083 numberofports=1

netsh http add urlacl url=http://+:8083/ user="NT SERVICE\SQLServerReportingServices"

Hope this help!

Ryan 0 Reputation points

2024-07-04T03:49:54.77+00:00

Legitimately created this account just to say thank you! Why in the world does that config.json not update automatically when you change the port in report server configuration
vaishnavee 0 Reputation points

2025-03-19T13:50:37.0733333+00:00

While checking on the bindings on 8082 port, I found that port is already being used bby the process RSHostingService.exe

C:\Users\xyz>netstat -ano | findstr :8082

TCP 0.0.0.0:8082 0.0.0.0:0 LISTENING 4

TCP 127.0.0.1:8082 127.0.0.1:49737 ESTABLISHED 4

TCP 127.0.0.1:49737 127.0.0.1:8082 ESTABLISHED 3748

TCP [::]:8082 [::]:0 LISTENING 4

C:\Users\xyz>tasklist | findstr 3748

RSHostingService.exe 3748 Services 0 70,188 K

Then now the question is - do we still need to change the config file to free available port?

Thanks in advance for any inputs!

Answer 2

Joyzhao-MSFT 15,636

Hi @CharlieLor ,

Add local administrator rights to the service account running the SSRS instance
Switch the account to local service/local system
Start the reporting services and configure.
Now change the service account to domain account.

Best Regards,
Joy

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.

CharlieLor 566 Reputation points

2021-05-11T17:41:21.107+00:00

Thanks, Yoyazhao! I got further this time. However, after step 4, I clicked on the Web Server Service URL and after 15 minutes of stalling, the page finally showed this message.
CharlieLor 566 Reputation points

2021-05-11T18:04:15.977+00:00

I also keep getting this error below in the C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\LogFiles\RSManagement_*_**__**.log file.

Error Number:-2,State:0,Class:11
2021-05-11 13:01:13.3116|WARN|13|Symmetric Key Encryption access data is missing or corrupt| RequestID = s_9e875818-00c0-49e9-8d57-1dbb79fd22b1 System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at Microsoft.BIServer.Configuration.Key.KeyRepository.GetEncryptedSymmetricKey(InstallationInfo installationInfo)
at Microsoft.BIServer.Configuration.Key.KeyRepository.ReloadEncryptedSymmetricKey()
at Microsoft.BIServer.Management.WebApi.Controllers.StateController.ReloadEncryptedSymmetricKey(ISqlAccess sqlAccess, Byte[]& encryptedSymmetricKey, DatabaseValidationStatus databaseValidationStatus)
ClientConnectionId:c9759d0b-0a25-4d42-81a5-2b010a6c2ea4
Error Number:-2,State:0,Class:11
CharlieLor 566 Reputation points

2021-05-11T19:13:02.367+00:00

And if I tried to delete the database encryption key, I get this error.

Microsoft.ReportingServices.WmiProvider.WMIProviderException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseError)
at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.ThrowOnError(ManagementBaseObject mo)
at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.DeleteEncryptedInformation()
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.DeleteEncryptedInformation()
Joyzhao-MSFT 15,636 Reputation points

2021-05-12T02:08:31.71+00:00
Make sure that SQL Server Reporting Services (SSRS) is up and running.

Make sure that the user who accesses the report with you has the "folder/report" permission.

Ensure that the service account of the SSRS instance (which can be found in SQL Server Configuration Manager or SQL Server Reporting Services Configuration Manager) has db_owner access rights to the respective ReportServer and ReportServerTempDB databases.

If all the above operations are normal, please check the error log at the corresponding time when the problem is reproduced. In addition to the above message, you will find more detailed information in it. For example, you may see other error messages: "The transaction log of the database'ReportServer' is full"... But for your problem, it is more likely to be a timeout issue.
The timeout problem is most likely that the account you are currently using lacks certain permissions.
Joyzhao-MSFT 15,636 Reputation points

2021-05-12T02:28:26.22+00:00
The "WARN" mentioned in the log file usually does not affect the use, and is different from "Error". If you want to try to delete the encryption key, please follow the steps below:
1.Open SQL Serrver Management Studio>Report Server>New Query:

exec DeleteEncryptedContent

2.Restart the service and its work.

Microsoft.ReportingServices.WmiProvider.WMIProviderException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseError)

Regarding the error message, please refer to my previous comment and check the log file for supplementary explanation of the error. Check permissions and check whether the database server hosting the ReportServer database has disk space problems.
Regards,
Joy
CharlieLor 566 Reputation points

2021-05-12T02:30:02.557+00:00

The account service I used is in the Local Administrators group on both the SSRS box and ReportServer database box. As soon as the SSRS is up and running, I see this error in the log.

Error Number:-2,State:0,Class:11
2021-05-11 13:01:13.3116|WARN|13|Symmetric Key Encryption access data is missing or corrupt| RequestID = s_9e875818-00c0-49e9-8d57-1dbb79fd22b1 System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
CharlieLor 566 Reputation points

2021-05-12T02:44:53.82+00:00

I got this message when trying to delete the key in SQL Server Management Studio.

The account service I'm running SSRS has local Administrator privilege on both SSRS and ReportServer database server. This domain account also has sysadmin privilege on the SQL Server 2019 as well as db_owner of the ReportServerTest and ReportServerTestTempDB databases. So I really don't know what else it needs.

Again many thanks for the help thus far. I have done local RS setup before but not a remote RS instance before so I'm running out of ideas.
CharlieLor 566 Reputation points

2021-05-12T03:15:01.177+00:00
I have searched all the logs and I do not find this error message: "The transaction log of the database'ReportServer' is full". However, I do see a lot of the above message in the log as soon as the RS starts up.

Another thing I'm quite confused is that I used the following command to remove the previous report service machine key from the ReportServerTest database.

begin tran delete from Keys where MachineName = 'RSoldInstance'

However, once I put in the domain/accountName for the Service Account in the RS box and restart the RS, the previous RS instance machine key is back in the ReportServerTest database. And once this old machine key is back, I see this message in the Web Service URL page.

The feature: "Scale-out deployment" is not supported in this edition of Reporting Services. (rsOperationNotSupported) Get Online Help

Why is the old machine key keeps coming back even though I've deleted it?
CharlieLor 566 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
Joyzhao-MSFT 15,636 Reputation points

2021-05-12T05:56:20.113+00:00
use ReportServer exec DeleteEncryptedContent

Excute:
Joyzhao-MSFT 15,636 Reputation points

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

Have you purchased two licenses？
CharlieLor 566 Reputation points

2021-05-12T15:01:06.797+00:00

Yes, I tried that. It didn't work. The "Executing query..." at the bottom of the screen keeps spinning but nothing else happened on the screen.
CharlieLor 566 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?
Harper, John W 1 Reputation point

2021-08-12T23:07:01.453+00:00

Could step 5 be "remove account from local administrator rights"?
Will RSCM behave normally or must the service account be local admin indefinitely?

Share via

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

2 answers

Your answer