Hi,

Can you make sure the .ini is correct? The information should be like this:

Metasource = IAM
Server = [Servername]
Database = [IAM_DATABASE]

Additional entries like RDBMS, Authentication andn Language can of course be added, but the error you are getting is that the database in the .ini does not have the get_gui_global_settings stored procedure.

If I use

Database = [IAM_DATABASE]

It opens IAM application and my Application, too:

Previously i was using  Database = MY_APPLICATION_DATABASE]

Can i use an .ini parameter to open only my application? Or is it a permission/setting on IAM for the user?

In the .ini, the Database parameter has to be equal to the IAM database where the end product's model is placed inside. The GUI will obtain the model of you end product(s) from the IAM database that is filled in. It cannot be your application database.

You picture is indeed the behavior I would have expected as IAM's model is inside your IAM. If you have rights to both your end product and the IAM, you will see both applications. If the logged in user only has rights to the end product, the IAM will not be visible.

If you apply the IAM rights to IAM and you have a name with weird characters like Zoë in the username the IAM sync fails with an error, but at that moment all rights of all users are deleted.

No-one is able to login anymore because the rights on the database are deleted.

Then you get this message as well...

Your user has no execute rights on stored procedures?

For your information:
Today we had the same error message in a newly set up environment.
Ultimately, it turned out that the Active Directory group that the user logs in with did not have a certain membership.
Checking this membership in the relevant AD group (at [Security], [Users] of the IAM database) immediately solved the problem.

Long live the community and the reference functionality we have with it :-)

Today it turned out that the IAM update from 2024.2 to 2024.3 had removed the previously added right of the AD group, resulting in the error message "get_gui_global_settings : missing stored procedure" again.

Adding the necessary right to the AD group solved the problem again.

We encountered the same issue because the 'End User' role was renamed (or dropped and recreated) as 'end_user' to align with the role name standardization introduced in 2024.3

It might be a good idea for Thinkwise to include this as a warning in the Release blog, as it is currently not mentioned (only that you should check any logic) 2024.3 | Thinkwise Documentation

We have received a ticket for this and will be resolved in the coming sprint (13-01 / 07-02).