Skip to main content

NAV 2013 & Later - Differences between Binaries in your installation or your database.

Hi all,

Sometime while working on a Upgraded Database to NAV 2013 & Later we face a run time error with pages. One of the issue & its resolution is listed below.

After upgrade from NAV 2009 / NAV 2009 SP1 & NAV 2009 R2 you might have faced an error message as shown below -

Compilation of assembly 'c:\ProgramData\Microsoft\Microsoft Dynamics\NAV\71\Serve\MicorosoftDynamicsNAVServer$..\assembly\Page.dll' failed.
This can be caused by differences between Binaries in your installation or your database. Ensure that all installation components are consistent and up to date.

We try to compile objects and its doesn't throws an error message but during run time the system popups up the above error message. Even the Debugger Doesn't help.

When i tried everything i thought of reading the complete error message and yes that was need to be done. The cause of error was specified in the error message.

Let's see what was it in my case.

Finding After Reading the Error Message -
1. I received this error for Page 6500.
2. Reason - I have two Functions with same name i.e OnAfterGetCurrRecord. (as shown below)

Resolution -

So i just designed the page and removed customized Function OnAfterGetCurrRecord, and the error was removed.

Why there were two in my case?

If you remember in NAV 2009 Versions we don't have the standard OnAfterGetCurrRecord Function in Pages, but with NAV 2013 and onward we get this function back. So i 2009 Due to some requirement we had created the function as customized.

Below are the Page triggers in NAV 2009 and NAV 2013.

There can be other errors like this, what we need to do is read the complete error message for the resolution.

Hope you like the post and will help you if you get stuck with same error.

Stay Tuned.

Saurav Dhyani


Post a Comment

Popular posts from this blog

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 - 

Dynamics 365 Business Central 2021 release wave 2 (BC19) Released.

Hi Readers, As we all were expecting Microsoft have Released Business Central 2021 Release Wave 2 Today a.k.a BC19. In this article we will see what all is announced with the General Availability.  Starting Today Customers & Partners can start using Business Central 19. #msdyn365bc #bc19

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.