- 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-09-2019 04:52 PM
I'm in 10.9 and facing the same issues..
07-09-2019 08:11 PM
We were able to go beyond this error - just enable TLS1.0 from registry "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols" since powershell is expecting tls1.0 enabled.
But sadly we experienced an issue with Private key not being accepted.
Please let me know if you are able to bypass this error after enabling TLS 1.0.
Also please make sure TLS 1.0 is disabled after the PostInstall command was completed successfully.
07-29-2019 02:29 PM
Hi @Senthilkumar Kothandaraman how did you resolve this? I'm also struct now in the same place where you shown in your above screenshot :
ITATP059E Error getting random bytes from cloud vendor. (Cloud vendor: AZURE API Error message: Could not load file or assembly 'AKVCSharpAPI, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies).
07-29-2019 02:39 PM
Hello Nirmal - Did you copy the Azure DLLs and PACLI folder to the Vault 'Server' Directory ? From the Error it looks like it i expecting a missing DLL in the 'Server' Directory.
There is a documentation bug in the Azure doc.
07-29-2019 02:44 PM
Can you also check if you can resolve your AKV name - "azure-key-vault01" from Vault server ?
07-29-2019 04:32 PM
what did you do for resolving KeyVault? may I know please ?
I've included below things in the dbparam.ini but its helpful I gues
AllowNonStandardFWAddresses=[192.168.1.6],Yes,3389:outbound/udp,3389:inbound/udp
AllowNonStandardFWAddresses=[192.168.1.6],Yes,3389:outbound/tcp,3389:inbound/tcp
AllowNonStandardFWAddresses=[168.63.129.16,169.254.169.254],Yes,53:outbound/tcp
AllowNonStandardFWAddresses=[168.63.129.16,169.254.169.254],Yes,443:outbound/tcp
AllowNonStandardFWAddresses=[13.72.250.239],Yes,53:outbound/tcp
AllowNonStandardFWAddresses=[13.72.250.239],Yes,443:outbound/tcp
07-29-2019 04:37 PM
Just followed the below steps.
1) Copied all DLLs and PACLI folder to server Directory
2) Made sure the AKV name is resolved from Vault server (nslookup)
3) Made Sure by Test-netconnection that I can reach the AKV name on 443
You have to copy all the DLLs to server folder.
Refer the Attached screenshot - the AKVCSharpAPI.dll is one of the Azure DLLs. Can you confirm you copied ?
07-29-2019 04:41 PM
If you have all the DLLs available and still you can't connect, then try running the command from powershell. Enable below for before you run :-
Enable TLS1.0 from registry for both client & server
"HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0"
You can disable it after command is executed succesfully
07-29-2019 04:57 PM
I think the problem is with resolving DNS.. all other things you've mentioned are validated and it there ..
07-29-2019 05:36 PM
But looks like your Powershell can resolve it, it is weird. Can you run the PostInstall command from powershell after enabling TLS 1.0 ? And let me know what you see
07-29-2019 05:46 PM
Same message as cmd when I run it from PS
07-29-2019 05:55 PM
Did you copy all the DLLs individually to the 'Server' Directory ? or copied to a folder in 'Server' Directory ?
07-29-2019 06:11 PM
copied to a folder in 'Server' Directory .. refer my placements below
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!

