KB Article #182441
Deployment error in Mapping Services console
Problem
-- When deploying a flow from MS, the following error is displayed in console:
2022-10-28 15:22:04,450|INFO |Worker-134 |importexport.logger.BasicImportLogger.info:82 - HTTP ERROR 401 Deploying MapContainer{name=Test_Map, version=1, id=ef360078-700e-4f44-9b8a-8f6de8e9d27f, shortDescription=null, longDescription=null, generatedBy=null, generationDate=2022-10-28T12:22:01.000Z, mapStages=1, directoryName=1666959721997.129187@sw2suppapp3593_cn, zipFileName=package1666959721669.zip, location=DEPLOY, deployedDate=0} to IntegratorInstance{teNodeName=sw2suppapp3593_te, nodeId=SW2SUPPAPP3593, hostName=SW2SUPPAPP3593, integratorHost=SW2SUPPAPP3593, integratorPort=8852, properties=[]} FAILED; >Check of compatibility of import failed; Deploying MapContainer{name= Test_Map, version=1, id=ef360078-700e-4f44-9b8a-8f6de8e9d27f, shortDescription=null, longDescription=null, generatedBy=null, generationDate=2022-10-28T12:22:01.000Z, mapStages=1, directoryName=1666959721997.129187@sw2suppapp3593_cn, zipFileName=package1666959721669.zip, location=DEPLOY, deployedDate=0} to IntegratorInstance{teNodeName=sw2suppapp3593_te, nodeId=SW2SUPPAPP3593, hostName=SW2SUPPAPP3593, integratorHost=SW2SUPPAPP3593, integratorPort=8852, properties=[]} FAILED; the CN log may contain additional information
URI: /deployment/import
STATUS: 401
….
An error occurred during http request processing:Integrator server failed during command execution
Resolution
* Make sure you have the same Patch level on both server and client installation.
* If the deployment package / container / flow includes a custom Tracking Object (for e.g. TO_INVOICE, BIS_INVOICE), you must consider the information below.
* The count of definition lines in the bdoc for tracking object type must start with 0 and for other types of bdocs must start with 1.
*In the bdoc to_invoice the count started at 1 (looking at the xml schema you may see order="1", order="2" ... ).
Therefore, modify the bdoc to start with 0 -> order="0", order="1" and so on.
* The modification must take place directly in the path for the BusinessDocument located in the project from the workspace.
* Restart Mapping Services and deploy with the following options:
- check Ignore date
- version = -> increase the version.
* Check in the GUI to see if it is possible to create the Map type component using the resource for BIS_INVOICE.
* Follow the specific procedure for Sentinel to update the Tracking Object: