I am getting a message The ordinal 379

[bryceyork]

I just started getting this message: 

The ordinal 379 could not be located in the dynamic link libraryiertutil.dll. 

its causeing some programs to not start 

any ideas what might be wrong and how to fix it ?  

I've done a full norton anti virus scan and I'm clean, or so it says I am 

[Mumbodog]

Which Operating System and Service pack level?

Which version of Internet Explorer?

When do you see this message.

Which programs do not start, be specific please.

[bryceyork]

I am running windows 7 home premium edition

service pack 1 

[bryceyork]

I don't know what version of Internet explorer was on here,  I haven't used it in ages and now it doesn't even open

[bryceyork]

My Corel PhotoImpact X3 doesn't work, it stalls on startup then just disappears 

Internet explorer just thinks for a few seconds then nothing at all.

When I open my outlook I get a few of the error messages then if I close the warning a few times it will eventually open

actually that happens with a few programs like word 

[Mumbodog]

Run a System File Checker

http://support.microsoft.com/kb/929833

[bryceyork]

Thank you, I'm going to try that asap 

[RobAld]

@ bryceyork

> ordinal 379 could not be located in the dynamic link library iertutil.dll

In lieu of exact version information about IE it would probably be sufficient for you to tell us what version of  iertutil.dll  that you have and check with some of the other common IE modules.   A simple way of doing that would be to  Run...  (e.g. press Win-R and enter   msinfo32.exe

Then drill down into the Sofware Environment, Loaded Modules display.  Then sort by Version descending.   E.g. that would put any modules with version starting with 9 or 8 near the top.  Besides  iertutil.dll  you should look at  ieframe.dll  and  mshtml.dll  for comparison.   Both are apt to be present even when  iexplore.exe  is not loaded.

However, if IE isn't working when it should be working that is a sign that your OS is sick, so it would be a good idea to get it working.

BTW a good way to get more detail for these cases is to execute the program under DependencyWalker, e.g. use that utility's F7 Profiler command with whatever command line operands the failing program is using.

FYI

Robert Aldwinckle
---