- 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-09-2019 07:16 AM
Hello - Doing a Manual Install in Azure for Vault Version 10.8, Installs went smooth but encountering an error while running PostInstall command.
Below are the things validated.
1) DNS works
2) test-net connection on 443 works (so no network issues)
3) KVM Machine permissions are set correct
Has anybody experienced this ? Please shed some light if you any resolution.
Thanks
07-29-2019 06:14 PM
Ah Now I see why you have the error. Don’t create a folder dll, just copy all the dlls directly under ‘server’ directory. Please keep me posted
07-29-2019 06:26 PM
there is an another error now but pass through the previous one..
07-29-2019 07:27 PM
Can u run it thro powershell? Make sure you enable tls 1.0 from registry
07-29-2019 07:44 PM
In the registry I've tried both 0 and 1.. but the same error
07-29-2019 07:52 PM
Did you add your Vault machine IPs to the key Vault with below permissions ?
07-29-2019 09:10 PM
tagged vault vm in keyVault's name and selected the permission as mentioned in the document. Is that correct?
07-30-2019 01:52 PM
@Senthilkumar Kothandaraman is the above screenshot is correct? in the key vault access policy I've search selected the VM's name and assigned those three permissions.
07-30-2019 06:57 PM
Thanks @Senthilkumar Kothandaraman Senthil..
Its working now.. just restarted the VM and executed the post install command via CMD (Administrator)
07-30-2019 07:53 PM
Awesome !! Sorry was travelling. Glad you have made it work !!
07-31-2019 09:10 PM
@Nirmalkumar Dhanaraj Were u able to login as Master ?
08-01-2019 11:46 AM
Hey @Nirmalkumar Dhanaraj ..Can you check one thing for me ?
Can you check the Windows Firewall Additional Security property ? As attached. Navigate to "Public Profile"..And Modify the outbound to "Block".
Then restart the vault - and Let me know if your vault comes up.
Per cyberArk they want to keep the Default outbound setting as block. But when you set it to 'block' vault can't communicate to AKV.
Just confirming if it's limited to our Environment.
Thanks.
08-01-2019 07:08 PM
Hi Senthil, Same thing from my vault as well. May be you can ask further details from cyberArk.. In which azure region are you deploying this?
08-07-2019 06:02 AM
Yeah They are checking with R&D. But as a workaround I would enable this start the Vault and then put it back to Block mode. It only needs to be Allow during starting the Vault.
02-25-2020 09:52 AM
This message is for people from the future who are searching on the error code ITATP060E, specifically when installing 11.1.
This is a known bug that was resolved in 11.2.
Hopefully you don't burn as many hours as I did troubleshooting this issue.
ITATP060E Error generating VKM Key. (Cloud vendor: AZURE API Error message: An error occurred while sending the request.).
05-17-2021 02:46 PM
@Christopher McNeil @Nirmalkumar Dhanaraj @Senthilkumar Kothandaraman : Hey All, I am getting this error with v12.1 where Vault is deployed via ARM template. Permissions are checked and that is fine. Should I also try to modify the "Public profile" for firewall to make it work?
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!

