0 votes

Hello,

We have hybrid setup with Azure AD sync. Sometimes when creating a user, we face below warning where in user is just created on-prem and not on o365.

This is the error received: "Failed to reset password in Microsoft 365. Object reference not set to an instance of an object."

image.png

This is a random issue and happens after couple of user creations. Please let me know if there is any fix.

Thanks!

by (20 points)
0

Hello,

What version of Adaxes are you currently using? For information on how to check it, have a look at the following help article: https://www.adaxes.com/help/HowDoI.ManageService.CheckAdaxesServiceVersion.html.

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

Also, please, enable tracing of requests sent to Microsoft 365, reproduce the issue and send us the log file. For information on how to enable the tracing, have a look at the following help article: https://www.adaxes.com/help/?HowDoI.PerformO365Tasks.TraceO365Requests.html.

1 Answer

0 votes
by (220k points)

Hello,

Unfortunately, this is a known issue related to the Microsoft library used by Adaxes. The issue is not related to Adaxes itself. We will contact Microsoft regarding the issue and do necessary updates in Adaxes whenever possible.

As of now, you can try restarting Softerra Adaxes Service and manually assign Microsoft 365 licenses to a user. As per our check this fixes the issue.

0

Hello,

We released a new version of Adaxes that includes a fix for the issue. You can download it here. The fix is also included into Adaxes 2020.1 Update 5.

Upgrade instructions

What's New

0

Hello,

Thanks for the update. I have upgraded to latest version and this error is fixed.

Although I am getting a new error intermitently, which occurs at script which is run at the end of the sequence to change O365 user name.

I am getting below error: image.png

Let me know if you can help fix this one.

Thanks, Sarang

0

Hello Sarang,

According to the error message the error occurs because the account you specified for the Microsoft 365 tenant in Adaxes does not have the required permissions. It is recommended to assign either the Global administrator role or both the Exchange administrator and User administrator roles in Microsoft 365.

Related questions

0 votes
0 answers

I have been getting the following error when running the built in user creation script. This has worked fine up until about 2 months ago. As you can see Adaxes sees my ... error. The account that I am using has the correct permissions to Exchange as well.

asked Dec 9, 2020 by joshua.velez (20 points)
0 votes
1 answer

Hi all, I want to create an external Username (username-ext). Loginname is the same as the initials. Changing the intiakls -> intials-ext ... CommandPipeline.Actions.ActionBase.Execute(ICommand command) --- Ende der internen Ausnahmestapel├╝berwachung ---

asked Jun 13, 2016 by massimo.ibba (450 points)
0 votes
1 answer

I created a new interface...on the Home Page Action, it only has new user. after the fields are filled out, I get "name is not specified for the new object". Please advise.

asked Oct 18, 2013 by MeliOnTheJob (1.7k points)
0 votes
1 answer

Hi guys, I've configured a button that copy a "Template" contact object. The Template object defined in this button is not member of any distribution group, but I want ... domain in the adaxes security settings but it's still not working. Any clues? Thanks.

asked Apr 24, 2014 by Masterkic (40 points)
0 votes
1 answer

Hi When one of our admins create a user through the webinterface, the following error appears, and the user is not created: Access to the attribute is not permitted because ... is owned by the Security Accounts Manager (SAM). (Server: domain.local) Any ideas?

asked Jun 4, 2013 by kjesoo (960 points)
2,740 questions
2,474 answers
6,475 comments
1,373,581 users