Share via

SSRS 2019 Configuration Error – “The RPC server is not listening (0x800706B3)”

Yael 20 Reputation points
2025-10-24T06:59:39.5533333+00:00

Hello Microsoft Support,

We are having an issue while configuring SQL Server Reporting Services (SSRS) 2019.

Environment:

  • Windows Server 2019
  • SQL Server 2019 Standard Edition
  • SSRS 2019 (standalone)
  • Service Account: NetworkService
  • Logged in as a domain administrator

Issue:

When using Report Server Configuration Manager > Database > Create or Change Database,

We get the following error:

Microsoft.ReportingServices.WmiProvider.WMIProviderException:

An error occurred when attempting to connect to the report server RPC endpoint.

System.Runtime.InteropServices.COMException: The RPC server is not listening. (0x800706B3)

Question:

What could cause this RPC endpoint error when configuring the SSRS database?

Could it be related to permissions or a mismatched instance configuration?

Thank you for your help.

z7143059001871_b7bd7531361dc3e72656d2c19781a8fd

SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
0 comments
Answer accepted by question author
  1. Lakshmi Narayana Garikapati 470 Reputation points Microsoft External Staff Moderator
    2025-10-24T08:29:33.3833333+00:00

    Hi @Yael,

    Thank you for reaching out to the SQL Forum.

    If you're having trouble with SQL Server Reporting Services (SSRS), it could be due to a few common issues. First, make sure key Windows services like Remote Procedure Call (RPC) and the SSRS service are running check this in Services.msc. . Sometimes, firewalls block RPC traffic (especially on TCP port 135), so make sure your firewall allows Remote Service Management and WMI. SSRS relies on WMI to configure the report server, so the account running Report Server Configuration Manager needs admin rights and access to the correct WMI namespace (like root\Microsoft\SqlServer\ReportServer<InstanceName>\v13, though the version may vary). If the namespace is missing or corrupted, the RPC call will fail try verifying or salvaging the WMI repository using winmgmt commands. Also, make sure the service account (like NetworkService) has proper permissions on SSRS folders and databases. To troubleshoot, start by checking the services with sc query, test WMI connectivity using wbemtest, look for errors in Event Viewer, and temporarily disable the firewall to rule out network issues. If the WMI namespace is missing, you may need to repair or reinstall SSRS. And yes, if you're using a named instance but SSRS was installed as default, the namespace path might not match, which can also cause problems.

    If you still have any questions or need further assistance, don’t hesitate to get in touch we’re happy to continue supporting you.

    We appreciate your participation and thank you for being an active member of the community.

    Best regards,

    Lakshmi

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.