- 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.
10-14-2025 01:26 AM
We are experiencing a failure with the PSM connector, resulting in the following exception, Kindly suggest if you have any thoughts "Account Username: testuser
PSMSR605E [39cc9499-4bad-4399-a7ff-40da278865d4] Error occurred while waiting for the dispatcher to communicate (Error details: [PSMSR282E One of the session components has failed and therefore the session will be close"
PSM trace logs contains this error:
=============================
[14/10/2025 | 15:55:49.720946] | {pid= 6452} | {tid= 10476} | class CPSMSessionKeeper * | PSM\PSMServer\PSMSessionKeeper.cpp(217) | :: | PSMSR906I [39cc9499-4bad-4399-a7ff-40da278865d4] Successfully sent abort minimize prevention request to the session keeper
[14/10/2025 | 15:55:49.720979] | {pid= 6452} | {tid= 10476} | class CPSMSessionProcessBase * | PSM\PSMServer\PSMSessionProcessBase.cpp(667) | :: | PSMSR292W [39cc9499-4bad-4399-a7ff-40da278865d4] Satellite process (Client dispatcher) has failed. Return code: -1073741819
[14/10/2025 | 15:55:49.721023] | {pid= 6452} | {tid= 10476} | class CPSMBaseException * | PSM\PSMServer\PSMBaseException.cpp(38) | :: | PSMSR009I Privileged Session Manager exception occurred. PSMSR282E One of the session components has failed and therefore the session will be closed. For further assistance, contact your system administrator. More info: Process [Client dispatcher] has failed. Session [39cc9499-4bad-4399-a7ff-40da278865d4]. (Codes: -1, -1)
[14/10/2025 | 15:55:49.721331] | {pid= 6452} | {tid= 10476} | class CPSMBaseException * | PSM\PSMServer\PSMBaseException.cpp(38) | :: | PSMSR009I Privileged Session Manager exception occurred. PSMSR605E [39cc9499-4bad-4399-a7ff-40da278865d4] Error occurred while waiting for the dispatcher to communicate (Error details: [PSMSR282E One of the session components has failed and therefore the session will be closed. For further assistance, contact your system administrator. More info: Process [Client dispatcher] has failed. Session [39cc9499-4bad-4399-a7ff-40da278865d4].]) (Codes: -1, -1)
[14/10/2025 | 15:55:49.721443] | {pid= 6452} | {tid= 10476} | class CPSMTSUserSessionService * | PSM\PSMServer\PSMTSUserSessionService.cpp(551) | :: | PSMSR586I [39cc9499-4bad-4399-a7ff-40da278865d4] Setting recorded session end time: 1760428549
Below change done, but no luck
I apply this change for parameter "LockApplicationwindow" under target settings to disable (Enable : No)
10-14-2025 02:41 AM
it would be good to provide more information
1- is it autoit based connector ?
2- was it working before ?
any other information which you think is relevant
10-14-2025 02:41 AM
it would be good to provide more information
1- is it autoit based connector ?
2- was it working before ?
any other information which you think is relevant
10-14-2025 04:27 PM
Hello @Gajula Phani Kumar
There are a few methods you can try.
PVWA > Administration > Configuration Option > PIM Suite Configuration > Connection Components > {ConnectionComponentName} > Target Settings > Lock Application Window > Timeout = 90000
PVWA > Administration > Configuration Option > PIM Suite Configuration > Connection Components > {ConnectionComponentName} > Target Settings > Lock Application Window > SearchWindowWaitTimeout = 120
If AppLocker does not allow MMC to run add the following rule in the PSMConfigureAppLocker.xml
<Application Name="MMC" Type="Exe" Path="C:\Windows\System32\mmc.exe" Method="Hash" />
<Application Name="AutoIt3" Type="Exe" Path="C:\Program Files (x86)\AutoIt3\AutoIt3.exe" Method="Publisher" />
I hope this helps you!
10-14-2025 04:27 PM
Hello @Gajula Phani Kumar
There are a few methods you can try.
PVWA > Administration > Configuration Option > PIM Suite Configuration > Connection Components > {ConnectionComponentName} > Target Settings > Lock Application Window > Timeout = 90000
PVWA > Administration > Configuration Option > PIM Suite Configuration > Connection Components > {ConnectionComponentName} > Target Settings > Lock Application Window > SearchWindowWaitTimeout = 120
If AppLocker does not allow MMC to run add the following rule in the PSMConfigureAppLocker.xml
<Application Name="MMC" Type="Exe" Path="C:\Windows\System32\mmc.exe" Method="Hash" />
<Application Name="AutoIt3" Type="Exe" Path="C:\Program Files (x86)\AutoIt3\AutoIt3.exe" Method="Publisher" />
I hope this helps you!
10-14-2025 04:54 PM
Hi @Gajula Phani Kumar
Please try to temporarily disable the antivirus on the PSM server or exclude PSM folder and test the connection.
Also try to reinstall Microsoft Visual C++ Redistributable
Put all the AppLocker rules in Audit mode.
In addition check the Windows Application Event Log on the PSM server at the exact time of the failure.
Hope it helps !
10-15-2025 01:03 AM
Please try followings to see whether it works .
Thanks
Biswadeep
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!

