Bug ID Number |
BUG-000120966 |
Submitted | March 18, 2019 |
Last Modified | June 5, 2024 |
Applies to | Portal for ArcGIS |
Version found | 10.6.1 |
Operating System | Windows OS |
Operating System Version | 2008 |
Status | Non-Reproducible
This issue was not reproducible when tested by the development team. Issues may be given this status when they cannot be reproduced or are no longer relevant in a development version of the software, but a specific fix was not installed to address the issue. The issue's Additional Information section may contain further explanation.
|
Additional Information
This is more likely due to a problem failing over, rather than the migration workflow for some reason. The standby should be properly promoted to primary during unregistering. More investigation is needed to determine why the standby cannot be promoted.
Workaround
- Navigate to the portal's local ...\DB folder (typically located in C:\arcgisportal\db) on the new machine. There is a file called recovery.conf. Rename or move the file out of this directory.
- Restart the portal OS service in the OS Services MMC.
- Change the content directory location on the new machine back to local storage (this reboots the portal again).
- Restart the ArcGIS Server OS service in the OS Services MMC. (This points the server at the new portal machine. Otherwise token errors are returned).
It appears that the new Portal machine fails to promote after removing the primary portal in step 4. This keeps the new machine's internal PostGRES in read-only mode. Removal of the recovery.conf file and restarting the portal manually puts the machine back in master mode, which allows writes to the database. After that the necessary changes to the portal directory can be made.
Steps to Reproduce