Nav 2009 SP1 with SQL Server 2012

NNav
NNav Member Posts: 12
edited 2013-10-17 in NAV Three Tier
Hi
I work with Nav 2009 SP1. The SQL client runs on Windows Server 2012, domain joined. SQL Server 2012 x64 is a separate server in the same domain and IP range, and also runs on Windows Server 2012.

I added the inbound firewall rule on SQL Server to open port 1433.
Then I put xp_ndo_x64.dll into the
C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn folder.
Now I restarted the SQL Server.

On the machine with Nav 2009 SP1 I start the classic client with SQL Server.
Choosing Database/New and opening the Server Name dialog box, the dedicated SQL Server is not listed.

I tested the accessibility of this SQL Server with Excel on a different domain joined machine, where it is possible to choose this SQL Server and all databases.

Why is my SQL Server not accessible with Nav 2009 SP1 ?

Patrick
NavGuy

Comments

  • mmperis8
    mmperis8 Member Posts: 19
    Hi,

    The dialog box to choose the SQL Server name never worked very well, but if you manually type the name of the server and instance and enter a valid username & password when you push accept button NAV will find the server.

    Regards.
  • NNav
    NNav Member Posts: 12
    Hi and thanks for your answer.

    When I add the instance name to the server name, the server still cannot be found.
    But now, by typing in only the server name, the error message appears, that the xp_ndo.dll is not present.

    In fact, I copied both xp_ndo.dll and xp_ndo_x64.dll into
    C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn before starting the classic client with sql server for the first time.

    I need to log in with Windows Authentication.

    What could be the solution here?
    NavGuy
  • mmperis8
    mmperis8 Member Posts: 19
    Hi,

    Normally the error is extended procedure named xp_ndo_enumusersgrup or xp_ndo_enumuserids does not exists. Is it? If this is the problem you have to create the extended procedures manually from the dll. This can be done from SQL management studio inside the folder programmability of the master database. (I type the name of extended procedures by memory. Don't trust, me copy the name from the error)

    Regards

Categories