Problem

-- getting this error at runtime

ERROR :20180830:15.51.54.54:B2Bi PE HME 3 Task 1(pe - B2Bi HME 3 Task(map-loader.dll)):[LIB - 6004]: Error while loading shared library is : The specified module could not be found.
UNKNOWN:20180830:15.51.54.54::
ERROR :20180830:15.51.54.54:B2Bi PE HME 3 Task 1(pe - B2Bi HME 3 Task(map-loader.dll)):[LIB - 6001]: Unable to load the shared library c:\Axway\B2Bi\Integrator\local\runtime\mappingcomponent/running/Generated/MapBroker/dmlobj-5B879458ec540-02

-- the flow uses at least one mapping

Resolution

* Integrator is not able to load the dll that is supposed to be generated when the flow is deployed

* open Integrator/data/log/agent.log and broadcast.log to search for deployment problems

* among different other problems it might be [TLV - 33029] or [SFS - 3029] errors like

2018-09-05 14:54:48,432 [Thread-5 ] INFO L515 MappingBinaryRepositoryManager.writeTraceExtractedFrom - [TLV - 33029]: Unable to delete file (c:\Axway\B2Bi\Integrator\local\runtime\mappingcomponent\running\PPTY-1.bin), errno (32)

or

2018-09-05 14:54:48,432 [Thread-5 ] INFO L515 MappingBinaryRepositoryManager.writeTraceExtractedFrom - [SFS - 3029]: Unable to delete file (c:\Axway\B2Bi\Integrator\local\runtime\mappingcomponent\running\PGECl-0), errno (32)

Those errors are notalways caught by the deployment module and might lead to the error reported in the description

-> try redeploy the flow without errors

-> if it does not work, those SFS / TLV error can be caused by the size of the local\runtime\mappingcomponent\running objects; contact Axway support to get assistance