Prev: Back up of Encryption Keys and changing Windows Service Identity
Next: Error: StringStartsWith can't accept null parameters
From: adaher008 via SQLMonster.com on 11 Dec 2007 15:06
I have a named instance of sql Server 2005 (SQLSERVER2005_T) on a Windows
Server 2003. Also during installation Reporting Services was installed on
that instance. I have all the sample databases (AdventureWorks and
AdventureWorksDW) installed. All services related to sql server as reporting
services etc. were installed and run under localsystem accounts.

On web server IIS 6.0, I have two Virtual directories related to Report
Server and Report Manager, ReportServer$SQLServer2005_T, and Report
$SQLServer2005_T respectively.
I ran the sample reports through Visual Studio and they ran fine. However I
could not deploy. Also, when I try to Browose on IIS either ReportServer
$SQLServer2005_T or Report$SQLServer2005_T Virtual Directories, I get the
following error :
------------------------------------------------------------------------------
-----------------------------------------------
Server Error in '/ReportServer$SQLServer2005_T' Application.
------------------------------------------------------------------------------
--
Configuration Error
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly
'ReportingServicesWebServer' or one of its dependencies. Access is denied.

Source Error:

Line 27: <assemblies>
Line 28: <clear />
Line 29: <add assembly="ReportingServicesWebServer" />
Line 30: </assemblies>
Line 31: </compilation>

Source File: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\
ReportServer\web.config Line: 29

Assembly Load Trace: The following information can be helpful to determine
why the assembly 'ReportingServicesWebServer' could not be loaded.


WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\
Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure
logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\
Fusion!EnableLog].

------------------------------------------------------------------------------
--
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET
Version:2.0.50727.42
------------------------------------------------------------------------------
-----------------------------------------------
I wonder what I am doing wrong. Please Help.

Thank You in Advance -

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200712/1

 | 
Pages: 1
Prev: Back up of Encryption Keys and changing Windows Service Identity
Next: Error: StringStartsWith can't accept null parameters