Cancel
Showing results for 
Search instead for 
Did you mean: 

Error 1019 (OPNFL)

Pioneer
Pioneer

I have been running a fairly large assembly simulation successfully for the past couple weeks, in FEMAP (NX NASTRAN) changing gussets and such to determine the best design.  Last night I received the error listed above.  The only change between my last successful run and the current run is that I saved as a new file in the same folder, deleted some geometry, imported the updated geometry, replaced some rigid elements and load locations, and remeshed as needed.  I don't get any error message in FEMAP, or any message saying the run ended.  The output screen gets as far as printing out the number of elements translated, then nothing, elapsed time shows as 00:00:00.  I am unable to open the F04 or F06 file within FEMAP, using windows explorer I still can't open the F04 file, but the F06 file reads as follows:

 

---------------

***USER FATAL MESSAGE 1019 (OPNFL)

    FORTRAN UNIT OPEN ERROR

    IOSTAT =            2, No such file or directory (errno=2)

---------------

 

I do get a log file, after listing the date and time for beginning the analysis I get the following two lines, which I suspect might be significant:

 

----------------

NX NASTRAN(iosdec): No such file or directory

forrtl: severe(66): output statement overflows record, unit -5, file Internal Formatted Write

----------------

 

Following that it runs through the Image/PC/Routine/Line/Souce columns, etc.

 

 

I'm a little lost on what exactly is happening here, and my google searches on the topic have been fairly fruitless.  Can anyone shed some light on what's going on?

7 REPLIES

Re: Error 1019 (OPNFL)

Phenom
Phenom
I hope you sorted this out for yourself since you posted, but if not.... there are some carry over aspects of Fortran where your choice of directory lengths and chosen characters still have practical limits. I suggest you radically simplify the folder/directory and the actual file name itself (shorter length and simplest characters) to be sure you haven't exceeded an obscure Fortran format limit when Nastran runs.

Re: Error 1019 (OPNFL)

Pioneer
Pioneer

I ended up reverting to a previously saved working file, saving as something else, re-applying my changes, and it worked.  Out of coincidence the name of the new saved file was shorter, so you are probably correct.  Thanks!

Re: Error 1019 (OPNFL)

Experimenter
Experimenter

Hi everyone, 

Sorry to resurface this thread. I have the same fatal error in my fo6 log but mine says IOSTAT : input/output error. Haven't been able to find any other community thread related to this error. The analysis runs and I get no error messages but I can't load results. When I click on f06 it shows the fatal error 1019 line and then fortran unit open error and then IOSTAT input/output error.

Thanks in advance

Re: Error 1019 (OPNFL)

Siemens Phenom Siemens Phenom
Siemens Phenom

The most likely sources for this error are running out of disk space, permission issue for the location Nastran is trying to write, and path or file naming issues.

File naming issues could be things like spaces or other odd chacters in the directory path as well as very long path or name.

It might help to know what version of Femap/Nastran you are using and if you could post the log file, that would certainly help.

Re: Error 1019 (OPNFL)

Experimenter
Experimenter

Hi fembracking,

I'm using the Femap stdudent version 11.4.1 and there's around 15GB space, I'll check the write properties and directory path names.

Thanks

Re: Error 1019 (OPNFL)

Experimenter
Experimenter

Here's the screenshot of the logfile

Re: Error 1019 (OPNFL)

Phenom
Phenom

Hi there,

In my view, your model and path name are still "slightly risky", and I don't know why the analysis seems to be running (= storing some analysis files) in the "C:\program files\siemens"  directory (which might not be writable for you).  The default behaviour of Femap is to put some of the temporary analysis files in whichever directory was last used to save anything from within Femap (model, material library, API, macro - whatever) and your analysis appears to be writing info in the Siemens directory.  Create a simple directory (not "on the desktop"), move the model there, open the model there and then save something from Femap in that same directory (maybe Save As chassis2) before running the analysis.

Also (less likely, if you have already had stuff running): go to the Femap installation directory, then Nastran directory, then Conf directory and open nast11.rcf (eg. using Notepad).  Make sure there is an sdir line eg:

sdir=d:\scratch

The major Nastran temporary scratch files are stored here during the analysis.

Make sure the directory exists and is fully owned/writable by you as a user.

 

Cheers.