Has anyone seen this before? Nothing has changed on the batch, it simply wont let me open it. This is on our internal PCs rather than instrument PCs. This is on Masshunter version 10.2
Find maintenance, best practice, and troubleshooting articles.
Has anyone seen this before? Nothing has changed on the batch, it simply wont let me open it. This is on our internal PCs rather than instrument PCs. This is on Masshunter version 10.2
Hello AbbieMerPol ,
Were you able to resolve the issue with opening your quant batch file? As Mohammad mentioned, the error can be caused if you have some quant installations set to use audit trails and others that do not. A batch that has had audit trails enabled can be opened and saved on a data system without auditing enable, but if this is done then the batch cannot be opened again on a system with auditing enable, since the hash file would not have been updated.
Hello AbbieMerPol ,
Were you able to resolve the issue with opening your quant batch file? As Mohammad mentioned, the error can be caused if you have some quant installations set to use audit trails and others that do not. A batch that has had audit trails enabled can be opened and saved on a data system without auditing enable, but if this is done then the batch cannot be opened again on a system with auditing enable, since the hash file would not have been updated.