- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have created a static library based on subroutines that I have either developed or copied in the past. This library worked flawlessly on my previous visual fortran (version 6) but appears to have problems in VF 10.0. More specifically, upon debugging my application and editing main program code, the library sometimes works fine but on other occasions causes a fatal error lnk2023: bad DLL or entry point 'msobj80.dll' link. Concerning this error, Steve recommended that uninstall the Intel Fortran Integration and then do a reinstall/repair of VS followed by reinstalling the integration. In fact, I downloaded and installed VS2005 SP1 and reinstalled the Fortranintegration. This fixed things for awhile but it still occurs on occasion. To avoid frequent reload/reinstalls, rebooting my computer has been effective in dealing with this error, though nonetheless quite inconvenient.
How do I deal with this error?
In the interest of application development, I have abandoned the library and copied the needed source code from it into my application project. So far so good, but clearly a not very elegant approach. Any suggestions?
Finally, to avoid a host of warnings, I have turned off the interface block generation and checking features under fortran diagnostics. The interfaces of the code that I am developing passed muster with my VF 6.0, but not with 10.0. Has a solution to the interface issue been found?
John
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
More details are needed regarding the interface checking. Please open an issue at Intel Premier Support and supply an example.
It sounds as if something on your system is either corrupting the DLL or doing something that prevents Windows from finding it properly. I doubt that this is caused by Intel Visual Fortran.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
$(VSInstallDir)Common7ide
If it isn't, you could see this problem. It might also be that you have some other copy of MSOBJ80.dll on your system in a folder listed in the PATH environment variable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
-Since it's a static library, make sure you're using /
libdir:noauto in the compiler's command line (Project>Properties>Fortran>Libraries>Disable default library search rules).
-It shouldn't be a problem for static libraries, but you can try using consistent runtime libraries (i.e., try not to mix debug libraries with the corresponding release ones). Since the source code for the library you're building is available, you can build both a debug and a release version and linking as appropriate; maybe adding a "d" suffix to the name of the debug one can help if you want to keep both libraries in the same folder.
-It seems to me that you're adding the library as an Item in the project. I've never tried that approach ---though I think it should work just the same---. What I usually do is adding the library as an additional dependency (Project>Properties>Linker>Input); you can try that and see if it solves the problem (it's also a good idea to add the library and include paths to the IDE options (Options>Intel Fortran>General)).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
we had a similar problem. We have two installations of IVF 10. One with VS2005 Std. One without VS2005 Std, just the part of VS2005 (Premier Partner Edition) that comes with IVF 10.
I can compile certain projects on the proper VS2005 Std. But not on VS2005 PPE. No reinstall and so on was helping.
We have just copied the copy of msobj80.dll to the second computer (it was missing). Now it works.
Frank
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Error 1 fatal error LNK2023: bad DLL or entry point 'msobj80.dll' LINK
Based on the tips in this thread I copied the dll from
....Microsoft Visual Studio 8VCBin
to
C:Program FilesMicrosoft Visual Studio 8Common7IDE
then it started working.
Why it stopped working i dont know, maybe something deleted the files?
I dont like this kind of things, I hope it will work som some time now. Thanks for this forum...
Best regards Are
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've noticed that the compiler error message 'missing msobj80.dll' is correlated with another problem I sometimes have, namely the debugger no longer being able to recognize breakpoints once it is connected to a process. That is to say, if I attempt to debug and find the 'disabled breakpoint' problem, and then try to work around it by putting some 'write' statements into my source code to print the variable values out into a file, then chances are I won't be able to compile it because of the 'missing msobj80.dll' error.
This is with VS2005 SP1 and IVF 10.1.024.
Nevertheless, copying the msobj80.dll file from VC/BIN to Common7/IDE fixes both problems. Thanks for the suggestion.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
THANKS for posting that. I got bit by this bug fromIntel Fortran that I installed last week.After it had been working fine, too.Quite the annoying mystery.
Copying the file to the other directory got rid of the error. I don't like these things either. This forum is definitely a good thing.
are_johan:
I bougth a new Fortran developer studio a month ago, an suddenly this problem occurred:
Error 1 fatal error LNK2023: bad DLL or entry point 'msobj80.dll' LINK
Based on the tips in this thread I copied the dll from
....Microsoft Visual Studio 8VCBin
to
C:Program FilesMicrosoft Visual Studio 8Common7IDE
then it started working.
Why it stopped working i dont know, maybe something deleted the files?
I dont like this kind of things, I hope it will work som some time now. Thanks for this forum...

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