Not able to connect to SQL server from NAV 2009 R2 in Windows server 2016 (Server cannot be found)

Harikiran

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 fine
7. 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 issues
12. 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.

irasoelbaks

I would suggest then to reinstall Nav or try the same in another environment, perhaps in a virtual environment?

I would also like to double check how you are connecting just to be sure. So please post the servername, instancename, username, password (mask it) and authentication type you use for SSMS. Then post the same for classic client so we can compare for you.

irasoelbaks

If Nav and SQL are on the same machine you should have no problems or complexity to connect. Can you access the database from SQL Server Management studio?
How do you open the database? From the classic client? What settings do you use? (SQL Host, SQL Instance, SQL Database and what authentication)

Harikiran

I can access db from SSMS.
I'm accessing database from classic client but same issue with RTC too.
I tried entering SQL server name both with host name and ip address
My SQL instance is default server instance,
tried both with windows and database authentication.

irasoelbaks

I would suggest then to reinstall Nav or try the same in another environment, perhaps in a virtual environment?

I would also like to double check how you are connecting just to be sure. So please post the servername, instancename, username, password (mask it) and authentication type you use for SSMS. Then post the same for classic client so we can compare for you.

Harikiran

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.