Author |
Topic |
whhs
Starting Member
14 Posts |
Posted - 2009-09-23 : 09:21:05
|
When trying to connect/login to the ReportServer, the following message comes up:The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) Get Online HelpCannot open database "Report" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. In the database ReportServer there is no possibility to add new users, thus also not the Network Service and Administrator.Any suggestions on how to connect - and further - configurate the MS Reporting Services 2005?Help much appreciated. |
|
JCirocco
Constraint Violating Yak Guru
392 Posts |
Posted - 2009-09-23 : 09:33:56
|
Sounds like the server is not initialized.To verify that the report server is initialized:- Go to reporting server (or have someone who has authority)- Start Reporting Services Configuration Manager- Third icon from botton labeled Initialization should be Green with Check mark. If it is not, select that and then click Initialize. It could also be the Windows Service Identity. That needs to be set to a user account with authority to the database where Reporting Services data is stored.John"The smoke monster is just the Others doing barbecue" |
|
|
whhs
Starting Member
14 Posts |
Posted - 2009-09-23 : 09:48:23
|
Thx John, the checkmark isn't green on 'Initialization' (not selectable).However, there is a slight problem creating the ReportServer database itself in the section 'Database setup'.The message that comes up is: Assigning Reporting Service Rights to UserHow can this be solved? |
|
|
JCirocco
Constraint Violating Yak Guru
392 Posts |
Posted - 2009-09-23 : 09:57:16
|
- Make sure that the SQL server name is correct- Verify that the Database name exists- What is the database version displayed (this caused us our problems when we did our installation)- What do you have for credentials type? We have Service Credentials selected and then we have a service account defined in the Windows Service Identity section. This user must have proper authority to the database. Unfortunately I do not have the authority to see what ours is set as here (sorry)John"The smoke monster is just the Others doing barbecue" |
|
|
whhs
Starting Member
14 Posts |
Posted - 2009-09-23 : 10:13:51
|
The SQL server name is correct.The database must be created (not there yet).Windows Server Identity (another tab) states when Applying on a Windows account:"Could not locate entry in sysdatabases for database 'ReportServer'. No entry found with that name. Make sure that the name is entered correctly."The service account is the default Administrator.Database version is blank (since there is no database I guess).I use the Service Credentials.Maybe there is something wrong with the (Reporting Services) rights of this Administrator. Where can I check them? What is necessary? What is mandatory? |
|
|
JCirocco
Constraint Violating Yak Guru
392 Posts |
Posted - 2009-09-23 : 10:25:04
|
I seam to recall it was the Blank version that was causing our error. Let me check to see if I still have documentation of what was changed.John"The smoke monster is just the Others doing barbecue" |
|
|
whhs
Starting Member
14 Posts |
Posted - 2009-09-23 : 10:34:12
|
That would be great if you'd still have the documentation.And would like to share :) |
|
|
JCirocco
Constraint Violating Yak Guru
392 Posts |
Posted - 2009-09-23 : 13:31:00
|
The 2 people that I emailed what was changed are not in today (and I diligently clean my sent email monthly). Hopefully they will be in tomorrow or check their email today.John"The smoke monster is just the Others doing barbecue" |
|
|
JCirocco
Constraint Violating Yak Guru
392 Posts |
Posted - 2009-10-02 : 13:15:51
|
whhs, Did you every get your issue resolved? I just created another test server and found the issue I was referring to. On the Database Connection section of Configure Report Server, if your Database version is blank, click the upgrade button to the right.Also, just to be sure, in IIS setup, the Website properties, ASP.net version tab had a blank version. Clicking the drop down allowed me to select a valid version.Sorry it took so long to get back on this.John |
|
|
whhs
Starting Member
14 Posts |
Posted - 2009-11-04 : 06:16:10
|
Yes, issue has been resolved by an external system administrator.Thx for the help anyways. |
|
|
|