You register NAS services manually. This article explains how it is done.

Note that you should replace the bold text with your own installation specific details.

If you are running your MS Dynamics NAV on a SQL database:

1. Use the command prompt and navigate to the Application Server folder
2. Uninstall the current NAS with the following command:
   NasSQL unistallasservice,appservername="servername-SQL"
3. Re-register the NAS with the following command:
   nassql installasservice, appservername="servername-SQL", servername="sqlServerName", nettype=tcp, database="databaseName", company="companyName", startupparameter=SS
4. Start the service from the Service Manager in Administrative Tools

If you are running your MS Dynamics NAV on a classic database:

1. Use the command prompt and navigate to the Application Server folder
2. Uninstall the current NAS with the following command:
   Nas uninstallasservice,appservername="servername-CLASSIC"
3. Re-register the NAS with the following command:
   nas installasservice, appservername="servername-CLASSIC", servername="ServerName", nettype=tcp, company="companyName", startupparameter=SS
4. Start the service from the Service Manager in Administrative Tools

Multiple NASes

You can have multiple NASes running on the same server. This might be because you have several NAV companies or that you are setting up a load balancing scenario with multiple NASes which connects to a single NAV company.

To set up a second NAS, copy the folder C:\Program Files\Microsoft Business Solutions-Navision\NAS. You only need to keep the following files:

• cronus.flf
• fin.etx
• fin.stx
• nc_tcp.dll
• nc_tcps.dll (if you are using secure tcp/ip)
• ndbcs.dll
• nassql.exe (if you are using a SQL database)
• nas.exe (if you are using a native database)

and the following files will be created automatically once you register the services:

• fin.emt
• fin.smt

and don't forget to place your license file in the folder as well.

Running multiple NASes also requires you to change the following files using Notepad (you will need to choose "show all files" as they lack extensions):

c:\windows\system32\drivers\etc\hosts

for each NAS, add a new line at the end looking like this:
127.0.0.1    service Name
The initial IP address should always be 127.0.0.1 and the service name should correspond to the name of the NAS service. For example if your NAS service in your Services console is named "Navision Application Server myTPNAS" then service name in the HOSTS file should be "myTPNAS". The spacing between the IP address and the service name should be a TAB, not just spaces.

c:\windows\system32\drivers\etc\services

for each NAS, add a new line at the end looking like this:
service name    xxxx/tcp
Service name should be replaced with the same value as described above regarding the HOSTS file. xxxx should be replaced with a "unique" number. We recommend starting with 2600 and then for each additional NAS, just increment the number with 1.

Troubleshooting

Try to connecto to your database using a NAV client. If that fails, make sure the everyone account has read (possible full) access to the databasefile (Native databases only).

Make sure each NAS service runs in the a Windows domain account which also has SUPER access in NAV. Make sure you add a Windows user and not a DB user in NAV.

Further troubleshooting tips regarding NAS can be found in the NAS & MQ Troubleshooter article.