tag:blogger.com,1999:blog-5976686513564131325.post3506537079020140212..comments2024-03-17T15:34:05.492-06:00Comments on MPECS Inc. Blog: Every IT Project Manager's Nightmare: The Upgrade that Breaks ThingsPhilip Elder Cluster MVPhttp://www.blogger.com/profile/06082028960643490292noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5976686513564131325.post-55719609759379676602007-03-12T14:19:00.000-06:002007-03-12T14:19:00.000-06:00Somehow, I believe that the NETFILE system wouldn'...Somehow, I believe that the NETFILE system wouldn't be running on a Microsoft platform.<BR/><BR/>It would be likely to be a very customized, possibly in-house, product that runs on top of UNIX.<BR/><BR/>DST related? Probably. Either way, my original contention still stands, they had two (2) years to test DST related patches VIRTUALLY before ever touching a production system.<BR/><BR/>And yes, as a Canadian taxpayer, I believe we have the right to know exactly what happned to the systems, and whether any data has been compromized in the process.<BR/><BR/>Thanks for the comment!<BR/><BR/>Philip E.Philip Elder Cluster MVPhttps://www.blogger.com/profile/06082028960643490292noreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-87241825279431107442007-03-12T13:13:00.000-06:002007-03-12T13:13:00.000-06:00The "sofwtare patch" in question was likely the Mi...The "sofwtare patch" in question was likely the Microsoft Daylight Savings Time patch. Not to say its MS's fault, however, goes to show how a minor DST patch can create mass havoc. As tax-paying citizens and residents, I suggest we demand the CRA to explain exactly what went wrong, which subcontractor had overall responsibility for the NETFILE system and what risk mitigation practices have been put in place to prevent this from happening again next year.Anonymousnoreply@blogger.com