1. On the server where the Identity Manager web portal is installed, navigate to C:\inetpub\wwwroot\IdentityManager\bin and open WebDesigner.ConfigFileEditor.exe to edit the web.config file located under C:\inetpub\wwwroot\IdentityManager:
2. Connect to the database:
3. Click to expand the "Log" section;
4. Enable the logging level as specified by Support for version 7. "Trace" is used to gather verbose logging. Support will normally request both the "Application log" and the "Database log":
For version 6, specify the SQL Log directory to enable SQL logging:
Save the config file once logging has been enabled. This will trigger a restart of the application pool.
5. After reproducing the issue, gather the required application and database logs from the C:\inetpub\wwwroot\IdentityManager\App_Data\Logs directory. For version 7 these will be called log.txt and dblog.txt, respectively; for version 6 the date is used, e.g. 2017-07-03 10-38-54.txt and SQL_2017_07_03_11_08_30_772.log, respectively. E.g.:
Version 6 logs: