|
1 | 1 | --- |
2 | 2 | title: Power Automate for desktop logs |
3 | | -description: Introduces the locations that contain Power Automate for desktop installation logs. |
4 | | -ms.reviewer: quseleba, guco |
5 | | -ms.date: 09/13/2024 |
| 3 | +description: Introduces the locations that contain Power Automate for desktop logs. |
| 4 | +ms.reviewer: quseleba, guco, madiazor, johndund |
| 5 | +ms.date: 01/20/2025 |
6 | 6 | ms.custom: sap:Desktop flows\Working with Power Automate for desktop |
7 | 7 | --- |
8 | 8 | # Power Automate for desktop logs |
9 | 9 |
|
10 | | -During the course of troubleshooting a problem with Power Automate for desktop, you may need to gather logs on the machine for customer support to analyze. These can be for a failed installation, a problem running your desktop flows, or a problem using Power Automate or the machine runtime application. |
| 10 | +When troubleshooting issues with Power Automate for desktop, you might need to collect logs for customer support to analyze. These logs can be for a failed installation, problems running desktop flows, or issues with Power Automate or the machine runtime application. |
11 | 11 |
|
12 | 12 | _Applies to:_ Power Automate |
13 | 13 | _Original KB number:_ 4555577 |
14 | 14 |
|
15 | 15 | ## Installer logs |
16 | 16 |
|
17 | | -The easiest way to get installer logs is to export them using the link provided at the end of a failed installation. When your installation fails and displays "There's a problem installing," click the "installation log files" link located under the **Troubleshooting tips** section. |
| 17 | +The easiest way to get installer logs is to export them using the link provided at the end of a failed installation. When your installation fails and displays "There's a problem installing," select the **installation log files** link located under the **Troubleshooting tips** section. |
18 | 18 |
|
19 | 19 | :::image type="content" source="media/how-to-get-power-automate-desktop-installer-logs/installation-log-files.png" alt-text="Screenshot of the page that contains the installation log files link that you can use to export the installer logs."::: |
20 | 20 |
|
21 | | -If you need to get the installer files manually, they can be found in the _%temp%_ folder of the user who performed the installation. You can find them by typing _%temp%_ in the address bar of File Explorer. The files of interest are: |
| 21 | +If you need to get the installer files manually, they can be found in the _%temp%_ folder of the user who performed the installation. You can find them by typing _%temp%_ in the address bar of File Explorer to locate the following files: |
22 | 22 |
|
23 | 23 | - _Power Automate for desktop\_*.log_ |
24 | 24 | - _Power Automate for desktop\_\*\_\*\_MicrosoftFlowRPA.log_ |
25 | 25 |
|
26 | | -The _Power Automate for desktop\_*.log_ file contains the general reason why the installation failed. The _Power Automate for desktop\_\*\_\*\_MicrosoftFlowRPA.log_ file has more detailed information. |
| 26 | +The _Power Automate for desktop\_*.log_ file contains the general reason for the installation failure. The _Power Automate for desktop\_\*\_\*\_MicrosoftFlowRPA.log_ file provides more detailed information. |
27 | 27 |
|
28 | 28 | :::image type="content" source="media/how-to-get-power-automate-desktop-installer-logs/power-automate-installer-logs.png" alt-text="Screenshot of the Power automate for desktop installer logs."::: |
29 | 29 |
|
30 | 30 | ## On-premises product logs |
31 | 31 |
|
32 | | -For issues with using Power Automate to create your flows, the Runtime Application to register or configure your machine, or during cloud runtime, you may need to gather on-premises logs. |
| 32 | +For issues with using Power Automate to create flows, the [Power Automate machine runtime application](/power-automate/desktop-flows/manage-machines#register-a-new-machine) to register or configure your machine, or during cloud runtime, you might need to collect on-premises logs. |
33 | 33 |
|
34 | | -The easiest way to do this is to use the Power Automate machine runtime application. If you have the application installed, you can [use it to export logs automatically](https://learn.microsoft.com/en-us/power-automate/desktop-flows/troubleshoot#collect-machine-logs). |
35 | | - |
36 | | -If you need to gather on-premises logs manually, they can be found can be found in _%programdata%\Microsoft\Power Automate\Logs_. |
| 34 | +The easiest way to do this is by using the Power Automate machine-runtime application. If you have the application installed, you can [use it to export logs automatically](/power-automate/desktop-flows/troubleshoot#collect-machine-logs). |
| 35 | + |
| 36 | +If you need to collect on-premises logs manually, they can be found in the _%programdata%\Microsoft\Power Automate\Logs_. |
37 | 37 |
|
38 | 38 | > [!NOTE] |
39 | 39 | > You need administrator privileges to read or copy these files to another folder. After copying them to a different folder, non-administrator users can open them. |
40 | 40 |
|
41 | 41 | ## Event Viewer logs |
42 | 42 |
|
43 | | -Event viewer application logs are helpful when an application crashes or a Windows service fails to start. |
| 43 | +Event Viewer application logs are helpful when an application crashes or a Windows service fails to start. |
44 | 44 |
|
45 | 45 | Follow these steps to view and save the logs: |
46 | 46 |
|
47 | 47 | 1. Open the Windows Event Viewer. |
48 | 48 | 2. Go to **Windows Logs** > **Application**, look for an error with the source corresponding to the application that experienced the problem. |
49 | | -3. If needed, use the **Filter Current Log** menu to filter by **Event level** or **Logged** time (such as the last hour). |
| 49 | +3. Use the **Filter Current Log** menu to filter by **Event level** or **Logged** time (such as the last hour) if needed. |
50 | 50 | 4. To save the filtered log file, select **Save Filtered Log File As** and save it as an event file. |
51 | 51 |
|
52 | 52 | :::image type="content" source="media/how-to-get-power-automate-desktop-installer-logs/power-automate-event-viewer-logs.png" alt-text="Screenshot of an example error logged in the Event Viewer."::: |
0 commit comments