Skip to main content

Bugs, Issues and Errors: msvcr80.dll

  • November 19, 2018
  • 6 replies
  • 1 view
Jan Cees Boogaard

msvcr80.dll

Author: andrew.young@equiniti-ics.com (Andrew Young)

We have recently upgraded our Uniface application software which resides on a Windows 2008 64 bit virtual server.

We have not made any changes to the Uniface installation (Uniface9.3.02.01 (P202 0720_1)).

Occasionally we are getting the following error in the Event Viewer when the application starts:

Faulting application uniface.exe, version 9.3.2.202, time stamp 0x4a64a17c, faulting module MSVCR80.dll, version 8.0.50727.4016, time stamp 0x49cc5361, exception code 0xc0000005, fault offset 0x000173c6, process id 0xf68, application start time 0x01cd1e40896fd9b6.

This results in a 'Uniface 9 encountered an error and needed to close' style error and our users cannot access the application.

If we set $ioprint = 63 in the application asn file, this cuts down on the frequency of the errors but slows the application performance.

We are not experincing the same problem on Windows 2003 32 bit servers.

Has anyone out there encountered anything similar or know of a solution?

Thanks and regards,

Andrew.

6 replies

Jan Cees Boogaard

msvcr80.dll

Author: andrew.young@equiniti-ics.com (Andrew Young)

We have recently upgraded our Uniface application software which resides on a Windows 2008 64 bit virtual server.

We have not made any changes to the Uniface installation (Uniface9.3.02.01 (P202 0720_1)).

Occasionally we are getting the following error in the Event Viewer when the application starts:

Faulting application uniface.exe, version 9.3.2.202, time stamp 0x4a64a17c, faulting module MSVCR80.dll, version 8.0.50727.4016, time stamp 0x49cc5361, exception code 0xc0000005, fault offset 0x000173c6, process id 0xf68, application start time 0x01cd1e40896fd9b6.

This results in a 'Uniface 9 encountered an error and needed to close' style error and our users cannot access the application.

If we set $ioprint = 63 in the application asn file, this cuts down on the frequency of the errors but slows the application performance.

We are not experincing the same problem on Windows 2003 32 bit servers.

Has anyone out there encountered anything similar or know of a solution?

Thanks and regards,

Andrew.

For the other forum users a quick FYI:

Andrew has provided me some additional info. And the reported crash is most likely caused by bug 28503 ("Activate 3GL causes crash if signature specifies return value in first parameter"). This problem first has been fixed with the patch P209, but there was a side-effect that was recognized as bug 28930 ("C Call-Out: Return value in first parameter empty in case IN parameter exists") and was resolved with patch P217.

I hope the provided information is helpful.

Kind regards,
Daniel


Author: diseli (daniel.iseli@uniface.com)
Jan Cees Boogaard

msvcr80.dll

Author: andrew.young@equiniti-ics.com (Andrew Young)

We have recently upgraded our Uniface application software which resides on a Windows 2008 64 bit virtual server.

We have not made any changes to the Uniface installation (Uniface9.3.02.01 (P202 0720_1)).

Occasionally we are getting the following error in the Event Viewer when the application starts:

Faulting application uniface.exe, version 9.3.2.202, time stamp 0x4a64a17c, faulting module MSVCR80.dll, version 8.0.50727.4016, time stamp 0x49cc5361, exception code 0xc0000005, fault offset 0x000173c6, process id 0xf68, application start time 0x01cd1e40896fd9b6.

This results in a 'Uniface 9 encountered an error and needed to close' style error and our users cannot access the application.

If we set $ioprint = 63 in the application asn file, this cuts down on the frequency of the errors but slows the application performance.

We are not experincing the same problem on Windows 2003 32 bit servers.

Has anyone out there encountered anything similar or know of a solution?

Thanks and regards,

Andrew.

Hi ,

We just found a solution .

we installed c++ 2005  Components.

You can try install .net framework 2 if you dont have the full set of   "Microsoft Visual Studio 2005"

It is quite surprising and amazing that The guys from the Lab do not provide it or explain that it is

one of the Prerequisite for uniface 9.5 etc' .

 

Avner


Author: avner (avner@one1.co.il)
Jan Cees Boogaard

msvcr80.dll

Author: andrew.young@equiniti-ics.com (Andrew Young)

We have recently upgraded our Uniface application software which resides on a Windows 2008 64 bit virtual server.

We have not made any changes to the Uniface installation (Uniface9.3.02.01 (P202 0720_1)).

Occasionally we are getting the following error in the Event Viewer when the application starts:

Faulting application uniface.exe, version 9.3.2.202, time stamp 0x4a64a17c, faulting module MSVCR80.dll, version 8.0.50727.4016, time stamp 0x49cc5361, exception code 0xc0000005, fault offset 0x000173c6, process id 0xf68, application start time 0x01cd1e40896fd9b6.

This results in a 'Uniface 9 encountered an error and needed to close' style error and our users cannot access the application.

If we set $ioprint = 63 in the application asn file, this cuts down on the frequency of the errors but slows the application performance.

We are not experincing the same problem on Windows 2003 32 bit servers.

Has anyone out there encountered anything similar or know of a solution?

Thanks and regards,

Andrew.

Hi Avner,

Thank you very much for taking the time to respond to my post.

Installing Microsoft Visual Studio 2005 on the affected servers is not really an option for us and .Net framework 2 is already present.

Do you think there is any point trying to re-install Microsoft Visual C++ 2005 Redistributable Package (x86) (http://www.microsoft.com/en-us/download/details.aspx?id=3387) or Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) (http://www.microsoft.com/en-us/download/details.aspx?id=5638)?

Thanks in advance for any suggestions.

Andrew.


Author: Andrew Young (andrew.young@equiniti-ics.com)
Jan Cees Boogaard

msvcr80.dll

Author: andrew.young@equiniti-ics.com (Andrew Young)

We have recently upgraded our Uniface application software which resides on a Windows 2008 64 bit virtual server.

We have not made any changes to the Uniface installation (Uniface9.3.02.01 (P202 0720_1)).

Occasionally we are getting the following error in the Event Viewer when the application starts:

Faulting application uniface.exe, version 9.3.2.202, time stamp 0x4a64a17c, faulting module MSVCR80.dll, version 8.0.50727.4016, time stamp 0x49cc5361, exception code 0xc0000005, fault offset 0x000173c6, process id 0xf68, application start time 0x01cd1e40896fd9b6.

This results in a 'Uniface 9 encountered an error and needed to close' style error and our users cannot access the application.

If we set $ioprint = 63 in the application asn file, this cuts down on the frequency of the errors but slows the application performance.

We are not experincing the same problem on Windows 2003 32 bit servers.

Has anyone out there encountered anything similar or know of a solution?

Thanks and regards,

Andrew.

Hi Andrew,

I don't think it's necessary to re-install Microsoft Visual C++ 2005 Redistributable Package - nor do I think that the originally reported crash (in MSVCR80.dll) has anything to do with the Redistributable Package.

In order to run Uniface version 9.3 on Windows it is an installtion pre-requiste to install the Microsoft Visual C++ 2005 Redistributable Package (x86). And for version 9.4 and 9.5 the Microsoft Visual C++ 2005 SP1 Redistributable Package (x86).This information can be found in the ReadMe of the Uniface Distribution (or on the Installation Medium). It is not necessary to have either Visual Studio 2005 or the .Net Framework 2 installed.

But the mentioned versions of the Visual C++ 2005 Redistributable Packages are just the minimum required versions! It is no problem (or even recommended by Microsoft) when you install the latest version of the mentioned Redistributable Packages (with all the latest security fixes). I believe the following the most up-to-date version of the Visual C++ 2005 Redistributable Package:

I'm not sure, but I believe this update also covers the problem described by Avner:

"A security issue has been identified leading to MFC application vulnerability in DLL planting due to MFC not specifying the full path to system/localization DLLs. You can protect your computer by installing this update from Microsoft."

 For more information see the Microsoft Support Knowledge Base Article KB2538242.

Now back to the crash you've described in your inital post. First of all, the patch level you're using is quite old. The latest patch for version 9.3.02 is P228 and you can download it from here. And a list of all included fixes can be found here (you need a Frontline account to access the site). I would suggest to install the latest patch first and then check if this cures the crash. In case you still encounter a crash then it might be a good idea to create a user-mode dump (as described here) and log a call with Uniface Customer Support (you can do this online with your Frontline account here).

I hope the provided information is helpful.

Kind regards,
Daniel


Author: diseli (daniel.iseli@uniface.com)
Jan Cees Boogaard

msvcr80.dll

Author: andrew.young@equiniti-ics.com (Andrew Young)

We have recently upgraded our Uniface application software which resides on a Windows 2008 64 bit virtual server.

We have not made any changes to the Uniface installation (Uniface9.3.02.01 (P202 0720_1)).

Occasionally we are getting the following error in the Event Viewer when the application starts:

Faulting application uniface.exe, version 9.3.2.202, time stamp 0x4a64a17c, faulting module MSVCR80.dll, version 8.0.50727.4016, time stamp 0x49cc5361, exception code 0xc0000005, fault offset 0x000173c6, process id 0xf68, application start time 0x01cd1e40896fd9b6.

This results in a 'Uniface 9 encountered an error and needed to close' style error and our users cannot access the application.

If we set $ioprint = 63 in the application asn file, this cuts down on the frequency of the errors but slows the application performance.

We are not experincing the same problem on Windows 2003 32 bit servers.

Has anyone out there encountered anything similar or know of a solution?

Thanks and regards,

Andrew.

=================
Begin Activation Context Generation.
Input Parameter:
 Flags = 0
 ProcessorArchitecture = x86
 CultureFallBacks = he-IL;he;en-US;en
 ManifestPath = K:\\one1\\usys9\\common\\bin\\uniface.exe
 AssemblyDirectory = K:\\one1\\usys9\\common\\bin\\
 Application Config File =
-----------------
INFO: Parsing Manifest File K:\\one1\\usys9\\common\\bin\\uniface.exe.
 INFO: Manifest Definition Identity is Compuware.Uniface,processorArchitecture="X86",type="win32",version="1.0.0.0".
 INFO: Reference: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="X86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
 INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762"
 INFO: Reference: Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762"
INFO: Resolving reference Microsoft.Windows.Common-Controls,language="*",processorArchitecture="X86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0".
 INFO: Resolving reference for ProcessorArchitecture X86.
  INFO: Resolving reference for culture he-IL.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\\Windows\\assembly\\GAC_32\\Microsoft.Windows.Common-Controls\\6.0.0.0_he-IL_6595b64144ccf1df\\Microsoft.Windows.Common-Controls.DLL.
    INFO: Did not find manifest for culture he-IL.
   INFO: End assembly probing.
  INFO: Resolving reference for culture he.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\\Windows\\assembly\\GAC_32\\Microsoft.Windows.Common-Controls\\6.0.0.0_he_6595b64144ccf1df\\Microsoft.Windows.Common-Controls.DLL.
    INFO: Did not find manifest for culture he.
   INFO: End assembly probing.
  INFO: Resolving reference for culture en-US.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\\Windows\\assembly\\GAC_32\\Microsoft.Windows.Common-Controls\\6.0.0.0_en-US_6595b64144ccf1df\\Microsoft.Windows.Common-Controls.DLL.
    INFO: Did not find manifest for culture en-US.
   INFO: End assembly probing.
  INFO: Resolving reference for culture en.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\\Windows\\assembly\\GAC_32\\Microsoft.Windows.Common-Controls\\6.0.0.0_en_6595b64144ccf1df\\Microsoft.Windows.Common-Controls.DLL.
    INFO: Did not find manifest for culture en.
   INFO: End assembly probing.
  INFO: Resolving reference for culture Neutral.
   INFO: Applying Binding Policy.
    INFO: Auto Servicing Policy redirected assembly version.
    INFO: Post policy assembly identity is Microsoft.Windows.Common-Controls,processorArchitecture="X86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7601.17514".
   INFO: Begin assembly probing.
    INFO: Attempt to probe manifest at C:\\Windows\\WinSxS\\manifests\\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
    INFO: Manifest found at C:\\Windows\\WinSxS\\manifests\\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
   INFO: End assembly probing.
INFO: Resolving reference Microsoft.Windows.Common-Controls.mui,language="*",processorArchitecture="X86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7601.17514".
 INFO: Resolving reference for ProcessorArchitecture X86.
  INFO: Resolving reference for culture he-IL.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\\Windows\\assembly\\GAC_32\\Microsoft.Windows.Common-Controls.mui\\6.0.7601.17514_he-IL_6595b64144ccf1df\\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Did not find manifest for culture he-IL.
   INFO: End assembly probing.
  INFO: Resolving reference for culture he.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\\Windows\\assembly\\GAC_32\\Microsoft.Windows.Common-Controls.mui\\6.0.7601.17514_he_6595b64144ccf1df\\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Did not find manifest for culture he.
   INFO: End assembly probing.
  INFO: Resolving reference for culture en-US.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\\Windows\\assembly\\GAC_32\\Microsoft.Windows.Common-Controls.mui\\6.0.7601.17514_en-US_6595b64144ccf1df\\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Did not find manifest for culture en-US.
   INFO: End assembly probing.
  INFO: Resolving reference for culture en.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\\Windows\\assembly\\GAC_32\\Microsoft.Windows.Common-Controls.mui\\6.0.7601.17514_en_6595b64144ccf1df\\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Did not find manifest for culture en.
   INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762".
 INFO: Resolving reference for ProcessorArchitecture x86.
  INFO: Resolving reference for culture Neutral.
   INFO: Applying Binding Policy.
    INFO: Find publisher policy at C:\\Windows\\WinSxS\\manifests\\x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_516d712b0f495a45.manifest
    INFO: Publisher Policy redirected assembly version.
    INFO: Post policy assembly identity is Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4940".
   INFO: Begin assembly probing.
    INFO: Attempt to probe manifest at C:\\Windows\\WinSxS\\manifests\\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc.manifest.
    INFO: Manifest found at C:\\Windows\\WinSxS\\manifests\\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc.manifest.
   INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC80.CRT.mui,language="*",processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4940".
 INFO: Resolving reference for ProcessorArchitecture x86.
  INFO: Resolving reference for culture he-IL.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\\Windows\\assembly\\GAC_32\\Microsoft.VC80.CRT.mui\\8.0.50727.4940_he-IL_1fc8b3b9a1e18e3b\\Microsoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture he-IL.
   INFO: End assembly probing.
  INFO: Resolving reference for culture he.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\\Windows\\assembly\\GAC_32\\Microsoft.VC80.CRT.mui\\8.0.50727.4940_he_1fc8b3b9a1e18e3b\\Microsoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture he.
   INFO: End assembly probing.
  INFO: Resolving reference for culture en-US.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\\Windows\\assembly\\GAC_32\\Microsoft.VC80.CRT.mui\\8.0.50727.4940_en-US_1fc8b3b9a1e18e3b\\Microsoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en-US.
   INFO: End assembly probing.
  INFO: Resolving reference for culture en.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\\Windows\\assembly\\GAC_32\\Microsoft.VC80.CRT.mui\\8.0.50727.4940_en_1fc8b3b9a1e18e3b\\Microsoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en.
   INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762".
 INFO: Resolving reference for ProcessorArchitecture x86.
  INFO: Resolving reference for culture Neutral.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\\Windows\\assembly\\GAC_32\\Microsoft.VC80.MFC\\8.0.50727.762__1fc8b3b9a1e18e3b\\Microsoft.VC80.MFC.DLL.
    INFO: Attempt to probe manifest at K:\\one1\\usys9\\common\\bin\\Microsoft.VC80.MFC.DLL.
    INFO: Attempt to probe manifest at K:\\one1\\usys9\\common\\bin\\Microsoft.VC80.MFC.MANIFEST.
    INFO: Attempt to probe manifest at K:\\one1\\usys9\\common\\bin\\Microsoft.VC80.MFC\\Microsoft.VC80.MFC.DLL.
    INFO: Attempt to probe manifest at K:\\one1\\usys9\\common\\bin\\Microsoft.VC80.MFC\\Microsoft.VC80.MFC.MANIFEST.
    INFO: Did not find manifest for culture Neutral.
   INFO: End assembly probing.
 ERROR: Cannot resolve reference Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762".
ERROR: Activation Context generation failed.
End Activation Context Generation.

 


Author: avner (avner@one1.co.il)
Jan Cees Boogaard

msvcr80.dll

Author: andrew.young@equiniti-ics.com (Andrew Young)

We have recently upgraded our Uniface application software which resides on a Windows 2008 64 bit virtual server.

We have not made any changes to the Uniface installation (Uniface9.3.02.01 (P202 0720_1)).

Occasionally we are getting the following error in the Event Viewer when the application starts:

Faulting application uniface.exe, version 9.3.2.202, time stamp 0x4a64a17c, faulting module MSVCR80.dll, version 8.0.50727.4016, time stamp 0x49cc5361, exception code 0xc0000005, fault offset 0x000173c6, process id 0xf68, application start time 0x01cd1e40896fd9b6.

This results in a 'Uniface 9 encountered an error and needed to close' style error and our users cannot access the application.

If we set $ioprint = 63 in the application asn file, this cuts down on the frequency of the errors but slows the application performance.

We are not experincing the same problem on Windows 2003 32 bit servers.

Has anyone out there encountered anything similar or know of a solution?

Thanks and regards,

Andrew.

Hi i found this on the web:

For your info, there are several issues with the MFC80LOC DLLs that are shipped with VC 2005 SP1.    I'll describe the current WinSxs situation for MFC80LOC, and also the applocal situation.

 1) go to

C:\\WINDOWS\\WinSxS\\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05

 and open up MFC80.DLL, the version that ships with VC 2005 SP1.

 Now in the resource editor, look at the RT_MANIFEST resources and double click on the 1000 resource. 

 Notice that it refers to Microsoft.VC80.MFCLOC and the version of the DLL is 8.0.50608.0.  That's a shock.  It should really be 8.0.50727.762.   

 However, due to the polices installed at:

 C:\\WINDOWS\\WinSxS\\Policies\\x86_policy.8.0.Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_x-ww_caeee150

 in the file: 8.0.50727.762.policy the old versions get redirected to 8.0.50727.762.  So there shouldn't be any errors.

 2) Now getting back to the applocal approach,  look at the folder:

 C:\\Program Files\\Microsoft Visual Studio 8\\VC\\redist\\x86\\Microsoft.VC80.MFCLOC

 now look at Microsoft.VC80.MFCLOC.manifest in notepad.  Look at the version number in there: 8.0.50727.42.  This is the version number of the RTM versions of MFC80LOC not the versions of SP1.

 Now look at the version number of any of the versions of MFC80LOC, e.g. mfc80CHS.dll.  It's 8.0.50727.762, which does NOT match the manifest. 

 But since the MFC80.DLL refers to 8.0.50608.0 and this doesn't even exist, then you are going to get these kinds of errors (since policies are not utilized in the applocal approach). 

 The ideal would be for all versions of MFC80LOC to be matching the manifest and also an MFC80.DLL that has a manifest that refers directly to the 8.0.50727.762 version of MFC80LOC versions instead of 8.0.50608.0.

 


Author: avner (avner@one1.co.il)

Recent badge winners

Explore all badges
Terms & ConditionsAccessibility statement