Skip to main content

Notifications

Microsoft Dynamics NAV (Archived)

Upgrade 2017 Cronos to 2018

Posted on by 222

I have prepared the database as per https://docs.microsoft.com/en-us/dynamics-nav/upgrading-the-data

I created a new server with NAV 2018 installed and working with the 2018 demo database.

I created a new service tier and copied the sql database from the old 2017 server to the new. Put the new database name in the new tier. The new tier has different ports to the original 2018 and when I start the tier it runs but then stops a few seconds after.

I get a lot of info  in the event log this is the last error and the other are warnings for info

Type: System.ObjectDisposedException
Message:
<ii>Cannot access a disposed object.
Object name: 'NavTenant'.</ii>
ObjectName: NavTenant
StackTrace:
at Microsoft.Dynamics.Nav.Runtime.NavTenant.get_Database()
at Microsoft.Dynamics.Nav.Runtime.AssemblyGetter.CompileBusinessApplication()
Source: Microsoft.Dynamics.Nav.Ncl
HResult: -2146232798

Also this warning 

The service could not remove service principal names because the service account could not be found in Active Directory.
Account: NT AUTHORITY\NETWORK SERVICE
Service principal names:
DynamicsNAV/Nav2018Demo:8045
DynamicsNAV/Nav2018Demo:8045

The other working tier uses the same account

Any idea what is wrong here?

*This post is locked for comments

  • PhilDOakley Profile Picture
    PhilDOakley 222 on at
    RE: Upgrade 2017 Cronos to 2018

    I think the spn registration message is not relevant as the working tier also shows errors in the event log when starting and stopping that.

  • PhilDOakley Profile Picture
    PhilDOakley 222 on at
    RE: Upgrade 2017 Cronos to 2018

    No still the same issue using administrator as the service logon. I am using administrator for all the work on this server and the setup etc.

  • Suggested answer
    Suresh Kulla Profile Picture
    Suresh Kulla 43,729 on at
    RE: Upgrade 2017 Cronos to 2018

    Can you try with you local account which has permissions to the DB ?

  • PhilDOakley Profile Picture
    PhilDOakley 222 on at
    RE: Upgrade 2017 Cronos to 2018

    Network service has dbo access to the new db. I also set the network service in SQL to be sysadmin still does not help

  • Suggested answer
    Suresh Kulla Profile Picture
    Suresh Kulla 43,729 on at
    RE: Upgrade 2017 Cronos to 2018

    It looks like the service account Network Services does not have proper permissions on your converted database, please assign the permissions and try again.

  • PhilDOakley Profile Picture
    PhilDOakley 222 on at
    RE: Upgrade 2017 Cronos to 2018

    I run as administrator for the dev env

    Without the tier running it is not possible to set the database to the correct tier in the dev env or to run the sync function. Something in the dtabase is stopping the service running.

  • Suggested answer
    Mohana Yadav Profile Picture
    Mohana Yadav 59,077 Super User 2024 Season 2 on at
    RE: Upgrade 2017 Cronos to 2018

    Opening development environment with Run as Administrator will solve these kind of issues sometimes.

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

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Complete!

🔔 Be sure to subscribe to the new forums you are interested in to stay up to date! 🔔

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,113 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 229,918 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans