Hello, I am trying to configure reporting services to use remote reporting database. My report server is SQL Server 2008 R2 Standard Edition. My remote database which hosts report database is SQL Server 2008 R2 Datacenter Edition deployed on failover cluster. When I configure the reporting server using Reporting Services Configuration Manager, it can connect to remote database with provided credentials. But when I browse to the report URL, it returns "The report server has encountered a configuration error." The event log has an error which says "Report Server (MSSQLSERVER) cannot connect to the report server database.". I am not sure if I am missing any steps here. Your help is appreciated. Thanks, Piyush

Get sysadmin or dbowner rights on the remote db instance for the credentials with which you are trying to configure SSRS.

The login has sysadmin rights, still the same error. Piyush

Another error in the log file is "Cannot get edition information from catalog server". I am not sure what is happening.

Hello Piyushc, Please review this solution...Especially to the following two explanations under Explanation: http://msdn.microsoft.com/en-us/library/aa337324.aspx The connection to the Database Engine service fails because remote connections or the TCP/IP protocol is not enabled. The service account is not configured correctly, or the account no longer has permissions on the report server database. This can occur if you do not use the Reporting Services Configuration tool to set up the account or the report server database. Also follow protocol under User Action: Start the Database Engine service if it is not running and check that remote connections are enabled for TCP/IP protocol. Use the Reporting Services Configuration tool to configure the report server database and service account. Kind Regards, WCC44

Thanks WCC44, I can connect using SQL Server Management Studio so service is definitely running and allows remote connections. Also I am using Reporting Services Config tool to configure database and service account still no luck. When I configure it with local database, it works without problem but as soon as I change database to remote, it starts to complain that remote database is not accessible. Anyone with any clue? Piyush

No one has an answer?

Take a look to this http://support.microsoft.com/kb/2291551

Hello Piyushc, Look over this documentation and the various links with in the documentation to determine whether you have configured everything correctly. You could also log into Reporting Services through SQL Server Management Studio>Right Click your server and choose properties>Choose Advance>Under Security, EnableRemoteErrors = T... This may help you to troubleshoot your remote connection...Also, it isn't advisable to leave EnableReportErrors = T...So when finished set back to False... Kind Regards, WCC44

Thank you all for the help. I am still not able to solve the problem. @Jaime, in my case as I mentioned, the reporting server is installed on Standard Edition and not Data Center Edition. My reporting database is Data Center Edition hosted on a failover cluster. @WCC44, not sure which document you are talking about. When I open Reporting Service Configuration Manager and select Scale-Out deployment tab, I don't see any servers listed there. One more update is that when I connect to Reporting Service using SSMS and try to do any action (like right click on server), I get the unhandled exception dialog box with error Microsoft.SqlServer.ReportingServices.ReportServiceDetailsException: The report server has encountered a configuration error. (rsServerConfigurationError) ---> Microsoft.SqlServer.ReportingServices.ReportServiceMoreInformationException: The report server has encountered a configuration error. (rsServerConfigurationError) --- End of inner exception stack trace --- at Microsoft.SqlServer.Management.UI.RSClient.RSClientConnection.SoapMethodWrapper`1.ExecuteMethod(RSClientConnection rsClientConnection) at Microsoft.SqlServer.Management.UI.RSClient.RSClientConnection.GetSystemPermissions() at Microsoft.SqlServer.Management.UI.RSWrapper.SystemPermissions..ctor(RSClientConnection connection) at Microsoft.SqlServer.Management.UI.RSUserInterface.MenuAccessHandler2.PermissionsCacheItem.get_SystemPermissions() at Microsoft.SqlServer.Management.UI.RSUserInterface.MenuAccessHandler2.EvaluateNode(XPathNavigator navigator, PermissionsCacheItem cache) at Microsoft.SqlServer.Management.UI.RSUserInterface.MenuAccessHandler2.Evaluate(String xmlExpression, INodeInformation source) at Microsoft.SqlServer.Management.UI.RSUserInterface.MenuAccessHandler2.Enabled(INodeInformation source) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolsMenuItemBase.UpdateMenuCommandStatus(MenuCommand menuCommand) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.DefaultMenuHandler.UpdateMenuCommandsStatus(MenuCommand menuCommand) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.DefaultMenuHandler.GetMenuItems(ArrayList items) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.DefaultMenuHandler.GetMenuItems() at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ExplorerHierarchyNode.ShowContextMenu(Point windowPos) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.LazyTreeView.WmContextMenu(Message& m) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.LazyTreeView.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) Anyone with any solution? Piyush

Hello Piyush, Here is the documentation that I had meant to include in my last post... http://msdn.microsoft.com/en-us/library/ms156453.aspx Review Planning for Scale-Out Deployment in SQL Server Books Online for guidelines on when to use a scale-out deployment. Review How to: Install SQL Server 2008 R2 (Setup) in SQL Server Books Online for instructions on how to install report server instances. Review How to: Configure a Report Server Scale-Out Deployment (Reporting Services Configuration) for instructions on how to share a report server database and join report servers to a scale-out. Optionally, if you are configuring the scale-out to run on a network load-balanced cluster, review How to: Configure a Report Server on a Network Load Balancing Cluster for instructions on how to configure view state validation. Kind Regards, WCC44

I am not deploying in Scale-Out topology. I want to have single report server with single remote report database. Anyway, does anyone know if there is a case that Standard Edition Reporting Services can not have Remote Reporting database? Piyush