【SSRS】 Setup RPC Exception 0x800706B3
>
>
【SSRS】 Setup RPC Exception 0x800706B3

SSRS - Setup RPC Exception 0x800706B3

SSRS - Setup RPC Exception 0x800706B3

Dealing with SSRS Setup RPC Exception 0x800706B3: error hit when generating Database script, Learn how to troubleshoot and resolve the RPC error in SSRS setup.

Resolving the SSRS Setup RPC Exception 0x800706B3 is a critical task for ensuring a seamless SQL Server Reporting Services (SSRS) installation. This error code indicates a problem with the Remote Procedure Call (RPC) communication, which is essential for SSRS to function correctly. To address this issue, follow a comprehensive troubleshooting process:

Solution - 1.

Check System Requirements:
  • Verify that your server meets the system requirements for SQL Server Reporting Services (SSRS) installation. Check the Microsoft documentation for the exact specifications needed for your version of SQL Server.
Firewall Configuration:
  • Ensure that inbound and outbound ports required for SSRS are open in your firewall. The default ports for SSRS are 80 and 443 for HTTP and HTTPS communication. If you’re using a named instance, ensure the port for that instance is open as well.
RPC/SSRS Service Status:
  • Confirm that the Remote Procedure Call (RPC) service is running on the server where you intend to install SSRS.
  • To check the RPC service status, open the “Services” application (services.msc) on your server, find the “Remote Procedure Call (RPC)” service, and ensure it’s set to “Automatic” startup and is running.
  • Make sure SQL Server (YourInstance), and SQL Server Reporting Services is running.
SQL Server Configuration:
  • Ensure that your SQL Server instance is configured correctly, as SSRS relies on SQL Server for its data. Check that SQL Server is installed and running without issues.
Service Accounts:
  • Confirm that the service accounts used by SQL Server and SSRS have the necessary permissions and are configured correctly.
  • The SQL Server service account and SSRS service account should have appropriate access to the required databases and directories.
Update/Reinstall:
  • As a last resort, consider updating or reinstalling SSRS. Before doing this, make sure to back up your SSRS configuration settings and databases to avoid data loss.

Solution - 2.

1 - Sample Code..

Check whether port 8082 already been used or not. If yes either free up the port 8082 and restart your SSRS or trying to use other port like 8080.

Assumed that port 8082 already used and decided to use other port 8080.
  • Go to your SSRS installation path C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\RSHostingService\config.json
  • Change the port from 8082 to 8080.
  • required to change 2 line of code.
Default – Partial code.
{
    "Config": 
    {
        "BI_SERVER": "false",
        "managementUrl": "http://localhost:8082",
        "rsConfigFilePath": "..\\ReportServer\\rsreportserver.config",
        "SecureConnectionLevel": "0"
    },
    "ManagementProcess": {
        "name": "Management Service",
        "path": "Management\\RSManagement.exe",
        "parameters": "",
        "Config": {
            "Dumper.flags": "SendToWatson, AllThreads, AllMemory",
            "Dumper.preventIfContains": "Microsoft.BIServer.HostingEnvironment.Exceptions.TrustedProcessTokenExpiredException",
            "listenerUrl": "http://+:8082/",
            "restartOnChangesTo": "Dumper.flags,Dumper.preventIfContains,listenerUrl"
        }
    }

After – Partial code.

{
    "Config": 
    {
        "BI_SERVER": "false",
        "managementUrl": "http://localhost:8080",
        "rsConfigFilePath": "..\\ReportServer\\rsreportserver.config",
        "SecureConnectionLevel": "0"
    },
    "ManagementProcess": {
        "name": "Management Service",
        "path": "Management\\RSManagement.exe",
        "parameters": "",
        "Config": {
            "Dumper.flags": "SendToWatson, AllThreads, AllMemory",
            "Dumper.preventIfContains": "Microsoft.BIServer.HostingEnvironment.Exceptions.TrustedProcessTokenExpiredException",
            "listenerUrl": "http://+:8080/",
            "restartOnChangesTo": "Dumper.flags,Dumper.preventIfContains,listenerUrl"
        }
    }
After change from port 8082 to 8080, open up your powershell and run below code:
netsh http add urlacl url=http://+:8080/ user="NT SERVICE\SQLServerReportingServices

After run restart your SSRS.

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments

Search

.
Xiao. tian
.

Piano - Music

.

Recent - Post

.
2 1 vote
Article Rating

Start typing and press Enter to search

Shopping Cart
0
Would love your thoughts, please comment.x
()
x