locked
Unable to connect to the remote server RRS feed

  • Question

  • Hi

    I have installed SQL Server 2014 on my server together with Reporting Services.

    I have an application written in vb that uses the Desktop Report viewer. When the application is running on the server I can access my reports no problem. I have installed the application on a client machine and whilst the program can access the tables in SQL Server with no problem when I try to run a report I get

    "Unable to connect to the remote server. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.5.143:8081"

    The code I am using to access the report in the Report viewer is

    Me.ReportViewer1.ServerReport.ReportServerUrl = New Uri(gstrRepUrl)
            Me.ReportViewer1.RefreshReport()
    
            Me.ReportViewer1.ServerReport.ReportServerCredentials.NetworkCredentials = New System.Net.NetworkCredential("Admin", "Blah", "http://PFSQL:8081/Reportserver_SQLExpress")
    

    where gstrURL is http://PFSQL:8081/reportserver_SQLEXPRESS

    I can ping the server name (PFSQL) from the client but if I enter the report Server detail in Internet Explorer it says it cannot access the server

    Any help really appreciated - I am up against a deadline here.

    Roy


    Roy T

    Tuesday, December 22, 2015 10:58 AM

Answers

  • Hi

    I have found the problem. The firewall on the server was blocking port 8081 (Doh!)

    Thanks

    Roy


    Roy T

    Tuesday, December 22, 2015 1:21 PM

All replies

  • Hello Roy,

    IP port 8081, have you setup this port in SSRS configuration manager? Default is port 80.

    Do you have a Windows Domain or is it only a Workgroup? In a Workgroup Windows authentication for SSRS don't work.


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Tuesday, December 22, 2015 11:10 AM
  • Hi Olaf

    Thanks for your reply

    Yes 8081 is set  up in Config manager

    I believe it is a Domain as it is part of my client's network using windows server 2012

    Roy


    Roy T

    Tuesday, December 22, 2015 11:19 AM
  • Hi

    I have found the problem. The firewall on the server was blocking port 8081 (Doh!)

    Thanks

    Roy


    Roy T

    Tuesday, December 22, 2015 1:21 PM