fatal error

[Deleted_U_Intel]

Every once ina while, especially when I am using the debugger, I get the following error:

Compiling with Intel Fortran Compiler 10.0.025 [IA-32]...
ifort /nologo /Zi /Od /module:"Debug" /object:"Debug" /traceback /check:bounds /libs:qwin /dbglibs /c /Qvc8 /Qlocation,link,"C:Program FilesMicrosoft Visual Studio 8VCin" "C:UsersJohn SullivanA_WorkDocumentsVisual Studio 2005My ProjectswkareaHEVHEV_2c.f90"
ifort /nologo /Zi /Od /module:"Debug" /object:"Debug" /traceback /check:bounds /libs:qwin /dbglibs /c /Qvc8 /Qlocation,link,"C:Program FilesMicrosoft Visual Studio 8VCin" "C:UsersJohn SullivanA_WorkDocumentsVisual Studio 2005SubroutinesHEV_world.f90"
Linking...
Link /OUT:"DebugHEV.exe" /INCREMENTAL:NO /NOLOGO /MANIFEST /MANIFESTFILE:"C:UsersJohn SullivanA_WorkDocumentsVisual Studio 2005My ProjectswkareaHEVHEVHEVdebughev.exe.intermediate.manifest" /DEBUG /PDB:"C:UsersJohn SullivanA_WorkDocumentsVisual Studio 2005My ProjectswkareaHEVHEVHEVdebughev.pdb" /SUBSYSTEM:WINDOWS "DebugHEV_2c.obj" "Debugplotit4.obj" "DebugHEV_world.obj" "DebugHISTOGRAM.obj" "C:UsersJohn SullivanA_WorkDocumentsVisual Studio 2005LibraryNewLibLib1.lib"
Link: executing 'link'
LINK : fatal error LNK2023: bad DLL or entry point 'msobj80.dll'

What is this due to? At this time, the only effective way I have of dealing with it is to reboot my machine. Currently, I am using Windows Vista Home Premium

Thank you!

John

[Steven_L_Intel1]

This is a bug in Visual Studio 2005. Installing VS2005 SP1 generally fixes it. See the compiler installation guide for a link.

[truelies]

I also have this error under windows xp:

Error 1 fatal error LNK2023: bad DLL or entry point 'msobj80.dll' LINK


Where can I find visual studio 2005 sp1 for windows xp? Thank you!

[Steven_L_Intel1]

Visual Studio 2005 SP1

[eos_pengwern]

The first time I saw this message (i.e. LNK2023 etc.), I upgraded to VS 2005 SP1 and it went away. Now it's back again, though I haven't done anything to VS in the meantime.It only occurs when I compile in Debug mode (Release mode is fine).

I tried recompiling in Debug mode in the first place because with my previous debug build (a couple of weeks ago), the debugger seemed to be ignoring all break points. Is there likely to be a connection between these two observations?

Thanks.

[eos_pengwern]

Update:

After reading John's related post in the "Static library" thread (message i.d. 30239289), I decided to reboot my computer and hey presto! the problem has gone away. Both problems, in fact, because now my breakpoints work as well.

I don't know whether this lies behind some of the problems, but I've noticed that there are in fact two different versions of msobj80.dll installed on my PC:

- in C:Program FilesMicrosoft Visual Studio 8VCBin, I have 8.0.50727.42, built on 9/23/05.

- in C:Program FilesCommon FilesMicrosoft SharedVSA8.0VsaEnv, I have 8.0.50727.762, built on 12/1/06.

My link.exe file in the VCBin directory has the .42 version number, so this at least is consistent. Even so, would it be an idea to update the older one, or should I just leave well alone?

[Steven_L_Intel1]

I would leave it alone.

[a_j_payne]

hi

i have exactly the same problem as john and others report. the problem went away for a while after installing SP1 but is back now. i will try rebooting as s-morris suggests, although this is hardly a satisfactory fix.

tony

[a_j_payne]

well it worked. i have a feeling that this error crops up when a the solution/project is opened in a particular way (eg double clicking on the .sln file). closing the solution before leaving MVS seems to be safer (and when restarting work opening MVS and then opening the solution/project within MVS).

tony

[bredsj]

Quoting - a.j.payne@bristol.ac.uk

well it worked. i have a feeling that this error crops up when a the solution/project is opened in a particular way (eg double clicking on the .sln file). closing the solution before leaving MVS seems to be safer (and when restarting work opening MVS and then opening the solution/project within MVS).

tony

Has anybody found a permanent fix to this problem yet? I'm also now getting this linker message and I have Service Pack 1 installed.

[Kevin_D_Intel]

Yes. There is a permanent fix discussed here involving copying the msobj80.dll. This will be included the next 10.1 update tentatively to be announced in the coming week.