SAP Logn issue with <sap id='sbar' />

[Radek_Aa]

Hello,

I’m facing the issue with SAP Login Activity
App is opening and performing login well, but i think it don’t detect the login status after on .
See the error message below:
SAP Login: Could not find the user-interface (UI) element for this action.

Possible solutions:
• Ensure application is opened and the UI element is visible on the screen at execution time
• Edit the Target of the UI activity and use Validation to debug the issue.
• If needed, re-indicate the element as its properties might have changed
• Use “Check state” activity to check the application state before executing the action
• Increase the “Delay before” value to allow time to the application to render entirely and become responsive: “”

Version of studio: 2025.0.176 STS
UiPath.UIAutomation.Activities: 25.10.19
Sap Logon Version:
SAP GUI for Windows
800 Final Release - 64bit
8000.1.3.3397
2209061
I also tried to reinstall studio, sap logon and try to use older versions of UiPath ui automation activities but without effect.

Regards,

[swapnil.naik]

1. Verify SAP Scripting Configuration

Make sure SAP GUI scripting is enabled both client and server-side.

On SAP GUI (Client)

1. Open SAP Logon
2. Click top menu → Options
3. Go to:
   Accessibility & Scripting > Scripting
4. Ensure:

• “Enable scripting” is checked
• “Notify when a script attaches to a running GUI” unchecked (optional)

5. Restart SAP Logon

On SAP Server (Basis/IT admin)

Transaction: RZ11

• Parameter name: sapgui/user_scripting
• Should be set to TRUE

---

2. Enable 32-bit Compatibility Mode (Important for UiPath)

Even though your SAP GUI is 64-bit, UiPath automation hooks still rely on 32-bit COM scripting bridge.

Try this:

• Open UiPath Assistant → Settings > SAP Settings
• Ensure “Enable SAP scripting” is ON
• Restart UiPath Studio

If still not working:

• Uninstall the 64-bit SAP GUI
• Install 32-bit version of SAP GUI 800 (many UiPath versions detect UI better there)

---

3. Re-indicate the SAP window target (selector update)

The window selector can change post-login (e.g., different window class name or session ID).

Fix:

• After successful login (manually), open SAP main screen
• Use Indicate Element again in UiPath to re-capture the window
• Then open the selector editor → verify if the "wnd[0]" and "session.findById" look correct
  Example of valid selector:

<wnd app='saplogon.exe' cls='SAP_FRONTEND_SESSION' title='SAP Easy Access*'/>

---

4. Add a “Check App State” or “Element Exists” delay

SAP may take 3–10 seconds to load after login.

Add before the next action:

• Activity: Check App State
  • Target: SAP main window (Easy Access)
  • Timeout: 10000 ms (10 sec)
  • Inside “Target Appears” → next actions (menu click, etc.)

Or simply:

Delay 00:00:05

---

5. Test with Older UIAutomation Activity Version

UiPath.UIAutomation.Activities 25.10.x has breaking changes with SAP GUI 800.

Try downgrading to:

UiPath.UIAutomation.Activities v23.10.8

and retest.

This version is confirmed stable with SAP GUI 800 in most enterprise setups (as of early 2025).

---

6. Run Studio as Administrator

Sometimes UiPath cannot attach to a high-integrity process like SAP unless both are same privilege level.

Right-click UiPath Studio → Run as Administrator.

Also check that SAP Logon isn’t running as admin if Studio isn’t (they must match).

Recommended Stable Setup (2025)

Component	Recommended
UiPath Studio	2025.0.176 STS
UiPath.UIAutomation.Activities	v23.10.8
SAP GUI	800 Final Release (32-bit)
Scripting	Enabled on both client & server
Run Mode	Both Studio & SAP as same privilege

[Radek_Aa]

Issue resolved - didn’t notice fact that sap gui scripting was disabled on server side.

[swapnil.naik]

I hope you find my solution helpful.