App Layering 2011 : After ELM Upgrade to 2011 from 2005, adding layer version gives "The issuing certificate does not have a usable private key."
Article ID: CTX296764
Updated On:
Description
--after upgrading ELM from 2005 to 2011
-- getting an error when we try to add a version to a layer "The issuing certificate does not have a usable private key."
-- have offload compositing enabled on vCentre connectors
Resolution
Connect via Putty session to ELM, as root, and run the following commands :
1. certmgr -list -c -m Root | grep -C 3 CN=DefaultRootCertificate
2. certmgr -del -c -m Root <UniqueHashHere>
3. systemctl restart maservice
4. certmgr -list -c -m My | grep -C 3 JwtCertificate
5. certmgr -del -c -m My <uniquehash>
6. systemctl restart maservice
1. certmgr -list -c -m Root | grep -C 3 CN=DefaultRootCertificate
2. certmgr -del -c -m Root <UniqueHashHere>
3. systemctl restart maservice
4. certmgr -list -c -m My | grep -C 3 JwtCertificate
5. certmgr -del -c -m My <uniquehash>
6. systemctl restart maservice
Problem Cause
Issue with certificate private key
Was this article helpful?
Yes
No
Powered by
