9999 1

The number of elements associated with a distributed load
exceeds the maximum number given on the SIZING, DIST LOADS
or FLUXES parameters. This usually happens in the
history definition, when a new distributed load is added, or
the number of elements is increased. Increase the value on
the parameter. Note that this cannot be done in a
restarted analysis, it must be done beginning with increment
zero.

9999 2

A line being read as a parameter line is unidentifiable.
This may be caused by illegal data or a mistyped line.

9999 3

The compilation of a user subroutine failed. The log file
contains information about the failure.

9999 4

The number of fixed displacement boundary conditions input
with the BC FILL or BC GENER options exceeds the maximum
specified with the SIZING parameter. Check the data and
change the maximum specification as necessary.

9999 6

The analysis cannot be run in the memory space available.

Adding the ELSTO parameter will store the element data on
the disk, thus reducing the amount of memory necessary.
Reducing the number of layers associated with beam and shell
elements and/or switching to reduced integration elements
will also reduce the amount of memory necessary.

9999 7

Normal finish caused by setting the STOP parameter.

9999 9

Too many points (more than 60) used in the BEAM SECT
parameter.  Either the number of branches in a beam section
is large, or the number of points per branch is large.
Reduce the relevant number(s).

9999 11

Not enough space to store the stiffness matrix. Use
bandwidth optimizer, if this has not already been done.
Change to the sparse solver or iterative solver if possible.

9999 12

Successful completion of job when a mesh display run is
completed and no subsequent analysis has been requested.

9999 13

Data errors have been detected during data input.  Refer to
output for location of error.  Likely causes are misspelled
keywords, mistyped lines or invalid input options.

9999 14

Negative relative density during equilibrium iterations for
the POWDER model. Decrease the load increment or use AUTO
STEP or AUTO INCREMENT schemes. If the problem still occurs
then check the material properties in the input data.

9999 15

Can not find the material data file in the job directory or
in the material database directory.  Check if the material
database and the material data exist. Make sure the material
data file name has an extension of ".mat".

9999 16

Element type being used is not supported by the user
subroutine hypela2.  Consult the description of hypela2
in Volume D for supported elements.

9999 17

Conjugate gradient solver (2) or Hardware solver (6) cannot
be combined with the OOC (out-of-core) parameter OR there is
not enough available memory to use this solver in-core.
Or Memory Allocation Failed for CASI solver.

9999 18

Error with MACHINING (METAL CUTTING) is found.
Possible reason and solutions:
1. Features that MACHINING does not support yet are used,
   Please turn off the unsupported feature if possible.
2. Error in cutter path data, check the APT/CCL file please.
3. If cutter motion type other than
   a) Point to Point (GOTO/),
   b) cycle motion (CYCLE/DRILL)
   has been used. Please use the correct CATIA setting to
   convert it into one of the above motion types.
4. Wrong load case definition option is used.

9999 19

Error in WELDING simulation. Inconsistency in WELD FLUX,
WELD PATH and WELD FILL DATA.
1. Check that weld flux id exists.
2. Check that weld path id associated with weld flux exists.
3. Check that weld filler id associated with weld flux
   exists.
4. Check that weld flux type (volumetric or surface) is
   consistent with distributed flux index

9999 20

Error in WELDING simulation. Position of weld flux is not
within specified weld path.
1. Check initial position of weld flux specified on
   WELD FLUX card.
2. Check that initial location is specified for weld flux when
   user subroutine uweldpath is used to specify weld path.
3. Weld flux may be moving out of range of the specified
   weld path. Check weld velocity and/or WELD PATH data.
   Extrapolation flag may be set to continue beyond last
   point on WELD PATH card.

9999 23

The wave front optimization scheme has lost continuity.
This indicates that the mesh is not continuous. Two or more
distinct bodies are defined in the same problem, and the
wave front renumbering scheme cannot handle this case.
Switch to the Sloan optimizer.

9999 24

No elements, springs or ties exist; the analysis cannot be
meaningful. Check your input, it is possible that the input
file is empty.

9999 25

Internal renumbering scheme for Lagrange multipliers does
not converge. Check if there are Herrmann elements where all
displacement degrees of freedom are prescribed. Try a
different optimization scheme. Otherwise Marc
system error; consult with an MSC.Software analyst.

9999 26

No element type chosen. Include ELEMENTS parameter.

9999 27

Failure in transformation, most probably due to bad
coordinates data.

9999 28

The contacting body is moving away from the bottom dead
center. Check current position and the bottom dead center
in the output file (jidname.out) and adjust your input data.

9999 29

The contacting body is not moving at all. Either the
bottom dead center is reached or the ZERO moving velocity
is encountered.  Check current position and the bottom
dead center or the velocity in the output file (jidname.out)
and adjust the input data.

9999 30

Selected surface entity not allowable in CONTACT model
definition option.  Check the input data.

9999 31

A surface has more entities than the maximum declared.
Increase the maximum number of entities on the CONTACT
model definition option.

9999 32

Circle segment data not consistent. Likely cause is that
radii calculated are not consistent with the given input.
Check input.

9999 33

There are more boundary nodes than the upper bound declared.
Increase the upper bound to the number of boundary nodes on
the CONTACT model definition option.

9999 34

Error in CONTACT model definition option. Either no
deformable body has been defined, or there are rigid
surfaces defined before deformable bodies. There must be at
least one deformable body on the CONTACT option. All
deformable bodies should be specified before rigid bodies.

9999 35

During initial surface approach, velocities were set to zero
before initial contact occurred.

9999 36

Data error in supplying the surface profile for a 2-D
deformable body. Check that elements specified for the body
form a continuous path. Make sure that there are no
inside-out or upside-down elements.

9999 37

Friction calculations with the CONTACT option are being
attempted without defining the relative sliding velocity
below which sticking is simulated. Input the relative
sliding velocity below which sticking is simulated on the
CONTACT option.

9999 38

The CONTACT model definition option is being exercised
without a time increment being defined. Enter the time
period using one of TIME STEP, AUTO TIME, AUTO STEP, AUTO
INCREMENT, DYNAMIC CHANGE or TRANSIENT history definition
options.

9999 39

Attempt to change contact data during a REZONE increment.
Only the elements associated with a deformable body can be
changed during rezoning. Other changes must be done through
the MOTION CHANGE or CONTACT TABLE history definition
options.

9999 40

During the approach stage of a CONTACT analysis, a rigid
body did not contact a deformable body within 1000 trials.
The time step per trial is chosen in such a way that the
displacement of the rigid body does not exceed 100 times
the error tolerance calculated by Marc.
The initial distance between the rigid and deformable
contact bodies is probably too large or the rigid body
velocity has an incorrect direction.

9999 41

Error in determining normal direction to a contact surface;
potential conflict with boundary condition. Try to remove
boundary conditions on nodes that come into contact. It is
better to use symmetry surfaces.

9999 42

The number of subdivisions of a 3-D arc must be greater than
1. Change your input in the CONTACT model definition option.

9999 43

The number of data points of a 3-D curve must be less than
or equal to the number of subdivisions. Change your input
in the CONTACT model definition option.

9999 44

The number of data points on a polyline must be equal to the
number of subdivisions minus 1. Change your input in the
CONTACT model definition option.

9999 45

The number of spline data points should be greater than 3
and less than 30. If the number is less than 3, convert
the spline segment into a line. If the number of points is
greater than 30, consider breaking the spline segment into
multiple spline segments.

9999 46

The number of Bezier data points should be greater than 3.
If the number of points is 2, then treat entity as a 4 node
patch (Type 7).

9999 47

The input data points are either too close or colinear.
Could not convert input to proposed surface type. Check
input in the CONTACT model definition option.

9999 48

The current patch is too small for program to find its
normal.  Check input of rigid contact surfaces. It is also
possible that deformation has caused a surface of a
deformable body to become very small.

9999 50
 
The normal direction of the tied node in deformable-
deformable contact has the same direction as a boundary
condition.  Try to remove boundary conditions of nodes that
come into contact.  It is better to use symmetry surfaces.
 
9999 51

END parameter is missing. This must be included in the
input file.

9999 57

In a contact body used in the beam-to-beam contact model
definition option a branch is detected. This is not
supported in the current version of the program.

9999 58

An analysis feature requested is currently not supported
by the single input file parallel version of Marc.

9999 59

An analysis feature requested is currently not supported
by the parallel version of Marc.

Unsupported features in the current parallel version
of Marc are: acoustic, auto therm
creep, bearing, buckling, beam-to-beam contact, segment-
to-segment contact, design sensitivity and optimization,
electromagnetics, explicit dynamics, fluid and its coupled
analysis, gap elements, harmonic, hydrodynamics, insert,
j-integral, out-of-core solver, unsymmetric solver,
radiation, convective terms in heat transfer, response
spectrum, rezoning, and steady state rolling.

9999 60

The listed contact body contains elements from the acoustic
region and elements from other regions.

9999 61

The listed contact body contains a combination of different
element types (e.g. solid+shell, solid+beam, beam+shell or
linear+quadratic). This is not supported.

9999 62

Beam bodies in the current version can not touch both beam
bodies and other bodies.

9999 67

The MSC password security has determined that
you are not allowed to run on this machine; possible reasons
are:

1) the choice of machine or current OS level is not
   compliant with the passwords;
2) the file "license.dat" in the MSC
   license directory contains wrong information;
3) the license directory has wrong access permissions.
4) all available licenses are in use - contact your local
   MSC.Software office to purchase additional licenses.
5) you are licensed to run MSC.AFEA and the interlock
   security has been violated because the input file was
   not created on the same machine or has been editted.
6) you are licensed to run an educational version and
   the maximum node limit has been exceeded.

9999 68

The MSC password security has determined that
you are not allowed to run on this machine; possible reasons
are:

1) the license has expired;
2) the file "license.dat" in the MSC
   subdirectory "security" contains wrong information;

9999 69

A 3rd party solver requested is not supported
in this version of Marc on this platform or
in multi-processor mode.

Use different Solver.

9999 70

Attempt to run a model larger than 500 nodes or 500 elements
using the demo version of Marc.

9999 71

While extracting outlines for remeshing, Marc
found more than 100 closed loops in one body. The closed
loops should be smaller than 100 at this time.

9999 72

While extracting outlines for remeshing, Marc
found more than 1000 nodes penetrating a contact body. The
slave surface probably has a very coarse mesh compared with
the master contact surface.

9999 75

More than 1 outline found for the 2D overlay mesher. Use
other meshers, such as the advancing front mesher, in order
to overcome the problem.

9999 76

Incompatible view factor data has been read in. The number
of segments read in is not consistent with the number
required.

9999 77

Error in restart run. There is an illegal change in
parameter or model definition options in the input file of
the restart run, such that the core allocation has changed.
This may also occur if restart data utilized is from a
different version of Marc.

9999 78

Error in restart run with user provided mesh data.
 
9999 80

Lap formation encountered during the analysis.

9999 81

Error in remeshing. A remeshing body is found to
have boundary conditions that are not supported.

Use new table input style to support global remeshing with
boundary conditions available after version 2005 for
remeshing with 3-D tetrahedral elements or 2-D with advancing
front mesher or Delaunay Triangle mesher.

9999 82

Number of faces of a cavity exceeds maximum estimated value.
Increase maximum number on CAVITY parameter.

9999 83

Error determining streamline. Check the input in
STREAM DEFINITION option. Make sure that the number of edges
is consistent between inner and outer surface, and that the
outer surface is truely the outer surface of this body.

9999 84

The density at the surface is less than or equal to zero in
recession/ablation calcuation. Either initial value of
density was not provided, or charred density was not
provided, or pyrolysis calculation is incorrect. Check input
data.

9999 85

The program is trying to perform an incremental data backup
for a nonlinear analysis. However, Parameter option ELASTIC
or SUBSTRUC indicates that this is a linear elastic analysis.
This is a conflict.

9999 100

Viewpoint chosen for plotting causes excessive distortion.
Probable causes are that the viewpoint chosen is either
within the body or too close to it.

9999 666

The POWDER model data input is incomplete. Check the input
in the POWDER option.

9999 1001

Connectivity exceeded at the node given in the message:

     "MORE THAN MAXNP JOINED TO NODE..."
    
during in-core assembly of elements. This aborts the program
at that point. If this occurs during a contact analysis, try
to activate single sided contact on the CONTACT option. This
can also occur if a contacted element has a user defined
tying on the contacted patch or edge.

Otherwise Marc system error; consult
MSC.Software analyst.

9999 1002

Connectivity exceeded at the node given in the message:

     "MORE THAN MAXNP JOINED TO NODE..."
    
during out-of-core assembly of elements. This aborts the
program at that point. If this occurs during a contact
analysis, try to activate single sided contact on the
CONTACT option. This can also occur if a contacted
element has a user defined tying on the contacted patch
or edge.

Otherwise Marc system error; consult
MSC.Software analyst.

9999 1003

Too many nodes joined to node in forming fluid coupling
matrix. Marc system error; consult MSC.Software
analyst.

9999 1004

Error occured when calculating equivalent nodal loads.
This is either due to an incorrect load type,
or the element going inside out. Check input for valid
load type for this element type or reduce step size.

9999 1005

Errors during stiffness or mass matrix generation. The
output will reveal which element has a particular problem.
If this occurs during the first assembly, it is due to input
errors associated with the COORDINATES, GEOMETRY or the
CONNECTIVITY model definition options. If this occurs during
a later increment, it is due to excessive deformation in the
element. Note that this can occur during the iterative
process, so that it is not always possible to visualize the
excessive deformation. Check the material behavior and the
magnitude of the incremental loads.

Suggestion :
------------
Activate the cut-back feature if using the AUTO LOAD, AUTO
STEP or AUTO INCREMENT solution schemes. This will allow the
analysis to automatically cut down the time step and try
again from the end of the last converged increment. For the
AUTO LOAD procedure, the increment numbers are maintained as
specified in the input.

9999 1006

Elastic reanalysis attempted with nonzero displacement
boundary conditions and boundary condition enforcement by
row/column elimination. This is not possible. Remove the
APPBC option.

9999 1007

Incorrect Film or Foundation load type given. See additional
messages in output to indicate which element, and correct
input

9999 1009

Error encountered in stress recovery. The output will reveal
which element has a particular problem. The error is usually
due to excessive deformation in the element. Note that this
can occur during the iterative process, so that it is not
always possible to visualize the excessive deformation.
Check the material behavior and the magnitude of the
incremental loads.

Suggestion :
------------
Activate the cut-back feature if using the AUTO LOAD, AUTO
STEP or AUTO INCREMENT solution schemes. This will allow the
analysis to automatically cut down the time step and to try
again from the end of the last converged increment. For the
AUTO LOAD procedure, the increment numbers are maintained as
specified in the input.

9999 1010

Error occured because emissivity was not defined for an
element edge or face that is used in a radiating cavity.
Correct input file.

9999 1021

Error in adding fluid mass to node. Marc system
error; consult an MSC.Software analyst.

9999 1030

Reference vector obtained by intersection of tangent plane
and orientation plane has zero length; cannot determine
preferred orientation. Check input in the ORIENTATION model
definition option.

9999 1031

Error while determining view factors in cavity. Make sure
that node numbers defining cavity are in consecutive order
in the input file.

9999 1040

Maximum number of element groups exceeded while using EBE
iterative solver. Increase the maximum number of groups
allowed in the SOLVER option.

9999 1041

Error in calculation of the spline constants during the 
reading of the material database.

9999 1042

Material database file could not be opened.

9999 1043

Too many materials from database used.

9999 1044

Curves in material database have too many points.

9999 1045

Error in calculation of the spline constants during the
reading of the material database.  Total number of curves
read from material database is too large.

9999 1050

Radiation is using an element type that is not supported by
cavity option - output indicates element type. Remove elements
of this type from cavity definition.

9999 1051

Error in calculating pyrolysis damage. Damage indicator is
less than zero or greater than 1.0

9999 1052

The pyrolysis appears to begin on the colder side. Possibly
the definition of interior and exterior surfaces is
incorrect.

9999 1053
 
The mass density is less than or equal to zero, either the
initial mass density was not defined via INITIAL PYROLYSIS
or the pyrolysis calculation is incorrect.

9999 1054

Too much ablation occured within this increment, and the
fixed time stepping procedure is used. Either switch to
adaptive time stepping or reduce the time step or increase
the amount of ablation allowed per time step.

9999 1055

Attempt to use table id which has not been defined

9999 1111

An error occurred during the outline search of a 2d contact
body.  In planar problems, check for correct anti-clockwise
numbering of all elements in the body.  Otherwise
Marc system error; consult MSC.Software analyst.

9999 1112

An error occurred during the adding of load provided in DMIG.
Marc system error; consult MSC.Software analyst.

9999 1113

An error occurred during adaptive meshing.
Marc system error; consult MSC.Software analyst.

9999 2004

The determinant of the stiffness matrix becomes zero or
negative when indicated node has been reached during the
Gaussian elimination phase of the solution process. This
means that the stiffness matrix is non-positive definite.
If this happens at the start of the analysis, the condition
is usually caused by the existence of rigid body modes.  It
may also be caused by incorrect material properties (e.g.
Poisson's ratio greater than 0.5; note that such situations
may arise through temperature dependence of properties). In
nonlinear cases, the structure may have buckled or reached a
plastic limit load. In rubber analysis, it may also be due
to the strain state being in a region where the input data
for the strain energy function is invalid. In contact
analysis with friction, lack of normal forces may result in
friction being absent. If desired, the program may be forced
to continue by use of the parameter PRINT or the model or
history definition option CONTROL. Either one of these
procedures may be used for restart. Whenever a non-positive
definite situation occurs one must exercise caution, as the
resultant numerical solution may be infeasible.

9999 2006

System error in multifrontal sparse solver. Marc
system error; consult MSC.Software analyst.

9999 2007

System error in CASI iterative solver. The output gives
additional messages. The problem may be due to rigid body
modes in the system. Switch to the multifrontal direct
solver if possibe.

9999 2008

Maximum connectivity has been exceeded during application of
tying constraints. If tyings are included, check the TYING
model definition and TYING CHANGE history definition
options.  This may also occur because of inconsistencies in
deformable- deformable contact; switch to single sided (K3
style) contact.  Marc system error; consult
MSC.Software analyst.

9999 2009

Not enough space to convert system from nodal blocks to row
format. Marc system error; consult MSC.Software
analyst.

9999 2011

Errors encountered during application of TYING equations.
Printout indicates specific problem.

9999 2012

One of the surface directions in Tying Type 22 (intersecting
shells of type 22) has zero length.  This is caused by bad
surface normal coordinates at one of the nodes being tied.

9999 2014

Search vector for eigen extraction is zero. Caused by
inadequate guess vector, or by asking for more eigenvalues
than the system contains. Do not attempt to extract more
modes than exist in the system. The number of modes is the
total number of degrees of freedom minus the number of
boundary conditions. Remember that contact to rigid bodies
effectively apply boundary conditions to the system, hence
removing potential modes.

9999 2015

Not enough work space for the fluid/solid interface
calculations.

9999 2016

Not enough work space for the fluid/solid interface
calculations.

9999 2017

Not enough work space for the fluid/solid interface
calculations.

9999 2020

Conjugate gradient iterative solver fails to converge within
the required number of iterations. This may be due to the
fact that there are rigid body modes in the system, or that
the system is numerically ill-conditioned, such as with
shell or membrane structures or Lagrange multipliers (i.e.
Herrmann elements).

Possible things to do:

1) Add pre-conditioner, incomplete Cholesky preferred;
2) Increase the number of iterations;
3) Set the number of iterations to a negative number. This
   will force the program to continue. If the solution is
   truly  poor, Marc will not converge in the
   outer Newton-Raphson iterations.

9999 2030

Unable to perform dynamic memory allocation for hardware-
provided direct sparse solver. Use reduced integration
elements and reduce the number of layers of shell elements.
If you still get this message, either increase the amount of
virtual/real memory on the computer, or switch to the
multifrontal sparse solver, or switch to the sparse
iterative solver.

9999 2031

Error occurred during initialization or factorization
process with hardware provided direct sparse solver. Switch
to one of the Marc solvers. Consult an
MSC.Software analyst.

9999 2032

The number of entries including fill-in is too large for the
sky-line solver. Use another solver.

9999 2033

Memory allocation error: not enough memory to perform
internal nodal renumbering with METIS.  To avoid this error,
try using either a different solver or nodal optimization
routine.

9999 2034

System error is occurred in PARDISO solver.
Marc system error; consult MSC.Software analyst.

9999 2035

Unable to perform dynamic memory allocation for
PARDISO direct sparse solver. Use reduced integration
elements and reduce the number of layers of shell elements.
If you still get this message, either increase the amount of
virtual/real memory on the computer, or switch to the
multifrontal sparse solver, or switch to the sparse
iterative solver.

9999 2036

An error occurred in internal nodal renumbering.
To avoid this error, try using either a different
renumbering scheme or different solver.

9999 2037

Error occurred during initialization or factorization
process with PARDISO solver. Switch to one of the Marc
solvers. Consult an MSC.Software analyst.

9999 2041

Error occurred during initialization or factorization
process with MF2 direct sparse solver. Switch
to one of the Marc solvers. Consult an MSC.Software analyst.

9999 2042

Error occurred during initialization or factorization
process with MUMPS direct sparse solver. Switch
to one of the Marc solvers. Consult an MSC.Software analyst.

9999 2043

Unable to perform dynamic memory allocation for MUMPS
direct sparse solver. Use reduced integration
elements and reduce the number of layers of shell elements.
If you still get this message, either increase the amount of
virtual/real memory on the computer, or switch to the
multifrontal sparse solver, or switch to the sparse
iterative solver.

9999 2109

Mode with zero energy is found during transient modal
response analysis. Probable cause is failure to use MODAL
SHAPE history definition option before DYNAMIC CHANGE is
used.  Check input file.

9999 2201

Attempt to recover a substructure, before solving the one
level higher superstructure.

9999 2304

Can not use Auto Increment with boundary conditions using
table input that it a function of time. Either switch to
Auto Step or remove time dependent table - load will be
controlled by Auto Increment procedure.

9999 2400

A node on the boundary of a deformable body tried to slide
out of surface definition in a contact analysis. Either the
segment of a rigid body is not large enough, in which case
increase the length, or the nodal points in the area of
contact have a large incremental displacement due to
possible instability. In the latter case, the suggestion
below may help under certain circumstances.

Suggestion :
------------
Activate the cut-back feature if using the AUTO LOAD, AUTO
STEP or AUTO INCREMENT solution schemes. This will allow the
analysis to automatically cut down the time step and to try
again from the end of the last converged increment. For the
AUTO LOAD procedure, the increment numbers are maintained as
specified in the input.

9999 2401

In a 3D contact analysis, a node touching a 3D NURBS cannot
be projected on the NURBS.  Marc system error:
consult an MSC.Software analyst.

9999 2402

A growing rigid body may have different growing factors in
x,y and z-direction in this release only if it is not
rotating.

9999 2403

A node with a local coordinate system (defined via
CYLINDICAL or TRANSFORMATION model definition option) comes
in contact or is being contacted. With the current version
this is not allowed.

Suggestion :
------------
Remove the local coordinate system and if needed, try to
replace local boundary conditions in global direction or
with the help of rigid bodies.

9999 2404

A growing rigid body should have relative size of 1.0 at
time 0.0 You should scale the initial size in the modelling
phase of your analysis.