cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

MDO license not acquired

346gnu
12-Amethyst

MDO license not acquired

Hello,

 

In advance of customer support on Monday on morning, perhaps a solution over the w/e?

 

Creo 1,2,3

 

I wanted to review an MDO model in Creo3 but when transferred to Mechanism I get ...

 

  • The option Mechanism_Dynamics has not been acquired.
  • All Mechanism Dynamics entities have been disabled.

Thinking this was inept installation I 'reconfigured' (several times) to ensure the floating module was selected.

 

Did not work for various cuts of Creo 3 & 2 & 1

 

Yes we have the license line items 127, 191

Yes ptcstatus shows the license available

No the configuration does not show any errors or hints that something went wrong

Yes all reconfiguration was carried out as administrator withing the administrator user

Yes our licences allow use of Creo 1,2,3,4 (but not MDO for 4)

 

Any thoughts?

 

Thanks

 

3 REPLIES 3
346gnu
12-Amethyst
(To:346gnu)

Update

 

Creo1.0

F000 - OK

M020 - OK

 

CREO2.0

F000 - OK

M030 - OK

M040 - NOT OK

M050 - OK

M060 - OK

M100 - NOT OK

 

CREO3.0

F000 - NOT OK

M030 - NOT OK

M110 - NOT OK

M120 - NOT OK

 

We have built and run MDO models in Creo3.0 before

 

But not since the installation of CREO4.0

 

All 'reconfigurations' as admin show the relevent options are selected.

TomU
23-Emerald III
(To:346gnu)

We don't have any standalone MDO seats but we do have one bundled with a Creo license.  I just checked and that particular license does work fine in both Creo 3.0 M140 and Creo 4.0 F000.  For what it's worth.

PROE_FAPMDO.png

MDO.png

346gnu
12-Amethyst
(To:TomU)

Thanks,

 

I have a deadline to hit so working in Creo2.0 M060 for now.

 

When I have finished I might have a bit of time to install Creo3.0 M140 and see what happens.

 

Also there is Creo 4.0 M020 available.

 

I may un then re install one of the 'failing' cuts.

 

Our modules are floating so might attempt an install on another machine.

 

Then might put in a call. There's clearly something 'unique' about the way our s/w is installed.

 

bfn

Announcements