Reporting Services Installation Problem

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Business Intelligence » Reporting Services Installation Problem -...

Reporting Services Installation Problem - help requested

Rate Topic

Display Mode

Topic Options

Author

Message

mwilson-556363

Posted Thursday, July 10, 2008 2:17 PM

Forum Newbie

Group: General Forum Members
Last Login: Tuesday, December 23, 2008 7:51 AM
Points: 1, Visits: 11

Hello - I'm almost at my wits end trying to get Reporting Services installed. I've been pouring through anything I can find online (mostly the SQL Server 2005 online book at MSDN). I have SQL Server 2005 installed on one server and I have a separate box I'd like to use for my web server (IIS and ASP.NET are all installed and working fine).

Here's a run-down of my installation process:

Running installation on web server (DEVWEB) logged in as a domain
user (user exists on both web server and database server)

During Setup
------------
Instance Name: Default Instance
Service Account: Windows domain account fi\devadmin

All product installations complete with no errors:
SQL Setup Support Files
OWC11
SQL Server Backward-Compatibility Files
Reporting Services
MSXML6
SQL Native Client
Workstation Components, Books Onlin...

Next run "Reporting Services Configuration" utility.
Instance Selection:
Machine Name: DEVWEB
Instance Name: MSSQLSERVER
Select "Connect" button

Server Status and Windows Service Identity have green checks.

Select "Report Server Virtual Directory"
Click "New" and choose defaults
Website: Default Web Site
Virtual Directory: Report Server
Click OK button & wait
- Create Virutal Directory (green check)
- Changing Secure Connection Level (green check)
- Updating Report Server URLs (green check)
Report Server Virtual Directory now has a green check

Select "Report Manager Virtual Directory"
Click "New" and choose defaults
Website: Default Web Site
Virtual Directory: Reports
Click OK button & wait
- Create Virtual Directory (green check)
Report Manager Virtual Directory now has a green check

Select "Web Service Identity"
ASP .NET Service account, accept default setting of "NT Authority\NetworkService"
Choose "ReportServer" from drop down for both Report Server and Report Manager application pools.
Click Apply button & wait
- Setting Web Service Identity (green check)
- Setting Report Manager Identiy (green check)
Web Service Identity now has a green check

Select "Database Setup"
Click "Connect" button.
Specify Server Name: DEVSQL
Credintials Type: SQL Server Account
Username: sa
Password: ***********

Click "New" for Database Name and choose defaults:
Server Name: DEVSQL
Credentials Type: sa
Password: ***********
Database Name: ReportServer
Language: English

Back on the Database Connection Window:
Server Name: DevSQL
Database Name: ReportServer
Credentials Type: Windows Credentials
Account Name: fi\devadmin
Password: **********
Click "Apply"

In SQL Server Connection Dialog,
Server Name: DEVSQL (grayed out)
Credentials Type: SQL Server Account
Username: sa
Password: **********
Click OK
- Verifying Database Edition (green check)
- Verifying Database Version (green check)
- Creating a Grant Rights script for fi\devadmin (green check)
- Assigning Reporting Services Rights to User (green check)
- Setting Connection Info for Reporting Services (yellow exclamation)
-- "Although saving the database connection succeeded, the report server
-- cannot access internal information about this deployment to determine
-- whether the current configuration is valid for this edition. If you
-- are configuring a scale-out deployment, be sure that you initialize
-- any new report servers from one that is already part of the
-- deployment."
Database Setup now has a green check.

When I try to click on "Initialization" I am given the following pop-up
error message:

"There was an error while switching panels. The most likely cause is an
error retreiving WMI properties. The exception details are: 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. Details: The RPC
server is not listenting. (Exception from HRESULT: 0x800706B3)"

Click OK and Initialization remains a red circle with a white X.

Examine Windows Services to see:
- RPC is started and running
- SQL Server Reporting Service (MSSQLSERVER) is started and running

Looking in logfile in this directory:
C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\LogFiles

The following ERROR is listed:

ReportingServicesService!library!8!7/10/2008-12:50:22::
e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailable
Exception: The report server cannot open a connection to the report server database.
A connection to the database is required for all requests and processing., ;

Info: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailable
Exception: The report server cannot open a connection to the report server database.
A connection to the database is required for all requests and processing.
---> System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the fact that under the default
settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

The ReportServer and ReportServerTempDB databases are created and the domain user appears to have all of the necessary permissions.

Sorry to be so long winded - I keep getting hung up at the same point and I have found no help in books or online yet - does anyone have any ideas of what I am doing wrong?

Thanks!
-Mark.

Post #531958

esraina

Posted Wednesday, March 25, 2009 3:08 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, March 14, 2012 8:46 AM
Points: 2, Visits: 5

Hello

in command window :

rsconfig -c -m and do restart to rs.
with thiscommand we can set connection information of 'reportserver' database for
rs. When you press apply button in rs database configuration still you can get error but
when you look at reportserver webservice and website they are work well now; and don't get error :

for more information you can look here :
http://ismailtutumluer.wordpress.com/2007/01/16/the-report-server-cannot-open-a-connection-to-the-report-server-database-a-connection-to-the-database-is-required-for-all-requests-and-processing/

Post #683126

esraina

Posted Wednesday, March 25, 2009 3:09 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, March 14, 2012 8:46 AM
Points: 2, Visits: 5

Hello

in command window :

rsconfig -c -m REMOTECOMPUTERNAME -s SQLSERVERNAME -d reportserver -a SQL -u SA -p SAPASSWORD and do restart to rs.

with thiscommand we can set connection information of 'reportserver' database for
rs. When you press apply button in rs database configuration still you can get error but
when you look at reportserver webservice and website they are work well now; and don't get error :

for more information you can look here :
http://ismailtutumluer.wordpress.com/2007/01/16/the-report-server-cannot-open-a-connection-to-the-report-server-database-a-connection-to-the-database-is-required-for-all-requests-and-processing/

Post #683128

AMBALAVANAN C

Posted Tuesday, August 23, 2011 10:01 AM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, September 06, 2012 8:03 AM
Points: 1, Visits: 100

Apply SP3 on Reporting services that might help.

Post #1164139

« Prev Topic | Next Topic »

Permissions