Appendix A. Known Issues and Limitations

Engineering Knowledge Manager

EKM Troubleshooting Guide |

8.2. Tablet use: Issues and Limitations |  |
Prev |  |

## Appendix A. Known Issues and Limitations

The following list contains known issues at the time of release, as well as system and software limitations.

- Installation and Configuration Issues

- Sign-In and Access Issues

- File Transfer Issues

- Data Management Issues

- Job Management Issues

- Process Management Issues

- Customization and Scripting Issues

- Browser-Related Issues

- Usability/Interface Issues

## Installation and Configuration Issues

- When installing EKM to a Windows Server, an "Enterprise" prefix may be incorrectly added to the `ekmURL` element in the ekm.xml file. For example,

  `<ekmUrl>http://Enterprise.hostname:8080/ekm</ekmUrl>`

  This is due to an issue with Java.

- When creating a workspace in a clustered setup, the EKM console may report an error even though it appears as though the workspace was created successfully.

- When importing a workspace, applications that were starred as favorites in the original workspace will no longer be starred in the new workspace.

- When browsing for network share directories in the EKM installation wizard, clicking Browse may not display available network shares. If you specify no path, a local file system path, or an invalid UNC path in the directory field before clicking Browse, the file chooser will only display a local file system view. If you want network shares to be displayed, you must (at a minimum) enter the base of a valid UNC path in the directory field before clicking Browse.

- In a multi-node EKM server setup on Windows, registering EKM as a service on a non-primary node may fail, resulting in an error similar to the following:

      C:\ekm\node2\v182\bin>register_ekm_service.cmd
      The system cannot find the path specified.
      Error: Unable to access jarfile wrapper.jar
      Press any key to continue...

  Currently, the `Yet Another Java Service Wrapper` is not getting installed on non-primary nodes.

  To work around this issue:

  1. On the primary node, locate the following folder:

     \ekm\node1\v182\programs\yajsw-beta-12.05

  2. Copy the folder to the non-primary node:

     \ekm\node2\v182\programs\yajsw-beta-12.05

## Sign-In and Access Issues

- If you are connected to EKM via Workbench, and Workbench crashes or does not exit cleanly, you will not be disconnected from the EKM server. This means that if you try to connect to EKM again, you will get an error. To resolve this issue, a member of the `admin` group must forcibly sign you out of EKM. See Forcing the Sign-out of a User in the Administration Guide for details.

- EKM cannot validate a connection’s credentials if the connection is currently open in Workbench. The connection will remain displayed in the Connections dialog box and appear as an available connection when using features such as Expand Search and Connection to a URL, but you will be prompted for sign-in credentials when you attempt to use it.

- When EKM is configured to use LDAP as the authentication method, and Windows Active Directory as the authentication service, users attempting to sign in to EKM may encounter an error if their password contains the British pound character ( £ ).

## File Transfer Issues

- The following are known limitations for uploading to the repository using the web browser:

  1. Duplicates are not allowed. If you try to add a new file that has the same name as a file already in the staging list, the new file will not be added to the staging list.

  2. The upload process uses a temporary system folder to hold files in the staging area before they are uploaded. If the temporary folder is full or almost full, then the upload may not work as expected. Contact your IT staff to clean up the temporary folder on the EKM server.

     1. If the temporary folder is full when the first file is added, a message "No files have been added" will be displayed. When you click Next, all of the files will be cleared.

     2. If the temporary folder is full sometime after the first file has been added to the staging area, then all files that are accepted before the System temporary folder becomes full will be successfully added to the staging area. The remaining files will not be uploaded and will not be displayed after you click Next.

  3. With some browsers there is a rare possibility that the Add button may be disabled when the Upload wizard first appears. As a workaround, if you click Next, the Add button will become enabled and you can ignore the message No files have been added.

  4. The maximum number of files allowed to be uploaded to the staging area in a single transfer is set to `100`. When the number of files is equal to 100, the Add button will become disabled and nothing else will be uploaded even if you Hide the entire list. In order to upload files again, the current upload will need to finish and you can start the upload process again using the Upload action menu. If the number of files selected exceeds the limit, only the first 100 files will be uploaded to the staging area. The remaining will be ignored without any notice.

- When using the Upload Files/Folders From Server action to upload a Workbench project (.wbpj file) and its corresponding _files folder, extraneous files marked as ‘File Not Found’ are displayed in the Extraction Monitor.

- If you are uploading a Workbench project using the File Transfer Client, and the upload fails for any reason, you cannot retry the upload in the File Transfer Client. You must start a new upload of the project.

- When using a cache server that is version 18.1 or newer, using the Save to Repository action in a pre-18.1 version of Workbench will fail. If you want to continue using the cache server, you can work around this issue by using the File Transfer Client in EKM to upload the project to EKM. After the initial upload to EKM, repository actions such as Open from Repository and Get/Send Changes will function properly via the cache server

## Data Management Issues

- If you are browsing to a repository object that has a name that contains multiple consecutive spaces, you need to manually provide these extra spaces in the text box. This is because HTML trims multiple spaces to a single space, and the name displays with a single space in the tree view.

- Object names cannot contain the following characters:

  `/ : [ ] * \ “ ”| \\ > < ?`

- Property names cannot contain the following characters:

  `/ : [ ] * \ “ ” | \\`

- Only numeric quantities are allowed in chart comparisons while creating a Comparison Report. If two or more reports are compared and any report content contains numbers mixed with units (for example, 415 KB, 123 MB, and so on), then that content cannot be compared using charts because it is treated as “String” type.

- Keyword or full text searches do not work with non-Latin characters (such as Chinese, Japanese, and so on). However, you can search for object names and property values that contain non-Latin characters by using advanced property based search and using `Equal to` or `Matches` criteria instead of `Contains`.

- In a keyword search, the following characters cannot be used as singular input:

  `+ ! ^ ( ) { } - [ ] “ ” ‘ ’`

  Some of the characters listed above are also invalid when they are part of a string. For example, while the strings `“fluent”` and `(fluent)` are valid, the strings `‘fluent’` and `[fluent]` are not. Also, some characters are valid at the beginning of a string, but not at the end of a string. For example, `!fluent` is valid, while `fluent!` is not.

  Non-alphanumeric characters that are part of keyword may be ignored. For example, entering the keyword `#scaling` could return results such as `scaling`, `#scaling`, `scaling#`, `scaling#one`, and so on. Similarly, entering the keyword `scaling#one` could return results such as `scaling`, `one`, `scaling#one`, `scaling:one`, `scaling-one`, and so on.

- During an upload, new files or folder may not be immediately displayed in the current EKM view. Refreshing the browser window will refresh the view.

- On a Linux EKM server that uses PuTTY, EKM may fail to properly extract simulation details and images from ANSYS Mechanical database files. This is due to Mechanical’s incompatibility with PuTTY. To resolve this issue, the EKM administrator should use a VNC session instead of PuTTY to run the EKM server.

- If a PDF or XML document is being displayed in EKM, the action menus get hidden behind the display. A simple workaround is to select a different view (for example, Properties) of the file. When this is done, the action menus are displayed properly.

- Geometry from older SpaceClaim .scdoc files (2011 or earlier) may not be supported, and will not be displayed on the Image tab.

- When viewing a SpaceClaim model, the viewer on the Image tab supports only facets, as well as bodies and parts from the `SpaceClaim/Graphics` section of the .scdoc file.

- On a Linux EKM server, EKM may fail to extract images from ANSYS Mechanical database files (.dsdb,.mechdb) and display them in the simulation details report.

  To work around this issue:

  1. In Workbench, select Tools > Options > Appearance, then enable Beta Options.

  2. Close and restart Workbench.

  3. Select Tools > Options > Mechanical, then enable Pre-load the Mechanical editor (Beta).

- When copying/cutting/pasting objects, if an object with the same name already exists in the target location, it will not be overwritten. Rather, a unique number will be appended to the name of the copied object to differentiate it from the existing object.

- When the name of a property value in an Electronics project contains special characters that are invalid in EKM, such as a forward slash (/), EKM replaces these characters with a space upon upload of the project to ensure successful data extraction. As a consequence, the representation of that property value name in the project's Properties in EKM may be slightly inconsistent with the actual property value name in the source project. For example, if a project uses a material named `XG196/96`, the material's section title in the Properties panel will read Material: XG196 96.

- When an EKM server is running on a RHEL system, data extraction may fail for Workbench project archive (.wbpz) files that contain Mechanical projects.

  To resolve this issue:

  1. In EKM, go to Administration > Servers > Master> EKM Server.

  2. Right-click the workbench.app.xml file and select Edit > External Application.

  3. Add an environment variable named LD_LIBRARY_PATH, and give it a value of `{$AWP_ROOT182}/Framework/bin/Linux64/Mesa`.

  4. Re-extract the .wbpz file.

## Job Management Issues

- When setting up a job, specifying an Input File with spaces in its name may result in an error. Depending on the application being used, enclosing the filename in double quotation marks may prevent this error.

- When a job involves Mechanical APDL (MAPDL) running in server mode, the job Status will update to Solving only for analysis types that iterate — for example, non-linear static and full transient analysis types. For other analysis types, the Status will remain Connecting to MAPDL until the solution is almost finished.

- If you pause or interrupt the solution during a Fluent server-mode job and enter a Fluent command in the command window which requires an argument to be wrapped in quotation marks, the command will be executed, but when you resume the solution, the job may go directly to the Finished stage. To avoid this issue you should re-execute the job instead of resuming the solution. Re-executing the job will resume the solution from the point at which it was paused or interrupted.

- When running an MAPDL server-mode job using an input file that contains errors, the job remains stuck in the following state: “Failed to connect to MAPDL. MAPDL job may have ended.”

- MAPDL server-mode jobs that use .dat files with a short duration may fail to execute.

- When running a Fluent batch job, attempting to select files after selecting a directory on the server as the Working Directory may result in an error.

- After using the Command Window to change a case file during a Fluent server-mode job, the updated details are not displayed in the job view unless the view is refreshed.

- When using the built-in MAPDL job template to run a job using a release 16 solver, monitors are not being shown when the job is paused or interrupted.

- When an admin user is viewing another user’s Electronics job, monitors are not being displayed in the job view.

- Performing a browser refresh of the Jobs section when any server-mode job is executing may result in an exception.

- When using the MAPDL job template, the job will not run in server mode if the solution is running in a pre-16.1 version of MAPDL on Linux, and Distributed Computing is being used. Live monitoring will not be available, and you will not be able to steer the solution from the Job Monitor.

- Attempting to interrupt a distributed MAPDL job that was started using the MAPDL Batch template does not work. The job keeps running, and the journaling status “Reading Input File” is displayed in the job view in EKM.

- When submitting a CFX job, live job monitors and controls are not available if the solver version is older than 17.1.

- Jobs submitted using built-in Fluent template will not exit if Fluent calculations diverge. You will need to exit manually using the Complete action on the Fluent actions toolbar.

- Jobs submitted using the built-in Fluent template will not exit if Fluent calculations diverge. You will need to exit manually using the Complete action on the Fluent actions toolbar.

- In EKM on Linux, attempting to edit a text file in a job’s working directory results in an error.

- When a CFX as-a-server job is running, live monitors may disappear if you refresh the view.

- Jobs submitted to Electronics Desktop v17.1 may not execute correctly if the OS of the execution node is SUSE Linux 12.0 or 12.1.

- The Workbench Batch template does not support job submission to versions of Workbench older than version 17.0.

- If you submit a project update to an EKM Portal from Workbench, and the job can run directly from the folder in which the Workbench project was opened (in other words, files do not need to be uploaded to the EKM job data directory), the transcript and convergence monitor views will not be available after the job has finished.

- If you get an error message in Step 3/3: Specify Execution Settings of the batch job wizard, then correct the error (for example, by selecting another queue) and click Finish, the job will begin to run, but the job status will be incorrectly reported as 'Failed'. To avoid this issue, close the wizard and start over when you see an error message.

- If you copy and paste the URL of a running job into a new browser tab or window, the EKM server may crash. To open a new window from EKM, you should use the More > Open in new window action in the Data section. Otherwise, if you open a new tab using the browser, you should enter the URL of the EKM server on that tab instead of pasting in the URL of a running job.

- When a job is submitted to an EKM portal from Workbench, and the job name contains characters that are valid in RSM but not in EKM (such as '%' and '+'), the job may fail.

- When running jobs from EKM, running a Workbench job for a Mechanical project may fail on RHEL systems. You may see an error similar to the following:

      A fatal error has occurred within ANSYSWBU.exe and it must be closed

  To resolve this issue:

  1. In rsm_env_profile, set the LD_LIBRARY_PATH environment variable value to `$AWP_ROOT182/Framework/bin/Linux64/Mesa`.

  2. Restart RSM services.

  3. In EKM, go to Administration > Servers > Master, then select the queue that contains the Workbench application (workbenchExecutionController.app.xml).

  4. Use the Edit External Application action to remove the LD_LIBRARY_PATH environment variable from the workbenchExecutionController.app.xml application:

## Process Management Issues

- When a process template has another process template nested inside of it, output files generated from batch nodes in the nested process template are not accessible.

- An error may occur when a non-admin user attempts to save changes to a process template that has been shared by another user.

- EKM is not detecting when a process template contains a batch node with an invalid path, and is permitting the process template to be saved and used for starting a process.

## Customization and Scripting Issues

- In custom dialog boxes that involve job execution, only batch jobs are supported. Interactive jobs are not supported.

- The "move" method in the scripting interface must be called outside a transaction rather than inside. Otherwise, the script execution will fail.

- On an EKM server running on Linux, a user may observe a failure when executing a python script that uses the python "datetime" module.

  For example, a python script on EKM contains this line:

      import datetime

  When the script is executed, an error like the following results:

      com.ansys.ingress.commons.IngressRuntimeException: java.security.AccessControlException:
      java.security.AccessControlException: WFSM000001: Permission check failed
      (permission "("java.lang.RuntimePermission" "accessClassInPackage.sun.util.calendar")" in code source
      "(null <no signer certificates>)" of "null") in <script> at line number 1
       at com.ansys.ingress.commons.IngressRuntimeException.create(Unknown Source)
       at com.ansys.ingress.core.custom.Interpreter.evaluateExpression(Unknown Source)
       at com.ansys.ingress.core.custom.Interpreter.evaluateMacro(Unknown Source)
      ...

  To work around this error, modify the file: EKM_HOME/conf/script.policy to grant a Java Security Manager permission that will allow the python "datetime" module to function correctly. To do this, modify script.policy as follows:

      grant {
          permission java.lang.RuntimePermission "accessClassInPackage.sun.*";
      };

## Browser-Related Issues

- If you have different workspaces open on different browser tabs, one of the tabs may display a blank page or error after a period of switching back and forth between workspaces. This indicates that the browser’s cookie size limit has been exceeded. You can resolve this by clearing the cookies of the EKM server domain. Consult your browser’s documentation for more information.

- If your browser’s font size is too large, tabs in the EKM web interface may display incorrectly.

- Selecting an EKM object from the Chrome browser’s History list may display an earlier object from the History list rather than the selected object.

- If using Internet Explorer, EKM will not display or behave properly if the EKM URL has been added to Compatibility View, or if the Display intranet sites in Compatibility View option is enabled. To edit these settings, select Tools > Compatibility View settings in Internet Explorer.

- When using EKM in a Chrome browser, attempting to fast-forward an .mp4 video (by sliding the playhead) does not work. When using EKM in a Firefox browser, the video progress bar does not display a playhead, or show the video's progress.

- When running EKM on Firefox 49.0.2 or later, attempting to upload files to EKM using the browser may cause the Firefox tab to crash.

  This occurs when the Multiprocess Windows feature is enabled in Firefox.

  To check to see whether or not this feature is enabled on your system, type `about:support` in the Firefox address bar, and press Enter. Look at the Multiprocess Windows setting in the Applications Basics list:

  If it is enabled, you will likely experience a crash when uploading files in EKM.

  To disable the Multiprocess Windows setting and prevent crashes:

  1. In the Firefox address bar, type `about:config` and press Enter.

  2. In the Search field that appears below the address bar, type `browser.tabs.remote.auto` and press Enter.

  3. Make sure that all of the displayed preferences are set to false. To toggle a value, double-click it.

  4. Restart the browser.

  5. Enter `about:support` in the address bar and verify that Multiprocess Windows is now disabled.

  Note: Updates to Firefox or changes to preferences may re-enable the Multiprocess Windows feature. In this case you will need to perform these steps again.

## Usability/Interface Issues

- Double-clicking on tree nodes or some action menus may result in an unhandled exception. This error has no adverse impact on the system and you can click Continue in the error page to continue your work.

- If a text box with a Browse button is pre-populated with a default path that is invalid, clicking the Browse button and selecting a new path will display an error message, and will not replace the invalid path. To resolve this issue you must click Browse a second time and re-select the new path.

- In the File Transfer Client, tooltips do not work initially in the Actions column due to a limitation of the Java GUI. To activate tooltips, simply click on any disabled button in the Actions column.

- In localized versions of EKM, the Usage Statistics report is not translated.

  In EKM Studio:

  - The Scripting Language label in the Edit Script dialog box is not translated.

  - The Language and ID labels and some field values are not translated in some dialogs.

  - In the Variable dialog, the unit system shown for specifying double/long values (for example, "[in SI units]") is not translated.

- Sometimes the Message dialog box (which shows the number of items processed, warnings, and errors) displays the number of items processed incorrectly for recursive operations (such as check-in, checkout, permission change, and so on).

- Selecting Go one level up after an exception may not display the correct section in some cases.

- Some functions are not available on a tablet. For a complete list see Tablet use: Unavailable actions.

- Some EKM functions do not work properly on a tablet. See Tablet use: Issues and Limitations.

- An exception may be shown if a user’s session has timed out due to inactivity.

- In a non-English locale, some error messages may not be translated when using the EKM Server Diagnostics utility.

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Prev | Up / Contents |

Release 18.2 - © ANSYS, Inc. All rights reserved.