Select to view content in your preferred language

Pro 3.7.1 + Azure Database for PostgreSQL, Enable Enterprise Geodatabase tool fails

84
3
yesterday
danbecker
Frequent Contributor

Azure Government tenant

Azure Database for PostgreSQL flexible servers, ver 15.18

Pro 3.7.1 running on Azure Virtual Desktop. OS is Win11 25H2 Multi-session

Everything is co-located in the same Azure GOV Virginia datacenter.

 

We've been running this db instance for years, absolutely no changes. The only thing that's recently changed is Pro 3.6.3 got upgraded to Pro 3.7.1. That process also created a new AVD session host image (obliviously).

Our workflow for creating a new eGDB that's worked for years:

1) PgAdmin4 is running on the AVD machine, we connect to the db instance as admin user, then create a new database, owned by SDE. 

2) SDE login role is also a member of azure_pg_admin.

danbecker_0-1786126217447.png

3) Pro 3.7.1, create new db connection to the new db, connecting as user SDE, save credentials in connection.

4) Run Enable Enterprise Geodatabase tool. The Authorization File (keycodes) we're using is from ArcGIS Server 12.1 (windows)

Error: 

The geodatabase administrator needs additional privileges to install or upgrade the geodatabase. To create a geodatabase in Postgresql, Arcsde admin user must have super user priviliges.
User does not have required privileges for geodatabase setup.

 

Pro 3.6.3 works fine:

I then signed-out of that Pro 3.7.1 AVD machine and signed-into a Pro 3.6.3 machine.

Ran the exact same Enable Enterprise Geodatabase tool, with the same database connection file (SDE user), also the same 12.1 keycodes authorization file. 

Success. 

danbecker_0-1786127126783.png

 

 

Why would this tool work at 3.6.3 and not 3.7.1 ? 

Anyone else experience this? 

 

0 Kudos
3 Replies
George_Thompson
Esri Notable Contributor

Looks like there is an issue at Pro 3.7.x: https://support.esri.com/en-us/bug/unable-to-create-an-enterprise-geodatabase-or-upgrade-a-bug-00018...

Maybe you can create it with Pro 3.6.x, then upgrade with the Pro 3.7 client.

--- George T.
0 Kudos
MarcoBoeringa
MVP Alum

@George_Thompson 

How can the status of this bug be "fixed" if the fix hasn't been backported to the 3.7.x cycle, which is the current release cycle? This time and again keeps amazing me: bug fixes need to be backported to the version they were introduced, or at least the oldest still fully supported release cycle that contains the bug. That is basic IT product management.

0 Kudos
danbecker
Frequent Contributor

Looks like I'm late to the party; glad we haven't deleted all our AVD machines running Pro 3.6.3 yet! 

0 Kudos