error 56, 67, 80 is not a valid value for Int32: quant analysis generate report

Hello ilefresne,

This is most probably due to a corrupted reporting method. See this community post regarding the error.

(+) Reporting all of a sudden stopped working for MH Quant 10.0 software - Forum - Mass Spectrometry Software - Agilent Community

Hello,

We have modified the Graphic settings tab and now the error is no longer displayed but the report in still not generated: it runs constantly

link?

(+) Reporting all of a sudden stopped working for MH Quant 10.0 software - Forum - Mass Spectrometry Software - Agilent Community

And here are the steps I'd recommend from that post

First close all open copies of Quant and Unknowns Analysis. Then go to the start menu, find the Agilent MassHunter Quantitative program group and then find Quantitative Analysis Tools. This will open a folder of shortcuts. One of them should be Restore User Settings. This will clear all user preferences, including window and column layouts. Run this short cut and type y to proceed.

Then I would open one of the demo data batches that shipped with Quant. I like using the TQ data for the Drugs of Abuse batch since it is small. Then make a new reporting method and use one of the default shipping template and see if the report generation is successful. 

it works, a report is generated but the progress bar keeps running, we have to stop it ourselves

ilefresne,

Does this occur for all batches and all templates/report methods?

Exactly which progress bar is getting stuck? I typically don't see one on my systems, even if I queue reports. 

Hello Howard,

Yes, for all batches

ilefresne,

I have seen corrupted Excel templates cause this issue, or perhaps a corrupted Excel addin. If this isn't an Excel template then it could be due to an issue with opening the completed file, if you have that option checked.

I have also seen similar issues if the resulting report file path is too long. You could try moving your data folder so that the complete path is shorter, say only one or two folders deep.

Unfortunately it could also be any of a number other issues with the report template, quant, or Windows. 

At this point it may be best to reach out to your local service team using the contact information here Contact Us | Agilent so they can work with you directly and help resolve the issue.

ilefresne,

I have seen corrupted Excel templates cause this issue, or perhaps a corrupted Excel addin. If this isn't an Excel template then it could be due to an issue with opening the completed file, if you have that option checked.

I have also seen similar issues if the resulting report file path is too long. You could try moving your data folder so that the complete path is shorter, say only one or two folders deep.

Unfortunately it could also be any of a number other issues with the report template, quant, or Windows. 

At this point it may be best to reach out to your local service team using the contact information here Contact Us | Agilent so they can work with you directly and help resolve the issue.

ok thank you very much for your help and your time