Article ID: 2126815 - Last Review: June 7, 2010 - Revision: 1.0

EapHost configuration APIs from a managed application built with AnyCPU option would fail with error 0x80420011 when run on 64-bit OS.

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

Expand all | Collapse all

SYMPTOMS

The problem is that .NET binaries when build for 'any cpu' specifies the image type as x86. So, when EapHost validates if the method binary is of the same architecture as the loading process, it will fail on AMD64 machines.

Back to the top

CAUSE

EapHost performs some validation checks before loading the EAP method dll, where it verifies that the calling application and the EAP method dll which it is trying to use are of same architecture. This validation is done by looking at the IMAGE_NT_SIGNATURE of the app exe and the EAP method dll. The issue is that we only look at the PE (Portable Executable) format in the NT_SIGNATURE to validate but need to look at the 32BIT field also to validate.

Back to the top

RESOLUTION

No workaround, so please provide both x86 and x64 applications.

Back to the top

MORE INFORMATION

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

Back to the top