The compile suddenly brings strange errors.

First compile brings:  * File i-o error: program.idy

then the 2nd compile brings: program.OBJ : error LNK2001: unresolved external symbol __mFerr3

Does anyone have an idea?

Regrds,

Georg

The compile suddenly brings strange errors.

First compile brings:  * File i-o error: program.idy

then the 2nd compile brings: program.OBJ : error LNK2001: unresolved external symbol __mFerr3

Does anyone have an idea?

Regrds,

Georg

Hello Georg, after closing netexpress, please delete all files in the debug und release directory and recompile your project and show the result!

On what os do you had install netexpress 5.1 ? Win7 - Win10 or Win11

Do you remember, long time we had seen us in Bad Honnef!?

Hi Georg,

When you state that this problem "suddenly" appeared is this implying that this program used to compile without errors and now this error occurs?

A couple of questions:

What has changed between the time where it worked and the time where it fails?
-  product update?
-  program change?
-  environment change?

Does this happen on all programs or just this one?
If it happens on all programs then you might want to try doing a Repair on Net Express.

Yes, I remember. We looked at List&Label. Now I use Version 27.

Regards, Georg

ok, yes, i use also LiLa 27 und all files/data are under sql, no isam-files.
Do you use also Visual Cobol x.x?
It will be time to have a new contact! What do you mean?

Hi Georg,

When you state that this problem "suddenly" appeared is this implying that this program used to compile without errors and now this error occurs?

A couple of questions:

What has changed between the time where it worked and the time where it fails?
-  product update?
-  program change?
-  environment change?

Does this happen on all programs or just this one?
If it happens on all programs then you might want to try doing a Repair on Net Express.

Chris,

after the repair I have delete the release and debug folder.

The first compile of the project was ok, but the 2nd  brought the  file i-o error.

Are the release and debug folders on a network drive by any chance? We have seen a similar issue before when a network drive was being used. If you are compiling to a network drive can you try your C drive instead?

It is a SSD in the NB.

Anyway I will copy the project to the c: drive and recompile it.

I will inform you about the result immediately.

Unfortunately all programs have the message * File i-o error: progname.idy

Does this same error occur if you open up one of the Net Express Sample projects under C:\\program files (x86)\\micro focus\\Net Express 5.1\\Examples\\Net Express IDE, e.g ADSAMP?

NO, this runs ok, but why now are both folders on the c drive

Chris,

is it possible that my .app file is corrupted. Is there a way to fix it.

The .app files are standard MF indexed files. From a NX command prompt you could run the rebuild command to check the file.

rebuild /f filename.app

For clarification, you moved all of your project folders and output paths to the C drive and it still fails?

You could also try to create a new project and place a simple helloworld program into it and see if that works. 

The rebuild brought nothing but the new project with one of the programs from the "not running project" was OK.

What now? The Project has over 250 files. Do I have to redo the whole project???

I am not sure what to do here as I have no idea what is causing the problem. If it happened after a Windows update then I am not sure what the update did to your project. I would hate for you to recreate the entire project and then have the error occur again.

To continue to troubleshoot this, after you get the error, can you try to delete the .idy files in the debug folder? If you cannot delete them then it probably means that they are being locked and this is why it cannot create them. If you can delete them then try the rebuild again to see if it is successful with the files gone.

I can delete all .idy files but without a positive result.

If I  have to change a program I create a project and compile it. it's a bypass for now.

I will investigate further.