This article addresses technology limitation warnings and object recognition issues specific to Chromium Embedded Framework (CEF) and SAP applications.
Chromium Embedded Framework (CEF)
If Ranorex Studio cannot identify elements within a CEF application, it is usually due to a conflict with the remote debugging port.
Another application is using the debugging port
Ranorex is not able to identify UI elements in your AUT if a different application (like Chrome DevTools) blocks the remote debugging port.
- Solution: Close all applications that might be connected to the AUT at the remote debugging port you specified. While Ranorex attempts to close these automatically, some tools require a manual shutdown.
- Alternative: Change the remote debugging port number for your AUT to avoid the conflict.
Remote debugging is unavailable
The UI elements of a CEF application are not exposed if the debugging port is disabled or misconfigured.
- Solution: Verify that you have activated the remote debugging port correctly (for example, in your source code) and that no other applications are using it.
- Port Reset: If you changed the port number, try resetting it to the default value (8081).
SAP
SAP automation requires specific network and privilege settings to function correctly.
Insufficient privileges
If Ranorex cannot interact with the SAP GUI, it is often due to a mismatch in security levels.
- Solution: Restart all Ranorex tools and the SAP AUT with identical privileges, preferably as an administrator.
Element identification issues
Network settings can impact how Ranorex discovers objects in the SAP GUI.
- Solution: Make sure your environment is configured with High Speed Connection (LAN), as Low Speed Connection (Reduced Network Traffic) can impact the functionality of the SAP GUI when using Windows.