I'm trying to install Reporting Services Point on a remote SQL 2008 R2 SP2 server. I select the SQL server under Servers and Site System Roles and it lists the site database server name, database name (should this name be the same as the DB found in Reporting Services Configuration Manager?), folder name and reporting services server instance. I enter a new account that is a sysadmin on the SQL click verify and get:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified).

Ping works both ways, remote connection on this SQL instance are enabled, static ports configured, a rule to allowany is set in the firewall. Should I perhaps be entering the port (this instance uses a non-standard one) in the Add Site System Roles Wizard?

If I open up Reporting Services Configuration Manager, the service is started, mode is native, a domain user account is used for the service account, web service URL opens, I even created a new DB. Report Manager URL opens.

SCCM itself uses the same remote SQL instance, so it appears connectivity works fine.

Any assistance is appreciated.

SCCM computer account is sysadmin and added to the Administrators group on the SQL.

Hi,

For the Site Database server name should be the SQL server that hosts the SCCM Primary Site DB, the Database name should be the SCCM Primary Site DB.

Then you select which Reporting Services Instance should be used under" Reporting Server Server Instance" as you already installed the Reporting Services role on the Server that hosts the SQL Reporting Services instance, the should do it.

Regards,
Jrgen

Thank you Jrgen.

This all checks out, I'm however still receiving the above error. I might add that the same instance is used for SCCM as well as Reporting Services. This is a very, very small deployment (under 100 clients) and I didn't see the point in separating the two.

Unbelievable, I used up almost two days on this and it turned out I needed to add the site database server name as: sqlserver.domain.com\SCCM,3433

A comma needed to be used. I thought no port needs to be entered and if perhaps that :3433 would work, but not ,3433.

Problem solved, Reporting Services installed.

• Marked as answer by CypherMike Thursday, June 06, 2013 12:50 PM

 Thank you very much - CypherMike. 

You helped me so much!!!

I installed the DB on another Instance so i had to change the port # and just here i found this info that i need to use comma to define the port.

Tnx