Report Permission Error

Hello All,

I am trying to create simple report in NAV 2009 Classic, when try to save report it gives me following error:

You don’t have permission to create report. Please contact your administrator.

My NAV Server and User configuration is as below:

  1. NAV Server is running under windows domain account.
  2. That user has SUPER permission role.
  3. Report Ojbect ID between 50000 - 50009
  4. My License have - 7,110 Report & Dataport Designer

I am not able to solve this issue. Can anybody help me out.


Hi Asim,

Are you doing this on a local database? Or on a server?

Make sure that your license has been imported correctly.

Hi Erik,

I have NAV Server on one machine and Database is on another machine (SQL Server 2005).

I have imported license file in NAV Classic, I also saved that license to Database using Alter Database option.


Hi Asim,

Welcome to the Dynamics User Group !

Has the user just the SUPER role ?

If so you will need to add the ALL role

Hi Dave,

Thank You.

As per your suggestion I changed the Role to ALL of my domain window user, but while changing this I am getting error like

You dont have permission on Table 0.

After that I change my login and logged in using database user (SA) and changed the Role of db user(sa) to ALL and now I am able to save my first report. [:)]

Thank you very much. Can you please tell me why windows user causing problem.


Hi Asim,

Glad to help [:D]

Note - you should have both SUPER & ALL role or for full permissions SUPER & SUPER (DATA)

Check the SQL permission for your windows login on the SQL database. Also have you run a Synchronize on the Single/All users?

Hi Dave,

I have created domain user account on SQL Server and given db_owner and db_securityadmin permission on Demo Database NAV (6).

I also synchronize all users.

I also have problem regarding Role Tailored Client connection to server using windows domain account , for which I have just posted another query on this forum.

Also done Object Change Listener process.


This is an overkill - normally you don’t need any of the above, especially the second one, as db_owner is the highest possible for given database…