Windows Azure crashes on leap year error

 

Leaves customers cloud-less for hours.

Microsoft has confirmed that a major worldwide outage on its Windows Azure cloud service was likely caused by a leap year coding error.

The firm's corporate vice president for cloud, Bill Laing, said in a blog post that the issue was determined "to be caused by a software bug".

"While final root cause analysis is in progress, this issue appears to be due to a time calculation that was incorrect for the leap year," he said.

The outage left customers without cloud access for between 12 and 23 hours, according to various reports.

While a fix had been pushed out in a bid to resolve the error, Laing noted yesterday that "some sub-regions and customers are still experiencing issues and as a result of these issues they may be experiencing a loss of application functionality."

The sub-regions included parts of the United States and Northern Europe, according to arstechnica.

Those problems were only completely resolved early Friday morning Australian time.

Microsoft said it would provide a full post-incident report within 10 days.

Microsoft was not the only firm to suffer leap year problems. In Australia, the HICAPS health payment service suffered issues, also allegedly due to a coding error that did not account for February 29.

Copyright © iTnews.com.au . All rights reserved.


Windows Azure crashes on leap year error
 
 
 
Top Stories
The True Cost of BYOD - 2014 survey
Twelve months on from our first study, is BYOD a better proposition?
 
Photos: Unboxing the Magnus supercomputer
Pawsey's biggest beast slots into place.
 
ANZ looks to life beyond the transaction
If digital disruptors think an online payments startup could rock the big four, they’ve missed the point of why people use banks, says Patrick Maes.
 
 
Sign up to receive iTnews email bulletins
   FOLLOW US...
Latest Comments
Polls
What is delaying adoption of public cloud in your organisation?







   |   View results
Lock-in concerns
  29%
 
Application integration concerns
  3%
 
Security and compliance concerns
  27%
 
Unreliable network infrastructure
  9%
 
Data sovereignty concerns
  22%
 
Lack of stakeholder support
  3%
 
Protecting on-premise IT jobs
  4%
 
Difficulty transitioning CapEx budget into OpEx
  3%
TOTAL VOTES: 1128

Vote