An unknown error occurred (11111). Anyone have a clue what this means?!

I don't know if this is what solved it, but my HD had some issues so I had to restore from a time machine backup. The libarary was actually on a separate drive. But anyway, I haven't had this problem since restoring. So for me, it's solved.

Hi,

I'm using iTunes Match since it's been made available in my country, and today is the first time I encounter your problem, and it's very frustrating !

I've purchased the official Skyrim OST (4CD), ripped in ALAC on my Windows Computer, and iTunes Match automatically uploaded all of the files.

But when I want to download them on my iPhone or MacBook Pro (I don't want ALAC on it because I don't have a lot of space disk remaining), about 15 of the 53 songs end up with an error message and the download won't start... But I know for sure the file is on the cloud, because when I do cmd+i on it on my MacBook Pro, it says it's in AAC, the size, frequency, etc !

I didn't have this problem with previous ripped CDs.

If you have a solution I'm willing to try !

I've already tried to deactivate then reactivate iTunes Match, delete then add again the music files... Nothing worked

A neat route is to turn iTunes Match off; import the Song files to library, transcode to 256 kbps AAC, remove ALAC files, turn iTunes Match on and 'Update iTunes Match'.

But what if I want to keep my ALAC files ?

Here's my setup :

Windows computer : ALAC only (large hard drive and neat speakers)

MacBook Pro : AAC downloaded through iTunes Match

iPhone : same as MacBook Pro

So if I import directly to the MacBook Pro AAC files then update iTunes Match, won't I end up with duplicates ? Since there're already automatically transcoded ALAC files on the cloud, the ones that appear with the cloud icon but that I can't download because of the error message

To resolve, copy the local ALAC Song files that you wish to keep to a folder outside iTunes and remove the Song files from the library and iCloud - you can then complete the process above but at your discretion import the ALAC Song files to your Windows machine as you need.

Well, thank you, I'll try that as soon as I can ! (travelling with my MacBook Pro right now)

I hope this helps. I've been trolling over macrumors/apple discussions and just googleing my brains out trying to figure this issue out. Here's what I posted over at macrumors that helped me with this exact same issue. I hope this helps:

===========

***UPDATE***

===========

After a TON of experimentation I figured out a (albeit a b it tedious and annoying) workaround.

I deleted a TON of albums belonging to the same artist(s) (they were all compilation albums from the TV Show Samurai Champloo).

Well, they're ALL apple lossless, but I was able to pinpoint the problematic one. "Departure" in full Apple Lossless would not redownload from the cloud as 256 kbps VBR aac. It just refused to redownload when uploaded in ALAC.

The remedy? I made a COPY of the album in iTunes converted to AAC 256 and uploaded it first, and what do you know... I can download them. The reason I chose 256 AAC was because everything else iTunes related seems to be 256 - ALAC to iCloud and purchased tracks.

However, I hope this can help people with the problem.

As for now, I'm actually gonna try to convert them to WA or AIFF then back to ALAC and try again. I wonder if the ALAC's had something wrong with them, a bit off on every single one from the same album, corruption. I have no idea.

I'll post further results if I find that ALAC -> AIFF/WAV -> ALAC -> iTunes Match works in any way to remedy "broken" files.

=============

***UPDATE 2***

=============

-Posting results of another experiment.

ALAC -> AIFF/WAV -> ALAC -> iTunes Match (uploaded) -> Download.

This method also fails, the end result file from match cannot be downloaded. I wanted to try it because I thought maybe a new copy of ALAC from a AIFF/WAV copy of the "broken" ALAC would fix bit errors/corrupt information/bad tags.

This is very odd, but since the ALAC -> AAC -> Match (uploaded) works just fine, use that. If you must replace your ALAC in your local iTunes Library, put them back in last so when match sees them they will be considered duplicates and not try to upload/match.

Hope this helps anyone with this exact same problem.

I can confirm that this is indeed what is occuring and re-encoding as an MP3 solves the ALAC problem. I was hoping that the 10.6 upgrade would solve the problem, but alas no.😟

What's wierd is that only a small percentage of my lossless tracks have this problem and it seems quite random.

You don't have to use mp3 you know... Considering you're storing it on a practically limitless file size cloud you should go 256 or 320 AAC, it's what I did. I also found another ALAC Upload that had the problem. It's obvious the lossless files are encoded to 256 in iTunes match on apples side. I'd rather a file that has to be uploaded and lossless is encoded to an AAC on my computer before it goes out. This way I KNOW how it's being encoded and what it's being encoded with. Apples AAC encoders on the store and iTunes match are ... Different than the QT Library encoders.

I am not sure if you have an answer, but I ran into the same issue only with certain songs, I could not download to my iPad or delete and redownload to iTunes on my workstation. I fixed it with three different songs by first deleting from library on workstation but keeping the file when promted to delete the file. It still showed up in iTunes but with a cloud symbol. I then deleted again and it removed it from my iTunes list. (I assume the last step just deleted from the cloud.) I then used the "File->Add File to Library..." and browsed to the file location and then added it. It now showed up in iTunes list and I right clicked and selected "add to cloud" or something like that. iTunes then re-uploaded the song. Once complete I was able to download to my iPad where I could not before. My guess is that the original upload was corrupted on the Apple server and I had to delete it and re-upload. Let me know if this works for you.

This works in some cases, but not all. To be honest, its happening on a lot of tracks and I don't have the time or inclination to do sift through 8k + songs to resolve. I've contacted support, I hope they have a decent answer otherwise I'll not be renewing next year. £21 to access some of your music when iTunes plays ball is not acceptable to me.

I've been using Match for about 4 days and I'm already to the point that I've disabled the auto-renew because of this error. To me the whole point of Match was to take the work out of managing my collection and with this error its caused more work...

I have this problem too. I did the standard thing on my iMac, created smart playlist identifying all songs I could download at 256, deleted and downloaded everything perfectly, not a single issue. Now I'm doing the same on my Windows laptop and about 1 in 100 tracks throws up the 11111 error - and these are tracks that downloaded fine on my iMac. It's very frustrating as the modal dialog halts the entire download process, so you leave it to get stuff overnight, and find it stopped 5 minutes after you left it. Occasionally retrying a failed track it downloads ok, but most fails won't at the moment.

Is there a clean way I can move the failed tracks from my iMac to my laptop without creating duplicates? I may try a few things once I finish the automatic download and know the final list of fails. I can move the files, I just want to get iTunes to recognise properly that the file is on the laptop and not just in the cloud.

I have the same problem as described by Эdd.

It is annoying as it makes it difficult to download 1000s of tracks.

Selecting "Update iTunes Match" has fixed a couple of the dozens of problems in my library.

It seems to have occurred AFTER I deleted all my library on my Mac and then downloaded 256kbps versions from the cloud, as the 256kbps file works ok on the Mac but cannot be downloaded again from the Cloud either to my Mac or to another device.

I can therefore delete the 256kbps from the Mac library, and then put it back. It will upload and lead to a duplicate as described above. I cannot delete the file from the Cloud that is causing the problem, so my library will show 2 entries, one of which no longer has any play history data but will play, and one of which is the problem track which wont play.

It's all a bit scruffy, for a paid for service.

This has been going for almost a week. At least for me but this is on my iPhone since I removed all the music on my iphone and replaced it. It has nothing to do with the 5.1.1 ios update because I did that to my ipad and so far the music that was downloaded is still intact. However I bet if i remove it and redownload it, that this will occur again. It's great how Apple seems to take forever to acknowledge anything is wrong. It is quite clear many people are having issues that weren't having them before.