web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

AX 2012 CU3 update - Software update checklist completed but continues to notify during AX login "The model store has been modified"

(0) ShareShare
ReportReport
Posted on by 935

I am trying to setup a new DEMO environment for AX 2012 FP1 w/ CU3.

I first installed FP1 using the FP1 installation Disc. I restored & used the AX Demo database available for download from MS for AX 2012. No issues.

I then applied the CU3 update and after completing the software update checklist I continue to receive “The model store has been modified” message when logging into AX. If I start the software update checklist again everything is marked as Finished except for an item under Data upgrade labeled “Upgrade additional features (required)” and identified as Ready.

I have already completed this item previously and when I click on that check list option to open the upgrade script history screen all entire in that screen are marked with a status of “Finished”

What am I missing to remove this message during login or what can I do to confirm there are no issues with the install or AX environment?

Thanks

*This post is locked for comments

I have the same question (0)
  • Andy Adamak Profile Picture
    4,074 on at

    Having this same problem after upgrading to R2.  Any pointers on what to do to make this go away?

  • Suggested answer
    André Arnaud de Calavon Profile Picture
    301,035 Super User 2025 Season 2 on at

    Check the version of AX by using the form About Microsoft Dynamics AX.

    If you see "Solution version: 6.1.1100.0", you can indeed expect problems.

    If you want to use this demo-set, you can better install AX2012 + CU3 with a clean database. Then export the model store. Restore the demo database. Import the (just exported) model-store again. Compile and synchronize the database.

    This worked for me. The demo database contains the model store, so CU3 was overwritten.

  • Andy Adamak Profile Picture
    4,074 on at

    I'm having the problem in R2... which is version 6.2.158.0.  We were running CU3 previously and that updated without issues.  R2 has been fine thus-far, I just can't get this "Model store has been modified" screen to go away.  I've tried to compile and synchronize, but the screen still pops up on login.

    Thanks

    -Andy

  • busch Profile Picture
    450 on at

    I am having the problem after just completing slip stream upgrade from FP CU3 to R2 CU1.  

    Each client login is also reporting "Object Server 01:  Internal version mismatch. Microsoft Dynamics AX client from XXXAOS (6.2.1000.156) tried to attach with 6.2.158.0 revision of kernel" in the event log.  Help about shows Kernel version: 6.2.1000.156.  AX32.exe lists the Product version as 6.2.1000.156.   However it is strange that  AxDebug.exe has product version 6.2.158.0.  Did the debugger executable not get updated in CU1?

  • busch Profile Picture
    450 on at

    My issue with the always appearing "The model store has been modified" was due to releaseUpdateConfiguration.MinorUpgrade being set.  I got this to reset by opening the Data upgrade checklist for in-place upgrade and marking ALL of the task complete, and closing the check list.    

    I am still getting the version mismatch event log warning.

  • Andy Adamak Profile Picture
    4,074 on at

    Busch,

    What about the tasks that you can't mark as complete?  Such as the very last "Synchronize the database" task.  We get errors due to configuration keys we have turned off, so it's never truly "successful"... but it is.  However, AX wont mark it as complete.  

  • busch Profile Picture
    450 on at

    Andy,

    Sorry, my non-completed tasks were in the top part of the data upgrade checklist so I could go mark them complete.

    You could put a breakpoint for the debugger in the SysCheckList form's close method and you'll see the checks being made.  I don't have access to a system now.. but I beleive you'll find that if you get the isEmpty to return a true result, that check list gets finialized.

  • Heinz Schweda Profile Picture
    1,367 on at

    Hello, had this behaviour recently after upgrading model files. In my case the field MinorUpgrade in table ReleaseUpdateConfiguration was set to 1, so the checklist always opened.

    I fixed this using a job containing this line:

    SysCheckList_Update::finalizeMinorUpgrade();

    Hint: AX uses info.startup() to check, if checklist must be opened.

  • Andy Adamak Profile Picture
    4,074 on at

    Heinz,

    THANK YOU!.  Fixed. You're the best.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans