Hi Guys,
Having this client’s machine decided to loading in a loop,
and showing an error in log as the follows.
I am not too sure what this is supposed to lead to.
Any help would be appreciated.
18/02/2023 15:05
[General Info]
Application: SambaPOS
Version: 5.5.0
Region: en
DB: CE
Machine: FORZA
User: Admin
Date: 18/02/2023
Time: 15:05User Explanation:
Admin said “”
[Exception Info 1]
Top-level Exception
Type: System.Exception
Message: An error occurred executing the following sql:
ALTER TABLE Users DROP Constraint [DF_Users_Terminal_Id]
The error was The foreign key constraint does not exist. [ DF_Users_Terminal_Id ]Source: FluentMigrator.Runner
Stack Trace: at FluentMigrator.Runner.Processors.SqlServer.SqlServerCeProcessor.Process(String sql)
at FluentMigrator.Runner.Processors.SqlServer.SqlServerCeProcessor.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(ICollection1 expressions) at FluentMigrator.Runner.MigrationRunner.ExecuteMigration(IMigration migration, Action2 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.AskMigrate(CommonDbContext context)
at Samba.Persistance.Data.Initializer.InitializeDatabase(DataContext context)
at System.Data.Entity.Internal.InternalContext.<>c__DisplayClass66_01.<CreateInitializationAction>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.<InitializeDatabase>b__58_0(InternalContext c) at System.Data.Entity.Internal.RetryAction1.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.Infrastructure.Data.SqlData.EFWorkspace…ctor(CommonDbContext context)
at Samba.Persistance.Data.WorkspaceFactory.Create()
at Samba.Presentation.Services.Common.DataGeneration.DataCreationService.get_Workspace()
at Samba.Presentation.Services.Common.DataGeneration.DataCreationService.ShouldCreateData()
at Samba.Presentation.Services.Common.DataGeneration.DataCreationService.CreateData()
at Samba.Presentation.Bootstrapper.InitializeShell()Inner Exception 1
Type: System.Data.SqlServerCe.SqlCeException
Message: The foreign key constraint does not exist. [ DF_Users_Terminal_Id ]
Source: SQL Server Compact ADO.NET Data Provider
Stack Trace: at System.Data.SqlServerCe.SqlCeCommand.ProcessResults(Int32 hr)
at System.Data.SqlServerCe.SqlCeCommand.ExecuteCommandText(IntPtr& pCursor, Boolean& isBaseTableCursor)
at System.Data.SqlServerCe.SqlCeCommand.ExecuteCommand(CommandBehavior behavior, String method, ResultSetOptions options)
at System.Data.SqlServerCe.SqlCeCommand.ExecuteNonQuery()
at FluentMigrator.Runner.Processors.SqlServer.SqlServerCeProcessor.Process(String sql)
[Assembly Info]
mscorlib, Version=4.0.0.0
PresentationFramework, Version=4.0.0.0
PresentationCore, Version=4.0.0.0
System, Version=4.0.0.0
WindowsBase, Version=4.0.0.0
Samba.Services, Version=5.5.8206.19287
System.ComponentModel.Composition, Version=4.0.0.0
System.Configuration, Version=4.0.0.0
DevExpress.Xpf.Core.v17.2, Version=17.2.13.0
System.Xaml, Version=4.0.0.0
Microsoft.Practices.Prism.MefExtensions, Version=4.0.0.0
Samba.Presentation.Services, Version=5.5.8206.19290
Samba.Presentation.Common, Version=5.5.8206.19292
System.Drawing, Version=4.0.0.0
Samba.Domain, Version=5.5.8206.19286
Microsoft.Practices.Prism, Version=4.0.0.0
System.Core, Version=4.0.0.0
Samba.Infrastructure, Version=5.5.8206.19282
DevExpress.Data.v17.2, Version=17.2.13.0
Microsoft.Practices.ServiceLocation, Version=1.0.0.0
Samba.Localization, Version=5.3.8206.19283
Samba.Persistance, Version=5.5.8206.19286
FastButton, Version=1.0.0.0
[System Info]
Operating System
-Microsoft Windows 10 Enterprise 2016 LTSB
–CodeSet = 1252
–CSDVersion =
–CurrentTimeZone = 0
–FreePhysicalMemory = 2355288
–OSArchitecture = 64-bit
–OSLanguage = 2057
–ServicePackMajorVersion = 0
–ServicePackMinorVersion = 0
–Version = 10.0.14393Machine
-FORZA
–Manufacturer = RealBom
–Model = FA-J1900
–TotalPhysicalMemory = 4113108992
–UserName = FORZA\Admin
######################### E N D #########################
also to mention, this is a multi terminal setup, the server and terminal B is working fine.
This one is Terminal A, which suddenly started to have such issue.
Turns out it might be a connection string issue?
which is very strange to happen in the middle of service, without anyone touching the settings.
I have modified the sambasettings.txt in C:\ProgramData
and it reconnected fine.
Very strange it looked like it was trying to connect to a compact edition database which is something we haven’t supported since an old version of v4
Do you still have an old ce database running on that machine? Maybe check for that. It could be causing the strange issue. Remove ce sql from that local machine if so.
1 Like