Update NAV2017 to new CU

Jan87

Hi experts,

we try to update a NAV2017 CU12 to CU26. When we try to start the service we get the following error:

"ServerInstance 'MicrosoftDynamicsNavServer$NAV2017-Testing_B' failed to reach status 'Running' on this server due to the following error: 'Cannot start the service.'. Additional information may be in the event log of the server."

In the event log there is only this:

Type: Microsoft.Dynamics.Nav.Management.Exceptions.NavServerInstanceException
SuppressMessage: False
SuppressExceptionCreatedEvent: False
FatalityScope: None
Message: <ii>ServerInstance 'MicrosoftDynamicsNavServer$NAV2017-Testing_B' failed to reach status 'Running' on this server due to the following error: 'Cannot start the service.'. Additional information may be in the event log of the server.</ii>
StackTrace:
at Microsoft.Dynamics.Nav.Management.NavServerInstanceBase.WaitForStatus(ServiceController sc, ServiceControllerStatus status)
at Microsoft.Dynamics.Nav.Management.NavServerInstanceBase.StartService(String serverInstanceName)
at Microsoft.Dynamics.Nav.Management.Cmdlets.SetNavServerInstance.InternalProcessRecord()
at Microsoft.Dynamics.Nav.Management.NavCommand.ProcessRecord()
Source: Microsoft.Dynamics.Nav.Management
HResult: -2146233088

We tried the following:

* use all different users (lokal admins, network users, normal users)
* uninstall reinstall
* copy files from DVD (when we copy the files from cu12 back the service starts again)

Hope anyone have an idea.

malintus

@Jan87 Try solutions from link above:
https://community.dynamics.com/nav/f/34/t/223086?pi61892=2#responses

Duikmeester

Did you open the database with a Development Environment (finsql.exe)?
There is probably a database conversion necessary which is triggered by opening the database.

Jan87

Thanks for the reply,

but it didn't start even without a database or an converted database.

malintus

@Jan87 Try solutions from link above:
https://community.dynamics.com/nav/f/34/t/223086?pi61892=2#responses

Jan87

Thanks for the reply. We found the same solution yesterday night.

We had to install the .Net 4.7.2 and everything worked fine