Fusion Log Binder collector assembly error - binding result: hr = 0x1. Wrong function

Question

I'm trying to figure out weird behavior on one machine. I have a trivial console application that will work interactively, but when I call it through WMI, it will start and exit immediately.

I turned on Fusion magazine since Procmon was unconfirmed. I see the following error:

*** Assembly Binder Log Entry (31-01-2015 @ 19:22:51) *** The operation was successful. Bind result: hr = 0x1. Incorrect function. Assembly manager loaded from: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll Running under executable C:\CMCBOOTSTRAP\Cmc.Installer.Agent.Console.exe --- A detailed error log follows. BEGIN : Native image bind. END : Incorrect function. (Exception from HRESULT: 0x00000001 (S_FALSE)) 

What is the reason for the "wrong function"? What else can I look to determine why this application effectively dies when launched through WMI?

And I mean trivial ...

 class Program { static void Main(string[] args) { Thread.Sleep(30000); } } 

The environment is Windows Server 2012 R2 and .NET 4.5.

Answer 1

This is a completely normal error, you got it from Fuslogvw.exe by setting the "Native Images" switch in the settings for log categories. Easy to play on my own machine, I see many of them.

The actual error code is S_FALSE, the COM error code, which means that "it completed successfully with an error." That's why he says The operation was successful . Incorrectly interpreted for the diagnostic message as "Function failed", this is a description of the Windows 1 error and returned by the winampi FormatMessage () function.

Successful failure is fully expected, you did not run Ngen.exe in your application with console mode, but its own image is not available for it. Keep looking, it is not. Change the log category to "Default", inline images are not your problem.