Skip to main content

You are not authorized to sign in. Verify that you are using valid credentials and that you have been setup as a user in Microsoft Dynamics NAV.

Hi all,

while creating a database in NAV 2013 or during upgrade we sometime forget to add our own windows login into the database.

Result of same is that we are unable to access the database anymore.

Till NAV 2009 R2 we used to add the login from the Native Client but with NAV 2013 user creation have also being moved to RTC Client.

So it was a tedious task to repeat activities again :(.

Below listed steps will delete all the existing users from the database but if you don't want to do that and just want to add your login in the database please follow the related post.

If you are using NAV 2013 R2 or Higher Please refer this article.


But today Waldo have posted a blog which will enable us to add the users into NAV 2013 Database where we are not authorized to sign in.

You can read the Blog entry here.

I take this opportunity to thank Mr. Waldo from my side and on behalf of all readers. You really Saved our effort.

UPDATE -

I think the link is not working as suggested by amit das here are the steps that need to be performed for same -

1. Open SQL Server.
2. Click on New Query form Top Left.
3. Copy below listed query and paste it in query window - (use your database name in brackets)

USE [Database Name]  
GO
delete from [dbo].[User] 
delete from [dbo].[Access Control] 
delete from [dbo].[User Property] 
delete from [dbo].[Page Data Personalization] 
delete from [dbo].[User Default Style Sheet] 
delete from [dbo].[User Metadata] 
delete from [dbo].[User Personalization] 

4. Run/Execute the query.

5. Change the Navision service credential to start as Network Service.

6. Follow the resolution steps discussed in post.

7. Once done, start the service and Start the RTC Client.

8. Once opened please create your windows user in the client and then proceed with any other activity.

Regards,
Saurav Dhyani
http://saurav-nav.blogspot.com/

Comments

  1. Thanks Buddy for share this link and also really thanks to Waldo who created this Blog

    ReplyDelete

Post a Comment

Popular posts from this blog

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. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searchi...

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.