Last week we encountered this error (below) on our PC running Venus 4. To fix it we did a Venus “repair”. The issue went away for a week only to appear again and cause a run crash. The trace was completely cut off and Run Control was killed.
Has anyone had this issue before? I have not seen this error “Unable to find a Dictionary Pair whose name matches…” before.
Hi @djunk
Your installation’s primary instrument configuration file is getting overwritten or otherwise being modified/corrupted in a manner that is altering required VENUS version-specific data within the file, affecting one or more instrument steps being used during runs of the affected method.
A software repair was effective as it restores all installation version-specific default files to their original state. The ML_STAR(let).cfg which maintains the affected dataset in your case is one of these files.
The most common way this type of issue is introduced is if during pkg export/import, the toggle for ‘include default Hamilton files’ is selected when importing a pkg prepared in a different version of VENUS. It is strongly recommended to not use this toggle, and leave it unchecked.
If your instrument configuration file was overwritten, it is possible other version specific files could have been affected during whichever event caused the original file modification. I would run another VENUS repair.
Thanks.
-Nick
Interesting. Thank you for the fast response. However, we have never imported a pkg file on this STAR before. We are going to try an entire reinstall. We are worried about simply trying another repair because this issue caused an entire run to crash even after the first repair.
Is there another potential root cause besides importing .pkg’s?
If it isn’t related to pkg import then I would need to review more materials to be able to make any assessment. Ideally I would need the following:
From the Hamilton\LogFilesFolder:
From the Hamilton\Config folder:
You can upload the requested files to this folder (password: Hamilton25).
Thanks.
-Nick
Hi again @NickHealy_Hamilton ,
I think the folder you send can only be used to download and I dont have the ability to upload my .pkg or traces there.
Unfortunately, this error is still happening after venus repair and reinstall.
Apologies - I updated the URL to allow for uploads. You can drop in the files now.
Thanks.
-Nick
No problem. I have uploaded the files. I also am attaching an image here of what some liquid handling (aspirate/dispense → raw hsl) steps look like in .med on this “corrupted” computer incase it contains clues into whats going wrong.
HI @djunk
Looks like there are a couple different issues here.
If method editor isn’t capable of rendering default ML_STAR instrument commands (which can be opened and edited in their respective UIs) and is resorting to displaying the original autogenerated HSL maintained in the .hsl or .hsi file, then this installation is either incomplete or corrupted. Key Windows registry entries which maintain instrument step software data required by VENUS is either missing from initial install or somehow being deleted.
For the ‘Unable to find a dictionary pair…’ error when opening method editor for the affected method also indicates corruption for ML_STAR steps programmed within the method. It looks like somehow lower level step metadata in one or more of the dependent files is also getting removed or otherwise tampered with.
Regarding the abrupt run crashes, you are describing a Windows application crash. The only way to dig further would be to review the Windows application event logs at the time of the crash and see if Run Control crashed due to an internal software component or killed with an external program.
Is the affected PC monitored by company/IT antivirus or some sort of endpoint protection? My best guess is that all signs are pointing to the contents of your Hamilton folder being corrupted/tampered with by antivirus scans. If there are scans, then the Hamilton folder and all of its contents need to be whitelisted from the antivirus so the folder is not regarded. I would inquire with your IT department.
Even if this is not the case, the VENUS installation and Windows environment of the PC is clearly unhealthy for robust operation of VENUS. I recommend sourcing a different PC or a factory Windows reset prior to any reinstallation or repair attempts.
Thanks.
-Nick
