We have a few backend windows services written in .net framework 1.1 running and on December 31st 2008 around 5.00 pm (EST) we stopped these services to run some year end reports.After the reports were run , we tried to start the services and the moment we attempt , it would give an error "Service did not start in a timely fashion".We tried every possible things that google came up with.Service Packs , WinDbg , GFlags etc etc.
Finally we called in Microsoft support around 10.30pm(we had premium support contract with Microsoft) and they started collecting all kinds of server data and around 12.05 am (EST) the services starting successfully with no issues.We hadn't done anything different or special to get it started.The whole team was stumped as to what was happening and equally glad that it was working.
The conclusion is Microsoft support team thinks that this could very well be something to do with the .NET Framework 1.1 namepsace System.ServiceProcess.ServiceBase inability to support leap year.They havent confirmed it yet and are still investigating.
I will keep posted as and when I have updates form MSFT support.I was planning for a dreadful 2009 start but gladly it all ended fine.