Error Message on Micromine GFFT access – Geobank Quick Articles

Issue

This document provides a procedure to address an issue where the attempts to open MGFFT failed with the error message raised but only on a specific machine.
The exact text contents in these messages could differ:

_______________________________________________________________________________________________________________

The composition produced a single composition error. The root cause is provided below. Review the CompositionException.Errors property for more detailed information.

1) The configuration section cannot contain a CDATA or text element.
(C:\Users\[UserName].[Domain_Name]\AppData\Local\MICROMINE Pty\Ltd\ Geobank.Mobile.exe_Url_2r22jsgmxUiryghcomryeqt4uyczīsz\24.0.0.1\user.config line 11)

Resulting in: An exception occurred while trying to create an instance of type 'Geobank.Mobile.Model.Options'.

Resulting in: Cannot activate part 'Geobank.Mobile.Model.Options'. Element: Geobank.Mobile.Model.Options --> Geobank.Mobile.Model.Options --> AssemblyCatalog (Assembly="Geobank.Mobile, Version=24.0.0.1, Culture=neutral, PublicKeyToken=null")

Resulting in: Cannot get export 'Geobank.Mobile.Model.IOptions (ContractName="Geobank.Mobile.Model.IOptions")' from part 'Geobank.Mobile.Model.Options'. Element: Geobank.Mobile.Model.Options (ContractName="Geobank.Mobile.Model.IOptions") --> Geobank.Mobile.Model.Options --> AssemblyCatalog (Assembly="Geobank.Mobile, Version=24.0.0.1, Culture=neutral, PublicKeyToken=null")

Resulting in: Cannot set import 'Geobank.Mobile.Services.Theming.ThemingService..ctor (Parameter="options", ContractName="Geobank.Mobile.Model.IOptions")' on part 'Geobank.Mobile.Services.Theming.ThemingService'. Element: Geobank.Mobile.Services.Theming.ThemingService..ctor (Parameter="options", ContractName="Geobank.Mobile.Model.IOptions") --> Geobank.Mobile.Services.Theming.ThemingService --> AssemblyCatalog (Assembly="Geobank.Mobile, Version=24.0.0.1, Culture=neutral, PublicKeyToken=null")

Resulting in: Cannot get export 'Geobank.Mobile.Services.Theming.ThemingService (ContractName="Geobank.Mobile.Interfaces.IThemingService")' from part 'Geobank.Mobile.Services.Theming.ThemingService'. Element: Geobank.Mobile.Services.Theming.ThemingService (ContractName="Geobank.Mobile.Interfaces.IThemingService") --> Geobank.Mobile.Services.Theming.ThemingService --> AssemblyCatalog (Assembly="Geobank.Mobile, Version=24.0.0.1, Culture=neutral, PublicKeyToken=null")

_______________________________________________________________________________________________________________

The composition produced a single composition error. The root cause is provided below. Review the CompositionException.Errors property for more detailed information.

1) '.', hexadecimal value 0x00, is an invalid character. Line 14, position 1.

Resulting in: '.', hexadecimal value 0x00, is an invalid character. Line 14, position 1.

(C:\Users\formUser\AppData\Local\Micromine_Australia_Pty_L\
Geobank Mobile.exe_Url_2r22jsghcibmryemx0lrygqt4uycz1sz\24.0.0.2\user.config line 14)

Resulting in: Configuration system failed to initialize

Resulting in: An exception occurred while trying to create an instance of type 'Geobank.Mobile.Model.Options'.

Resulting in: Cannot get export 'Geobank.Mobile.Model.Options (ContractName="Geobank.Mobile.Model.IOptions")' from part 'Geobank.Mobile.Model.Options'. Element: Geobank.Mobile.Model.Options (ContractName="Geobank.Mobile.Model.IOptions") --> Geobank.Mobile.Model.Options --> AssemblyCatalog (Assembly="Geobank.Mobile, Version=24.0.0.2, Culture=neutral, PublicKeyToken=null")

_______________________________________________________________________________________________________________

In contrast, MGFFT continues functioning without problems on the other machines or the same PC but with a different Windows user login.

Potential Causes

There could be various reasons, but if the error message mentions the user.config file, which is likely the source of the problem, and that is why it needs to be checked first.
The configuration specific to the Windows local user login is stored in one of the subfolders in %localappdata%.
The error message may appear if some corruption of the XML File happens, such as if the file contains incorrect syntax.

Solution

Navigate to `%localappdata%’ by pasting this into a Windows Explorer address field and pressing Enter.
To know where to go next, you’ll need to read the error message to identify the folder name. It could be ‘MICROMINE_Pty_Ltd` or ‘MICROMINE_Australia_Pty_L`. Go into one of these folders.
Read the error message and identify the next folder name, which starts with ‘Geobank.Mobile.exe_...’.
Go now into this folder.
Read the error message and identify the next folder name, which represents a version of Geobank (e.g., 24.0.0.1).
Go into this folder.
Locate the XML file `user.config’ and open it using a text editor like Notepad++ with “XML Tools Plug-in” enabled to use syntax-checking features.
Look for missing tags, incorrect attributes, or improper closures, which could contribute to file corruption.
Correct any identified issues.
Delete or rename this file if the corruption cannot be noticed and resolved manually.
Launch the Micromine Geobank for Field Teams application.
Navigate to the profile you need and open it for logging operations.
This action should automatically regenerate a new, error-free version of the `user.config’ file.

Verification

Check that the MGFFT can do usual activities like opening the profile/s and working with them in logging and configuration modes without error messages.

Preventive Measures

To prevent this issue from recurring:

Regularly back up the `user.config’ file.
File integrity checks should possibly be implemented as part of routine maintenance.

Want to learn more?

Online Help Manuals - Click here for the latest version

Learning Management System - Click here to login or here to request access

Issue

Potential Causes

Solution

Verification

Preventive Measures

Related articles