Tuesday, September 1, 2015

You receive "Exception has been thrown by the target of an invocation" when running some reports in Management Reporter 2012 CU13

In my previous post, I talked about a cryptographic exception I encountered while upgrading Management Reporter 2012 from CU6 to CU9 (on the way to CU13), while attempting to setup the Data Mart database - see You receive "Could'n retrieve the list of available databases: The connection attempt failed" error when updating Management Reporter 2012. The solution turned out to be very simple, but in the scheme of things a bit time consuming to figure out. Once we had upgraded to CU9, it was time to attempt the upgrade to CU13.

The upgrade process

Upgrading to CU13 was pretty straight forward.  However, after the upgrade, the customer attempted to generate a couple of the many reports from Report Designer with the following error being displayed in Web Viewer:

This report can't be displayed. Make sure that your computer has an internet connection and that Management Reporter is running. If this problem continues, contact your administrator.

Image
Management Reporter 2012 CU13 error when generating report to Web Viewer

When attempting to open the same report from Report Viewer, we obtained the following exception error, with the Report Viewer application crashing after clicking the OK button:

Exception has been thrown by the target of an invocation.

Image

After the errors, we tried copying the columns, row definitions, and trees onto completely new report objects (rows, columns, and trees), respectively, and tried to run the reports once more, obtaining the same results. The customer relies on this report on a daily basis, so it was critical we fix whatever issue was causing these reports to crash.

After some back and forth with Microsoft Support, it was determined that with CU13 the B0 print control in the row is not working and causing the exception:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidCastException: Specified cast is not valid.

Microsoft Support is currently working on getting the issue written up and triaged so as soon as a bug number (or a fix!) is available I will publish more about it.

As it stands, we reverted back to CU9 and upgraded to CU12 which did not display the issue described herein.

Until next post!

MG.-
Mariano Gomez, MVP

2 comments:

Kevin said...

Have you had any updates from Microsoft on this issue? We are seeing this exact issue on our test server.

Ven Sharma said...

Mario - Thank you. This post is so invaluable and is saving a bunch of time and effort. Was this with the CU13 re-release + hotfix (performance improvements)?