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 -

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




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.

Regards,
Saurav Dhyani

Comments

Post a Comment

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searchi...

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.