- 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.
11-27-2024 09:44 PM
The other day, I successfully onboarded a MySQL database and was able to establish a connection through SQL Server Management Studio. However, when attempting to connect again now, I am unable to establish any connection. There are no error messages displayed on the interface, but upon checking the PSM console logs, the following errors were observed:
| PSMSR864E [71112f4c-cf8a-4688-94f1-1b1c6cf0cf34] A failure occurred while waiting for the PSMMessageAlert to end. Extra Details: 3. Reason: PSMSR362E [71112f4c-cf8a-4688-94f1-1b1c6cf0cf34] An attempt to use the [GetProcessHandle] method was made when process was not initialized.
PSMSRSRU001E [71112f4c-cf8a-4688-94f1-1b1c6cf0cf34] No recording files to upload
PSMSR126E [71112f4c-cf8a-4688-94f1-1b1c6cf0cf34] Failure occurred while handling session. PSMSR133E [71112f4c-cf8a-4688-94f1-1b1c6cf0cf34] Failed to create process "C:\Program Files (x86)\CyberArk\PSM\Components\\MSSQLManagementStudioDatabaseAuthenticationDispatcher.exe". Code: 1260 (Codes: -1, -1)
12-06-2024 05:10 AM
@Bellatrix Lestrange Additionally set the applocker in Audit mode and filter of 'Warnings' in the event viewer; Applications and Services >> Microsoft >> Windows >> Applocker >> exe and dll
Go through all the warning and look for SSMS related blocks.
Re-run applocker hardening to set back to Enforce rules.
11-28-2024 02:58 AM
Hi @Bellatrix Lestrange
This error is due to AppLocker blocking the MSSQL Database Authentication .exe.
Please add the “MSSQLManagementStudioDatabaseAuthenticationDispatcher.exe” in the the PSMConfigureAppLocker.xml and rerun the PSMConfigureAppLocker.ps1
12-05-2024 07:52 AM
Hi @Bellatrix Lestrange
As it seems Malhar provided an answer for your question, could you kindly share if this solution resolved your issue?
If so, could you please mark the answer as "Select as Best" to help other community members?
If the issue is still relevant, I would advise raising a ticket with our Support team for further assistance.
Thank you,
Liad
12-06-2024 05:10 AM
@Bellatrix Lestrange Additionally set the applocker in Audit mode and filter of 'Warnings' in the event viewer; Applications and Services >> Microsoft >> Windows >> Applocker >> exe and dll
Go through all the warning and look for SSMS related blocks.
Re-run applocker hardening to set back to Enforce rules.
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!

