can not connect to iTunes says fatal unable to process request

This worked for me. I'm on iphone 5 IOS 7.

Thank you Lucy. Your advice worked for me.

But I didn't need to change password. I did a network factory reset and changed cookies to all.

And it worked.

Thank you again.

Working now! Very very disappointed that Apple neglected to comment.

i'm working now too. looks like they found the issue. thankfully before anybody noticed....

The fatal error issue is now fixed! You can now log into App Store or iTunes on your iOS device. See the update att he bottom of this article for more info http://www.maclife.com/article/news/itunes_store_users_being_kicked_out_accounts _fatal_error_updated

Folks, it is working again! Time is 2:29 EST. Don't make any changes on your end. Clearly, this was an Apple problem NOT something on our end.

Someone was asking what OS people were running. I'm running OS 10.9 on an iMac, and 7.0.4 on an iPad3 and an iPhone 5S.

Thanks to all who tweeted and blogged and posted! Let's hope it remains stable and secure!

Message was edited by: karenmom

Working!

Working for me too. I didn't have to change anything. It just started working all of a sudden.

I just got my "Thank you for notifying Apple of this issue. We are working on a resolution to this problem. You will be notified after the matter has been investigated and further information is available." email from Apple. :-)

all fixed.

Guess that reply was a little late in getting to you. Back online!

Working now

Just got a response from the tech ... they're acknowleging the problem, don't know how long it will take to fix it, and will email me (yeah, right) when its fixed.

Mario, should be working fine now. The fatal error issue is now fixed! You can now log into App Store or iTunes on your iOS device. See the update at the bottom of this article for more info http://www.maclife.com/article/news/itunes_store_users_being_kicked_out_accounts _fatal_error_updated

I reset my password, probably only an hour or so before Apple fixed it (of course). That did resolve it for me, but seriously, it's a sad day when it takes Apple (and the wealth of technical resources they have) 12+ hours to fix an issue of this significance.