Permission error when upgrading from Business Central 16.1

MarcusRBMarcusRB Member Posts: 39
Hello,

I am trying to upgrade Business Central 16.1. I have tried upgrading to 16.2, 16.6 & 16.10.

No matter the version, when I run the command
Start-NAVAppDataUpgrade -ServerInstance BC160 -Name "System Application -Version 16.10.21502.0"

I get the following error:
4jdys1wp2szi.png

The "same" error, has also looked like this with later CU's (e.g. 16.6 & 16.10):
tki5milxcusk.png
This is mainly for SEO:
Start-NAVDataUpgrade : Could not upgrade the extension System Application for tenant default due to the following error: You do not have the following permissions on TableData Plan: Modify.

Any help is appreciated :smile:

Best Answer

  • MarcusRBMarcusRB Member Posts: 39
    Accepted Answer
    The issue has been resolved. I had earlier tried to import our developer license and seen it work, but then cause a different error. I have now tried to import our developer license before starting the upgrade, and that worked.

    So:
    1. Import developer license.
    2. Begin upgrade.

Answers

  • MarcusRBMarcusRB Member Posts: 39
    edited 2021-02-15
    These are the steps I'm taking:
    1. Download latest cumulative update.
    2. Back up the database.
    3. Run the Business Central Administration Shell as an administrator.
    4. Uninstall all extensions.
    Get-NAVAppInfo -ServerInstance BC160 | % {Uninstall-NAVApp -ServerInstance BC160 -Name $ _. Name -Version $ _. Version -Force}
    Note: There will be some yellow errors.
    5. Remove the existing symbols.
    Unpublish-NAVApp -ServerInstance BC160 -Name System
    6. Stop the nav instance.
    Stop -NAVServerInstance -ServerInstance BC160
    7. Run setup.exe from cumulative update to uninstall current business central.
    Run setup.exe from cumulative update to install latest business central.
    Select custom installation.
    Select AL Development Environment.
    Select Server Administration Tools.
    Select Server & Opportunity to test the page.
    Select Web Server Components.
    Fill in the same information as originally used, but leave the SQL database field blank.
    8. Log in to the server with the administrator account.
    9. Convert the database to the latest version.
    Invoke-NAVApplicationDatabaseConversion -DatabaseServer Redacted -DatabaseName "Redacted"
    10. Connect the nav instance to the database.
    Set-NAVServerConfiguration -ServerInstance BC160 -KeyName DatabaseName -KeyValue "Redacted"
    11. Restart nav instance.
    Restart-NAVServerInstance -ServerInstance BC160
    12. Release the new system symbols.
    The app package with the symbols can be found here in the DVD folder for the cumulative update.
    Publish-NAVApp -ServerInstance BC160 -Path "C:\Redacted\Dynamics.365.BC.21502.DK.DVD\ModernDev\program files\Microsoft Dynamics NAV\160\AL Development Environment\System.app" -PackageType SymbolsOnly
    13. Repair released extensions.
    Get-NAVAppInfo -ServerInstance BC160 | Repair-NAVApp
    Note: There will be some red warnings.
    14. Restart nav instance.
    Restart-NAVServerInstance -ServerInstance BC160
    15. Sync.
    Sync-NAVTenant -ServerInstance BC160 -Mode Sync
    16. Release the System Application app.
    Publish-NAVApp -ServerInstance BC160 -Path "C:\Redacted\Dynamics.365.BC.21502.DK.DVD\Applications\System Application\Source\Microsoft_System Application.app"
    17. Sync with the System Application app.
    Sync-NAVApp -ServerInstance BC160 -Name "System Application" -Version 16.10.21502.0
    18. Upgrade data for the System Application app.
    Start-NAVAppDataUpgrade -ServerInstance BC160 -Name "System Application" -Version 16.10.21502.0
  • irasoelbaksirasoelbaks Netherlands, theMember Posts: 80
    Please check if you have Modify permissions on the 'Plan' table. Permissions should be Ok on both license as authorization level.
  • MarcusRBMarcusRB Member Posts: 39
    Accepted Answer
    The issue has been resolved. I had earlier tried to import our developer license and seen it work, but then cause a different error. I have now tried to import our developer license before starting the upgrade, and that worked.

    So:
    1. Import developer license.
    2. Begin upgrade.
  • irasoelbaksirasoelbaks Netherlands, theMember Posts: 80
    edited 2021-02-17
    I don't know what's happening in the upgrade but you could get problems because now 'unlicensed' (setup) tables could/are being 'touched' where the normal license doesn't have access to. This will sooner or later result in errors for the end users.
Sign In or Register to comment.