shockwave Posted April 14, 2014 Report post Posted April 14, 2014 HI I added the reporting services point to my site system roles. No error here. When I go to the list of errors it is empty. After more online searching I find this. In CMtrace in srsrp.log there is this text: Reporting Services URL from Registry [http://configmgr1/ReportServer/ReportService2005.asmx] SMS_SRS_REPORTING_POINT 14/04/2014 9:35:32 4272 (0x10B0) System.Web.Services.Protocols.SoapException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing.~ at Microsoft.ReportingServices.WebServer.WebServiceHelper.EnsureModeFromCatalog()~ at Microsoft.ReportingServices.WebServer.WebServiceHelper.EnsureRSNativeMode()~ at Microsoft.ReportingServices.WebServer.ReportingService2005..ctor() SMS_SRS_REPORTING_POINT 14/04/2014 9:35:32 4272 (0x10B0) (!) SRS not detected as running SMS_SRS_REPORTING_POINT 14/04/2014 9:35:32 4272 (0x10B0) Failures reported during periodic health check by the SRS Server ConfigMgr1.eindwerk.local. SMS_SRS_REPORTING_POINT 14/04/2014 9:35:32 4272 (0x10B0) Registry change SMS_SRS_REPORTING_POINT 14/04/2014 9:35:32 4272 (0x10B0) Waiting for changes for 1 minutes SMS_SRS_REPORTING_POINT 14/04/2014 9:35:32 4272 (0x10B0) Apparantly the server can't connect to the database. I've tried with multiple users in the reporting service site system role. Always the same result. specs: server is vmware windows 2008 r2 sql server 2008 sccm + sql server + reporting is on same vm domain functional level 2008r2 Quote Share this post Link to post Share on other sites More sharing options...
AmrelMahdy Posted April 14, 2014 Report post Posted April 14, 2014 Did you install "reporting Service" component in the SQL ? Quote Share this post Link to post Share on other sites More sharing options...
shockwave Posted April 14, 2014 Report post Posted April 14, 2014 yes, SQL Server Reporting Service is running automated at startup Quote Share this post Link to post Share on other sites More sharing options...
shockwave Posted April 17, 2014 Report post Posted April 17, 2014 anyone have an idea? Quote Share this post Link to post Share on other sites More sharing options...
AmrelMahdy Posted April 18, 2014 Report post Posted April 18, 2014 please attach the file "srsrp.log" Quote Share this post Link to post Share on other sites More sharing options...
shockwave Posted April 18, 2014 Report post Posted April 18, 2014 this is the file: http://speedy.sh/sjj3S/srsrp.log Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted April 18, 2014 Report post Posted April 18, 2014 Did you also run the configuration of reporting services? Quote Share this post Link to post Share on other sites More sharing options...
AmrelMahdy Posted April 19, 2014 Report post Posted April 19, 2014 There is the Error "System.Web.Services.Protocols.SoapException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing.~ at Microsoft.ReportingServices.WebServer.WebServiceHelper.EnsureModeFromCatalog()~ at Microsoft.ReportingServices.WebServer.WebServiceHelper.EnsureRSNativeMode()~ at Microsoft.ReportingServices.WebServer.ReportingService2005..ctor() $$<SMS_SRS_REPORTING_POINT><04-14-2014 08:58:03.159-60><thread=4272 (0x10B0)>" try to follow the Below Steps Open the SQL Server Configuration Management tool. Click the triangle in front of “SQL Server Network Configuration”, and click the “Protocols for MSSQLSERVER”. (If you are using a named SQL Server instance, please select the named instance instead.) Please make sure both the “TCP/IP” and “Named Pipes” protocols are enabled. To enable a protocol, please right-click on the protocol and click “Enable”. Quote Share this post Link to post Share on other sites More sharing options...
shockwave Posted April 19, 2014 Report post Posted April 19, 2014 they already were enabled [ Quote Share this post Link to post Share on other sites More sharing options...
AmrelMahdy Posted April 21, 2014 Report post Posted April 21, 2014 check this Article http://sqljoe.wordpress.com/2011/02/16/ssrs-errors-rsreportserverdatabaseunavailable-the-report-server-cannot-open-a-connection-to-the-report-server-database/ http://social.technet.microsoft.com/wiki/contents/articles/15475.how-to-successfully-install-reporting-services-point-role-in-sccm-2012-sp1.aspx Quote Share this post Link to post Share on other sites More sharing options...
shockwave Posted April 22, 2014 Report post Posted April 22, 2014 thanks, I've looked into the sql server reporting manager. I can't find the reports database in SQL Server Management studio so I assumed it didn't exist I tried to create a new db but the db ReportServer exists after all. I found it in the folder C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA. I got this error when I tried creating a db that already exists. System.Data.SqlClient.SqlException: Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\ReportServer.mdf' because it already exists. Change the file path or the file name, and retry the operation. CREATE DATABASE failed. Some file names listed could not be created. Check related errors. 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(SqlConnection conn, String script, ICommandWrapperFactory commandWrapper) at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(String connectionString, String script) at ReportServicesConfigUI.SqlClientTools.SqlTools.ApplyScript(String connectionString, String script) If I create a new database for reporting, should it be in native mode or sharepoint mode? Quote Share this post Link to post Share on other sites More sharing options...
shockwave Posted April 26, 2014 Report post Posted April 26, 2014 In Reporting Services Configuration Manager I've moved it to a new database. Then it worked in SCCM. Thanks Quote Share this post Link to post Share on other sites More sharing options...