We had a pretty uneventful CRM installation, the product installed on the
first attempt with no errors, and all aspects of it appear to operate correctly
with the exception of Reports. When opening the reports node in CRM, we were
getting the ever so useful "An Error has occurred, please contact your system
administrator". I enabled verbose error messages in the web.config file and
captured the followng error message.

=========
Microsoft CRM Unhandled Error Details:
Server Error in '/' Application.
--------------------------------------------------------------------------------

Compilation Error
Description: An error occurred during the compilation of a resource required
to service this request. Please review the following specific error details
and modify your source code appropriately.

Compiler Error Message: CS0011: Referenced class 'Microsoft.Crm.Util' has
base class or interface 'Microsoft.Crm.SharedUtil' defined in an assembly
that is not referenced. You must add a reference to assembly 'Microsoft.Crm'.
=========

This is followed by 500 odd lines of "autogenerated" source code for "public
class home_reports_aspx" which I can include if necessary.

SQL Reporting services is working fine and when accessed directly on its
URL we can view and run the reports that CRM created during the install;
so I don't think this is a problem with Reporting Services. Furthermore,
when I use the Deployment Manager to specify a different, non existent Reporting
Services URL I still get the same error message, which would indicate that
CRM is failing before it even attempts to connect to the reporting server.

CRM and SQL Reporting Server are on the same front-end machine but running
under different IIS virtual servers. This is Windows Server 2003 32 bit edition
with SP2. CRM has rollup 2 applied, and Reporting Services has SQL 2005 SP2
applied.

The backend server is Windows Server 2003 64 bit edition running SQL 2005
Standard x64.

Any thoughts - no matter how trivial - would be greatly appreciated.

kind regards,
Paul Ritchi

Re: Error Opening Reports Node on New Installation. by Darren

Darren
Thu Aug 09 18:09:02 CDT 2007

Hi Paul,

Can you check your IIS to see if CRM is running in .Net version 1.1
and the MSCRMService Virtual Directory is also running .net 1.1. If
not, please change it to .net 1.1 and do an iisreset to try again to
see if it works.

Darren Liu
Crowe
http://www.crowecrm.com

On Aug 9, 4:47 pm, Paul Ritchie <REMOVEpritc...@xtraREMOVE.co.nz>
wrote:
> We had a pretty uneventful CRM installation, the product installed on the
> first attempt with no errors, and all aspects of it appear to operate cor=
rectly
> with the exception of Reports. When opening the reports node in CRM, we w=
ere
> getting the ever so useful "An Error has occurred, please contact your sy=
stem
> administrator". I enabled verbose error messages in the web.config file a=
nd
> captured the followng error message.
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D
> Microsoft CRM Unhandled Error Details:
> Server Error in '/' Application.
> -------------------------------------------------------------------------=
--=AD-----
>
> Compilation Error
> Description: An error occurred during the compilation of a resource requi=
red
> to service this request. Please review the following specific error detai=
ls
> and modify your source code appropriately.
>
> Compiler Error Message: CS0011: Referenced class 'Microsoft.Crm.Util' has
> base class or interface 'Microsoft.Crm.SharedUtil' defined in an assembly
> that is not referenced. You must add a reference to assembly 'Microsoft.C=
rm'.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> This is followed by 500 odd lines of "autogenerated" source code for "pub=
lic
> class home_reports_aspx" which I can include if necessary.
>
> SQL Reporting services is working fine and when accessed directly on its
> URL we can view and run the reports that CRM created during the install;
> so I don't think this is a problem with Reporting Services. Furthermore,
> when I use the Deployment Manager to specify a different, non existent Re=
porting
> Services URL I still get the same error message, which would indicate th=
at
> CRM is failing before it even attempts to connect to the reporting server.
>
> CRM and SQL Reporting Server are on the same front-end machine but running
> under different IIS virtual servers. This is Windows Server 2003 32 bit e=
dition
> with SP2. CRM has rollup 2 applied, and Reporting Services has SQL 2005 S=
P2
> applied.
>
> The backend server is Windows Server 2003 64 bit edition running SQL 2005
> Standard x64.
>
> Any thoughts - no matter how trivial - would be greatly appreciated.
>
> kind regards,
> Paul Ritchie



Re: Error Opening Reports Node on New Installation. by George

George
Mon Aug 13 08:07:41 CDT 2007

Hi Paul,

did you check if Microsoft.Crm is in assembly cache (it should be as well as
15+ other Microsoft.Crm.* assemblies)?

Hope this helps
--
George Doubinski
CRM Certified Professional - Developer


"Paul Ritchie" <REMOVEpritchie@xtraREMOVE.co.nz> wrote in message
news:285ed51b1907b8c9a94aaa20d8be@news.microsoft.com...
>
> We had a pretty uneventful CRM installation, the product installed on the
> first attempt with no errors, and all aspects of it appear to operate
> correctly with the exception of Reports. When opening the reports node in
> CRM, we were getting the ever so useful "An Error has occurred, please
> contact your system administrator". I enabled verbose error messages in
> the web.config file and captured the followng error message.
> =========
> Microsoft CRM Unhandled Error Details: Server Error in '/'
> Application. --------------------------------------------------------------------------------
>
> Compilation Error Description: An error occurred during the compilation of
> a resource required to service this request. Please review the following
> specific error details and modify your source code appropriately.
> Compiler Error Message: CS0011: Referenced class 'Microsoft.Crm.Util' has
> base class or interface 'Microsoft.Crm.SharedUtil' defined in an assembly
> that is not referenced. You must add a reference to assembly
> 'Microsoft.Crm'.
> =========
>
> This is followed by 500 odd lines of "autogenerated" source code for
> "public class home_reports_aspx" which I can include if necessary.
>
> SQL Reporting services is working fine and when accessed directly on its
> URL we can view and run the reports that CRM created during the install;
> so I don't think this is a problem with Reporting Services. Furthermore,
> when I use the Deployment Manager to specify a different, non existent
> Reporting Services URL I still get the same error message, which would
> indicate that CRM is failing before it even attempts to connect to the
> reporting server.
> CRM and SQL Reporting Server are on the same front-end machine but running
> under different IIS virtual servers. This is Windows Server 2003 32 bit
> edition with SP2. CRM has rollup 2 applied, and Reporting Services has SQL
> 2005 SP2 applied.
> The backend server is Windows Server 2003 64 bit edition running SQL 2005
> Standard x64.
>
> Any thoughts - no matter how trivial - would be greatly appreciated.
>
> kind regards,
> Paul Ritchie
>
>