Fix for Unknown Error 13014, 13136 or 13213 While Syncing iPhone After Updating to iTunes 8.0.1

November 2009

Disclaimer

Sun	Mon	Tue	Wed	Thu	Fri	Sat
1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30

This website is not owned by, is not licensed by nor is a subsidiary of Apple Computer, Inc. Apple iPhone are trademarks of Apple Computer, Inc., registered in the U.S. and other countries. The content of this website is not supplied or reviewed by Apple Computer, Inc. All articles, images, logos and trademarks in this site are property of their respective owners. Please follow this link to read the complete disclaimer.

Apple had released iTunes 8.0.1 to improve stability and performance and also fixes a number of important bugs.

However, some users have reported persistent problems syncing their iPhones after updating to iTunes 8.0.1.

I had even suggested a workaround to fix this problem. If that hasn't helped then checkout the fix recently posted by Apple on their Support page after the jump.

Some users have reported that they are getting one of the following error messages after upgrading to iTunes 8.0.1 and connecting iPhone:

"The iPhone "iPhone name" cannot be synced. An unknown error occurred (13014)." - As seen in the screen shot below.
"The iPhone "iPhone name" cannot be synced. An unknown error occurred (13136)."
"The iPhone "iPhone name" cannot be synced. An unknown error occurred (13213). "

Apple has posted three solutions that you can try out one at a time to resolve the sync issue:

Quit and reopen iTunes. If the issue continues, then restart your computer.
Turn off Genius in iTunes in the Genius sidebar (choose View > Hide Genius Sidebar).
Quit iTunes, temporarily disable the anti-virus security software on your computer, then reopen iTunes and try to sync your device. If iTunes successfully syncs your iPhone or iPod touch, consult the anti-virus software vendor.

Are you facing this issue? Let us know if this helped or if you have figured out any other way to fix this issue.

[via Apple Support]

Follow this blog