Problem: Algorithm without ELSE

Solution: ELSEIF loops have to be finished by an ELSE statement.

Issue No.: 103983

Presently this is a Warning. Should be an Error in the future.

See Section 7.8.11, “ Attribute algorithms ”.

Problem: Missing Company key

Solution: Set the key

Presently this is a Warning. Should be an Error in the future.

Issue No.: 97129

See Section 3.2.2, “ Definition of catalog Company key (license key) ”.

Problem: Error message:

Project file name should be unique.
The standard numbers should be unique.

In following example a project had been duplicated and only equipped with other table values.

Note This is NOT a recommended approach!

Solution: Instead work with link projects. Create ONE project with all possible table values and filter the link project. Details on this can be found under Section 5.8.2.1.3, “ New link ” -> subitems "Restricted display" and "Restricted display in value ranges".

Problem: No order number and type code specified

Issues: 102895, 102663

Solution: Make sure that all visible projects and projects used as linked projects have proper CNSTYPECODE or CNSORDERNO classification.

See Section 3.2.18, “Classification according to CNSORDERNO / CNSTYPECODE ”.

Note "Proper" also means unique! Also see Fig. „Add unique ORDENRNO for each project“.

Problem: Image (*.png) is too large

Issue No.: 102615, 95873, 96105

Solution: Set target file to CADENAS standard 400x400, color depth 8 bit. When using automated generation this is ensured, if under Picture size, the option STANDARD is selected.

Relevant links:

Also see next point.

Problem: No preview file set

Solution: Under Edit project -> tabbed page General -> Preview, insert the preview image.

If there are no preview images yet, you can automatically create them.

Details on this can be found under Section 5.8.2.1.14.3, “ Generate image data/preview images with batch run ”.

Problem: Recursion in algorithm for variable

Solution: Check and correct the error in the algorithm. Example: Recursion for both variables A and B (A(attribute algorithm)-->$B. B(attribute algorithm)-->$A.)

See Section 7.8.11, “ Attribute algorithms ” -> "Error avoidance".

Problem: Different projects have the same order number

Add unique ORDENRNO for each project

Solution: Correct the Standard name (NB) in a way that all values are unique.

See Section 5.8.2.1.12, “ Test project / Test directory ” -> Test standard part identifier for uniqueness.

Note If it's not only about simple corrections but about duplicates, use link projects. A detailed explanation on a similar case can be found below.

Problem: The assembly contains parts without NB

Solution: Add NB in project

For details see Section 7.12.7.3, “ Guideline for NB, SHORTNB, LINA definition and Identification type ”.

Problem: Multiple parts of the assembly have the same NB

Solution: Find projects in TestMeta that have same NB and modify it to be unique.

For details see Section 7.12.7.3, “ Guideline for NB, SHORTNB, LINA definition and Identification type ”.

Problem: Standard name (NB) doesn't contain the value range variable

Solution: Add all value range variables from project table in Standard name (NB).

For details see Section 7.12.7.3, “ Guideline for NB, SHORTNB, LINA definition and Identification type ”.

Problem: Different table rows have the same value which results in the same Standard name (NB).

Solution: Change same table values or add more variables to the Standard name, so that different values result. If in above example, the Standard name is expanded from NB='$ORDERNO.' to NB='$ORDERNO. $A.' uniqueness is given.

Each row should have a different value if it is only one variable in NB.

For details see Section 7.12.7.3, “ Guideline for NB, SHORTNB, LINA definition and Identification type ”.

Problem: QA check throws following error message:

In project <project path> (<name.tab>, line xy) is the same standard name: <value>

Dialog box "QA check"

This error message occurs, if the equation of Standard name is identical at several projects AND the table has the same values.

Example:

Project 1 with NB='Cube 1 - $L.'

project1.prj and project2.prj are duplicates

Project 2 with the same NB NB='Cube 1 - $L.' and the same table values.

Solution: In above example we have the case of duplicates. There are some possible solutions:

For details also see Section 7.12.7.3, “ Guideline for NB, SHORTNB, LINA definition and Identification type ”.

Problem: Same Short name (max. 16 characters)

Values of different variables are identical. In this case there is no uniqueness, what is not allowed.

Solution: Find project with same short name, and add correct short names for each project

For details see Section 7.12.7.3, “ Guideline for NB, SHORTNB, LINA definition and Identification type ”.

Problem: Value range variable is not contained in the short name.

Solution: Include all value range variables from project table under Short name (max. 16 characters).

For details see Section 7.12.7.3, “ Guideline for NB, SHORTNB, LINA definition and Identification type ”.

Problem: "Error: In row <row_name> exists the same short name"

Solution: Check if all value range variables are included under Short name (max. 16 characters).

For details see Section 7.12.7.3, “ Guideline for NB, SHORTNB, LINA definition and Identification type ”.

Problem: "Error: Shortname is too long"

Solution: Maximum length of Short name (KB) (max. 16 characters according to CAD!).

If the string of a Short name is larger than this limit, an entry is created in the log file.

See Section 5.8.2.1.12, “ Test project / Test directory ” -> Test short name.

Problem: "Error in short description, variable <xy> is not defined"

Solution: Check the difference between "Standard name" and "Short name" In Short name you may have variable which are not in the table.

See Section 5.8.2.1.12, “ Test project / Test directory ” -> Test short name.

Problem: Error when trying to pull the license key

The project does not have the correct License key.

Solution:

See Section 3.2.2, “ Definition of catalog Company key (license key) ”.

Problem: Error while recalculating part

Solution: Open .3db in PARTdesigner. Find error in sketch with Check Part .

Also see Section 7.17.2, “ Test part ”.

Problem: Two or more connection points in sketch have the same name.

Solution: Open 3db -> Sketch: Check the names of connection points and rename the affected ones so that each name is unique then.

Problem: The objects are not connected (disjoint feature <name>)!(part: <name> -> History: <name>)

Solution: Check .3db with Check Part button, find disjoint figures and connect them.

Also see Section 7.9.7, “Problem avoidance ” -> Error message "The result is more than one solid"

Problem: Internal error. Edit or delete the last step you performed.

Solution: Find Error in .3db with Check Part button.

Also see Section 7.17.2, “ Test part ”.

Problem: Non manifold : Each edge can only be connected to exactly 2 faces. More than 2 are detected.:

A definition for "non-manifold" related to praxis is: You could not machine the shape out of a single block.

The interior cut touches a face of the body at a line.

Solution: Check .3db (geometry) You have not allowed geometry in .3db.

Also see Section 7.9.7, “Problem avoidance ” -> Error message "non-manifold".

Problem: The part <name> has no geometry

Solution: Add .3db in project.

See Section 5.9.3.2, “ 3D models ”.

Problem: Extrusion length is 0. the_extrusion_length_must_be_greater_than_0

Solution: Check extrusion conditions in .3db.

See Section 7.6.4.2.1, “ Extrude... ”.

Problem: Error in connection rules

Solution: Check the connection rules of the configuration file (asmcfg) in the dialog box Rule properties.

See Section 9.7.2.4, “Connect the components via rules ”.

Problem: Timeout. The set test time expired.

Solution: Set a higher value for timeout to avoid it.

See Section 6.3.3, “PARTproject QA: Svn Login ”.

Problem: Error message "No connection to the TestMeta possible!"

After starting TestMeta, PARTproject connects to Testmeta by the COM system. If this is not possible an error message is shown.

Solution: Check if a crashed TestMeta is still running in the background. For other reasons please check the log files for errors.

See Section 6.3.3, “PARTproject QA: Svn Login ”.

Problem: Unable to find file

Solution: Check for files which are not entered in PARTproject folder

See Chapter 2, Create electronic product catalog - Overview -> Additional information.

Problem: Certain variable used, but not defined.

Error message: "Error in recalculation, variable <name> is not defined"

Solution: Define used variable

Note When deleting variables always make sure that it is not used anywhere. Otherwise during QA check, the following error message will appear. Example: Error in short description, variable <name> is not defined.

Also see Section 7.8.1, “ Variable Manager - The most important at a glance” -> Point "Functions"

Problem: Number must be greater than 0.

Projects have to have a proper table, otherwise saving is not possible in PARTdesigner.

When creating new projects the following error message appears, because no table still exists:

Error ZA line (ZA,DA,0), Number must be greater than 0.

Solution: Create a table. (Whether the variable is used in the model doesn't matter.) At least one variable with one value has to exist in the table.

A table with one variable and one value is sufficient to avoid the error.

The error could also arise during QA check.

See Section 5.8.2.1.2, “ New project ”.

Problem; No existing records in the file

Error message:"No existing records in the file" is a subsequent error of "Error ZA line (ZA,DA,0), number must be greater than 0" (possibly caused, when subsequently removing table lines again).

Solution: At least one variable with one value has to exist in the table.

See Section 5.8.2.1.2, “ New project ”.