Skip to main content

When I try to use the "DLL: Run function command" to run certain method of a DLL library which I created and compiled to 64 bits, .Net Framework 4.7.2, the command allows me to choose the target DLL file, either it's a file in machine hard disk or a file within control room, when I click the "Next" button, control room shows a popup "Deploying to your computer..." (it take some 20 seconds), then "Select DLL file" popup, and then "An internal error has occurred. Please stop the operation and try again. If the problem persists, please contact your system administrator" popup.

This is only happening when I compile the dll to 64 bits, if I move it to 32 bits A360 can show the methods.

I have tried with 2 different dlls, both of them gives the issue when I compile them to 64 bits.

I'm not 100% of my Bot Agent version (32 or 64 bits), bot it's installed in Program Files, (not Program Files X86), so I guess it's the 64 bits version.

In the DLL package documentation I found it's not completely clear about 64 bits DLLs are supported, since it says "Las funciones DLL de 32 bits son compatibles, ya que AutomationAnywhere.ManagedDLLWrapper.exe utiliza bibliotecas de 32 bits"

 

Any idea community?

I believe only 32-bit DLLs are supported. This has to do with the runtime Java library rather than the 64-bit Bot Agent executables.

Thanks for your response my friend, just if this is useful for community I have worked around this by calling the DLL method using a power shell script, with the Open program command. By the way, I didn't get it to accept static methods.

Reply


Terms & ConditionsCookie settings