The Model Store has Been Modified &The number sequence for party records is not set

15 Jun

Yesterday I was  preparing an AX enviornment with an upgrade of AX 2012 RTM to CU8 and CU9 and found myself having a strange issue.

I have installed Dynamics AX 2012 RTM with slipstreaming of CU8 and CU9 and imported the home made vertical model on the same.As part of the upgrade you need to complete a checklist including such things as Compile application and detect conflicts.

When I opened the environment first time after importing the model then after upgrading Microsoft Dynamics AX 2012 you will get the following dialog upon starting the AX client:


When I have performed the appropriate upgrade actions (AOT compile, code check, CIL compile, synchronize, upgrade scripts), the dialog still might pop up every time you start the client. Selecting “Skip” was not solved this.I run  through all these processes multiple times but everytime i was getting the same dialog popup “The Model Store has Been Modified“.

I installed AX on single server with AX 2012 R3+CU8+CU9.I also compiled application with client and AXBuild for Parallel Compile on AOS of X++ to p-code and  also had synchronized the client via database and via AOT.

I googled multiple places and found few solution to get rid of this dialog popup like

Solution 1 :AXUTIL set /noinstallmode which prevents the AX client initialization checklist

Solution 2:If you can access SQL server open SSMS locate ReleaseUpdateConfiguration Table update the column MinorUpgrade “One” to “Zero”.

Solution 3:

a)Prevent the dialog from appearing by clicking
System administration > Setup > Checklists > Prevent startup of checklist

b)Even after above steps still the pop up is coming then write a job containing this line


I have tried all mentioned option which  helped me get rid of this popup but does not solved my problem.when i started opening user interface(forms) then i started getting another  error message in every module of AX. when i again tried to perform checklist:(

“The number sequence for party records is not set”

Now again I thought to perform Compile,CIL and Synchronize but doesn’t matter how many times I compile, CIL compile or sync (successfully),the error remain same and checklist remains saying that these items still need to be completed.I also spent so many hours to resolve this but no success.

I found an blog which clarified the reason  to solve ‘The number sequence for party records is not set.’. It only appear after when we import the ISV, VAR and USR models.

Root cause:It turns out the offending code was in the ISV model(Campus Nexus) in the startupPost() method on the Info class.our ISV model has a piece of code changes application behavior during startup.

Inside the startupPost() and startup() method was a find method that selects Table SYSSetupLog  which contains status information of initialization checklist and application wasn’t able to update the same for compile,CIL and Synchronization.So Kernel was considering model store is dirty. its little hard to digest.


1.Truncate the SysSetupLog table from SQL using DELETE FROM SYSSETUPLOG).

2.Create the following job and run it inside AX:



This job is saving a record SysCheckList_Upgrade with description status Finished  in Table SysSetupLog because AX 2012 R3 CU9 Data Migration/Upgrade did not correctly set the SysCheckList_Upgrade SysSetupLog entry to Finished, but it is Executed.

3.Restart AX Services and Issue Resolved. 🙂

I will explore little more and will update on same page if found something.for me its solved the problem time being.

Special Thanks for below articles which helped me to solve my issue.for more details please refer below articles links :

Number sequence error when starting the Upgrade checklist

The Model Store Has Been Modified – AX2012 R3 CheckList

The Model Store has Been Modified – AX2012 R3 CheckList Issue

The model store has been modified

Happy Daxing 🙂


One response to “The Model Store has Been Modified &The number sequence for party records is not set

  1. Tina van der Vyver

    June 20, 2016 at 7:12 pm

    Hi Deepak! I am glad my post helped you. ISV’s should be more aware of how their code can affect the application during different states. Good that you resolved your issue!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: