FlexSim Knowledge Base
Announcements, articles, and guides to help you take your simulations to the next level.
Sort by:
Staying up-to-date   FlexSim recommends staying up-to-date and using the latest Software version. New features, improvements, and bug fixes make your simulations more stable, more powerful, and easier to build.   In addition, the Software is developed for use with contemporaneous hardware, operating systems, and drivers. Among other reasons, as third parties phase out these technologies, FlexSim must discontinue support for Software versions developed for use with those technologies.   Finally, as usage of older versions decreases, FlexSim must devote its resources to supporting more recent Software versions to best serve the majority of our customers who stay current on Software maintenance and updates.   Lifecycle and Support Policy   If you must use an older Software version, understanding the Software Support Lifecycle will help you make informed decisions about when to upgrade.   A Software release is generally supported until it is four (4) or more versions prior to the current release. For the most up-to-date lifecycle and support policy information, please see section 17. Software Support of FlexSim's Software License Agreement (SLA).   As with all future-looking plans, our lifecycle and support policy is subject to change. You should not rely on this policy for making purchasing decisions. We attempt to keep this article up to date, but in any cases where this information disagrees with FlexSim's Software License Agreement, the SLA governs.   Lifecycle status terminology   Supported - FlexSim will maintain licensing infrastructure necessary for a given Software version and will provide technical support for that version for licensed users under current maintenance or subscription. Bugfixes - Bugfixes are issued periodically for the latest Software version, as needed. A Software version typically receives bugfixes until the next Software feature release. Learn more about FlexSim version numbering and bugfixes. LTS - Long-term support versions receive bugfixes for a longer period, typically 12-15 months. Beta - Preview the next version of FlexSim Software for demonstration, testing, and validation. Beta versions may not be suitable for day-to-day production use. Beta versions are superseded by their production-release version. No support - After a Software version is 4 or more versions older than the latest release it is no longer supported. Such a version may continue to work on the computer where it is installed and licensed, but it is no longer eligible for technical support and FlexSim cannot guarantee that licensing infrastructure will remain in place to move the license key to another computer.   Supported Versions   The following Software versions are currently supported.    Application   Version   General Availability     Lifecycle Status  FlexSim 26.0 2025-12-09   supported + bugfixes FlexSim 25.2 2025-08-12   supported FlexSim 25.1 2025-04-14   supported FlexSim 25.0 2024-12-11   supported + LTS   Unsupported Versions   The following Software versions are past their supported lifecycle. We recommend updating your software to a supported version.    Application   Version   General Availability   End-of-Life   Lifecycle Status  FlexSim 24.2 2024-08-05 2024-12-09 no support FlexSim 24.1 2024-04-08 2025-08-12 no support FlexSim 24.0 2024-12-06 2025-04-14 no support FlexSim 23.2 2023-08-07 2024-12-11 no support FlexSim 23.1 2023-04-03 2024-08-05 no support FlexSim 23.0 2022-12-05 2024-04-08 no support FlexSim 22.2 2022-08-02 2024-04-05 no support FlexSim 22.1 2022-04-04 2024-04-05 no support FlexSim 22.0 2021-12-06 2024-04-05 no support FlexSim 21.2 2021-08-09 2024-04-05 no support FlexSim 21.1 2021-04-02 2024-04-02 no support FlexSim 21.0 2020-12-04 2024-03-26 no support FlexSim 20.2 2020-08-11 2024-03-26 no support FlexSim 20.1 2020-04-10 2024-03-26 no support FlexSim 20.0 2019-12-06 2023-12-31 no support FlexSim 17.0 - 19.2 various 2023-12-31 no support FlexSim 7.7 - 16.2 various 2022-06-30 no support HC 5.3 2017-10-13 2022-06-30 no support FlexSim < 7.7 various 2020-12-31 no support HC < 5.3 various 2020-12-31 no support   Notes   The date format used is YYYY-MM-DD Bugfix releases follow the same lifecycle as the major release with which they are associated. Versions not listed should be assumed as past their supported lifecycle.  
View full article
Names and version numbers   FlexSim releases have names like “FlexSim 2016 Update 1” (also known as FlexSim 16.1), with corresponding version numbers in the format year.update.bugfix.   The year version number tracks with the “release year” when the software was released. For example, FlexSim 2016, having version number 16.0.0, was released for the 2016 “release year”. A “release year” roughly follows the calendar year, but a 2017 release could come at the end of the 2016 calendar year, for instance. The update version number is a count of how many feature-updates have been produced for a “release year”. For example, version 16.0.0 is the first feature-release for 2016. It is not an update, so the update version number is “0”. FlexSim 2016 Update 1 has version number 16.1.0 – it is the first update to the 2016 release. 16.2.0 is the 2nd update, and so on. Bugfix version numbers change when software is released without significant new features, but where errors, inconsistencies, or other bugs are fixed. For example, the first bugfix release for FlexSim 2016 Update 1 is 16.1.1, the next 16.1.2, and so on. Release schedule   New versions of FlexSim are released on a loose schedule:   Yearly release: November beta, December release. Update 1: March beta, April release. Update 2: July beta, August release. Bugfixes: as needed As with all future-looking plans, this schedule is subject to change. You should not rely on this schedule for making purchasing decisions.   How licensing works for a given version number   A new license is required for feature releases (i.e. year and update releases). Bugfix releases do not need a new license. For example, if you have a 16.1 license, you can license any FlexSim 2016 Update 1 releases, including all its bugfix releases, like 16.1.0, 16.1.1, 16.1.2, etc.   Licenses can also be used for older versions – i.e. they are backward compatible. For instance, if you have a 16.1 license, it can license any 16.1.x release, plus all older versions of the software back to 5.0.0. However, your 16.1 license will not work for any newer versions, such as 16.2.x or 17.0.x.   License Codes   Your license code should look something like mycompany.com03-A9B8C-7D6E5-F4G3H-FSENT17.1. Each part conveys some information:   mycompany.com- means this seat was initially licensed to mycompany. 03 is a unique index number for the license, but the actual number is meaningless. This number persists across upgrades. The mycompany.com03 license, if upgraded to version 18.0 or 18.1, etc, would still begin with mycompany.com03, even though the random characters and version number would change. A9B8C... The middle part of a license code is a unique, random mix of letters and numbers. It is different for each license, and changes when a license is upgraded for the next FlexSim version. FSENT signifies the product, in this case FlexSim Enterprise, but you may also see FSEDU for Educational, or OPTQU for OptQuest, etc. Each FlexSim product has a unique product code. 17.1 specifies the version number this license is good for. It can be used to license any FlexSim 17.1.x version or earlier, back to version 5.0. The license won't work for later software versions, like 17.2 or 18.0. For that, the license must have current maintenance and be upgraded for use with the new version. Upgrading Licenses   To use a new year or update release, your FlexSim license will need to be upgraded.   The exact steps for upgrading your license differ based on your type of license:   License Server - Upgrading your hosted licenses Standalone - Upgrading your license If your maintenance agreement has expired, or if you have timed licenses, your licenses will not upgrade. In either case, please contact your local FlexSim representative.   If you install and run a version of FlexSim software greater than your license’s version number, that newer software won’t be licensed, but will run in the feature-limited "Express" mode. To use a fully-featured, licensed copy of the software, make sure that the software’s year.update version number is not greater than your license’s year.update version number (which is typically visible in the license code itself as the final digits of the code - see License Codes above).   Long-term support (LTS) versions   From Wikipedia: Long-term support (LTS) is a product lifecycle management policy in which a stable release of computer software is maintained for a longer period of time than the standard edition.   FlexSim maintains the year release for more than a year, overlapping with the release of the next yearly release for a few months.   Here is an example of how it works:   In December 2017, the current LTS release was version 17.0.11. That same month version 18.0.0 was released. Because 18.0 was brand new, it was not yet considered the LTS version - we let it mature a bit before promoting it to the current LTS. During the time when 18.0 was the latest version, new bugfix releases were added for both 18.0 and 17.0. Finally, in April 2018, 18.1.0 was released. At that time the 18.0 branch was on its 4th bugfix release, 18.0.4, and the 17.0 LTS branch was up to 17.0.13. With the release of 18.1.0 the 18.0 branch was promoted to our current LTS release, and the 17.0 LTS was retired - it receives no further bugfix releases.   As with all future-looking plans, our LTS plan is subject to change. You should not rely on this plan for making purchasing decisions.   Downloading an appropriate version of FlexSim software   To download the version of FlexSim software that best matches your license version:   Log in to your FlexSim Account at https://account.flexsim.com/login/. Visit the downloads page at https://account.flexsim.com/downloads/. Download the latest bugfix release for your license’s version.   If a version of the software most appropriate for your license version is not listed on the main download page, click the More Versions button next to the product matching your license (see screenshot). This will open an expanded view with older versions of that product. Older software versions are not available for download from within unlicensed guest accounts. Additionally, software that has reached End of Life (no support) may no longer be listed for download. Contact your support representative for more information or to inquire about a specific legacy version.     If your FlexSim Account is a guest account (does not own a FlexSim license), only the latest software versions are available for download. Your FlexSim Account must own a license directly, or a license owner can share their license info with you, in order for you to see the More Versions button and have access to download older versions of the software. Visit your Licenses page to see if your account has access to licenses and have them loaded into your account session, then go back to the Downloads page and look for the More Versions button. Older software versions are not available for download from within unlicensed guest accounts.   Model compatibility across FlexSim versions   FlexSim versions are backward compatible, meaning that when a model built in an older year.update release of the software is opened in a newer year.update version, the model is put through an upgrade process that updates the model for use in that later version:     We recommend always saving this updated model under a new file name in order to preserve the original, non-upgraded model file, which you should archive for safe keeping.   FlexSim is NOT forward compatible, meaning that a particular year.update version of FlexSim does not support opening model files saved in newer year.update versions of the software. This is due to changes that are introduced to objects, data structures, added features, etc., that an older version of the software would not support.   A FlexSim model built with a particular year.release version of FlexSim can be opened by any bugfix release of the same year.release version, forward or backward. Bugfix releases do not change objects, data structures, etc., in such a way as to break model compatibility across different bugfix versions of the same year.update FlexSim release.   You should use judgment and care in upgrading models and continuing model development in newer versions of the software. If your simulation team has licenses that have expired at different times, and a colleague is on an older license and you are not able to renew maintenance at this time, you may want to standardize on that lowest version number of FlexSim so that models your team creates and edits can be interoperable among teammates.   FlexSim's model upgrade functionality is fairly robust, but if you are upgrading a model from a version of FlexSim many years older than the version you're opening it in, it may be necessary to open and save the model in an intermediate version (or two). Contact your FlexSim support representative if you encounter any problems upgrading your FlexSim model to a later version.   Opening Files from different versions (Flexsim Version Selector)   If this is a first time install of the FlexSim software, you can double click on any .fsm file and Windows will ask you what software you'd like to open .fsm files. In the program selection scroll down to the version entitled Flexsim Version Selector. This application will automatically open any .fsm file in the version that the file was originally saved or created in.   Alternatively, you can right click on a .fsm file in Windows and navigate to the option Open With > and then navigate to Flexsim Version Selector from here. This will set the version selector application as the primary method for opening .fsm files in the future.  
View full article
Introduction   A new feature-version of FlexSim Simulation Software is released several times per year. In order for client PCs to be able to run a licensed version of the upgraded software, you may need to upgrade the activated license(s) on your license server. Licenses with a current maintenance subscription are eligible to be upgraded to the latest version.   If you don't understand how licensing works for different FlexSim versions, please review our Answers article FlexSim Version Numbering.   Overview   There are 6 main steps to upgrading the licenses hosted on your lmadmin or lmtools license server:   Check if you need to upgrade your license server files Return the licenses you intend to upgrade Upgrade your licenses Activate the upgraded license Reread the license Upgrade client PCs   Several of these steps have their own fully documented procedures. We'll link you to those resources below.   1. Check if you need to upgrade your license server files   If your organization's license server was installed previously and hosting licenses for FlexSim 25.1 or lower, it may need to be upgraded for compatibility with FlexSim 25.2 and higher. Click here to learn more or go directly to the latest license server files.   After you have upgraded your license server files, move on with the rest of the upgrade process, as outlined below.   2. Return the licenses you intend to upgrade   The steps to return a license-server-based license are fully documented. Choose the link below that best matches your needs, depending on whether your license server can connect to the Internet:   License Server - Return - Online License Server - Return - XML / Offline   Be sure to return ALL licenses you wish to upgrade.   3. Upgrade your licenses   NOTE: Licenses with expired maintenance will not upgrade. Timed licenses do not upgrade. Only permanent (not timed) licenses under current maintenance can be upgraded. Contact your salesperson for extending a subscription or other circumstances.   Log in to your FlexSim Account.   If you were already logged in to your FlexSim Account, in the top navigation menu hover over your initials icon and choose Reload Account.     Now in the top navigation menu, choose Licenses > List.     Check that the available seat count is equal to the total. All of a license’s seats should be returned for it to upgrade.   Click on the Upgrade Licenses button.     If you have several licenses to upgrade and all are owned by or shared with your FlexSim Account, they will all be upgraded at once. Please be patient while the upgrade process works in the background.   When the page refreshes, eligible licenses will have a new activation ID for the latest version of the software. Your license code indicates its version at the end of the code to help you know what versions your license will properly activate. Review license code format.   4. Activate the upgraded licenses   The steps to activate a license-server-based license are fully documented. Choose the link below that best matches your needs, depending on whether your license server can connect to the Internet:   License Server - Activation - Online License Server - Activation - XML / Offline   5. Reread the license   Your license server needs to start serving up your newly activated licenses. You can either restart your license manager service, or use your license manager's option to reread your licenses.   The steps to reread your licenses differ depending on which license manager you are using to host your licenses. Use these links to jump to instructions for the license manager you're using:   lmadmin lmtools+lmgrd   6. Upgrade client PCs   Finally, upgrade your PC with a version of FlexSim appropriate for your new license (learn how licenses work across versions).   After installing a new version of FlexSim, you will need to configure it to get a license from your license server. There are two ways a client PC can be configured. Choose the method below that most closely matches the main use case for your client PC:   Single-user client PCs - this method configures settings that are saved on a per-user basis. Multi-user client PCs - usually appropriate for a university computer lab or other shared-PC situation, where the configuration should be computer-based.   Having trouble licensing your client PC?   Verify client PC licensing to find out if your client PC is successfully getting a license from your new license server. Diagnose Client/Server connectivity issues that may be preventing your FlexSim software from obtaining a license. Discover other issues that may be preventing your client PC from obtaining a license by working through our License Server Troubleshooting tips.  
View full article
You've installed, configured, and started your license server. FlexSim is installed and your client PCs are set to get a license from your license server. How can you tell if they're communicating and licensing properly?   You can check both the client PC and the license server to make sure that licensing is happening:   Client PC   Within FlexSim software on the client PC, go to the main menu, Help > About FlexSim. The popup should indicate the activated license type. Test licensed features to see if they work. Check the article FlexSim Feature Limitations by License Type to see what features should be available given your license type (Enterprise, Educational, Student, Runtime). For instance, the Experimenter feature should be available to each of those license types.   License Server   In lmtools logs (Config Services > View Log…), you should see that a seat is in use. (See How do I read/analyze my vendor daemon logs? What do the various lines mean?). . In lmadmin logs you should see that a seat is in use.   If your client PC is not getting licensed and/or your license server logs don't indicate communication with a client PC, check the license server troubleshooting steps.  
View full article
Why would I delete a fulfillment?   You may need to manually delete a fulfillment from your PC if:   Your license is broken. Sometimes you can fix this problem yourself by attempting a repair. However, you may get a message that the repair failed. "Repair: failure. Online return/repair request for the activation ID is not originated from the original client machine." In this case contact your local FlexSim distributor to explain the situation and let them take a look. Reference this post. If they determine it is best to delete the broken fulfillment, follow the instructions below to do so. Your distributor will then force-return the broken license so that it will be available for a new activation. You mistakenly requested a force-return of a license. If you later find the fulfillment that you thought was lost, that fulfillment is no longer able to be returned normally (because it was already force-returned).   In these cases, and in a few other rare circumstances, you may find it necessary to manually remove a fulfillment from your computer. This process occurs exclusively on your computer without any communication with FlexSim's main license server.   Delete your fulfillment   FlexSim 23.0 or greater   For FlexSim version 23.0.1 or greater, you can delete fulfillments using the License Activation window.   From FlexSim's main menu, choose Help > License Activation. Under the Advanced tab, find the Delete sub-tab. Choose the fulfillment you'd like to remove from your computer and click Delete. Confirm your choice to remove the fulfillment from your computer.     Currently licenses that are *BROKEN* do not show up in this list (how do licenses become broken?), so if this applies to your situation you will need to use the Older versions method below.   Older versions   If you are using an older version of FlexSim, we recommend that you download the latest FlexSim software and use the updated delete method described above, even if your license is for an older FlexSim version. Older FlexSim versions do not have a graphical interface for removing fulfillments, but if you're comfortable you can still do so using a FlexScript command.   Find the fulfillment ID   The first step is to find the fulfillment ID of the license you want to return. This is an identifier unique to the activation you're removing.   View your licenses to find the fulfillment ID you wish to remove from your PC.   Prepare your delete command   Once you know your broken fulfillment ID, you're ready to build the command that will remove it from your computer.   licenseactivation(LA_DELETE_FULFILLMENT_RECORD, "paste entire 'FID_...' fulfillmentID here");   Be sure to paste the complete fulfillment ID into the 2nd parameter.   Depending on your software's licensed state, you may be able to run this command directly in a script window. If not, we'll work around that limitation by using an object's reset trigger.   Execute the delete command   There are two ways to manually delete your fulfillment:   Run the command in a script window Use a 3D object's reset trigger   Run in a Script window   If your FlexSim installation is still licensed, you can open a Script window to run FlexScript commands:     Run the command console. You will be prompted to confirm that you truly want to remove the fulfillment:     Choose Yes to remove the fulfillment.   Use a 3D object's reset trigger   If your FlexSim software is not licensed the Script command console is not available. Instead, do the following:   Create a new model. Drag any object into the 3D view. Create a reset trigger on that object. Enter the FlexScript command into the reset trigger. Press OK to save the script. Reset the model. Choose Yes to confirm that you truly want to remove the fulfillment.  
View full article
tl;dr   must be stable and persistent, always able to maintain a constant connection with the client software don't use a user's personal computer as a license server use a currently supported Microsoft OS bare-metal hardware, virtual hardware, cloud hosted - all are fine if the hardware meets the OS specifications, it meets the license server specifications configure your network and firewalls to allow the client-server communication   Use an always-on, accessible server (not a user's PC)   Your license server should be on a stable, persistent system that is always on and always accessible via a stable IP address or fully qualified domain name. A user’s personal system is not a good license server, unless they are only serving licenses to themselves, in which case please consider contacting your local FlexSim distributor to exchange for a standalone license.   Operating System   Hosting FlexSim licenses requires a currently supported version of Windows (desktop or server versions are supported). FlexSim and FlexNet do not support Windows operating systems that have reached their end-of-life. See Microsoft guidance on product lifecycle.   You should perform all Microsoft Updates so that your operating system is fully patched prior to installing the license server software.   In the future we hope to allow FlexSim licenses to be hosted on Linux or Mac license servers, in addition to Windows. Work toward multiplatform is ongoing. We do not currently have an estimated timeline.   Server Hardware   If your license server hardware meets the specifications required for the chosen Microsoft OS, it will be adequate to run the license server software. Hosting licenses is generally NOT a demanding workload.   Please do not confuse these minimal license server hardware requirements with the different and more demanding system requirements for running FlexSim Simulation Software.   Cloud Hosting   Your license server could be hosted by a cloud provider or on premises, on a virtual machine, or a bare-metal OS.   Keep in mind that your license server should be a stable, persistent server that client PCs can remain connected to. If your server setup works by creating and destroying new instances of a virtual machine each time you reboot, it is NOT suitable for use as a license server. You will lose your Trusted-Storage-based FlexSim licenses when the virtual machine is terminated.   Networking, firewalls, connectivity   For the client software to remain licensed, it must maintain a constant network connection to your license server. The exact details of such a configuration are up to you.   If you want to limit client-server connections to the local network, allow access to the license server worldwide over a VPN, or make your licenses available over the public Internet, these are all decisions you must make and configure your network and firewalls accordingly such that your FlexSim client PCs can maintain a constant connection to the license server.   Further networking guidance, including information regarding firewalls and port numbers, is found in the individual instructions for lmtools or lmadmin.  
View full article
Not sure about the differences between network and standalone licenses? No worries! Read on for an in-depth explanation of each license model:   Standalone Licensing (Client-Activatable) Network Licensing (Server-Concurrent)   You can also download our printable reference, which includes some example scenarios: Standalone vs Network Licensing.pdf.   Standalone Licensing (Client-Activatable)     Once a standalone license is activated to a PC it remains there permanently until it is returned. The PC could be rebooted, taken offline, or even have FlexSim uninstalled - the license remains on the PC.   The steps to activate and return a license are user-accessible from within FlexSim software. Once FlexSim is installed, there are no special PC permissions required to activate or return licenses.   See our licensing procedures article for instructions for managing your standalone licenses (activate, return, repair, upgrade).   User-managed license movement   The ability for the user to activate and return their license at will is a big advantage. It allows teams the freedom to share a license, while still giving individuals the freedom to take a license off-site or off-Internet. As long as a team sharing a license communicates effectively, the license can be passed around to whoever needs it at the moment, by returning the license from one PC and activating to another.   History Log   FlexSim's main license server logs a license's activation/return history, including who last activated (in case you need to contact someone about returning it!). The license history log can be viewed by any FlexSim account that can view the license. This includes the license owner and any account the owner has shared with.   Your activation IDs (the license codes copied into FlexSim to activate your license) can be shared and visible - including the activation history - with every member of your group. See the Sharing tab on your FlexSim account's Licenses page.   Trusted Storage   Your standalone FlexSim licenses are activated to a special holding area on your computer called Trusted Storage, which exists outside and independently of FlexSim software. FlexSim's activation process will authenticate your computer with our main license server and store your license credentials in Trusted Storage, completely outside of any FlexSim installation.   You could uninstall FlexSim, but your license will still reside in your computer's Trusted Storage. You would need to reinstall FlexSim in order to access the return functionality to move your license off of your computer.   So, you can go ahead and use ANY version of FlexSim to activate ANY version of your license so that it will be stored in your computer's Trusted Storage. Whether the activated license will enable features in your version of the software is a separate question - and as a quick reminder, FlexSim's licenses are backward-compatible, meaning that if you have a 21.2 license, you can use that with any version of the software up to version 21.2.x, including all older versions back to 5.0.   The crux is, your standalone license can be accessed by any version of FlexSim installed on your computer, regardless of what version was used when activating the license, because all versions just put your license into Trusted Storage, and all versions check license rights by reading out of Trusted Storage.   Standalone pros   User-level control of the license gives flexibility in who has the license at any given moment. FlexSim maintains the license server, so you don't have to (avoids complexity of installing, configuring, maintaining, and upgrading your own separate license server). Online tools to see the license history and who currently has the license (via your FlexSim Account). In-software auto-upgrades makes upgrading your license easy.   Standalone cons   People sharing the license need to coordinate who will use it when and remember to return the license when unused. Lost, stolen, or broken licenses require interaction with your local FlexSim rep to fix.     Network Licensing (Server-Concurrent) Let's begin with an overview of the setup (simplified from our license server installation instructions) :   Provision a computer/VM to act as the license server. It should remain powered on and attached to the network at all times. Activate your FlexSim licenses to your local license server. Install and configure the license manager software. Configure firewalls and permissions on the server and/or network to allow communication with FlexSim client PCs.   Next, the client PCs:   Install FlexSim on the client PC. Configure licensing settings in the client software to point to the license server. Configure firewalls and permissions on the client PC and/or network to allow communication with the license server. The network connection between client and server must be maintained throughout use of FlexSim software. If the network connection breaks, FlexSim software reverts to the feature-limited Express mode.   This sort of setup is great for computer labs at universities, for instance, where there are many client PCs, and license server hardware or virtual machine is easy to obtain or already exists. Also, where the client PCs are stationary and always on the network, and where network topology makes it easy for the clients to stay connected to the server.   Opening FlexSim software requests a seat from the organization's license server. Closing the software returns the seat.   Network pros   Allows for management of many licenses (seats) from a single location. Some server settings are customizable (Options files can be quite powerful - see chapter 13). Licenses can never become lost or stranded on client PCs. If a client PC loses its connection to the server, the server will reclaim the seat after a timeout period (default timeout is 15 minutes).   Network cons   Complexity of installing, configuring, maintaining, and upgrading a separate license server. Client PCs must maintain a constant connection to the server. No online record of activations/returns (but you can examine your own raw server logs).  
View full article
Assumed configurations   All steps below assume that you followed the installation instructions as described in our license server installation instructions, and that all FlexSim's license server files were extracted to the location C:\FlexSim_LMTOOLS. Throughout these instructions we will reference files inside that folder.   Reread the license   Within your FlexSim_LMTOOLS folder, right-click lmtools.exe and choose Run as administrator. You may need to accept a permissions prompt. Go to the Start/Stop/Reread tab. Choose the FlexNet License service for your FlexSim licenses. The name of the service could be FlexSim_License, but the service could have been given a different name. Press the ReRead License File button. Close lmtools.
View full article
This table is meant as a reference and guideline. While we strive to maintain this list regularly, it may be out of date at any given time. If an advertised feature of FlexSim is not listed here, it is generally not subject to limitations by license type.   The Express license type is FlexSim's default, unlicensed state. Downloading and installing FlexSim to a new computer, it will be in Express mode. The other license types require you to obtain a license and apply it to the software. Please refer to FlexSim's End User License Agreement (EULA) for details on allowed uses, restrictions, and other considerations. If you wish to test a particular license type, please contact your local distributor to request a test license.   Please Note: Runtime seats are no longer available for new purchase or renewal but are referenced in this table to support those Runtime licenses still outstanding.   Please Note: Autodesk sells a node-locked subscription license. This is the same as Enterprise in the table below, with some restrictions on moving the license. Please see our article Node-locked license vs Transferable license.       Express Runtime Student Educational Enterprise Use Cases (see EULA) Testing, evaluation, and model viewer only. Run only (no model building). Educational use only. Educational use only. See EULA. Open, Run, Save open and run any size model ✔ ✔ ✔ ✔ ✔ open and save models in XML format     ✔ ✔ ✔ unlocked random streams   ✔ ✔ ✔ ✔ compile models built with C++ (optional, requires Visual Studio)   ✔ ✔ ✔ ✔ save model size limitations model size must be under limitations none model size must be under limitations none none experimenter   ✔ ✔ ✔ ✔ OptQuest optimizer   with OptQuest add-on license up to 10 optimization variables with OptQuest add-on license with OptQuest add-on license webserver (requires separate download) ✔ ✔ ✔ ✔ ✔ Model Building model building features available ✔ no ability to add objects or activities, but any objects and activities used by existing models are editable ✔ ✔ ✔ create objects and activities ✔   ✔ ✔ ✔ object creation limit 30   100 none none process flow activity creation limit 35   250 none none execute FlexScript in script console     ✔ ✔ ✔ tree view     ✔ ✔ ✔ Tool Box Add Tools ✔ no ability to add tools, but all tools used by existing models are editable ✔ ✔ ✔ FlowItem Bin ✔   ✔ ✔ ✔ Global Tables ✔   ✔ ✔ ✔ Time Tables ✔   ✔ ✔ ✔ MTBF/MTTR ✔   ✔ ✔ ✔ Down Behavior ✔   ✔ ✔ ✔ Dashboards ✔   ✔ ✔ ✔ Groups ✔   ✔ ✔ ✔ Process Flow (all options) ✔   ✔ ✔ ✔ Global List (all options) ✔   ✔ ✔ ✔ Statistics - Statistics Collector ✔   ✔ ✔ ✔ Statistics - Milestone Collector ✔   ✔ ✔ ✔ Statistics - Calculated Table ✔   ✔ ✔ ✔ Statistics - Experimenter     ✔ ✔ ✔ Statistics - Tracked Variable     ✔ ✔ ✔ FlowItem (all options) ✔   ✔ ✔ ✔ Modeling Logic (all options)     ✔ ✔ ✔ Visual - Model Floor ✔   ✔ ✔ ✔ Visual - Model Background ✔   ✔ ✔ ✔ Visual - Video Recorder     ✔ ✔ ✔ Visual - Fly Path     ✔ ✔ ✔ Connectivity - Database Connector ✔   ✔ ✔ ✔ Connectivity - Excel Import/Export ✔   ✔ ✔ ✔ Connectivity - Visio Import     ✔ ✔ ✔ Connectivity - Emulation (Modbus and OPC DA connections only. Other connection types require an Emulation license.) ✔   ✔ ✔ ✔
View full article
Node-locked   Node-locked can only be activated once. Be sure that you install the license where you would like it to be installed for the next year. FlexSim can assist with one migration for extenuating circumstances, such as a crashed computer, but there will be fees for any additional migrations. Please contact your distributor to receive assistance with moving your license. The node-locked license feature of terminal server usage (remote desktop) is disabled and cannot be enabled.   Transferable   There is no limit to the number of times a license seat can be activated and returned. If the transferable license is not a network license, then by default the license feature of terminal server usage (remote desktop) is disabled.    Please reference other articles or our documentation for further information about licensing.
View full article
You should have already completed all preceding steps found in the article Hosting your FlexSim licenses with lmtools, including all those under the headings "Preparation and Prerequisites" and "Activate licenses to your license server". Your license server will communicate with client PCs using two executables, the lmgrd.exe licensing service and the flexsim.exe vendor daemon.   This article shows how to add exceptions for these applications through Windows Firewall. If you have additional firewalls or network appliances that need to be configured, please check the section Port Considerations at the end of this article.   Allow an app through Windows Firewall Port Considerations   Allow an app through Windows Firewall   Windows Firewall allows you to specify certain applications that will be allowed through different network types. If you're not sure about firewalls and networking, be sure to contact someone in your organization that administers these things.   You will need administrator privileges on your license server to add firewall exceptions.   Open the Allowed apps interface   Click the Start button or press the Windows key, then type Firewall into the search box. Choose the option to Allow an app through Windows Firewall.     If you don't see that option, you can choose the option Windows Defender Firewall at the top of the search results. This will open the Windows Defender Firewall topic the Control Panel. There you can choose Allow an app or feature through Windows Defender Firewall in the side panel:     Add a firewall exception for lmgrd.exe   In the Allowed apps window, click the Change Settings button, then the Allow another app… button.     In the Add an app window that opens, click the Browse… button. Navigate to extracted license server downloads. Double click lmgrd.exe to choose the file.     Click the Network types… button.   Check the boxes for the various network types that the firewall should allow. We recommend allowing your FlexNet licensing to communicate across all network types, but contact your server or network administrators if you're not sure.     Click Okay to close the Choose Network Types window.   Back on the Add an app window, click the Add button.   Add a firewall exception for flexsim.exe   Repeat the steps above for flexsim.exe:   Click the Allow another app… button. Browse… to your extracted license server downloads. Select flexsim.exe. Click Network types… and choose the appropriate networks to allow access to lmgrd.exe. These should be set to the same settings chosen for lmgrd.exe, and you can usually allow all network types - domain, private, and public. Click the Add button. Click OK to close the Control Panel window.   Port considerations   You may need to allow communication through other firewalls or network appliances, depending on your network topology and specific licensing plans for how and from where client PCs will connect to the license server. Usually for such firewalls or devices you will configure inbound and outbound port exceptions to allow your license server communications to pass through.   A FlexSim license server has its ports defined in a flexsim.lic license file, specified when you configured your FlexSim_Licensing service.   Our default ports are as follows:   lmgrd.exe - licensing service - port 26914 - TCP flexsim.exe - vendor daemon - port 56914 - TCP   There is a chance you specified custom your port numbers. If you're not sure you can check your flexsim.lic license file. Read more about FlexSim's license file and default vs custom port numbers in our article FlexSim's license file.
View full article
These instructions are to be performed on a license server hosting FlexSim licenses. You will need the license server files. If you do not already have a copy of those linked files on your license server, download them to your license server then extract the entire archive to a convenient location.   Run flexsimserveractutil.exe as an adminstrator by right-clicking the .exe and selecting Run as Administrator. Go to the main menu, Tools > View License Rights. Scroll through the displayed license information. Find any activated licenses that indicate they are broken. Find each broken license's Fulfillment ID (starts with FID_). Copy the Fulfillment ID to the clipboard (highlight including the FID_ prefix, through to the end of the line. Ctrl-C to copy). Go to the main menu. Select Connect > Repair. Paste the Fulfillment ID into the field (Ctrl-V). Delete any spaces that may have been included before or after the pasted Fulfillment ID. Press the Repair button. The utility will attempt to contact FlexSim's license server in order to repair the license.   If you have any questions or problems, please search our Answers Community for possible solutions. There is a good chance someone else has already asked your question. Still not finding what you're looking for? Submit a new question and we'll check it out. If you're including any confidential information, such as license codes, be sure to mark your question as private! You can also contact your local FlexSim distributor for live phone, web, or email help.
View full article
The following articles describe various error messages and numbers you may see as you work with your FlexSim licenses, along with possible solutions and workarounds.   flxActCommonHandleOpen (50003, 71000, 10103) flxActAppReturnSend (50018, 41145, 32) Manual activation error (50019, 41200, 19) Manual XML licensing error (50019, 42107, 10246) Licensing activation error (50041, 41143, 34)   Operations error: 7032 Invalid fulfillment ID Operations error: 7109 Invalid activation ID Operations error: 7131 Server activation is not allowed Operations error: 7174 Only deployed entitlement line item can be fulfilled Operations error: 7189 Client activation is not allowed Operations error: 7284 Cannot perform support actions on inactive fulfillment record Operations error: 7288 fulfill count exceeded the available seat count Operations error: 7466 The return of the fulfillment is denied Operations error: 7581 Online return/repair request is not originated from the original client machine   Trusted storage binding change detected
View full article
Have you ever encountered this error?   --- Status... Status: 4 Creating request Status: 5 Request created Status: 6 Context created Status: 7 Connected to remote server Status: 0 Error ERROR: flxActAppReturnSend - (50018,41145,32) "Failure to send request or receive a response for an unspecified reason. Recovery: check parameters used for the request." ---   We're looking for more information on this error. If you're encountering this error, please comment below.   This error appears to be a communication error where the client PC may have an Internet connection, but is not successful in contacting the license server. This may be due to a firewall misconfiguration or a proxy server.   You may want to make sure your client PC can connect to FlexSim's servers (addresses and ports listed in this article).   You may also need to configure FlexSim to communicate through your proxy server:  
View full article
Introduction to lmtools   This article is a sort of table of contents to the various articles that will take you from start to finish in installing, licensing, configuring, and running your FlexSim license server using the lmtools license manager.   background info   Server-based vs Standalone licensing - Learn the differences between these two license models, and when you might choose one over the other. License managers - lmadmin vs lmtools - FlexSim supports these two FlexNet license managers. Learn the differences, and why FlexSim recommends lmtools.   Let's get started   When installing a new license server, start here at the top and work your way down the list of articles linked below. By the end you should be in good shape to properly host and serve your FlexSim licenses.   Each link should open in its own browser tab, so once you complete a sub-task just close that tab. Then back here in this main tab click the link to the next step.   The list of links below might seem intimidating, but conceptually it's just 4 main things we're about to work through:   Preparation and Prerequisites Activate licenses to your license server Configure the licensing service Configure client PCs   If you run into any problems, you can also find additional helpful resources linked at the end of this article:   Troubleshooting Related links     1) Preparation and Prerequisites   System Requirements - almost any Windows computer could act as your license server. Click inside for the details. Download files - download the required lmtools files and extract them to an appropriate folder on your license server. FlexNet Licensing Service 64 - FlexSim is licensed using Revenera's industry-standard FlexNet licensing platform. This article prepares your license server with the background service necessary for hosting your FlexSim licenses.   2) Activate licenses to your license server   Choose the right steps below to license your server, depending on whether or not your license server can communicate over the internet directly with FlexSim's main license server.   • Online, Internet-enabled systems   License Server - Activation - Online - Activate your FlexSim licenses to your license server directly over the Internet. Should be easy-peasy. • Secure / Offline / Air-gapped systems   If your license server will not connect to the Internet (or if for any reason it cannot communicate with FlexSim's license servers) there are a few extra steps to get up and running. You've got this!   Configure Trusted Storage - Your new license server has a secure storage area for holding license info, but first it must authenticate with FlexSim's main license server. License Server - Activation - XML / Offline - the manual steps to activate your FlexSim licenses onto your license server.   3) Configure the licensing service   Configure your license service - use FlexNet's lmtools license manager to create and configure the service that will serve up your FlexSim seats. Add Windows Firewall exceptions - your licensing service needs to communicate with other PCs on the network. This will get you started.   4) Configure client PCs   With your license server installed and configured, it's finally time for your license server to fulfill its destiny and serve licenses to your client PCs.   Make sure you know the IP address or fully qualified domain name for your license server, as well as the license service port number (see #1 under Check the service status). You'll use your server's address/name and service port when configuring the client PCs.   FlexSim Version Numbering - your FlexSim license is for a particular version of FlexSim. If your software maintenance is not current, you may need to use an older version of the software. In this article you'll learn how licensing works for a given version number and where to download an appropriate version of FlexSim that will work with your license. With an appropriate version of FlexSim installed on the client PCs, you're ready to configure them to communicate with your license server. There are two ways a client PC can be configured. Choose the method below that most closely matches the main use case for your client PC:  Single-user client PCs - this method configures settings that are saved on a per-user basis. Multi-user client PCs - usually appropriate for a university computer lab or other shared-PC situation, where the configuration should be computer-based. Verify client PC licensing - Not sure if your client PC is getting licensed properly? Dive in to find out how to tell your client PC is successfully getting a license from your new license server   Troubleshooting   Isn't there a law in the universe that if something can go wrong, it will? If you're stuck in a licensing black hole, these tips might be just the thing to help you get moving.   Client/server connectivity - if the client PC and the license server can't communicate, the client PC won't be able to get a license. Troubleshooting tips - when you're pretty certain that connectivity isn't an issue, but your client PC still isn't getting a license, check here for some ideas.   Related Links   FlexSim's license file - your new licensing service uses a license file to specify port numbers. Get more background on license files and ports here.  
View full article
Preparation   You may want to brush up on how a license version is related to a product version.   When you understand what version of FlexSim will work with your license, download and install an appropriate software version for your license.   If your computer is not connected to the Internet, you will need to transfer FlexSim's installer to your computer on a USB drive or some other method.   You will also need to be able to transfer XML license files to and from your offline computer.   NOTE: If this is the first time a license has been activated on this computer, an initial XML request/response communication will be needed to configure your local Trusted Storage.   This means that for a first ever license activation on a given computer, complete the steps below for just a single Activation ID - that will configure your computer's Trusted Storage.   Once that is complete, repeat again the entire Manual XML activation process for that initial Activation ID and any other Activation IDs that will be installed to this computer.   Find your licenses   Log in to your FlexSim Account, click the Licenses link in the top menu. In the Licenses submenu, choose List. Expand the various product and version folders to find the Activation ID you wish to activate. An Activation ID looks similar to this example: yourcompany.com01-ABCDE-FGHIJ-KLMNO-FSENT16.2   Create manual activation requests   Open FlexSim Software. In FlexSim's main menu, Go to Help > License Activation. Click the Advanced tab. Go to the Manual Activation sub-tab. Enter a valid Activation ID into the field (see the Find your licenses heading, above). Click the Generate Request button. You will be prompted to save an XML file. Choose a location and filename to save your XML activation request. If this is your first time ever activating any FlexSim licenses on this PC, only generate an XML request for one activation ID (see red-highlighted note above). Otherwise, repeat steps 4-6 for all licenses you wish to activate on this PC, so that all your XML activation request files can be transferred at one time.   Submit your manual activation requests   Transfer your XML activation requests to a computer with Internet access. From your Internet-connected computer, open a web browser and login to your FlexSim Account. Click the Licenses link in the header, then choose Manual XML in the Licenses submenu. Upload your XML files by dragging them onto the drop zone. Your uploaded XML requests will be processed. Upon completion, you will be prompted to download each XML response.   Process your manual activation responses   Transfer your downloaded XML activation responses to the offline computer you are licensing. In FlexSim, using the same licensing interface where you generated your request, click the Process Response button. Browse to an XML activation response file. FlexSim should give you an indication of successful processing of your activation, and your activation will be complete. Repeat to process the XML activation responses for any other licenses you are manually activating.   IMPORTANT NOTE   If this is the first time a license has been activated on this computer, an initial request/response communication will only serve to configure your local Trusted Storage.   This means that for a first ever license activation on a given computer, after this first request/response has been successfully processed on the offline computer, a 2nd request using the same license code will need to be generated/uploaded/processed/downloaded/processed to fully activate your license.   This is a one-time event per-computer. Subsequent license activations to the same system require only one request/response XML pair. If you have any questions or problems, please search our Community for possible solutions. There is a good chance someone else has already asked your question.   Still not finding what you're looking for? Licensed users can submit a support request and we'll check it out.
View full article
You should have already completed all preceding steps found in the article Hosting your FlexSim licenses with lmtools, including all those under the headings "Preparation and Prerequisites" and "Activate licenses to your license server". At this point you're ready to install, configure, and start the service that will serve your FlexSim licenses.   Create the service Configure service permissions Start the service Check the service status Troubleshooting problems with the service   Create the service   We'll use lmtools to create your new licensing service.   On your license server, in your extracted download folder of FlexSim license server materials, right-click lmtools.exe and choose Run as administrator. Go to the Config Services tab. Create a new licensing service by typing FlexSim_License into the Service Name input field. The Service Name field looks like a dropdown selector, but you can click in it to type a new name. Use the 3 Browse buttons to specify the paths to files (lmgrd.exe, flexsim.lic, log.log) that are also included with the FlexSim license server materials. Check the boxes for Use Services and Start Server at Power Up. Press the Save Service button in the upper right. Confirm the save by choosing Yes. You may receive an error message regarding "Windows preferred path". This is normal and this message can be safely ignored.   Configure service permissions   Your new FlexSim_License service needs permissions set to function properly.   Click the Windows Start button or press the Windows key, then type “Services” into the search box in the Start menu, and press Enter. Windows will search for and open Windows Services Manager. Find FlexSim_License in the list of services. If it is missing from the list, see the section Troubleshooting the licensing service below. Open the FlexSim_License service’s Properties window by double-clicking its name. Go to the Log On tab. Choose the option to Log on as: Local System account. Press OK to close the FlexSim_License Properties window.   Start the service   While still in Windows Services Manager, use the Start link to start your new FlexSim_License service.     You should see a status bar showing the startup progress. The service usually starts in under a minute.   If there are any errors or other problems with starting the service, skip to the section Troubleshooting problems with the service.   Check the service status   After the service is started, head back to lmtools to check the log. You can view the service log from the Config Services tab, press the View Log... button, located toward the lower right of the Config Services panel.   You should find the following information in your log file:     lmgrd.exe is listening on port 26914. This is the port the licensing service will use when listening for client PC communication. The bootstrap license file flexsim.lic was found and loaded. (This is not a license file specific to you and does not contain your license info. FlexSim licenses use Trusted Storage and licenses are activated to your license server using flexsimserveractutil.exe). The flexsim.opt Options file was found and loaded. A list of product features activated in your server's Trusted Storage. Your feature set may differ somewhat from this example, depending on your license and product, but you should see several of the features above. 900 seconds is the minimum timeout allowed by FlexNet, and we configure our installation to use this minimum value using the options file. The flexsim.exe vendor daemon is using port 56914.   To close the log, press the Close Log button, toward the lower right of the Config Services panel in lmtools.   Troubleshooting problems with the service   Did everything work? If not, perhaps you have one of these issues:   The FlexSim_License service is not listed as an installed service in Windows’ services. The FlexSim_License service does not start manually. The FlexSim_License service does not start up automatically when the computer restarts.   If any of these apply to you, please check the following:   You ran lmtools as a user with admin rights, and right clicked the program to choose Run as Administrator. On the Config Services tab, you checked the boxes Use Services and Start Server at Power Up. There isn’t already a process running or service installed named FlexSim_License. lmgrd.exe, flexsim.exe, and all other files downloaded together with them are in the same folder, and in a file path that does not contain any folder named “FlexSim” (case insensitive). The FlexSim_License service must run as an account with proper permissions. It’s possible that the Local System Account setting specified in Configure service permissions above does not have adequate permissions, and you will need to specify the service to run under a different account. Work with your server administrator or IT department to determine an account with the proper permissions to run your license service. You could have a port conflict, where one or both of the ports specified in your flexsim.lic license file are in use by another service on your license server. Check the section Resolving port conflicts. Some anti-virus solutions prevent unrecognized services from running or accessing necessary functionality. If your license service won't start, try temporarily disabling any anti-virus solution installed on your license server. If this fixes the issue, work with your IT administrator to modify your anti-virus settings. Remember to reactivate your anti-virus software after this experiment.  
View full article
A license file? What's that? License not included Default port numbers Custom port numbers Automatic port numbers Resolving port conflicts A license file? What's that?   When you set up a license server to host your FlexSim licenses, you'll configure settings for a FlexNet licensing service (lmtools, lmadmin). Some settings are specified in a plain text file ending in the .lic file extension.   You'll find FlexSim's license file, flexsim.lic, alongside the other downloaded license server materials (lmtools, lmadmin). The license file is just plain text. You can open it and examine its contents using your favorite text editor (Notepad, Notepad++, VSCode, etc.).   If you've used FlexNet licensing before, you know that often a .lic license file contains license codes and hashes that authenticate a product license on a computer system. However, this isn't the case for FlexSim.   License not included   FlexSim's license file doesn't contain any license information. Instead FlexSim licenses are held in FlexNet's Trusted Storage. That's why every customer downloads an identical license file alongside all our other license server materials.   FlexSim's flexsim.lic license file is a bootstrapper that tells FlexNet's licensing service to find FlexSim's license information in Trusted Storage, and to specify port numbers that will be used for serving the licenses.   Here are the complete contents of FlexSim's default flexsim.lic license file:   SERVER this_host ANY 26914 VENDOR flexsim port=56914 USE_SERVER FEATURE serverfeature flexsim 1.000 permanent uncounted HOSTID=ANY \ SIGN="05CB 6F61 116D 06E3 A08D CAFB FC5C BEF3 DF53 BDC6 AF68 \ 060C 27B8 9968 CB94 0515 2BE7 E30C 2FAF C0D6 1D77 CCEB 878E \ 2D67 1434 0E3F 6BA5 1FDA BD35 F98D"   Default port numbers   You can see on lines 1 and 2 above where we've defined FlexSim's default license server port numbers:   26914 (lmgrd.exe - the licensing service. Client PCs specify this port on the license server.) 56914 (flexsim.exe - the vendor daemon)   Custom port numbers   While we recommend using FlexSim's default port numbers, you can edit your flexsim.lic file to specify your own custom port numbers. Simply replace the default port numbers in your plain text license file with any valid, available port numbers you wish to use.   Automatic port numbers   Also not recommended - you can also remove the port numbers (and the “port=”) from the flexsim.lic file to allow the FlexNet Licensing Service to auto-assign port numbers, like this:   SERVER this_host ANY VENDOR flexsim USE_SERVER FEATURE serverfeature flexsim 1.000 permanent uncounted HOSTID=ANY \ SIGN="05CB 6F61 116D 06E3 A08D CAFB FC5C BEF3 DF53 BDC6 AF68 \ 060C 27B8 9968 CB94 0515 2BE7 E30C 2FAF C0D6 1D77 CCEB 878E \ 2D67 1434 0E3F 6BA5 1FDA BD35 F98D"   We don't recommend auto-assigned port numbers since the FlexNet Licensing Service could auto-assign new, different port numbers any time the licensing service is restarted (such as when your server restarts to install Windows updates, etc.).   Port numbers that change regularly can make it more difficult to maintain the firewall exceptions or other network settings needed for your license server to communicate properly with client PCs.   Resolving port conflicts   If your licensing service has trouble starting or properly hosting licenses, or if other licensing services fail after starting your FlexSim licensing service, you could have a port conflict.   You could try specifying your own custom ports as described above. This is a good solution if you know what port numbers are in use with existing services and can choose unused port numbers. After changing the port numbers defined in your flexsim.lic license file, restart your FlexSim_Licensing service.   If you’re not sure what port numbers to try, you could allow FlexNet to auto-assign port numbers itself – it tries to find and use free ports, though it isn’t foolproof. After modifying your flexsim.lic license file to allow automatically chosen port numbers, restart your FlexSim_License service. Then check the log file (lmtools, lmadmin) to see what ports were auto assigned.   If everything works, we suggest that you take the port numbers automatically assigned by FlexNet and hardcode them into your license file. This way you can maintain static exceptions more easily in your firewall. Be sure to configure your client PCs to use the new license service port number.  
View full article
A license server hosting FlexNet enabled products like FlexSim relies on a service called FlexNet Licensing Service 64. As of FlexSim version 25.2, FlexSim requires FlexNet Licensing Service 64 version 11.19.8.0 or higher.   Is FlexNet Licensing Service 64 already installed?   There is a chance that you already have a version of FlexNet Licensing Service 64 installed. Let’s check: Click the Start button or press the Windows key, then type “Services” into the search box in the Start menu, and press Enter. Windows will search for and open Windows Services Manager. If the list of services is not already sorted by name, click the Name column heading. Scroll down to services beginning with F. Do you see a FlexNet Licensing Service 64?   If you find that FlexNet Licensing Service 64 is not installed, or if you only have the 32-bit version (missing the ‘64’ in the service name), skip below to the heading Install the FlexNet Licensing Service.   Check the installed version of FlexNet Licensing Service 64   If FlexNet Licensing Service 64 is already installed, we should make sure it is version 11.19.8.0 or higher. If your FlexNet Licensing Service 64 has a lower version number, you will need to remove the older service and upgrade. We’ll get to those steps soon, but first, let’s check what version is installed:   In Windows Services Manager, scroll down to the entry for FlexNet Licensing Service 64. Double click the service name to open its Properties window. In the middle of the General tab, find the Path to executable. Copy the path location from just after the opening double quote (“) until the final backslash (\) before the filename. This is the path. It is probably something like C:\Program Files\Common Files\Macrovision Shared\FlexNet Publisher\. With the path now copied to your clipboard, note the name of the .exe. It is probably FNPLicensingService64.exe. Open a file explorer (Windows Key + E) and paste the path into the Address bar. Hit Enter to navigate to the path. Right click the .exe file that the service's Properties indicated is the service executable. Select Properties to view the .exe file’s properties. Navigate to the Properties window’s Details tab. The Product version should be version 11.19.8.0 or greater. Make sure that the Product name indicates 64-bit.   If you found that you don’t have FlexNet Licensing Service 64 installed, skip below to the heading Install the FlexNet Licensing Service.   If you found that your version number of FlexNet Licensing Service 64 is lower than 11.19.8.0, you will need to upgrade the service.   Upgrade FlexNet Licensing Service 64   To upgrade your FlexNet Licensing Service 64 to version 11.19.8.0, first complete the following: In Windows Services Manager, right click FlexNet Licensing Service 64 and choose Stop. Navigate to the Path to executable shown in the service’s properties. Rename the service’s .exe file by putting an underscore (_) in front of the .exe’s name. Continue with the instructions below under the heading Install FlexNet Licensing Service 64.   Install FlexNet Licensing Service 64   In your extracted download folder of FlexSim license server materials, navigate into the folder flexsimserveractutil. Right-click flexsimserveractutil.exe and select Run as administrator. Select the menu option Tools > Licensing Service > Install anchor service.   You should receive a confirmation that FlexNet Licensing Service 64 is now installed.     For further information on compatibility of various Flexnet licensing components, see Version Compatibility Between Components.  
View full article
Preparation   You will need to be able to transfer plaintext XML license files to and from your offline computer.   Create manual return requests   Open FlexSim Software. In FlexSim's main menu, Go to Help > License Activation. Click the Advanced tab. Go to the Manual Return sub-tab. Each of your activated licenses is listed in the dropdown selector. Select a license you want to return. Click the Generate Request button. You will be prompted to save an XML file. Choose a location and filename to save your XML return request. Repeat for all licenses you wish to return, so that all your XML return request files can be transferred at one time.   Submit your manual return requests   Transfer your XML return requests to a computer with Internet access. From your Internet-connected computer, open a web browser and login to your FlexSim Account. Click the Licenses link in your FlexSim Account's page header. Click the Manual XML link in the submenu. Upload your XML file by dragging it onto the drop zone, or click the drop zone and browse to your XML file. Your uploaded XML request will be processed. Upon completion, you will be prompted to download the XML response. Download the response XML file. Repeat for any licenses you are manually returning, so that all your XML return response files can be transferred back to your offline PC at one time.   Process your manual return responses   Transfer your downloaded XML return responses to the offline computer you are un-licensing. In FlexSim, using the same licensing interface where you generated your request, click the Process Response button. Browse to an XML return response file. FlexSim should give you an indication of successful processing of your return, and your return will be complete. Repeat to process the XML return responses for any other licenses you are manually returning.   If you have any questions or problems, please search our Answers Community for possible solutions. There is a good chance someone else has already asked your question. Still not finding what you're looking for? Submit a new question and we'll check it out. If you're including any confidential information, such as license codes, be sure to mark your question as private! You can also contact your local FlexSim distributor for live phone, web, or email help.
View full article
Top Contributors