Skip to main content

NAV 2013 & R2 - You do not have the following permissions on Codeunit ApplicationManagment: Execute.

Hi all,

In NAV 2013 and NAV 2013 R2 a conman issue faced is -

"You do not have the following permissions on Codeunit ApplicationManagment: Execute."

Steps to Resolve -

1. If the database have been received from different database (from client) and users inside database have no user of your domain then -

> Delete all user specific details from SQL. Refer Post for the command.

2. If the database have users from your domain and someone can login but not you, please check role provided to your User.

3. If the database have users but no one is able to access the Role Tailored (Windows) Client then follow steps as below -

a. Check the User which is being used to run services as shown below.

b. Open SQL Server navigate to Securities - Logins.

c. Select the properties of User which is used to run services, in my case Network Service.
(Should be a domain account with password expiration policy set to NEVER)

d. Navigate to User Mapping from Left Panel.

e. Click on MAP Boolean and Select Default Schema as db_owner as shown below.

f. Add this to Database role memebership as -
   > db_datareader.
   > db_datawriter.
   > db_ddladmin.
as shown below.

I hope the post help you to resolve the issues.

These postings are provided "AS IS" with no warranties and confer no rights. You assume all risk for your use.

Saurav Dhyani


Popular posts from this blog

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this 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.