upgrade to MH 11.1

Hello,

i upgraded my MH QUANT 10.1 to 11.1 and since then the batch.script doesn't work for me, we are using a modified component.config, do you know where the error could be? This component.config worked with all 10 versions of masshunter (10,10.1 and 10.2)

Thank you.

  • This is written in log..> [ERROR] ComponentManager: Script processing error: Compiler executable csc.exe not found.

  • Hello  ,

    I'm not aware of this error specifically in regard to Quant or MassHunter, but generally this type of error points to either a corrupted or missing Microsoft .NET framework component. Make certain both the 3.5 and 4.x versions of .NET Framework are enabled in your Windows Features section or try repairing them. 

  • Hello,

    we have latest framework 4.8 and framework 3.5 SP1, it works fine with MH 10.1.

    <?xml version="1.0" encoding="utf-8"?>
    <components>
      <defaultnamespace>Agilent.MassSpectrometry.DataAnalysis.Quantitative</defaultnamespace>
      <references>
        <reference framework="true" assembly="System.Data.dll"/>
        <reference framework="true" assembly="System.Data.DataSetExtensions.dll"/>
        <reference framework="true" assembly="System.Xml.dll"/>
        <reference framework="true" assembly="System.Web.Services.dll"/>
        <reference framework="false" assembly="Quantitation.dll"/>
        <reference framework="false" assembly="QuantUtils.dll"/>
        <reference framework="false" assembly="ScriptableInterfaces.dll"/>
        <reference framework="true" assembly="System.Linq.dll"/>
        <reference framework="true" assembly="System.Core.dll"/>
        <reference framework="true" assembly="System.Xml.Linq.dll"/>
        <reference framework="true" assembly="System.Windows.Forms.dll"/>
        <reference framework="true" assembly="System.Threading.Tasks.dll"/>
        <reference framework="true" assembly="System.Drawing.dll"/>
        <reference framework="false" assembly="C:\Program Files\Agilent\MassHunter\Workstation\Quant\bin\Als.OData.dll"/>
        <reference framework="false" assembly="C:\Program Files\Agilent\MassHunter\Workstation\Quant\bin\Microsoft.OData.Client.dll"/>
        <reference framework="false" assembly="C:\Program Files\Agilent\MassHunter\Workstation\Quant\bin\Microsoft.OData.Core.dll"/>
        <reference framework="false" assembly="C:\Program Files\Agilent\MassHunter\Workstation\Quant\bin\Microsoft.OData.Edm.dll"/>
        <reference framework="false" assembly="C:\Program Files\Agilent\MassHunter\Workstation\Quant\bin\Microsoft.Spatial.dll"/>
        <reference framework="true" assembly="System.Net.dll"/>
        <reference framework="true" assembly="System.IO.dll"/>
      </references>
      <interface name="IScriptableSample">
        <implementation assembly="CompoundMath_Script.dll">
          <script name="CompoundMath_Script.txt">
            <references>
              <reference framework="false" assembly="BatchAnalysis.dll"/>
            </references>
          </script>
        </implementation>
      </interface>
      <interface name="ICustomExpressions">
        <implementation assembly="C:\MassHunter\Scripts\Quant\IScriptable\CustomExpressions_Script.dll">
          <script name="C:\MassHunter\Scripts\Quant\IScriptable\CustomExpressions_Script.cs">
            <references>
            </references>
          </script>
        </implementation>
      </interface>
      <!--<interface name="IScriptableBatch">
        <implementation assembly="C:\MassHunter\Scripts\Quant\IScriptable\Batch_Script.dll">
          <script name="C:\MassHunter\Scripts\Quant\IScriptable\Batch_Script.txt">
            <references>
              <reference framework="false" assembly="BatchAnalysis.dll"/>
            </references>
          </script>
        </implementation>
      </interface>-->
      <interface name="IScriptableBatch">
        <implementation assembly="C:\MassHunter\Scripts\Quant\IScriptable\Batch_Script.dll">
          <script name="C:\MassHunter\Scripts\Quant\IScriptable\Batch_Script.txt">
            <references>
              <reference framework="false" assembly="BatchAnalysis.dll"/>
              <reference framework="true" assembly="System.Data.dll"/>
              <reference framework="true" assembly="System.Linq.dll"/>
              <!--<reference framework="true" assembly="System.Linq.Enumerable.dll"/>-->
              <reference framework="true" assembly="System.Data.DataSetExtensions.dll"/>
              <reference framework="true" assembly="System.Collections.dll"/>
              <reference framework="true" assembly="System.Xml.Linq.dll"/>
              <reference framework="true" assembly="System.IO.dll"/>
              <reference framework="true" assembly="System.Xml.dll"/>
              <reference framework="true" assembly="System.Core.dll"/>
              <reference framework="true" assembly="System.Threading.Tasks.dll"/>
              <reference framework="true" assembly="System.Net.dll"/>
            </references>
          </script>
        </implementation>
      </interface>
      <interface name="IScriptableOutlier" instanceName="Accuracy">
        <implementation assembly="OutlierAccuracy_Script.dll">
          <script name="OutlierAccuracy_Script.txt">
            <references>
            </references>
          </script>
        </implementation>
      </interface>
      <interface name="IScriptableSample">
        <implementation assembly="Sample_Script.dll">
          <script name="Sample_Script.txt">
            <references>
            </references>
          </script>
        </implementation>
      </interface>
      <interface name="IScriptableCompound">
        <implementation assembly="Compound_Script.dll">
          <script name="Compound_Script.txt">
            <references>
            </references>
          </script>
        </implementation>
      </interface>
      <interface name="IScriptableQuantifierIon">
        <implementation assembly="QuantifierIon_Script.dll">
          <script name="QuantifierIon_Script.txt">
            <references>
            </references>
          </script>
        </implementation>
      </interface>
      <interface name="IScriptableQualifierIon">
        <implementation assembly="QualifierIon_Script.dll">
          <script name="QualifierIon_Script.txt">
            <references>
            </references>
          </script>
        </implementation>
      </interface>
    </components>

  •  ,

    I am not familiar with those types of modifications to quant. In general, the error for not finding csc.exe means that the expected version of .NET Framework has not been found or that the installation for that version is corrupt and missing csc.exe or other necessary files. The file csc.exe should be located in C:\Windows\Microsoft.NET\Framework or \Framework64 and then the .NET version. Not all version folders will contain csc.exe.

    I would try repairing or verifying your .NET installations. Microsoft provides tools for doing this.

    If that doesn't work, then for troubleshooting purposes, I would suggest temporarily changing the Windows language to English (United States) just to rule out any issues that might cause with quant. It is unlikely, but language settings have caused unexpected issues and it should be quick enough to try and rule this out.

    Finally, I would suggest seeking assistance from whoever provided the custom .dlls and component.config.xml file. If this was provided with assistance from Agilent, then I would suggest reaching out to your local support team or the contact that provided the files. Contact Us | Agilent

  •  ,

    I should add, as always when there are unexpected errors or behavior, try running Restore User Settings from the Quant Tools program group. I'm not certain why the settings in this file would cause the issue you are seeing, but I have seen corrupted Quant settings cause any number of strange issues. 

  • We tried repair those frameworks but it give same error, like i said its working on MH 10.1 so we suspect maybe is something wrong with that 11.1 version. I will try change that language. We contact our local agilent service, but they dont have experiences with batch.script. The guy who created this, found no error. Thank you for your time.

  • is there any way I can see in the log where masshunter is looking for the csc.ex file?

  •  ,

    I'm not aware of any way to log this information from quant. I believe quant should be using the 4.x version. 

  • First of all, thank you for posting publicly, I had not noticed this interface feature of MassHunter Quant, it looks very useful.

    Were you able to get it working in 11.1?

    If you're allowed to share your "IScriptable" folder, I would be very interested in seeing an use example. I am University/Government employed in Denmark, if that helps regarding permissions. Slight smile

    I am aware it will not function fully on my machine, but csc.exe indicates some compiling failing at the initialization, and you don't seem to be referencing any internal dll, so I should get far enough that I might be able to reproduce or not, and if it doesn't fail on my machine, you can get a hint at what is wrong.

Was this helpful?