0 votes

As we have begun to go into production with Adaxes and we are noticing that it is becoming increasingly slower. Our installation is a VMware VM running 2008 R2. It originally had one 1 CPU assigned to it, but we noticed that the CPU would spike on the queries, so we added another CPU and 2 more GB of memory to upgrade it to 6GB.

An example of the slowness would be when we would type the first name of a user in the Quick Search field on the home tab, the browser will start to spin, but it will take another 20 - 30 seconds for it to go to the search page and then once there another 20-30 seconds to show results.

I have also checked the resources on the domain controllers and found nothing there indicating resource problems.

Is there some recommendations or something I could look at to try and figure out what is slowing down the pages?

Adaxes is helping us manage two forests. The first forest has a total of 4 domains and the second forest is a single domain. There is no trust between the forests. Adaxes is using two separate accounts to manage each forest.

Thanks

by (1.2k points)
0

Hello,

To help us troubleshoot the issue, please enable tracing in Adaxes Web Interface:

  1. On the computer where your Adaxes Web Interface is installed, open the folder that any of Adaxes Web Interface sites are installed to. By default, Adaxes Web Interface sites are installed to the following folders:

    • Administrators:
      C:\Program Files\Softerra\Adaxes 3\Web Interface\Admin\
    • Help Desk:
      C:\Program Files\Softerra\Adaxes 3\Web Interface\HelpDesk\
    • Self-Service:
      C:\Program Files\Softerra\Adaxes 3\Web Interface\SelfService\
  2. Find the Web.config file.

  3. Find the following lines:
    <!--- Trace settings -->
    <trace enabled="false" pageOutput="true" requestLimit="40" localOnly="false" mostRecent="true" />

  4. Change trace enabled="false" to trace enabled="true" and save the file. This will enable tracing in this Adaxes Web Interface site.

After you've enabled tracing, login to the Adaxes Web Interface site for which you enabled tracing and try to load one of the pages that causes slowdowns. When the page loads completely, some tracing information will be available at the bottom of the page. Save this page as an HTML file and send this file to our support email (adaxes@softerra.com). We'll see what we can do about that.

0

Further troubleshooting found that the issue is with the Panel and a componet(s) under it. I removed them all and the pages are working now. What I found is that every time the page came up, the panel was still processing (GeatewayService.asmx) and when you did anything, the cancelling of that process also took time. So if you went to the home page and started a quick search, you had to wait for the process to cancel before you went to the search page and then that panel process slowed up the actions on the search page.

0

Hello Robert,

We need some time to study your trace file. I'll update this topic as soon as we come up with something.

0

I think I have narrowed it down to the My Approvals component. I created a duplicate site and with all the components, I had the same issue, but when I removed My Approvals, the performance issue went away.

0

Robert,

OK, we'll think of a way to resolve the issue, thank you for the information.

1 Answer

0 votes
by (216k points)

Hello Robert,

What could cause the issue is that you have too many Approval Requests (over 1000). To check the number of pending Approval Requests:

  1. Launch Adaxes Administration Console.
  2. In the Console Tree, expand the service node that represents your Adaxes service.
  3. Select Approval Requests.
  4. In the Result Pane, select All requests in the Show field and Pending in the Status field.
  5. Press the Apply Filter button.
  6. The number of pending Approval Requests will be shown at the top of the Result Pane.
0

The Inactive Computer Deleter! We have a lot of old computer accounts in our AD, but this was running every night. I don't believe I had anything less than 5000 pending requests to disable computers. I had scheduled this back on the Dec 12th and never saw anything in the history to indicate that it was doing anything, so I put it on my to do list to check out when I had time not knowing that it was building the pending approval queue to create a debilitating experience. Every night that it ran, it duplicated an approval request. I noticed a request for the same computer for each night that it ran.

I have learned to make sure I understand and read what exactly the process will do.

I would like to ask that something be put in to stop the scheduled processes and draw attention to the fact that the pending approval queue is too high.

Thanks for help!!

0

Hello Robert,

To remedy the issue, you can find all inactive computers in your Active Directory using the Inactive Computers Report. Then, you can disable them, for example. Also, you can move your inactive computers to a certain OU and then exclude the OU from the activity scope of the Inactive Computer Deleter Scheduled Task. If you want to receive a notification each time the Scheduled Task creates an Approval Request, you need to include yourself to the list of approvers of the Disable the Computer account action of the task.

To find all inactive computers in your Active Directory:

  1. Login to Adaxes Web Interface.
  2. Select Reports from the Top Navigation Menu.
  3. On the page that appears, select Inactive Computers under Computer Reports > Account Status.
  4. Specify the number of days during which a computer should be inactive to match the criteria and click Generate.

On how to exclude a certain OU from the activity scope of a Scheduled Task, see Step 10 of the Schedule Tasks for Active Directory Management Tutorial.

To receive notifications whenever the Inactive Computer Deleter Scheduled Task creates an Approval Request:

  1. Open Adaxes Administration Console.
  2. In the Console Tree, expand the service node that represents your Adaxes service.
  3. Navigate to Configuration \ Scheduled Tasks \ Builtin.
  4. Select Inactive Computer Deleter.
  5. Double-click the Modify the computer: disable the account action.
  6. in the dialog box that appears, click Add... in the Get approval for this action section.
  7. In the dialog box that appears, select your own user account and click OK.
  8. Double-click the Delete the Computer action.
  9. in the dialog box that appears, click Add... in the Get approval for this action section.
  10. In the dialog box that appears, select your own user account and click OK.
  11. Click OK again and save the Scheduled Task.
    Now you will receive notifications on Approval Requests created by the Inactive Computer Deleter Scheduled Task to the e-mail specified in the Email property of your user account.

Related questions

0 votes
0 answers

Hello, we installed Adaxes on a clean Windows 2012 R2 system. Clean means there is no other software installed. After starting the Web interface configurator the screen hangs and ... time to get a cup of copy. Any advice how we can investigate this behaviour?

asked Jul 12, 2018 by HorstR (460 points)
0 votes
0 answers

Hello We added a second domain to our Adaxes environment and we saw a huge drop in performance in the web interface. We are looking at this Web Interface Slow Performance link for now and wanted to see if there were any other suggestions.

asked Feb 21, 2017 by willy-wally (3.2k points)
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

Hi, we have a problem when calling the Exchange properties. This takes a very long time. Can we speed up in any way? How then does the communication with the Exchange? Thanks a lot and greets, Dennis

asked Mar 11, 2014 by dega78 (40 points)
0 votes
0 answers

I've been getting reports that the performance of 2013.2 is slower than the previous version of ADAxes. Searching, editing, etc. Is this a known issue?

asked Feb 17, 2014 by BradG (950 points)
3,548 questions
3,239 answers
8,232 comments
547,814 users