Year 2000 problem#Year 2010 problem

Year 2010 problem (also 2010 bug) refers to multiple, occurred in different computer applications at the turn of 2009/2010 software error.

Known Issues Examples

  • The widest public attention caused an error in the programming of various debit and credit cards, which made more than 30 million cards temporarily inoperable. The responsibility for this failure has taken over the Dutch company Gemalto. The problem has now been solved by an adaptation of terminals, to the effect that non- EMV chip, but the really outdated magnetic stripe was read. For bank customers resulting from the failure costs ( for example, for international transfers for travelers ) to savings banks and other banks have agreed to refund.
  • In Australia, the ATMs of Bank of Queensland were paralyzed by an error which led to today's date in 2016, making customer cards were considered " expired".
  • An error in the spam filter SpamAssassin meant that after 31 December 2009 sent mails are classified as spam. Affected the mail service GMX and 1 & 1 have included The cause was a faulty rule.
  • Short news of smartphones with the Microsoft operating system Windows Mobile 6.1 and 6.5 gave since 1 January 2010 as they are shipped out a date in 2016 to.
  • One problem there was also for users of the ERP software from SAP. When spool entries expiration date has been calculated incorrectly.
  • An error in the Endpoint Protection Manager Symantec, a security software for corporate customers, meant that virus definition updates to date in 2010 were classified as out of date.
  • The Newton PDAs Apple an integer overflow in the date calculation for data after January 5, 2010, 18:48:31 clock meant that alarm messages were repeated in an endless loop.

The year - 2010 problem occurred unexpectedly, therefore the remedy took some time to complete. In contrast, in the medial heavily escorted year 2000 problem ( " Millennium Bug" ) complications largely failed or could be resolved quickly. The reason for this should especially be predicted in advance of the New Year 1999/2000 disaster scenarios, which contributed to an elaborate preparation of the software manufacturers and users.

Causes

Storage of -year figures in BCD format

In various systems, in particular debit card, is for storing the year numbers in BCD - code is used, in which the numbers 0 to 9 are represented with four bits. The (incorrect ) reading of such a stored two-digit year ( X'10 ', binary 0001 0000 ) as a 1 -byte binary number leads to confusion between 10 and 16

12662
de