CADDS & CAMU Error Codes


Error Code 22

Command:
ACTivate ASSembly ASSEmblyname <filename> ADRawname layout
Activating Assembly Design Environment
Selected VPmode is VPAll.
You are entering the camu environment.
Activating an OLD assembly: <Assy filename>

Error:
Error in accessing the database: <Assy filename>
The DB process associated with this file has abnormally exited.

Or:
There is a problem activating the assembly tree <Assy filename>
You will have to reissue ACTIVATE ASSEMBLY.

Result is error code 22
Means: Something has killed off the ODB_DAEMON. This daemon controls the CAMU process.

Error Summary
After an unexpected Exit, the ODB_SERVER is the only process to kill. Killing both the ODB_SERVER AND ODB_DAEMON may result in the error code.

Correction:
Contact System Administrator to reset daemon.



Error Code 1 or 67

Command:
ACTivate Model <part.filename>

Error: Never activated the model, returns you back to the assembly.
Result is error code 1 or 67

Means: The _pd file of the model has somehow become corrupt.

Correction: The model can not be fixed, bring back from tape or backup.



Error Code 82

Command:
ACTivate ASSembly ASSEmblyname <AssyFilename> ADRawname <drawing>

Error: Activating an OLD assembly: <Assy Filename>

The file is being opened for output, but is already open for write. (ca95)

ERROR: There is a problem activating the assembly tree <Assy Filename>.
You will have to reissue ACTIVATE ASSEMBLY.
Result is error code 82
Assembly Design Version 2.0
Activating Assembly Design Environment
Means: Another User has the assembly tree active.

Correction:
You can not activate another assembly when it is active somewhere else,
fmclear or findout who has it.



Error Code 109

Means:
A component you are trying to view has exceeded 99 vp_link files.

Correction:
Remove the vp_link files from the affected database. File or refresh your
assembly



Error Code 112

Command:

VIEW COMponent

Error:

"A validate_db was run on the part, tvf's are out of date."

Result is error code 112

Means:
All the tvf's of the part are not in sequence with the assembly.

Correction:
Regenerate tvf via ACT COMponent



Error Code 113

Command:
VIEW COMponent

Error:
Result is error code 113

Means:
No tvf present. Possible cause - parametric model that had no explicit
tvf generated.

Correction:
Regenerate tvf via ACT COMponent



Error Code 114

Command:
VIEW COMponent CIName j-box.125755-5_1 OUTlinemode 1 DETAilmode 1

Error:
Cannot display instance. The referenced part is single part-format while
the active part is double part-format. Part formats cannot be mixed.

Result is error code 114

Means:
The part is single precision.

Correction:
If part is on active disk follow reformat procedures.



Error Code 116

Command:
VIEW COMponent CIName ...

Error:
Result is error code 116

Means:
Part has a zero length _pd file. It's either corrupt or hasn't been filed
yet.

Correction:
File the part if new. No resolution for a corrupt zero length _pd.



Error Code 121

Command:
VIEW COMPONENT

Error:
Result is error code 121

Means:
Model part has no vp_links

Correction:
Contact System Administrator to create vp_links.



Error Code 123

Command:
VIEW COMponent CIName j-box.125755-5_1 OUTlinemode 1 DETAilmode 1

Error:
A open operation on the file, 125755.K.001.&PD, has failed with the following
error.
The viewpart directory (vp_links) does not have write access. (caa1)

To enable this command the unix permission must be changed on the (vp_links)
directory.

Result is error code 123

Means:
Permissions do not allow access to vp_links directory.

Correction:
Contact System Administrator to chmod 777 vp_links.



Error Code 127

Command:
VIEW COMponent CIName j-box.125755-5_1 OUTlinemode 1 DETAilmode

Error:
WARNING: The model part associated to the component contains no graphical
entities to view.

Result is error code 127

Means:
The last filed off TVF contains no model entities.

Correction:
** Make sure draw 1 is the MRA

** Act model draw 1 and file part or regen mdraws



Error Code 202

Command:
ACTIVATE ASSEMBLY

Error:
Result is error code 202

Means:
You are trying to activate an assembly of C5 format while your current
part format is DOUBLE.

Correction:
Type: SELECT PFORMAT C5

Re-activate the assembly



Error Code 9017

Command:
VIEW COMPONENT

Error:
Result is error code 9017

Means:
An attempt to view in a non C5 model into a parametric assembly.

Correction:
Convert the part to C5

Re-activate the assembly




Activating a Read Only Model

Command:
ACTivate MODel CIName j-box.125755-5_1

Error:
User only has read access to this part.

Error Recovery: Reactivating part WP.CAMU.1006997.0.LAYOUT.

Activating SUSPENDED part.

ERROR
Activating a read only model is not allowed, except for the root
component model.

Means:
Trying to activate a write protected part.mdraw.

Correction:
Contact System Administrator.



Shows old model geometry

Command:
View Component

Error:
When the camu assembly was activated, the updated model did not show the
updated changes.

Means:
The model retained the old mra which was linked to the pd file, therefore
the assembly was viewing in the old tvf.

Correction:
Activate the model as a part, and delete the draw 'mdraw' (i.e. delete
draw mdraw )

Activate all the drawings one by one, after the last one is activated,

file part notvf

exit part q

Activate the camu assembly, and activate the model within the camu assembly
to recreate

the mdraw, then file the model



Error Code 26241

Command:
HIDE OBJECT in a CAMU assembly

Error:
*** Hidden-line removal could not be completed ***

Exit Code 26241 was generated...

Correction:
Your assembly contains one or more bad solids. View smaller portions of
your assembly and re-hide. Continue viewing on more and more components
until the error is repeated.

Once error has repeated, view only the sub-assembly that re-created the
error and re-hide to verify. Begin viewing on 1 or 2 components at a time
within the affected sub-assembly and re-hide until you have found the problem
database.

Once located, perform a validate_db on the problem part(s). This may or
may not fix the problem. If the solid is unfixable, the solid may need
to be re-created.


Error Code 51718

Command:
ACTivate ASSembly

Correction:
Contact System Administrator to change permissions on the _db to 775.


Error Code 70003

Command:
VIEW COMponent CIName ...

Error:
Result is error code 70003

Means:
Part has a zero length _fd file. It's either corrupt or hasn't been filed
yet.

Correction:
File the part if new. No resolution for a corrupt zero length _fd.


Error Code 70005

Error:
Error Code 70005

Correction:
Exit your CADDS session and restart.


Error Code 70006

Error:
Usually occurs after transferring a model to a new directory and viewing
it in within CAMU. The error relates to the vp_links file.

Correction:
Have your sys admin trash the entire vp_links directory of the affected
model and re-create it. Re-activate the model via the CAMU assembly.


DR51 Error

Command:

HIDE OBJECT

Problem:
When performing an HLR on a parametric part, you receive an error code
DR51. The solid will not hide or un-hide. We believe using the "ALL"
modifier with HIDE OBJECT is causing this condition. Don't use "ALL".

Work Around:
1.Run "ckcad -f -p -dex" on the part in a UNIX shell. (-dex removes
the data exchange table)
2.Activate the part thru explicit.
3.Activate a drawing
4.Now you only need to perform:
1.CHANGE EXTENTS LEAST UPDATE
2.REG GRA
5.FILE PART
6.Enter parametrics
7.Key: eval "(verify_hist)" ...Wait for the message "Regeneration Completed"

8.FILE PART
9.Enter Explicit (regenerates the data exchange table removed by -dex)

10.Perform FULL dbase mgmt:
1.CHECK DBA
2.CHANGE EXTENTS LEAST UPDATE
3.REG GRA
11.FILE PART
12.HIDE OBJECT should now work.


Error: Command not valid at this time

Correction:
Key: <CTRL>E several times. This should take care of it.


Error: Requested license not avalible.

"Requested license not avalible." appears when exiting a CAMU assembly.

Means:
This is a known bug with Revision 8.1.2.

Correction:
This is a bogus error message. There is nothing wrong with the CADDS5 session.


Error: ** FILE MANAGER ERROR C01C **

Error:
** FILE MANAGER ERROR C01C **

Means:
Corrupt TVF file.

Correction:
Act part and EXIT PART FILE NOTVF UNLINKED


Error: WARNING: Another user is activating this previous revision

Error:
WARNING: Another user is activating this previous revision assembly for
conversion to the current revision. Please activate after the assembly
has been filed.

Means:
This is a known bug in 8.1.2. This happens when you copy a component from
a reference assembly and put it into your active assembly. Leaving your
_db file corrupt.

Correction:
Contact the support group, the _db will need to be rebuilt. This bug is
fixed in rev 8.3.

Error: Error Code CAA1

CAMU Environment

Explicit or Parametric Environments

Command Issued:

## View Component


CADDS 5 Error:

A open operation on the file, WOR.GWD.IDP2.G234567.-0.MODEL.&PD,
has failed with the following error:

The viewpart directory (vp_links) does not have write access.
(CAA1)

Summary of the Error:
This indicates that either the permissions for the databases "vp_links" directory are not set up properly or there are no "vp_links" directory.


Correction:
Contact a Systems Administator for help.


Error Code CA02

Explicit or Parametric Environments


Command Issued:
## Activate Part


CADDS 5 Error:
A open operation on the file, WOR.GWD.IDP2.G123456.-0.CHASSIS.&pd,
has failed with the following error:

A directory in the file does not have search permission or the
required read/write permissions are not granted for the file for
the current user. (ca02)

Error: Part cannot be activated.


Summary of the Error:
The UNIX permissions are not set to the correct settings.



Correction:
Please contact a Systems administrator for further assistance.


Error Code CA06

CAMU Environment

Explicit Environment


Command Issued:
## Hide Object


CADDS 5 Error:
** FILE MANAGER ERROR CA06 **
An internal FM problem has occurred. A bad file descriptor has been
passed to a UNIX system call.
(open, read, write, and lseek system calls)

An unknown error has occurred. So that Computervision can
improve the quality of this error message, please submit a bug
indicating the command which generated this message and the two
commands executed just prior to it. Thank you.


Summary of the Error:
No information is currently available to explain why this error is occuring.



Correction:
No information is currently available on the proper way to correct this error code. When a method is
determined this information will be updated.

If you determine a method that is valid, please contact Rick Henry.


Error Code for CA20

CAMU Environment

Explicit or Parametric Environments


Command Issued:
## Activate Assembly


CADDS 5 Error:
A call to the UNIX system call 'mkdir' has returned an error.
The directory has not been created. (CA20)


Summary of the Error:
This means that the terminal that the environment variable DB_DAEMON_HOST is set to does not
have read/write permissions on the MCAD server.


Correction:
Please contact the Systems office for further assistance.


CL_MSG_UNKNOWN_DIALOG

Parametric Environment (ONLY)


Command Issued:
%% Insert Feature (Property Sheet for other libraries)


CADDS 5 Error:
CL_MSG_UNKNOWN_DIALOG: Dialog ModelInsertFeatureCab Not Registered


Summary of the Error:
Something is causing CADDS 5 not to see the necessary libraries to create this new CVACT based
property sheet.


Correction:
For all paths that callout CADDS 5 directories, /usr/apl/cadds/bin must be first. This is especally true
for the .cvactrc file. Check the "env" for "PATH" /usr/apl/cadds/bin must be first.


CR

Explicit or Parametric Environments


Command Issued:
Property Sheet Selection


CADDS 5 Error:
CR process is not active at this time.


Summary of the Error:
CR are the newer property sheets that have been built using the CVACT tool. The error means that the
CR file is not sourced any- where in either .caddsrc, .caddsrc-local or .cshrc . Also, the .cvactrc file
should also be sourced the .cshrc file is the better location for sourcing it.


Correction:
This line must be added to any one of these files .caddsrc, .caddsrc-local or .cshrc .

setenv LD_LIBRARY_PATH /opt/SUNWits/Graphics-sw/xgl-3.0/lib: \
/usr/ucblib:/usr/openwin/lib:/usr/apl/cadds/slib:/usr/lib: \
/usr/apl/cvact/lib:/usr/apl/cadds/slib:/usr/dt/share/include/Xm

The .cvactrc file should be sourced from the .cshrc file. These lines should appear in your .cshrc file.

#-- Setting Library paths for CVACT and sourcing the rc script.

if ( -d /usr/apl/cvact ) then

if ( -f "$HOME/.cvactrc" ) then
source $HOME/.cvactrc
else
source /usr/apl/cvact/Install/cvactrc
endif
endif


ERROR OCCURRED...FROM DMG BITMAP

Explicit Environment (Only)


Command Issued:
## Activate Drawing

CADDS 5 Error:
ERROR OCCURRED DURING READ FROM DMG BITMAP;
rdbitm c01cdmgmain: DMG FILE ERROR c01C##

Summary of the Error:
The DMG is a Drawing management subfile of _pd database. It tells what needs to be regenerated when switching drawings. Apparently, DMG BITMAP means there's a problem with some TVF information stored within the _pd file, and the only way to fix that is a File Part NOTVF unlinked. Just deleting the drawing TVF files won't fix the TVF info stored in the _pd.

Correction:
Anytime you get an error message that mentions DMG BITMAP, this series of commands in that part will usually fix the problem.

## FILE PART NOTVF NOSHADE NOHIDE UNLINKED
## EXIT PART QUIT
## ACTIvate PART <filename>
## ACTIvate DRAW <any drawing>
## FILE PART

If problem still exists, _pd is probably bad. validate_db or ckCAD may or may not check this area, but you can try. If still problems, try some INSERT PART type of scheme to create a new database.


Error Code 2404

CAMU Environment

Explicit or Parametric Environments


Command Issued:
## File Assebmly


CADDS 5 Error:
Part =USR2.AUX174.ASSY.AEG2.KEB.6850804.-0.UPCON-MULT.EHP.&PD was filed.

Filing: Updating assembly tree database...
WARNING: A problem occurred while committing the assembly to the
database. Some changes may not have been filed.

Result is error code 2404


Summary of the Error:
None is currently available.


Correction:
No information is currently available on the proper way to correct this error code. When a method is
determined this information will be updated. If you determine a method that is valid, please contact
Rick Henry.

** FILE MANAGER ERROR C006 **

CAMU Environment

Explicit or Parametric Environments

## FILE ASSembly ** FILE MANAGER ERROR C006 ** The requested file cannot be found. (fileopen, fileinfo, filemodify, filedelete) Part

=USR2.AUX174.ASSY.AEG2.RJE.DBG677785.-3.DOLLY-ASSY.SHT1.&PD was filed. Filing: Updating assembly tree database...

WARNING: A problem occurred while committing the assembly to the database. Some changes may not have been filed. Result is error code 2300

## FILE ASSembly ** FILE MANAGER ERROR C006 ** The requested file cannot be found. (fileopen, fileinfo, filemodify,
filedelete) Part =USR2.AUX174.ASSY.AEG2.RJE.DBG677785.-3.DOLLY-ASSY.SHT1.&PD was filed.

ERROR: Error in accessing the database: =USR2.AUX12.ASSY.AEG2.RJE.DBG677785.-3.DOLLY-ASSY.&DB The DB process associated with this file has abnormally exited.

ERROR: Error in accessing the database: =USR2.AUX12.ASSY.AEG2.RJE.DBG677785.-3.DOLLY-ASSY.&DB The DB process associated with this file has abnormally exited.

ERROR: Error in accessing the database: =USR2.AUX12.ASSY.AEG2.RJE.DBG677785.-3.DOLLY-ASSY.&DB The DB process associated with this file has abnormally exited.

ERROR: Error in accessing the database: =USR2.AUX12.ASSY.AEG2.RJE.DBG677785.-3.DOLLY-ASSY.&DB The DB process associated with this file has abnormally exited.

Filing: Updating assembly tree database...

ERROR: Error in accessing the database: =USR2.AUX12.ASSY.AEG2.RJE.DBG677785.-3.DOLLY-ASSY.&DB The DB process associated with this file has abnormally exited.

Result is error code 22


Error Code 30523

CAMU Environment

Explicit or Parametric Environments


Command Issued:
## View Component


CADDS 5 Error:
Result is error code 30523


Summary of the Error:
The Root node is being selected to view all of the components from and it is trying to be viewed itself.


Correction:
Change the "OUTLINE" selection on the "View Component" property sheet from "VIEW" to "NONE".
The Root node can not be viewed.


Error Code 51724

CAMU Environment

Explicit or Parametric Environments


Command Issued:
## View Component


CADDS 5 Error:
WARNING: A problem occurred while committing the assembly to the database.
Some changes may not have been filed.

Result is error code 51724


Summary of the Error:
None is currently available.


Correction:
No information is currently available on the proper way to correct this error code. When a method is
determined this information will be updated. If you determine a method that is valid, please contact
Rick Henry.


Error Reading Miptr

Explicit Environment (ONLY)


Command Issued:
## Hide Object


CADDS 5 Error:
The digitized solid or trimmed surface is an 

  old style object. It must be rebuilt.

** WARNING ** Error reading Miptr XXX.

Continuing HLR for remaining Objects.

** ERROR ** No valid objects found.

Terminating HLR process.


Summary of the Error:
When a Parametric model is changed sometimes the Explicit mode view graphics do not update.
Therefore the Parametric model must be forced to regenerate the Explicit mode view graphics.


Correction:
Enter into the Parametric environment and change any parameter and regenerate the model. Change
the recently changed parameter back to it's original value and regenerate the model again.


FF_ITEM_TYPE_FEATURE_NAME

Parametric Environment (ONLY)


Command Issued:
%% Select Library (For Parametric Features)


CADDS 5 Error:
The LDM server has used up all of it's available sessions.

Error - Invalid enrty - FF_ITEM_TYPE_FEATURE_NAME expected

Typing mistake, the token is invalid.


Summary of the Error:
For some reason no libraries appear in the run time list for selection. Also no features from any
existing library will work. The cause of this is unknown.


Correction:
Contact Systems. The features process must be killed and restarted.


 HLR

CAMU Environment

Explicit Environment (Only)


Command Issued:
## Hide Object All Blanked :


CADDS 5 Error:
The digitized solid or trimmed surface is an

old style object. It must be rebuilt.

** WARNING ** Error reading Miptr XXX.

Continuing HLR for remaining Objects.

** ERROR ** No valid objects found.

Terminating HLR process.


Summary of the Error:
The Explicit graphics for the Parametric database are not viewing and can not be selected to perform
HLR. Probably only bits and pieces of the model are visible.


Correction:
Enter to the Parametric side of the database. Change any parameter and regenerate the model. Enter
to the Explicit side and all of the entities will be visible and can be HLR'ed. Go back to the Parametric
side and change the parameter that was changed back to it's original value.


invalid_header_size

Explicit or Parametric Environments


Command Issued:
## Activate Part


CADDS 5 Error:
## ACTivate PARt WOR.GWD.IDP2.DBG567890.-0.COVER

Single precision not allowed for parametrics:
Use REFORMAT PART to enable parametric changes to the part
or SELECT PFORMAT SINGLE to work only in explicit.

%% Activate Part =USR2.AUX173.WOR.BGD.NSP2.DBG727212.-0.SEAL-WG

Single precision not allowed for parametrics:

Use REFORMAT PART to enable parametric changes to the part

or SELECT PFORMAT SINGLE to work only in explicit.

%>

## SELect PFOrmat Single

The default part-format for parts is now SINGLE.

## ACTivate PARt =USR2.AUX173.WOR.BGD.NSP2.DBG727212.-0.SEAL-WG

Activating OLD part.

Part not usable due to invalid header size - COMMAND ABORTED

## REFORmat PARt From WOR.GWD.IDP2.DBG567890.-0.COVER To WEEK.GWD.NEW

Part name WEEK.GWD.NEW.WOR.GWD.IDP2.DBG567890.-0.COVER is illegal.
Part not reformatted.


Summary of the Error:
For some reason the "_PD" has become corrupt and "Validate_Db" or "Ckcadds" will not work to correct
this problem.


Correction:
First use the "LIST PART DIRECTORY" command to check whether the database is a CADDS 4X style or a CADDS 5 DESIGN style part.

## LISt PART DIr =USR2.AUX173.WOR.BGD.NSP2.DBG727212.-0.SEAL-WG

**DIR NAME**
=USR2.AUX12.WOR.GWD.IDP2.DBG567890.-0.COVER

CREATION
**PART NAME** TYPE DATE TIME ACCESS DATE
WOR.GWD.IDP2.DBG567890.-0.COVER UNKNOWN 7-23-97 13:25:46 7-23-97
##

Copy the "_PD" file from another database via UNIX. The current "_PD" is no longer any good. Once
this is completed, activate the database and enter the Parametric environment. Change any parameter and regenerate the model, thus forcing the Explicit graphics to rewrite the newly copy "_PD" file. The database should be back to normal. This will only work if the database was created through Parametrics.


Library Current

Explicit or Parametric Environments

For CADDS 5 Design Parts (ONLY)


Command Issued:
%% Activate Part


CADDS 5 Error:
Part is not in library current.


Summary of the Error:
The Parametric databases "_fd" which contains the Parametric information for a CADDS 5 database has
been lost. The reason for this happening is unknown.


Correction:
Follow the steps below to correct this problem:


Activate a new Parametric database and create a drawing.

File the database and exit it.

>From UNIX level copy the newly created "_fd" file to the database that is having problems.

Sometimes this works and sometimes it doesn't. If this method does not work, then submit a Pink
Sheet and have the database reloaded from a date when the "_fd" file might still be attached.


Unknown Error

Parametric Environment


Command Issued:
%% File Part


CADDS 5 Error:
AN UNKNOWN ERROR OCCURED WHILE ATTEMPTING TO
FILE PART. PLEASE REPORT THIS PROBLEM TO
COMPUTERVISION
***************PART NOT FILED****************


Summary of the Error:
This error seems to happen within the Parametric modeling environment. If a diameter parameter is
moved before the database has been filed


Correction:
Upon activating a new Parametric database issue the "File Part" command. If the above error appears
quit the database and try again.


vp_links

CAMU Environment

Explicit or Parametric Environments


Command Issued:
## View Component


CADDS 5 Error:
A open operation on the file, WOR.GWD.IDP2.G234567.-0.MODEL.&PD,
has failed with the following error:

The viewpart directory (vp_links) does not have write access.
(caa1)


Summary of the Error:
This indicates that either the permissions for the databases "vp_links" directory are not set up properly
or there are no "vp_links" directory.


Correction:
Contact a Systems Administator for help.


WARNING: The model part...contains no graphical enties to view. (No graphical entities to view)

CAMU Environment

Explicit and Parametric Environments


Command Issued:
## View Component CIName a0931-1.100886_1 OUTlinemode 1 DETAilmode 1


CADDS 5 Error:
VIEW PART 1008861.A.001

WARNING: The model part associated to the component contins

no graphical enties to view.

Summary of the Error:
The MRA tvf file is not there.


Correction:
Activate and file the part with:
ACTivate MODel CIName a0931-1.1008861_1
ACTivate ADRawing ADRawname layout EXPLODedview 0

FILE ASSembly MODELName =USR5.PARTSA.WP.222.1008861.A.001



Error Code Exit assembly fileflag

CAMU Environment

Explicit Environments


Command Issued:
## Exit assembly fileflag yes or no


CADDS 5 Error:
Usually on "exit assembly fileflag yes" or "exit assembly file flag no": Rolling segmentation violations and rolling bus errors.


Summary of the Error:
Activate Model within the CAMU environment will result in a scrolling segmentation violation/bus error message under the following scenario:

The default part format is double (C4X double precision). This can be set by selecting pformat double from the FILE MANAGEMENT icon or saving the pformat in a parameter file that is referenced by the .caddsrc/.caddsrc-local file.

An explicit assembly is activated and two components are added which reference models which are of pformat C5. Activate the first C5 model, then attempt to activate the second C5 model - this will result in the scrolling error and the CADDS5 session will be hung.


Correction: ** SEGV or BUS ERROR is NOT a CV error message. These are OS messages that indicate memory violations by the program. (Usually a bug) One known cause is the following bug:

Defect ID: 143731

CADDS 5 Revision: 5.2.0


Error Code 30201

CAMU Environment

Explicit or Parametric Environments


Command Issued:
## View Component


CADDS 5 Error:
In a assembly trying to view on several different components. has failed with the following error:

Result is error code 30201


Summary of the Error:
?? Multi-user ODB problem


Correction:
Check for ODB processes and contact a Systems Administator for help.


In CADDS command window "Error in accessing the database..."

CAMU Environment


Explicit or Parametric Environments


Command Issued:
## View Component


CADDS 5 Error:
Error in accessing the database:

The DB process associated with this file has abnormally exited.


Summary of the Error:
his means that the connection to ODB_SERVER was established, then lost. Maybe the ODB_SERVER process crashed or was killed...


Correction:
Contact a Systems Administator for help.


No such message: 23 in table: 1712

Environment:
Unknown

Command Issued:


CADDS 5 Error:
Error: No such message: 23 in table: 1712

Summary of the Error:
There is no such message in table 1712. Table 1712 is for IPC errors.

Correction:
This appears to be a generic Interprocess Communication error, and that Computervision originally mis-handled the message number


AM: Cannot connect to service DB_DAEMON_xxxxxxxx on

Environment:
CAMU, Explicit and Parametric

Command Issued:


CADDS 5 Error:
AM: Cannot connect to service DB_DAEMON_xxxxxxxx on
RPC: Program not registered

Summary of the Error:
Basically, the ODB_DAEMON was spawned to create ODB_SERVER. The new RPC program number is appended to create this DB_DAEMON_xxxxxxxx service (really an RPC alias for the new SERVER). The A_D process should then talk directly to ODB_SERVER. Either the ODB_SERVER executable never started, crashed, or couldn't register.

Correction:
Check that the ODB_am_wh environment variable is set OK.


atan2: DOMAIN error

Environment:
CADDS Explicit

Command Issued:


CADDS 5 Error:
Error: atan2: DOMAIN error

Summary of the Error:
atan 2 is a system call for trig arctan function. Computervision gave bad input somewhere. From man page: atan() returns NaN and sets errno to EDOM when x is NaN. In addition, a message indicating DOMAIN error is printed on the standard error output.

Correction:
Unknown - try exiting CADDS and reentering again.


UNABLE TO NORMALIZE MATRIX...

Environment:
CADDS and CAMU Explicit

Command Issued:


CADDS 5 Error:
Error: "IGSERR(036): UNABLE TO NORMALIZE MATRIX FOR ECB 1025"

Summary of the Error:
This is a CADDS explicit graphics display message and appears that it can happen in both explicit part or CAMU.

Correction:
In an explicit part, try EXIT PART NOTVF UNLINKED


INTERNAL ERROR: The id hash table...

Environment:
CAMU Explicit and Parametric

Command Issued:


CADDS 5 Error:
INTERNAL ERROR: The id hash table could find the specified name.

Summary of the Error:
In the code, this error comes from looking up a name in the name-to-object hash table when in fact the given name does not exist. File Assembly does a "Refresh" also. The refresh from the server must be asking to remove a named object that didn't exist locally

Correction:



NO ELEMENTS ERROR

Environment:
CADDS and CAMU Explicit

Command Issued:
##VIEW PART
or:
## COPY ENTIty TO XX

CADDS 5 Error:
Error: NO ELEMENTS ERROR. Bad HLR entities.

Summary of the Error and Correction:

Bad HLR entities. This most often occurs when an HLR entity is deleted, or a part that has had an HLR done to it is inserted or copied (view part/copy ent to XX). The entities cannot be deleted until a database cleanup is done. After this, you can delete these entities. As a last resort you can delete these entities by miptr number. While in validate_db -p, use the "delete entity miptr/mirange" command.

The NO ELEMENTS ERROR means that whatever was digitized was expecting to find all the members of a particular Solid and was unable to do so.

Here are the reasons that might cause this:

  1. The SOLID Bit was set in the MIBLOCK of an entity and it is not a member of a Solid or Trimmed Surface. Both ckcad and validate_db (CHECK DBASE) should correct this, but ckcad knows about more cases than validate_db.
  2. The SOLID is corrupt.
    1. If the SOLID is Explicit, then ckcad's "report solid" command can identify and, in some cases, correct the Solid/Trimmed Surface. CADDS's DEBUG SOLID VALIDATE can detect some flawed Solids, but it over-reports conditions and misses others (this is why it is not a supported command and it has not been updated in over five years).
    2. If the SOLID is Parametric, the only reliable way (until C5 Rev. 7 -- Parametrics will have a validator) to determine if the Solid is valid on the Explicit Side is to dig a piece of the Solid (in Getdata, SOlid dig ) and if you get the NO ELEMENTS ERROR, then you must fix the Solid on the Parametric Side.

(RD,WR)FACE(0,1,2) error value 1...

Environment:
CADDS

Command Issued:


CADDS 5 Error:
(RD,WR)FACE(0,1,2) error value 1-- boundry index = -1, edge index = -1;
"read" MIPTR and subrec indes are -1 and -1; "write" MIPTER and subrec
index are -1 and -1. Bad face with MIPTR=0 in solid with MIPTR=38332

Summary of the Error:
This is a fatal error message - usually considered to be the kiss of death for the database.

Correction:
Try using validate_db or ckCAD or inserting database into a new empty part. Otherwise, unknown


{RD, WR}FACE{0,1,2} error value -51850...

Environment:
CADDS or CAMU Explicit and Parametric

Command Issued:
## HIDE SOLId

CADDS 5 Error:
{RD, WR}FACE{0,1,2} error value -51850 -- boundry index = -1, edge index = -1;
"read" MIPTR and subrec index are -1 and -1;
"write" MIPTR and subrec index are -1 and -1.

Bad face with MIPTR=3422 in solid with MIPTR=526,

**WARNING** Error reading Miptr 526.
Continuing HLR for remaining objects,

**ERROR** No valid objects found.
Terminating HLR process,

Summary of the Error:
When trying to do HLR on a parametric part in explicit, this error appears. Parametric part has been modified and update HLR image has been performed.

Correction:
Try changing a parameter on your parametric part to regenerate it, then change it back. You should be able to do a HLR restore at this point to clear the bad stuff and do an HLR to get it back. The best recommendation is to do a complete HLR restore and re-hide to the model whenever possible.


ERROR: You cannot orient a component

Environment:
CAMU Explicit and Parametric

Command Issued:
## VIEW PART =XXXX.XXXXXX.ADHANDLEPART

CADDS 5 Error:
Error: You cannot orient a component with a non-existent model together with no CV_ASSEMBLY_HANDLE_PART being set in your environment.

Summary of the Error:
Unable to open drawing for specified part. This could mean the drawing file does not exist.

Correction:
This could mean the drawing file does not exist.


Tesselation Errors

Environment:
CADDS Explicit

Command Issued:
Solids commands

CADDS 5 Error:
tesselator error number is XXXXX

Summary and Correction of the Error:

If you work solely in solids it should be a translation error, if not, you have serious problems. If you build your own solids from surfaces, etc., then just verify the surfaces being used and make sure they are all degree 3. If not fix them. There may be a software setting that will help this but in general it means that surface is either corrupt or rippled in such a way that the system cannot shade it correctly, thus you get a tesselator error.

Generally you will not get a tesselator error just from the regeneration of the _pd file so look closely at your surfaces. This problem will only go away when the person or person's building that model make sure there are no surfaces that break the continuity rule. Rule number one in Class A surface design, absolute tangency without step occurance.(no ripples,etc..)