When High Availability (HA) is enabled, upgrading the master database in one server (for example, PRIMARY) attempts to apply the same changes to the other server (for example, SECONDARY).The result is that you cannot upgrade syspartitionkeys and sysslices because those tables do not yet exist. Consequently, the first server that is upgraded cannot upgrade the master database.
The upgrade on the second server succeeds, although you see several warning messages about the privileges not being revoked (message 4622, state 1). When you re-run the upgrade process on the first server, it then succeeds, although it also produces the same messages.
To avoid this problem:
Disable HA in the old secondary server:
sp_companion primary-server-name, 'drop' sp_configure 'enable HA', 0
Disable HA in the old primary server:
sp_configure 'enable HA', 0
Restart the servers.
To perform the upgrade re-run installmaster.
Restart both servers.
Re-run installhasvss on both servers.
In the new secondary server, enter:
sp_companion primary-server-name, configure[, with_proxydb]
