Running Reports from a SSRS Scale-Out instance
Hi to all, First of all, thanks for the good information that usually all of us can find here to solve our problems with SQL. Now I'm going to try to explain my problem. Following some of the Q&A published here, I have installed a SSRS Scale-Out environment with 2 SSRS Web instances and an external SSRS DB repository. After that, I have published some rdl files without any kind of problems. The problem that I found is the following, if in one of my SSRS Web instances I call to the report using localhost (http://localhost:9000/Reports/Pages/Report.aspx?ItemPath=%2fMy+Reports%2fEQUIPOS_HW+-+RMA), the report works perfectly and I can see the data obtained from an OLAP cube in SSAS, but if I call to the report using any other way to call to the system (example: IP, hostname, etc. --> http://127.0.0.1:9000/Reports/Pages/Report.aspx?ItemPath=%2fMy+Reports%2fEQUIPOS_HW+-+RMA), I receive this kind of error: Error al procesar el informe. (rsProcessingAborted) No se puede crear una conexión al origen de datos 'EQUIPOS_HW'. (rsErrorOpeningConnection) The connection either timed out or was lost. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. An existing connection was forcibly closed by the remote host I have tested changing the different values in the SSRS Configuration tool (connection users, ports and binding (serve in all assigned or serve in all unassigned)) but in all the test the error is the same. Do you know how solve this problem? Thanks in advance and best regards.
April 11th, 2011 1:02pm

Hi Simkin99, From your scenario, my understanding is that you cannot access the reports through IP, hostname, etc. Please correct me if my understanding is wrong. It sounds like you may have the two websites on the same port and typing the servername or IP address causes conflict. When you install multiple instances of Reporting Services on the same computer, the Report Server Web service and Report Manager must have at least one URL reservation each. The entire set of reservations must be unique in HTTP.SYS. You can vary the port, host name, or virtual directory name to create a unique URL. As for the 127.0.0.1, this is the IPv4 address used to access to localhost, it only supports local administration on the report server computer. If you select this value, only users who are logged on locally to the report server computer will have access to the application. If the issue still exists, could you please supply more information about the issue, such as what steps you have taken to configure the two web services and report manager URLs, and if the report server database and the two web service instances are installed on one computer and so on, and then we could help you better. For more information, please refer to the following article: URL Reservations for Multi-Instance Report Server Deployments: http://msdn.microsoft.com/en-us/library/bb677369(v=SQL.100).aspx Thank you, Eileen
Free Windows Admin Tool Kit Click here and download it now
April 14th, 2011 4:17am

Hi Simkin99, From your scenario, my understanding is that you cannot access the reports through IP, hostname, etc. Please correct me if my understanding is wrong. It sounds like you may have the two websites on the same port and typing the servername or IP address causes conflict. When you install multiple instances of Reporting Services on the same computer, the Report Server Web service and Report Manager must have at least one URL reservation each. The entire set of reservations must be unique in HTTP.SYS. You can vary the port, host name, or virtual directory name to create a unique URL. As for the 127.0.0.1, this is the IPv4 address used to access to localhost, it only supports local administration on the report server computer. If you select this value, only users who are logged on locally to the report server computer will have access to the application. If the issue still exists, could you please supply more information about the issue, such as what steps you have taken to configure the two web services and report manager URLs, and if the report server database and the two web service instances are installed on one computer and so on, and then we could help you better. For more information, please refer to the following article: URL Reservations for Multi-Instance Report Server Deployments: http://msdn.microsoft.com/en-us/library/bb677369(v=SQL.100).aspx Thank you, Eileen Hi Eileen, I'm try to clarify it. My database server (SQL 2008 R2) has installed: IIS, DB Engine, SSIS, SSAS and SSRS configured to serve the reports in "all assigned URL" using port 9000. Here I create the reports and I can run them usign http://localhost:9000/Reports/Pages/.... and using http://<hostname>/....Reports/Pages/ Furthermore, I have 2 other machines with IIS, DB Engine and RS to complete a Scale-Out environment with three nodes. In each one of this other machines, I have applied the same RS configuration than in the first one (serve in "all assigned URL" using port 9000) but here, only using http://localhost:9000/Reports/Pages/.... the reports runs correctly. The configuratión that I have applied in the three machines for RS is: 1. Service Account. I'm using a domain account with all privileges in OS and DB (for complete this test only) 2. Web Service URL: I'm using the default virtual directory with IP Address = All Assigned, TCP Port =9000 and without certificates. 3. Database: I'm connecting to the database server IP with SQL credentials with all privileges in DB (for complete this test only). The connection test was completed without error. 4. Report Manager URL: I'm using the default virtual directory and port 9000. I haven't configured anything special for "E-mail Settings", "Execution Account" and "Encryption Keys" and in "Scale-Out Deployment" I have the three servers joined. I haven't made any other configuration neither in the web servers nor in the db server. Waiting that this info can clarify the problem. Thanks for your help.
April 14th, 2011 11:41am

I assume you can manage your reports via http://127.0.0.1/xxxx more interested to see your datasource definition - EQUIPOS_HW, This is a very interesting error 'An existing connection was forcibly closed by the remote host', looks like your sql server disconnected you.If you think my suggestion is useful, please rate it as helpful. If it has helped you to resolve the problem, please Mark it as Answer. http://twitter.com/7Kn1ghts
Free Windows Admin Tool Kit Click here and download it now
April 14th, 2011 12:01pm

I assume you can manage your reports via http://127.0.0.1/xxxx more interested to see your datasource definition - EQUIPOS_HW, This is a very interesting error 'An existing connection was forcibly closed by the remote host', looks like your sql server disconnected you. If you think my suggestion is useful, please rate it as helpful. If it has helped you to resolve the problem, please Mark it as Answer. http://twitter.com/7Kn1ghts Hi SevenKnights, That was "Great End", if in the Web servers, I use 127.0.0.1 instead of localhost, the error appears again. I didn't say it before because I didn't want to complicate more the explanation. About the datasource: <DataSources> <DataSource Name="EQUIPOS_HW"> <ConnectionProperties> <DataProvider>OLEDB-MD</DataProvider> <ConnectString>Data Source=win-p3d62011n13;Initial Catalog=SSAS_ENRIQUE</ConnectString> <IntegratedSecurity>true</IntegratedSecurity> </ConnectionProperties> <rd:SecurityType>Integrated</rd:SecurityType> <rd:DataSourceID>2725c462-4c93-48c1-bd15-7dc54f53ffdc</rd:DataSourceID> </DataSource> </DataSources> Thanks for your help too.
April 14th, 2011 1:00pm

what's your SSAS connection setup? only one connection per user? Or did you set your datasource/report to use persistent connection?If you think my suggestion is useful, please rate it as helpful. If it has helped you to resolve the problem, please Mark it as Answer. http://twitter.com/7Kn1ghts
Free Windows Admin Tool Kit Click here and download it now
April 14th, 2011 5:42pm

Hi SevenKnights, In SSAS I have using this connection string: Provider=SQLNCLI10.1;Data Source=WIN-P3D62011N13;Integrated Security=SSPI;Initial Catalog=DWH_TICPLUS_ENRIQUE with max connection=10 and ImpersonateServiceAccount I have tried to raise the number of connection and the security to SQL credentials: Provider=SQLNCLI10.1;Data Source=WIN-P3D62011N13;Persist Security Info=True;Password=**********;User ID=**********;Initial Catalog=DWH_TICPLUS_ENRIQUE but without good news. Thanks and regards
April 15th, 2011 5:48am

Simkin99 here you can see there is a difference : Data Source=win-p3d62011n13;Initial Catalog=SSAS_ENRIQUE Data Source=WIN-P3D62011N13;Integrated Security=SSPI;Initial Catalog=DWH_TICPLUS_ENRIQUE So I am not sure whether connection is used in your report. but from the error message, apparent the first one was used. You have to look at the first one connection setup. and why SSAS close your connection. You may be able to find some useful information in the SSAS log.If you think my suggestion is useful, please rate it as helpful. If it has helped you to resolve the problem, please Mark it as Answer. http://twitter.com/7Kn1ghts
Free Windows Admin Tool Kit Click here and download it now
April 15th, 2011 7:58am

Hi to all, Sorry for delay but we have a lot of work the last days. At the end we have changed our idea and now, we are going to use the Report Viewer control from an aspx site instead a Scale Out environment to publish the reports. Thanks for your kind help and best regards. Simkin
April 27th, 2011 7:46am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics