The case of the MatchMover license problem


In this case, the customer was able to run the main application (Softimage), but MatchMover reported a fatal license problem:

License was not obtained
Tried ADLM 2011 (590D1 21012.0.0.F), error 43

License method:
environment variable MAYA_LICENSE_METHOD='network'

Product choice:
environment variable MAYA_LICENSE='adlm-590d1-2012.0.0f'

License method:
environment variable MAYA_ALT_EN is not set

In similar 3ds Max-related cases, the error looked like this:

License was not obtained
Tried ADLM 2011 (128D1 21012.0.0.F), error 43

License method:
environment variable MAYA_LICENSE_METHOD='standalone'

Product choice:
environment variable MAYA_LICENSE='adlm-128d1-2012.0.0f'

License method:
environment variable MAYA_ALT_EN is not set

In these kinds of cases, the first thing to try is setting the ADSK_MATCHMOVER_LICENSE environment variable. This environment variable can have the following values:

  • SOFTIMAGE
  • MAYA
  • 3DSMAX
  • 3DSMAXDESIGN

If that doesn’t work, then you’ll need to do some more troubleshooting.

If you create a c:\flexlm folder, MatchMover will create the log files adlm.log and MatchMoverLicense.log in the c:\flexlm folder.

adlm.log is the more useful of the two, and will contain log entries like this:

17200	2011/06/22	16:50:37	Reason=Fatal error
17200	2011/06/22	16:50:37	ComputerName=MTLEXAMPLE
17200	2011/06/22	16:50:37	OS=6.1.7600.
17200	2011/06/22	16:50:37	File=AdlmIntLicense.cpp,Line=612
17200	2011/06/22	16:50:37	VendorID=6 [ADLMPIT]
17200	2011/06/22	16:50:37	VendorError=12 [The root information in Product Information Table XML file is missing]
17200	2011/06/22	16:50:37	Reason=Fatal error
17200	2011/06/22	16:50:37	ComputerName=MTLEXAMPLE
17200	2011/06/22	16:50:37	OS=6.1.7600.
17200	2011/06/22	16:50:37	File=AdlmIntLicense.cpp,Line=613
17200	2011/06/22	16:50:37	AdlmIntError=25 [The product key was not found]

If you see the errors [The product key was not found] and [The root information in Product Information Table XML file is missing], then see this post for more information on fixing the problem.

MatchMoverLicense.log typically is just pretty much the same text that you saw in the popup message dialog boxes:

====== BEGIN MAYA LICENSE DIAGNOSTICS Wed Jun 22 16:50:37 2011 ======
623848 ::: 2
623905 
623911 
623907 
623909 
623801 ::: m2010.016 win64, built Mar  2 2011 00:27:42
623802 ::: links in AdLM but not Flint
623833 ::: 'adlm'
623858 ::: 'en_US'
623912 
623913 
623824 ::: MAYA_LICENSE_METHOD 'standalone'
623823 ::: MAYA_LICENSE 'adlm-128d1-2012.0.0.f'
623826 ::: MAYA_ALT_EN
623830 ::: MAYA_LOCATION 'C:/Program Files/Autodesk/MatchMover2012'
623866 ::: 'C:/Program Files/Autodesk/MatchMover2012/adlm/en_US'
623846 ::: AdLM 4.0.35.0 (A035) win64
623807 ::: standalone MA 128D1 2012.0.0.F
623109 --- MA 128D1 2012.0.0.F 25
623837 ::: 0
623834 ::: 0
623838 ::: 
623805 ::: 
====== END MAYA LICENSE DIAGNOSTICS Wed Jun 22 16:50:37 2011 ======

A note about those MAYA env vars. You cannot override them by setting them before you start MatchMover. MatchMover appears to set them itself. For example, with ADSK_MATCHMOVER_LICENSE=3DSMAX, MAYA_LICENSE_METHOD comes from the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\3dsMax\14.0\MAX-1:409\ADLM\Type, where Type=2 is Standalone and Type=1 is Network.

Finally, to get more diagnotics (like what license MatchMover is actually trying to use), open a Command Prompt and run these commands:

cd C:\Program Files\Autodesk\MatchMover2012
set FLEXLM_DIAGNOSTICS=3
MatchMover.exe

You’ll get some pop-up dialog boxes with messages like this:

---------------------------
FLEXible License Manager
---------------------------
FLEXnet Licensing checkout error: License server system does not support this feature.
Feature:       85700MAXDES_2012_0F
License path:  @127.0.0.1;mtl-gohabsgo;C:/Program Files/Autodesk/MatchMover2012\*.lic;c:/flexlm\maya.lic;
FLEXnet Licensing error:-18,147
For further information, refer to the FLEXnet Licensing documentation,
available at "www.flexerasoftware.com".
---------------------------
OK   
---------------------------

7 thoughts on “The case of the MatchMover license problem

      • Yes , we work today since 4 hours with the customer support and no ways for solving the problem at this time , tomorrow they coming back to resolve it after working with the development team.Thank you for your answer , and i just would like to say thanks to Hashim from the autodesk support team to help me like this.I’m very , very happy.

      • I’m sorry to hear that you’re having such a problem. I’ve had a few cases like that. A few times we got things to work by reinstalling everything…not the most satisfying solution. But that was on Windows.

  1. I tried all the way alone , by a new install in first , by the terminal windows with script after(all the next night) , but nothing work , and today the support team take the hand on my mac , they work inside 3 or 4 hours , but no way also, last year i had the same problem , but it was resolving by paste the licence env file from maya to matchmover , but this time it is something different , only for the development team, i know scripting , but in first i’m a “3d artist” and web developer in php and js, i’m always in production, and no time to solving some software problem , but autodesk have a quick reaction, and for the tracking this time i can resolve by the new camera tracking in after effect cs6, the problem was i have to import camera data into maya and usually all is automatic between matchmover and maya , here i have to finish in after effect by faking real 3d by 2,5 , so not easy , but client can’t wait , this is not his problem.So what i said to Hashim is what all the work done for windows have to be the same on mac or linux , it’s important for us , having a good working worflow is important , i’m freelance not a studio , i can’t have a development team next to me.But i’m happy to see , that my problem interest the customer support, i have maya , and i like working with all the package who come with it , i really don’t want to go on other software , i study days and night with autodesk product , now i’m a very “speed worker” inside this environment , and i want to stay here.So i was disappointed by this problem , but autodesk team make me happy by their quick reaction.
    kinds regards
    Emmanuel

  2. I have the same Problem: Matchmover 4.0 doesn´t start, because my “permanent” and uncounted key is expired. I paid for this Software, but cannot use it. Thank you, REALViz, I´ll never forget.
    Jens, looking for realiable companies to buy software from.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s