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: Microsoft365/purview/ediscovery/resolve-ediscovery-issues.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ When you view the search result statistics in the *Export Summary \<timestamp\>.
46
46
47
47
An estimate of the search results is just that: It's an estimate and not an actual count of items that meet the search query criteria. For more information about why estimated and downloaded search results can differ, see [Differences between estimated and actual eDiscovery search results](/microsoft-365/compliance/ediscovery-differences-between-estimated-and-actual-search-results).
48
48
49
-
[Back to top](#resolve-search-errors-in-ediscovery-standard)
49
+
[Back to top](#resolve-search-errors-in-ediscovery)
50
50
51
51
## Search error: "Location is ambiguous"
52
52
@@ -58,7 +58,7 @@ When you run an [eDiscovery search](/microsoft-365/compliance/ediscovery-search-
58
58
59
59
### Cause
60
60
61
-
The locations specified in the error message are invalid. The mailbox identifier for each invalid location is used by duplicate or conflicting objects in Exchange Online Protection (EOP).
61
+
The locations that are specified in the error message are invalid. The mailbox identifier for each invalid location is used by duplicate or conflicting objects in Exchange Online Protection (EOP).
62
62
63
63
### Resolution
64
64
@@ -74,7 +74,7 @@ For each invalid location, follow these steps:
74
74
75
75
3. Remove the duplicate or conflicting object.
76
76
77
-
[Back to top](#resolve-search-errors-in-ediscovery-standard)
77
+
[Back to top](#resolve-search-errors-in-ediscovery)
78
78
79
79
## Search error: "Recipient not found"
80
80
@@ -100,7 +100,7 @@ The system can't find one of the [recipients](/powershell/module/exchange/new-ma
100
100
101
101
4. After you verify that the recipient is synced in EOP, retry your search.
102
102
103
-
[Back to top](#resolve-search-errors-in-ediscovery-standard)
103
+
[Back to top](#resolve-search-errors-in-ediscovery)
104
104
105
105
## Search error: CS007
106
106
@@ -134,7 +134,7 @@ Your [eDiscovery search](/microsoft-365/compliance/ediscovery-search-for-content
134
134
135
135
Retry your search. If your search still fails, split your search into smaller searches. For example, use date ranges or limit the number of search locations to return smaller result sets.
136
136
137
-
[Back to top](#resolve-search-errors-in-ediscovery-standard)
137
+
[Back to top](#resolve-search-errors-in-ediscovery)
138
138
139
139
## Search or export error: "Maximum number of jobs for your organization are currently running"
140
140
@@ -187,7 +187,7 @@ To resolve the error, use the following procedure:
187
187
188
188
2. Retry your search or export operation.
189
189
190
-
[Back to top](#resolve-search-errors-in-ediscovery-standard)
190
+
[Back to top](#resolve-search-errors-in-ediscovery)
191
191
192
192
## Export error: "Item has been moved or deleted" or "Unable to retrieve item due to timeout"
193
193
@@ -207,7 +207,7 @@ These "FailedToExportItem" error messages indicate that the system didn't export
207
207
208
208
Wait for the system to retrieve and export the original mailbox items that are associated with the temporary backups.
209
209
210
-
[Back to top](#resolve-search-errors-in-ediscovery-standard)
210
+
[Back to top](#resolve-search-errors-in-ediscovery)
211
211
212
212
## Export error: "File wasn't exported because it doesn't exist" or "File not found"
213
213
@@ -227,7 +227,7 @@ You might see this error message if the eDiscovery search includes Microsoft Sha
227
227
228
228
To resolve the issue, reindex the SharePoint Online or OneDrive for Business location by using one of the procedures that are provided in [Manually request crawling and reindexing of a site, a library or a list](/sharepoint/crawl-site-content). If you want the search results to include the renamed or moved files, rerun the eDiscovery search.
229
229
230
-
[Back to top](#resolve-search-errors-in-ediscovery-standard)
230
+
[Back to top](#resolve-search-errors-in-ediscovery)
231
231
232
232
## Export download issue: eDiscovery export doesn't download any files
233
233
@@ -247,7 +247,7 @@ The issue can occur for any of the following reasons:
247
247
248
248
If you're experiencing issues that affect the download, see [Best practices for downloading export packages](/purview/edisc-search-export).
249
249
250
-
[Back to top](#resolve-search-errors-in-ediscovery-standard)
250
+
[Back to top](#resolve-search-errors-in-ediscovery)
251
251
252
252
## Export download error: "Search result was not downloaded as it is a folder"
253
253
@@ -265,4 +265,4 @@ You might see this error message if your search includes Microsoft SharePoint On
265
265
266
266
No resolution is required. You can safely ignore the error message.
267
267
268
-
[Back to top](#resolve-search-errors-in-ediscovery-standard)
268
+
[Back to top](#resolve-search-errors-in-ediscovery)
Copy file name to clipboardExpand all lines: support/power-platform/power-automate/desktop-flows/office-automation/excel/troubleshoot-excel-errors.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,15 @@
1
1
---
2
-
title: Errors when running desktop flows including Excel actions
2
+
title: Errors when running desktop flows that include Excel actions
3
3
description: Provides mitigation steps for errors generated by Excel actions in desktop flows.
4
4
ms.author: iomavrid
5
5
author: yiannismavridis
6
-
ms.date: 07/21/2025
6
+
ms.reviewer: amitrou, nimoutzo
7
+
ms.date: 07/22/2025
7
8
ms.custom: sap:Desktop flows\Office automation
8
9
---
9
-
# Errors when running desktop flows, including Excel actions
10
+
# Errors when running desktop flows that include Excel actions
10
11
11
-
This article provides mitigation steps for errors generated by [Excel actions](/power-automate/desktop-flows/actions-reference/excel) in desktop flows. Most errors occur in the context of multiple Excel actions, and there's no strict mapping between them.
12
+
This article outlines steps to mitigate errors that might occur when using [Excel actions](/power-automate/desktop-flows/actions-reference/excel) in Power Automate desktop flows. Some of these errors might occur when you try to open a blank or existing Excel file using the **Launch Excel** action. Most errors occur in the context of multiple Excel actions, and there's no one-to-one mapping between specific errors and actions.
title: Collect Data to Analyze and Troubleshoot Active Directory Scenarios
3
+
description: Helps gather information about your issue by using the TroubleShootingScript (TSS) toolset and learn what data to collect based on Active Directory scenarios.
# Collect data to analyze and troubleshoot Active Directory scenarios
12
+
13
+
This article helps you gather information about your issue by using the TroubleShootingScript (TSS) toolset before contacting Microsoft support.
14
+
15
+
## Prerequisites
16
+
17
+
Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
18
+
19
+
## Scenario: Active Directory replication and topology
20
+
21
+
### TSS cmdlet
22
+
23
+
Client:
24
+
25
+
```powershell
26
+
.\TSS.ps1 -Scenario ADS_AuthEx
27
+
```
28
+
29
+
Server (domain controller (DC)):
30
+
31
+
```powershell
32
+
.\TSS.ps1 -Scenario ADS_Auth
33
+
```
34
+
35
+
### TSS cmdlet description
36
+
37
+
Run this cmdlet on both the source and destination DCs to gather data at the same time. Begin logging on both DCs using the TSS cmdlet and reproduce the issue by initiating replication with the [repadmin /replicate](/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc742152(v=ws.11)) cmdlet. For example, `repadmin /replicate dest-dc01 source-dc01 DC=contoso,DC=com`.
38
+
39
+
## Scenario: Active Directory Certificate Services (ADCS)
40
+
41
+
### TSS cmdlet
42
+
43
+
Client:
44
+
45
+
```powershell
46
+
.\TSS.ps1 -Scenario ADS_AuthEx
47
+
```
48
+
49
+
Server:
50
+
51
+
```powershell
52
+
.\TSS.ps1 -Start -ADS_ADCS
53
+
```
54
+
55
+
### TSS cmdlet description
56
+
57
+
Depending on the issue or scenario, you can run this cmdlet only on the ADCS server, the client, or both. Begin logging using the TSS cmdlet and reproduce the issue.
58
+
59
+
## Scenario: Authentication issues (Kerberos and New Technology LAN Manager (NTLM))
60
+
61
+
### TSS cmdlet
62
+
63
+
Client:
64
+
65
+
```powershell
66
+
.\TSS.ps1 -Scenario ADS_AuthEx
67
+
```
68
+
69
+
Server:
70
+
71
+
```powershell
72
+
.\TSS.ps1 -Scenario ADS_Auth
73
+
```
74
+
75
+
### TSS cmdlet description
76
+
77
+
Depending on the specific issue or scenario, you might need to gather data from the client, the server, and the DC, or from all three sources. For thorough troubleshooting, it's important to obtain data from all three sources. However, if you can't retrieve logs from the DC, you can continue logging on the client and server with the TSS cmdlet, and reproduce the issue.
78
+
79
+
## Scenario: Domain join
80
+
81
+
### TSS cmdlet
82
+
83
+
Client:
84
+
85
+
```powershell
86
+
.\TSS.ps1 -Scenario ADS_AuthEx
87
+
```
88
+
89
+
Server:
90
+
91
+
```powershell
92
+
.\TSS.ps1 -Scenario ADS_Auth
93
+
```
94
+
95
+
### TSS cmdlet description
96
+
97
+
Depending on the specific issue or scenario, you might need to gather data from the client and the DC. However, if you can't retrieve logs from the DC, you can continue logging on the client with the TSS cmdlet, and reproduce the issue.
title: Collect Data to Analyze and Troubleshoot Application Management Scenarios
3
+
description: Helps gather information about your issue by using the TroubleShootingScript (TSS) toolset and learn what data to collect based on application management scenarios.
# Collect data to analyze and troubleshoot application management scenarios
12
+
13
+
This article helps gather information about your issue by using the TroubleShootingScript (TSS) toolset before contacting Microsoft support.
14
+
15
+
## Prerequisites
16
+
17
+
Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
18
+
19
+
## Scenario: Modern, Inbox, and Microsoft Store apps
20
+
21
+
### TSS cmdlet
22
+
23
+
```powershell
24
+
.\TSS.ps1 -Scenario PRF_UWP
25
+
```
26
+
27
+
### TSS cmdlet description
28
+
29
+
The `PRF_UWP` scenario is useful for troubleshooting problems with Inbox applications (Appx or Modern apps), the Start menu, and the Shell. For example, Universal Windows Platform (UWP) apps (such as Settings, Calculator, and Microsoft Store) don't launch or crash. This scenario also applies to issues where AppX package registration fails, or UWP apps are slow or unresponsive.
30
+
31
+
## Scenario: Microsoft Store
32
+
33
+
### TSS cmdlet
34
+
35
+
```powershell
36
+
.\TSS.ps1 -Scenario PRF_Store
37
+
```
38
+
39
+
### TSS cmdlet description
40
+
41
+
The `PRF_Store` scenario is useful for troubleshooting installation problems with Inbox applications (Appx or Modern apps). For example, Microsoft Store doesn't open, crashes, hangs, or fails to install or update apps. This scenario also applies to issues where app deployments that rely on the Microsoft Store infrastructure fail, or where Microsoft Store apps don't appear in the Start menu or Company Portal.
42
+
43
+
## Scenario: WinGet
44
+
45
+
### TSS cmdlet
46
+
47
+
```powershell
48
+
.\TSS.ps1 -Scenario PRF_WinGet
49
+
```
50
+
51
+
### TSS cmdlet description
52
+
53
+
The `PRF_WinGet` scenario is useful for troubleshooting issues with WinGet cmdlets failing or hanging. This scenario also applies to issues where the installating or upgrading apps via WinGet isn't working, or issues with the Microsoft Store integration in WinGet.
54
+
55
+
## Scenario: Photos app
56
+
57
+
### TSS cmdlet
58
+
59
+
```powershell
60
+
.\TSS.ps1 -Scenario PRF_Photo
61
+
```
62
+
63
+
### TSS cmdlet description
64
+
65
+
The `PRF_Photo` scenario is useful for troubleshooting problems such as the Photos app not opening, crashing, or freezing. It also applies to issues where images fail to render or load slowly, or issues with editing, saving, or sharing photos.
66
+
67
+
## Scenario: Clipboard and copy/paste
68
+
69
+
### TSS cmdlet
70
+
71
+
```powershell
72
+
.\TSS.ps1 -Scenario PRF_Clipboard
73
+
```
74
+
75
+
### TSS cmdlet description
76
+
77
+
The `PRF_Clipboard` scenario can help diagnose issues where the clipboard functionality is degraded or broken. Examples include copy/paste failing intermittently or stopping working entirely. This scenario also applies to issues where clipboard operations are slow or hang (for example, Snipping Tool delays).
78
+
79
+
## Scenario: Camera problems
80
+
81
+
### TSS cmdlet
82
+
83
+
```powershell
84
+
.\TSS.ps1 -Scenario PRF_MediaCamera
85
+
```
86
+
87
+
### TSS cmdlet description
88
+
89
+
The `PRF_MediaCamera` scenario is useful for troubleshooting problems such as the camera not being detected or not working in apps like Teams, Zoom, or Camera. You might see a message like "No camera found" or an error code when launching the Camera app, or encounter a black screen or frozen video feed during video calls.
title: Collect Data to Analyze and Troubleshoot Group Policy Scenarios
3
+
description: Helps gather information about your issue by using the TroubleShootingScript (TSS) toolset and learn what data to collect based on Group Policy scenarios.
# Collect data to analyze and troubleshoot Group Policy scenarios
12
+
13
+
This article helps gather information about your issue by using the TroubleShootingScript (TSS) toolset before contacting Microsoft support.
14
+
15
+
## Prerequisites
16
+
17
+
Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
18
+
19
+
## Scenario: Issues applying Group Policy
20
+
21
+
### TSS cmdlet
22
+
23
+
Client:
24
+
25
+
```powershell
26
+
.\TSS.ps1 -Scenario ADS_AuthEx
27
+
```
28
+
29
+
Server (domain controller):
30
+
31
+
```powershell
32
+
.\TSS.ps1 -Scenario ADS_Auth
33
+
```
34
+
35
+
### TSS cmdlet description
36
+
37
+
Depending on the specific issue or scenario, you might need to gather data from the client and the domain controller. However, if you can't retrieve logs from the domain controller, you can continue logging on the client with the TSS cmdlet and reproduce the issue.
0 commit comments