Anyone experienced these error codes when trying to initialise their Janus liquid handler?
MDT module load error - MDT failure: Instrument module collection - Illegal argument
Corrupted or missing storage file!
Error parsing Order Key
Just started throwing them up out of nowhere - any help would be appreciated!
Hi Tanya,
I’ve always had an issue where none of the errors are properly explained in any of the user-provided text, even the scripting advanced features documents. It’s infuriating.
My first thought was that it somehow was reconfigured to use an MDT head when there isn’t one, but I’m going to assume you have one unless mentioned otherwise.
What I would guess is that access to or the contents of some random selection of the C:\Packard\JANUS folder are inaccessible or deleted. Check user permissions and/or windows updates to see if anything changed recently regarding those permissions. If IT has a hand in updating windows or settings, they often will implement “common sense” restrictions during new updates, and preventing the native software programs from being able to access their needed files. This is especially true with Winprep, who’s files are all readily accessible, readable, and editable by anyone logged in. Because the base software is so old, it needs to be this way for the instrument to function. IT may have just restricted direct access to the C: drive to “Admins only” or something recently without warning.
If you can’t find anything restricting access there, check for recently deleted files and restore them, especially if they are within the C:\Packard\JANUS folder or sub-folders.
Other than that, the only thing I can think of is if the instrument settings removed the MDT load position somehow. The old MDT heads need a specific labware/deck position to load tips on. In the error message, the term Storage is the same term used in some of the base language to refer to labware or labware positions. If the base format of the instrument layout removed the MDT load position, or if the protocol you are using does not have an MDT load position, it may not want to initialize during a run because it thinks it doesn’t have all the pieces to use the MDT head correctly. This might be true even if you don’t end up using the MDT head at all in your protocol.
Let me know how it goes and if you have any follow ups.
Best,
Doug