Skip to main content
L
LI_38655511-Visitor
1-Visitor
June 23, 2021
Solved

Non legge la licenza di Creo 2.0 dopo aver installato Creo 8.0

  • June 23, 2021
  • 2 replies
  • 9639 views
I am using Creo Parametric 2.0 M250

Buongiorno,
da quando ho installato Creo 8.0, non parte più Creo 2.0.

Here are the errors that I faced
License request failet for feature
    Best answer by LI_3865551

    I solved the whole problem, I reinstalled CREO 2.0 and re-entered the license, now it works.
    Thanks to everyone for the proposed solutions.

    2 replies

    B
    23-Emerald III
    BenLoosli23-Emerald III
    23-Emerald III
    June 23, 2021

    You will need to request/download a new license that is good for Creo 8.

    You may also need to update your installation of the licensing software.

    L
    LI_38655511-VisitorAuthorAnswer
    1-Visitor
    June 24, 2021

    I solved the whole problem, I reinstalled CREO 2.0 and re-entered the license, now it works.
    Thanks to everyone for the proposed solutions.

    K
    KenFarley21-Topaz II
    21-Topaz II
    June 23, 2021

    If you installed a new license server that will let you run Creo 8, in order to run older versions of Creo I've been told that you need to use the "standard text" license file for the Flexlm software, not the other file that you were given. I think the file has the suffix ".std_txt".

    Also, sometimes attempting to install different versions of Creo to run on the same system can break one of the installations, probably the last one installed is the one that works. I think it's a case of the last one installed setting the search paths in the environment so the older versions don't "see" their proper modules, etc. It can be pretty messy.

    K
    KenFarley21-Topaz II
    21-Topaz II
    June 23, 2021

    I just checked some old license files and the file name seems to be something like "lmxxxxxxx_standard.txt". Makes sense, I guess, since that will let you use standard text editors to open it by just clicking on the file.

    Terms & ConditionsCookie settingsAccessibility statement