Dynamics Navision 2013 NAS Setup

Toddy_Boy

In a past life I have setup the NAS for classic client i.e. setting up the service on the server.

In 2013 the services are all wrapped up together i.e. Client, SOAP, OData and NAS Settings.

Whoever setup our Navision has a service for the NAS seperate to the main service which holds settings for Client, SOAP, OData.

Is this normal practice?

postsaurav

Hi @Toddy_Boy ,

Yes that is correct way to setup NAS.
Reason Being -
1. Your NAS Service should not restart as also in classic client and the service account that is used to
run service for NAS should have sufficient permission on database in SQL and NAV.

2. Your Client service might have a client timeout value to close session if not used for a certain period of time. Those settings cannot be used with NAS Service.

The Service which is setup for NAS should not have access to user for accessing NAV Client.

A seprate service for same is always suggested.

postsaurav

Hi @Toddy_Boy ,

Yes that is correct way to setup NAS.
Reason Being -
1. Your NAS Service should not restart as also in classic client and the service account that is used to
run service for NAS should have sufficient permission on database in SQL and NAV.

2. Your Client service might have a client timeout value to close session if not used for a certain period of time. Those settings cannot be used with NAS Service.

The Service which is setup for NAS should not have access to user for accessing NAV Client.

A seprate service for same is always suggested.

DenSter

It is really down to your preference, there is no right or wrong. If you set up service tiers with multiple tasks, then if any of those tasks runs into a fatal error, the entire service tier will go down. So if there is an error that brings client service down, that will also affect the other services. By separating the services into separate service tier instances, they won't affect each other.

It's up to you and how you want to manage the situation. If you don't want to create multiple system users for each service, then that would not be a reason for you to separate them. It is perfectly fine to have everything running in one service tier, as long as you know what could happen.

Toddy_Boy

Thanks that all makes perfect sense.