Toggle sidebar Toggle sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Apple Configurator 2 cannot sign in, error message displayed

B4U

B4U

macrumors 601
Original poster
This has started last night on my 2019 iMac running the latest available MacOS Sequoia 15.7.7.
When trying to sign in on Apple Configurator 2 version 2.20 (11B11), it gives an error message.
"The operation couldn’t be completed. (AMSErrorDomain error 100.)"

Tried searching online for the error message and did not find anything.
Anyone else encountered this before?
Screenshot 2026-06-26 at 00.21.29.png
 
Sounds like Apple messed something up again then. 😅
Thank you for confirming. 😀
 
B4U said:
When trying to sign in on Apple Configurator 2 version 2.20 (11B11), it gives an error message.
"The operation couldn’t be completed. (AMSErrorDomain error 100.)"
Click to expand...

I've been having Apple Account login problems with AC2 as well on Macs running Ventura and Sequoia. I see different error messages though (something like "Sign-in failed"). I first encountered the problem about a month ago. The most recent occurrence was yesterday.
 
  • Like
Reactions: B4U
I started Apple Configurator, it returned an error about some download, but I appeared to be signed in. I signed out to see if Apple fixed the problem and now I can't sign in again 🙂
 
  • Like
Reactions: B4U
bogdanw said:
I started Apple Configurator, it returned an error about some download, but I appeared to be signed in. I signed out to see if Apple fixed the problem and now I can't sign in again 🙂
Click to expand...
That is similar to what I was doing and got to this state too.
Already signed into the main account, signed out and sign in to sub account.
Password was correct but then got that AMSErrorDomain error pop-up.
Tried to sign in back to the main account, and encountered the same error pop-up. 😅
 
Tried an older machine with Big Sur and Configurator 2.15.1. It was already signed in, but cannot download anything.
Signed out, and tried to sign back in, got not authorized pop-up message.
This sounds like an expired certificate issue to me.
 
  • Like
Reactions: KaliYoni
Okay, last resort workaround of a workaround.
On an old Windows 10 machine with iTunes 12.6.5.3, I am able to get the apps.
But that only works if I am downloading the app from the purchased page.
When I tried to update the apps already in the Mobile Application folder, iTunes throw an error saying those apps were not downloaded from my account and refused to update.
So, I had to remove those apps from the library and go to purchased in order to download the apps.
Hence, a workaround (iTunes) of a workaround (Configurator). 🤣
 
  • Haha
Reactions: bogdanw
Apple Configurator 2.20 on Tahoe 26.5.1 and 26.5.2 gives same error. Seems to be widespread enough to rule out coincidence here...
 
  • Like
Reactions: B4U
I'm having the same problem for two weeks now. Yesterday, I had contact with Apple support who looked together with me. They are going to send it to the right team. I will update here if I've any update!
 
  • Love
Reactions: B4U
I'm having the same issue now, no all devices across few locations.
Is there a way to fix it? It's big deal🙁
 
Has anyone been able to resolve it? Still getting Auth failed on all of my devices on different macs, from different locations.
 
FYI, I called Apple back last Friday because I hadn't heard anything yet regarding the open case. Another person took a look at it and decided to escalate the issue. He messaged me on Friday evening saying he would provide an update later that day, but I think that will have to wait until tomorrow... I'll keep you posted!
 
  • Like
Reactions: B4U
shponzo said:
FYI, I called Apple back last Friday because I hadn't heard anything yet regarding the open case. Another person took a look at it and decided to escalate the issue. He messaged me on Friday evening saying he would provide an update later that day, but I think that will have to wait until tomorrow... I'll keep you posted!
Click to expand...
What did the geniuses say? 🙂
 
I just had to call them back myself. There’s no solution yet; it is now a known issue, and they said they would add me to the "general case" so it could be given higher priority. However, support advised me to look into alternative solutions as well, since this could take weeks or even months.. It was quite possible that it wouldn't be resolved until the next Apple Configurator or Mac OS X update. But surely that can't be right... 😳🤪

It’s unbelievable that a business product can be out of commission for so long.
 
  • Like
Reactions: B4U
shponzo said:
I just had to call them back myself. There’s no solution yet; it is now a known issue, and they said they would add me to the "general case" so it could be given higher priority. However, support advised me to look into alternative solutions as well, since this could take weeks or even months.. It was quite possible that it wouldn't be resolved until the next Apple Configurator or Mac OS X update. But surely that can't be right... 😳🤪

It’s unbelievable that a business product can be out of commission for so long.
Click to expand...
Hoping they can fix with macOS 15...
Otherwise, will have to continue with the workaround of the workaround.
 
I initiated an Apple case on Tuesday, June 30th (Apple captured logs with me for diagnostic purposes). Apple Support and I had a follow-up call last Thursday, but it was made much shorter since Apple knows about the issue from multiple other reports. That's all I have to add. I just wanted to write a quick "thank you" to everyone on this thread, especially B4U and the early folks, as you saved me tons of grief by confirming that it wasn't a local device or network issue.
 
  • Like
Reactions: B4U
pholowka said:
I initiated an Apple case on Tuesday, June 30th (Apple captured logs with me for diagnostic purposes). Apple Support and I had a follow-up call last Thursday, but it was made much shorter since Apple knows about the issue from multiple other reports. That's all I have to add. I just wanted to write a quick "thank you" to everyone on this thread, especially B4U and the early folks, as you saved me tons of grief by confirming that it wasn't a local device or network issue.
Click to expand...
Together, our voices are louder! 🤣
Thank you for following up with Apple.😀
 
Same issue here on multiple devices running different versions. One of them is fully up to date with macOS 15.2 and AC 2.20, so updating to the newest OS version does not work. I also opened a ticket with Apple Configurator support, but haven't received any feedback yet.

Does anyone have an update?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back