0 votes

Just recently upgraded to 2018.1

When I create a new user from a user template, it's not working correctly.

I created a user called Sams Club. And look at the image below. It is using the Username from the Template, not from my form in the "Before User Creation" business rule.

When I don't use a template everything works fine though.

by (1.4k points)


For troubleshooting purposes, could you post here or send us (support[at]adaxes.com) a screenshot of the After User Creation Business Rule?


Sent email to support.

1 Answer

0 votes
by (227k points)
selected by
Best answer


Thank you for the provided details. According to the Business Rule After User Creation configuration, First Name and Last Name are used to set the email address of the new user, not the username. To remedy the issue, replace the value references combination %firstname%.%lastname% with %username% in the corresponding action.


That section is correct, it's the Before user creation which is wrong. I just sent some more information.


Ok we have a solution from Support on this. So basically I had a custom user creation action that uses a AD User template. In the form I had removed a few fields that I didn't think was important for the user to see to complete the form. Those were DisplayName and User Logon Name (pre-Windows 2000). I had to re-add those to the form as a work around to make this work again.

Here's the response and steps from Support on this:

Thank you for all the provided details. The issue is caused by a bug in Adaxes 2018.1. We will fix it in the next update to Adaxes 2018.1. As a workaround for now, you need to add the sAMAccountName property to the Custom New User using Template action form. To do so:

1. Open Adaxes Web Interface Configurator
2. In the top left corner, select the Web Interface.
3. In the left pane, click Actions.
4. Double-click the Create New DFCU User action.

5. Activate the Form Customization tab and click Customize Form.

6. Select the General section and click Add below the Fields section.

7. Select User Logon Name (pre-Windows 2000) and click OK three times.

  1. Save the changes.

Related questions

0 votes
1 answer

After we updated our site to 2018.1 suddenly the Password Self Service link is throwing an error: " Could not load file or assembly 'Softerra.Adaxes.Adsi, Version= ... . The system cannot find the file specified." Other interfaces are workin as expected.

asked Jul 20, 2018 by johnsonua (390 points)
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
1 answer

When setting a default OU for new user creation, our domain does not expand. Editing users is fine, installed console is fine. Config was working before upgrade to 2018.1. Any suggestions?

asked Jul 17, 2018 by polley (1.2k points)
0 votes
1 answer

Hello, after update to 2021.1 we have problems with an old Windows 2003 domain. The service account for the domain will rapidly locked out from the Adaxes server. What we ... in 2021.1 for Managed Domain? Or how can I integrade old domains? regards Helmut

asked Mar 12, 2021 by a423385 (510 points)
0 votes
1 answer

Short Version: Issue: Found that the form\view config under /AdaxesConfig does not match what is seen on the user modify page Long version: We upgraded from 2017.1 to 2018 ... when editing a user are configured for the View Form for User in the /HelpDesk page

asked Sep 4, 2018 by jiambor (1.2k points)
2,801 questions
2,535 answers
61,659 users