WebGIS Discussions

Need a push in the right direction when configuring WebMap, Portal or SDI services? Looking for hints and tips, or just looking for Ideas and information? The WebGIS discussion board is where you start those discussions, connect and share information.
Showing results for 
Search instead for 
Do you mean 
Reply
Highlighted
Super Contributor
Posts: 301
Registered: ‎02-09-2016
Accepted Solution

Installing licensing tool throws XamlParseException

Hi all,

 

We install the latest licensing tool 11.13.2 on a 64 bit window 7 professional and the dot net framework version is 4.6.1. The installing process seems to go successfully, but when we launch the tool, it instantly show the error dialog below

2017-03-02 16_28_27-Inbox - Bob.Pham@intergraph.com - Outlook.png

 

From the licensing tool log file, it shows an error in Xaml Parse which is very confusing.

 

2017-03-02 16_31_15-Downloads.png

 

Appreciate all suggestions and ideas. I also include the log file.

 

Kind regards

 

 

Highlighted
Staff
Posts: 297
Registered: ‎11-05-2015

Re: Installing licensing tool throws XamlParseException

The stack trace in the log file indicates that this was actually caused by a problem somewhere deep in the .NET framework. The topmost trace in the call stack says that the MissingMethodException has been thrown while in System.Windows.SystemResources.ResourceDictionaries.LoadDictionary, which looks like a PresentationFramework internal method.

 

I think you should recheck your .NET installation on the machine.

Highlighted
Occasional Contributor
Posts: 20
Registered: ‎09-23-2015

Re: Installing licensing tool throws XamlParseException

Hi Bob,

 

 

You should try to downgrade to .NET 4.5. 

 

Best regards,

Robbert

Highlighted
Super Contributor
Posts: 301
Registered: ‎02-09-2016

Re: Installing licensing tool throws XamlParseException

Hi team,

 

The minimum framework for the latest licensing tool is 4.5.2, so I don't think we can downgrade to .NET 4.5

 

After trying to use the repair framework tool from Microsoft, the licensing tool starts to work.

 

Thank you for all suggestions

Highlighted
Regular Contributor
Posts: 188
Registered: ‎11-17-2015

Re: Installing licensing tool throws XamlParseException

Hello,

 

We encouter the same problem on two customer machines (Windows 7 x64).

We try to repair the .NET framework. No effect.

Is there a prerequisite for the 2018 license tool? In the download website: no prerequisite...

 

Any idea?

Thank you.

Yohann.

Highlighted
Super Contributor
Posts: 301
Registered: ‎02-09-2016

Re: Installing licensing tool throws XamlParseException

Hi yly,

 

I just wonder whether you could upgrade the dot net framework to higher version such as 4.6 and recheck again.

 

Kind regards,

Highlighted
Regular Contributor
Posts: 188
Registered: ‎11-17-2015

Re: Installing licensing tool throws XamlParseException

Hello,

 

Our customer was already in 4.7 framework.

By installing the 4.7.1, license administrator works.

Seems that License Administrator needs something which is missing in some .NET framework installation.

It occured on 3 (Win 7 x64 .NET 4.7) machines on customer side.

Was OK on a (Win 7 x86 .NET 4.6) and (Win 2012 R2 x64 .NET 4.7). 

It is hard to say to our customer to reinstall .NET framework on each end user machines...

 

Yohann.

Highlighted
Regular Contributor
Posts: 188
Registered: ‎11-17-2015

Re: Installing licensing tool throws XamlParseException

Seems like uninstalling old Intergraph Licensing damages the .NET framework...

 

See here: https://community.hexagongeospatial.com/t5/Licensing-Knowledge-Base/Intergraph-License-Administratio...

 

Will be difficult to explain this to our customers...

Highlighted
Regular Contributor
Posts: 246
Registered: ‎10-26-2015

Re: Installing licensing tool throws XamlParseException

This isn't a solution to your problem but I wondered why you are installing the License Administrator on machines? All of the products have a Configuration Wizard that allows you to configure licenses and access host IDs so the only benefit of installing the license administrator is to view concurrent license usage which is not a requirement for our customer machines so I don't install the License Administrator.