Configuration of Reporting Services
obviously until I get this sorted I cannot deploy my reports in my Reporting Services Configuration All ticked except initialisation (3) in Database services ticked but on the right hand side there are warnings/errors Verifying Database Edition - ticked Verifying Database Version - warning The current connection string is not valid and can't be used to connect to SQL Server Where do I check this? (1) Creating A Grant Rights script for LocalSystem = ticked Assigning Reporting Services Rights to User = error (2) System.Data.SqlClient.SqlException: The role 'RSExecRole' does not exist in the current database. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(String connectionString, String script) at ReportServicesConfigUI.SqlClientTools.SqlTools.ApplyScript(String connectionString, String script) Can someone tell me what I should be checking please? thanks
November 23rd, 2006 4:58am
HI !!! I am also facing the same problem, The database server is sql 2000 personal edition while reporting server is sql 2005 evaluation. In 'Database Setup' option displayes 'success'; but 'Verify Database Version' and 'Setting Connection Info For Reporting Server' are warnings while 'Create grants rights script' task is failing. The 'Initialization' option is also failing. The message displayed is 'The report server cannot open connection to report server database (rsReportServerDatabaseUnavailable)' Which setting should I check in report configuration? Or is this backward compatibility issue?
December 7th, 2006 7:32am
On your reporting database, Make sure under Security/Roles - that the RSExecRole exist, if not create it. It should also be assigned to the schema of RSExecRole. Finally, on your report service login User make sure that this user is assigned under the RSExecRole. I hope this helps. Ham
December 7th, 2006 9:57pm
HI Ham, Thanks a lot for the reply. I'll try out the solution suggested by you andletyou know the outcome after that. -Nishad
December 11th, 2006 8:35am
Ham, I am having the same problem. I need extra clarification, though. When you say check under Security/Roles, are you talking about doing this on the Reporting Services server or the database engine server that reporting services is connected to? For instance, in my Object Explorer I see my reporting services server and under that in the tree is Security -> Roles. However, when I try to right-click on anything there it gives me the following message: Unhandled exception has occured in a component in your application. If you click Continue, the application will ignore this error and attempt to continue. The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. the expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase). Furthermore, when I try to upgrade the database by clicking 'Upgrade' in the Database Setup section of the Reporting Services Configuration Manager it gives me a green check on Verifying Database Edition and a yellow exclamation mark on Verifying Database Version. The warning says: The current connection string is not valid and can't be used to connect to SQL Server. So, if you mean I should add the RSExecRole to Security/Roles under my reporting services server, then I am in even deeper trouble than I thought. However, if you mean I should add them to Security/Server Roles under my database engine tree then I'm probably back in business. I am loathe to try anything until I get clarification. Thanks for your kind help!
December 16th, 2006 12:27am
Nevermind, I solved my problem. I just needed to click the New button on the Database Setup page before trying to connect. Pretty silly on my part, but all's well that ends well.
December 18th, 2006 11:52pm
Ham and Philip, I am having similary problem. When i am trying to get connection with my existing database, It says in task status 1- Varifying Database Edition (Pass) 2- Verifying Database Version (! Exclamitaion) 3- Creating Grant Rights for ServerName\UserName (Not Pass X) In the browser when i am typing http://LocalServer/ReportServerThat generate error that is Reporting Services Error The report server cannot open a connection to the report server database. The logon failed. (rsReportServerDatabaseLogonFailed) Get Online Help Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E) SQL Server Reporting Services Please help me Regards, Irfan
December 29th, 2006 12:48am
Irfan, If I remember correctly from when I was having my troubles, this may be due to ASPNET permissions on your web server. You might google ASPNET reporting services server persmissions or something like that. Best luck to you!
December 29th, 2006 1:12am
Irfan, This is stating that the "Report Database is failing" - First, verify that the login setup for Report Server logon in the Report Configuration Manager is correct. You can verify that by connecting to the SQL2005 via studio management with the report server logon credentials let me know if this works for you.
December 29th, 2006 7:06pm
Was also getting the error and just needed to click "new" instead of entering the fields. Would be nice if the error reflected that the DB had not been created yet (and user rolls had not either). Thanks, -Greg
April 30th, 2008 7:36am
Though the question has been closed, I'd like to add some comment on Irfan's questions ...Irfan, please try with following steps: Check the users inRSExecRole of ReportServer database Open "Reporting Services Configuration Manager" -> Database, verify the login under[Current Report Server Database Credential] is one of users inRSExecRole or not, if not, click "Change Credentials" button to change to an user inRSExecRole. done Hope that helpsJeffrey
March 23rd, 2009 6:42am
Best post ever on the internet to solve the SSRS 2005 connection issue. Thank you very much guys.
February 7th, 2010 1:55pm
Nevermind, I solved my problem. I just needed to click the New button on the Database Setup page before trying to connect. Pretty silly on my part, but all's well that ends well. Man, this is the best post ever about this problem. After seeking for about 2 hour on google, loosing the morning and being oriented by the administrator to reinstall everything, this simple click on the 'New' button solved my problem. Pretty silly on my part too! :) Thanks in advance!
January 26th, 2011 12:19pm