Skip to main content

NAV 2013 R2 - Cumulative update 21 Released.

Hi all,

Please find below the details of  Cumulative Update 21 released for Microsoft Dynamics NAV 2013 R2.

Title - Cumulative Update 21 for Microsoft Dynamics NAV 2013 R2



Build No. - 41768


Release Date - July, 2015


Local Version Included - AU, AT, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, RU, UK

Download Link


Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5



Platform Issues Resolved in the Cumulative Update are -
----------------------------------------------------------------------------------------------------------------
ID
Title
361376
The client crashes with the ArgumentOutOfRangeException exception.
374899
The client crashes when you customize the ribbon with a visible action group.
374815
INCSTR does not work with double byte numeric characters.
374868
Repositioning on a list page generates unnecessary reads.
371919
"Compilation of CodeUnit xxx failed because of an I/O error on the following computer" error message when you try to run a job queue process.
374995
Sorting on FlowFields cannot be done when SmartSQL is set to disabled.
374782
Double underline does not display in Excel when you export an account schedule.
374942
Table relations error in lookup.
371853
"Binding managers cannot change state from Filling to FiPreFilling" error message in an event log.
374832
The VariableName identifier cannot be found.
372105
The client crashes with the System.ArgumentException exception when printing.
375000
MODIFYALL damages the MAXSTRLEN function on a temporary table.
375132
The service crashes constantly with a .net error message.
374929
Locked objects are getting status of uncompiled after import.
----------------------------------------------------------------------------------------------------------------

For information about previous Update Rollup / Cumulative update released for Microsoft Dynamics NAV 2013, NAV 2013 R2 & NAV 2015 please Navigate to Hotfix Label or follow the Link.

All These links required valid Partner Source / Customer Source Login...

Regards,
Saurav Dhyani
saurav-nav.blogspot.com

Comments

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.