Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

SSRS Unable to deploy project with custom assembly to SQL 2012

Posted on 2014-11-20
3
Medium Priority
?
1,261 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 1000 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

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In part one, we reviewed the prerequisites required for installing SQL Server vNext. In this part we will explore how to install Microsoft's SQL Server on Ubuntu 16.04.
What if you have to shut down the entire Citrix infrastructure for hardware maintenance, software upgrades or "the unknown"? I developed this plan for "the unknown" and hope that it helps you as well. This article explains how to properly shut down …
Familiarize people with the process of utilizing SQL Server functions from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Ac…
Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties

971 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