Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now

0

Power BI error message: The commit failed for this transaction.

I see the following message:

 

The commit failed for this transaction. Error returned: 'The database file is locked. SQLite Error Code=5. an error occurred while attempting to update a row in a system table 'Culture' in the metadata database.'.

 

details:

 

Feedback Type:
Frown (Error)

Timestamp:
2022-05-17T10:37:43.8317210Z

Local Time:
2022-05-17T12:37:43.8317210+02:00

Session ID:
0933fc48-ed88-46a2-b8d4-2291ac923344

Release:
April 2022

Product Version:
2.104.941.0 (22.04) (x64)

Stack Trace:
Microsoft.AnalysisServices.OperationException
at Microsoft.AnalysisServices.Tabular.Server.CommitTransactionPrivate()
at Microsoft.AnalysisServices.Tabular.Server.CommitTransaction(ModelOperationResult& modelResult)
at Microsoft.PowerBI.Modeler.ModelManager.<>c__DisplayClass93_0.<CommitTransaction>b__0()
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<>c__DisplayClass6_0`1.<RunInActivity>b__0()
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.RunInActivity(ModelingActivityKind activity, Action action)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.RunInActivity[T](ModelingActivityKind activity, Func`1 action)
at Microsoft.PowerBI.Modeler.ModelManager.InternalTransaction.Commit(Boolean recalc)
at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.ModelAuthoringTransaction.Commit(RecalcBehavior recalcBehavior)
at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.ExtendedModelChangeScope.ExecuteChange(ModelChange modelChange, Boolean saveChange, RecalcBehavior recalcBehavior, String descriptionToTrace)
at Microsoft.PowerBI.Client.Windows.Commands.ApplicationCommands.LinguisticSchemaCommands.<>c__DisplayClass41_0.<TryApplyLinguisticSchema>b__0(IExtendedModelChangeScope scope)
at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.<>c__DisplayClass9_0.<RunExtendedModelChangeAsync>b__0(IExtendedModelChangeScope scope)
at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.<>c__DisplayClass10_0.<<RunExtendedModelChangeAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.<ContinueWithAsyncOperation>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.DesktopModelingHost.<RunOutOfBandExtendedModelChange>d__29.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Commands.ApplicationCommands.LinguisticSchemaCommands.<TryApplyLinguisticSchema>d__41.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Commands.ApplicationCommands.LinguisticSchemaCommands.<ApplyLinguisticSchemaChange>d__40.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAwaitableAsyncExceptions>d__1.MoveNext()

PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.104.941.0","ModuleName":"Microsoft.PowerBI.Tabular.dll","Component":"Microsoft.AnalysisServices.Tabular.Server","Error":"Microsoft.AnalysisServices.OperationException","MethodDef":"CommitTransactionPrivate - PFE_TM_SQLITE_BUSY,PFE_TM_PERSIST_UPDATE_SYSTABLE_FAILED","ErrorOffset":"178"}

OS Version:
Microsoft Windows NT 10.0.22000.0 (x64 en-US)

CLR Version:
4.7 or later [Release Number = 528449]

Peak Virtual Memory:
55 GB

Private Memory:
1.13 GB

Peak Working Set:
2.29 GB

IE Version:
11.1.22000.0

User ID:
b56e4483-b83a-4597-b539-7b717e6c3f0e

Workbook Package Info:
1* - nl-NL, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: True.

Telemetry Enabled:
True

Model Default Mode:
Import

Model Version:
PowerBI_V3

Enabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_azureMapVisual
PBI_compositeModelsOverAS
PBI_enhancedTooltips
PBI_enableWebView2
PBI_mobileAuthoringFormattingUI
PBI_useModernFormatPane
PBI_sparklines

Disabled Preview Features:
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect
PBI_dataPointLassoSelect
PQ_WebView2Connector
PBI_scorecardVisual
PBI_lineChartError

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

DPI Scale:
100%

Supported Services:
Power BI

Status: Delivered

Here are various scenarios of SQLite error database is locked:

  • When you use a table to write and on which the SELECT operations are previously active.
  • The database gets locked in a situation when you try to DROP or CREATE an index or table while the SELECT statement is still in a pending state. The main reason behind it is the misconception of the users that if the Sqlite3_() returns the SQLITE_DONE value, the SELECT statement is finished. However, there is a different scenario because the SELECT statement is not considered to be completed until Sqlite3_reset() or Sqlite3_finalize() are called.
  • When you try to  SELECT operations on the same table at the same time in an application having multiple threads and SQLite is not allowed for the same.

 

To solve this issue, you can try:

  1. By creating backup having no locks
  2. Rewirte the code
  3. Increase default timeout

 

For more details, see:

  1. How to resolve SQLite Error Code 5 “Database is Locked”? 
  2. SQLite Error Database is Locked- How to Resolve? 
  3. How to Fix SQLite Error Database is Locked – Error Code 5 

 

Best Regards,
Community Support Team _ Yingjie Li

Comments
v-yingjl
Community Support
Status changed to: Delivered

Here are various scenarios of SQLite error database is locked:

  • When you use a table to write and on which the SELECT operations are previously active.
  • The database gets locked in a situation when you try to DROP or CREATE an index or table while the SELECT statement is still in a pending state. The main reason behind it is the misconception of the users that if the Sqlite3_() returns the SQLITE_DONE value, the SELECT statement is finished. However, there is a different scenario because the SELECT statement is not considered to be completed until Sqlite3_reset() or Sqlite3_finalize() are called.
  • When you try to  SELECT operations on the same table at the same time in an application having multiple threads and SQLite is not allowed for the same.

 

To solve this issue, you can try:

  1. By creating backup having no locks
  2. Rewirte the code
  3. Increase default timeout

 

For more details, see:

  1. How to resolve SQLite Error Code 5 “Database is Locked”? 
  2. SQLite Error Database is Locked- How to Resolve? 
  3. How to Fix SQLite Error Database is Locked – Error Code 5 

 

Best Regards,
Community Support Team _ Yingjie Li