@Ephraim Malane - without having the actual CCR IDs, most likely the case is that your CCR deployed through TEST added a file, and CCR will automatically detect if the CCR that added a file is not yet in the target environment and therefore will prevent other CCRs from 'leap-frogging' past it.  This is because if you leap past a CCR which originally adds a file, if you later need to back out the CCR it will result in a 'delete' of the file from all environments (because you're undoing an 'add').  

Probably the best bet for you is to reach out to Support so they can help you manually move the 'add' into the CCR that you want to move forward.  You will probably also need help cleaning up the CCR that you cancelled, as I am guessing that the backout failed due to edits already being promoted to TEST on top of the 'add' that you are trying to back out from there.

I love the subject matter - I was touring Independence Hall in Philadelphia on New Year's Eve with my family (which is where this document was signed).  Following up with watching '1776' (the musical), and "National Treasure" in the following couple of days :)  So I've been having a lot of focus on the U.S. Declaration of Independence recently ;)   

Evgeny - if you can track non-registered users on the side, do they get included in the "View Count" for each article?  Or do only logged in readers get counted?

Another contributing factor in the underreporting of readers is the participants who read the articles via email.  I at least scan every article and question on the D.C. via my Inbox as I prefer an email-centric workflow.  However, I am counted as a 'reader' only on those articles and questions which I decide to comment on or answer.  I am sure I am not the only one consuming the D.C. content in this way.

@Jamshid Dehghanian  - You are running a Community Edition of InterSystems IRIS for Health, and the built-in license key will only work for approximately one year and then will expire ... this may lead to the message you're seeing.  Options include:

- Go to Evaluation.InterSystems.com and download the latest version of InterSystems IRIS for Health Community Edition

- Reach out to your account manager and ask for an extended Community Edition key that you can install on your instance

Note - your routines and classes will be stored within the Routine DB for your Namespace, so you should be able to look in the SMP and see which iris.dat this is and you can just make a copy of that file on the OS level (stop InterSystems IRIS first).  This will ensure that you don't lose anything for that namespace.  You can also back up your data database if that is important to you.  When you upgrade to a newer kit these should be preserved anyway, but I understand you'd like extra insurance so this is the way to ensure that.

Hope that helps