Solved

SSRS Unable to deploy project with custom assembly to SQL 2012

Posted on 2014-11-20
3
780 Views
Last Modified: 2014-11-21
Using Visual Studio 2013 with BI I created a SSRS project which I have been successfully deploying for months.  This week I created a customer assembly DLL and referenced it in all the project's reports.  While this works on my development machine I am unable to deploy it to my SQL Server 2012 server with the following error:


Error rsProcessingError : Error while loading code module: ‘DSSFunctions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’.
Details: Could not load file or assembly 'DSSFunctions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.

I believe this is down to the referenced Microsoft.ReportingServices.ProcessingObjectModel.  This is version 12 on my development machine but is 11 on the server.
0
Comment
Question by:canuckconsulting
  • 2
3 Comments
 
LVL 10

Accepted Solution

by:
Walter Padrón earned 500 total points
ID: 40456111
The .Net framework on the server is older than the framework on your developer machine.
You can install a newer version on the server or set the project that build the custom DLL to target an older framework version.

Best regards
0
 

Author Comment

by:canuckconsulting
ID: 40456412
That doesn't appear to be the case here.  I took screenshots of the relevant registry entries and the framework match at 4.5.1  as per the definitions below:

.Net Framework Versions
Server .Net version
Development .Net version
I also ran CLRVER.EXE on both systems showing they have the same versions:

CLRVER Results Side by SideI really think it's that ProcessingObjectModel but can't work out how to get to the next step.
0
 

Author Closing Comment

by:canuckconsulting
ID: 40457805
Turned out to be related to .Net version with the issue being SSRS itself was built using .Net 3.5 and .20.  I rebuilt my project to .Net 3.5 and worked.

For me another issue was the version of Microsoft.ReportingServices.ProcessingObjectModel which I required to be able to pass parameters from my report to the custom assembly.  On my development machine my custom assembly is built using version 12 of the DLL.  However when deploying to SQL 2012 I need to use a version of the assembly instead referencing version 11 which I copied rom the target machine.  This is a bit messy for now but at least it works.
0

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

A long time ago (May 2011), I have written an article showing you how to create a DLL using Visual Studio 2005 to be hosted in SQL Server 2005. That was valid at that time and it is still valid if you are still using these versions. You can still re…
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now