Languages: DE | ES| IT | NO |UK | SI |


Home Free Trial

System Requirements for BI4Dynamics NAV              Watch Webinar                                                   

Permissions

Specifying appropriate permissions on your servers and databases is the most important part of BI4Dynamics system requirements. Without appropriate permissions you won’t be able to access and transfer data from the source NAV/AX databases to the target data warehouse and OLAP cubes. It is important to differentiate two user accounts that are used to run BI4Dynamics:

  • The user running BI4Dynamics application (the user must be local administrator, logged on your server).
  • The user running SQL Agent Job.

In our documentation you will find our recommendation that you use one single domain user account for BI4Dynamics. And this user account should have all the required privileges.

 

System requirements

 

Check system_requirements


The Diagram Recommended Setup
Permissions

We have a single BI4Dynamics domain user account, which is set to never expire (including password). This account:

  • Is administrator on the windows BI server (in essence he is the user running BI4Dynamics installation).
  • It has permissions on the BI SQL Server.
  • It has the Server role on the BI OLAP Server.
  • Both SSAS and Agent service run under this same user.
  • The user also has read permissions on the NAV/AX database(and master database of SQL server in case of NAV license being uploaded to the Server).

Account & Permissions

  • SQL DB connection to the Microsoft Dynamics NAV server to get the data (privileges to read data).
  • User on MS SQL with Create/Drop database and linked server permissions.
  • User on MS SQL Analysis with permission to deploy new analytical database.
  • User on SQL Agent with permission to access NAV database.
  • Windows account with local administrator privileges.
  • Privileges to read data from NAV SQL instance master database (if the NAV license is uploaded to the server).
Note: All six (6) accounts can be combined into one (1) Windows domain account.
Note: One Windows domain account is preferred.

Windows server

  •  Windows Server 2003, 2008, 2008 R2 or Win XP/Vista/7
  • 2 – 4 Intel® processors or equivalent (at least 2GHz)
  • 4 GB RAM (recommended at least 8 GB RAM)
  • Two (2) Hard Disks with 250 GB
  • UAC should be disabled or the application needs to be installed somewhere else than in Program Files
  • NET Framework 4.0
  • Server has to be connected to the Internet with port 80 opened (if the server is under proxy, the application needs access to our authorization web service)
  • User must be member of local administrator´s group
Note: Hardware configuration should strongly base on the size of Microsoft Dynamics NAV database and number of analytical users.

SQL Server & BI SQL Permission

SQL SERVER

 

BI SQL PERMISSION
  • Microsoft SQL Server 2005, 2008 or 2008 R2 (Standard/Enterprise/Development version):
    Database Engine, Analysis Services, SQL Agent. 
  • All services run under the windows domain user with appropriate permissions.
  • Collation has to match the collation of the NAV database.
  • Separate partitions for: Data, Log, Temp.

 
  • Server Roles: sysadmin or dbcreator
  • Effective Server Permissions: create any database or alter any database or control server

For Linked Server:

  • Server Roles: sysadmin or setupadmin
  • Effective Server Permissions:

Analysis Server

User must have Server Role assigned.

Services LOG ON Accounts

  • SQL Server Analysis Server service and
  • SQL Server Agent service.

Run under BI4Dynamics domain user account.

NAV Database & Permissions

 NAV Database

 NAV Database Permissions
  • NAV license needs to be uploaded either on the server (to the master database of SQL instance) or into the NAV database.
     
  • There has to be at least one entry in Currency and Country tables per Company (only applies to companies you intend to use in BI4Dynamics).
  1. Server Roles: sysadmin
  2. Effective Server Permissions: control server
  3. Database Roles: db_owner or db_datareader
  4. Effective Database Permissions: select or control
Note: If the NAV license is uploaded to the server, than the user also need to have read permission on the master database of SQL Server where NAV database resides.

NAV License

Uploaded to the master database on the SQL server or uploaded to the NAV database.

The Most Frequent Errors 

1.ERROR: Can not find the data source license key on your server.

 

2.ERROR: Can not save the instance!

Possible reasons:

  • The NAV license is not uploaded to the server.
  • The uploaded license is different.
  • The user doesn‘t have access to the database.

 Solution:

  • Check if the correct license is uploaded to the server or database.
  • Check user permissions on the master database.

 

Possible reasons:

  • Don‘t have permissions to the file system.
  • UAC turned on.

Solution:

  • Make sure user has permissions on the file system.
  • Turn off UAC (don‘t forget to restart).
  • Install somewhere else than Program Files.

3.ERROR: Can not connect to your server (as user).

 

4.ERROR: The job failed.

Possible reasons:

  • User doesn‘t have appropriate permissions.
  • Target server not accessible on the network.

Solution:

  • Check the network and user permissions.

 

Possible reasons:

  • Customizations done on the standard tables.

Solution:

  • Update BI4Dynamics stage table/column name.

 5.ERROR: The job failed.

 

 

Possible reasons:

  • The Agent Job service runs under an underprivileged user account (default is Network Service).
  • Check AgentErrorLog.txt in your BI4 instance directory for details.

Solution:

  • Change the user account of the agent job service.
  • Use a proxy setting for job execution.

 

  PDF installation_manual              Watch Webinars