Wave 2 Upgrade from BC Spring

ara3n
ara3n Member Posts: 9,258
in NAV Three Tier
Hello I'm testing/upgrading an unmodified database for practice/experience/confirmation. I'm following the following the steps by MS.

Here is the link

Under Task 6: Synchronize the tenant, system application, and base application extensions
Step 4. Synchronize the tenant with the Business Central Base Application extension (Microsoft_BaseApp):

I'm running the following command.
Sync-NAVApp -ServerInstance BC150 -Tenant default -Name "Base Application" -Version 15.0.36560.36649

The documentation has a different version. My guess is because it's the W1 version. I'm doing the NA version. To get the version code you can run cmd 
Get-NAVAppInfo -ServerInstance BC150

PS C:\WINDOWS\system32> Get-NAVAppInfo -ServerInstance BC150
Id : 63ca2fa4-4f03-4f2b-a480-172fef340d3f
Name : System Application
Version : 15.0.36560.36649
Publisher : Microsoft
ExtensionType : ModernDev
Scope : Global

Id : 437dbf0e-84ff-417a-965d-ed2bb9650972
Name : Base Application
Version : 15.0.36560.36649
Publisher : Microsoft
ExtensionType : ModernDev
Scope : Global

I'm getting the following error in step 4
Sync-NAVApp : The following SQL error was unexpected:
There is already an object named 'Cronus Dynamics$G_L Entry$437dbf0e-84ff-417a-965d-ed2bb9650972$VSIFT$Key6' in the database.
At line:1 char:1
+ Sync-NAVApp -ServerInstance BC150 -Tenant default -Name "Base Applica ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Sync-NAVApp], InvalidOperationException
+ FullyQualifiedErrorId : MicrosoftDynamicsNavServer$BC150/default,Microsoft.Dynamics.Nav.Apps.Management.Cmdlets.SyncNavApp


Step 3 that sync the "system application" worked fine.
Sync-NAVApp -ServerInstance BC150 -Tenant default -Name "System Application" -Version 15.0.36560.36649

There are two companies in the database.
Ahmed Rashed Amini
Independent Consultant/Developer


blog: https://dynamicsuser.net/nav/b/ara3n

Answers

  • ara3n
    ara3n Member Posts: 9,258
    found the solution on yammer.

    The solution is to wait for 15 cu 1 or when doing the migration is to upgrade to bc 14 cu 5 first.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • ara3n
    ara3n Member Posts: 9,258
    Ran into second error.
    Sync-NAVApp : Table OAuth 2.0 Setup :: Unsupported field change. Field:Access Token Due DateTime; Change:Remove
    At line:1 char:1
    + Sync-NAVApp -ServerInstance BC150 -Tenant default -Name "Base Applica ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (:) [Sync-NAVApp], InvalidOperationException
    + FullyQualifiedErrorId : MicrosoftDynamicsNavServer$BC150/default,Microsoft.Dynamics.Nav.Apps.Management.Cmdlets.SyncNavApp
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • ara3n
    ara3n Member Posts: 9,258
    I got around the problem and deleted the table. Since the client isn't using it.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • coder
    coder Member Posts: 16
    edited 2019-10-24
    Sync-NAVApp : The following SQL error was unexpected:
    There is already an object named 'Cronus Dynamics$G_L Entry$437dbf0e-84ff-417a-965d-ed2bb9650972$VSIFT$Key6' in the database.
    At line:1 char:1
    + Sync-NAVApp -ServerInstance BC150 -Tenant default -Name "Base Applica ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (:) [Sync-NAVApp], InvalidOperationException
    + FullyQualifiedErrorId : MicrosoftDynamicsNavServer$BC150/default,Microsoft.Dynamics.Nav.Apps.Management.Cmdlets.SyncNavApp



    Have you got the resolution for the above issue.
    Or should we wait for CU1 for BC15.
  • ivancito86
    ivancito86 Member Posts: 18
    Hi,

    I get the same error, I upgraded to version 14.5 and then to 15 but the error is the same. It can't be possible that we have to wait the next cumulative, possibly in the next cumulative will get another error and I will have the next Cu... of Microsoft I already wait what it being.

    Somebody have found a solution of that without I have waiting??

    Best regards.
  • ara3n
    ara3n Member Posts: 9,258
    You probably upgraded to 14.6 instead of 14.5 . In 14.6 you get another error about another table. I solved by deleting the table, and yes we have to wait for CU 1 for a fix.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • Madhurigore
    Madhurigore Member Posts: 1
    edited 2019-10-30
    Grate Information was very useful for me..

    https://hyderabad.crbtech.in/programmes/dba-training-programme/

Categories