Skyline is trying to find the following DLLs:
Thermo.TNG.MethodXMLFactory.dll
Thermo.TNG.MethodXMLInterface.dll
One way around this is to find these DLLs on your system and put them in the following location relative to your Skyline.exe or SkylineDaily.exe:
Method\Thermo\BuildThermoMethod
I suspect that the failure is coming from the older versions of these DLLs that we release with Skyline, which at least gives us some hope of working even if we can't figure out where these DLLs live on your machine.
The current code for finding them doesn't us an instrument name:
using (var tngKey = Registry.LocalMachine.OpenSubKey(@"SOFTWARE\Wow6432Node\Thermo Instruments\TNG"))
using (var machineKey = GetFirstSubKey(tngKey))
using (var versionKey = GetFirstSubKey(machineKey))
{
if (versionKey == null)
return null;
var valueObject = versionKey.GetValue(@"ProgramPath");
if (valueObject == null)
return null;
return valueObject.ToString();
}
It just looks at the first sub-key of TNG and then the first sub-key of that key, and then the value ProgramPath in there. From the screenshot you have provided that would be the TSQAltisPlus\3.4 key. Does the 3.4 key contain a value "ProgramPath"? If so, does the path it contains point to a folder that contains the DLLs listed above?
Skyline is trying to find your updated versions of these DLLs and use them, but it seems to be failing and then the older versions it has complain about not finding what they expect in your registry.
You can bypass all of this by copying your updated versions of those DLLs yourself. You can use the directions on finding Skyline.exe here:
https://skyline.ms/install_recover.url
And then just search for one of the DLLs above. Once you find them, just replace them with the ones installed for your instrument.
If you can provide us with any updated information on how to find a path to these files in your registry that might help us improve the code that looks for them.