hexagon logo
Register Sign in
  • State Not Answered
  • Replies 9 replies
  • Subscribers 4 subscribers
  • Views 142 views
  • Users 0 members are here
Options
Related

Fatal message 6352 Same model ran on 2013, but on versions 2017 and 21019 this problem exists.

Viplava
 *** USER WARNING MESSAGE 285 (DML)
   FATAL ERRORS WERE FOUND WHILE READING THIS BEGIN SECTION
   MODEL SUMMARY DOES NOT INCLUDE COUNT OF FATAL ENTITIES
 ^^^   
 ^^^ >>> IFP OPERATIONS COMPLETE <<< 
 ^^^   
 *** SYSTEM FATAL MESSAGE 6352 (IFP6PCMP)
   LOGIC ERROR: 9212
   USER ACTION: CONTACT MSC.SOFTWARE CLIENT SUPPORT.
   PROGRAMMER INFORMATION: KPCOMP=     1, NPCOMP=     0
0FATAL ERROR
Parents
  • 0
    Great.... 444=9 should also work. 444=0 would switch back to the 2012 ifp Processing.
    Personally I would prefer using 444=9 as it uses the new IFP processing which is much faster and better checks in place for input file checking.
    This is useful as it tells the user to check if he has accidentally placed incorrect values in the fields... Once he has confirmed that everything is correct, he can add the cell to run the job.
     
Reply
  • 0
    Great.... 444=9 should also work. 444=0 would switch back to the 2012 ifp Processing.
    Personally I would prefer using 444=9 as it uses the new IFP processing which is much faster and better checks in place for input file checking.
    This is useful as it tells the user to check if he has accidentally placed incorrect values in the fields... Once he has confirmed that everything is correct, he can add the cell to run the job.
     
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement