Reporting Services 2012 deploy error: “Error while loading code module”

11
votes

I am trying to deploy a report to the server with a custom assembly for the first time. I am able to deploy the same report without the assembly. I am using Reporting Services 2012 (Visual Studio 2010) to deploy the report.

Here is the full error message I get when I try to deploy:

Error while loading code module: ‘SGA.Reporting, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’. Details: Could not load file or assembly 'SGA.Reporting, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

I have read several posts on this same issue, not of which have solved my problem. It's a dll compiled for .NET Framework 4.0, AnyCPU.

On my local PC where I'm deploying from I've copied my dll to all these folders: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PublicAssemblies C:\Windows\Microsoft.NET\Framework\v4.0.30319 C:\Windows\Microsoft.NET\Framework64\v4.0.30319

On the server I'm deploying to I've copied my dll to these all these folders: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PublicAssemblies C:\Windows\Microsoft.NET\Framework\v4.0.30319 C:\Windows\Microsoft.NET\Framework64\v4.0.30319

Any ideas?

3
reporting-services

3 Answers

12
votes

It turned out I needed to copy the dll to this folder on the report server: %ProgramFiles%\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\bin

That is the only place it is needed on the report server if you just want to deploy reports to it.

3
votes

I had similar problems. I only had it in the public assemblies. Once I added the dll to the private assemblies location it worked. Are you running VS as administrator?

1
votes

Another solution is to deploy your assembly to GAC. You will need to "strong name" it to be able to deploy to GAC. When it is in GAC, you don't need to have it in Reporting Services\ReportServer\bin