Skip to main content

VIEW SERVER STATE permission on SQL Server?

Hi all,

Sometime While trying to Login into a database we face an error message as shown below.

Microsoft Dynamics NAV Classic
You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server.

Contact your system administrator.


Cause of Error -

This error normally occurs due to issues that occur while creating Login ID in SQL Server.

Resoultion -

1) Open SQL Server Managment Studio.
2) Click on New Query.
3) Copy & Paste Query given Below.
4) Replace USERID with the User ID for which the error is coming.
5) Select the Whole Query.
6) Press F5.


USE [master]

Now try to Login, the issue is resolved.

Thanks & Regards,
Saurav Dhyani


  1. That made the trick!!! Thank you

  2. Thank You Saurav! That solve my problem

  3. Hi Saurav,
    thank you, this helped when we needed a fast solution.
    You may solve this issue more general using the traceflag 4616 when starting SQL Server.


    1. Hi Andre,

      Thanks for the update. Your comment will help others who will be visiting this post.

      Thanks Man.



Post a Comment

Popular posts from this blog

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all, As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes. Let's start the process. Remember -  1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only. 2) The Synchronization of users with SQL Server is no more required.