|
CAA_0502 |
|
Source:
"container name" CAA Container failed to migrate links. |
| Description: The update of the links of a CAA Container failed. |
|
Workaround:
None
|
|
CAA_0503 |
|
Source:
"container name" Error during the remove of the container. |
| Description: The CAA container failed to be removed. |
|
Workaround:
None
|
|
CAA_0504 |
|
Source:
"container name" Error in the content of XML file for CAA support.
This container has already an implementation. |
| Description: The XML file declares that the migration of a container is already defined.
This could be a internal DS container. |
|
Workaround:
You probably should not declare this container in the CAA XML file. |
|
CAA_0505 |
|
Source:
"container name" Error in the content of XML file for CAA support.
This Mode is not supported for CATProduct document. mode = "defined
mode". |
| Description: A CAA container in a CATProduct cannot be migrated. |
|
Workaround:
You can define this container to be removed in the CAA XML files. |
|
CAA_0506 |
|
Source:
"container name" Error in the content of XML file for CAA support.
This Mode is not supported for CATPart or CATDrawing document. mode
= "defined mode". |
| Description: A CAA container in a CATPart or a CATDrawing cannot be migrated. |
|
Workaround:
You can define this container to be removed in the CAA XML files. |
|
CAA_0507 |
|
Source:
"container name" Error in the content of XML file for CAA support.
This kind of document is not supported. docType = "defined doc
type". |
| Description: CAA container can only be defined in CATPart, CATDrawing or
CATProduct files. |
|
Workaround:
None |
|
CAA_0508 |
|
Source:
"container name" Error in the content of XML file for CAA support.
A container is declared 2 times with a different TargetRep or a
different RepId attribute. docType = "defined doc type". |
| Description: A CAA container cannot be declared with different attributes at the
same time for one kind of document. |
|
Workaround:
Remove one of the conflicting declaration in the CAA XML files. |
|
CAA_0509 |
|
Source:
The folder defined for the CAA XML files can not be found. |
| Description: The folder defined in Tools / Options for the migration of the CAA
data does not exist.
|
|
Workaround:
Change the directory to an existing one or deactivate the migration
of CAA data in Tools / Options. |
|
CAA_0510 |
|
Source:
"document name" Error in the syntax of XML file for CAA support. |
| Description: The given XML file has a wrong syntax. |
|
Workaround:
Correct the syntax of the XML file to respect the DTD. |
|
CAA_0511 |
|
Source:
No folder is defined for CAA XML files in Tools/Options. |
| Description: No folder is defined for CAA XML files in Tools/Options.
|
|
Workaround:
Define the directory to an existing one or deactivate the migration
of CAA data in Tools / Options. |
|
CAA_0512 |
|
Source:
"feature name" Error in the content of XML file for CAA support. An
old attribute of this feature is declared 2 times with a different
new attribute.
|
| Description: There is an error in the content of the CAA XML files. An old
attribute appears two times mapped with different new attributes. |
|
Workaround:
Remove or correct one of the two declarations. |
|
CAA_0513 |
|
Source:
"container name" Error in the content of XML file for CAA support.
This kind of Representation Reference is not supported. |
| Description: CAA container can only be migrated into a Technological
Representation or a 3DShape.
|
|
Workaround:
None |
|
CAA_0514 |
|
Source:
XML files CAA XML file content has been changed during session. |
| Description: CAA XML file content has been changed during session. |
|
Workaround:
Restart the session to take CAA support changes into account. |
|
CAA_0515 |
|
Source:
XML files CAA support has been enabled or disabled during session. |
| Description: CAA support has been enabled or disabled during session. |
|
Workaround:
Restart the session to take CAA support changes into account. |
|
CAA_0518 |
|
Source:
"container name" Error in the content of XML file for CAA support A
container is declared 2 times with a different Mode. |
| Description: A CAA container cannot be declared to be imported "As Is" and Removed
at the same time for one kind of document. |
|
Workaround:
Remove one of the conflicting declaration in the CAA XML files. |
|
CAA_0531 |
|
Source:
"aggregating feature name" CAA Container check failed. Container owns
a feature aggregating an other feature that is not required to be
migrated into the same Rep Ref. |
| Description: Migration of aggregated feature leads to invalid
inter-representation link. |
|
Workaround:
Define the same target Representation for aggregated feature as for
aggregating feature. |
|
CAA_0532 |
|
Source:
"extended feature name" CAA Container check failed Container owns a
feature extended by an other feature that is not required to be
migrated into the same Rep Ref. |
| Description: Migration of extended feature leads to invalid inter-representation
link. |
|
Workaround:
Define the same target Representation for Extended feature as for
Base feature. |
|
CAA_0533 |
|
Source:
"Mechanical feature name" CAA Container check failed. Container owns
a Mechanical feature and is not required to be migrated into a
3DShape. |
| Description: "Mechanical feature" should be migrated in 3D Shape. |
|
Workaround:
Define 3D Shape as target Representation in the CAA XML files for
container owning this Mechanical feature. |
|
CAA_0534 |
|
Source:
"pointing feature name" CAA Container check failed. Feature is
pointing by tk_specobject link to another feature that does not
belong to the same Rep Ref. |
| Description: Migration of feature leads to invalid inter-representation link. |
|
Workaround:
Define the same target Representation for pointing and pointed
features. |
|
CAA_1501 |
|
Source:
CAA Container cannot be migrated. |
| Description: Error during Import when checking input documents. |
|
Workaround:
See related error(s) for further information about import failure. |
|
CAA_1502 |
|
Source:
CAA Container failed to declare PLM Entities. |
| Description: Error during Import when declaring PLM Entities. |
|
Workaround:
See related error(s) for further information about import failure. |
|
CAA_1503 |
|
Source:
CAA Container failed to migrate PLM Entities. |
| Description: Error during Import when migrating PLM Entities. |
|
Workaround:
See related error(s) for further information about import failure. |
|
CAA_1504 |
|
Source:
CAA Container failed to migrate links. |
| Description: Error during Import when migrating links. |
|
Workaround:
See related error(s) for further information about import failure. |
|
CAA_1505 |
|
Source:
Error in analysis of XML files for CAA support. |
| Description: Error during Import when parsing XML file(s). |
|
Workaround:
See related error(s) for further information about import failure. |
|
CAA_1506 |
|
Source:
Container cannot be migrated. |
| Description: Error during Import when checking input documents. |
|
Workaround:
See related error(s) for further information about import failure. |
|
CAA_1507 |
|
Source:
CAA Container failed to declare PLM Entities. |
| Description: Error during Import when declaring PLM Entities. |
|
Workaround:
See related error(s) for further information about import failure. |
|
CAA_1508 |
|
Source:
CAA Container failed to migrate PLM Entities. |
| Description: Error during Import when declaring PLM Entities. |
|
Workaround:
See related error(s) for further information about import failure. |
|
CAA_1509 |
|
Source:
CAA Container failed to migrate links. |
| Description: Error during Import when migrating PLM Entities. |
|
Workaround:
See related error(s) for further information about import failure. |
|
INFRA_0101
|
|
Source:
Contextual Link.
The document "doc name" is pointed but does not belong to the list of imported files. It's probably a root of one of the selected files. It must be selected, or the link removed to be able to successfully import these files. The document "doc name" is pointed but does not belong to the list of imported files. A document with same name is present, but the path is different. It should be possible to succeed by deactivating the option "Folder of the link". The document "doc name" is pointed but does not belong to the list of imported files. No suitable reason found. |
| Description: A contextual link element cannot retrieve its context.
|
|
Workaround:
Deactivate the Folder of the link option.
Define a new context using the command Define contextual
links or isolate this broken external reference before
importing.
|
|
INFRA_0106 |
|
Source: Not supported Publication type.
Creation of port "port name" has failed.
Reroute the original Publication on the same geometrical element
through the Publication window before importing. |
| Description: Publication was badly generated in CATIA V5.
|
|
Workaround:
Reroute the original publication on the same geometrical element through 'Publication' dialog box before importing.
|
|
INFRA_0110 |
|
Source: Invalid character found in the name of the document |
| Description: Some characters are not supported, such as: ?
|
|
Workaround:
Remove the invalid characters from the document name. |
|
INFRA_0302 |
|
Source: Failed to open document. Document can not be read. It is possible to ignore it thanks to extensions filter. This filter is available in FBDI settings panel (Extensions to ignore). |
| Description: This type of document is not supported by FBDI. |
|
Workaround:
You can filter this kind of document (Tools/Options/General/File Base Design Import/FBDI General/Extensions to ignore). You can also isolate the link on this document from the CATIA V5 Edit links or remove the data pointing this document in CATIA V5. |
|
INFRA_0303 |
|
Source: "Document type"
This document cannot be imported as its type is not supported. |
| Description: This type of document is not supported by FBDI. |
|
Workaround:
You can filter this kind of document (Tools/Options/General/File Base Design Import/FBDI General/Extensions to ignore). You can also isolate the link on this document from the CATIA V5 Edit links or remove the data pointing this document in CATIA V5. |
|
INFRA_0304 |
|
Source: Error during the save.
Error trying to save data imported with FBDI.
And potentially:
Cannot create the component because its identifier set is already
used for an other component.
Choose other identifiers. |
| Description: This message means that the last stage of the asynchronous
operation failed. Data are not saved and the result of the
migration is lost.
|
Workaround:
If the error is coming from a problem with the identifier set,
there are two possibilities:
- Change the CATIA V5 Part Number or another property mapped with a
CATIA V6 Attribute in the identifier set.
- Change the prefix for the import in PLM Access > Creation Preferences.
|
|
INFRA_0307 |
|
Source: Error to create the DMT.
|
| Description: The Document Mapping Table creation failed. |
|
Workaround: None |
|
INFRA_0308 |
|
Source: NON Fixable Error: Error Name.
Clean data at CATIA V5 level.
Container Container Name.
|
| Description: Error detected on data but it was not possible to correct the
problem.
|
|
Workaround: The user has to correct the problem in CATIA V5, using the CATDUA
V5 tool on the corresponding error. |
|
INFRA_0310 |
|
Source: Data Integrity Checks.
|
| Description: Data integrity check fails.
|
|
Workaround: Use CATDUA in CATIA V5. |
|
INFRA_0311 |
|
Source: Data partially imported. Save cannot be performed.
|
| Description: The structure of one link at least is not V6 compliant. |
|
Workaround: Use CATDUA in CATIA V5. |
|
INFRA_0312 |
|
Source: The current environment cannot be used to import data in the
modeler: ModelerName. Select an other environment and retry the import.
|
| Description: The current environment does not support the creation of data for an application. |
|
Workaround: Use an other environment.
|
|
INFRA_0313 |
|
Source: This document cannot be imported.
It is logged as V6 Master.
It comes from CATIA V6 and was modified in CATIA V5.
|
| Description: This document can't be imported. It is logged as V6 Master. It comes from CATIA V6 and was modified in CATIA V5. |
|
Workaround: Re-export this document using CATDWC or retrieve the original exported document. |
|
INFRA_0320 |
|
Source: "Document Pathname" document cannot be migrated. |
| Description: This type of document is not supported by FBDI. |
|
Workaround: You can filter this kind of document (Tools/Options/General/File Base Design Import/FBDI General/Extensions to ignore). You can also isolate the link on this document from the CATIA V5 Edit links or remove the data pointing this document in CATIA V5. |
|
INFRA_0321 |
|
Source: Wrong mapping context for a CATIA V6 file. Current file has first been created on CATIA V6 session. However it is not referenced in the current mapping environment. It cannot be processed by FBDI. |
| Description: This file coming from CATDWC can't be imported with FBDI. |
|
Workaround: To import the other files, use the same mapping context as the one used to export this file. |
|
INFRA_0405 |
|
Source: It is not possible to order the files to import.
|
| Description: It can be due to a cycle in the links of the files. |
|
Workaround: None |
|
INFRA_0406 |
|
Source: "document pathname" has unresolved link to: "not found document
Id".
|
| Description: The pointing document is missing.
|
|
Workaround: Use the Isolate option or Remove the link to this document in CATIA V5. |
|
INFRA_0408 |
|
Source: Unavailable document. Following pointed document is missing on disk. "Pointed Document Id". It is however possible to isolate it by activating Isolation Link option. |
| Description: The pointing document is missing and the link can be isolated. |
|
Workaround: Use the Isolate option or Remove the link to this document in CATIA V5.
|
|
INFRA_0409 |
|
Source: Unavailable document. Following pointed document is missing on disk. "Pointed Document Id". Its link can not be isolated. |
| Description: The pointing document is missing but the link can't be isolated. |
|
Workaround: Remove the link to this document in CATIA V5.
|
|
INFRA_0412 |
|
Source: It is not possible to group files and order them into import packages. |
| Description: Due to links configuration, no package could be defined for the split import. |
|
Workaround: Reduce the number of documents to order. |
|
INFRA_0413 |
|
Source: It is not possible to import this package. |
| Description: The import of this package did not succeed during its migration. |
|
Workaround: Reduce the number of documents to order. |
|
INFRA_0414 |
|
Source: A process could not run. |
| Description: It was not possible to monitor the import processes. |
|
Workaround: Reduce the number of documents to order. |
|
INFRA_0415 |
|
Source: This document could not be migrated because of a pointed document in error. The filepath of the pointed document in error is "Pathname of File". This pointed document belongs to an other package in failure or has itself a prerequisite document from an other package in failure. |
| Description: Nothing can be imported. |
|
Workaround: Look for the pointed document result.
|
|
INFRA_0416 |
|
Source: Nothing can be imported.
|
| Description: All the pointed documents failed to be imported, so nothing can be
imported. |
|
Workaround: Look for the pointed document result.
|
|
INFRA_0417 |
|
Source: In Replace Mode a document is missing to perform the import. |
| Description: In order to import (update mode) the selected documents, you need to add the one displayed in error message. |
|
Workaround: Add the document displayed in error window in the selected documents list. |
|
INFRA_0418 |
|
Source: In Replace Mode a selected document is too old to be imported. |
| Description: The selected document has already been migrated with a most recent file version. So it won't be updated with this previous file version. As there is a Pre Req on this document from another one to be updated, the import is not possible. |
|
Workaround: In order to import current selected documents, add the most recent version of the document in the selected document list. |
|
INFRA_0423 |
|
Source: At least one of these files cannot be used to define a package import. "List of files". |
| Description: The selected files can not be imported. |
|
Workaround: Reduce the number of documents to order. |
|
INFRA_0424 |
|
Source: Cycle detected in the links between the document "List of documents in the cycle"
|
| Description: The document in the list point each other in a cycle. |
|
Workaround: Remove links between at least 2 documents of the list in CATIA V5 to remove the cycle and try again the import. |
|
INFRA_0602 |
|
Source: This kind of CATfct file cannot be imported. |
| Description: Only some CATfct can be imported through FBDI.
|
|
Workaround: None |
|
INFRA_1102 |
|
Source: container name. This container refuses migration.
|
| Description: No implementation for this type of container.
|
|
Workaround: None
|
|
INFRA_1103 |
|
Source: Publication Element named "publication name" of type Publication could not be migrated. |
| Description: Error in the migration of this publication.
|
|
Workaround: Remove the publication in CATIA V5 |
|
INFRA_1107 |
|
Source: Business Logic is not valid.
|
| Description: See details on the error to understand the problem that occured durong the Business Logic execution. |
|
Workaround: Contact the responsible of the Business Logic implementation.
|
|
INFRA_1108 |
|
Source: Import Export Business Logic is not valid. Import Export Business logic can not be parsed. |
| Description: See details on the error to understand the problem that occured durong the Business Logic execution. |
|
Workaround: Contact the responsible of the Business Logic implementation.
|
|
INFRA_1109 |
|
Source: PLM Component creation failed. |
| Description: The creation of a Product component failed. |
|
Workaround: Contact the responsible of the Business Logic implementation. |
|
INFRA_1110 |
|
Source: Modification of Attributes of the identifier set is not possible. The value of the attribute "Attribute Name" on the object of type "Component Type" can't be modified. The value was not modified. Contact your administrator. |
| Description:The Business Logic try to modify an attribute of the identifier set. This operation is not valid. |
|
Workaround: Contact the responsible of the Business Logic implementation. |
|
INFRA_1111 |
|
Source: No attribute has been modified by Business Logic. No attribute has been modified for the object of type : "Object type". |
| Description: The Business Logic did not modify any attribute. |
|
Workaround: Contact the responsible of the Business Logic implementation. |
|
INFRA_1300 |
|
Source: One error occured during import. |
| Description: Internal Error.
|
|
Workaround: None
|
|
INFRA_1301 |
|
Source: Affect PLMId. A PLMId is being affected twice. |
| Description: The document can not be imported but the cause is not identified. |
|
Workaround: None
|
|
INFRA_1302 |
|
Source: "type of the document". This Document refuses migration. |
| Description: The document can not be imported but the cause is not identified. |
|
Workaround: None
|
|
INFRA_1303 |
|
Source: type of the document. This Document failed to declare PLM Entities. |
| Description: The document cannot be imported but the cause is not identified. |
|
Workaround: None
|
|
INFRA_1304 |
|
Source: This document failed to migrate. |
| Description: The document cannot be imported but the cause is not identified. |
|
Workaround: None |
|
INFRA_1305 |
|
Source: This document refuses the migration.
|
| Description: The document cannot be imported but the cause is not identified. |
|
Workaround: None
|
|
INFRA_1306 |
|
Source: Unable to create a Representation Reference for this file. |
| Description: The document can not be imported but the cause is not identified. |
|
Workaround: None
|
|
INFRA_1307 |
|
Source: This document failed to declare the PLM entities. |
| Description: The document can not be imported but the cause is not identified. |
|
Workaround: None
|
|
INFRA_1308 |
|
Source: This document failed to migrate links. |
| Description: The document cannot be imported but the cause is not identified. |
|
Workaround: None
|
|
INFRA_1309 |
|
Source: This document failed to migrate entities. |
| Description: The document cannot be imported but the cause is not identified. |
|
Workaround: None
|
|
INFRA_1313 |
|
Source: An error occurred during the deletion of the old data.
|
| Description: The document cannot be imported but the cause is not identified. |
|
Workaround: None
|
|
INFRA_1314 |
|
Source: An error loading the document globally.
|
| Description: The document cannot be imported but the cause is not identified. |
|
Workaround: None
|
|
INFRA_1315 |
|
Source: Error cleaning a V4 model file.
|
| Description: The document cannot be imported but the cause is not identified. |
|
Workaround: None
|
|
INFRA_1316 |
|
Source: Error during mapping tables saving. |
| Description: Internal error |
|
Workaround: None
|
|
INFRA_1317 |
|
Source: A problem occured on design tables. Some design tables have not
been saved. |
| Description: Design tables were not correctly imported.
|
|
Workaround: None |
|
INFRA_1318 |
|
Source: An error occured during mapping tables loading
. |
| Description: Internal error |
|
Workaround: None |
|
INFRA_1319 |
|
Source: Failed to open document. Error while reading the document. |
| Description: Some details could explain the origine of the problem.
|
|
Workaround: None |
|
INFRA_1320 |
|
Source: Error during the update process. Some data to update are already in
session. Close them before doing FBDI. |
| Description: This command cannot work on data already in session. |
|
Workaround: Close all your editors and start the command again. |
|
INFRA_1321 |
|
Source: Error during the update process. Cannot retrieve previously migrated
data. |
| Description: The mapping informations can't be retrieved. |
|
Workaround: None |
|
INFRA_1322 |
|
Source: Error during the update process.
Some V6 components resulting from a previous Import cannot be
reloaded. |
| Description: The components from the previous import can't be loaded. They could
have been removed, or the P&O could prevent the current user to
load them.
|
|
Workaround: None for removed components. Try another user for P&O problem.
|
|
INFRA_1323 |
|
Source: Error during the update process. It was not possible to remove some
data. |
| Description: Internal error |
|
Workaround: None |
|
INFRA_1325 |
|
Source: The case of the file on the disk does not correspond to the case of the file pointed from the other documents. The FBDI of the file is not possible: "Doc Pathname". You can use the V5 command "Send to" for this file and the documents pointing it to restore the cohesion. |
| Description: The case of the name of the file was modified since the save of the
data. This situation is not supported by FBDI.
|
|
Workaround: Use the "Send to" or "Save as" command in V5. |
|
INFRA_1326 |
|
Source: Failed to open document. |
| Description: Give details on the open error.
|
|
Workaround: None
|
|
INFRA_1327 |
|
Source: Update of mapping failed after creation of new versions. |
| Description: New useless versions have been created and should be deleted.
|
|
Workaround: None |
|
INFRA_1328 |
|
Source: The mapping failled to be saved after the creation of the new versions. The new versions of the components that were created should be deleted. |
| Description: The new versions of the components that were created should be deleted. |
|
Workaround: Delete the objects created by the versioing operation. |
|
INFRA_1329 |
|
Source: An unknown error occured during conversion of the V5 stream. |
| Description: Internal Error |
|
Workaround: None |
|
INFRA_1330 |
|
Source: One error occured during import. |
| Description: Internal Error |
|
Workaround: None |
|
INFRA_1331 |
|
Source: An unknown error occured during the analyse of the list of representations to import. |
| Description: Internal Error |
|
Workaround: None |
|
INFRA_1332 |
|
Source: An unknown error occured during the completetion of the list of the representations to import. |
| Description: Internal Error |
|
Workaround: None |
|
INFRA_1333 |
|
Source: One error occured during computation of document list. |
| Description: Internal Error |
|
Workaround: None |
|
INFRA_1334 |
|
Source: Fail to compute the import mode for this document. |
| Description: Internal Error |
|
Workaround: For the non CATIA document, you can exclude the type of document in the options.
|
|
INFRA_1335 |
|
Source: Unexpected Error. Update scenario may not work properly on the imported data. |
| Description: SaveMapping fails (DBDI only) |
|
Workaround: None |
|
INFRA_1402 |
|
Source: An error occurred during contextual links redirection. Contextual part is: "Document name". Element Name is: "Element name". Contextual assembly is: "Document name" |
| Description: The contextual link import failed. |
|
Workaround: Isolate contextual link in CATIA V5. |
|
INFRA_1403 |
|
Source: pathname of the document. Document cannot be read because it has been created with a too
recent version of CATIA V5.
|
| Description: Document coming from a CATIA V5 version not yet supported.
|
|
Workaround: Use a more recent version of CATIA V6.
|
|
INFRA_1404 |
|
Source: Document cannot be read because it has been created with a too
recent version of CATIA V5.
|
| Description: CGR document coming from a CATIA V5 version not yet supported. |
|
Workaround: Use a more recent version of CATIA V6.
|
|
INFRA_1405 |
|
Source: The import of document from http/https link is not supported.
|
| Description: The selection of a file pointed through http or https is not supported. |
|
Workaround: Select the file by using a supported file system.
|
|
INFRA_1406 |
|
Source: An upward link hasn't been correctly converted.
|
| Description: Internal Error. |
|
Workaround: None |
|
INFRA_1601 |
|
Source: application name. Fail in is migrable. |
| Description: Internal error |
|
Workaround: None |
|
INFRA_1602 |
|
Source: Unknown. Fail in is migrable. |
| Description: internal error |
|
Workaround: None |
|
INFRA_1603 |
|
Source: application name. Fail to declare PLM entities.
|
| Description: Internal error |
|
Workaround: None |
|
INFRA_1604 |
|
Source: application name.Fail to declare PLM entities.
|
| Description: Internal error |
|
Workaround: None |
|
INFRA_1605 |
|
Source: application name. Fail to migrate entities. |
| Description: Internal error |
|
Workaround: None
|
|
INFRA_1606 |
|
Source: Unknown.
Fail to migrate entities.
|
| Description: Internal error |
|
Workaround: None
|
|
INFRA_1607 |
|
Source: application name. Fail to migrate links.
|
| Description: Internal error
|
|
Workaround: None
|
|
INFRA_1608 |
|
Source: Unknown.
Fail to migrate links.
|
| Description: Internal error |
|
Workaround: None |
|
Warning CAA_0535 |
|
Source: "container name" CAA Container check failed. Container already
exists with the same UserId in the same document. |
| Description: Several containers with same UserId are found in document. This is
tolerated but may reveal a strange modelization. |
|
Workaround: None |
|
Warning CAA_0536 |
|
Source: "feature name" CAA Container check warning. Feature will not be
migrated because its parent feature (aggregating / base feature) is
removed. |
| Description: No migration of parent feature leads to no migration of child features. |
|
Workaround: None |
|
Warning INFRA_4101 |
|
Source: Multi-representation not supported. |
| Description: Import of CATPart with multiple representations is not yet
supported. Default representation only has been imported. |
|
Workaround: None
|
|
Warning INFRA_4103 |
|
Source: Not supported publication type. Publications located in CATProduct document pointing to parameter located in CATPart document are not supported. The port "port name" has been created empty. |
| Description: Publications located in CATProduct document pointing to parameter
located in CATPart document are not supported. |
|
Workaround: None |
|
Warning INFRA_4105 |
|
Source: Publication name not modified. The publication name was changed in V5 since the first import. The name of the corresponding V6 publication is not modified. Original publication name is "Publication name from first import". The publication new name "Publication name" is not taking into account. |
| Description: The publications cannot be renamed in V6. |
|
Workaround: None |
|
Warning INFRA_4106 |
|
Source: Publication 'nameOfPub' could not be declared. Entities declaration has failed. Entities migration was skipped. Links migration was skipped. |
| Description: An unexpected error occured during the PLM entities declaration of a publication. Therefore,its PLM entities declaration and migration will be skipped by the FBDI engine. |
|
Workaround: None |
|
Warning INFRA_4107 |
|
Source: Product reference 'nameOfRef' could not be declared.
Entities migration was skipped. |
| Description: An error occured during the entities declation of a product
reference. The reference will not be migrated.
|
|
Workaround: None |
|
Warning INFRA_4108 |
|
Source: Publication 'nameOfPub' could not be migrated. Entities migration has failed. Links migration was skipped. |
| Description: An unexpected error occured during the PLM entities migration of a publication. Therefore,its migration will be skipped by the FBDI engine. |
|
Workaround: None |
|
Warning INFRA_4109 |
|
Source: Product instance 'nameOfInstance' could not be declared. Entities migration was skipped. |
| Description: An error occured during the entities declation of a product instance The instance will not be migrated. |
|
Workaround: None |
|
Warning INFRA_4110 |
|
Source: Publication 'nameOfPub' 's links could not be migrated. Links migration has failed. |
| Description: An unexpected error occured during the links migration of a publication. Therefore,its migration will be skipped by the FBDI engine. |
|
Workaround: None |
|
Warning INFRA_4111 |
|
Source: Activation/Desactivation status for the instance 'nameOfInstance' could not be migrated. |
| Description: The activation/desactivation of the instance were not migrated due to an unexpected error. |
|
Workaround: None |
|
Warning INFRA_4112 |
|
Source: Graphical properties for the instance 'nameOfInstance' could not be migrated. |
| Description: The graphical properties of the instance were not migrated due to an unexpected error. |
|
Workaround: None |
|
Warning INFRA_4113 |
|
Source: Product instance 'nameOfInstance' could not be migrated. |
| Description: An error occured during the entities migration of a product instance. The instance wil not be migrated. |
|
Workaround: None |
|
Warning INFRA_4114 |
|
Source: Properties of the instance 'nameOfInstance' could not be migrated. |
| Description: An error occured during the migration of the instance's properties. These properties won't be migrated. |
|
Workaround: None |
|
Warning INFRA_4115 |
|
Source: Product reference 'nameOfreference' could not be migrated. |
| Description: An error occured during the entities migration of a product reference. The reference wil not be migrated.
|
|
Workaround: None |
|
Warning INFRA_4116 |
|
Source: Failed to locate the representation reference. |
| Description: The representation reference was not found. |
|
Workaround: None |
|
Warning INFRA_4117 |
|
Source: Representation instance could not be migrated.
|
| Description: The representation instance could not be created.
|
|
Workaround: None |
|
Warning INFRA_4118 |
|
Source: Product properties could not be migrated.
|
| Description: An error occured during the migration of a product's properties.
These properties won't be migrated.
|
|
Workaround: None |
|
Warning INFRA_4120 |
|
Source: An occurrence of product instance 'nameOfInstance' could not be migrated. |
| Description: An error occured during the entities migration of a product instance occurrence. The occurrence wil not be migrated. |
|
Workaround: None |
|
Warning INFRA_4121 |
|
Source: A contextual link has been isolated. Contextual part is: "Part name". Element Name is: "Element name". Contextual assembly is: "Assembly name". |
| Description: The link could not be imported so it has been isolated. |
|
Workaround: None |
|
Warning INFRA_4122 |
|
Source: Publication 'nameOfPub' could not be migrated because one with the same name was already migrated. |
| Description: Within an import, we try to migrate a publication that has the same name as one that was previously migrated. |
|
Workaround: None |
|
Warning INFRA_4123 |
|
Source: Modification on identifier set attribute is ignored. The value of the attribute "Attribute name" on the object of type"Object type" has been modified through business logic. As this attribute belongs to identifier set this modification is ignored.
|
| Description: The identifier set attributes are not modified by the Business
Logic. |
|
Workaround: Update the script of the Business Logic so it does not try to
modify the attributes of the identifier set. |
|
Warning INFRA_4124 |
|
Source: A contextual link has been isolated. Contextual part is: "Part name". Element Name is: "Element name". Contextual assembly is: "Assembly name". |
| Description: The link could not be imported so it has been isolated. |
|
Workaround: None |
|
Warning INFRA_4125 |
|
Source: Isolation of a broken contextual import. A broken contextual import has been removed. |
| Description: The link could not be imported so it has been isolated. |
|
Workaround: None |
|
Warning INFRA_4126 |
|
Source: Isolation of a broken contextual import. A broken contextual import has been removed. Original data of this broken contextual import were located in document "Document name". |
| Description: The link could not be imported so it has been isolated.
|
|
Workaround: None |
|
Warning INFRA_4127 |
|
Source: Isolation of a broken contextual import. A broken contextual import has been removed. Original data of this broken contextual import were located in document "Document name". |
| Description: The link could not be imported so it has been isolated.
|
|
Workaround: None |
|
Warning INFRA_4128 |
|
Source: "container name"
This container is not migrated. |
| Description: No implementation for this type of container.
|
|
Workaround: None |
|
Warning INFRA_4129 |
|
Source: Product instance "Instance name": The properties of one occurrence could not be migrated. |
| Description: The properties of the occurrence were not imported. |
|
Workaround: None |
|
Warning INFRA_4130 |
|
Source: A publication was renamed to skip a naming conflict. Original name was : toto, New name is : toto_1. |
| Description: In case of multirep ( DBDI ) we can have naming conflict with publication. We try to rename the pub. In this case, this rename lead to a successfull creation. |
|
Workaround: Rename publications in V5 |
|
Warning INFRA_4131 |
|
Source: It wasn't possible to create a V6 PORT even with a renaming Publication name was : toto |
| Description: In case of multirep ( DBDI ) we can have naming conflict with publication. We try to rename the pub. In this case, this rename still lead to a failure. |
|
Workaround: None |
|
Warning INFRA_4132 |
|
Source:It wasn't possible to create a PORT with name : toto. Check that a port with the same name has not been created before and modify the name on original data if necessary. |
| Description: The creation of a PORT fails. The reason could be a naming conflict issue. |
|
Workaround: Rename publications in V5 |
|
Warning INFRA_4133 |
|
Source:It wasn't possible to create a PORT with name : toto |
| Description: The creation of a PORT fails. The reason cannot be a naming conflict issue. |
|
Workaround: None |
|
Warning INFRA_4134 |
|
Source: Port Name Modification. To be conform with CATIA V6 naming rule a port has been created with a slightly different name from the publication one. Original publication name is 'Original Port Name' whereas port name is 'Modified Port Name' |
| Description: Some caracters are no more supported in the publication name. They are automatically removed during the import. |
|
Workaround: None |
|
Warning INFRA_4201 |
|
Source: After the import, the data is no longer up to date. A manual update is necessary. |
| Description: The import had an impact on the update status of the document. |
|
Workaround: Update the result of the import manually. |
|
Warning INFRA_4202 |
|
Source: An import link on a parameter in a CATProduct file has been isolated. |
| Description: This V5 modelization is not supported |
|
Workaround: None |
|
Warning INFRA_4301 |
|
Source: Cleaning of unknown features + list of the removed features. |
| Description: Some features have an unknown type. They are deleted in the FBDI process. The features aggregated by a removed features are also deleted. |
|
Workaround: Clean input data in CATIA V5. |
|
Warning INFRA_4303 |
|
Source: Error during the update process. Some previously migrated data cannot be reload in Edit Mode. |
| Description: Some data can not be visible in the editor at the end of FBDI. |
|
Workaround: FBDI is not interrupted. Close and re-open your data.
|
|
Warning INFRA_4304 |
|
Source: Some data in the document leads to the mode 'No import'. |
| Description: The document is not imported. |
|
Workaround: None |
|
Warning INFRA_4305 |
|
Source: Data created on CATIA V6 and modified on CATIA V5. |
| Description: Data you are trying to import comes from CATIA V6 and has been modified in CATIA V5. It is a conflicting situation. Current data as well as its pointed data will not be updated through FBDI. |
|
Workaround: None |
|
Warning INFRA_4306 |
|
Source: There is no data to save. |
| Description: All the files were already imported by using the mapping tables. |
|
Workaround: None |
|
Warning INFRA_4401 |
|
Source: A link towards external document cannot be taken into account. |
| Description: The current external link presents an empty path as pointed document path. This path is then ignored. |
|
Workaround: Clean input data in CATIA V5. |
|
Warning INFRA_4402 |
|
Source: Pointed Document is ignored. "Document pathname" is ignored as its extension is not authorized. |
| Description: The document is not imported. |
|
Workaround: None |
|
Warning INFRA_4403 |
|
Source: Link isolation. The pointing element was: "Name of the pointing object". The pointed document was: "Name of the pointed documents" |
| Description: Generic warning mesage for isolation of links during import. |
|
Workaround: None |
|
Warning INFRA_4404 |
|
Source: Pointed document environment is not File. Pointed document: "Document pathname" is ignored as its environment is : "Document Environment". It could be possible to import it through DBDI. |
| Description: The pointed document is not imported. |
|
Workaround: None |
|
Warning INFRA_4405 |
|
Source: The data "component Id" cannot be promoted in the Reference. Remove Links to these components to be able to promote the Workspace. |
| Description: DWS : data that can't be inserted under the root of DWS cannot be promoted. |
|
Workaround: |
|
Warning INFRA_5101 |
|
Source: Unable to value the mapping attribute. |
| Description: The V5 properties were not reported on the V6 component. |
|
Workaround: None |
|
Warning INFRA_5102 |
|
Source: Publication without name. A publication has no name. The corresponding port has been created with the following name: "name of the port". |
| Description: Port created with a computed name. |
|
Workaround: None |
|
Warning INFRA_5304 |
|
Source: Warning raised while opening the file "File name". |
| Description: Give details on the open warning |
|
Workaround: None |
|
Warning INFRA_5305 |
|
Source: Open failed. Migration skipped. The links pointing this document will be isolated. |
| Description: DBDI migration: the open of the document failed. |
|
Workaround: Check if the source document is not corrupted. |
|
Warning INFRA_6301 |
|
Source: There is no Representation to convert. |
| Description: There is no Representation to convert. |
|
Workaround: None |
|