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

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:  

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.

Sometimes things don't work out the way you thought they would. Usually, at least with license servers, it just means that you missed a step, or there is some issue that wasn't considered. Below we'll outline some things you should check:   Server configuration   - Check the service   Is the FlexSim_License service you created using LMTOOLS up and running? When you created and configured your licensing service, did you check the log file? Look for any errors or issues in the log. Troubleshoot the service if necessary.   - Local test   You can rule out configuration issues by installing FlexSim locally on your license server. Configure the local FlexSim installation using the port you specified (default is 26914) and the local IP address 127.0.0.1, to point your local FlexSim installation to the local license server to see if your license server can license itself.   - Connectivity problems   If your local test works, then your client PC licensing issues may actually stem from connectivity problems. In that case, check out our article Client/Server connectivity.   - Check, check again   Double check that your server is configured properly. When viewing your license service’s log file, you should see indications of ports in use, features being served, etc. (lmtools, lmadmin). If no features are listed, or port numbers are different than what was expected, please revisit the configuration guide (lmtools, lmadmin). Carefully read and execute each step of the instructions to make sure that you have properly configured your license server.   Overzealous anti-virus   Some anti-virus solutions prevent unrecognized services from running or accessing necessary functionality. If a local test (above) works, you may only need to test disabling anti-virus solutions on the client PC. Or if you're trying to get the license service to run on the server, you may need to test there also. Remember to reactivate your anti-virus software after this experiment.   Version or product mismatch   Your actual license, activated to your server using flexsimserveractutil.exe (online, manual), must be for a FlexSim version the same or greater than the software’s version number.   Your license is also for a specific product (FlexSim vs FlexSim Healthcare vs FlexTerm, etc.).   See the article FlexSim Version Numbering, for more information regarding FlexSim versioning and how it relates to licensing.   Seats all in use   If your FlexSim client software is not obtaining a license from the server, it’s possible that all seats are already in use on other client PCs. Check the log files (lmtools, lmadmin) to determine where your seats are currently in use.

Verify Connectivity   Issues with client-server licensing can often be traced to communication issues that prevent the client PC and server from communicating. The first step is to verify whether the client PC can connect to the license server over the licensing ports.   Even if you successfully establish connectivity, remember that server configuration or license issues can also keep a client PC from becoming licensed. See our Troubleshooting Tips article for guidance.   Basic connectivity (ping test)   On the client PC, click the Start button or press the Windows key, then type “cmd” into the search box in the Start menu, and press Enter. Windows will search for and open the Command Prompt.   From the command prompt, enter ping [server name or IP address]. For example, if your license server has a local IP address of 10.0.0.135, then type on the command line ping 10.0.0.135.   If you are referencing your license server by name in FlexSim software’s License Activation interface, use the same fully qualified domain name here instead of the IP address:     If your client PC receives a response from your license server, then the server is visible across the network, by name or IP address, from the client PC.   Advanced connectivity - ports test   If you can pass the ping test the next step is to see if the required ports are open for communication. There are a couple of methods you can use to test if your client PC can connect to your license server over the ports specified in the .lic file.   PowerShell Test-NetConnection   From Windows PowerShell, enter Test-NetConnection [server name or IP address] -Port [port number]. For example, if your license server has a local IP address of 10.0.0.135, and is hosting FlexSim licensing over our default ports 26914 and 56914, you should run the following two commands:   Test-NetConnection 10.0.0.135 -Port 26914 Test-NetConnection 10.0.0.135 -Port 56914   If both of these commands include in their response TcpTestSucceeded : True, then the required connectivity is available. Test-NetConnection documentation   Telnet   Check out our tutorial video at https://flexs.im/telnet that guides you through the basic steps of enabling telnet on your client PC, then using it to test port connections from a client PC to your license server.   Double check your configurations   If you can't establish a ping connection or a port connection, use the suggestions below to double-check your settings. Or perhaps you passed the connection verification checks but FlexSim Software is still not getting licensed? These connectivity tips may reveal the solution:   CLIENT PC SETTINGS - You may have a typo or otherwise have misconfigured the settings that point your client PC to the license server. Double check that your settings are entered using the correct format (single-user client PC, multi-user client PC).   PORT & ADDRESS - Double check the port number and server address/name used in activating licenses on your client PC. Make the port number specified is the number in use for your license service. Our default port number is 26914 but enter your custom port number if you set your own.   SERVER FIREWALL - Did you add the required exceptions to your license server’s firewall (lmtools, lmadmin)? To any other network appliances and firewalls (lmtools, lmadmin)?   Connectivity suggestions   You've triple-checked your client PC settings. You've set firewall exceptions. The port test still shows that you can't connect from the client PC to the server. What can you do?   These aren't fixes, but they can help you narrow the source of the problem so that you can find a solution.   CHECK THE LICENSE SERVER - Maybe your license server isn't actually serving your licenses. You can install the FlexSim simulation software locally on your license server, then using the port you specified (default is 26914) and the local IP address 127.0.0.1, you can point your local FlexSim installation to the local license server to see if your license server can license itself. If it can't, check out these license-server troubleshooting tips (where you'll also read about this local test troubleshooting method).   DISABLE FIREWALLS (temporarily as a test) - A connection issue could be caused by a firewall configuration problem on the client PC, on the license server, or on some network appliance in between. One at a time, disable intervening firewalls on the client PC, the license server, and appliances in-between, as applicable. With each disabled firewall, retest connectivity. If connectivity is established after disabling a firewall, work on that firewall's configuration, then reenable it. Test again. Repeat for each firewall until a connection between client and server can be established.   DISABLE ANTI-VIRUS (temporarily as a test) - Some anti-virus solutions will block application communications. Disable anti-virus software on the client PC. If nothing changes, also disable anti-virus on the 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.   ASK YOUR FRIENDLY NEIGHBORHOOD ADMIN - Your network may have settings, topology, filtering, etc. that affect the client PC’s ability to communicate with the license server. Work with your network administrator to make sure the client PC can communicate with the license server across your network using both port numbers - for the licensing service and the vendor daemon. See default and custom port numbers.

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.

Have you received this licensing error?   Operations error: 7288 The activation of the fulfillment is denied by the activation policy because fulfill count exceeded the available seat count.     Here are some common reasons you may encounter this error, along with some possible solutions.   All seats are already in use   Problem: All the seats of this license are already activated. There are no available seats left to activate.   Solution: You must return a seat from a computer where it is currently activated. Once a seat has been successfully returned it is available for a new activation.   If you are not sure where your license is currently activated, there are two main methods for finding out:   Go on a hunt: On each computer where the license may be activated, check the license status by opening FlexSim and going to Help > License Activation > View Licenses tab > press the View Licenses button. This will show you the license information for the current PC. Check the history: You can view your activation/return history from your FlexSim account's licenses page. On the Licenses page, expand the folders until you can see the Activation ID you are trying to track down. Click the Activation ID to load the history for this license. This history includes dates/times of the activations and returns. If the information is available it will also list the computer name where the license was last activated and the Windows username of the logged in user who completed the action. If the computer where your license was activated has been stolen, destroyed, wiped, etc., please contact your local distributor to discuss a solution.   Activation ID is obsolete   Problem: You are trying to activate an obsolete activation ID. An activation ID can become obsolete if it has been cancelled, replaced, or upgraded.   Solution: Make sure to use the most up-to-date version of your license. Log in to your FlexSim account to view your latest license codes.   Consider the following scenario: You purchased a FlexSim license and were emailed a license code. You used that license on your laptop for several years, upgrading FlexSim as new versions were released and following the prompts to upgrade your license as needed. Now you have purchased a new laptop. You successfully returned your license from your previous laptop. On the new PC you installed FlexSim and needed to get it licensed. You looked up your original license code from your years-old email, but when attempting to activate you received error 7288.   The reason is that over the years as you upgraded FlexSim you also upgraded your license code. The old, original license code is obsolete. You must log in to your FlexSim account to get the most recent license code. With the new license code you are able to successfully activate your license on your new laptop.

Does your license server randomly stop serving your FlexSim seats? When you check the logs, do you see error messages like the following? 5:34:42 (flexsim) Trusted storage binding change detected! Vendor daemon is being shutdown. 5:34:42 (flexsim) EXITING DUE TO SIGNAL 65 Exit reason 42 5:34:47 (lmgrd) flexsim exited with status 65 (Trusted storage binding change detected.) 5:34:47 (lmgrd) Vendor daemon shutdown - trusted storage binding change detected. Hosting your license server on a VM Many organizations host their license servers on virtual machines and this is a perfectly fine and fully supported way to host your licenses. However, you should be aware that some common virtual machine workflows can disrupt your license server. For instance, you may encounter the errors above if you restored your VM's state to a live snapshot. A live snapshot takes a snapshot of memory as well as disk. Hyper-V is an example of a hypervisor that allows live snapshotting. If a virtual machine does a revert-to-live-snapshot operation, restoring the memory and disk to a previous state, it can interrupt the integrity of your server's trusted storage. To prevent any corruption of your Trusted Storage state, Trusted-Storage-based license servers poll Trusted Storage every 90 seconds to determine if a snapshot restore has occurred. Hence, within at least two minutes of a Trusted-Storage-based license server being reverted, it will shut down, with server log messages similar to the log block above. This shutdown helps preserve the integrity of your license server's local trusted storage. Restoring functionality As you can see at the bottom of the error message, the resultant state of your license server is that your vendor daemon is shut down. This means that your license server is no longer serving FlexSim seats. To restore full functionality, simply start (or restart) the service from Windows services: Or if you're hosting your licenses with lmadmin, start (or restart) the vendor daemon:

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

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.

Have you received this licensing error? An error occurred in the activation request Operations error: 7174 Only deployed entitlement line item can be fulfilled. You may encounter this error if your license code is no longer valid or is in need of support. Here are some common scenarios where this might happen: If this was a timed license that has expired, it is no longer viable and was likely obsoleted. If the license was upgraded, you need to make sure you're using the latest version of the activation ID, as any older versions of the license code will not work once an upgrade of the same license has been used. If the license model was changed from standalone to license-server (or vice-versa) you may be trying to use an old license that was replaced. If your license was put into a support state and was not changed back. If you are encountering this error, please start a new Private Question and include your activation ID. We'll be able to look up the specific situation for your license. Or you can reach out to your local distributor for direct phone, email, or web support.

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.

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.

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.

Failed to connect to the license server Have you ever encountered this error? ERROR: flxActAppActivationSend - (50041, 41143, 34) "Failed to connect to the license server or Operations server. Recover: check connection and that server is operational." This error indicates that your computer is not able to communicate with FlexSim's license server. If your computer is purposely air-gapped, please use the Manual XML licensing methods listed at the bottom of this article. Protocols, ports, and addresses A license activation or return will attempt to make HTTP (port 80) and HTTPS (port 443) connections, currently with the following servers: license.flexsim.com www.flexsim.com sw.flexsim.com sw1.flexsim.com Make sure these communications are allowed on your network. To make sure you maintain compatibility with any possible future changes to our server configurations, consider configuring your network to allow communication with any *.flexsim.com subdomain. Troubleshooting Any of the following could prevent your FlexSim software from communicating with FlexSim's license servers: Your computer is air-gapped or otherwise blocked from communicating over the Internet. The FlexSim software is not allowed to communicate over the Internet. FlexSim's above-listed addresses are blocked on your network or computer. Your network communicates through a proxy service but you haven't configured the proxy server settings inside FlexSim. FlexSim's license server may be down due to some outage or maintenance. Let's look at solutions for each possibility: 1. No communication / connection issues If your computer is disconnected from the Internet, you will need to connect in order to activate or return a license online. If this is not possible, please use the Manual XML licensing methods listed at the bottom of this article. You may also see this error if you're on a flaky wi-fi connection, or a slow network connection. The communication must be solid enough that it does not time-out, where the client software is able to receive a response in a timely manner. If you are connected to the Internet but on a slow or unreliable connection, you can fall back to the Manual XML licensing methods, or you can retry the online activation multiple times - it may eventually complete successfully after several attempts. 2. FlexSim's communications are blocked If your computer is connected and you can visit other sites, but FlexSim's licensing actions are still blocked, it could be due to an anti-virus solution or other security measure preventing FlexSim's communications. Work with your IT team to disable such measures and test if FlexSim is allowed to communicate. If so, configure your security measures to allow FlexSim to communicate for licensing purposes, or if that is not possible, use the Manual XML licensing methods listed at the bottom of this article. 3. FlexSim's license server is blocked Perhaps one or more of FlexSim's license server addresses (listed above) is blocked on your network. This could be a deliberate blocking of a specific address, or more likely a general block of a wider range of sites or IP addresses. Work with your IT team to determine if this is the case and if the block can be removed. If that is not possible, use the Manual XML licensing methods listed at the bottom of this article. 4. Proxy is not configured If your network settings require that FlexSim communicates through a proxy server, you'll need to configure the software to do so. For FlexSim version 23.0 and higher you'll do this directly in the software. From FlexSim's main menu, navigate to Help > License Activation > Advanced > Proxy Details. Fill in your proxy server information and click the Apply button. If you're using an older version of FlexSim, you can download this attached model. This is an older model file compatible with FlexSim version 5.0 and up. It has a Model Control GUI that is an extension to the License Activation window that includes this extra tab where you can put proxy details. proxy-details-v5.fsm 5. License is already activated but fulfillment is broken The license you're trying to activate may already be activated on your computer, but in a broken or unusable state. Follow the instructions for your license hosting situation to remove the broken fulfillments: Standalone - Delete fulfillment License Server - Delete fulfillment 6. License server offline There are circumstances when FlexSim's main license server can go offline. Most commonly this is due to regular updates or patches being applied. In this case the server will return to normal operation shortly. Please be patient and try again in a few minutes. In cases where longer maintenance is planned you will find a notification at the top of this community indicating the purpose, date/time, and expected duration of such maintenance. This notification will be given as early as possible to help you plan around such downtime. In rare circumstances an outage could be caused by a failure in one or more of the license server's databases, operating system, server hardware, networking, or data center. When such an outage occurs, we will post a notice at the top of this community and work to restore service as quickly as possible. Help! I need support! If none of the above suggestions work for you, please start a new question and include as many details as possible about what you've already tried and what you see happening. Please be aware that if FlexSim's license server is online and other clients are able to activate and return their licenses successfully, that the issue is within your organization's network or on your computer. The proper place to turn to for support will be to your own internal IT teams. The above information, including the protocols, ports, and addresses and the different troubleshooting suggestions should be enough information to solve the issue. Manual XML licensing If you are not able to allow FlexSim to communicate over the Internet, please use our manual XML activation/return methods for offline systems: Standalone - Activation - XML / Offline Standalone - Return - XML / Offline License Server - Activation - XML / Offline License Server - Return - XML / Offline

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.