Troubleshooting: SQL Server 2008 R2 Reporting Services Report Manager URL Shows 500 Internal Server Error in Internet Explorer

December 15, 2011 3 Comments


Well, Going through a serious issue while getting an 500 Internal Server error during hitting up the SSRS 2008 R2 Report Manager URL in Internet Explorer 9 64 bit in elevated mode. Checked the Reporting Services Configuration Manager & seem to be all right as like this.

  •  SQL Server Instance with Reporting Services Configuration Manager.
  • While checked about the Web Services URL , Report Server Database all seemed to be okay.

  • Since , SQL Server 2008 onwards Reporting Services instance works with HTTP runtime (not with IIS) henceforth checked the RSTempfiles folder & given the admin access to the Reporting Services Administrator of the System from Security of the folder.

  • Restarted the SQL Server Reporting services from Services of the Windows but still no success.
  • Henceforth , Checked the Reporting Services Log Files & found the following error:

AppDomain ReportServer_SQLEXPRESS_0 failed to start. Error: Could not load file or assembly ‘Oracle.Web, Version=2.111.7.0, Culture=neutral, PublicKeyToken=89b483f429c47342’ or one of its dependencies. The system cannot find the file specified. (C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Config\machine.config line 176)

  • Checked in Windows Event Viewer & got the suspicious error:

Resolution:

  •  It may seems that reparing the .NET Framework 2.0 will reach the goal but more than that first uninstall the Oracle Client installed on the System as Oracle Client / Oracle Server merely configures Machine.Config of .NET Framework & result is refleced in Event Viewer or Process Monitor.

Issue: Getting Error Previous Installation of Microsoft Visual Studio 2008 during installation of SQL Server 2008 or 2008 R2.

  • Followed by Error prompt like this:

Resolution:

  • If start troubleshoot by uninstalling the SQL Server 2008 then during installation of SQL Server 2008 uninstall VS 2008 (If VS 2008 SP1 is not installed)then  in new instance first install SQL Server 2008 without Integration Services , SQL Server Management Tools(Basic, Complete) & BIDS.
  • Then install again VS 2008 & immediately again update VS 2008 SP1 & then upgrade SQL Server 2008 / 2008 R2 BIDS, SSIS & Management Tools (Basic & Complete) SSMS features.

Filed under Azure SQL Database / SQL Server

About Anindita
Anindita Basak is a Cloud Architect. Worked in as Developer & Senior Developer on Microsoft Azure, Data Platform, IoT & BI , Data Visualization, Data warehousing & ETL & of course in Hadoop platform.She played both as FTE & v- employee in Azure platform teams of Microsoft.Passionate about .NET , Java, Python & Data Science. She is also an active Big Data & Cloud Trainer & would love share her experience in IT Training Industry. She is an author, forum contributor, blogger & technical reviewer of various books on Big Data Hadoop, HDInsight, IoT & Data Science, SQL Server PDW & PowerBI.

3 Responses to Troubleshooting: SQL Server 2008 R2 Reporting Services Report Manager URL Shows 500 Internal Server Error in Internet Explorer

  1. Pingback: Troubleshooting: SQL Server 2008 R2 Reporting Services Report …

  2. dotnetandabhi says:
    December 26, 2011 at 19:43

    Good Post.

    By the way In this very new upcoming version of SQL Server does microsoft paid any attention over pagination of data in SQL server.

    To achieve 10 rows starting from 21st to 30th row following queries are required in respectively in MYSQL and SQL SERVER.

    Like in MySQL it is very easy
    –MySQL
    SELECT * FROM Students ORDER BY Name ASC LIMIT 20,10

    –SQL Server
    SELECT * FROM
    (SELECT ROW_NUMBER() OVER (ORDER BY Name ASC) AS Row, * FROM Students)
    AS StudentsWithRowNumbers
    WHERE Row > 20 AND Row <= 30'

    But to achieve the same in SQL server We have to do some workaround. 😦

    I am waiting for this and few similar features in SQL server since SQL server 2005 release , but I think this time also I have to wait for next version 🙂

    Reply

  3. Pingback: poorly written

Leave a comment