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

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.
28 comments
Read Complete Article »

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.
21 comments
Read Complete Article »

🚀 Exploring Vibe Coding with GitHub Copilot for Business Central.

Hi All, In a recent #BCOpenDiscussion session, we delved into the fascinating concept of Vibe Coding —a new way of building software where developers collaborate with AI (like GitHub Copilot) to co-create solutions.  The session covered practical setup, how AI understands context, and even touched on Microsoft's new Model Context Protocol (MCP) integration for enhanced learning. Let’s break down the journey, step by step.
Post a Comment
Read Complete Article »