FlexSim Knowledge Base
Announcements, articles, and guides to help you take your simulations to the next level.
Sort by:
Have you received this licensing error?   Operations error: 7581 Online return/repair request for the activation ID example.com01-ABCDE-FGHIJ-KLMNO-FSENT22.2 is not originated from the original client machine.   This error means that the licensing system did not recognize the the computer that requested the repair is the original computer where the license was initially activated.   This can happen when: It is not the same computer. Maybe the user activated a license, then moved the hard drive to a new computer (or cloned it, etc). This would break the license, and it wouldn't be able to repair because the licensing system recognizes that the computer hardware is different. There was a significant change to the computer. A large operating system update, a change to the hard drive's boot sector (for instance, installing a 2nd operating system to dual boot), or another significant hardware change.   In this case the license cannot be returned, and it cannot be repaired. You will need to contact your local FlexSim representative to explain the situation.   As you work with your FlexSim rep, they will guide you in deleting your unreturnable/unrepairable fulfillment (license server, standalone), then after your FlexSim rep performs a license force-return, your license should be available again for a new activation.
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
When you try to activate offline, the following error might appear in the console: ERROR: flxActSvrActivationRespProcess - (50019, 42107, 10246) "Failure to process response for an unspecified reason. This error may be returned when a valid failure response is received, for example when the activation server denies a request. Recovery: check parameters used for the request." License Server Manual XML Activation error example: Standalone Manual XML Activation error example: If you encounter this error, check the response.xml file you are attempting to process. If it includes the text SERVER_CONFIG or CLIENT_CONFIG, but your Trusted Storage is already configured, you may receive this error. With Trusted Storage already successfully configured, you must generate a brand new activation request. Upload the new request to your FlexSim Account for processing. If the license is available you will be able to download the XML response. This response should process and successfully activate your license. Full instructions for performing manual XML licensing for license servers can be found in our license server installation instructions document. ===== Here are some other items to keep in mind with manual XML licensing on your license server: Download the response XML files and transfer them to their license server without modification. Modifying the XML files in any way will "break" them. This includes line endings and other white space. The files include checksums and if the files change they will not work. The destination license server needs to be the same system where the request was generated. The FlexNet Licensing Service 64 needs to be installed, be a high enough version, and be running properly as a Windows service. Checking these items is covered in our license server installation instructions starting on page 6 with 3. FlexNet Licensing Service. flexsimserveractutil.exe may need admin privileges to write to the proper places on the system. Be sure to right-click the application and choose Run as Administrator.
View full article
Remembering the proper credentials To log in to lmadmin's Administration area you need know the port number your license server manager is hosting on and your lmadmin admin password. lmadmin's default port number for serving its web-based user interface is 8090. There is a very good chance that your system is hosting lmadmin on its default port. On your license server, open a browser and go to http://127.0.0.1:8090 to see if this will open lmadmin's web-based interface. The default login information for lmadmin's Adminstration area is username admin and password admin. Upon your first logging in to the Administration area you would have been prompted to create your own new password consisting of at least 8 characters. If you have forgotten either the port number or your admin password, there is unfortunately no way to recover these. You will need to uninstall, then reinstall lmadmin. If you do not wish to do so at this time, you should be able to start serving your upgraded FlexSim licenses by restarting the lmadmin64 Windows service. Logging in to lmadmin Use a web browser to connect to the lmadmin service at https://127.0.0.1:8090 (specify a different custom port besides 8090, as necessary). The FLEXnet Publisher interface should open. Click on Administration to sign in. After logging in to the Administration portal, click the Vendor Daemon Configuration tab on the bottom left. Click on the flexsim daemon. Reread the license If there is a Start button, that means that your flexsim vendor daemon is currently stopped. Press the Start button to start the vendor daemon using your upgraded licenses. If there is a Reread License Files button, that means that your flexsim vendor daemon is currently running, and serving the old licenses. Press the Reread License Files to start serving your newly activated and upgraded licenses.
View full article
Have you received this licensing error? Operations error: 7284 Cannot perform support actions on inactive fulfillment record FID_ ... (entire fulfillment ID listed) You may encounter this error during an attempted license return or repair. This error means that the fulfillment was already returned. A fulfillment is an activation of a license. Once that activation has been returned to the main license server, the fulfillment becomes inactive. It is meaningless to return or repair a fulfillment that has already been returned. So, how do you have an inactive fulfillment still on your computer if it was supposedly returned? There are a couple of ways this can happen: Someone requested that the license be force-returned. Sometimes a license can be lost, so a client contacts their local distributor to force the license back. Later on, the license is found activated on a PC, however it will not be returnable because the license was already force-returned. You returned your license normally, but later restored your computer from a backup or otherwise rolled back to a previous state. This may break your license, but in trying to repair the old fulfillment, the main license server reports to you that actions cannot be taken on that inactive fulfillment - it was already returned. The point with this error is that FlexSim's main license server has a record that your fulfillment was already returned. The fulfillment you are trying to return or repair is inactive - no actions can be taken on it. The solution is to delete the fulfillment record from your PC: License Server - Delete fulfillment Standalone - Delete fulfillment
View full article
Have you received this licensing error? Operations error: 7466 The return of the fulfillment is denied by the return policy because max return exceeded. This error indicates that returns are disabled for your license. Your license is configured for one-time activation onto a computer. If you believe your license should be able to transfer from one computer to another, please contact your local distributor to discuss the situation.
View full article
Have you received this licensing error? Operations error: 7131 Server activation is not allowed to activate entitlement line item: Make sure the license model is a server license model. You may encounter this error if you attempt to activate a standalone license using flexsimserveractutil.exe on a license server. A standalone license is intended to be activated directly within FlexSim Simulation Software installed on a client PC. Please see our instructions for standalone licensing for the procedures to use with your standalone FlexSim licenses.
View full article
Have you received this licensing error?   An error occurred in the activation request Operations error: 7109 Invalid activation ID:     This error can occur when you are attempting to activate a standalone license online using the Activate tab.   You may encounter this error if you have incorrectly typed your activation ID, left the field blank, or if the system otherwise does not recognize the license code you have entered as a valid activation ID.   Some older versions of FlexSim also were not able to remove spaces or other whitespace from the beginning or end of the activation ID field, so be sure that any spaces or other extraneous characters are removed from both the beginning and ending of the license code text.
View full article
Have you received this licensing error? An error occurred in the activation request Operations error: 7189 Client activation is not allowed to activate: Check the license model to make sure a client can activate. You may encounter this error if you attempt to activate a network license directly within FlexSim software. A network license is intended to be installed on a license server using a FlexNet license manager - either lmtools or lmadmin. Please see our instructions for installing a license server, which also include directions for connecting your client software to the license server to obtain a license.
View full article
Have you received this licensing error? Operations error: 7032 Invalid fulfillment ID: FID_ ... (entire fulfillment ID listed) You may encounter this error during an attempted license return. This error means that the license server has no record of your license activation, and therefore is not able to recognize the return action from your unknown activation. This error should only be encountered under a few rare circumstances: 1. Rollback on FlexSim's main license server FlexSim's main license server could be rolled back to an earlier time due to a necessary database restoration in order to mitigate database corruption or other unforeseen issues or circumstances. License actions, such as license activations or returns, that occurred after the last viable backup was saved, but before its restoration, will be lost. The solution for any license affected will consist of one or both of the following: If an activation occurred during the lost time period you would need to manually remove any un-returnable fulfillments. Standalone - Delete fulfillment License Server - Delete fulfillment If a license return occurred during the time period, you should contact your local FlexSim distributor to request a force-return. Explain the error and this situation. 2. Change to FlexSim's licensing infrastructure Your FlexSim product has reached End-of-Life and the license server under which your license was originally activated has been retired. This situation is outlined in FlexSim's End User License Agreement > Software End-of-life. As of this writing, FlexSim has never retired any of our FlexNet licensing infrastructure and we currently have no plans to do so. This item is included here for completeness' sake and in the event that such future licensing changes occur. If you are using software past its End-of-Life date and you think this problem may be affecting you, please contact your local FlexSim distributor.
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
This article is used to aggregate all other licensing articles under one heading. You can use the navigation panel in Answers' right column to navigate between the various licensing articles in this tree. Sharing your licenses License Models Licensing Procedures Licensing Errors FlexSim Feature Limitations by License Type License server - feature pools - only checkout features for license type FlexSim Version Numbering, including how licensing works for a given version number In addition, the following links contain some general licensing tips. These will likely be added to a future article. A few of the items are outdated, but in general the advice is still good. General licensing tips (Mar 9, 2018) License Q&A (Jul 17, 2017)
View full article
Top Contributors