Meraki failing to clear passcode on iPad

SOLVED
BishopM
Just browsing

Meraki failing to clear passcode on iPad

An iPad with iOS 15.6 accidently had a passcode set when a user picked it up after an iOS update. The Clear Passcode command is not working with the following message in the Activity Log:
 
Code: 5013
Domain: MCPasscodeErrorDomain

 

Error: The passcode cannot be cleared (-1)
 
The iPad has now not accepted any communication/commands from Meraki for the last 4 days...Any ideas on how to resolve it gratefully accepted.
1 ACCEPTED SOLUTION
PaulF
Meraki Employee
Meraki Employee

That you got the "MCPasscodeErrorDomain" response shows the Meraki SM sent the command successfully to the device, and that the device received it, but couldn't action it.

 

Getting the inability to do any further commands against the device would imply that there was a deeper issue with the device itself. Whilst brutal, resetting it appears to have been the only resolution.

 

 

View solution in original post

6 REPLIES 6
Inderdeep
Kind of a big deal
Kind of a big deal

@BishopM : Can you restart the iPad and try again ?

Regards/Inder
Cisco IT Blogs awarded in 2020 & 2021
www.thenetworkdna.com

Thanks, I've tried that, several days ago, but it hasn't made a difference.

Inderdeep
Kind of a big deal
Kind of a big deal

Did you run any other command and check if it works ?

Regards/Inder
Cisco IT Blogs awarded in 2020 & 2021
www.thenetworkdna.com

It's not responded to Meraki since 8 Aug:Screen Shot 2022-08-12 at 10.41.36 AM.png

BishopM
Just browsing

I gave it a day or 2 to see if the iPad and Meraki would resume communication... but they didn't. Ended up restoring the iPad back to a fresh build and re-enrolling into Meraki and re-installing all the apps. A lot of work to clear a passcode. Will test another iPad and see if the Meraki "Clear Passcode" feature is working at all with iOS 15.6

PaulF
Meraki Employee
Meraki Employee

That you got the "MCPasscodeErrorDomain" response shows the Meraki SM sent the command successfully to the device, and that the device received it, but couldn't action it.

 

Getting the inability to do any further commands against the device would imply that there was a deeper issue with the device itself. Whilst brutal, resetting it appears to have been the only resolution.

 

 

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels