Skip to main content

Critical bug in NAV 2013 R2 - Data loss can occur when you change an object multiple times or compile all objects in a live database that has active users connected.

Dear all,

As discussed in Last post Microsoft NAV 2013 R2 had a Critical Bug of Data Loss when we change an Objects Multiple Times or Compile Objects in Live Database that has active users connected.

Microsoft Have Released A Platform Hotfix for the same, which is now available for download from partner source.

Below are the details of KB Article -

Platform hotfix for Microsoft Dynamics NAV 2013 R2 (Build 36281)

Tag for Major Issue - 
357487 Data loss can occur when you change an object multiple times or compile all objects in a live database that has active users connected.

Download Link - https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?scid=kb;EN-US;2934571

Please note that implementing KB 2934571 will require a database conversion

Regards,
Saurav Dhyani
saurav-nav.blogspot.com

Comments

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 - 

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

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.