Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

Unable to write result files (Internal Programming Error in virfile.c)

Hello all,

I get error code below after a converged NLSTAT analysis, hence result files could not be written. Same problem occurs after restart run of last increment of that analysis on different workstations (there is plenty of disk space by the way).

   *** Nonlinear solution has converged ***

(Scratch disk space usage for starting iteration = 2679 MB)


*** INTERNAL PROGRAMMING ERROR ***
in file 'virfile.c', at location # 318.

Attempt to read past file size

************************************************************************
OptiStruct error termination report printed to file
'TRS30_YS_R4-TYX_RBE3_restart.stat'.

Unable to find an attachment - read this blog

Find more posts tagged with

English

OptiStruct

Accepted answers

All comments

Altair Forum User

Hi @yhamurisci

Can you change working directory and try one more time?

If you still face the error, please share the model file.

Altair Forum User

Hi Prakash,

I also changed the working directory with shorter path by changing the computer, but it didn't work.

Unfortunately, the model file is too large to share.

Thanks for your support.

Regards.

Altair Forum User

@yhamurisci

OK, I will check if I can do something to fix the error without sharing the file.

Can you deactivate or remove all result outputs and check if that helps?

Altair Forum User

The problem also occurs if you have 2nd order elements with SMP parallelization.

This is fixed in HyperWorks 2017. If you have 2nd order elements in your model, try to update HyperWorks to 2017 and try again.

Altair Forum User

Yes, the model includes 2nd order elements as usual but the difference is this model also has RBE3 elements.

We had so many NLSTAT runs with 2nd order tetra elements, but we got this error for the first time when RBE3 elements are used.

Regards.

Altair Forum User

@yhamurisci

This happens with 2nd order and smp parallelization and/or due to requesting of GPFORCES and other outputs when using LGDISP.

Since you are working with your local support, let us know if you need any help from us /emoticons/default_smile.png' srcset='/emoticons/smile@2x.png 2x' title=':)' width='20'>

Altair Forum User

@yhamurisci

This happens with 2nd order and smp parallelization and/or due to requesting of GPFORCES and other outputs when using LGDISP.

Since you are working with your local support, let us know if you need any help from us /emoticons/default_smile.png' srcset='/emoticons/smile@2x.png 2x' title=':)' width='20' />

That's it /emoticons/default_smile.png' srcset='/emoticons/smile@2x.png 2x' title=':)' width='20' /> After cancelling GPFORCES request, problem was resolved.

Thank you very much for your support /emoticons/default_smile.png' srcset='/emoticons/smile@2x.png 2x' title=':)' width='20' />

Altair Forum User

That's it /emoticons/default_smile.png' srcset='/emoticons/smile@2x.png 2x' title=':)' width='20'> After cancelling GPFORCES request, problem was resolved.

Thank you very much for your support /emoticons/default_smile.png' srcset='/emoticons/smile@2x.png 2x' title=':)' width='20'>

Thank you for updating /emoticons/default_smile.png' srcset='/emoticons/smile@2x.png 2x' title=':)' width='20'>