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

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.