When a large number of Managed Domains are integrated with Active Roles, or when the Active Roles Service is located in a site with significant latency to one or more Domain Controllers, clicking on Directory Management in the Active Roles Web Interface takes a long time or fails with the error Request timed out.
Clicking on Directory Management in the Web Interface sends a query to the associated Active Roles Service and requests top-level Domain information for all Managed Domains as one operation.
When working with many or with geographically distant Domain Controllers, this operation can take some time. If the duration of this operation exceeds the default timeout period set within IIS of 120 seconds, then the operation will fail with a timeout error.
WORKAROUND
Increase the default timeout within IIS to meet the requirements of the environment.
Edit the time out settings in the web.config file for the target IIS site by following the below steps:
1. In the web.config file (can be located here: WI_Install_Path\Public\) in the <system.web> section locate <httpRuntime executionTimeout="<time_in_seconds>"/> and correct the value to a higher number. If there is no such setting, add it, so it look as follows (example for the 5 minutes setting):
<system.web>
<httpRuntime executionTimeout="300"/>
2. In IIS 7 Manager check the 'Connection Time-out' setting in seconds (Right-click on the site (for example: "Default Website"), click "Manage Web Site" | "Advanced Settings"), increase the timeout value as needed.
STATUS
Enhancement request number 90868 has been submitted to Development for consideration in a future release of Active Roles.
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center