How to Stop Negative Inventory in NAV2013 R2

In earlier versions we have to customize NAV to achieve this but NAV2013R2 brings this feature as standard.

We can set up that outbound posting that brings inventory below zero is blocked. 

This can be set up per item or for all items. 

This setup is in the Inventory Setup, we can put a check mark in Prevent Negative Inventory field

 which specifies if you can post transactions that will bring inventory levels below zero.

The selection that you make in this field indicates the value in the Prevent Negative Inventory 

field on individual item cards. The values will either be Default (Yes) or Default (No), 

which you can change.

I know have setup this for all Items i.e., in Inventory Setup and when I try to post an Item which has

 in sufficient Inventory then I got below error.

Microsoft Dynamics NAV

---------------------------

You have insufficient quantity of Item 1000 on inventory.

---------------------------

OK

---------------------------

How to create a new ServiceTier in NAV2013R2

     1. Create a copy from the service-tier folder. (for example C:\Program Files\Microsoft Dynamics NAV\71\Service)

     2. Change the settings in file Customsettings.config. (database and instance name)

  

     3. Change in query below the values NewServiceTierName into the new name of the service-tier 

        Execute below query With PowerShell (Run As Administrator)

     4. New-Service -Name 'MicrosoftDynamicsNAVServer$NewServiceTierName' -BinaryPathName '"c:\Program Files\Microsoft Dynamics NAV\71\NewServiceTierName\Microsoft.Dynamics.Nav.Server.exe" $NewServiceTierName /config "c:\Program Files\Microsoft Dynamics NAV\71\NewServiceTierName\Microsoft.Dynamics.NAV.Server.exe.config"' -DependsOn 'NetTcpPortSharing' -Description 'Service handling NewServiceTierName' -DisplayName 'Microsoft Dynamics NAV 71 Server [NewServiceTierName]' -StartupType Automatic

     5 Execute with Command Prompt (Run as Administrator) the query: (change also NewServiceTierName)

      sc config MicrosoftDynamicsNavServer$NewServiceTierName depend= NetTcpPortSharing/HTTP

      6  Go to Services.msc and change the service-account from the new created service-tier into ….

      7  Start new service-tier.

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