- 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-10-2021 11:05 PM
After the server restart - Central Policy Manager Scanner Service is not Running. Upon checking on the PM / PMtrace logs we are seeing error Error verifying CPM engine signature | PTM terminal.exe)
Any help?
Fixes Tried :
1.Checked CPMInstall.log - we did not see any errors
2.Since the error states PMTerminal we thought disabling the PMterminal wil fix the issue,
Disabled DEP on files used by CPM (https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PAS%20INST/Following-Central-...)
But this didnt help. We disabled and retried the restart, still the same error we are seeing.
3. ON PVWA we checked if SSL/TLS is enabled . They are enabled.
4.Made changes as per : https://cyberark-customers.force.com/s/article/00005074
5.As per an article we also checked d cacpmscanner.exe to see if nay unwnated character is der. Remove the garbled character (�E¿) before <?xml version="1.0" encoding="utf-8"?> in CACPMScanner.exe.config. The config file looks good. This option is also verified.
6) Compared with OLD & NewCPM server
Observation : In Old CPM server Cyberark Central Policy manager scanner service is running and everything is working fine.
New CPM server seCyberark Central Policy manager scanner service service is not running. Facing the same Issue what we are facing in new
CPM server.
7) Checked whether https/443 was blocked between the CPM server and PVWA server or not.
The port was open between CPM server & PVWA server. It is allowing traffic from CPM to PVWA over 443.
😎 Imported the PVWA portal certificate from Existing SIT-B PVWA server to new SIT-B PVWA servers(25 & 26). Even after performing the iisreset, Couldn't start the Cyberark Central Policy manager scanner service in New CPM server.
5) Peformed the following action in PVWA portal: Option > CPM Settings > General ->VerifyEnginesSignatures and set it to no. Restarted the CPM service.
Still Facing the Issue with the CPM server.
6) Tested the new PVWA URL's inside CPM server, everything working fine except internal LB URL.
None of these changes helped. Please suggest.
01-11-2021 07:52 AM
Usually the problem is ssl certificate.
Verify that vault.ini contain FQDN address of PVWA, not localhost/127.0.0.1.
Import PVWA certificate as trusted cert.
01-11-2021 05:53 AM
Hi
You can do the following: Option > CPM Settings > General ->VerifyEnginesSignatures and set it to no.
Restart CPM service and you should be good to go.
01-11-2021 06:50 AM
will try that update you webber.
01-11-2021 07:07 AM
Hi webber, The settings are already configured / Set as NO. Still we see same error.
01-11-2021 07:52 AM
Usually the problem is ssl certificate.
Verify that vault.ini contain FQDN address of PVWA, not localhost/127.0.0.1.
Import PVWA certificate as trusted cert.
01-11-2021 11:21 PM
Ok heron. will try that and update. Thanks
01-12-2021 03:33 AM
Maybe it is an easy fix. Stop the CPM Service, use the PrivateArk Client and change the password of the CPM-user listet in the user.ini. Create on the CPM an new cred-file with the new password. Now start the CPM service and after that the scanner service.
01-20-2021 04:07 AM
Thanks stefan. It is a certificate issue. We fixed the certificate and the issue is resolved.
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!

