When packaging assemblies, during the extraction, below warning messages are triggered :

WARNING The DLL extractor has returned an not mapped error when extracting \\...\lib\...\Newxxx.Json.dll

1. Create a ".NET assemblies on your file system" package that points to the assemblies location.
2. Package the ".NET assemblies on your file system".
3. Open the Extraction.castlog2 file

This issue occurs when the .NET extractor is not able to find the depencies between assemblies.

1. In the DMT package windows, go to the extraction step and open the Extraction.castlog2, and check the name of the dll files involved in the warning.
   
2. Check if .NET assemblies are in the delivery machine (local machine) or in the network.
   1. If the assemblies are in the network
      1. The assemblies have to be in the same folder.
      2. If the issue is still there for some assemblies, check the .NET security policy.
      3. If the security policy is very low, check the dependency.
   2. If the assemblies are in the Delivery machine
      1. Put all the assemblies in the same folder.
      2. If the issue is still there for some assemblies, check the dependency. 

This warning message occurs when the .NET extractor is not able to find the dependencies between assemblies.To make the extractor works correctly, you have to:

Check if .NET assemblies are in the delivery machine (local machine) or in the network

If the assemblies are in the network

Assemblies have to be in one folder

Put all the assemblies in the same folder, then, it will be easy for the extractor to find the dependencies.

If Issue is still there, check the security policy

If the issue is still there, check the .NET Security Policy. The .NET extractor has to open and read the assemblies. If the security policy is high, it prevents the extractor to open the assemblies, and then, to get the dependencies. If the customer needs to keep the assemblies on network, he must reduce the .NET security policy.

If Issue is still there even if the security policy is low, check the dependencies

If the security policy is already low, and the assemblies are in only one folder, check the dependencie of the assemblies triggered with the warning.

To check the dependencies, run the .NET Extractor manualy :

<?xml version='1.0' encoding='utf-8' ?>
<Assemblies>
  <ToRead>
    <Assembly path="D:\Example_of_path\location_of_the_assemblies\net40\TheAssemblytoExtract.dll">
      <ReferenceDir path="D:\Example_of_path\location_of_the_assemblies\net40\"/>
    </Assembly>
  </ToRead>
</Assemblies>

WARNING Failed to load a type from assembly ':\Example_of_path\location_of_the_assemblies\net40\Microsoft.Data.OData.dll, [Microsoft.Data.OData, Version=5.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad3
64e35]', reason: 'Could not load file or assembly 'Microsoft.Data.Edm, Version=5.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. General Exception (Exception from HRESULT: 0x80131500)'

If the assemblies are in the Delivery machine

Assemblies have to be in one folder

Put all the assemblies in the same folder, then, it will be easy for the extractor to find the dependencies.

If the Issue is still there, check the dependencies

If the assemblies are already in one folder, check the dependencie of the assemblies triggered with the warning by running the .NET extractor manually as explained in the Run the .NET extractor manually paragraph

Ticket # 5531