Registering nc_tcp.dll for use in NAS - Windows 2012R2

hairam

Hi everyone,
I am having som problems starting a NAS on one of our customer servers.
Navision 2009R2 is installed from the DVD and then updated to the current build by overwriting the files with build 34699.

Setup:
Navision 3.60 database (Native server)
Client version 2009R2 - Build 34699
Windows 2012R2 server.

The service is started with
Server.exe cache=100000, servername=MYSERVER, NETTYPE=TCP, database=D:\Database\FirstDatabaseFile01.fdb
I have added MYSERVER into the hostfile and the services file with Port 2407/TCP.
Native server starts fine.

NAS is started with
nas.exe servername=MYNAS, NETTYPE=TCP ,database=E:\Database\FirstDatabaseFile01.fdb, company="Test Company", startupparameter=JOBQUEUE
I have added MYNAS into the hostfile and the services file with Port 2408/TCP.

It gives me the following error
Application Server for Microsoft Dynamics NAV version 6.00 (Build 32012)
Copyright (c) 1987-2010 Microsoft Corporation
The operating system cannot load the DLL module C:\Program Files (x86)\Microsoft Dynamics NAV\60\Application Server\nc_TCP .DLL.
Check that the DLL module exists, and check that any other DLL modul es that it will use also exist.
The Application Server for Microsoft Dynamics NAV AppServer could not initialize properly.
The server will attempt to initialize every 30 seconds until this is successful.

I find i strange that it still says Build 32012 when the details of the NAS.exe file is build 34699.

I tried registering the dll file nc_tcp with regsvr32.exe but get a error.
The module "nc_tcp.dll" was loaded but the entry-point DllRegisterServer was not found.
Make sure that "nc_tcp.dll" is a valid DLL or OCX file and then try again.

I went though the patches from MS for updates to the NC_TCP.dll file but as far as I can see it has not been updated.

So any ideas?

FDickschat

NAS always reports RTM build no. in the Windows Event Log regardless of the actual build used.

hairam wrote:

nas.exe servername=MYNAS, NETTYPE=TCP ,database=E:\Database\FirstDatabaseFile01.fdb, company="Test Company", startupparameter=JOBQUEUE
I have added MYNAS into the hostfile and the services file with Port 2408/TCP

Too many parameters. This would be enough:
nas.exe servername=MYNAS, NETTYPE=TCP ,company="Test Company", startupparameter=JOBQUEUE
Also no need to add a port to the services file for the NAS. It is not a server, only a client without a GUI.