0 votes

We are struggeling with a bit slow response from the webinterface.

Standing on the Home page then clicking the Search tab, it takes about 5 seconds until it loads.

Standing on the Home page searching for a user from Quick search takes about 8 seconds until the result page loads (if you search for a common name that will give you a LOT of results, it still takes 8 seconds to load, but it then shows the "Loading" icon in the results pane).

Selecting a user from the results pane to show their properties also takes about 8 seconds to load (plus extra time for exchange properties to load).

We've also set up a brand new web interface server on Server 2012 R2 to test performance, but the results are about the same.

Is there any IIS tuning or something that can be done to speed things up?

We are currently running 2012.1 3.5.9329.0 (Did not see anything in the release notes about performance enhancements for the web interface in version 2012.2)

by (960 points)


That's too much. To help us troubleshoot the issue, can you answer the following questions:

  1. Are Adaxes Web Interface and Adaxes service installed on the same computer? If this is the same computer, is Adaxes service started?
  2. How many AD sites do you have in all the domains managed by Adaxes?
  3. When did it all start? Did your Active Directory undergo any infrastructure changes around the time when such time lags started?


1: We have tried both (hence the new 2012R2 server). Yes, Adaxes service is started
2: 6 sites in total (also 6 managed domains)
3: This has been a issue for quite a while, cannot pinpoint when it started.

1 Answer

0 votes
by (216k points)

The most probable reason for the issue is that there are no Domain Controllers for some of the AD domains managed by Adaxes in the AD site where the Adaxes service is installed. In such a case, Adaxes service tries to connect to DCs located in other AD sites, which involves time lags related to remote calls.

To remedy the issue, you can install DCs for such domains in the AD site where Adaxes service is installed.

Alternatively, if you don't need the Adaxes service in that site to manage such domains, you can unregister them to prevent calls to remote DCs and the related time lags. If you have several Adaxes services that share common configuration, the other services in the configuration set will continue managing the domains even if you unregister them on one of the services in the set, which gives you the advantage to register domains only on those Adaxes services where you need the domains to be managed. For information on how to unregister a domain, see the following help article: http://www.adaxes.com/help/?HowDoI.Mana ... omain.html.


OK, we've received the file and asked our QA team to investigate the issue. We'll update you as soon as they come up with something.


By the way, how many pending Approval Requests do you have? There was an issue in Adaxes that caused Web interface slowdown if there were many pending Approval Requests. It was fixed in Adaxes 2013.1.

To find all pending Approval Requests:

  1. Launch Adaxes Administration Console.
  2. Expand the service node that represents your Adaxes service.
  3. Navigate to Configuration \ Approval Requests.
  4. In the Result Pane (located to the right), select All Requests and Pending.
  5. Click the Apply Filter button.

To remedy the issue with many Approval Requests, you'll need to upgrade. Find the latest build here.

Upgrade Instructions


There are no approval requests pending.



OK. In a minor update to Adaxes 2013.2 that will be available in a day or two, we'll implement the possibility to enable detailed tracing of operations performed by the Web Interface. After upgrading to the minor update, you'll be able to enable tracing so that we can identify, which operation is causing the slowdown.



The minor update that allows you to enable detailed tracing of operations performed via the Web Interface was released on November 21. You can download it here.

Upgrade Instructions

What's New in the Minor Update

To enable tracing in the Web Interface after you upgrade to the minor update:

  1. Open the folder that contains the Web Interface that you are experiencing issues with. By default, Adaxes Web Interface sites are installed to the following folders:
    C:\Program Files\Softerra\Adaxes 3\Web Interface\Admin\
    Help Desk:
    C:\Program Files\Softerra\Adaxes 3\Web Interface\HelpDesk\
    C:\Program Files\Softerra\Adaxes 3\Web Interface\SelfService\

  2. Find the Web.config file and open it with any text editor.

  3. Find the following lines in the file:

     <!--- Trace settings -->
     <trace enabled="false" pageOutput="true" requestLimit="40" localOnly="false" mostRecent="true" />
  4. Change trace enabled="false" to trace enabled="true".

  5. Find the following lines:

     <!-- Web settings -->
  6. Paste the following block before the lines:

            <add name="WebPageTraceListener" 
                 type="System.Web.WebPageTraceListener, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
  7. Save the file.

After making modifications to the file, try logging into the Web interface and performing the actions that caused the slowdown. Each time you perform an action, the Web Interface will output tracing information at the bottom of the page. Save this page as an HTML file and send this file to our support email (support@adaxes.com).

Related questions

0 votes
1 answer

Hello - It seems we've been experiencing some slow performance via the web interface lately. It was reported to me that it seem to have gotten bad within the last week. ... where to start to troubleshoot. We only have 1 server that caters to Adaxes. Thank You

asked Apr 26, 2016 by MeliOnTheJob (1.7k points)
0 votes
1 answer

I am noticing both with 2013.1 and 2013.2 that inital page load for each app is very sluggish, however subsiquent loads are awesome...I have seen a few posts in the back ... app pool is the root but not sure thoughts on IIS Performance tuning for IIS 7.5??

asked Nov 4, 2013 by kf4ape (490 points)
0 votes
0 answers

Hi, I've got very slow perf on web AdaxesADmin interface. I've done search in this forum, ad firewall rule to open 389,636,3268,88,135,49152-65535 ports on my ... .Stop() give me : 'serveur RPC pas disponible. HRESULT 0x8007068A' Resolving AdsPAth: 5596 ms

asked Nov 8, 2018 by Nicolas.lussier (190 points)
0 votes
1 answer

I'm lost as to why "Create User" doesn't show up. I made a new dashboard, mirroring the default Help Desk. Under Actions, I enabled Create User. On the web interface, the option to create a user is not showing. Am I missing a step?

asked May 15 by tromanko (330 points)
0 votes
1 answer

I'd like to limit users from being able to login to the Web interface. In other words, if a user opens multiple browsers or tabs, can I prevent them from being able to login to each tab/browser and starting multiple sessions? Thanks!

asked Apr 10 by cewilson (140 points)
3,435 questions
3,131 answers
546,360 users