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: articles/update-manager/migration-troubleshoot.md
+9-12Lines changed: 9 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,19 +14,19 @@ ms.author: sudhirsneha
14
14
15
15
This article describes the errors that might occur when you use migration portal experience or scripts, and how to resolve them.
16
16
17
-
## Required PowerShell modules for executing prerequisite script are not installed
17
+
## Required PowerShell modules for executing prerequisite script aren't installed
18
18
19
19
### Cause
20
20
21
-
When the required powershell modules are not installed for executing the prerequisite scripts, you may see the following errors:
21
+
When the required PowerShell modules aren't installed for executing the prerequisite scripts, you may see the following errors:
22
22
23
23
:::image type="content" source="./media/migration-troubleshoot/error-prerequisite-scripts.png" alt-text="Screenshot that shows the error code when PowerShell modules aren't installed. " lightbox="./media/migration-troubleshoot/error-prerequisite-scripts.png":::
24
24
25
25
:::image type="content" source="./media/migration-troubleshoot/error-migration-prerequisite-scripts.png" alt-text="Screenshot that shows the error code when the required PowerShell modules aren't installed. " lightbox="./media/migration-troubleshoot/error-migration-prerequisite-scripts.png":::
26
26
27
27
### Resolution
28
28
29
-
Ensure you have successfully executed the Command`Install-Module -Name Az -Repository PSGallery -Force`
29
+
Ensure you successfully execute the command`Install-Module -Name Az -Repository PSGallery -Force`
30
30
31
31
## Unable to acquire token for tenant organizations
32
32
@@ -36,14 +36,11 @@ Encountering a warning as - unable to acquire token `organizations` with error `
36
36
37
37
### Cause
38
38
39
-
This is part of one of the documented [issues](https://github.com/Azure/azure-powershell/issues/25005) with Az.Accounts 3.0.0 module. [Learn more](/answers/questions/1342970/warning-unable-to-acquire-token-for-tenant-organiz)
39
+
This is part of one of the documented [issues](https://github.com/Azure/azure-powershell/issues/25005) with Az.Accounts 3.0.0 module. [Learn more](https://learn.microsoft.com/answers/questions/1342970/warning-unable-to-acquire-token-for-tenant-organiz)
40
40
41
41
### Resolution
42
42
43
-
Execute command `Update-AzConfig -EnableLoginByWam $false` in an elevated Powershell Session.
44
-
45
-
46
-
## WARNING: Unable to acquire token for tenant organizations
43
+
Execute command `Update-AzConfig -EnableLoginByWam $false` in an elevated PowerShell Session.
47
44
48
45
### Issue
49
46
@@ -66,19 +63,19 @@ Your organization requires to use `Connect-AzAccount` with `DeviceCode` paramet
66
63
67
64
### Cause
68
65
69
-
[Operational Insights](/powershell/module/az.operationalinsights/) module is not installed.
## Could not convert string to DateTimeOffset: 1719675651. Path 'expires_on', line 1, position 1608.
72
+
## Couldn't convert string to DateTimeOffset: 1719675651. Path 'expires_on', line 1, position 1608.
76
73
77
74
### Cause
78
75
79
-
This error can come up while executing the Migration/Deboarding Runbook in Azure. This can happen if you have custom Az Modules in your automation account which are outdated.
76
+
This error can come up while executing the Migration/Deboarding Runbook in Azure. This can happen if you have custom Az Modules in your automation account, which are outdated.
80
77
81
78
### Resolution
82
79
83
-
Delete custom Az Modules and ensure that default Az Module is updated to 8.0.0 for Powershell 5.1
80
+
Delete custom Az Modules and ensure that default Az Module is updated to 8.0.0 for PowerShell 5.1
0 commit comments