AzureDeviceManagementClient.exe Can't load a custom plugin about azure-client-tools HOT 4 CLOSED

Hi v-jiq,

We have seen similar logs when the plug-in had some missing dependencies. Is it possible that it requires some dlls and they are not at the same folder?

If that's not the case, I would recommend to temporary change the plug-in configuration from out-of-proc to in-proc. You can do that by changed the plug-in manifest file and setting the "outOfProc" to false. This should narrow down the problem - and the you can share the logs again...

Let us know how this goes...

thanks,
george

from azure-client-tools.

Hi george,
I have retried according to your guide , that temporary change the plug-in configuration from out-of-proc to in-proc.

the log prompts that failed to load library SampleComponentNamePlugin.dll. but I have putted SampleComponentNamePlugin.dll to Specified directory. The SampleComponentNamePlugin.dll are generate by refer to this link -- https://github.com/ms-iot/azure-client-tools/blob/master/docs/device-agent/development-scenario/developer-plugin-creation.md and no modify anything.

below is log:

configure file:

dll:

Thanks

from azure-client-tools.

Hi v-jiq,

The device agent finds the dll. So, your configuration seem to be fine.

The error returned is 193 - looking this up in Windows codes, it's "is not a valid Win32 application".

Does the architecture of the dll matches the architecture of the agent/device? (x64, win32, arm, etc).

thanks,
george

from azure-client-tools.

Thanks george, as you said, the architecture error caused this problem!!

from azure-client-tools.