Skip to main content

Port Sharing in NAV 2013

Hi all,

After installing NAV 2013, the Port 7046 is blocked for NAV 2013 Management services.

Earlier till NAV 2009 R2 we can create services for NAV 2009 and NAV 2009 SP1 on the same port by enabling TCP Port Sharing service.

But when we try same after installing NAV 2013 it gives an error.



Reason -

The service created by NAV 2013 is not configured for Port Sharing. I mean it does not depends on Port Sharing service.

Resolution -

A breif explanation will be configuring the NAV 2013 deafult service and enabling dependency on NetPortSharing service. This will enable the Port sharing for Port 7046.

The command will be -
sc config ServiceName depend =NetTcpPortSharing/HTTP

where the Service Name - can be seen from the services.msc console.

The detailed article for the same can be found at Waldo's Blog.

Thanks Man :).

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

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.