Known Issues and Limitations
The following issues have been identified in CIMPLICITY v2024:
| Description | Tracking ID |
|---|---|
| Screen in CimEdit from the CIMPLICITY Workbench will not open if the project is placed in a directory with special names. For example, C:\MyProject_Automation\CIM_Ver2\. | SF-01120187 |
| Unable to form logical links between primary and secondary servers in a redundant setup. | SF-01123046 |
| String indexer for the CimClassList object does not work as expected. Working alternative is not documented well. | SF-00984050 |
| Class dialogs have inconsistent Pre/Post Script selection behavior (Typed/Browsed). | SF-01077222 |
| When only Proficy Authentication is enabled on the CIMPLICITY node, the login dialog appears and then disappears on a Webspace session, preventing login to the session. If mixed mode is enabled, the login dialog on the client appears correctly. | NA |
IGS Server Does Not Start Due to Port Conflicts Another application such as Proficy Licensing may dynamically request to use a port number that is also one of the several port numbers configured for use by the IGS Server. A conflict occurs when the IGS Server then tries to start. To resolve this issue, you can use the netsh command from a Command Prompt in Windows to instruct Windows to exclude a specific port number, or port number range, from the list of available ports in the Dynamic range (ports 49152 to 65535) for Windows. For more details on this command and what default ports are used by the IGS, see the Resolving Port Conflicts section of the Port Assignments topic in the IGS help. |
NA |
The following limitation has been identified in CIMPLICITY 2024:
| Description | Tracking ID |
|---|---|
| The Redundant Configuration Update feature is not supported when opening a remote project over a UNC path. | NA |