- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
01-26-2024 01:35 PM
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:
So far, I have done the following:
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.
03-04-2024 07:12 AM
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
01-26-2024 04:35 PM
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."
01-26-2024 06:18 PM
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.
01-28-2024 08:13 PM
Hi @Jim Johnson
Here are my suggestions,
Hope it helps !
02-06-2024 05:05 PM
Hi,
We upgraded from 13.2 to 14.0 and are having the same issue. Does anyone know what might be the cause?
02-07-2024 02:16 AM
Hi @Jim Johnson ,
Could you try adding this at the top of the script and try again.
#pragma compile(x64, false)
Thank you
02-07-2024 02:16 AM
Hi @Jim Johnson ,
Could you try adding this at the top of the script and try again.
#pragma compile(x64, false)
Thank you
03-01-2024 05:10 AM
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.
03-04-2024 05:51 AM
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.
03-04-2024 06:03 AM
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.
03-04-2024 07:12 AM
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
03-04-2024 07:12 AM
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
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!

