Skip to content

Commit 950418c

Browse files
authored
Update scanning-shir-troubleshooting.md
1 parent 8b10671 commit 950418c

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

articles/purview/scanning-shir-troubleshooting.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,10 +22,11 @@ This article explores common troubleshooting methods for self-hosted integration
2222
For failed activities that are running on a self-hosted IR or a shared IR, the service supports viewing and uploading error logs from the [Windows Event Viewer](https://learn.microsoft.com/shows/inside/event-viewer).
2323
To get support and troubleshooting guidance for SHIR issues, you may need to generate an error report and send it across to Microsoft. To generate the error report ID, follow the instructions here, and then enter the report ID to search for related known issues.
2424

25-
1. Before starting the scan on the Purview portal:
25+
1. Before starting the scan on the Microsoft Purview governance portal:
26+
- Navigate to the SHIR VM, or machine and open the Windows Event Viewer.
2627
- Clear the windows event viewer logs in the "Integration Runtime" section. Right-click on the logs and select clear logs option.
27-
- Then, start the scan on Purview portal.
28-
- Once the scan shows status "Failed" on Purview portal, navigate back to the SHIR VM, or machine and refresh the event viewer in the "Integration Runtime" section.
28+
- Naviigate back to the Microsoft Purview governance portal and start the scan.
29+
- Once the scan shows status "Failed", navigate back to the SHIR VM, or machine and refresh the event viewer in the "Integration Runtime" section.
2930
- The activity logs are displayed for the failed scan run.
3031

3132
:::image type="content" source="media/scanning-shir-troubleshooting/shir-event-viewer-logs-ir.png" alt-text="Screenshot of the logs for the failed scan SHIR activity.":::

0 commit comments

Comments
 (0)