Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We are moving to azure our develpment structure. On NAV installation, in "specify parameters" step, I'm cleaning the "SQL Server Instance" field and when I click on "Apply" I get the following error: "The SQL Server instance '' exists, but a connection could not be established. Verify that SQL Server is running, that the TCP/IP protocol is enabled and, that a login exists for your Windows account."
I've tested the comunication between NAV machine and SQL machine and its up (installed SQL Management Studio on NAV machine and can load SQL server from SQL machine). The service user is administrator on NAV machine and also confirmed that TCP/IP protocol is active at SQL Configuration Manager.
Tried in NAV 2016 and NAV 2015.
Any idea? Thanks in advance
has the service account the permission "log on as a service"?
check your firewall settings, if the needed ports are added.
check if the nav service account was added to the database as user with sql right db_owner.
I've included the service account in "log on as a service" permission set.
The firewall turnned off for same domain computers and also added the user on SQL with dbo rights.
is there a second nav service instance? if yes, check, if the service name and the ports are different.
That's the first nav service instance on the machine. Also tried to change the ports just in case.
please check the windows event log. maybe there are more details in the error message.
Somehow I'm not receiving the error message in the event viewer (Windows Logs/Application). Got quite confused now. Is it because it comes from a setup process?
means that error message comes directly from nav setup.
best you run nav setup with demo profile and change the settings after successfully run with nav service management tool.
Well, I did some changes... It works but I need to be honest I don't know why.
Enabled "Named Pipes" on SQL Configuration Network. Instead of Custom Installation I did Developer. Have removed some features like "Install Demo Database" and some excel and outlook plugins.
Thanks a lot for your time Jonathan :)
the main changes, i think, were using a predefined setup mode instead of the custom, as i suggested, and enabling the "named pipes" protocol.
quote: "For Microsoft Dynamics NAV to work correctly, the Named Pipes and TCP/IP protocols must be enabled for SQL Server."
from msdn article "Troubleshooting: SQL Server Connection Problems":
I think you get this error because you have SQL server installed locally, while you're actually trying to connect to another SQL server.
You need to run the SQL server component install on that machine, not the one where you install your other NAV software.
If you did not have the SQL server installed locally, you would get a different error saying "SQL Server Instance '' could not be found"
Business Applications communities