AX 2012 incremental CIL production

(0) Share

Report

Posted on by Renaud PAQUAY

Hi,

Sometimes you need to fix a bug in the production environment in the USR layer.

Once the bug fix is installed, if the code could be run on the server side or whathever, you have to run the incremental CIL process. The production AOS is up and running at this stage.

Most of the time, we don't have any problems at all, everything's fine, but sometimes, the AOS crashes....and we've got plenty of unhappy users.

Does anyone know what are the risks to execute CIL on a running production environment ? Does anyone has the same symptoms/problems ?

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (0)

dolee 11,279 on at

Like (1)

Report

RE: AX 2012 incremental CIL production

Hi Paquay,

No I didn't mean that. There will be down time but it'll be shorter with the modelstore approach because you won't be generating CIL after deploying the updated code/model.

Was this reply helpful? Yes No
Nabeel Shoaib Faruqui on at

Like (0)

Report

RE: AX 2012 incremental CIL production

Dear Dominic Lee,

Are you saying that resoration of Model Store will not bring a downtime? as per my knowledge, restoration also requires downtime until the model is restored successfully.

Was this reply helpful? Yes No
Suggested answer

rudra 6,534 on at

Like (0)

Report

RE: AX 2012 incremental CIL production

Hi Renaud,

As everyone said do not touch development workspace in Production environment, if you found there is some issues with Production environment, please replicate the Production database to the Test Environment and play as you need.For this reason only Microsoft has brought the concept of having Test environment, implementing directly to Production is not advisable in some cases you might get the long downtime if your aware of the issue.

I think this is most easiest way to make your users happy with Production environment.

Was this reply helpful? Yes No
Suggested answer

Kumar Gaurav @ MS on at

Like (0)

Report

RE: AX 2012 incremental CIL production

CIL generation causes system services reset therefore should never be done in live while users are still on it. Also make sure that no batch process is running. You need to take a window with no user and no batch process to run CIL

Was this reply helpful? Yes No
dolee 11,279 on at

Like (0)

Report

RE: AX 2012 incremental CIL production

Yeah I see what you mean, but what Jo, Dennis and I saying are basically you can't guarantee a hassle free quick fix because it's not supported.

And since Microsoft have not done any testing/fine tuning to support the use case you mentioned, there could be other errors that's harder to find.

In the end, I think it is for the good of the users to use a supported way to do things because, even though more time is needed to fix an issue, their work is safer this way.

Was this reply helpful? Yes No
Renaud PAQUAY on at

Like (0)

Report

RE: AX 2012 incremental CIL production

Hello everybody,

Thank you for your answers. I know the healthy and standard way of doing these kind of fixes is to build a new modelstore in a preproduction environment and so on, like explained in the whitepapers

But I'm talking here about a critical bug fix that need to be fixed in the production environment because a functionnality is down and everyone is waiting for the functionnality to work again. For example an error in an Aif interface with thousand of documents running per minute :-)

Don't you ever had to fix something in the production env ?

Was this reply helpful? Yes No
Suggested answer

Denis Macchinetti 16,444 on at

Like (0)

Report

RE: AX 2012 incremental CIL production

Hi Renaud

I'm agree with Dominic.

Also, read the Dynamics AX 2012 White Paper: Deploying Customizations Across Microsoft Dynamics AX 2012 Environments

www.microsoft.com/.../details.aspx

Was this reply helpful? Yes No
dolee 11,279 on at

Like (0)

Report

RE: AX 2012 incremental CIL production

Hi,

I don't think the case of compiling CIL in a operating Production environment is supported. May be you should consider other deployment strategy.

Consider having a copy of the production environment available. When in need to apply hot fixes, apply them to the copy first, then you can do compilation and CIL generation. Once that's done, export the modelstore and deploy it to the production environment.. You do need down time. However, no compilation/CIL generation is required so it shouldn't be long.

Was this reply helpful? Yes No
Jo Neetesonne 175 on at

Like (0)

Report

RE: AX 2012 incremental CIL production

I would never fix a bug in production by importing an xpo...

This is a recipe for disaster, as you have already experienced.

Always try to reproduce the bug in test environment and fix it there, before doing a full modelstore update of the production environment.

Was this reply helpful? Yes No