Error, while Install NAV2016 CU29 or higher ServiceTier

Me_Ontour
Me_Ontour Member Posts: 11
edited 2018-06-23 in NAV Three Tier
Hi Folks,

I tried to Ugrade all our ServiceTiers today,
but i could not Install CU29 or Higher (up to CU32) on our WIN 2008/2012 R2 Machines

The Install Process aborts with a Message, that Due to a Permission Problem, The Service is not able to Start.

This is the Message from the Server-Protocol

Server instance: DynamicsNAV90
Tenant ID:
User:
Type: Microsoft.Dynamics.Nav.Types.NavConfigurationException
SuppressMessage: False
SuppressExceptionCreatedEvent: False
FatalityScope: None
Message: 'SecurityProtocol' has an invalid value.
StackTrace:
bei Microsoft.Dynamics.Nav.Types.ServerUserSettings.LoadProperties()
bei Microsoft.Dynamics.Nav.WindowsServices.DynamicsNavServer.Main(String[] args)
Source: Microsoft.Dynamics.Nav.Types
HResult: -2146233088


Does anyone encountered the same problem ?


Cheers,

Chris

Answers

  • Antoniomvalls
    Antoniomvalls Member Posts: 34
    edited 2018-06-25
    it could be because of the new GDPR property "DataClassification".

    An application upgrade is needed

    Giving thanks is always wellcome
  • Me_Ontour
    Me_Ontour Member Posts: 11
    edited 2018-06-26
    Hi,

    The database is converted to CU32 and
    on our other Servicetier-Servern with WIN 2016 there is no Problem.

    Therfore it could not be GDPR, couldn't it?
  • Antoniomvalls
    Antoniomvalls Member Posts: 34
    then probably. I cannot help u more sorry
    Giving thanks is always wellcome
  • aayala
    aayala Member Posts: 2
    Hello,

    I have same problema on two customers installing last CU for NAV 2016 and 2017. There is any resolution?

    Thanks a lot
  • RemkoD
    RemkoD Member Posts: 100
    aayala wrote: »
    I have same problema on two customers installing last CU for NAV 2016 and 2017. There is any resolution

    For NAV 2017 CU19 and CU18 we've encountered an issue with installing NAV or starting a NAV Service after upgrading manually. Described in more detail in this post. We've settled with CU17. Reinstalling .NET could resolve the issue.

    The error with NAV 2017 we encountered is different from the one described by Me_Ontour in this post.
  • aayala
    aayala Member Posts: 2
    Thanks RemkoD
  • PawanCDK
    PawanCDK Member Posts: 1
    Me_Ontou,

    Did you find a solution to your problem?

  • RemkoD
    RemkoD Member Posts: 100
    @PawanCDK
    In most cases upgrading the .NET framework to 4.7.2 on the server is sufficient to install NAV2017 CU18 or higher.
  • danizahu87
    danizahu87 Member Posts: 1
    RemkoD wrote: »
    @PawanCDK
    In most cases upgrading the .NET framework to 4.7.2 on the server is sufficient to install NAV2017 CU18 or higher.

    Thank you very much! Upgrading the .NET framework to 4.7.2 on the server fixed my problem of updating Navision 2015 to the latest CU

Categories