Errors Detected from Downward Compatibility

Reason:

You do not have access to the export command when running 3DEXPERIENCE to V5 File system conversion, as validated by the PLMImportExportPnOAndAttributeValuations business logic.

Possible resolution:

Contact the responsible of the business logic implementation.

Behavior:

Process of current object completely stops and DownwardCompatibility jumps to the next selected object if any. Process ends with error ReturnCode=8.

Reason:

When running 3DEXPERIENCE to V5 File system conversion, converted objects (CATPart, CATProduct, CATDrawing, model, cgr) has to be written in the conversion directory.

This error is detected when another document, which is not the result of a previous conversion of the current one, already exists in the conversion directory with similar name.

Possible resolution:

To solve this error, you may activate the 'Overwrite existing document'/'Save backUp data' in the DownwardCompatibility user interface or move/remove manually all previous documents from the conversion directory.

Behavior:

Process of current object completely stops and DownwardCompatibility jumps to the next selected object if any. Process ends with error ReturnCode=60.

Customization: Error can be demoted into Warning while exporting the environment variable :

Error_CATDWC_DocumentAlreadyExist=Warning

Reason:

When running 3DEXPERIENCE to V5 File system conversion, converted objects (CATPart, CATProduct, CATDrawing, model, cgr) has to be written in the conversion directory.

This error is detected when the document, which should be the result of a previous conversion of the current one, already exists in the conversion directory but cannot be updated because has no write access.

Possible resolution: To solve this error, you may activate the change manually the write access permission of the document conversion directory.

Behavior:

Process of current object completely stops and DownwardCompatibility jumps to the next selected object if any. Process ends with error ReturnCode=60.

Reason: When running Conversion in coexistence mode, document initially imported using FBDI/DBDI are declared "V5 master".

These imported objects should not be modified within the 3DEXPERIENCE, but they can be used within 3DEXPERIENCE and included within any structure. When Converting down to V5 such an assembly containing V5 originally imported data, these data are not re-exported on disk, but V5 original documents are loaded from disk to created the final CATProduct.

This error is detected when a V5 original document cannot be found on disk and then participate to the complete resulting CATProduct definition.

Behavior: Process of current object completely stops and DownwardCompatibility jumps to the next selected object if any. Process ends with error ReturnCode=62.

Customization:

Error can be demoted into Warning while exporting the environment variable :

Error_CATDWC_DocumentV5MasterMissing=Warning

Then, V5Master document is locally recreated starting with the 3DExperience data, and removed from disk at the end of the conversion.

Reason:The targeted CATIAV5 version defined in the input XML file for the 3DEXPERIENCE to V5 conversion is not a valid version.

Using the numerous standard 3DEXPERIENCE to V5 User Interfaces (DownwardCompatibility, XPGBatchUtility, CoexistenceBatch, Export to V5File) it is not possible to define a configuration with such an non-valid CATIAV5 version, but it is still possible using skeleton input XML file to generate this configuration.

Trying to convert any data down to a non-valid CATIAV5 version leads to this error.

Possible resolution: To solve this error, you have to change the targeted CATIAV5 version defined in the XML file to one of the supported version as follow:

CATIAV5R15, CATIAV5R16, CATIAV5R17, CATIAV5R18, CATIAV5R19, CATIAV5R20, CATIAV5R21, CATIAV5-6R2012, CATIAV5-6R2013, CATIAV5-6R2014, CATIAV5-6R2015.

Behavior:Process completely stops and ends with fatal ReturnCode=69.

Reason: Starting with V6 R2012x, it is possible to convert Part with specification down to a specific CATIAV5 level aligned with AsSpec conversion.

To learn more about compatible versions, please see File Coexistence and Migration User's Guide,Running the DownwardCompatibility Batch: Exporting Applications to Previous Versions: About Part Conversion

Using the numerous standard 3DEXPERIENCEToV5 User Interfaces (DownwardCompatibility, XPGBatchUtility, CoexistenceBatch, Export to V5File) it is not possible to define a configuration with such an unsupported set of options: [AsSpec conversion+NonAsSpec Version], but it is still possible using skeleton input XML file to generate this configuration.

Trying to convert with Specification down to a not compatible AsSpec CATIAV5 version leads to this error.

Possible Solution: To solve this error, you have to change the targeted version to the supported AsSpec version (the highest CATIA V5 version available for conversion), or switch to the AsResult conversion mode

Behavior: The process completely stops and ends with the fatal ReturnCode=70.

Reason: Starting with V6 R2012x, it is possible to convert Part with specification down to a specific CATIAV5 aligned with AsSpec conversion, if Part contains only AsSpec compatible features.

The list of compatible features is documented in File Coexistence and Migration User's Guide,Running the DownwardCompatibility Batch: Exporting Applications to Previous Versions: About Part Conversion

Behavior: The process of the current object completely stops and ends with the error ReturnCode=71.

Customization: You can demote this error into a Warning using the following environment variable:

Error_CATDWC_AsSpecIncompatibleFeature=Warning

Reason: When running 3DEXPERIENCE to V5 conversion on a Representation or a Reference in a associative mode down to any CATIAV5 level higher than CATIAVR17, an internal coexistence mapping table is used to retrieve and manage updates on the corresponding V5 documents.

This error is detected when expected information needed for associative management cannot be retrieved from the mapping table. Then, it isn't possible to convert the object in a associative mode.

This error is mainly an internal error and should not be detected. In most of the case, getting this error reveals mapping data corruption.

Behavior: The process of the current object completely stops and DownwardCompatibility jumps to the next selected object if any. The Process ends with the error ReturnCode=72.

Reason: When running 3DEXPERIENCE to V5 conversion on a Representation in a AsResult mode, some information to manage mapping between V6 feature and V5 generic naming are stored in a 'Global import' mapping information.

This error is detected when 'Global import' cannot be created or successfully updated from the mapping. Usually, an additional message informs on the feature which cannot be processed.

In most of the case, getting this error reveals a corrupted data.

Possible solution: To solve this error, you may run the CheckRepresentation batch application on the Representation to try to clean it.

Behavior: The process of the current object completely stops and DownwardCompatibility jumps to the next selected object if any. The Process ends with the error ReturnCode=73.

Reason: When running V6toV5 conversion on a Representation in a AsResult mode, some information such as ProdCont containing positioning, ..., has to be updated in the corresponding CATPart.

This error is detected when the mandatory ProdCont container cannot be retrieved in the CATPart.

In most of the case, getting this error reveals a corrupted CATPart.

To solve this error, you have to run CATDUAV5 on the CATIA V5 document to try to clean it.

Possible Solution: To solve this error, you have to run CATDUAV5 on the CATIA V5 document to try to clean it.

Behavior: The process of the current object completely stops and DownwardCompatibility jumps to the next selected object if any. The Process ends with the error ReturnCode=73.

Reason: When running 3DEXPERIENCE to V5 conversion on a Representation in a AsResult mode, some information such as ProdCont containing positioning (...) has to be recreated in the corresponding CATPart.

This error is detected when the ProdCont container cannot be created. Then, it isn't possible to recreate a valid CATIA V5 CATPart.

This error is mainly an internal error and should not be detected. In most of the case, getting this error reveals memory issue.

Behavior: The process of the current object completely stops and DownwardCompatibility jumps to the next selected object if any. The Process ends with the error ReturnCode=73.

Reason: When running 3DEXPERIENCE to V5 conversion on a Representation in a AsResult mode, some information such as ProdCont containing positioning (...) has to be updated in the corresponding CATPart.

This error is detected when the mandatory ProdCont container cannot be updated in the CATPart.

In most of the case, getting this error reveals a corrupted CATPart

Possible solution: To solve this error, you may have to run CATDUAV5 on the CATIA V5 document to try to clean it.

Behavior: The process of the current object completely stops and DownwardCompatibility jumps to the next selected object if any. The Process ends with the error ReturnCode=73.

Customization: This error can be demoted into a Warning while exporting Error_CATDWC_PartProdContUpdate=Warning environment variable.

Reason: Starting with 3DEXPERIENCE R2015xGA, it is possible to convert in AsSpec and AsResult modes any assembly containing other scales than Normal Scale down to a CATIA V5 version higher than CATIAV5R18, but all Representation under the assembly must have the same scale.

Trying to convert an assembly containing Representations of different scales leads to this fatal error.

Possible solution: To solve this error, you have to change (the root) objects to process to (to a sub assembly leading to) a set of objects of the same scale.

Behavior: The process of the current object completely stops and DownwardCompatibility jumps to the next selected object if any. The Process ends with the error ReturnCode=74.

Reason: Starting with 3DEXPERIENCE R2015xGA, it is possible to convert in AsResult mode any assembly containing other scales than Normal Scale using a StartUp CATPart of the same scale than the Representations to convert.

Trying to convert AsResult a Representation of a different scale than the StartUp CATPart leads to this fatal error.

Possible solution: To solve this error, you have to change the defined StartUp CATPart to a one with appropriate Scale.

Behavior: The process of the current object completely stops and DownwardCompatibility jumps to the next selected object if any. The Process ends with the error ReturnCode=74.

Behavior: The process of the current object completely stops and DownwardCompatibility jumps to the next selected object if any. The Process ends with the error ReturnCode=74.

Reason: When running V6toV5 conversion on a (Rep & Ref) VPLMObjects, the PLMProperties of the Objects are transferred into the Document properties of the generated CATPart & CATProduct. By Default, all properties are reported 'as is' as strings on the Document property, but behavior can be changed using the dedicated DWCPLMAttributesMappingAndPN BusinessLogic.

Any failure due to internal property incompatibility or BusinessLogic error leads to this error.

This error can be customized into a Warning to make the conversion successful but without any Properties reported on the CATDocument property.

Possible solution: To solve this error, check the BusinessLogic consistency.

Behavior: The Process of the current object completely stops and DownwardCompatibility jumps to the next selected object if any. The process ends with the error ReturnCode=76.

Customization: This error can be demoted into Warning while exporting Error_CATDWC_TransferPLMProperties=Warning environment variable.

Reason: When running 3DEXPERIENCE to V5 AsResult conversion on a Representation, it is possible to define a CATPart to use as a startup when creating a new CATPart (CATShape and CATDrawing are not in the scope of StartUp CATPart). Then any CATPart created by the DownwardCompatibility batch is initialized with the content of the startup CATPart instead of created from scratch.

This error is detected when the StartUp CATPart cannot be used for several reasons:

Behavior: The process of the current object completely stops and DownwardCompatibility jumps to the next selected object if any. The Process ends with the error ReturnCode=77.

Customization: This error can be demoted into a Warning while exporting Error_CATDWC_PartStartUpInvalid=Warning environment variable.

Reason: When running 3DEXPERIENCE to V5 conversion on a Representation in a AsResult mode, the complete representation has to be opened to be converted into the corresponding CATPart. This error is detected when the representation cannot be opened. In most of the case, getting this error reveals a corrupted Representation.

Possible resolution: To solve this error, you may run CheckRepresentation batch application on the representation to try to clean it.

Behavior: Process of current object completely stops and DownwardCompatibility jumps to the next selected object if any. Process ends with error ReturnCode=78.

Customization: Error can be demoted into Warning while exporting the environment variable: Error_CATDWC_PartOpenFailure=Warning

Then, the representation is converted AsCGR instead of AsResult.

Reason: When running 3DEXPERIENCE to V5 conversion on a (Rep & Ref) VPLMObjects, the PLMProperties of the Objects are transferred into the Document properties of the generated CATPart & CATProduct. By default, all properties are reported 'as is' as strings on the Document property, but behavior can be changed using the dedicated PLMAttributesMappingAndPN Business Logic. This will enable to define attributes (names/types/values) to be set on generated CATIAV5 document. Any failure due to PLMAttributesMappingAndPN Business Logic error when computing attribute Mapping leads to this error. In most of the case, failure is due to bad business Logic implementation, error syntax, ...

Possible resolution: To solve this error, check the Business Logic consistency.

Behavior: Process of current object completely stops and DownwardCompatibility jumps to the next selected object if any. Process ends with error ReturnCode=79.

Reason: When running 3DEXPERIENCE to V5 conversion on a (Rep & Ref) VPLMObjects, by default, the Part Number & Document Name of the generated CATPart (or CATProduct, CATDrawing), is based on Tree Mask attributes from 3DEXPERIENCE object. But this behavior can be changed using the dedicated PLMAttributesMappingAndPN Business Logic. This will help to define the string to be set as Part Number or Document Name for generated CATIAV5 Document. Any failure due to PLMAttributesMappingAndPN Business Logic error when computing PartNumber & Name leads to this error. In most of the case, failure is due to bad business Logic implementation, error syntax, ...

Possible resolution: To solve this error, check the Business Logic consistency.

Behavior: Process of current object completely stops and DownwardCompatibility jumps to the next selected object if any. Process ends with error ReturnCode=80.

Customization: Error can be demoted into Warning while exporting the environment variable : Error_CATDWC_PartNumberBLError=Warning

Then, default PartNumber and Name based on Tree-Mask attributes is applied.

Reason: When running 3DEXPERIENCE to V5 conversion on an assembly that contains multiple representations under a terminal reference, only one can be seen as the main representation. By default, a CATPart (.model or .cgr) for each representation (except 2D drawing representations) is created. Only the first CATPart of type Definition is linked to the CATProduct & others are isolated. But behavior can be changed using the dedicated CATDWCExportMainRepresentationValuation Business Logic. This will define the exact representation which will be main representation (CATPart) & others will be alternate ones (CATShapes). Any failure due to CATDWCExportMainRepresentationValuation Business Logic error leads to this error. In most of the case, failure is due to bad business Logic implementation, error syntax, ...

Possible resolution: To solve this error, check the Business Logic consistency.

Behavior: Process of current object completely stops and DownwardCompatibility jumps to the next selected object if any. Process ends with error ReturnCode=81.

Customization: Error can be demoted into Warning while exporting the environment variable :

Error_CATDWC_ MainRepBLError =Warning

Reason: When running3DEXPERIENCE to V5 conversion on a graphical Representation (cgr), a corresponding .cgr CATDocument is created .cgr CATDocument creation failure leads to this error.

Behavior: Process of current object completely stops and DownwardCompatibility jumps to the next selected object if any. Process ends with error ReturnCode=82.

Reason: It is possible to convert in AsSpec and AsResult modes any assembly created with a Academia licence down to any CATIA V5 version, but when re-exporting the data, V5 data to synchronize must be of the same type than original data. Trying to synchronize an Academia object on a standard (non Academia) CATDocument, or trying to synchronize a standard (non Academia) object on an Academia CATDocument leads to this error.

Possible resolution: To solve this error, you have to restore the initial document on disk to synchronize the document or remove the document on disk to re-create it.

Behavior: Process of current object completely stops and DownwardCompatibility jumps to the next selected object if any. Process ends with error ReturnCode=87.

Reason:

You do not have the required privileges to export some objects in session when running 3DEXPERIENCE to V5 File system conversion, as validated by the PLMImportExportPnOAndAttributeValuations business logic.

Possible resolution:

Contact the responsible of the business logic implementation.

Behavior:

Process of current object completely stops and DownwardCompatibility jumps to the next selected object if any. Process ends with error ReturnCode=97.