You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/power-platform/power-automate/desktop-flows/ui-automation/cannot-access-java-application-elements.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.custom: sap:Desktop flows\UI or browser automation
7
7
---
8
8
# Can't access the elements of a Java application
9
9
10
-
When [automating Java applications](/power-automate/desktop-flows/how-to/java)with Power Automate for desktop, you might experience an issue where Power Automate can't access the UI elements of the Java application. Follow the steps in this article to troubleshoot this issue.
10
+
When [automating Java applications](/power-automate/desktop-flows/how-to/java)by using Power Automate for desktop, you might experience an issue where Power Automate can't access the UI elements of the Java application. Follow the steps in this article to troubleshoot this issue.
11
11
12
12
_Applies to:_ Power Automate
13
13
_Original KB number:_ 5014922
@@ -18,30 +18,30 @@ Power Automate for desktop can't access the UI elements of a Java desktop applic
18
18
19
19
## Diagnose using the troubleshooter
20
20
21
-
To solve this issue, first try the [troubleshooter](/power-automate/desktop-flows/troubleshooter):
21
+
To solve this problem, first try the [troubleshooter](/power-automate/desktop-flows/troubleshooter):
22
22
23
-
1. In Power Automate for desktop, navigate to **Help** > **Troubleshooter**, and then run the [troubleshooter](/power-automate/desktop-flows/troubleshooter).
23
+
1. In Power Automate for desktop, go to **Help** > **Troubleshooter**, and then run the [troubleshooter](/power-automate/desktop-flows/troubleshooter).
24
24
25
-
2. In the **Troubleshooter** window, select **Run** on the **Troubleshot UI/Web automation issues** panel.
25
+
1. In the **Troubleshooter** window, select **Run** on the **Troubleshot UI/Web automation issues** panel.
26
26
27
-
3. If an issue is found for **Java Automation**, expand the panel to see the details.
27
+
1. If the troubleshooter finds an issue for **Java Automation**, expand the panel to see the details.
28
28
29
-
4. If a **Fix** button is available, select it to apply the fix. Ensure all running **Java** applications are closed before applying the fix.
29
+
1. If a **Fix** button is available, select it to apply the fix. Make sure you close all running **Java** applications before applying the fix.
30
30
31
-
If the issue persists after using the troubleshooter, follow the steps in [Manual troubleshooting](#manual-troubleshooting) to further troubleshoot the issue.
31
+
If the problem persists after using the troubleshooter, follow the steps in [Manual troubleshooting](#manual-troubleshooting) to further troubleshoot the problem.
32
32
33
33
## Manual troubleshooting
34
34
35
-
Use these steps only if the troubleshooter finds no Java installations or cannot configure the environment.
35
+
Use these steps only if the troubleshooter finds no Java installations or can't configure the environment.
36
36
37
37
### Configure Java (for Java 7 and 8)
38
38
39
-
Use these steps to troubleshoot Java 7 and 8. If you are using Java 9 or later, see [Configure Java (for Java 9 and later)](#configure-java-for-java-9-and-later).
39
+
Use these steps to troubleshoot Java 7 and 8. If you're using Java 9 or later, see [Configure Java (for Java 9 and later)](#configure-java-for-java-9-and-later).
40
40
41
41
#### Locate the Java installation folder
42
42
43
43
1. Check common paths such as `C:\Program Files\Java\jre7` or `C:\Program Files\Java\jre8`.
44
-
1. Some apps use an embedded Java runtime that is not registered system-wide. To identify the location of an embedded Java runtime:
44
+
1. Some apps use an embedded Java runtime that isn't registered system-wide. To identify the location of an embedded Java runtime:
45
45
46
46
1. Start the Java application.
47
47
@@ -51,7 +51,7 @@ Use these steps to troubleshoot Java 7 and 8. If you are using Java 9 or later,
51
51
52
52
1. Use that folder as `<JRE_HOME>\bin`.
53
53
54
-
To avoid this issue in future, install Java under `Program Files` or enable the option to register Java in the system registry during installation.
54
+
To avoid this issue in the future, install Java under `Program Files` or enable the option to register Java in the system registry during installation.
55
55
56
56
#### Copy required files (administrator rights required)
57
57
@@ -70,11 +70,11 @@ Copy these files from the Power Automate for desktop installation folder (`C:\Pr
70
70
If the line starts with `#`, remove the `#` to uncomment it. If other assistive technologies are listed, append the Microsoft value at the end, separated by a comma.
71
71
72
72
> [!NOTE]
73
-
> Manual file placement works only for Java 7 and 8. Java 9 and later do not support loading assistive technologies by this method.
73
+
> Manual file placement works only for Java 7 and 8. Java 9 and later don't support loading assistive technologies by this method.
74
74
75
75
### Configure Java (for Java 9 and later)
76
76
77
-
For Java 9 and later versions, you cannot modify the Java installation in the same way. Use one of the following methods instead.
77
+
For Java 9 and later versions, you can't modify the Java installation in the same way. Use one of the following methods instead.
78
78
79
79
#### Set environment variable (recommended)
80
80
@@ -95,11 +95,11 @@ Append these arguments to the app's Java startup command:
95
95
96
96
- Always try the Power Automate for desktop Troubleshooter first. It's the safest and fastest method to configure Java automation.
97
97
- Manual file placement applies only to Java 7 and 8. Use the environment-variable or JVM-argument method for Java 9 and later.
98
-
- Java versions earlier than 7 are not supported.
99
-
- The attach mechanism may not work reliably with Java 9 or Java 10.
98
+
- Java versions earlier than 7 aren't supported.
99
+
- The attach mechanism might not work reliably with Java 9 or Java 10.
100
100
- Use Task Manager to find the Java executable path when an application uses an embedded runtime.
101
-
-Administrator rights are required to place files in Java installation folders.
102
-
- If you placed the files manually, they are not updated automatically when Power Automate for desktop is updated. Repeat the manual file placement after each Power Automate for desktop update to use the latest Java automation files.
101
+
-You need administrator rights to place files in Java installation folders.
102
+
- If you placed the files manually, they aren't updated automatically when Power Automate for desktop is updated. Repeat the manual file placement after each Power Automate for desktop update to use the latest Java automation files.
103
103
- After making changes, close all running Java applications. Restarting the PC is recommended.
0 commit comments