0 votes


our users have to login to the Adaxes web service by using their username and password, no SSO is used.
I have configured the option in the web interface "domainless username".
It is working fine, till after some weeks/months the user cannot login anymore.
They get the error message" The account name is invalid. It is expected to be formatted either as 'DOMAIN\user' or 'user@domain'"
Login with the domain is still possible, without not.
I could fix it by deleting/re-adding the group of users to the web interface/access control, but after some weeks/months this happens again.

Thank you

by (240 points)

1 Answer

0 votes
by (216k points)

Hello Thorsten,

It looks like the computer where the Web Interface is installed cannot use its own account to login to the your DC and authenticate users. To remedy the issue:

  1. On the computer, where Adaxes Web Interface is installed, launch Internet Information Services (IIS) Manager from Control Panel \ Administrative Tools.
  2. In the Connections Tree, expand the server that hosts the Web Interface type, and then expand Sites.
  3. Expand the web site for Adaxes Web Interface.
  4. Select the virtual directory for the Web Interface type that you are experiencing issues with.
  5. In the right view pane click Basic Settings.
  6. Note the application pool that is used for the Web Interface type. It is displayed in the Application pool field.
  7. Click Cancel.
  8. In the Connections Tree, select Application Pools.
  9. Select the application pool that is used for the Web Interface type.
  10. Click Advanced Settings in the right view pane.
  11. In the dialog box that appears, select the Identity field.
  12. Press the embedded Edit button.
  13. Select the NetworkService built-in account.
  14. Click OK two times and restart IIS.

Related questions

0 votes
1 answer

I recently upgraded to version 2013.1 and since then a create user action on my help desk website no longer adds the @domainname.com to the User logon name field. ... there Exchange will not create the mailbox. Any help with this issue is appreciated. Thanks

asked May 13, 2013 by bemho (520 points)
0 votes
1 answer

This note is found in the documentation on how to configure allowed domains in Adaxes 2023. Allowed domain names can only be selected from the alternative UPN suffixes for on- ... required to pick up the change, or is there another way to trigger the update?

asked Jan 31 by dtb147 (290 points)
0 votes
1 answer

We are testing Windows Autopilot and would still like to use the adaxes client to allow for SSPR. Is it possible to configure the Windows Integration settings on a machine that is not domain joined but is joined through Azure AD?

asked Sep 3, 2020 by scoutcor (120 points)
0 votes
1 answer

Hi all, I am receiving the following error when trying to connect to my domain using a Domain Administrator account. Any idea how to fix this? Thanks Derek

asked Dec 9, 2013 by DerekZA (50 points)
0 votes
1 answer

Unfortunately, the logon names are not set automatically when a user is created. For the Full Name attribute everything is working fine. Where did I make a mistake here? Greetings, Robin

asked Apr 26, 2022 by robin.christmann (160 points)
3,167 questions
2,870 answers
506,086 users