Thursday, September 17, 2015

Microsoft Dynamics GP Web Client no longer working on Google Chrome 45

If you had gotten used to running the Microsoft Dynamics GP web client on Google Chrome, chances are you have just woken up to the constant requests for installing the Silverlight plugin. You may have attempted the installation a few times by now, only to notice that you are still being requested to install Silverlight.

Microsoft Dynamics GP Web Client on Chrome 45 

Google Chrome users who normally relied on functionality that NPAPI plugins provided won't be able to make use of them anymore with the release of Chrome 45. NPAPI-only plugins such as Java or Silverlight are used throughout the web and while their use is declining, there are numerous applications and services that make use of either one or another plugin - for example, your beloved Microsoft Dynamics GP web client.

This Chrome Extensions article explains the security concerns behind the use of NPAPI-based plugins, mainly, the ability of said plugins to gain access to a user's local machines. Any security gaps in such plugins would render a user's machine vulnerable to exploits by malicious code.

However, this should not at all come as a surprise, since Google had it in the works to remove NPAPI support since September of 2013, see Saying Goodbye to Our Old Friend NPAPI, with Chrome 45 selected as target for final deprecation.

So what are the alternatives?

Well, you can fall back once more to Internet Explorer 10 (desktop), Mozilla Firefox, or even Apple's Safari. If my mind serves me correctly, the latter two will have some minor limitations (as in "may not be fully compatible").

Option number 2 would have you downgrading Chrome, if you are willing to get the installer from non-Google sites like Old Apps or File Hippo.

As a final note, the following browsers DO NOT support Silverlight:

Microsoft Internet Explorer 10 modern UI
Microsoft Edge (formerly code name Spartan, available on Windows 10)
Google Chrome (version 45 and above)
Opera (version 20 and above, current version is 32)

Until next post!

MG.-
Mariano Gomez, MVP

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