Please Check your Management Port in Microsoft Dynamics NAV 2013 R2


As you know, since Microsoft Dynamics NAV 2013 R2, schema changes are now handled in a different way as described, among other places, in the Paradigm blog post. All schema changes are now synchronized to the SQL Server database through the Microsoft Dynamics NAV service tier.

We sometimes hear of partners receiving the following error when they try to import a .fob file:

“The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.”

This can cause huge problems, especially if it is a newly upgraded database, and you need to Import the fobs from the older version, or if you want to import in a live environment some objects that you just developed in your test environment.

There are several reasons why you can get the ServiceChannel error, one of which was fixed in build 36310 (TFS#358256 Channel errors when trying to default to SPN). So if you are still using an older build number, please be sure you are on a higher build number.

But still, it happens quite often, that even on higher build numbers, you still get the error. In this case you should do the following:.

  1. Verify that you are selecting the correct Microsoft Dynamics NAV Server instance in the development environment by choosing File, Database, Information, and then verifying the value of Server Instance.
  2. Verify that the firewall is opened for the Server Port (usually 7046) and the Management Port (usually 7045) on the corresponding box where the service is running.

It sounds too easy, and in most of the cases the people do not believe us! But after a while they come back to say…yes It was really the management port.

So whenever you want to import any objects into Microsoft Dynamics NAV 2013 R2, if you get any related errors, please check the management port and the firewall settings.

Comments (1)

  1. Jaap says:

    Ok, opening the management port solves it for single tenant databases.

    But for multitenant database I get now the error:

    Tenant 'xxx' could not be found.

    Check that:

    1. Tenant 'xxx' is mounted on the server, or

    2. Specify a different Tenant in Tools|Options.

    Any idea?

Skip to main content