Personalized Community is here!
Quickly customize your community to find the content you seek.
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
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Working on a new migration of NAV 2009 R2. So, now we're using a new environment such as Windows Server 2016 and SQL 2017 and NAV 2009 R2. For now NAV client, NAV server and SQL server are all in the same machine(Windows Server 2016) for my troubleshooting.I've installed NAV 2009 R2 but when I go to NAV database open and when I try to open the database it says Server not found inside windows server 2016 but I'm able to get the same in my local machine.Another issue is I'm not able to connect to SQL database when I try to install sql components(but manually handled this by creating extended stored procedure of xp_ndo files of 32 bit and 64 bit separately so this should be a concern I believe.Just my work arounds here:1. I installed SQL 2017 in my local machine and checked NAV 2009 R2 it works fine so issue is not here with SQL compatibility I believe.2. I have highest privilege permission as administrator in windows server 2016, I ran the setup as administrator and UAC is turned off.3. port id, sql and nav exe files, services have been added in windows firewall.4. firewall is anyway turned off for now.6. ping, telnet of the server is working fine7. I'm able to connect to SQL server through SSMS studio.8. Tried both windows and SQL authentication.9. Also verified by giving ip address instead of name in server when I was trying to open database from NAV classic.10. config file of NAV has been verified with Server name, database name, port ids.11. All services are running fine without issues12. tcp/ip port is enabled.13. Verified tcp port 1433, it is listening for SQL server.So, in one word I would say, I have referred all previous blogs related to this issue before creating this question. So, trying to find out my luck here atleast if any geeks can solve my issue.
Are you able to see the server and select database but when you click Ok you are getting that error? or you are not able view the server and database from NAV?
I'm able to view the default server but when I look up for database it says server not found.
Just thought if it could be compatibility issue of windows server 2016 and nav 2009 r2 so tried installing nav 2017 but again same connection error.
SQL server instance exists but a connection could not be established. But to confirm sql server is running, tcp is enabled and my user id exists as windows account.
Please share some screenshots of the error and how you are connecting and also when you connect using SSMS
Looks like there was a compatibility issue of Windows Server 2016 with NAV 2009 R2. I tried the same in Win Server 2012 and it did work as expected.
Business Applications communities