August 16th, 2024

The case of the missing ordinal 380

Raymond Chen
Raymond Chen

A customer reported that some of their clients were getting an error message when running their program:

contoso.exe – Ordinal Not Found

The ordinal 380 could not be located in the dynamic link library C:\Program Files\Contoso\Contoso.exe.

The first thing to note is that this error message is misleading. It’s true that the missing ordinal is 380, but Contoso.exe is not the dynamic link library. Rather, it is the module that contains the reference to the missing ordinal. Unfortunately, the error message doesn’t tell us the DLL that lacks the desired ordinal 380 export. We’ll have to go find it ourselves.

We can use the LINK /DUMP /IMPORTS command to find all the functions that Contoso.exe imports, and search for a 380.

And there it is:

    COMCTL32.dll
             100B76110 Import Address Table
             100EC5868 Import Name Table
                     0 time date stamp
                     0 Index of first forwarder reference

                             Ordinal   380

And if you look in comctl32.dll version 6, you’ll find that it’s

        380   7F 000C0DA0 LoadIconMetric

Okay, so they are trying to link to the function Load­Icon­Metric in comctl32.dll, and it’s not there.

At this point, you may remember that there are two versions of comctl32.dll: Version 5 and version 6. Version 5 is the one you get by default, and to get version 6, you need to specify it in your application manifest.

The evidence suggests therefore that on the affected systems, something is wrong with their application manifest and the system is not processing it properly.

The customer liaison took this information back to the customer. I haven’t heard back from them, so I’m hoping they figured out why their manifests aren’t working on some systems.

Category
Old New Thing
Topics
Code

Author

Raymond Chen

Raymond has been involved in the evolution of Windows for more than 30 years. In 2003, he began a Web site known as The Old New Thing which has grown in popularity far beyond his wildest imagination, a development which still gives him the heebie-jeebies. The Web site spawned a book, coincidentally also titled The Old New Thing (Addison Wesley 2007). He occasionally appears on the Windows Dev Docs Twitter account to tell stories which convey no useful information.

4 comments

Discussion is closed. Login to edit/delete existing comments.

Newest
Newest
Popular
Oldest
  • Dmitry · Edited

    BTW, could anyone suggest a sane tool to check manifests are there and are perfectly valid?

    By sane I mean freeware, lightweight, portable, no stupid .NET/Java/Python/C++ runtime dependencies — something that just runs out of the box and does its job letting one be sure that the manifest will just work. You know, just what they (should have?) taught them since the first computer programming class.

    I remember trying some console utility and a few other programs...

    Read more
  • Henry Skoglund · Edited

    From Windows 1.0 up to Windows 7 the equivalent error message used to be: “The ordinal 380 could not be located in the dynamic link library comctl32.dll” or the more common “The procedure entry point LoadIconMetric could not be located in the dynamic link library comctl32.dll”.

    Why regress to the more confusing “… Contoso.exe” flavor?

Read next

Feedback