A customer in the united states notified biomerieux of an issue associated with myla.¿the customer reported experiencing a problem with their data not crossing over to their lis system.In addition, the customer indicated they and could not launch myla and received an error message indicating service was temporarily unavailable.Biomerieux initiated troubleshooting, examination of data logs and performed a full system restore, which resolved the problem.However, the customer indicated test results were not available for two (2) days while the myla system was down.An internal biomerieux investigation will be initiated.
|
A customer in the united states notified biomérieux of an issue associated with myla® involving data not crossing over to the lis.An internal biomérieux investigation was performed.Biomérieux restored the system to a working state and with customer's agreement, took the full system backup (fsb) from13oct2016 for investigation purpose.Investigation of the fsb indicated the database engine postgresql was in error since "2016-10-12 20:02:22 gmt".The same postgresql error was reproduced in house by removing the access rights on the folder d:\programs.The investigation found that this myla® server was used under "data analytics" project managed by us subs.The customer has agreed to be a pilot site for the "data analytics" project of the us subs.Us it teams made some changes on the myla® server for project needs.One change was done on d: drive ntfs permission in order to be able to remotely download csv files extracted daily from the server.The modification done by the subs on 12oct2016 caused the myla® crash due to database engine errors.Immediate action: this modification was removed by support teams activities on 14oct2016.So the customer myla® server was recovered in the validated state.Root cause: since initial installation, myla® server was no more in a validated state, because d: drive ntfs permissions were changed for local "data analytics" project.Human error.
|