SQL server not listed on NAV client

Kisu

I have up running SQL service with navision database on it, but the server itself wont show up on Navision clients server list when I'm trying to open it.
But if I type the server name manually on the servername textfield and browse databases it founds the database and I'm able to connect it.

Anyone had this problem? :-k

When we first put up the service it showed up, but after some patches or server configures the server dissapeared from the list and I'm not sure what does that.

kriki

This has also happened to me. I don't know why it happens, but I don't care. In general I create a shortcut to the finsql.exe with all the parameters to connect to the right DB in it. This is easier if I swap between DB's, I know I will always have the correct one.

Kisu

kriki wrote:

This has also happened to me. I don't know why it happens, but I don't care. In general I create a shortcut to the finsql.exe with all the parameters to connect to the right DB in it. This is easier if I swap between DB's, I know I will always have the correct one.

It seems it happens also if I install another instance of the SQL server on same windows server.

I made the shortcuts too. :?
Atleast the server works as it should be, it just wont show up on the list.

davmac1

I have only had this problem on Windows XP - just had to change SQL Server 2005 to enable tcp/ip.

Persson

davmac1 wrote:

I have only had this problem on Windows XP - just had to change SQL Server 2005 to enable tcp/ip.

I have had this problem on WIN 2000 / NAV 2.6 / SQL2000, WIN XP / NAV 4.03 / SQL2005 and WIN XP / NAV 5.0 / SQL2005.

Don't have any clue about what's causing it. But the application and the database server works what ever you have to type the database server name or you have to choose it from the list.

cCode

I also had that annoying "feature", databases won't list in Nav Client when using SQL Server 2005 (I use named instance) running on Windows 2003 Server.

Solution:
enable Named Pipes for Server

1) start program "SQL Server Conficuration Manager" from Microsoft SQL Server 2005/Conficuration tools/
2) open SQL Server 2005 Network Conficuration
3) open Protocols for (your instance name)
4) select Named Pipes and enable it (right click, select enable)
5) stop database, start database (SQL Server 2005 Services) use refresh to make sure that server has right status, stop or running.

Won't harm if you enable TCP/IP as well. Check also that client protocols are enabled.

This worked for me.

dmccrae

The enumeration of servers on the network has always been an issue due to the API being used for this, within the ODBC driver.

Be aware that from version 5.0 of NAV, only locally installed server instances are listed in the server window, but this does not affect your ability to connect to a remote server.

NavStudent

Thank you for this info. I always wondered the method used and why it didn't display all the servers.


I'm glad this problem has been resolved.