Skip to main content
Question

DeviceHub AuthLogin error – concurrent API login limit reached

  • April 13, 2026
  • 8 replies
  • 29 views

Hi,

We are running into an issue with Acumatica DeviceHub and wanted to check whether anyone has seen this before.

We are receiving the following error in the DeviceHub log during label printing:

Error calling AuthLogin
“The number of concurrent API logins specified for your user account on the Users (SM201010) form has been reached.”

Here is what we found so far:

  • The DeviceHub user in Users (SM201010) has Max. Number of Concurrent Logins = 3
  • In License Monitoring Console (SM604000), our license shows:
    • Maximum Number of Web Services API Users = 20
    • Maximum Number of Concurrent Web Services API Requests = 3
  • We changed Maximum Number of Concurrent Web Services API Requests from 3 to 5 and tested again, but the error still remained
  • In System Monitor → Active Users, we can see multiple active DeviceHub sessions, including API sessions
  • DeviceHub appears to repeatedly try to log out and log back in, but continues failing with the same AuthLogin error
  • Because of this, printing fails when DeviceHub tries to retrieve the PDF for the print job

Our questions are:

  1. What is the best way to clear or reset old/stuck DeviceHub API sessions?
  2. Is there a recommended way to prevent DeviceHub from creating multiple lingering sessions?
  3. Would increasing Max. Number of Concurrent Logins for the DeviceHub user be the correct fix, or is this more likely caused by stale sessions / multiple DeviceHub instances running?
  4. Is there any DeviceHub-side cleanup or logout handling we should check?

Any guidance would be appreciated.
Thanks

8 replies

mohammadnawaz51
Jr Varsity II
Forum|alt.badge.img+6

@rmore49 This is login issue, did any upgrade happens? or any new tenants created?


  • Author
  • Freshman I
  • April 13, 2026

Hi,

Yes, you are correct a new tenant was created. Could that be the reason for this issue? If so, what should we do to prevent this error from continuing?

Thanks.


mohammadnawaz51
Jr Varsity II
Forum|alt.badge.img+6

@rmore49 Which version you are using?

Also did you given the tenant name in the configuration?


  • Author
  • Freshman I
  • April 13, 2026

We are currently using Acumatica 2025 R1, build 25.101.0153. We were recently upgraded to R2, but that upgrade was revoked immediately since we did not want to proceed with it. We also have two separate tenants, one for the test site and one for the production site, and they are named differently.


mohammadnawaz51
Jr Varsity II
Forum|alt.badge.img+6

@rmore49 Is the new tenant created today, did you install the device hub again since you revoked the upgrade immediately! Reconfigure the device hub will resolve the issue.

 


  • Author
  • Freshman I
  • April 13, 2026

Hi,

Thanks for your reply

The tenant was actually created some time ago, but we had not been using this DeviceHub much. We were able to log in before, but the upgrade issues happened a few days ago, and since then we have not been able to log in to DeviceHub. We only just realized that the two issues might be related.

When you say to reconfigure DeviceHub, do you mean we should update the existing configuration, or delete it and create a new one from scratch? In your opinion, which option would be better in this case?

Thanks.


mohammadnawaz51
Jr Varsity II
Forum|alt.badge.img+6

@rmore49 take the backup of device hub files and create a new one or try from different system.


Forum|alt.badge.img
  • Jr Varsity I
  • April 14, 2026

@rmore49 try to reinstalling the device hub try to set up again - reconfiguring device will solve your problem.