Reporting Services failure

I am on TFS Beta 3, and haven't used the reporting stuff much (I did get it up and running after install). Just went to run a report and got the following:

An error has occurred during report processing. (rsProcessingAborted)

Could not load file or assembly 'Microsoft.ReportingServices.Modeling' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)

Any idea what it could be I'm the administrator on the machine (ran it on the TFS server machine in order to get the message). Haven't done any shenanigans with SQL Server 2005 on that machine (running developer edition). Happens on any and all reports when I go to run the report itself.

Answer this question

Reporting Services failure

Cliff Williams
As far as I can tell, the Microsoft.ReportingServices.Modeling assembly is part of the SQL BI tools. The assembly is located in %programfiles%\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies on my machine. If Bryan's suggestion does not reveal the source of the problem, you might try uninstalling the SQL BI tools to see if that helps. The other thing to do is to find the assembly and take a close look at version numbers. Does it match all of the other SQL binaries on your machine
paul9955
Can you see report contents when browsing to the project node under http://<server>/reports using IE or is this just a problem when viewing reports using the Team Explorer How about IE from a different machine
Ashvin Patel
That was it! The version of the dll in c:\program files\Microsoft SQL Server\MSSQL.3\ReportingServices\ReportServer\bin failed the sn -v test.

The version that ws in C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies passed it, so I renamed the bad file in both the ReportingServices directory and the cache area and copied in the good file and all was fine.

The file version looked identical, but obviously was bad. I'll chalk it up to the phase of the moon for now, but at least this documents the fix.

Thanks!
frogggy
Did you do the search from a command line window: dir /s c:\Microsoft.ReportingServices.Modeling*

What could be happening is that this dll might possibly in your gac %windir%\assembly foder or you could have an invalid version of this dll somehow resulting from your upgrades.

Please do the following to verify you have a valid version (strongly signed version of the dll):

From the .net SDK tools use the SN tool:

sn -v Microsoft.ReportingServices.Modeling.dll

it should teall you something like:

Microsoft (R) .NET Framework Strong Name Utility Version 2.0.50608.0
c Microsoft Corporation. All rights reserved.

Assembly 'Microsoft.ReportingServices.Modeling.dll' is valid

Furthermore you can use the filever tool or property sheet to look at the version information of the file. I get the following when I run this:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies>filever Microsoft.ReportingServices.Modeling.dl
l
--a-- W32i DLL - 9.0.1399.0 shp 576,216 10-14-2005 microsoft.reportingservices.modeling.dll

Thanks,

Dan
AlpEren

Bruce, were you able to fix the problem Consider upgrading to the RC, as there have been a significant number of fixes made after beta 3.

Buck
AmA-Nique
If I browse to http://<server>/reports, it brings up the normal Reporting Services menu and displays all my projects. But when I run any report it dies with the message. I've tried IE from two different machines (it gives a more cryptic message if you don't run it from the server machine and tells you to run it on the server to see the full message).
JTSTAR
The version and time/date information on the assembly match what I have on my machine.

You should be able to just uninstall/reinstall SQL Reporting Services rather than all of SQL to try to fix the problem.

The presence of a temporary ASP.NET assembly on your machine made me go back and look at my TFS application tier machine. It looks like the Microsoft.ReportingServices.Modeling assembly is not just a part of the SQL BI tools (which are installed on my data tier machine). The modeling assembly is also used as part of the ReportServer site. That makes the report generation errors make more sense, but still does not explain the trouble you are having. The assembly that is the source of the temporary ASP.NET copy should be visible in the Default Web Site/ReportServer/bin folder of inetmgr.exe. It is physically present under the %programfiles%\Microsoft SQL Server\MSSQL.1\Reporting Services\ReportServer\bin subdirectory when SQL Reporting Services is working properly.
Raj83475454
I did a search on Microsoft.ReportingServices.Modeling.* and found the same version of the dll (version 9.0.1399.0) dated 10/14/2005 3:43 am.

One of the versions had a different date, but the same size and internal version number. It was in:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\reportserver\55a9c3a5\2dd8b450\assembly\dl3\d4977d94\002cac5d_9bd0c501

I tried renaming it and copying in one from program files, but it didn't make any difference.

There are no other reports listed. I tried creating a new report and it gave a message saying no models were found.

The TFS server was built first from beta 2, and then upgraded to beta 3 (with a complete uninstall/re-install of sql server). I'm pretty sure I ran some reports when I upgraded it, but am not positive. I suppose I could try a complete uninstall/reinstall of sql server and re-attach all the dbs, but I'd still like to know what's going on...
Timothy Wilson
Can you run a non-TFS report It seems like Reporting Services rendering is broken since it can't load one of it's dlls.
Reporting Services failure

Answer this question