locked
Unable to connect to the remote server RRS feed

  • Question

  • I have an Azure VM setup with a website and SQL Server Reporting Services. The site uses a ReportViewer object to render the reports which grabs the data from our data server and displays the report on the web page. The whole system worked fine until earlier this week when, out of the blue, the webpage would give this error: 

        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 137.135.9.93:80

      The webpage loaded but the place where the report usually renders gave the error message. We have done many checks including restarting the report server, rebooting both website and data servers, update the servers, check the configuration files but we cannot figure out what is going on. The reports will even run from the SQL Server Reporting Services webpage but will not load from the website. What is goingon here and why won't this work?

    Thursday, April 23, 2015 8:54 PM

Answers

  • Hi 

    I suggest you try these steps first;

    1. RESTART : In case if there is a storage timeout, restarting the VM from the management portal might get it work

    2. RESIZE: In case if restart does not help, you could temporarily rezise the VM core from the portal, as rezing will move it to a different host . Please note that resizing the VM will get you a new NIC and D (temporary Drive)

    3.  RECREATE: If the above mentioned steps fail you coulkd start fresh and delete the VM BUT KEEP THE DISC, and create a new VM using the Disc. ( However you could wait for a day before trying this steps as most of the times connectivity is restored.)

    Hope this helps.

    Warm Regards;

    Shreya hajela

    Friday, April 24, 2015 7:25 AM

All replies

  • Hi 

    I suggest you try these steps first;

    1. RESTART : In case if there is a storage timeout, restarting the VM from the management portal might get it work

    2. RESIZE: In case if restart does not help, you could temporarily rezise the VM core from the portal, as rezing will move it to a different host . Please note that resizing the VM will get you a new NIC and D (temporary Drive)

    3.  RECREATE: If the above mentioned steps fail you coulkd start fresh and delete the VM BUT KEEP THE DISC, and create a new VM using the Disc. ( However you could wait for a day before trying this steps as most of the times connectivity is restored.)

    Hope this helps.

    Warm Regards;

    Shreya hajela

    Friday, April 24, 2015 7:25 AM
  • Thank you for your help. The issue wound up being an IIS port conflict with another one of our sites on the server. I will keep your advice in mind for future connectivity issues. Thanks!
    Wednesday, April 29, 2015 6:59 PM