Skip to main content

MSDYN365BC - Publish Extension Error - NetFx40_LegacySecurityPolicy is enabled and must be turned off.

Hi Readers,

I hope till this time everyone would have tried creating and publishing extension on Business Central
on-Prem Version.

If you haven't then start and learn how to do that. If you already started doing this you might be getting an error message while publishing extension.

In this article, we will discuss how to fix NetFx40_LegacySecurityPolicy issue.


Error Message - 

The request for path /DynamicsNAV130/dev/metadata failed with code InternalServerError.
Reason: NetFx40_LegacySecurityPolicy is enabled and must be turned off in the Microsoft.Dynamics.Nav.Server.exe.config file.



To Fix this issue - 

1. Open Notepad as Administrator. 
     Navigate to C:\WINDOWS\system32.
     Right click on Notepad and select Run as administrator.
   

2. Open "Microsoft.Dynamics.Nav.Server.exe" file from Service Folder as shown below.


3. Change the NetFx40_LegacySecurityPolicy parameter from true to false. Save the file.

4. Restart NAV Service.

5. Try publishing extension again, it should get published successfully.


Hope you find the information useful.

Regards,
Saurav Dhyani.
www.sauravdhyani.com

Comments

  1. Hi Saurav,

    I faced this problem and carried out the steps mentioned in your blog. I am glad it has worked and the NetFX error got resolved.

    Many thanks for posting this.

    Krupesh

    ReplyDelete
  2. Hi Saurav,

    Your posts are always helpful. Thank You so much for the valuable info. The error got resolved.

    Thanks once again.

    Shikha

    ReplyDelete
  3. Hi Saurav,

    I do not know where I would be without you. The knowledge that you share is always a huge help!

    Thank you as always.

    KT

    ReplyDelete
    Replies
    1. Thanks KT for the kind words.
      It great to hear that i was able to help.

      Delete
  4. Hi Saurav there are implications of this change?

    ReplyDelete
    Replies
    1. I Don't think as this problem does not exist in future versions.

      Delete

Post a Comment

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searching for the error i figured out the issue was due to - Design change in NA

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.