Azure Database for PostgreSQL flexible servers. Upgrade ERROR. (Code: InternalServerError)

Question

Hello!

I'm experiencing the following error: "An unexpected error occurred while processing your request. Tracking ID: '8fd3ed48-0750-48ae-abbd-2ac18fae5ffd' (Code: InternalServerError)" when I'm trying to perform a major upgrade of my Azure Database for PostgreSQL flexible servers.

I have several servers with different versions (15, 17), and I wanted to upgrade them to version 18, but when I try to upgrade from version 15 to 16 or from version 17 to 18, I get the same error at every step of the upgrade.

I've tried this both in "Azure-cli" and from the Azure Portal, but the same error occurs.

{
    "status": "Failed",
    "error": {
        "code": "InternalServerError",
        "message": "An unexpected error occured while processing the request. Tracking ID: 'b962ed94-5a4f-4e83-924e-d58427b97902'"
    }
}

Please help me solve this!
Thanks!

Answer 1

Hi @TsaR

It looks like you’re running into a generic InternalServerError when trying to bump your flexible server from 15→16 or 17→18. That error can happen for a few reasons, so here’s a quick set of steps you can try to pinpoint and resolve it:

Review the error and activity logs • Grab the Tracking ID from the error message and pull the Azure activity logs:

az monitor activity-log list --correlation-id <your-tracking-id>

• Look for any detailed errors right before or after the failure.

Verify your resource configuration • Make sure your server has enough free storage (at least 10–20% headroom) and sufficient vCore capacity. • Double-check that you haven’t hit any regional or subscription quotas.

Run the upgrade precheck • Execute the built-in precheck to surface any unsupported extensions or misconfigurations:

az postgres flexible-server upgrade-precheck \
  --name <server-name> \
  --resource-group <resource-group>

• Address any flagged issues (e.g., drop unsupported extensions, free up storage, adjust parameters) before re-running the upgrade.

Confirm your Azure CLI is up to date • An older CLI can occasionally misbehave:

az upgrade

• After the upgrade, retry your operation.

Check Azure Service Health • Head to https://status.azure.com to make sure there aren’t any ongoing platform issues in your region.

Retry the major‐version upgrade • Once the above steps are clear, kick off the upgrade again either in the portal or via CLI:

az postgres flexible-server upgrade \
  --name <server-name> \
  --resource-group <resource-group> \
  --version 18 \
  --yes

• Monitor progress in the portal’s notifications or az postgres flexible-server show.

If you still hit that InternalServerError after going through those steps, it would help to know:

• The exact output (and any errors) from the upgrade-precheck command.
• How much free storage and vCores your server currently has.
• Whether you’re using any non-default extensions or custom server parameters.
• The exact region your flexible server is deployed in.

Hope this helps get your upgrade across the finish line!

Reference docs

• Resolve InternalServerError: https://learn.microsoft.com/azure/postgresql/troubleshoot/flexible-server/internalservererror
• Major version upgrade precheck: https://learn.microsoft.com/azure/postgresql/flexible-server/upgrade-precheck
• Perform major version upgrade: https://learn.microsoft.com/azure/postgresql/flexible-server/how-to-perform-major-version-upgrade
• Azure CLI upgrade: https://learn.microsoft.com/cli/azure/update-azure-cli
• Azure Service Health: https://status.azure.com