Created by Salim Frontin, last modified by Alex Thottunkel on Jan 22, 2024
Purpose (problem description)

This page explains the fatal error while running the analysis and its impact.

You can find the following fatal error in your analysis log file for the corresponding analysis unit.

2016-05-19 15:30:41.754 InformationMODULMSG ; Job executionStarting analysis of C:\CASTMS\Deploy\Source Code\Source Code\File.Website\File.Website.csproj (1 / 1)0; DOTNET
2016-05-19 15:30:43.189 FataLerrorMODULMSG ; Job executionMissing mandatory reference towards mscorlib: project C:\CASTMS\Deploy\Source Code\Source Code\File.Website\File.Website.csproj will be skipped0 ; 00 0DOTNET

As you can see from the fatal error that the analysis of project File.Website.csproj is being skipped, so you will not find any corresponding objects created in your knowledge base.

Observed in CAST Extension Version


Release

Yes/No

1.0(tick) 
Observed in RDBMS

RDBMS

Yes/No

Oracle Server (tick) 
Microsoft SQL Server (tick) 
CSS3(tick) 
CSS2 (tick) 
Step by Step Scenario

Below is the step-by-step scenario leading to the problem:

  1. Package and deliver .Net application (either C# or VB)
  2. Accept and set as current version from CAST MS.
  3. Run analysis.
  4. Analysis stops with fatal error seen in the Analysis Log.
Action Plan

  1. Search in analysis log for the Project Path corresponding to the Fatal error message. For example in the below analysis log :

    2016-05-19 15:30:41.754 Information MODULMSG ; Job execution Starting analysis of C:\CASTMS\Deploy\Source Code\Source Code\File.Website\File.Website.csproj (1 / 1)
2016-05-19 15:30:43.189 Fatal Error MODULMSG ; Job execution Missing mandatory reference towards mscorlib: project C:\CASTMS\Deploy\Source Code\Source Code\File.Website\File.Website.csproj will be skipped

    the project path is C:\CASTMS\Deploy\Source Code\Source Code\File.Website\File.Website.csproj

  2. Search for an information message of Project Path (as shown below) in analysis log when you browse the analysis log messages from bottom to top:

    2016-05-19 15:30:29.906993 Information MODULMSG ; Job execution Project Path C:\CASTMS\Deploy\Source Code\Source Code\File.Website\File.Website.csproj

    If the above information message exists, the project belongs to an analysis unit automatically created by CAST MS due to a project discovered by the CAST Delivery Manager Tool. If no information message exists, then the Analysis Unit has been manually defined. For more info on Analysis Units creation see    CMS - Analysis Unit editor in CAST-MS open the Analysis Unit Editor->Analysis tab->Referenced Assemblies and check if mscorlib.dll library is in the list of referenced assemblies.

    1. If mscorlib.dll library is not in the list of referenced assemblies then:
      1. If this is a user defined analysis unit, then you should manually add the .NET assemblies in the Analysis tab Referenced Assemblies as described in CMS - .NET Technology options
      2. If this is an automatically created analysis unit, go to    CMS - Delivery tab->‘Manage the delivery’ for the Current Version. Check in .NET source packages for any missing library alerts concerning mscorlib.dll.
        1. If such alerts exist, check if a package of type ‘.NET framework (system assemblies)’ as described in page has been correctly added.
          1. If there is no such package then you should create a new package, add a package with the .NET assemblies. You can find more info on how to do this in this page
          2. If there already exists such a package then you should check whether mscorlib.dll has been discovered in this package
            1. If mscorlib.dll is missing, then the .NET assembly has not been correctly added. If you have followed all the steps described in this page, then contact CAST Technical Support. with the following Relevant input
            2. If mscorlib.dll is not missing in the .NET assembly package, then you should check the alerts of the other .NET packages for missing library files concerning mscorlib.dll file. It can be the case that the version of mscorlib.dll assembly missing is not the standard one provided by .NET framework, for instance it could be the Silverlight version of this dll. In this case you should treat the issue as a standard DMT alert issue, which means that it can be re mediated by:

        2. If no alert exists, then contact CAST Technical Support. with the following Relevant Input

    2. If mscorlib.dll library is in the list of referenced assemblies then it could be the case that the referenced paths are not correct which generally occurs during the change of deploy folder path post Migration, adding other version or change of deploy folder path in CAST-MS preferences file.

      The below solution (fixed in 8.2.5) is applicable when you deploy the packages by setting it as current version, the .net framework assembly package path does not change and remains the old one.This procedure has to be done for each 'set as current version'

        1. Deploy sources and set as current version

        2. Quit CAST-MS

        3. Run a SQL session. Configure and execute the below query where: 

          <XXX_MNGT> is the management schema name
          <ORIGINAL_PATH> is the path which has to be changed
          <NEW_PATH> is the new path
          Ensure the 2 paths are ending with '\' (folder separator) to avoid having issues with substring folder names

          update <XXX_MNGT>.cms_net_assembly_file
set assemblypath = replace(assemblypath, '<ORIGINAL_PATH>', '<NEW_PATH>')

For example: 
update test_Dotnet_810_mngt.cms_net_assembly_file
set assemblypath = replace(assemblypath, 'S:\SOURCES\DotNet\ANALYZED\MYAPP\V1\Ms_Fw_dll\', 'S:\SOURCES\DotNet\ANALYZED\MYAPP\V2\Ms_Fw_dll\')

        4. Open CAST-MS and run the analysis

  3. If you do not find the information you are looking for or solution for your problem, in this page, contact CAST Technical Support with the following Relevant input for reproduction of the issue

Notes/comments


Related Pages