Skip to main content
I am trying to activate indicium + Mobile GUI for one of my customers. The Test/Demo environment and the model of my application works without problems. Unfortunately the final application can not be found.

The following error message appears::



https://[url]/api/iam returns SQLSERVER_IAM: 2018.2

https://[url]/api/5 returns Application not found



I checked the following components:

- Latest versions of Indicium (2018.2.5), SF, IAM (2018.2), Mobile GUI (2018.2.8).

- The user has got all rights.

- Application alias



What else could it be?
Hi Harm,



Do both the pool user and the user you are trying to log in have rights to the application with ID 5? You can verify this by executing the following statements on the IAM database:

code:
exec get_gui_gui_appl 'pool user', 5, 99
exec get_gui_gui_appl 'end user', 5, 99


Both statments must give results.

If both give results, please check the following:



1. Does Indicium refer to the same IAM database in the application settings?

2. Is the pool user correct? If there is a pool user in the application settings, it has priority over the Application Pool user in IIS.

Kind regards Vincent


Hi Vincent,

Thank you for your feedback. I have been able to solve it with your help.

The pool_user had no rights in my application. I have added these to a user group with full rights.

I just do not understand why this is necessary for Indicium/Mobile GUI and net for the Web GUI?

Sincerely,

Harm
Hi Harm,



The Web GUI loads the model for every user, whereas the Indicium application tier only loads the full model once (using the pool account).


The information in this topic is a bit outdated. From Thinkwise Platform version 2018.3 and onwards, the pooling account used by Indicium (and Web) to access the databases no longer needs to be present in IAM.



The SQL statements seen above are not usable for version 2018.3+ as they have been replaced with different mechanisms.



If an Application not found message persists, check out the documentation on this response.