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
Labels:
Location: Dehradun, Uttarakhand, India

Comments

  1. RishiFebruary 25, 2019 at 9:55 AM

    Awesome It really works.

    ReplyDelete
  2. Krupesh & FamilyApril 24, 2019 at 2:52 PM

    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
  3. UnknownOctober 22, 2019 at 1:58 PM

    Hi Saurav,

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

    Thanks once again.

    Shikha

    ReplyDelete
  4. UnknownJanuary 22, 2020 at 6:00 PM

    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. Saurav DhyaniJanuary 24, 2020 at 11:28 AM

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

      Delete
  5. Ethan0kDecember 17, 2020 at 11:34 AM

    Hi Saurav there are implications of this change?

    ReplyDelete
    Replies
    1. Saurav DhyaniJanuary 6, 2021 at 7:22 PM

      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    ---------------------------
10 comments
Read Complete Article »

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.
Post a Comment
Read Complete Article »

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all, As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes. Let's start the process. Remember -  1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only. 2) The Synchronization of users with SQL Server is no more required.
1 comment
Read Complete Article »