Troubleshooting

These indicate that you need to open the Behavior Execution Engine Client Licensing Settings as an administrator. When opening the settings, right-click the shortcut or executable and select Run as administrator, entering your administrator credentials when prompted.

See the Developer Environment topic for recommendations on how to configure your IDE.

This is likely an issue with locating the installed "api" folder or "delegates" folder containing the published libraries for delegate development. Check your "settings.gradle" file to ensure the paths to the "install" folder are correct. Make sure to use '/' as the directory delimiter. Gradle may be interpreting '\' as an escape character, causing the directory path to resolve incorrectly.

If checking the "settings.gradle" file doesn't help or you are using another build tool other than gradle, you may need to revisit your dependencies and ensure that the contents of the %BEE_Install_Dir%/api directory are included in the build.

This indicates that Behavior Execution Engine cannot find your license. Double-check your licensing settings.

This indicates that Behavior Execution Engine cannot find your license. Check the following:

• Open the Behavior Execution Engine Client Licensing Settings and make sure that the Port and Server 1 are set correctly and saved.

  If you installed Behavior Execution Engine for all users, you must open the settings as an administrator. When opening the settings, right-click the shortcut or executable and select Run as administrator, entering your administrator credentials when prompted.

• On the license server, open the Ansys License Management Center and make sure that the license manager is running.
• Still in the license manager, under License File Options, select View FlexNet License, and verify that you have a Behavior Execution Engine license installed. Behavior Execution Engine licenses use the key moxie_sysml. If you do not have a Behavior Execution Engine license installed, select Add a License File to add one.

This means that the Ansys Systems Tool Kit^® (STK^®) application (not Behavior Execution Engine) cannot find its license. Manually try to open the STK application, and you should get a dialog box that states: "A current STK license could not be found." Click OK to open the STK client licensing settings, and refer to STK licensing documentation to set up your STK license.

If you do not get a dialog box with an error message, and the STK application starts normally, then this error is most likely a version compatibility issue. Ensure you have installed the same release of both the STK application and Behavior Execution Engine.

For the SysML v1 Execution Engine, if you are running into STK application version compatibility issues, you can also try attaching to a running instance of the STK application using the MoxieStkScenarioFromFile stereotype.

This occurs when you do not have a compatible version of STK Engine installed. Ensure you have installed STK Engine version 13.0 or later. See the Prerequisites topic for details on supported versions.

This could be a timing issue driven by the difference in precision between the two tools with respect to time and date. The default time precision for the STK application is at the millisecond level, but you can increase this precision. First, you must have the STK application installed and have saved at least one scenario. Then find the file called _Default.ap, which should be in C:\Users\<username>\Documents\STK_ODTK 13\Config\Defaults\_Default.ap. Open the file in a text editor and go to the Precision section. Change the Date and AnimationTime values to 6 for nanosecond precision.

If your simulation fails, you should begin your investigation by looking at the simulation log file.

This can occur when there are different versions of Behavior Execution Engine and the ModelCenter application installed on the machine. Check to ensure that the same Ansys product version was installed for both. This can sometimes be an issue if installing a different version of the STK Enterprise application compared to installing the ModelCenter application, or vice versa.

This can occur when Behavior Execution Engine is installed in Program Files.

Try copying the contents of the installation directory to another directory that you can access. Then, double-click the Behavior Execution Engine component in the ModelCenter workflow or Component Tree, select Options, and set BEE Install to the directory you copied everything into.

When running from the ModelCenter application, Behavior Execution Engine saves all its logs to the ModelCenter application logs folder.

When the ModelCenter application interacts with Behavior Execution Engine, it starts a separate process to interrogate and execute the SysML project. If you manually close the console window for this process, or it otherwise dies without the ModelCenter application closing it, the application will still think the process is available.

Right-click the Behavior Execution Engine component in the ModelCenter workflow or Component Tree and select Reconnect. If you still see the error, you may need to restart the ModelCenter application.

Ensure that you have the JAVA runtime installed and registered with your windows environment directories as the JAVA_HOME path specifying the path to the folder containing java.exe.