Can't email Snapshot report (SSRS subscription)

(1) Share

Report

Posted on by Joe Woltering

12,163

Trying to schedule the e-mailing of a CRM Snapshot report by creating a subscription in SSRS. The e-mail send fails with the error: "Failure sending mail: Failed to load expression host assembly. Details: Could not load file or assembly 'Microsoft.Crm.Reporting.RdlHelper, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies."

I tried updating the Version # to 6.0.0.0 (and even 7) per some articles online but this has not resolved it. Every time, it continues to show 5.0 as the version.

*This post is locked for comments

I have the same question (0)

All responses (26)

Answers (1)

Rajkumar Rajaraman on at

Like (0)

Report

Have you referred this?

nishantrana.me/.../could-not-load-file-or-assembly-microsoft-crm-version5-0-0-0-cultureneutral-publickeytoken31bf3856ad364e35-or-one-of-its-dependencies-the-system-cannot-find-the-file-specified-or-deploying

Was this reply helpful? Yes No
Joe Woltering 12,163 on at

Like (1)

Report

No, that did not resolve it. Also, my issue is in 2015, not 2011.

Was this reply helpful? Yes No
Joe Woltering 12,163 on at

Like (1)

Report

It would appear that when CRM creates the report it is defaulting it to Version 5.0.0.0. This must be a bug as the SSRS Reporting Extensions use Version 6.0.0.0

Was this reply helpful? Yes No
Joe Woltering 12,163 on at

Like (1)

Report

This is what's in my SSRS log:

LOG: This bind starts in default load context.

LOG: Using application configuration file: C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer\bin\ReportingServicesService.exe.Config

LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v2.0.50727\config\machine.config.

LOG: Post-policy reference: Microsoft.Crm.Reporting.RdlHelper, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

LOG: Attempting download of new URL file:///C:/Program Files/Microsoft SQL Server/MSRS12.MSSQLSERVER/Reporting Services/ReportServer/bin/Microsoft.Crm.Reporting.RdlHelper.DLL.

WRN: Comparing the assembly name resulted in the mismatch: Major Version

ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.

Was this reply helpful? Yes No
Joe Woltering 12,163 on at

Like (1)

Report

The assemblies would appear to be correct in the web.config on the SSRS server:

<dependentAssembly>

<assemblyIdentity name="Microsoft.Crm.Reporting.RdlHelper" publicKeyToken="31bf3856ad364e35" culture="neutral" />

<bindingRedirect oldVersion="5.0.0.0" newVersion="7.0.0.0" />

<bindingRedirect oldVersion="6.0.0.0" newVersion="7.0.0.0" />

</dependentAssembly>

Was this reply helpful? Yes No
Joe Woltering 12,163 on at

Like (0)

Report

I have tried reinstalling the Reporting Extensions but still same error.

Was this reply helpful? Yes No
Verified answer

Joe Woltering 12,163 on at

Like (2)

Report

Wow, finally got it! This is 100% a bug in the way the assembly is loaded to process the report on the SSRS side-- perhaps having to do with a combination of CRM 2015 and SQL 2014 SSRS (not really sure, nor do I care at this point). If anyone is having the same problem, and would like to know the fix, send me a PM.

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

Dear All,

Would it be possible to share this answer? I have exactly the same problem ... and looks really like a bug. Not fixed in 0.2 update if i read well the release notes.

Thanks a lot !

Was this reply helpful? Yes No
Varun Singh 943 on at

Like (0)

Report

HI Joe Dubs,

I have updated the reference in the below two path web.config but still not working.

Do I need to update somewhere else also. Would you please help me.

C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer

C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportManager

Was this reply helpful? Yes No
Joe Woltering 12,163 on at

Like (0)

Report

What error(s) are you seeing in your SSRS log?

* You may need to enable Fusion logging to get additional information about the error.

Was this reply helpful? Yes No