Datamation takes a look at efforts by some big names in enterprise IT to clamp down on errors caused by the changeover in the calendar year. No, it’s not the fabled Y2K bug striking a decade too late: It’s “Y2K10” and some of the problems it causes could still be serious.
Remember the Y2K bug? Ten years after the original scare leading up to the year 2000, IT systems are once again facing problems due to the changing of the calendar year.
Now, the issues are stemming from the rollover to 2010 — or Y2K10, as it’s being termed. There are reports out of Germany that millions faced problems with credit and debit card access due to Y2K10 bugs.
It’s not just consumer-facing technology that has had difficulties. On the enterprise IT side, network and security software has been hit with some Y2K10-related issues as well. Fortunately, several IT vendors are already springing into action to address glitches in their products caused by the new calendar year. Among them is networking giant Cisco (NASDAQ: CSCO).
