Cannot finalize app layers after upgrade from 2003 to 2009. “a Microsoft NGen operation is needed”

[Rene Tap1709160993]

Cannot finalize app layers after upgrade from 2003 to 2009.

When I choose Finalize it comes up with “a Microsoft NGen operation is needed”. It doesn’t matter if I run ngen update several times and I’ve tried it also with the force switch. The registry keys HKLM\SOFTWARE\Microsoft\.NETFramework\v2.0.50727\NGenService\Roots\WorkPending and HKLM\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727\NGenService\Roots\WorkPending both have the value 0

When I create a new layer and open the LayerIntegrity.txt file the message “a Microsoft NGen operation is needed”. Is already there while there isn’t any application installed yet.

 

I’ve restored the ELM to the version before the upgrade every thing works fine again and the is no message in the LayerIntegrity.txt file only “”

 

Thanks

René

[Raymond Colon]

In addition to following the article, especially the part to run, ngen eqi 3.. Should you continue to see the message, the OS layer itself may need to complete the ngen operation(s), following the article.. You should add a version to the OS layer, do Shutdown For Finalize. If you see the message follow the steps in the article. Finalize the layer, then use that version to update, create layers.

 

In our latest release, we are doing a better job of detecting and prompting for ngen to be ran, we were not in the past. This is why you may not see the same ngen message using an older release.

 

 

[Penny Adams]

Morning,

 

Make sure you follow this article:

https://support.citrix.com/article/CTX222099

 

Especially where you run NGEN in both Framework and Framework64

 

 

[Rene Tap1709160993]

Thanks Raymond, I will run the update to 2009 again (next week) and I will add a new version of the OS layer and from that version I will create a new app layer. I will let you know if this solves the problem

 

 

 

[Rene Tap1709160993]

Thanks Raymond and Pennyad,

 

Creating a new version of the OS layer and using ngen eqi 3 instead of ngen update before finalize was the solution.

 

Thanks

René