PlayStation Network Error - PS3 Date Bug?

[admin]

Users trying to connect to the PlayStation Network on their PS3s are getting an odd "8001050F" error message, and some speculate it may have something to do with a PS3 firmware bug relating to the date.

When users start their PS3, they get an error message about not being able to connect to the PSN, and they may also find that their date has been reset back to 1st January, 2000.

Apparently, only the older "fat" PS3s are affected, PS3 Slims are still able to connect to the PSN. The problem appear to be worldwide, and it seems that most "fat" PS3 are unable to log on to the PSN at this very moment. The Internet connection on the PS3 is still active, as using the built in browser still works.

It could be just a coincidence, but February 28th has just passed, and the leap year logic in the PS3 firmware may be the cause of this connection problem.

Sony has yet to release an official response to the problem. Sony PS3 firmware problems have come under the spotlight recently when a class action lawsuit was launched claiming that buggy PS3 firmware can cripple certain PS3s.

More:

http://www.neowin.net/news/playstation-bug-cripples-quotfatquot-ps3-models-worldwide-2

[admin]

Some are also reporting that purchase/licensing data is gone, along with the date.

Luckily, the PS3 firmware update mechanism isn't tied to the PSN, so if Sony releases a fix, people should still be able to update their machines with it and fix this problem.

Unfortunately, the PS3 trophy system (which requires an active PSN connection) means that for many games, you can't even play offline until this problem is fixed.

[admin]

Problem seems to be resolved for now. It was a internal clock issue with older, fat PS3s, and it relates to the PS3 thinking 2010 was a leap year. Either Sony fixed the PSN issue on their end, or the problem went away naturally after the day past (in all time zones). Here's the official PS3 blog entry for this problem:

http://blog.us.playstation.com/2010/03/playstation-network-service-restored/

For a quick rundown on the Gregorian calendar system's use of leap years, leap years occur in years that are divisible by 4, but not in any that is divisible by 100 (except if it is divisible by 400). So 2010 is not a leap year because it isn't divisible by 4. 1900 wasn't a leap year either because it was divisible by 100 but not 400. 2000 was a leap year because it was divisible by 400. Perhaps the folks at Sony HQ can get a similar rundown to avoid future problems.