Skip to main content

Could not connect to the SQL database. (-2147467259 master ). This can be caused by insufficient permissions. Indirect permissions through Windows group memberships may not work as expected when User Account Control (UAC) is turned on.

Hi all,
During Installation of NAV 2009 & Later, sometime we come across an error which says -

Could not connect to the SQL database.  (-2147467259   master      ). This can be caused by insufficient permissions. Indirect permissions through Windows group memberships may not work as expected when User Account Control (UAC) is turned on.

This error can be occured due to multile Reasons, so there are mutiple resoultion for the same.

Resolutions -

1) Did u Run installer as Administrator (If Operating system is Windows 7)?
    If not then try intalling using Run as Administrator.

2) Go to services.msc from RUN and check that SQL Server service is running or not. If not start the service and try intalling again.

3) Your Windows does not have sufficient priviledges on the SQL Server. Set up your account with the sysadm server role. Note, that you cannot rely on indirect permissions through Windows group memberships when Vista User Access Control (UAC) is turned on. Try seraching UAC in Control Panel.

4) A previous installation has left the database files (mdf+ldf) sitting in the \Program Files\Microsoft Dynamics NAV\60\Database\ folder and the SQL Server has been reinstalled. This will result in the installer trying to attach an orphaned database. If this is the case, then you should just delete the files or Rename the Database, run the installation once where you select to remove the database components, and run the installation once again where you select to install the demo database.

These are the comman resolutions in this case i was able to find it. I hope someone might be helpfull and it resolve someones issues.

Thanks & Regards,
Saurav Dhyani


  1. I linked to your good post in my blog

  2. Did notice you are setting up NAV7. Probably not the standard NAVDEMO setup but a other instance. I tried the same with the same error.
    Was able to setup the database from the databasesetup MSI

    1. Yes the screen shot is for NAV 7 but it also comes with other version of Navision Role Tailored Client..

  3. Hi Sourav that you for your post however it does not solve the issue.

    1. Hi for which version the steps dosen't resolved the issue.

      Saurav Dhyani

  4. Hi Saurav

    I was installing Nav2103. i got the same error. i checked whatever u had mentioned points above. But doesn't resolved the issue. Kindly inform if you know to solve this issues



    1. Hi Kavi,

      Are you using Demo installation or the customize installation.

      You can drop me mail on

      Saurav Dhyani


Post a Comment

Popular posts from this blog

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.

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 - 

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.