- 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.
05-12-2022 04:59 AM
When I checked the logs, it tried to create the safe and prov users again and it gave error that safe already exists. Since we have already used all our licenses for CP, it tried to create user again and did not identify the existing user and gave error license limit reached and failed to create the prov user. As a workaround, I have deleted the existing user and ran upgrade again and it was successful. I have to add the user again to the target safes.
I would like to know if someone has experienced similar issue and what has been done to avoid the failure?
Thanks!
Neha Mehta
06-01-2022 06:28 AM
Hi Tchua,
Thanks for the answer but the permission and everything was in place. The problem we faced is a known product defect #00017460 which still hasn't been fixed.
The only workaround is to remove one of the CP app users and run the installation again which we have already implemented.
Thanks!
Neha
05-17-2022 06:26 AM
Hi @Neha Mehta
Thank you for raising this question.
@Teck Chuan Lim - Can you help on this matter?
Thanks,
Gil
05-18-2022 08:16 PM
Hi @Neha Mehta ,
Upgrading of existing CP to v12.4 does not consume new AppProvider user license.
Only new CP installation will consume new AppProvider user license.
The same and current provider user (used for CP to communicate to the Vault) will remain the same and there isn't a need to update any safe(s) memberships.
Probably check what are the errors listed within the CreateEnv.log file found under path C:\Program Files (x86)\CyberArk\ApplicationPasswordProvider\Env\Log
Another area I suspect that might have to lead to your problem is the Vault user used for the upgrade might not have sufficient rights.
Here are some links that might be helpful:
https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-CP/Latest/en/Content/CP%20and%20ASCP/troubleshooting-Installation-Windows.htm
https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-CP/Latest/en/Content/CP%20and%20ASCP/Upgrading-the-Credential-Provider.htm
06-01-2022 06:28 AM
Hi Tchua,
Thanks for the answer but the permission and everything was in place. The problem we faced is a known product defect #00017460 which still hasn't been fixed.
The only workaround is to remove one of the CP app users and run the installation again which we have already implemented.
Thanks!
Neha
06-05-2022 06:18 PM
@Neha Mehta
Thanks for sharing your experience and bug information with the community. 👍
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!

