Thanks George - that's super helpful!
If you are using the Pro 3.2 client for the upgrade, it may be due to version of the geodatabase. You will need to do an intermediate upgrade to 10.6.1 or newer first, then you can go to Pro 3.2. I did notice that you can use Pro 3.0.x as it will upgrade from 10.4.1.
Pro 3.2 help: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-sql-server/upgrade-geodatabase-sqlserver.htm
You can upgrade directly from a 10.6.x, 10.7.x, 10.8.x, 10.9.x, or 11.x geodatabase if your database release is supported for the ArcGIS version to which you upgrade.If SQL Server is not at a release supported for the geodatabase version you upgrade from and the geodatabase version you upgrade to, you may have to upgrade the database and geodatabase multiple times before you can upgrade the geodatabase to the latest version.For each intermediate geodatabase upgrade, follow the upgrade instructions for that geodatabase version, and test the geodatabase as you move from version to version.
If SQL Server is not at a release supported for the geodatabase version you upgrade from and the geodatabase version you upgrade to, you may have to upgrade the database and geodatabase multiple times before you can upgrade the geodatabase to the latest version.
For each intermediate geodatabase upgrade, follow the upgrade instructions for that geodatabase version, and test the geodatabase as you move from version to version.
I'm having this exact same issue 13 years later in ArcGIS Pro 3.2 - does anyone have any suggested reading or how to I hit 'Run Upgrade' on a 10.4.1 geodatabase from the Catalog view in Pro? I'm seeing the exact same error as above as DBO owner...
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.