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:  

In the last little while we've had several questions regarding Picking Line operations. (How to make one, how to simplify, how to set up one using Process Flow & Lists, etc.) So I've put together a very simple little model utilizing Process Flow and a basic List structure, that shows a basic picking line. It creates orders, and sends them by tote via a conveyor, and Operators will pick items from their respective stations to fulfill the orders into the tote, before sending it to Checking and Shipping. Note that this could easily be adapted into an assembly line situation as well. pickingstations.fsm

FlexSim 2020 Update 1 Beta is available. (Updated 24 March 2020) To get the beta, log in to your account at www.flexsim.com, then go to the Downloads section, and click on More Versions. It will be at the top of the list. If you have bug reports or other feedback on the software, please email dev@flexsim.com or create a new idea in the Development space. Release Notes Updated the Statistics Collector to be simpler and more user friendly. Added a PowerPoint FlexScript API. Added an HTTP FlexScript API. Added a sorting tab to various charts. Improved performance of chart templates. Replaced the code profiler with a new Performance Profiler. Added a Memory Profiler. Added OnEntry and OnExit events to TaskExecuter objects. Added an icon to library items that launch a pop-out library of choices. Reorganized the dashboard library using the pop-out library to consolidate charts with multiple visualizations. Updated the WebServer to use the Version Selector. Added a Find/Replace UI for global tables. Added support for Ctrl-F and Ctrl-H keyboard shortcuts for various windows. Added support for renaming objects using the F2 keyboard shortcut. Added a Vec3 overload to the Object.setRotation() method. Added a stop parameter to the userinput() command which will stop code execution until a value is entered. Added a default parameter to the realtime() command that returns realtime(1)+0.001*realtime(2). Updated various pickoptions to use the TaskSequence and TaskExecuter APIs. Added tutorials for the Statistics Collector. Fixed some issues with the importtable() command. AGV Added new Train functionality. Added offset travel functionality to the AGV network. Added a time-based trailing option. Added the routing drawing feature to a right click option. Updated Quick Properties' apply to all selected objects functionality to work with AGV objects. Made arrows bigger. Fixed several spinners in Quick Properties not applying immediately. Backwards Compatibility Note: the following changes may slightly change the way updated models behave. Changed behavior for when a TaskExecuter is connected to an AGV network, and is set to use the navigator for its offset travel. Previously, the navigator was hard-coded to find the closest control point. Now, you instead need to add an OnAGVOffsetTravel trigger to the navigator, wherein you can direct the AGV how to offset. People Added clipboard, test tube, and pill bottle flow items. Added a Max Speed property to Equipment objects. Updated Transport and Equipment objects to do low priority returns. Added the ability to install instanced People flows. Updated the LocationStaytimeHistory chart to handle people entering and exiting transports inside a location. Process Flow Added an AGV travel activity. Updated the Sink to notify parent tokens on a Run Sub Flow activity that the child token finished the subflow. Updated the Wait for Event and Event-triggered Source activities to be able to display more than one link at a time. Updated the sampler for Universal Edit fields to display process flow variables and current labels when sampling white space. Added a pop-out library for choosing the shape of Container objects. Added a pop-out library for choosing the type of travel activity. A* Updated the Heat Map to use a Color Pallete.

Run FlexSim "in the cloud"? Instead of provisioning a desktop or laptop PC that meets FlexSim's recommended system requirements, you may prefer for your FlexSim users to use a thin client PC which connects to a more powerful back end system that actually runs FlexSim. FlexSim does not test our products in such environments, so your user experience may vary. Meet the system requirements It is important that the remote system meet or exceed FlexSim's recommended system requirements. Usually for CPU and RAM that is not a problem. In the past, the biggest hurdle was typically graphics. Does the remote machine support hardware accelerated graphics, and support streaming those graphics to the thin client where the user is actually sitting? If the graphics are not accelerated, or if accelerated graphics can't be streamed to the user, then the system doesn't meet FlexSim's requirements and you may have a bad user experience. In the past In the past, provisioning such a system to meet FlexSim's requirements was quite a specialized combination of hardware and software. Even today not every cloud provider has the infrastructure to stream accelerated graphics. Our anecdotal experience is that such set ups are becoming more common among 3rd party cloud providers. Going forward Major players now seem to have mainstream support for hardware accelerated graphics: https://aws.amazon.com/ec2/elastic-graphics/ https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sizes-gpu https://cloud.google.com/gpu/ As mentioned above, FlexSim is not targeted to these environments and the software is not tested in these environments, so your mileage may vary. Conclusion With more and more cloud providers enabling hardware accelerated graphics, there is a chance that FlexSim could work well on a cloud-based platform. If you have tried running FlexSim remotely using one of these or another cloud provider, we'd love to hear your experience. Please comment below to let us know about your setup, what worked, and what didn't.

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.

Background   The method for licensing a single-user client PC saves client PC license settings to the Windows profile data of the signed in user, so license settings are saved on a per-user basis.   In cases where the exact number or identity of PC users is not predetermined, such as in a university computer lab, it is impractical to license users individually in this manner. Another use-case for this method is when FlexSim Software is automatically pushed or deployed to client PCs. Having the licensing as part of the deployment is useful.   For this mult-user method we'll use a license file on the client PC to license FlexSim software generally for any user of the PC.   Use a license file   Create a plaintext license file   On the client PC create a plaintext license file named flexsim.lic with the following 2 lines (exclude any line numbers):   SERVER 127.0.0.1 ANY 26914 USE_SERVER   If your Windows settings do not show file extensions, it is possible that your flexsim.lic license file is actually named flexsim.lic.txt, which will not work. Be sure to show file extensions and make sure your license file ends with the .lic file extension. The actual name of the file is not important (it could be helloWorld.lic, for instance), but it needs to end in .lic.   Modify   On the client PC, modify your new license file with the following changes:   On line 1 change "127.0.0.1" to the IP address or fully qualified domain name of your license server. If you modified your license server with custom port numbers, on line 1 replace the default port 26914 with your custom port number.   Install   With FlexSim software installed on a client PC, your new license file should be copied into FlexSim’s installation directory in the following location:   C:\Program Files\FlexSim <version>\program\   Your exact folder path could differ based on custom installation locations or FlexSim version, but it should be placed into FlexSim’s program\ folder.   Multiple license servers?   If your FlexSim licenses/seats are spread across multiple license servers, you can configure your client software to try to pull a license from any of your multiple license servers. Simply create a new license file for each possible license server and save each to the same program\ folder. In this scenario, in your program\ folder you would have multiple license files listed, like this:   flexsim1.lic flexsim2.lic flexsim3.lic etc. Each license file should reference a different license server and its port number.   Next   Check out the next article to learn how to verify that your client PC is licensed, and what to do if it isn't: License Server - Verify client PC licensing.  

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.

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.

"switch by case" is a stucture in many programming languages. It is a availbale in Flexscript. A case must be a number for a switch by case structure in Flexscript. A decide activity can switch even to string value cases. All you need is to rename the connector from a decision activity to a following activity. process_flow_by_case.fsm

Background   Often a client PC is used by a single user who should have access to change license settings.   This method saves licensing settings to the user’s Windows profile. In this manner licensing is saved on a per-user basis and should be completed in advance for each FlexSim user on this client PC.   In some situations it is better to license the PC once for any user who might log in. This can be the case for a university computer lab, for instance. If your situation would be better served by licensing the software one time for all users of the PC, please check out our guide to license a mult-user client PC.   Configure Licensing   To license an individual Windows user, do the following while logged into Windows as that user:   Open FlexSim software on the client PC by right clicking the program icon and choosing Run as Administrator. You won't normally need to start FlexSim under elevated privileges, but sometimes licensing the PC for the first time requires it. Go to the software’s main menu and select Help > License Activation. Navigate to the License Server tab. Check Use concurrent licensing. Enter the License Server Address using the form port@host, where host is an IP address or fully qualified domain name (FQDN). For example, if your license server is reachable via the FQDN licenseserver.mycompany.com: If you used FlexSim’s default license service port number, enter 26914@licenseserver.mycompany.com. If you specified a custom port, use that number instead. For example, if you entered 27500 as your custom port number, you should enter 27500@licenseserver.mycompany.com. Click Apply Configuration.   Multiple license servers?   If your FlexSim licenses/seats are spread across multiple license servers, you can configure your client software to try to pull a license from any of your multiple license servers. Simply enter all available license server options, separated using a semi-colon, like this:   26914@lic.server.one;27001@lic.server.two;27009@lic.server.three   Here is an example image:   The software will attempt to contact each license server in turn until it obtains a seat or has attempted all license servers and failed.   In the example above, lic.server.one and lic.server.two are fully qualified domain names to properly configured license servers, with lmgrd serving on ports 26914 and 27001 respectively. You could also use an IP address instead of a FQDN.   Next   Check out the next article to learn how to verify that your client PC is licensed, and what to do if it isn't: License Server - Verify client PC licensing.

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.

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.  

Greetings, I would like to share my latest FlexSim creation with the community, HUGE thank you to the flexsim overlords for creating such an awsome software https://youtu.be/WyfNS6vfLZE. G

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.  

First things first Sometimes the easiest method for fixing a standalone license is to simply activate the same license again. No need to return first. Just get the full activation ID for any broken licenses and activate them again. Look for the broken licenses within FlexSim by going to Help > License Activation > View Licenses tab and pressing the View Licenses button. Scan the license information for licenses that indicate they are **BROKEN**. For licenses that are broken, look up the full activation IDs in your online FlexSim Account. Using the full activation IDs for each broken license, activate the licenses normally within FlexSim by going to the Activate tab and pasting and activating each activation ID in turn. No need to return the licenses first. In case you need more detailed activation instructions, see: Standalone - Activation - Online Standalone - Activation - XML / Offline If you completed the 3 steps above but encountered error messages, it is time to manually repair your licenses. Okay, time to repair Standalone licensing does not have a method for repairing online. Here are the steps to manually repair your license. These instructions apply to FlexSim 2016 and later. If you are using an older version of FlexSim, please download FlexSim's latest version and follow these instructions. You can manage your older FlexSim licenses from the latest software - the License Activation window will still show your older licenses and you'll be able to complete all these steps for your broken pre-version-16.0 licenses. Open FlexSim as an administrator by right clicking the program icon and selecting Run as Administrator. From the main menu, go to Help > License Activation. Go to the Advanced tab, then the Repair tab. For each broken license listed in the License selector box, click the Generate XML Request button. Save each XML file to a convenient location on your computer. Log in to your FlexSim Account. From the top navigation header click the Licenses link, 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. In FlexSim (your instance opened above in step 1 using Run as administrator), you should still be on the same License Activation > Advanced > Repair tab. Process each response by pressing the Process Response button and browsing to an XML response. FlexSim should successfully repair the license. After repair it should be usable and returnable. 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.

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 Tools > Manual Activation > Generate Request. Select the Repair option. Paste the Fulfillment ID into the field (Ctrl-V). Delete any spaces that may have been included before or after the pasted Fulfillment ID. Browse to a location where you will save the XML repair request. Choose a file name for the saved file. Press the Generate button. Repeat steps 4-10 for any broken licenses. Transfer the XML repair request files to an Internet connected computer. The files are plain text XML and can be manually examined in any text editor if necessary for security purposes. Be sure not to modify the files, including line endings. If the file is modified in any way, the various hashes in the file will register the change and the request will fail. Log in to your FlexSim Account. Click the Licenses link in the top navigation menu, 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. Transfer the XML response files back to your license server. In flexsimserveractutil.exe (your instance opened above in step 1 using Run as administrator), from the main menu, choose Tools > Manual Activation > Process Response. Process each response by browsing to an XML response, then pressing the Process button. The license should be successfully repaired. After repair it should be usable and returnable. 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.

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.

I have created the following model to use elevator for different floor. I am not sure what I have missed out that the elevator is not working. Please advise me. Thanks multi-floor.fsm David

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 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.