Skip to main content

NAV 2013 R2 - How to Login in a Database Which have NO Companies?

Hi all,

This post can also be used for NAV 2013 R2 - Creating New Companies in Database From Cmdlets.

With Release of NAV 2013 R2, we can create database from the Developer Environment but there is no option of creating company from Developer Environment.

Due to this we have so many issues as Role Tailored Client will not open until there is a company in the database. One of the issues is discussed below with resolution.




Suppose i received Only Objects from my Client For NAV 2013 R2. I imported same By Creating a New Database From Developer Environment.

I created the service for the same as shown below.



Now i tried to open Role Tailored Client For same, but i cannot get in because there are no companies in Database as shown below.



Let's see how we can create Company for getting access to the Windows (Role Tailored) Client.

Steps -

1. Open Powershell ISE as Administrator. How to Open ISE

2. Run the Below Listed Command to Create A company in the Database.

-----------------------------------------------------------------
#Prepare PowerShell
Set-ExecutionPolicy unrestricted -Force
Import-Module 'C:\Program Files\Microsoft Dynamics NAV\71\Service\NavAdminTool.ps1'

#Create Company with Name Demo Company and Instance DynamicsNAV71
New-NAVCompany -CompanyName "Demo Company" -ServerInstance DynamicsNAV71 -Confirm
-----------------------------------------------------------------

The Above command will create a Company "Demo Company" in the database Mapped to Service Instance DynamicsNAV71.

Change these two Parameter as per your requirement.

Click F5 to Run the Command. It will ask for Confirmation for Creating Company Select Yes.



Once you see completed in Status Bar as shown below that means company is created.



Now lets try to open the Windows Client.



So we can now get access to the Windows Client. Now the First task is to create your user in database with Super Rights.

I hope you find the post usefull.


Regards,
Saurav Dhyani
saurav-nav.blogspot.com

Comments

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.