I’ve just updated to the latest version of Samba (5.7.26) and when trying to launch it I keep getting these issues. The first time I launch I’ve ensured that the data connection string is correct and updated, and then when I try to restore my backup it just crashes and gives me one of these errors. Then when trying to launch again, I just keep getting the same ones pop up. I’ve completely uninstalled Samba and SQL 2017 and reinstalled them both and it happens everytime. Any help at all?? I don’t have a great understanding of SQL so don’t have a clue what to do.
-----------------------------
[General Info]
Application: SambaPOS
Version: 5.7.26
Region: en
DB: SQ
Machine: TILL1
User: simon
Date: 13/06/2026
Time: 16:23
User Explanation:
simon said “”
[Exception Info 1]
Top-level Exception
Type: System.Exception
Message: An error occured executing the following sql:
EXEC SP_Migration_208_UpdateTickets
The error was Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Operation cancelled by user.
The statement has been terminated.
The statement has been terminated.
Source: FluentMigrator.Runner
Stack Trace: at FluentMigrator.Runner.Processors.SqlServer.SqlServerProcessor.ExecuteNonQuery(String sql)
at FluentMigrator.Runner.Processors.SqlServer.SqlServerProcessor.Process(String sql)
at FluentMigrator.Runner.Processors.SqlServer.SqlServerProcessor.Execute(String template, Object[] args)
at FluentMigrator.Expressions.ExecuteSqlStatementExpression.ExecuteWith(IMigrationProcessor processor)
at FluentMigrator.Runner.MigrationRunner.<>c__DisplayClass1f.b__1c()
at FluentMigrator.Runner.MigrationRunner.AnnounceTime(String message, Action action)
at FluentMigrator.Runner.MigrationRunner.ExecuteExpressions(ICollection`1 expressions)
at FluentMigrator.Runner.MigrationRunner.ExecuteMigration(IMigration migration, Action`2 getExpressions)
at FluentMigrator.Runner.MigrationRunner.ApplyMigrationUp(IMigrationInfo migrationInfo, Boolean useTransaction)
at FluentMigrator.Runner.MigrationRunner.MigrateUp(Boolean useAutomaticTransactionManagement)
at FluentMigrator.Runner.MigrationRunner.MigrateUp()
at FluentMigrator.Runner.Initialization.TaskExecutor.Execute()
at Samba.Persistance.Data.Migrator.DoMigrate(String connectionString)
at Samba.Persistance.Data.Migrator.DoMigrate(CommonDbContext context)
at Samba.Persistance.Data.Initializer.Migrate(CommonDbContext context)
at Samba.Persistance.Data.Initializer.InitializeDatabase(DataContext context)
at System.Data.Entity.Internal.InternalContext.<>c__DisplayClass66_0`1.b__0()
at System.Data.Entity.Internal.InternalContext.PerformInitializationAction(Action action)
at System.Data.Entity.Internal.InternalContext.PerformDatabaseInitialization()
at System.Data.Entity.Internal.LazyInternalContext.<>c.b__58_0(InternalContext c)
at System.Data.Entity.Internal.RetryAction`1.PerformAction(TInput input)
at System.Data.Entity.Internal.LazyInternalContext.InitializeDatabaseAction(Action`1 action)
at System.Data.Entity.Internal.LazyInternalContext.InitializeDatabase()
at System.Data.Entity.Internal.InternalContext.Initialize()
at System.Data.Entity.Internal.InternalContext.ForceOSpaceLoadingForKnownEntityTypes()
at System.Data.Entity.DbContext.System.Data.Entity.Infrastructure.IObjectContextAdapter.get_ObjectContext()
at Samba.Persistance.Data.WorkspaceFactory.CreateReadOnly()
at Samba.Persistance.Data.Dao.Single[T](Expression`1 predictate, Expression`1[] includes)
at Samba.Presentation.Bootstrapper.ConfigureAggregateCatalog()
at Microsoft.Practices.Prism.MefExtensions.MefBootstrapper.Run(Boolean runWithDefaultConfiguration)
at Samba.Presentation.App.RunInReleaseMode()
Inner Exception 1
Type: System.Data.SqlClient.SqlException
Message: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Operation cancelled by user.
The statement has been terminated.
The statement has been terminated.
Source: .Net SqlClient Data Provider
Stack Trace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at FluentMigrator.Runner.Processors.SqlServer.SqlServerProcessor.ExecuteNonQuery(String sql)
Inner Exception 2
Type: System.ComponentModel.Win32Exception
Message: The wait operation timed out
Source:
[Assembly Info]
mscorlib, Version=4.0.0.0
System, Version=4.0.0.0
Samba.Services, Version=5.7.26.421
Samba.Domain, Version=5.7.26.421
Samba.Infrastructure.Data, Version=5.7.26.421
System.ComponentModel.Composition, Version=4.0.0.0
Samba.Presentation.Services, Version=5.7.26.421
System.Core, Version=4.0.0.0
PresentationCore, Version=4.0.0.0
WindowsBase, Version=4.0.0.0
PresentationFramework, Version=4.0.0.0
DevExpress.Xpf.LayoutControl.v17.2, Version=17.2.13.0
System.Xml, Version=4.0.0.0
DevExpress.Xpf.Grid.v17.2, Version=17.2.13.0
DevExpress.Xpf.Grid.v17.2.Core, Version=17.2.13.0
System.Xaml, Version=4.0.0.0
Samba.Infrastructure, Version=5.7.26.421
Microsoft.Practices.Prism, Version=4.0.0.0
System.Runtime.Serialization, Version=4.0.0.0
Microsoft.Practices.Prism.MefExtensions, Version=4.0.0.0
DevExpress.Xpf.Core.v17.2, Version=17.2.13.0
System.Windows.Forms, Version=4.0.0.0
System.Drawing, Version=4.0.0.0
Samba.Persistance, Version=5.7.26.421
Stateless, Version=1.0.0.0
PropertyTools, Version=2012.4.14.1
Samba.Localization, Version=5.7.26.421
ReachFramework, Version=4.0.0.0
EntityFramework, Version=6.0.0.0
FluentValidation, Version=3.4.0.0
NCalc, Version=1.3.8.0
Microsoft.CSharp, Version=4.0.0.0
Omu.ValueInjecter, Version=2.3.0.0
Microsoft.Practices.ServiceLocation, Version=1.0.0.0
DevExpress.Data.v17.2, Version=17.2.13.0
WindowsInput, Version=1.0.4.0
[System Info]
Operating System
-Microsoft Windows 10 Home
–CodeSet = 1252
–CSDVersion =
–CurrentTimeZone = 60
–FreePhysicalMemory = 2574972
–OSArchitecture = 64-bit
–OSLanguage = 1033
–ServicePackMajorVersion = 0
–ServicePackMinorVersion = 0
–Version = 10.0.19045
Machine
-TILL1
–Manufacturer = LENOVO
–Model = F0BY00G2UK
–TotalPhysicalMemory = 8491298816
–UserName = TILL1\simon
next one:
-----------------------------
[General Info]
Application: SambaPOS
Version: 5.7.26
Region: en
DB: SQ
Machine: TILL1
User: simon
Date: 13/06/2026
Time: 16:35
User Explanation:
simon said “”
[Exception Info 1]
Top-level Exception
Type: System.InvalidOperationException
Message: This SqlTransaction has completed; it is no longer usable.
Source: System.Data
Stack Trace: at System.Data.SqlClient.SqlTransaction.ZombieCheck()
at System.Data.SqlClient.SqlTransaction.Rollback()
at FluentMigrator.Runner.Processors.GenericProcessorBase.RollbackTransaction()
at FluentMigrator.Runner.Processors.GenericProcessorBase.Dispose(Boolean isDisposing)
at FluentMigrator.Runner.Processors.ProcessorBase.Dispose()
at FluentMigrator.Runner.Initialization.TaskExecutor.Execute()
at Samba.Persistance.Data.Migrator.DoMigrate(String connectionString)
at Samba.Persistance.Data.Migrator.DoMigrate(CommonDbContext context)
at Samba.Persistance.Data.Initializer.Migrate(CommonDbContext context)
at Samba.Persistance.Data.Initializer.InitializeDatabase(DataContext context)
at System.Data.Entity.Internal.InternalContext.<>c__DisplayClass66_0`1.b__0()
at System.Data.Entity.Internal.InternalContext.PerformInitializationAction(Action action)
at System.Data.Entity.Internal.InternalContext.PerformDatabaseInitialization()
at System.Data.Entity.Internal.LazyInternalContext.<>c.b__58_0(InternalContext c)
at System.Data.Entity.Internal.RetryAction`1.PerformAction(TInput input)
at System.Data.Entity.Internal.LazyInternalContext.InitializeDatabaseAction(Action`1 action)
at System.Data.Entity.Internal.LazyInternalContext.InitializeDatabase()
at System.Data.Entity.Internal.InternalContext.Initialize()
at System.Data.Entity.Internal.InternalContext.ForceOSpaceLoadingForKnownEntityTypes()
at System.Data.Entity.DbContext.System.Data.Entity.Infrastructure.IObjectContextAdapter.get_ObjectContext()
at Samba.Persistance.Data.WorkspaceFactory.CreateReadOnly()
at Samba.Persistance.Data.Dao.Single[T](Expression`1 predictate, Expression`1[] includes)
at Samba.Presentation.Bootstrapper.ConfigureAggregateCatalog()
at Microsoft.Practices.Prism.MefExtensions.MefBootstrapper.Run(Boolean runWithDefaultConfiguration)
at Samba.Presentation.App.RunInReleaseMode()
[Assembly Info]
mscorlib, Version=4.0.0.0
System, Version=4.0.0.0
Samba.Services, Version=5.7.26.421
Samba.Domain, Version=5.7.26.421
Samba.Infrastructure.Data, Version=5.7.26.421
System.ComponentModel.Composition, Version=4.0.0.0
Samba.Presentation.Services, Version=5.7.26.421
System.Core, Version=4.0.0.0
PresentationCore, Version=4.0.0.0
WindowsBase, Version=4.0.0.0
PresentationFramework, Version=4.0.0.0
DevExpress.Xpf.LayoutControl.v17.2, Version=17.2.13.0
System.Xml, Version=4.0.0.0
DevExpress.Xpf.Grid.v17.2, Version=17.2.13.0
DevExpress.Xpf.Grid.v17.2.Core, Version=17.2.13.0
System.Xaml, Version=4.0.0.0
Samba.Infrastructure, Version=5.7.26.421
Microsoft.Practices.Prism, Version=4.0.0.0
System.Runtime.Serialization, Version=4.0.0.0
Microsoft.Practices.Prism.MefExtensions, Version=4.0.0.0
DevExpress.Xpf.Core.v17.2, Version=17.2.13.0
System.Windows.Forms, Version=4.0.0.0
System.Drawing, Version=4.0.0.0
Samba.Persistance, Version=5.7.26.421
Stateless, Version=1.0.0.0
PropertyTools, Version=2012.4.14.1
Samba.Localization, Version=5.7.26.421
ReachFramework, Version=4.0.0.0
EntityFramework, Version=6.0.0.0
FluentValidation, Version=3.4.0.0
NCalc, Version=1.3.8.0
Microsoft.CSharp, Version=4.0.0.0
Omu.ValueInjecter, Version=2.3.0.0
Microsoft.Practices.ServiceLocation, Version=1.0.0.0
DevExpress.Data.v17.2, Version=17.2.13.0
WindowsInput, Version=1.0.4.0
[System Info]
Operating System
-Microsoft Windows 10 Home
–CodeSet = 1252
–CSDVersion =
–CurrentTimeZone = 60
–FreePhysicalMemory = 2197352
–OSArchitecture = 64-bit
–OSLanguage = 1033
–ServicePackMajorVersion = 0
–ServicePackMinorVersion = 0
–Version = 10.0.19045
Machine
-TILL1
–Manufacturer = LENOVO
–Model = F0BY00G2UK
–TotalPhysicalMemory = 8491298816
–UserName = TILL1\simon
@amarshall05
!!! DO NOT MANUALLY ADJUST VERSION NUMBERS !!!
Each version corresponds to database changes that if not applied will leave your database in an inconsistent state and it’s doubtful SambaPOS will even start.
The poster above is correct in identifying the db size as the culprit. The default timeout to run the migrations is too little.
This isn’t something a user can solve. Reach out to [email protected] for guidance.
Thanks for your reply!
I’ll give Samba an email and see what they say. It was working perfectly fine but then after a power cut we got logged out of the licensing and when trying to log back in we kept getting a JSON error which is then what caused it to crash.
Other Samba forums said this was due to us having to update Samba which is what we did, and then it did all this.
Man, don’t go messing around with this - it’ll cause you nothing but problems. Did you reach out to SambaPOS support?
The issue you’re having is because of the size of some of your database tables, when there’s an update that affects all rows of data (e.g. add/drop a column) every row must be read, adjusted, then saved. This takes time (sometimes a lot). The code that does the updating of the database only has a pre-determined about of time to complete the update or else it fails - this keeps the application from just locking up indefinitely.
There are ways to try and make this work but it’s not for the average user which is why I suggested you work with SambaPOS support on this.