Le bug de l’an 2000 sur PS3 mais en 2010

Vous l’avez certainement remarqué aujourd’hui, le PSN fait buguer complètement les PS3 FAT…

L’erreur 8001050F est apparue aujourd’hui sur toutes les consoles PS3 FAT qui ont tenté de se connecter sur le PSN.  Apparemment c’est un bug provenant d’une fonctionnalité de ‘l’horloge de la ps3. Sony confirme que le problème devrait être réglé dans les 24 hrs.

D’après les dires de Sony, les ps3 slims sont épargnées. C’est quand même dingue qu’il existe encore de nos jours des bugs d’horloge. 🙂

Le message officiel de Sony concernant le bug :

As you may be aware, some customers have been unable to connect to the PlayStation Network today. This problem affects the models other than the new slim PS3.

We believe we have identified that this problem is being caused by a bug in the clock functionality incorporated in the system.

Errors include:
* The date of the PS3 system may be re-set to Jan 1, 2000.
* When the user tries to sign-in to the PlayStation Network, the following message appears on the screen; « An error has occurred. You have been signed out of PlayStation Network (8001050F) ».
* When the user tries to launch a game, the following error message appears on the screen and the trophy data may disappear; « Failed to install trophies. Please exit your game. »
* When the user tries to set the time and date of the system via the Internet, the following message appears on the screen; « The current date and time could not be obtained. (8001050F) »
* Users are not able to playback certain rental video downloaded from the PlayStation Store before the expiration date.

We hope to resolve this problem within the next 24 hours. In the meantime, if you have a model other than the new slim PS3, we advise that you do not use your PS3 system, as doing so may result in errors in some functionality, such as recording obtained trophies, and not being able to restore certain data.

As mentioned above, Please be advised that the new slim PS3 is not affected with this error. We are doing our best to resolve the issue and do apologize for any inconvenience caused.

For the latest status on this situation please check either the PlayStation blog (blog.us.playstation.com) or PlayStation.com.

Un bon fail pour Sony sur ce coup.