| Bug ID Number |
BUG-000128413 |
| Submitted | February 5, 2020 |
| Last Modified | February 20, 2025 |
| Applies to | Portal for ArcGIS |
| Version found | 10.6.1 |
| Operating System | Windows OS |
| Operating System Version | 2016 64 Bit |
| Status | Duplicate
The issue is a duplicate of an existing issue. See the issue's Additional Information section for details. Customers associated with the duplicate issue are automatically attached to the open issue.
|
Additional Information
Duplicate of BUG-000127231
Workaround
Main workaround for the first scenario:
- Fix: Move the content directory to the C: drive using portaladmin. Upgrade Portal for ArcGIS, and move the content directory back to the D: drive
Also tested other scenarios which were successful:
- The second scenario(successful upgrade):
- When using the OpenStack virtual machine manager, use virtual machine tools to create a second D: drive.
- Using the GUID Partition Table setting, bring the drive online in Disk Management.
- Install Portal for ArcGIS 10.6.1, specify the content directory to D: drive.
- Upgrade Portal to ArcGIS 10.7.1
- Successful upgrade.
- Third Scenario(successful upgrade)
- Using disk management, shrink the C: drive, then create a D: drive from the leftover partition.
- Install Portal for ArcGIS 10.6.1, specify the content directory to D: drive.
- Upgrade Portal for ArcGIS 10.7.1.
- Successful upgrade.
- The underlying question: Why does the Portal for ArcGIS upgrade not work in the first scenario when using a MBR initialized D: drive that was created from the VM tools?
Steps to Reproduce