Upgraded from CU1 to CU2 of Business Central on-premises

This topic contains 2 replies, has 3 voices, and was last updated by  Locus IT 2 months, 3 weeks ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #20630

    Andrew Jenson
    Participant

    I’ve just recently upgraded from CU1 to CU2 of Business Central on-premises and now I can’t synchronize the schema via PowerShell & the NAV RTC will not run at all.

    #20632

    Anne Smith
    Participant

    Hello Andrew,

    It’s within SQL. If you google it there are scripts that let you view the property & scripts to turn it on or off, using SQL Server Management Studio. If you can’t find let me know & I will post something here for you.

    I noticed CU3 was released yesterday so I’d be interested to know if this issue is just CU2 or CU2 & beyond

    #21060

    Locus IT
    Participant

    Hello Andrew,

    When you open the old database with the new CU02 client and NAV performs the automatic database upgrade task it is enabling change tracking in SQL on the following tables.

    • Add-in
    • Object Metadata
    • NAV App Object Metadata
    • NAV App Tenant App
    • NAV App
    • NAV App Publish Reference
    • Debugger Breakpoint

    By resetting these ie. turning off Change Tracking I have solved the issue.

    This must be a bug with Cumulative Update 2 as this doesn’t occur with CU1.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Skip to toolbar