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 - 

Error After Restore SQL Backup of NAV 2013 Database

Hi all, we are facing a conman issue during restoring a SQL Database backup restored for NAV 2013. While Trying to run object from Object Designer we get below listed error (even the service is configured properly) - --------------------------- Microsoft Dynamics NAV Development Environment --------------------------- There are no NAV Server instances available for this database. You must ensure that a NAV Server instance is running and is configured to use the database before you perform this activity. --------------------------- OK    ---------------------------

Future - What Next After NAV 2016. Code Name - Madeira...

Hi All, While Browsing web I came across some article which says about next release of Microsoft Dynamics NAV. Let's see the History of Code Names Given to Previous Version  - NAV 2013 - Code Name 'Sicily' NAV 2015 - Code Name 'CRETE' NAV 2016 - Code Name 'CORFU' And as we all know that all these are the Islands.