- 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.
02-25-2019 12:05 PM
02-25-2019 12:05 PM
Fix solution for CPM 10.7 Installation Error:
CPMEM038E Error while trying to import platforms.
{"ErrorCode":"PASWS187E","ErrorMessage":"The requested resource with API version '10.7' does not support HTTP method 'GET'."}
It looks like the root cause if this error is TLS 1.2 is disabled on the CPM, which prevent connection to the PVWA! Here is what we did in our case:
1. Check your GPO, if it doesn’t disable TLS 1.2 on the CPM server.
2. In order to minimize the connection between the CPM and PVWA servers, and isolate the issue (1:1), edit the Vault.ini in the CPM:
On the CPM, open the Vault.ini file
In the [API] section, edit the URL to include one PVWA server or LB URL dns fqdn.
the syntax should look like: https://pvwa_srv.corp.com/PassswordVault
Nothing after ‘PasswordVault’!
3. Open the Vault and navigate to PVWAConfig safe, open it and edit the PVConfiguration.xml file to include the same URL you configured in the previous step at:
…ApplicationRoot=”The PVWA or LB URL”….
Make sure you have a copy before making any changes (download a copy from the save)
4. On the CPM, open the registry and add the following keys:
• Enable TLS 1.2 protocol:
• [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client] "DisabledByDefault"=dword:00000000
• [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server] "Enabled"=dword:ffffffff
• Enable .NET to use TLS 1.2:
• [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001
• [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001
5. Reboot the server
6. Check if the registry keys you created above still there.
7. Run CPM repair.
Select ‘Yes’ to recreate the environment in the Vault
Select ‘Original Oracle file’
8. The installation should be finished with no errors this time.
9. Check logs and services.
Good luck,
Feedback & comments are welcome
03-28-2019 01:21 AM
Still Issue persist when we applied the recommendation above. What would be the issue if we dont fix the error during the installation
03-28-2019 01:43 AM
I Found that the issue only comes when you input the LB PVWA Address but if you insert the actual address it doesnt show the error.
What would be the implication if we proceed with local address instead of LB in an environment where we use PVWA LB
03-28-2019 08:26 AM
There are two things that caused this issue:
TLS is not enough! I also sow this error in ver 10.8... I tried it without importing the PVWA's certificate.
I hope this would help
Feedback & Comments are very welcome 🙂
03-28-2019 08:30 AM
Thank you Jazuc for your comment, this is interesting, I think it's a matter of certificates, can you give an example about the "actual address" you are talking about ? is it IP or URL ? what exactly do you mean?
Thanks in advance
05-01-2019 12:40 AM
Hello @Anan Habka ,
Thanks this worked for me. In my case, the LB URL was not activated yet and hence it showed the error. I replaced it with the individual URL and now it worked.
05-01-2019 06:35 AM
Happy to know that this helped you @sriram nagarajan 😎
07-08-2019 08:22 PM
@Anan Habka Are your steps confirmed by CyberArk Support or R&D?
I am having the same error with Ver 10.10 CPM installation, and it didn't work with importing the PVWA cert on the CPM server.
API section does have the right URL of the PVWA. And repair installation had the same error and some platforms were missing obviously.
07-10-2019 12:19 PM
Hello,
I think I can find or get approval for that -:) I'm just sharing my experience with the ppl here , For formal answer, I guess you need to open a case.
To add to this fix, make sure that the Vault.ini (in the CPM) has the right pvwa_fqdn (in the API section) , besides the SSL certificate must have this fqdn.
And make sure you have port 443 opened from the CPM to the PVWA
Also, on the PVWA's IIS you need ssl for each server. The idea is that all component trust the same SSL Root certificate name( url).
(Usually in public CA , all servers already trust it)
Before repairing the CPM, try the pvwa url in IE + Chrome browser, and check if the certificate is valid (getting green locker icon, in Chrome you might get '?')
Hope this helps & please put your comment, I'd love to get any feedback.
Thank you
07-10-2019 12:30 PM
Many thanks for the detailed notes, @Anan Habka . I believe I've tried everything you said on your checklist. And even I tried to rebuilt the environment and servers, and got the exactly same error the 2nd time too. When I run the Repair install, it returned the same error before installing plug-in software. I am really not sure what's going on here.
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!

