- 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.
07-31-2023 12:49 AM
Hello Everybody,
Now i'm building PSM plugin for App Desktop Check Point Smart Console, i've set the Debug Level as per link https://community.cyberark.com/s/question/0D52J00007S9qNYSAZ/how-do-i-turn-on-the-psm-debug-levels-t... and add parameter as per link https://community.cyberark.com/s/article/PSMDU014E-Error-performing-dispatcher-s-request-GetSessionP... but the result i always getting error PSMSR163E once Connect using PVWA
Below are the logs error
Please help guys
Note : I'm using version 13.0
08-08-2023 02:21 AM
Hello,
This the update regarding case above, i commented some line code in AutoIT script. I try to open again SmartConsole from PVWA but now i get error PSMSR126E & PSMSR163E. But in component log file there is no error
Please help guys
08-09-2023 09:26 PM
Hi @Agus Susanto ,
I think you need to delete some property, it seems you have to duplicate the platform from Windows domain and customize CC via autoIT
08-09-2023 11:12 PM
Hello @Duong Trung Duong ,
No property "PSMRemoteMachine" & "Domain" in my PSM Smart Console connection component plugin being set & i already comment out line code regarding "PSMRemoteMachine" & "Domain" in AutoIT script. now the error are PSMSR126E & PSMSR163E
08-10-2023 12:32 AM
Error code 87 means "parameter incorrect" (https://learn.microsoft.com/en-us/windows/win32/debug/system-error-codes--0-499-). Since it is accompanied by an "failed to open process" message, it sounds like there is either an issue with PSM executing the SmartConsole exe, or an issue with PSM sending the SmartConsole process' PID to the session recorder. Use something like Sysinternals ProcMon or ProcExp to investigate what happens after your dispatcher launches the SmartConsole exe... does it launch a child process? Does it access a a file that isn't there? Does it try to write into a directory that isn't writable for that user?
05-15-2024 03:31 AM
Hello @Agus Susanto ,
were you able to fix this error and get the script running?
I'm trying to do exactly the same (Checkpoint R81.1) and get the exact same error.
Any help would be greatly appreciated!
Thanks
Joerg
05-15-2024 07:55 PM
Hello @Joerg Raidt ,
please refer to the link https://community.checkpoint.com/t5/Management/R81-SmartConsole-config-file-doesn-t-work/m-p/112464/highlight/true#
in my case, i decreased my Smart Console version from 81.10 to 80.x
06-03-2024 02:41 AM
I tried running it with an AutoIT script. I did have the problem, that Checkpoint did start a new instance of its own software. So the process id I initially got when I started the Checkpoint GUI was not in use any more. I had to wait a little, search again for a process with this name and use this process id/handle instead.
11-22-2024 02:43 AM
Hello @Joerg Raidt , does this fixed your issue. I am also facing the same issue. If you can could you please share the part which you have changed to pick the new PID.
11-25-2024 02:55 AM
Hello @Sankha Rajaguru ,
yes, as far as I can remember, that solved it. It was a customer project, so I don't have access to it anymore, but the solution wasn't that difficult.
You run the correct executable via AutoIT but don't immediately grab the process ID (usually, you could just take the ID that is returned by the call to run the executable), but in this case, you have wait some seconds and then search for the right window.
07-03-2025 12:14 AM
Hi,
Can u fixed this issue or not ?
07-03-2025 12:15 AM
Hi,
Can u fixed this issue or not ?
02-09-2026 09:29 PM
Hi,
What is your smartconsole version?
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!

