- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After a long absence, I am once again being plauged by the error message below. To date my best response is to reboot the machine. But it is becoming sufficiently frequent that rebooting is becoming impractical.
What can I do about this issue?
My operating system is Windows Vista - Home Premium.
Thank you!
John
Compiling with Intel Fortran Compiler 10.1.013 [IA-32]... ifort /nologo /Zi /Od /gen-interfaces /warn:interfaces /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_2f_1.f90" ifort /nologo /Zi /Od /gen-interfaces /warn:interfaces /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:NO /DEBUG /PDB:"C:UsersJohn SullivanA_WorkDocumentsVisual Studio 2005My ProjectswkareaHEVHEVHEVdebughev.pdb" /SUBSYSTEM:WINDOWS /IMPLIB:"C:UsersJohn SullivanA_WorkDocumentsVisual Studio 2005My ProjectswkareaHEVHEVHEVdebughev.lib" "DebugHEV_2f_1.obj" "DebugHISTOGRAM.obj" "Debugplotit4.obj" "DebugHEV_world.obj" "C:UsersJohn SullivanA_WorkDocumentsVisual Studio 2005LibraryNewLibLib1.lib" Link: executing 'link' LINK : fatal error LNK2023: bad DLL or entry point 'msobj80.dll' HEV - 1 error(s), 0 warning(s) |
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We just learned some more about this problem. Here is Microsoft's description:
MsPdbsrv.exe is installed in 2 place by VisualStudio. One of the location is
"Program FilesCommon FilesMicrosoft SharedVSA8.0VsaEnv". The bug is that
msobj80.dll isn't installed at that location. If mspdbsrv.exe is started from a non-VS
environment, it will not find msobj80.dll when link.exe communicates with mspdbsrv.exe.
So you could copy msobj80.dll to that directory, or make sure
Program FilesMicrosoft Visual Studio 8Common7 is always in your path.
Supposedly, this is fixed in Visual Studio 2005 SP1. Or you can copy msobj80.dll to the VsaEnv folder.
MsPdbsrv.exe is installed in 2 place by VisualStudio. One of the location is
"Program FilesCommon FilesMicrosoft SharedVSA8.0VsaEnv". The bug is that
msobj80.dll isn't installed at that location. If mspdbsrv.exe is started from a non-VS
environment, it will not find msobj80.dll when link.exe communicates with mspdbsrv.exe.
So you could copy msobj80.dll to that directory, or make sure
Program FilesMicrosoft Visual Studio 8Common7 is always in your path.
Supposedly, this is fixed in Visual Studio 2005 SP1. Or you can copy msobj80.dll to the VsaEnv folder.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you sure that Visual Studio's executables and libraries are actually under Documents? My guess is that you're seeing the personal projects directory tree.
Have you installed Service Pack 1 for VS2005 as well as the update for Vista? Both are called out in the Intel Fortran installation guide as required for Vista.
Have you installed Service Pack 1 for VS2005 as well as the update for Vista? Both are called out in the Intel Fortran installation guide as required for Vista.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page