- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This post is related to several others here, and I'm starting a new thread to facilitate swift searching.
Several people have reported the classic "application configuration is not correct" error at runtime. This is of course not peculiar to Intel Visual Fortran. Indeed, many C++ developers are seeing the same thing.
What is different this time is that Microsoft appears to have made a mistake in packaging the redistributable runtime libraries for Visual Studio 2005 SP1 currently offered as vcredist_x86.exe at
http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
The libraries installed by the aforementioned installer are functionally different from those installed by the vcredist_x86.exe (yes, same file name, but different contents) supplied with the Visual Studio 2005 SP1 installer. The latter are typically installed at
%PROGRAMFILES%\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\vcredist_x86
The vcredist_x86 installed from the URL are typically of no help when deploying applications built with Visual Studio 2005 SP1, contrary to what the web page states. The vcredist_x86 installed with the Visual Studio 2005 SP1 update works as advertised.
I have no idea why the download (at least as of this week) does not work as advertised. All I know is that I have a solution.
If you suspect your application is affected by this issue, you can run Dependency Walker (http://www.dependencywalker.com). If Dependency Walker reports that it is unable to bind to a particular version of MFC80.DLL, MFP80.DLL or MSCRT80.DLL (or with a particular public key), then there is an excellent chance that this post will be helpful to you.
Good Luck!
NFU
Several people have reported the classic "application configuration is not correct" error at runtime. This is of course not peculiar to Intel Visual Fortran. Indeed, many C++ developers are seeing the same thing.
What is different this time is that Microsoft appears to have made a mistake in packaging the redistributable runtime libraries for Visual Studio 2005 SP1 currently offered as vcredist_x86.exe at
http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
The libraries installed by the aforementioned installer are functionally different from those installed by the vcredist_x86.exe (yes, same file name, but different contents) supplied with the Visual Studio 2005 SP1 installer. The latter are typically installed at
%PROGRAMFILES%\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\vcredist_x86
The vcredist_x86 installed from the URL are typically of no help when deploying applications built with Visual Studio 2005 SP1, contrary to what the web page states. The vcredist_x86 installed with the Visual Studio 2005 SP1 update works as advertised.
I have no idea why the download (at least as of this week) does not work as advertised. All I know is that I have a solution.
If you suspect your application is affected by this issue, you can run Dependency Walker (http://www.dependencywalker.com). If Dependency Walker reports that it is unable to bind to a particular version of MFC80.DLL, MFP80.DLL or MSCRT80.DLL (or with a particular public key), then there is an excellent chance that this post will be helpful to you.
Good Luck!
NFU
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you sure that your various versions are not actually the other way around?
That link in your post looks to be specifically to the old version of the libraries that were current when VS 2005 SP1 was released. It shouldn't be relevant for applications built on machines that have been updated since SP1.
I'm guessing that the vcredist that you found on your machine (and also the actual libs, dll's, pdb's etc) has probably been updated by Windows Update or similar (it will have been updated, unless your IT environment has taken steps to prevent that). Have a look at the date on the file. If its dated mid July 2009, then it (and the actual version of libraries that you are linking to, and hence the earliest version of libraries that your require) isn't what was installed with SP1 - it is much later.
The latest vcredist download that I'm aware of is at http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en (a different link to the one in your post). This appears to have the same mid July 2009 stuff that is on my development machines.
Now, if your complaint is that your development libraries shouldn't change without you knowing, or that MS shouldn't leave old versions of the redistributable lying around without clear indication that they are out of date - then you might have a point!
That link in your post looks to be specifically to the old version of the libraries that were current when VS 2005 SP1 was released. It shouldn't be relevant for applications built on machines that have been updated since SP1.
I'm guessing that the vcredist that you found on your machine (and also the actual libs, dll's, pdb's etc) has probably been updated by Windows Update or similar (it will have been updated, unless your IT environment has taken steps to prevent that). Have a look at the date on the file. If its dated mid July 2009, then it (and the actual version of libraries that you are linking to, and hence the earliest version of libraries that your require) isn't what was installed with SP1 - it is much later.
The latest vcredist download that I'm aware of is at http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en (a different link to the one in your post). This appears to have the same mid July 2009 stuff that is on my development machines.
Now, if your complaint is that your development libraries shouldn't change without you knowing, or that MS shouldn't leave old versions of the redistributable lying around without clear indication that they are out of date - then you might have a point!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - IanH
Are you sure that your various versions are not actually the other way around?
That link in your post looks to be specifically to the old version of the libraries that were current when VS 2005 SP1 was released. It shouldn't be relevant for applications built on machines that have been updated since SP1.
I'm guessing that the vcredist that you found on your machine (and also the actual libs, dll's, pdb's etc) has probably been updated by Windows Update or similar (it will have been updated, unless your IT environment has taken steps to prevent that). Have a look at the date on the file. If its dated mid July 2009, then it (and the actual version of libraries that you are linking to, and hence the earliest version of libraries that your require) isn't what was installed with SP1 - it is much later.
The latest vcredist download that I'm aware of is at http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en (a different link to the one in your post). This appears to have the same mid July 2009 stuff that is on my development machines.
Now, if your complaint is that your development libraries shouldn't change without you knowing, or that MS shouldn't leave old versions of the redistributable lying around without clear indication that they are out of date - then you might have a point!
That link in your post looks to be specifically to the old version of the libraries that were current when VS 2005 SP1 was released. It shouldn't be relevant for applications built on machines that have been updated since SP1.
I'm guessing that the vcredist that you found on your machine (and also the actual libs, dll's, pdb's etc) has probably been updated by Windows Update or similar (it will have been updated, unless your IT environment has taken steps to prevent that). Have a look at the date on the file. If its dated mid July 2009, then it (and the actual version of libraries that you are linking to, and hence the earliest version of libraries that your require) isn't what was installed with SP1 - it is much later.
The latest vcredist download that I'm aware of is at http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en (a different link to the one in your post). This appears to have the same mid July 2009 stuff that is on my development machines.
Now, if your complaint is that your development libraries shouldn't change without you knowing, or that MS shouldn't leave old versions of the redistributable lying around without clear indication that they are out of date - then you might have a point!
Ian: You're right. I blew that one. Thanks for the correction.
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