Troubleshooting the XPDMImportExportBatch Process

You can troubleshoot the errors that occur during the XPDMImportExportBatch process. The error codes and associated messages are shown in the 3DEXPERIENCE platform Gateway Administration Console and the html report.

For more information, see 3DEXPERIENCE Native Apps User's Guide: Native Apps Common Services | Tools | Batches | Running a Batch Directly.

This page discusses:

Installation and Configuration
Gateway connectivity and Event bus handling
Infrastructure or XPDMXML handling
Warnings

Installation and Configuration


Error Code	Description	Reason	Solution
201	Unable to find a mapping context associated to this X-PDM site ID.	The Engineering Adapter for X-PDM is not configured correctly as a coexistence context is not available with the same name as X-PDM site ID(that is, the XPDM Import Project or Export Project).	Contact your local administrator. See, Identify The Exchange Channel.
203	Unable to read `fsclient-config.properties` or invalid content.	The Engineering Adapter for X-PDM is not configured correctly.	Contact your local administrator. See, Configuring fsclient-config.properties File.
206	Required license (MUX) is not available.	MUX license is not assigned to the user.	Contact your local support for the license.
207	3DEXPERIENCE platform Server is not X-PDM enabled.	The 3DEXPERIENCE platform server is not configured for X-PDM exchange, Adapter for X-PDM is not installed with Enable Engineering Exchanges.	Install XPC product ( Enable Engineering Exchanges option).
208	Input parameters combination provided is unsupported.	Input parameters combination is not compatible.	Modify the input batch XML to set correct batch parameter combination.
228	Missing UE5 license or required components.	UE5 license is not assigned.	Contact your local administrator.

Gateway connectivity and Event bus handling

Environment: On premises only


Error Code	Description	Reason	Solution
300	Failed to send the event.	Connectivity problem for Gateway. The Gateway is offline or not reachable.	Contact your local administrator.
301	Failed to connect to the file server.	Connectivity problem for file server. The file server is offline or not reachable.	Contact your local administrator.
302	Failed to upload file to the file server.	The file server setup is incorrect or file server is full.	Contact your local administrator.

Infrastructure or XPDMXML handling


Error Code	Description	Reason	Solution
303	Input object not supported.	-	Contact DS support.
304/008	Failed to retrieve input object.	-	Contact DS support.
305	Failed to complete the input object.	-	Contact DS support.
306	Attachment file creation failed.	The output directory is full.	Contact your local administrator.
307	Failed to expand the structure from input object.	Object is not supported for Expand Completion Type.	Contact DS support.
310	Output directory is not empty.	The `MetadataFile` input parameter refers to a non-empty directory.	Change `MetadataFile` input parameter.
312	Input object not supported (Drawing in Tessellated mode).	It is forbidden to export Drawing (as root object) with Tessellated option.	Select Exact option or change the root object.
315	Input XPDMXML file not found.	The `MetadataFile` input parameter refers to a non-existing file.	Change `MetadataFile` input parameter.
319	Failed to complete the input object. Invalid Expand Level.	Incorrect value of `Expand level` in Completion Type.	Contact your local administrator.
400	Failed to parse input XPDMXML file.	The XPDMXML file contains malformed XMLcontent.	Contact your local administrator.
401	Failed to create PLM Components from the input XPDMXML file.	The XPDMXML file content is invalid.	Check the report for information.
402	Failed to transfer the PLM Components to the 3DEXPERIENCE platform server.	Either of the following: The objects or attributes received in XPDMXML are invalid. The attribute mapping BusinessLogic is incorrect. The X-CAD converter set up is incorrect.	Check the report for information. Contact DS support.
403	Failed to transform the PLM components into the output XPDMXML file or fatal problem in tessellated geometry conversion.	The X-CAD converter setup is incorrect.	Check the report for information. Contact DS support.
404	Failed to transform the PLM components into the output XPDMXML file or fatal problem in exact geometry conversion.	The X-CAD converter setup is incorrect.	Check the report for information. Contact DS support.
406	Failed to transfer the ownership of the PLM components.	-	Contact DS support.
407	Failed to set the PLM components to transfer in the batch context.	-	Contact DS support.
600	Failed to introspect 3DEXPERIENCE content with CAD master.	-	Check the XPDMImportExportBatch report.

Warnings

Following listed warnings are non-fatal issues which allow a successful exchange of metadata.

Note: Though XPDMImportExportBatch process is completed with a warning, an error is shown in the XPDMImportExportBatch.htm batch report. Batch Monitor shows the information status as Failed.


Error Code	Description	Reason	Solution
1000	Geometry conversion failure during import of one or more X-CAD representations. Import is successful with blank geometries created for the conversion failures. For example, when you import a 3DShape without geometry, error code 1000 is displayed.	The X-CAD data is corrupt or converter failed to handle the data.	Check the report for information. Contact DS or converter support.
1001	Geometry conversion failure during export of one or more representations into X-CAD tessellated representations. Export is successful. There will be no File Reference in the XPDMXML file corresponding to the failed representations. The `UpdateFileMode` attribute of the Rep3D or Rep3DAggr for which conversion failed is set to `IgnoreExistingNotProvided`.	Converter failed to handle the data.	Check the report for information. Contact DS or converter support.
1002	Geometry conversion failure during export of one or more representations into X-CAD exact representations. Export is successful. There will be no File Reference in the XPDMXML file corresponding to the failed representations. The `UpdateFileMode` attribute of the Rep3D or Rep3DAggr for which conversion failed is set to `IgnoreExistingNotProvided`.	Converter failed to handle the data.	Check the report for information. Contact DS or converter support.
1003	Geometry conversion failure during export of one or more representations into CATIA exact representations. Export is successful. There will be no File Reference in the XPDMXML file corresponding to the failed representations. The `UpdateFileMode` attribute of the Rep3D or Rep3DAggr for which conversion failed is set to `IgnoreExistingNotProvided`.	Converter failed to handle the data.	Check the report for information. Contact DS or converter support.
1600	3DEXPERIENCE content with CAD master is introspected with permissible warnings.	-	Check the XPDMImportExportBatch report.