1.
Ensure the Server name is
accurate if it is a new server.
2.
Make sure the date and time is
set accurately.
3.
SQL Server Installation:
i. Database Engine access requirements:
1.
Inbound rule for local port
1433
2.
Inbound
rule for SQL application C:\Program Files\Microsoft
SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\Sqlservr.exe
ii. Analysis Services access requirements:
1.
For a default instance of SQL, create an inbound rule for port 2383. The execute the following
commands:
a.
netsh advfirewall firewall
add rule name="SQL Server Analysis Services (tcp-in) on 54321" dir=in
action=allow protocol=TCP localport=54321 profile=domain
b.
netsh advfirewall firewall
add rule name="SQL Server Analysis Services inbound on TCP 2383"
dir=in action=allow protocol=TCP localport=2383 profile=domain
2.
For a
default instance of SQL, create an inbound rule for port 2382. Verify that you can browse to the instance by trying to
connect to the instance using the syntax <servername>\<instancename>.
iii. Report Server access requirements:
1.
Inbound
rule for local port 80.
b)
Activate .Net 3.5 if the
machine is Server 2012 using Add Roles and Features from Server Manager. Server
2010 has .Net 4.0 installed but SQL searches for 3.5. (Recommended to add the
Application Server Role on the Server)
c)
Once all the prerequisite
checks are complete and all successful, you will be required to select SQL
Server Features to install. The following are the minimum features required for
NAV:
i. Database Engine Services.
ii. Management Tools – Basic
iii. Management Tools – Complete
iv. Analysis Services (Optional)
v. Reporting Services (Optional)
1.
Ensure that Microsoft Outlook
and Excel 2010 or later versions are installed on the server.
2.
Ensure that the Microsoft
Search service is installed and activated.
3.
Ensure that the “SQL Server”, “SQL
Database Agent”, “SQL Server Browser”, “SQL Server Analysis Service” and SQL
Server Reporting Services” services startup type is set to automatic and are
running.
4.
Launch Setup file from
installation media.
5.
Select “Installation Option”
from the Dynamics NAV Setup screen.
a)
Note: Monitor the installation
ensure that SQL Express is not installed if SQL Standard is already installed
and will be the default database application. If SQL Standard is not installed
or recognized, the installation process will install SQL Express Server 2010.
6.
Select “Server” for the
installation option.
7.
Highlight all options top
install and the click on “Apply” to start the installation.
8.
Upon completion of the
installation, log into SQL Management Studio to confirm that the “Demo”
database was successfully created.
1. Launch the setup from installation media.
2. Select “Add or remove components”
3. Under Microsoft Dynamics NAV, select “Client” to install and then
select “Development Environment” and “Microsoft Office Excel Add-in” and then
click next.
4. In the “Specify Parameters” window, type “Demo” in the SQL Database
field, then click “Apply”.
5. Launch Dynamics NAV Administration Tool, select the DynamicsNAV71 instance,
and click on Edit” and update the database server field with the appropriate
name and then click on “Save”.
6. Restart the DynamicsNAV71 service by right clicking on the instance
and click “Restart”.
7. Once complete, launch Dynamics NAV client to determine if the
installation was successful. If the application launches successfully into the
demo company, the installation process is completed.
c)
To rename a server that is running
SQL , you will need to perform the following steps:
vi. For a SQL server with a default instance:
1.
Rename the computer in Computer
Properties.
2.
Execute the following query:
sp_dropserver
<old_name>;
GO
sp_addserver <new_name>, local;
GO
3.
Execute the query to see if the
query was successful:
SELECT @@SERVERNAME AS 'Server Name';
4.
To view the instance name:
select @@servername + '\' + @@servicename
vii. For a server with a named instance:
1.
Rename the computer in Computer
Properties.
2.
Execute the following query:
sp_dropserver <old_name\instancename>;
GO
sp_addserver <new_name\instancename>, local;
GO
3.
Execute the query to see if the
query was successful:
SELECT
@@SERVERNAME AS 'Server Name';