Want to configure Report server to use SSL

Hi,

• I created a Report using Business Intelligence Studio. Its working working well, i can able to view records. But when i try to deploy the report an error occurs specifying that "A connection could not be made to the report server http://localhost/ReportServer. (Microsoft Report Designer)".
• I open the IIS 7 and find out virtual directories "Reports" and "ReportServer" are available.
• I check on the browser and type "http://localhost/reports".  I find the browser direct to this url: http://localhost/reports/Pages/Folder.aspx and find error specifying the following one:

         Error:The report server is not responding. Verify that the report server is running and can be accessed from this computer.

• when i type http://localhost/reportmanager, i found the error:

  HTTP Error 404.0 - Not Found

  The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

  <
  

Custom report items in SQL Server 2005 Reporting Services address your needs for custom reports without the pain of doing it from scratch.

Teo Lachev

MSDN Magazine October 2006

Reporting has always been one of the dark arts of development. The tools typically seem to do just enough to get you to a certain point, then leave you to find workarounds to solve more complex issues.

John Papa

MSDN Magazine July 2006

To help stop the spread of worms, viruses, and other hostile activity, it is important to track down and report the servers used in these attacks along with those used to send spam. Many Web administrators, however, don't take the time to track them because the manual process can be quite cumbersome. The Microsoft .NET Framework comes to the rescue with several networking classes, including the Dns class and the TcpClient class, that abstract away the complexity of performing DNS and WHOIS lookups. These classes make it easy to create a simple, straightforward ASP.NET-based utility for performing these lookups and automating this very important task.

G. Andrew Duthie

MSDN Magazine April 2002

We have installed Reporting Services 2008 integrated with MOSS with SQL Server 2008 on a 64 bit platform.

The environment has worked fine in test (but the servers are not hardend).

With the production environment, any attempt to export from a report into another format (eg excel, tiff etc) results in an unexpected error within SharePoint requiring closing the browser and reopening.

There are no details behind the error. We can also find no traces of the error within any of the logs (SharePoint, Reporting Services, Windows event log etc)

When the report is opened directly from Reporting Services (ie http://servername:8080/reportserver) the report exports fine. Similarly, if the report is opened directly from Report Builder 2, or through opening Report Builder 2 from SharePoint there is no issue. This issue only happens when the report is invoked directly through SharePoint.

We can only assume that this issue has something to do with server hardening/UAC as we have

I configured reporting services integrated with Share Point. I can able to access the report server URL using firefox. But, i am unable to browse to the URL using IE. Anyone, please shed some light on this. I can able to access URL in IE by using IP address:

Example : [Firefox]

http://systemname/reportserver      {accessible}

Example : [Internet Explorer]

http://systemname/reportserver      {Not accessible}

http://IPADDRESS/reportserver    {accessible}

Thanks,

Gautam