Apple Configurator 2 - 0x204 (516) & 0x2BD (701) errors

Question

beks6 Author

Level 1

12 points

Apple Configurator 2 - 0x204 (516) & 0x2BD (701) errors

Since two weeks or so we get the following error when trying to Update iOS devices with Apple Configurator 2

ConfigurationUtilityKit.error 0x2BD (701)

It says the iOS-Image is not valid.

You can "skip" this message and try an update again. The files are being downloaded but then we get an error with

NSCocoaErrorDomain – 0x204 (516)

This error says some files can't be moved to ACUDownloadFileOperation and the hint to move or rename the file. But even when you delete this file you get stuck at the same error.

We are using a MacMini for caching software. We already deleted the whole content from AssetCache folder on the MacMini but nothing changes the problem. It seems like an issue on Apple Servers.

Can someone confirm same problems or does anyone have an advice what there is left to do?

All Software is up to date!

Posted on May 2, 2018 7:24 AM

Reply

Answer 1

May 2, 2018 8:06 AM in response to beks6

We are having this issue as well. We tried two different MacBooks with fresh installs of AC2, that did not work. That leads me to believe it's either iOS related or the update services from Apple communicating with AC2.

We also completely uninstalled AC2 from the MacBook via Applications folder & ~/Library/"anything regarding AC2". That did not work. I was able to get our technician to down a new ipsw from https://ipsw.me/, and they drag and drop the ipsw download on top of the iPad in AC2 and that worked. But anytime they run "restore" or "update" it fails while "downloading" the iOS update. I replaced the existing ipsw in the AC2 downloads & firmware folder in the ~/Library/.... area and that did not work. The only working solution is drag and drop from a non Apple update service.

Reply

Answer 2

May 3, 2018 8:09 AM in response to beks6

Sorry, I should've been clearer in my original post. Yes, the iTunes can only help with one device at the time. Unfortunately, if you have multiple devices you wish to work with, you're stuck. 😟

Like Jeffmw777 said, I really hope too they fix this as soon as possible, as it's becoming a real nuisance.

Reply

Answer 3

May 3, 2018 9:52 AM in response to beks6

I think I have a workaround. Do the first restore in iTunes for one of each model. Then from that point on, Configurator will use that firmware file to update the rest. It will use iTunes' download cache first and then if it needs to, download it itself (which is the part that fails).

Reply

Answer 4

beks6 Author

Level 1

12 points

May 3, 2018 9:55 AM in response to beks6

Yes, we did the same today with one model, we‘ll try it tomorrow with different devices and maybe move the ipsw to the caching server (if necessary) so we hopefully can continue without troubles when Apple fixes this issue

Reply

Answer 5

May 10, 2018 9:36 PM in response to beks6

My option was to change the folder permissions to RW for everyone and manually downloaded the file into that directory. Thereafter it would restore ok.

Haven't tried another IOS update yet but I have noticed this is also affecting the Apple Caching server as well.

Reply

Answer 6

May 11, 2018 5:55 AM in response to ausloki69

I had the same thought about caching servers. If they are holding a corrupted iOS, then that's why our MacBooks are downloading a bad update and why this is a problem for every single campus. I don't want to flush all of our cached content but we may have to.

Reply

Answer 7

May 2, 2018 11:15 AM in response to beks6

We started getting this error about 2 weeks ago. No solution for it yet but, if someone just need to Restore, that process can still be done in iTunes, so that's lucky.

Reply

Answer 8

beks6 Author

Level 1

12 points

May 3, 2018 4:07 AM in response to servermaster

Yes, but if you have to restore minimum 10 devices at once that‘s not the way :)

Reply

Answer 9

May 3, 2018 6:11 AM in response to beks6

I have 40 devices to update so I'm hoping Apple can fix this soon.

Reply

Apple Configurator 2 - 0x204 (516) & 0x2BD (701) errors

Similar questions