Skip to main content

Table xxx is Locked by User XXX.


Hi all,

Sometime client face issues while posting transaction that Table is Locked by a particular User.

Yes, i know that if a user is Performing a huge transaction then it happens and we can identify that from
File - Database - Information - Session Tab. Here we can get the User Name in Blocking User ID Field.

But what if the Blocking user id is BLANK. What can be the reason of the Locking message that client users are getting?



I was amazed while i figured out this error, i went to SQL Server and Opened the task Manager and i was amazed to see the the SQL Server Process is using majority of CPU Resoruces.

Then i went to File Database Information tab, and it showed to me that database was untilized to 99%. I went to Alter database option and that was the place i understood the reason for the error.

The Transaction Log File Unrestricted grow Property was set to False, and the LOG was full.


Resolution Steps -
1) Disconnect all users from the database.
2) Increase initial size of Log File From SQL Server as shown in screen below.
3) From classic client alter database set Unrestricted grow property to Yes.
4) Restart the SQL Server.



Thanks & Regards,
Saurav Dhyani

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.