Jonathan, I should have clarified. All of my testing was done using Operating System Authentication (OSA).
Answers to your questions:
- Yes, we are using OSA, and Easy Connect hangs when trying to access Geodatabase Connection Properties
- For our implementation, Easy Connect with database authentication (schema owner DB user) also hangs.
- When username and password is not saved, I get an error. The odd part, I got the error before it even asked me for a username and password.
- Connection Error: Unable to get geodatabase connection properties.
- A database connection exception has occured. Underlying DBMS did not accept username/passowrd.
For our implementation, what we have found is that all of the errors are generated when "SDE" is selected as the schema geodatabase, which is the default when the Create Database Connection dialog. If we use the Create Database Connection geoprocessing tool and pre-set a schema other than "SDE", then TNSNAMES and LDAP works fine for seeing and changing Geodatabase Connection Properties. Oddly, Easy Connect still has issues.