Samba POS hangs after clearing data


#1

I cleared data with the script below the following error and got the error below ;

One client cannot open but the second one is working.
[General Info]

Application: SambaPOS
Version: 4.1.82
Region: en
DB: SQ
Machine: SERVER
User: Club16
Date: 12-Dec-18
Time: 1:06 PM

User Explanation:

Club16 said “”

[Exception Info 1]

Top-level Exception
Type: System.InvalidOperationException
Message: Sequence contains more than one matching element
Source: System.Core
Stack Trace: at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable1 source, Func2 predicate)
at Samba.Services.Implementations.SettingsModule.SettingService.GetTerminalByName(String name)
at Samba.Presentation.Common.Services.ApplicationState.SetCurrentTerminal(String terminalName)
at Samba.Presentation.Common.Services.ApplicationState.InitializeSettings()
at Samba.Presentation.Bootstrapper.InitializeShell()
at Microsoft.Practices.Prism.MefExtensions.MefBootstrapper.Run(Boolean runWithDefaultConfiguration)
at Samba.Presentation.App.RunInReleaseMode()


[Assembly Info]

Samba.Services, Version=1.0.0.0
mscorlib, Version=4.0.0.0
System, Version=4.0.0.0
Microsoft.Practices.Prism, Version=4.0.0.0
WindowsBase, Version=4.0.0.0
Samba.Infrastructure, Version=1.0.0.0
Samba.Infrastructure.Data, Version=1.0.0.0
PresentationFramework, Version=4.0.0.0
System.Xaml, Version=4.0.0.0
Samba.Presentation.Services, Version=1.0.0.0
FluentValidation, Version=3.4.0.0
Samba.Domain, Version=1.0.0.0
DevExpress.Xpf.Grid.v14.1, Version=14.1.6.0
DevExpress.Xpf.Grid.v14.1.Core, Version=14.1.6.0
PresentationCore, Version=4.0.0.0
Stateless, Version=1.0.0.0
System.Core, Version=4.0.0.0
System.Drawing, Version=4.0.0.0
DevExpress.Xpf.Core.v14.1, Version=14.1.6.0
EntityFramework, Version=4.4.0.0
System.Windows.Forms, Version=4.0.0.0
System.ComponentModel.Composition, Version=4.0.0.0
Samba.Localization, Version=1.0.0.0
Microsoft.CSharp, Version=4.0.0.0
Microsoft.Practices.ServiceLocation, Version=1.0.0.0
Samba.Persistance, Version=1.0.0.0
Microsoft.Practices.Prism.MefExtensions, Version=4.0.0.0
PropertyTools, Version=2012.4.14.1


[System Info]

Operating System
-Microsoft Windows 7 Professional
–CodeSet = 1252
–CSDVersion = Service Pack 1
–CurrentTimeZone = 180
–FreePhysicalMemory = 2635208
–OSArchitecture = 64-bit
–OSLanguage = 1033
–ServicePackMajorVersion = 1
–ServicePackMinorVersion = 0
–Version = 6.1.7601

Machine
-SERVER
–Manufacturer = LENOVO
–Model = 10AU002AUM
–TotalPhysicalMemory = 4103503872
–UserName = SERVER\Club16


DELETE FROM [TicketEntities]
GO
DELETE FROM [Tickets]
GO
DELETE FROM [AccountTransactionDocuments]
GO
DELETE FROM [AccountTransactions]
GO
DELETE FROM [AccountTransactionValues]
GO
DELETE FROM [Calculations]
GO
DELETE FROM [CostItems]
GO
DELETE FROM [InventoryTransactionDocuments]
GO
DELETE FROM [InventoryTransactions]
GO
DELETE FROM [Orders]
GO
DELETE FROM [PaidItems]
GO
DELETE FROM [PeriodicConsumptionItems]
GO
DELETE FROM [PeriodicConsumptions]
GO
DELETE FROM [ProductTimerValues]
GO
DELETE FROM [Payments]
GO
DELETE FROM [WarehouseConsumptions]
GO
DELETE FROM [WorkPeriods]
GO
DELETE FROM [USERS]
GO
UPDATE [Numerators] SET Number = 0
GO
UPDATE [EntityStateValues] SET EntityStates = ‘[{“S”:“Available”,“SN”:“Status”}]’ Where EntityStates like ‘%Status%’
GO


#2

Go into settimgs and set terminal name. Both may be named the same.


#3

I have set terminal using the working terminal but the terminal giving exception is still hanging. How do I set terminal and it is not even getting to the log in stage?


#4

Terminals can all be assigned the same terminal name without issue so pretty sure that option shouldn’t be the cause.
Perhaps something wrong in the local settings text file relating to the terminal name allocation?..
Id try maybe deleting the settings text file on that machine and try opening. It will clear the connection string so will need reconnecting to the database. Unless you want to open up the settings file and see if maybe terminal name is in their twice possibly?