Skip to content

Commit 169fcca

Browse files
authored
Update scanning-shir-troubleshooting.md
1 parent a2b9290 commit 169fcca

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

articles/purview/scanning-shir-troubleshooting.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -29,31 +29,29 @@ To get support and troubleshooting guidance for SHIR issues, you may need to gen
2929
- Once the scan shows status "Failed", navigate back to the SHIR VM, or machine and refresh the event viewer in the "Integration Runtime" section.
3030
- The activity logs are displayed for the failed scan run.
3131

32-
:::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.":::
32+
:::image type="content" source="media/scanning-shir-troubleshooting/shir-event-viewer-logs-ir.png" lightbox="media/scanning-shir-troubleshooting/shir-event-viewer-logs-ir.png" alt-text="Screenshot of the logs for the failed scan SHIR activity.":::
3333

3434
1. For further assistance from Microsoft, select **Send Logs**.
3535

3636
The **Share the self-hosted integration runtime (SHIR) logs with Microsoft** window opens.
3737

38-
:::image type="content" source="media/scanning-shir-troubleshooting/shir-send-logs-ir.png" alt-text="Screenshot of the send logs button on the self-hosted integration runtime (SHIR) to upload logs to Microsoft.":::
38+
:::image type="content" source="media/scanning-shir-troubleshooting/shir-send-logs-ir.png" lightbox="media/scanning-shir-troubleshooting/shir-send-logs-ir.png" alt-text="Screenshot of the send logs button on the self-hosted integration runtime (SHIR) to upload logs to Microsoft.":::
3939

4040
1. Select which logs you want to send.
4141
* For a *self-hosted IR*, you can upload logs that are related to the failed activity or all logs on the self-hosted IR node.
4242
* For a *shared IR*, you can upload only logs that are related to the failed activity.
4343

4444
1. When the logs are uploaded, keep a record of the Report ID for later use if you need further assistance to solve the issue.
4545

46-
:::image type="content" source="media/scanning-shir-troubleshooting/shir-send-logs-complete.png" alt-text="Screenshot of the displayed report ID in the upload progress window for the Purview SHIR logs.":::
46+
:::image type="content" source="media/scanning-shir-troubleshooting/shir-send-logs-complete.png" lightbox="media/scanning-shir-troubleshooting/shir-send-logs-complete.png" alt-text="Screenshot of the displayed report ID in the upload progress window for the Purview SHIR logs.":::
4747

4848
> [!NOTE]
4949
> Log viewing and uploading requests are executed on all online self-hosted IR instances. If any logs are missing, make sure that all the self-hosted IR instances are online.
5050
5151

5252
## Self-hosted integration runtime SHIR general failure or error
5353

54-
There are lots of common errors, warnings, issues between Purview SHIR and Azure Data Factory or Azure Synapse SHIR.
55-
56-
If your SHIR issues aren't resolved, refer to the [Azure Data Factory ADF or Azure Synapse SHIR troubleshooting guide](../data-factory/self-hosted-integration-runtime-troubleshoot-guide.md)
54+
There are lots of common errors, warnings, issues between Purview SHIR and Azure Data Factory or Azure Synapse SHIR. If your SHIR issues aren't resolved at this stage, refer to the [Azure Data Factory ADF or Azure Synapse SHIR troubleshooting guide](../data-factory/self-hosted-integration-runtime-troubleshoot-guide.md)
5755

5856
[!INCLUDE[SHIR](../data-factory/includes/troubleshoot-shir-include.md)]
5957

0 commit comments

Comments
 (0)