Most Popular Stories
- Chrome 17's new features enhance speed, security
- Bug in Trendnet webcams exposes them to public viewing
- Spotlight: Intel launches 520 Series solid-state drive
- Apple's iPad 3 will be unveiled first week of March, says report
- Microsoft: How Windows 8 on ARM will be different
- There's no escaping the app economy
Events
- MDSL Telecom Expense Management Roadshow
Feb 21–23, 2012 — New York, Houston, Chicago - Customer Engagement Technology World
March 28-29, 2012 — San Francisco - Ready to meet the next-generation of business?
March 4-6 2012 — San Francisco, CA - CIO Summit
March 18- 21 — Miami, FL
Sponsored Links
Free Newsletter
HOT TOPICS >> The tech world's top flops and fiascos of 2011 | Top 8 features in Windows 8 | Paul's Q&As
INDUSTRY >> Healthcare IT | Government IT | Financial Services IT | Biotech IT | Compliance IT
Free Newsletter
Latest News
Popular Topics
Whitepapers
- Whitepaper: Integrated Analytics and WCM Can Improve Performance & ROI
- The E-discovery Toolbox: What you should look for in a unified e-discovery solution
- The Data Center in Your Future
- Durable Smart Devices for Mobile Field Forces: Selection and Evaluation Criteria
- CSO White Paper - Desktop Virtualization: Empowering Information Security
- IMPROVING THE MANAGEMENT OF FEDERAL GOVERNMENT IT ASSETS THROUGH BETTER COMMUNICATION WITH THE IT INDUSTRY
Leap Year bug plagues Exchange Server
In this post-Y2K era, it can be hard to believe that calendar-related bugs still are an issue. So you can imagine that IT admins the world over were surprised to discover that they were unable to install Microsoft Exchange 2007, set up new mailboxes or make various other configuration changes last Friday, all because of a Leap Year bug. The problems occurred if users started or restarted Microsoft's Exchange System Attendant service between 12 a.m. UTC on Feb. 29 and 12 a.m. UTC on March 1. Users could alleviate the problem by restarting their Exchange Server after those hours had passed--a fact that many discovered after wasting a full day trying to solve the problem. Here's hoping that Microsoft manages to sort this issue out before the next Leap Year.
For more on the Leap Year bug:
- see this InformationWeek article
Related Stories
- Java exploits reach unprecedented levels, according to Microsoft
- Large Patch Tuesday from Microsoft this month
- Microsoft clears remaining bugs after record Patch Tuesday
- Microsoft building Exchange 14 as a service first
- Microsoft has fixes planned for 2,000 Windows 7 bugs
- Four security bulletins for Patch Tuesday next week
- iPhone in the enterprise: An interview with Microsoft's Exchange group
- 2007: The year in tech
- Microsoft Office 2008 for Mac gets official
- Microsoft offers Exchange Server 2007's second beta
Home
| Subscribe | Advertise | RSS |
Privacy
| Site Map
| EditorsTHE FIERCEMARKETS NETWORKFierceEnergy | FierceSmartGrid | FierceFinance | FierceFinanceIT | FierceComplianceIT | FierceHealthcare | FierceHealthFinance | FierceHealthIT | Hospital Impact | FierceMobileHealthcare | FierceHealthPayer | FiercePracticeManagement | FierceEMR | FierceCIO | FierceCIO:TechWatch | FierceContentManagement | FierceMobileIT | FierceGovernmentIT | FierceGovernment | FierceHomelandSecurity | FierceBiotech | FierceBiotech Research | FiercePharma | FierceVaccines | FierceBiotechIT | FiercePharma Manufacturing | FierceMedicalDevices | FierceDrugDelivery | FierceIPTV | FierceOnlineVideo | FierceTelecom | FierceEnterpriseCommunications | FierceBroadbandWireless | FierceDeveloper | FierceMobileContent | FierceWireless | FierceWireless:Europe | FierceCable© 2011 FierceMarkets. All rights reserved. |
![]() |




