Issue with PSM version 14.0 and AutoIT

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Issue with PSM version 14.0 and AutoIT

L1 Bithead

Hello, I have a support ticket open for this but I haven't been able to get a response for the past month.

 

I'm building a new connector server, Windows Server 2022, with PSM version 14.0. AutoIT simply will not work. The error I am seeing is:

 

  • PSMGenericClientWrapper error: Failed to load DLL (Components folder)\\PSMDispatcherUtils.dll

 

So far, I have done the following:

 

  • Triple-checked Applocker, including rerunning hardening, clearing all rules, putting it in audit mode and reviewing Applocker event logs. None of that has resulted in any change to the error
  • Reviewed all folder permissions for PSMShadowUsers
  • Tried to manually debug AutoIT. It is failing at the stage where it tries to call dllOpen in PSMGenericClient PSMGenericClientWrapper.au3
  • Reviewed all local and domain GPO settings

 

The funny thing is I have another WS2022 connector server where AutoIt is working. So that points to a policy or permissions issue, but I have reviewed every setting I can think of between the two servers and they are identical.

 

Another funny thing is if I copy an older version of PSMDispatcherUtils.dll from another connector server (version 13.1), AutoIT works. That is bizarre to me.

 

I'm at the end of my rope and I'm not sure how to troubleshoot further. Support is not responding, so I am reaching out here. Thanks in advance for any assistance you can lend me.

1 accepted solution

Accepted Solutions

L2 Linker

Dear all,

I had the same issue with an open case for long time.

Facts: this is happening both on 14 and 13.2 (though in some cases not all the time in 13.2)

The official (and documented also solution) is to not use au3 scripts, but convert them to .exe (this is working fine and is more secure)

 

The solution to move autoit3.exe to the the components folder (and change the applocker accordingly) is working also (confirmend)

 

you dont have to change anything on your scripts

 

best regards

View solution in original post

11 REPLIES 11

L7 Applicator

I've seen this solution posted at Reddit before :

 

"Edit the system PATH variable and move PSM\components to the top and rerun the script." (hat tip to Strict_Mycologist101)

 

 

General consensus is that there are multiple versions of openssl on the host and an earlier version is being found which is incompatible with the latest cyberark compiled binaries.

 

Also check the standard stuff again, although the earlier version working does point more to Incompatability with some other files.

 

" Ensure that the hardening scripts has been updated accordingly if there are changes to the PSMConnect and PSMAdminConnect Users.

- Re-run the PSM hardening script and then verify PSMconnect , PSMAdminConnect and PSMShadowUsers should have Read & execute, List Folder contents and Read permission to Component folder."

L1 Bithead

Thanks for the suggestion. Unfortunately it did not solve my issue. It feels like a permissions problem, GPO or otherwise. But I'm not sure how to troubleshoot it. I can't find anything in the logs and the CyberArk error message is useless.

L7 Applicator

Hi @Jim Johnson​ 

 

Here are my suggestions,

 

  1. The fact that using an older version of PSMDispatcherUtils.dll works suggests there might be compatibility issues with the current version. Ensure that the AutoIT script is compatible with the version of the PSMDispatcherUtils.dll library you are using. It's possible that the newer version of the library has some changes that the script doesn't handle correctly.
  2. Check the Windows Event Viewer for any relevant error messages or warnings related to the failure to load the DLL. It might provide more details about the underlying issue.
  3. Even if you've reviewed local and domain GPO settings, there might be subtle differences between the two servers that are causing the issue

 

Hope it helps !

L1 Bithead

Hi,

We upgraded from 13.2 to 14.0 and are having the same issue. Does anyone know what might be the cause?

L4 Transporter

Hi @Jim Johnson​ ,

 

Could you try adding this at the top of the script and try again.

 

#pragma compile(x64, false)

 

Thank you

L4 Transporter

Hi @Jim Johnson​ ,

 

Could you try adding this at the top of the script and try again.

 

#pragma compile(x64, false)

 

Thank you

This game me a clue about why my app was not liking the DLL.

AutoIT was compiling 64 bit version of the script instead of 32 bit.

L1 Bithead

CyberArk responded on my associated support case and recommended moving the autoIT.exe file directly into the components folder on the connector server (and updating the path in the PVWA connection component). That solved it for me. Apparently multiple customers are having this issue with PSM version 14, and CyberArk is working on a fix.

FWIW:

I got it to work on my v14 setup with the solution I previously posted (Compiling with the 32 bit pragma definition plus explicitly compiling with x86 option from the right-click menu). This solves the failures once you compile the script not finding the "PSMDispatcherUtils.dll" eror. After placing the resulting exe file in the components folder.

Developing with the /test argument did not work until I moved my au3 scripts to another folder and used PSMGenericClientDriver.dll from a 11.4.0.24 version I got lying around. This solves the part of the testing not working.

L3 Networker

Dear all,

I had the same issue with an open case for long time.

Facts: this is happening both on 14 and 13.2 (though in some cases not all the time in 13.2)

The official (and documented also solution) is to not use au3 scripts, but convert them to .exe (this is working fine and is more secure)

 

The solution to move autoit3.exe to the the components folder (and change the applocker accordingly) is working also (confirmend)

 

you dont have to change anything on your scripts

 

best regards

L2 Linker

Dear all,

I had the same issue with an open case for long time.

Facts: this is happening both on 14 and 13.2 (though in some cases not all the time in 13.2)

The official (and documented also solution) is to not use au3 scripts, but convert them to .exe (this is working fine and is more secure)

 

The solution to move autoit3.exe to the the components folder (and change the applocker accordingly) is working also (confirmend)

 

you dont have to change anything on your scripts

 

best regards

  • 1 accepted solution
  • 1332 Views
  • 11 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!