Monthly Archives: March 2016

ALWAYS! Restart Service Tier after FOB Import!

Blogging about your own mistakes is always easiest. Reasoning is simple; if I make the mistake, chance is someone else makes it too.

Yesterday we had quite some panic at one of my large customers. After importing a fob file with some (small) changes some reports started to break that were not changed by the release.

Not all the users were suffering from this, only few, and after restarting the client, at first, the issue seems to be resolved.

However after a few hours we had the issue returning at users who had already restarted so we had some panic since it kind of goes against one of NAVs strong principles. Consistency. IF you have issues with NAV it is always relatively easy to reproduce.

Fortunately this was the case after some testing but debugging and restarting the client did not change the issue. It persisted.

What do you do in cases like this? Scream loud and wave your arms? No. Stay calm and look for differences. ;-).

After some thinking I realised that I had not restarted the service tier after importing the FOB. This “should not” be required since the new metadata is picked up automagically. However after restarting the service tier the issue was solved.

Since the issue was with a report, I emailed back and forth with Michael Nielsen who does first line support of the reporting tool we use, ForNAV. He confirmed quickly that importing a fob MAY cause inconsistency in your metadata and it is an issue that is very hard to troubleshoot or even reproduce with NAV.

So I’ve learned my lesson and will from now on always restart the service tier after importing fob files.


Unblock a DLL on Windows Server 2012 and Windows 10

It has been very quiet at my blog for the last two months. The main reason for this is the go-live of a big NAV2016 upgrade I’ve been working on for the last half year or so.

This blog is related to this project. We are using some DLLs for this project. Among them are Anveo and ForNAV.

Sometimes you get a new version of a dll from one of your vendors. In some cases windows might prevent you from using them. You have to unblock it explicitly.

This is the error message you might get:


“Cannot create an instance of the following .NET Framework object”

Reason is that you need to go to the properties of the DLL and manually unblock it.


After this is done you can use the DLL. You need Administrator previledges.