Jump to content
  • 0

Certificate and composting issue with Citrix App Layering 2009 upgrade


Venkat Bhimisetty

Question

After upgrading from 2005 to 2009 App Layering in Prod I am getting an error message while creating a version to OS Layer “The issuing certificate does not have a usable private key”.

 

In Dev App Layering I am getting "Waiting for the Compositing Engine machine to be ready" and after 20 minutes "The Compositing Engine failed to initialize after '00:20:00'."before the upgrade it used to work fine.

 

It happens on every layer (App, OS, Platform) I want to add  a Version :(

 

Config:

OS: Windows 10 1909

Connector: vSphere and PVS

Upgraded from 2005

 

image.thumb.png.53013c47fc79319adee6c1eac000e2c8.png

Link to comment

6 answers to this question

Recommended Posts

  • 1

This worked for me when i got that error

First create a snapshot of the appliance

Then logon to the console as root with putty

 

Run

certmgr -list -c -m Root | grep -C 3 CN=DefaultRootCertificate

 

That will output a unique hash which you use in the next command


certmgr -del -c -m Root <UniqueHashHere>

 

Test creating layers.

If it works then delete the snapshot

  • Like 1
Link to comment
  • 0
On 10/2/2020 at 11:00 AM, Rob Zylowski1709158051 said:

This worked for me when i got that error

First create a snapshot of the appliance

Then logon to the console as root with putty

 

Run

certmgr -list -c -m Root | grep -C 3 CN=DefaultRootCertificate

 

That will output a unique hash which you use in the next command


certmgr -del -c -m Root <UniqueHashHere>

 

Test creating layers.

If it works then delete the snapshot

It is working now, Thank you!!

Link to comment
  • 0

I just upgraded yesterday and have the exact same issue.

I ran the commands and tried creating a new application layer and still get the same error.

“The issuing certificate does not have a usable private key”.

Any progress on this?

I just tried this also same outcome.

https://discussions.citrix.com/topic/410573-certificate-error-after-upgrading-to-elm-2009/

 there was another upgrade today. When it finished downloading I installed it and now things seem to be working again.

 

Link to comment
  • 0

Hello, 

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

 

It worked fine for me.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...