| Numéro d’ID de bogue |
BUG-000128413 |
| Envoi | February 5, 2020 |
| Dernière modification | February 20, 2025 |
| S’applique à | Portal for ArcGIS |
| Version trouvée | 10.6.1 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 2016 64 Bit |
| Statut | Duplicate
Le problème est le doublon d’un problème existant. Pour plus d’informations, reportez-vous à la section Informations supplémentaires correspondant au problème. Les clients concernés par le doublon du problème sont automatiquement associés au problème ouvert.
|
Informations supplémentaires
Duplicate of BUG-000127231
Solution de contournement
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?
Étapes pour reproduire