FlexNet Version Error

[MS_Santos]

I'm installing CREO 10.0.6.0 to use CREO Anysys Simulation, when I start it gives a flexnet version error, I've tried all possible versions and I can't get it to work, the license is for CREO 11, as shown in the print

[KenFarley]

What I see is that you have licenses that are valid for Creo 11, which is good if you're trying to install Creo 10.

What the error messages are telling you is your FlexNet installation on your server is not of a high enough version to be used with the software you are trying to use. You or your network administrator need to update the FlexNet license server to a version that is compatible, apparently at least 11.19.

In olden times, FlexNet licensing was bundled together with the Creo installation, but that's not the case anymore. Someone has to download the most recent FlexNet licensing installation from the PTC site, and replace your installation. Just make sure whatever you download is compatible with ALL the things you intend to use.

[KenFarley]

I did a quick check and for Creo 10.0.6 the download area tells you:

Creo 10.0.6.0 is packaged with the PTC License Server powered by FlexNet Publisher 11.19.6.1. For VERY IMPORTANT information, refer to CS413906

So if you take care of things to comply with this requirement, you should be okay.

[MS_Santos]

So I went to the PTC website and downloaded this version for flexnet, but I still got the same error, my machine is windows 11

[KenFarley]

If you run ptcstatus, what do you see?

It's a batch file located in something like "C:\Program Files\Creo 11.0.1\Parametric\bin". It should tell you the version of FLEXnet Publisher your computer is seeing (mine is 11.17).

[MS_Santos]

 Here's how it looks

[KenFarley]

So, the third line says that you're running version 11.17, while the error message says the minimum it requires is 11.19.

FlexNET needs to be updated to 11.19 (and restarted).

[MS_Santos]

I've just done it, now CREO Anysys Simulation isn't working.

[KenFarley · Accepted solution]

The only other thing I've found (copied from CS413906 referenced in my message above) is this info:

• UPDATED (14-Oct-2024):
  • Customers are requested to switch to the latest license server (11.19.6.1 or higher) as soon as possible, because starting with the below maintenance releases (MOR’s) of Creo, this will no longer be optional, but enforced as a policy so as to stay in compliance and ensure that customers have the latest security vulnerability fixes
    • Creo 11.0.3.0 (January-2025)
    • Creo 10.0.7.0 (December-2024)
    • Creo 9.0.10.0*
    • Creo 8.0.12.0*
      • * NOTE: Creo 8.0.12.0 & 9.0.10.0 onward will check FLEX version differently than Creo 10.0 & 11.0
        • If the FLEX version detected is prior to 11.9.1 (the original FLEX version available with those releases) OR 11.19.6.1 is in use, then Creo will start
        • If FLEX version detected is 11.19.1 through 11.19.6.0, then a message will be displayed and Creo will not start
  • Customers are recommended to upgrade early, so that they are already running a compliant license server before upgrading to a version of Creo where it is enforced
  • Customers are recommended to upgrade due to the following:
    • Issues resolved in PTC License Server (FLEXnet Publisher) version 11.19.6.1:
      • Resolve security vulnerabilities
      • Ensure customers get accurate concurrent license usage reported
      • Resolve exit issue related to TIMEOUTALL variable and Toolkit unlock license
      • Server restarts and premature exits identified in 11.19.6.0
  • The latest license server may be obtained as a standalone download from PTC License Server: FLEXnet Publisher
  • For more complete information regarding the resolved vulnerability, please refer to CS394029 - Security Vulnerabilities identified in FlexNet Publisher 2023 Release versions prior to 11.19.4.0
  • For additional issues resolved, please refer to CS408239 - PTC License Server (FLEXnet Publisher) 11.19.1.0 security vulnerability and incorrect reporting of licenses used in Creo

This is pretty much all I can figure out about this. If you still can't get things working, the best bet is to contact the people who sold you the licenses and ask them to help. They are usually very good at this kind of thing, since it's the core of their business.