How will install NAV 2009 SP1 classic native mode server?

Franklin

Hi everybody,

I have installed a 2009 SP1 native database but its on local mode. I can´t convert it on server mode and only can access only one machine.

How i should create the database on server mode?

](*,)

ara3n

the native server hasn't not changed from 5.0 so you would do it the same way.
Install the database server and point it the fdb and connect to the database server instead of directly to the fdb.

Franklin

ara3n wrote:

the native server hasn't not changed from 5.0 so you would do it the same way.
Install the database server and point it the fdb and connect to the database server instead of directly to the fdb.

Ok, i do this:

SERVERNAME: FGOMEZ
DATABASE NAME: C:\Users\fgomez\Desktop\Areatrans\Cambio versión\BBDD real\Areatrans 2009.fdb
AUTHENTICATION: Database Server Authentication
USER ID: LINA M
PASSWORD: (blank)

NET TYPE: TCPS

If y accept it then:

themave

try netype tcp

not tcps

TCPS has caused this problem for as long I we have used Navision, which is 10 year now

Franklin

themave wrote:

try netype tcp

not tcps

TCPS has caused this problem for as long I we have used Navision, which is 10 year now

With TCP it does not work.

ara3n

did you install the database server with TCP option?

csntor

Just a thought. Did you try connection with IP address in SERVERNAME instead of the name of the server FGOMEZ. If there is no issue with network, it should see the server with the IP address. If not, ping the IP address to see if it is available to the user. Finally, involve your Network guys to check why the server is not responding.

Franklin

ara3n

How do I have to install the database server with TCP? I don´t understand you.

csntor

It doesn´t run with the IP and i ping the server and it´s available. I think the problem is something of setup or instalation as ara3n says...

It must be some option when creating the database or something because if I open the database in the first time and I selected File / Database / Information, It appears in local mode, not server mode.

DenSter

The native database server options are explained in the document called 'w1w1ism.pdf'. They should be available here: http://www.microsoft.com/downloads/deta ... laylang=en

The document is for the 5.0 version, but that should still apply for 2009.

Franklin

DenSter wrote:

The native database server options are explained in the document called 'w1w1ism.pdf'. They should be available here: http://www.microsoft.com/downloads/deta ... laylang=en

The document is for the 5.0 version, but that should still apply for 2009.

Thx but...

In 5.0 when you install de database server mode, the installation allows you to tell the server name and the Network Type but in NAV 2009 don´t appear these options... i think that is the problem.

DenSter

I haven't used native database server for a very long time, so I wouldn't know what your particular problem is. I just know that whenever I had any problem, I was always able to solve it using that document.

KYDutchie

Hi,

What user account is your service running on?
It cannot be the local system account, it won't accept any connections from clients.

Hope this helps,

Willy

rdebath

Franklin,

It looks like you're trying to use TCPS with database logins. The documentation says:

Navision Database Server and TCPS
We recommend that you use the TCPS secure protocol to communicate between the Navision clients and Navision Database Server. TCPS is a secure version of TCP/IP and uses the Security Support Provider Interface (SSPI) with encryption enabled and Kerberos authentication.
TCPS is the default protocol for Navision Database Server.
TCPS is a strict protocol and will only allow you to log on to Navision Database Server if:
· the computer you are using is a member of the same domain as the server.
· the user account that you are using is a Windows domain account in the same domain as the server and has been assigned some role(s) in the database.
Furthermore, when you are running Navision Database Server as a service on WindowsTM XP and Windows ServerTM 2003, you must run it as the NT Authority\Network Service or the Local System account. This means that you cannot run the server from a command prompt if you are using TCPS
as the network protocol. When you are running Navision Database Server as a service on WindowsTM2000, you can only use the Local System account. To have the highest level of security and benefit from the TCPS protocol, we recommend that you run your Navision Database Server on Windows XP or on Windows Server 2003 and use TCPS as the network protocol.

On an semi-related note I see that it's using and encrypted connection to the database. That will get rid of any real chance of a network error causing some form of database corruption. Some estimates (Hello David ?) say that half of data corruption events for the Native DB come from network problems.

David_Singleton

rdebath wrote:

Franklin,

It looks like you're trying to use TCPS with database logins. The documentation says:

Navision Database Server and TCPS
We recommend that you use the TCPS secure protocol to communicate between the Navision clients and Navision Database Server. TCPS is a secure version of TCP/IP and uses the Security Support Provider Interface (SSPI) with encryption enabled and Kerberos authentication.
TCPS is the default protocol for Navision Database Server.
TCPS is a strict protocol and will only allow you to log on to Navision Database Server if:
· the computer you are using is a member of the same domain as the server.
· the user account that you are using is a Windows domain account in the same domain as the server and has been assigned some role(s) in the database.
Furthermore, when you are running Navision Database Server as a service on WindowsTM XP and Windows ServerTM 2003, you must run it as the NT Authority\Network Service or the Local System account. This means that you cannot run the server from a command prompt if you are using TCPS
as the network protocol. When you are running Navision Database Server as a service on WindowsTM2000, you can only use the Local System account. To have the highest level of security and benefit from the TCPS protocol, we recommend that you run your Navision Database Server on Windows XP or on Windows Server 2003 and use TCPS as the network protocol.

On an semi-related note I see that it's using and encrypted connection to the database. That will get rid of any real chance of a network error causing some form of database corruption. Some estimates (Hello David ?) say that half of data corruption events for the Native DB come from network problems.

yes I think you are right, maybe even a part of the reason for moving to TCPS.

Franklin

Thx everybody.

Finally i have installed the sql mode because i don´t understand anything and the customer was stopped.

:thumbsup: