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. 2 A line being read as a parameter line is unidentifiable. This may be caused by illegal data or a mistyped line. 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. 6 The analysis cannot be run in the memory space available. Either increase the work space on the SIZING parameter or modify the input. Adding the ELSTO parameter stores 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 also reduces the amount of memory necessary. Be sure that the best solver has been chosen for your problem and that the bandwidth is being minimized. 7 Normal finish caused by setting the STOP parameter. Try to request larger work space on the SIZING parameter than the required work space mentioned in the output file, remove the STOP parameter, and resubmit the analysis. 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). 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. Increase the maximum memory allowed with the MAXSIZE variable in the include file. 12 Successful completion of job when a mesh display run is completed and no subsequent analysis has been requested. 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. 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, check the material properties in the input data. 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". 16 Element type being used is not supported by the user subroutine hypela2. Consult the description of HYPELA2 in MSC.Marc Volume D: User Subroutines and Special Routines for supported elements. 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. 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. 24 No elements, springs or ties exist; the analysis cannot be meaningful. Check your input, it is possible that the input file is empty. 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. 26 No element type chosen. Include ELEMENTS or SIZING parameter. 27 Failure in transformation, most probably due to bad coordinates data. 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. 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. 30 Selected surface entity not allowable in CONTACT model definition option. Check the input data. 31 A surface has more entities than the maximum declared. Increase the maximum number of entities on the CONTACT model definition option. 32 Circle segment data not consistent. Likely cause is that radii calculated are not consistent with the given input. Check input. 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. 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. 35 During initial surface approach, velocities were set to zero before initial contact occurred. 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. 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. 38 The CONTACT model definition option is being exercised without a time increment being defined. Enter the time period using either TIME STEP, AUTO TIME, AUTO STEP, AUTO INCREMENT, DYNAMIC CHANGE ,or TRANSIENT history definition options. 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. 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. 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. 42 The number of subdivisions of a 3-D arc must be greater than 1. Change your input in the CONTACT model definition option. 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.

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. 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. 46 The number of Bezier data points should be greater than 3. If the number of points is 2, treat entity as a 4-node patch (Type 7). 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. 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. 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. 51 END parameter is missing. This must be included in the input file. 52 The number of elements on sizing line is too small for beam-beam contact - increase number to twice the number of elements. or The number of nodes on sizing line is too small for beam-beam contact - increase number to twice the number of nodes in model. 53 The number of contact body entities is larger than the maximum number allowed in the input file. Increase the maximum number allowed in the second field of the second data block of the CONTACT model definition option. See MSC.Marc Volume C: Program Input, Chapter 3. 54 The number of contact body entities is larger than the maximum number allowed in the input file. Increase the maximum number allowed in the second field of the second data block of the CONTACT model definition option. See MSC.Marc Volume C: Program Input, Chapter 3. 55 The number of nodes on the SIZING parameter must be increased to accommodate beam-beam contact. 56 The number of elements on the SIZING parameter must be increased to accommodate beam-beam contact. 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. 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, adaptive, auto therm creep, axisymmetric to 3-D data transfer (AXITO3D), bearing, buckling, beam-to-beam contact, design sensitivity and optimization, electromagnetics, explicit dynamics, fluid and its coupled analysis, gap elements, harmonic, hydrodynamics, j-integral, out-of-core solver, radiation, response spectrum, and rezoning. 60 The listed contact body contains elements from the acoustic region and elements from other regions. 61 The listed contact body contains a combination of different element types (solid+shell or solid+beam or beam+shell). This is not supported. 62 Beam bodies in the current version cannot touch both beam bodies and other bodies. 67 Marc 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 Marc subdirectory "security" contains wrong information. 3. The directory "security" has wrong access permissions. 4. All available licenses are in use - contact your local MSC.Software office to purchase additional licenses. 68 Marc 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 Marc subdirectory "security" contains wrong information. 70 Attempt to run a model larger than 500 nodes or 500 elements using the demo version of Marc. 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. 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. 73 While extracting outlines for remeshing, Marc found that more than 1000 nodes are needed for interpolation of the new surface. Consult MSC.Software to change the limit. 74 While extracting outlines for remeshing, Marc found that more than three times the number of previous mesh nodes are needed for the new outline. This indicates that the user is trying to remesh with a very small element size compared with the original element size. Consult MSC.Software to change the limit. 75 More than 1 outline found for the 2-D overlay mesher. Use other meshers, such as the advancing front mesher, in order to overcome the problem. 76 Incompatible view factor data has been read in. The number of segments read in is not consistent with the number required. 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. 78 Error in restart run with user provided mesh data. 79 Error in memory allocation. 80 Lap formation encountered during the analysis. 81 Error in remeshing. Nodes belonging to a body which is being remeshed have boundary conditions which cannot be transported correctly to the new mesh. 82 Number of faces of a cavity exceeds maximum estimated value. Increase maximum number on CAVITY parameter. 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. 666 The Powder model data input is incomplete. Check the input in the POWDER option. 1001 Connectivity exceeded at the node given in the message: MORE THAN MAXNP JOINED TO NODE... during in-core assembly of elements. This aborts Marc 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. 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 Marc 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. 1003 Too many nodes joined to node in forming fluid coupling matrix. Marc system error; consult MSC.Software analyst. 1005 Errors during stiffness or mass matrix generation. The output reveals 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. 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. 1009 Error encountered in stress recovery. The output reveals which element has a particular problem. The error is usually due to excessive deformation in the element. 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. 1021 Error in adding fluid mass to node. Marc system error; consult an MSC.Software analyst. 1030 Reference vector has zero length; cannot determine preferred orientation. Check input in the ORIENTATION model definition option. 1031 Error while determining view factors in cavity. Make sure that node numbers defining cavity are in consecutive order in the input file. 1040 Maximum number of element groups exceeded while using EBE iterative solver. Increase the maximum number of groups allowed in the SOLVER option. 1041 Error in calculation of the spline constants during the reading of the material database. 1042 Material database file could not be opened. 1043 Too many materials from database used. 1044 Curves in material database have too many points. 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. 1051 Error in calculating pyrolysis damage. Damage indicator is less than 0 or greater than 1.0. 1052 The pyrolysis appears to begin on the colder side. Possibly the definition of interior and exterior surfaces is incorrect. 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. 1111 An error occurred during the outline search of a 2-D 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. 2004 The determinant of the stiffness matrix becomes zero or negative when the indicated node has been reached during the Gaussian elimination phase of the solution process. This means that the stiffness matrix is nonpositive 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 (for example, Poisson's ratio greater than 0.5; note that these 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, Marc may be forced to continue by use of the PRINT parameter or the CONTROL model (or history) definition option. Either one of these procedures may be used for restart. Whenever a nonpositive definite situation occurs one must exercise caution, as the resultant numerical solution may be infeasible. 2007 System error in sparse conjugate gradient solver. Marc system error; consult MSC.Software analyst. 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. 2009 Not enough space to convert system from nodal blocks to row format. Marc system error; consult MSC.Software analyst. 2011 Errors encountered during application of TYING equations. Printout indicates specific problem. 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. 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. 2015 Not enough work space for the fluid/solid interface calculations. Increase the space specified on the SIZING parameter, 2016 Not enough work space for the fluid/solid interface calculations. Increase the space specified on the SIZING parameter. 2017 Not enough work space for the fluid/solid interface calculations. Increase the space specified on the SIZING parameter. 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. 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

forces Marc to continue. If the solution is truly poor, Marc does not converge in the outer Newton-Raphson iterations. 2030 Unable to perform dynamic memory allocation for hardware-provided direct sparse solver. Decrease the amount of memory requested on the SIZING parameter down to the number printed in the output file (jidname.out). 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, switch to the multifrontal sparse solver, or switch to the sparse iterative solver. 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. 2032 The number of entries including fill-in is too large for the sky-line solver. Use another solver. 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. 2201 Attempt to recover a substructure, before solving the one level higher superstructure. 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 allows 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. 2401 In a 3-D contact analysis, a node touching a 3-D NURBS cannot be projected on the NURBS. Marc system error: consult an MSC.Software analyst. 3001 The maximum number of increments specified on the CONTROL option has been reached. Note that increment zero has to be considered as an increment as well. 3002 Analysis has failed to converge to required convergence tolerances. One of several error conditions has been detected and the run aborted. The output specifies additional messages. 3003 Analysis could not be finished because the maximum number of increments defined in an adaptive loading procedure has been reached or the calculated step is too small. The user should increase the number of increments allowed during the automatic loading procedure. 3004 Successful completion. No additional incremental data was found and the analysis is complete. 3005 Successful completion. The CASE COMBIN(ATION) model definition option was used. 3006 Successful completion. The user requested that the restart file be read and that either the results be printed or a post file be created. 3007 A restart analysis has been requested at an increment that is not on the restart file. The previous output will give the message RESTART DATA AT INCREMENT XX The new input file should specify the increment number XX on the RESTART model definition option. 3008 Contact caused the restarting of an increment an excessive number of times. This may be due to separation or increment splitting. Increase the separation force or reduce the size of the step. An

alternative is to increase the number of recycles allowed. 3009 Time step size becomes too small to continue the analysis. This may be due to having too many cutback times in current increment. An alternative is to increase the allowed maximum number of cutback times. 3010 Successful completion of design sensitivity analysis. 3011 Successful completion of design optimization process. 3012 No constraints activated at vertex of design space. Enter bounds on design variables, as these are probably missing. 3013 User element is not supported in design sensitivity analysis or design optimization process. 3014 For design optimization with composite layer thicknesses as design variables, the initial thicknesses may not be given in terms of percentages. Enter only estimated values, as it is not necessary to enter accurate values in this case. 3015 Unable to reduce the time step below the minimum value allowed, and to still satisfy the user criteria in the AUTO STEP history definition option. Either change the criteria or reduce the minimum time step allowed. 3016 The element chosen is not supported in the Lorenzi j-integral calculation. This element type must not be used in the crack region of the model, but it can be used outside the crack region. 3020 Job stopped immediately due to user intervention. 3021 Job stopped at end of increment due to user intervention. 3025 Normal ending of Marc-reader. 3026 Marc-reader does not support substructures or superelements. 3027 Marc-reader does not support: 1. UFCONN user subroutine; 2. Element type chosen. 3. Reading of a restart file. Set relevant field to 1 in Marc input file. 3300 The eigenvalue extraction did not converge within the maximum number of iterations allowed. Increase the maximum number of cycles or tolerance in the MODAL SHAPE, MODAL INCREMENT, BUCKLE, or BUCKLE INCREMENT options or, if applicable, change from the inverse power sweep to the Lanczos method using the BUCKLE parameter. 3301 Eigenvalue analysis requested, but either mass is zero or initial stress stiffness is zero. For dynamic modal analysis, make sure that there is mass in the system. This can be from either entering a mass density or mass points. For buckling analysis, make sure that load has been previously applied to the structure, such that stresses are present. 3302 Nonpositive definite system occurred during Lanczos eigenvalue extraction for buckling analysis. Decrease the applied load before the buckling analysis is performed or switch to the inverse power sweep method using the BUCKLE parameter. 4001 Sequential I/O error: problems with opening, reading or writing files. Check file access permissions and available disk space. If on a restart or post file, there was an attempt to read an increment which is not on file. Otherwise, Marc system error; consult an MSC.Software analyst. 4002 Cannot find jidname.pass file which is needed for automatic restart run. This is an internal file and should not be removed. 4003 Cannot read any "continue" statement in jidname.rst file for the automatic restart run. Check jidname.dat to make sure there are loadcases to run the problem. 4004 Cannot find the jidname.rst file which is needed for automatic restart run. This is an internal file and should not be removed. 4009 Sequential I/O error, unable to open file. Either a file requested is not found, or there is a system protection against opening the file. Make

sure that you have read/write permission in the current directory or that the file has not been opened by another process, for example, Mentat. If this is a mesh data file, the mesher may have failed to create a mesh. 4031 Unable to obtain the memory requested during a dynamic memory request. This can be due to the following reasons: 1. The maximum allowed amount of memory is exceeded. This is specified by the MAXSIZE variable in the include file in the tools directory in the Marc install directory. MAXSIZE specifies the memory in million words, multiply by 4 to get the amount in megabytes. 2. There is not enough free memory on the system. If the memory available is not enough for an in-core solution, Marc attempts to perform the solution out-of-core. In this case, some data which normally would be stored in memory is stored on the hard disk (which could slow down the analysis considerably). The memory request fails if there is still not enough memory for the analysis. 4209 The option of reading radiation VIEW FACTORs from a file is specified in the related model definition option, but either the given file could not be opened (e.g., no read permission) or, the input option -vf was not used to specify the file. 4210 Restart requested, but no restart file was provided. Add "-rid" parameter when submitting the job. 4211 Substructure analysis requested, but no database was found. Add "-sid" parameter when submitting the job. 4212 AUTO STEP does not support electromagnetics analysis. Try to use other auto loading strategies. 4213 AUTO STEP does not support soil material models. Try to use other auto loading strategies. 4214 AUTO STEP does not support powder material models. Try to use other auto loading strategies. 5001 The number of nodes created during adaptive meshing is greater than the number specified on the ADAPTIVE parameter. Either increase the number on the ADAPTIVE parameter or reduce the number of levels allowed with the ADAPTIVE model definition option. The analysis can be forced to continue using the ADAPTIVE parameter. 5002 The number of elements created during adaptive meshing is greater than the number specified on the ADAPTIVE parameter. Either increase the number on the ADAPTIVE parameter or reduce the number of levels allowed with the ADAPTIVE model definition option. The analysis can be forced to continue using the ADAPTIVE parameter. 5003 Adaptive meshing is not available for the element type used. Either use a valid element type, remove ADAPTIVE option or use ADAPTIVE option with a set specifying elements of a valid type. 5004 Adaptive meshing is not available for the element type used. Either use a valid element type, remove ADAPTIVE option or use ADAPTIVE option with a set specifying elements which are of a valid type. 5005 Number of boundary conditions created during adaptive meshing exceeds the number specified on the SIZING parameter. Increase the number of boundary conditions specified on the SIZING parameter. 5006 The number(s) of nodes and/or elements created during adaptive meshing is greater than the numbers specified on the ADAPTIVE parameter. Either increase the numbers on the ADAPTIVE parameter or increase the element edge length on the ADAPT GLOBAL option. The analysis can be forced to continue using the ADAPTIVE parameter. 5007 Error in performing adaptive meshing with elastic foundations or

films; Marc system error; consult an MSC.Software analyst. 5008 The number of elastic foundations or films created during adaptive meshing exceeds the number specified on the ADAPTIVE parameter. Add FOUNDATION model (or history) or FILMS model (or history) definition option. 5009 Error in memory allocation while performing adaptive meshing. Marc system error; consult an MSC.Software analyst. 5010 System error during adaptive meshing. Marc system error; consult an MSC.Software analyst. 5011 Unable to find surface for adaptive meshing with shells if the ATTACH NODE model definition option is used. Check definition of surfaces. 5012 Unable to find surface normal when using the ATTACH NODE model definition option with 3-D adaptive meshing. Check definition of surfaces. 5013 The command string to call mesher is too long. It is likely that your path to the mesher is too long or your filename is too long. 5023 Not enough space on SIZING parameter to create new mesh. Increase workspace available. 5024 Not enough space on SIZING parameter to perform rezoning. Increase workspace available. 5025 The node being printed is used in the TRANSFORMATION model definition option and also belongs to an element which is subdivided in the ADAPTIVE option. This is not allowed. 5050 Number of divisions in the x-direction exceeds maximum needed. Increase the element target length on ADAPT GLOBAL option. 5051 Number of divisions in the y-direction exceeds maximum needed. Increase the element target length on ADAPT GLOBAL option. 5052 Something is wrong with start point in mesher. Reduce the element target length on ADAPT GLOBAL option. 5053 Something is wrong with projection in mesher. Reduce the element target length on ADAPT GLOBAL option. 5054 Something is wrong with start point in mesher. Marc system error; consult an MSC.Software analyst. 5055 Something is wrong with the mesh outline; outline is not complete. Marc system error; consult an MSC.Software analyst. 5056 Cannot mesh with current edge length. Try smaller edge length and, if necessary, increase maximum number of elements and nodes on the ADAPTIVE parameter. 5057 Error found from 3-D hexmesher. Check error message in file jidname.log. 5058 2-D overlay mesher failed to create a mesh after many trials. This may be due to small element size or wrong outlines. 5059 The mesher failed to create a mesh. Check error messages in the output file (jidname.out) or in the log file. 5060 Can not find the mesh data file. The mesher might be hanging due to memory problem or the disk space is full. 5061 The mesh data file is not complete. The mesher might be hanging due to memory problem or the disk space is full. 5062 The solver has been waiting for remeshing status file. Check if Run_sleep program is running properly. 5063 The element size for remeshing is found to be zero. You need to specify the element size or number of elements needed for remeshing. Check input. 9999 The log or status files are incomplete. The exit code is not available.