‘Management Reporter Configuration Console has stopped working’ and/or ‘Unexpected end of file’

Exception has been thrown by the target of an invocation’ in Management Reporter
September 24, 2017
Ramping up for GP Year End
October 21, 2017

‘Management Reporter Configuration Console has stopped working’ and/or ‘Unexpected end of file’

If you are receiving the error, ‘Management Reporter Configuration Console has stopped working,’ when trying to launch the Management Reporter Configuration Console and you have already tried to clear out the Application log file in Event Viewer (https://community.dynamics.com/gp/b/dynamicsgp/archive/2015/10/08/mr-configuration-console-crashes-when-opening) but still receive the same error, chances are you are also getting an ‘Unexcepted end of file’.


Problem Details are:

Problem signature:

Problem Event Name:  CLR20r3

Problem Signature 01:  MRConfigurationConsole.exe

Problem Signature 02:  2.12.14001.45

Problem Signature 03:  564f9134

Problem Signature 04:  System.Runtime.Serialization

Problem Signature 05:  4.0.30319.36415

Problem Signature 06:  59a6751a

Problem Signature 07:  123a

Problem Signature 08:  85

Problem Signature 09:  System.Xml.XmlException

OS Version:       6.1.7601.

Locale ID:          1033

Additional Information 1:           867d

Additional Information 2:           867d11b32ce19f476cdf9251d2415a17

Additional Information 3:           cbe6

Additional Information 4:           cbe68bc31718fdf21159846c7949db9c


Read our privacy statement online:



If the online privacy statement is not available, please read our privacy statement offline:



To resolve these errors, complete the following steps:

  1. From the Management Report server, click Start > Administrative Tools > Event Viewer.
  2. When in Event Viewer, expand Applications and Services Logs > Microsoft > Dynamics > MR-Logger > Operational.  Change to the Detail view.  You will notice you have an error, ‘Unexpended end of file’.
  3. On the same Management Reporter server, go to C:\ProgramData\IsolatedStorage.  (Note:  The ProgramData folder is sometimes a hidden folder, so you may need to manually type it in.)
  4. Within the’ IsolatedStorage’ folder, check each folder level for a ‘Publisher.XXXXXXX’ one by one.  In this example, the Publisher folders were 2 folders beneath the IsolatedStorage folder.
  5. Once you locate the Publisher folders, open it and you will find an ‘AssemFiles’ folder.
  6. Within the’ AssemFiles’ folder, locate and right click to open the ‘DeploymentContext.txt’ in a text editor.  If the file is empty, rename the file.  If the ‘DeploymentContext.txt’ file contains something inside, just close it and leave it as is.
  7. Make sure to complete steps 4, 5 and 6 on all folders and files you located within the ‘IssolatedStorage’ folder.

Once these steps have been completed, relaunch the Management Reporter Configuration Console and it should open successfully.

Customer Portal