2 Servers RTC service Issue

Lamba

I have two servers, one is Database server and the other is Nav App server,i am able to connect to the the db present at the database server
by classic client. But for starting the RTC, i have changed the custom settings.
When i am starting the Microsoft Dynamics nav service at the app server it is showing error as:

---

Services

---

The Microsoft Dynamics NAV Server service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

---

OK

---

Lamba

The service is log on by Network service.

Jatin_Patel

Check Dependent Service for MS Dynamics NAV Service in dependencies Tab of Services Property window.

Do you have any other NAV service on same server?

Lamba

Now i have installed only the Client at the app server, and i have made the requisite changes in the clientusersetting file present at user folder in c drive.
As i try to connect to the server following error message appears:

A server was not found at "net.[url=tcp://DBserver:7046/DynamicsNAV/Service]tcp://DBserver:7046/DynamicsNAV/Service[/url]".
Either the URL is incorrect or the server is currently not available.

But i can ping to the DBserver and as previously as i have installed the classic client and was able to connect to the dbserver.

Jatin_Patel

Check CustomSettings.config file at "C:\Program Files (x86)\Microsoft Dynamics NAV\60\Service" and start NAV Service as user who has DB server rights.

Also check Event Log.

Peter_Wibeck_[MSFT]

So if I understand you correct you have below setup

DBServer: Where you have installer NAV database
AppServer: Where you have installed NAV service tier.
Client: Where you have installed RTC and classic client

You are able to connect with classic client to DBServer. But you are not able to start NAV service tier.
1. Verify that the user running NAV service tier is dbowner in the database and have login rights on DBServer
2. Verify that the user running NAV service tier has "Logon as service" rights
3. Verify that the user running NAV service tier is added as user in classic client
4. Ensure you are connecting to AppServer from RTC. From you previous error message it looks like you are trying to connect to DBServer.

- Look in the event log on AppServer machine for any startup errors from NAV service tier.