Can not end the work period

qawechi · June 22, 2025, 1:33am

My log file:

6/22/2025 4:30 AM
-----------------------------
[General Info]

Application: SambaPOS
Version:     5.7.20
Region:      en
DB:          SQ
Machine:     TWILIGHT
User:        qawec
Date:        6/22/2025
Time:        1:30 AM

User Explanation:

qawec said ""
-----------------------------

[Exception Info 1]

Top-level Exception
Type:        System.Data.Entity.Infrastructure.DbUpdateException
Message:     An error occurred while updating the entries. See the inner exception for details.
Source:      EntityFramework
Stack Trace: at System.Data.Entity.Internal.InternalContext.SaveChanges()
   at System.Data.Entity.Internal.LazyInternalContext.SaveChanges()
   at System.Data.Entity.DbContext.SaveChanges()
   at Samba.Infrastructure.Data.SqlData.EFWorkspace.CommitChanges()
   at Samba.Persistance.Data.CachedDao.CacheSave[T](T entity)
   at Samba.Persistance.Data.Dao.Save[T](T entity)
   at Samba.Services.Implementations.InventoryModule.InventoryService.DoWorkPeriodEnd(WorkPeriod currentWorkPeriod, WorkPeriod previousWorkPeriod)
   at Samba.Services.Implementations.InventoryModule.InventoryWorkperiodProcessor.ProcessWorkPeriodEnd(WorkPeriod currentWorkPeriod, WorkPeriod previousWorkperiod)
   at Samba.Presentation.Services.Implementations.WorkPeriodModule.WorkperiodClient.StopWorkPeriod(String description)

Inner Exception 1
Type:        System.Data.Entity.Core.UpdateException
Message:     An error occurred while updating the entries. See the inner exception for details.
Source:      EntityFramework
Stack Trace: at System.Data.Entity.Core.Mapping.Update.Internal.UpdateTranslator.Update()
   at System.Data.Entity.Core.EntityClient.Internal.EntityAdapter.<>c.<Update>b__21_0(UpdateTranslator ut)
   at System.Data.Entity.Core.EntityClient.Internal.EntityAdapter.Update[T](T noChangesResult, Func`2 updateFunction)
   at System.Data.Entity.Core.EntityClient.Internal.EntityAdapter.Update()
   at System.Data.Entity.Core.Objects.ObjectContext.<SaveChangesToStore>b__153_0()
   at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
   at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesToStore(SaveOptions options, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction)
   at System.Data.Entity.Core.Objects.ObjectContext.<>c__DisplayClass148_0.<SaveChangesInternal>b__0()
   at System.Data.Entity.Infrastructure.DefaultExecutionStrategy.Execute[TResult](Func`1 operation)
   at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesInternal(SaveOptions options, Boolean executeInExistingTransaction)
   at System.Data.Entity.Core.Objects.ObjectContext.SaveChanges(SaveOptions options)
   at System.Data.Entity.Internal.InternalContext.SaveChanges()

Inner Exception 2
Type:        System.ArgumentException
Message:     Parameter value '2.2083333333333333333333333333' is out of range.
Source:      System.Data
Stack Trace: at System.Data.SqlClient.TdsParser.TdsExecuteRPC(SqlCommand cmd, _SqlRPC[] rpcArray, Int32 timeout, Boolean inSchema, SqlNotificationRequest notificationRequest, TdsParserStateObject stateObj, Boolean isCommandProc, Boolean sync, TaskCompletionSource`1 completion, Int32 startRpc, Int32 startParam)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
   at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.<>c.<Reader>b__6_0(DbCommand t, DbCommandInterceptionContext`1 c)
   at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target, Func`3 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)
   at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command, DbCommandInterceptionContext interceptionContext)
   at System.Data.Entity.Internal.InterceptableDbCommand.ExecuteDbDataReader(CommandBehavior behavior)
   at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.Entity.Core.Mapping.Update.Internal.DynamicUpdateCommand.Execute(Dictionary`2 identifierValues, List`1 generatedValues)
   at System.Data.Entity.Core.Mapping.Update.Internal.UpdateTranslator.Update()

-----------------------------

[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.7.20.604
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
Samba.Presentation.Services, Version=5.7.20.604
Samba.Infrastructure, Version=5.7.20.604
Microsoft.Practices.Prism, Version=4.0.0.0
Samba.Domain, Version=5.7.20.604
Microsoft.Practices.Prism.MefExtensions, Version=4.0.0.0
Samba.Presentation.Common, Version=5.7.20.604
System.Drawing, Version=4.0.0.0
System.Core, Version=4.0.0.0
DevExpress.Data.v17.2, Version=17.2.13.0
Microsoft.Practices.ServiceLocation, Version=1.0.0.0
Samba.Localization, Version=5.7.20.604
Samba.Persistance, Version=5.7.20.604
FastButton, Version=1.0.0.0
Samba.Infrastructure.Data, Version=5.7.20.604

-----------------------------

[System Info]

Operating System
-Microsoft Windows 11 Pro
--CodeSet = 1252
--CSDVersion = 
--CurrentTimeZone = 180
--FreePhysicalMemory = 3469116
--OSArchitecture = 64-bit
--OSLanguage = 1033
--ServicePackMajorVersion = 0
--ServicePackMinorVersion = 0
--Version = 10.0.22631

Machine
-TWILIGHT
--Manufacturer = Dell Inc.
--Model = OptiPlex 7460 AIO
--TotalPhysicalMemory = 8383074304
--UserName = twilight\qawec

-----------------------------


######################### E N D #########################

qawechi · June 24, 2025, 10:09pm

that is what ChatGPT say:

Thanks for sharing the full error details — this one is pretty revealing. The root issue appears to stem from this part of the log:

Inner Exception 2 > System.ArgumentException > Message: Parameter value ‘2.2083333333333333333333333333’ is out of range.

That highly precise decimal value is causing trouble because the SQL Server column likely has a precision limit that can’t store such a long number. So, what’s happening is:

A value like 2.208333... (possibly a quantity, ratio, or conversion factor) is being saved to the database.

But the destination column in SQL Server might be defined as something like DECIMAL(10,2) or DECIMAL(5,3), which means it simply can’t fit all those decimal places.

This causes the database update operation to fail when closing the work period, which is what SambaPOS was trying to do at the time (StopWorkPeriod method).

What You Can Do

Check your database schema: Look at the relevant table columns related to inventory or work periods and verify their numeric precision and scale. You may want to increase them if necessary.

Add input validation: Somewhere earlier in the pipeline, it’s a good idea to round values to a suitable number of decimal places before saving.

Audit inventory or calculations: If this happened during end-of-work-period processing, it might involve calculated ratios (like average cost or consumption). You might need to tweak how those are being generated.

If you’d like, I can help you write a SQL script to identify which column might be the culprit. Or we can dig into the table structure of the affected entity in SambaPOS. Let me know how deep you’d like to go!

qawechi · June 24, 2025, 10:17pm

and this is what gemini say:

The error log indicates a System.Data.Entity.Infrastructure.DbUpdateException in SambaPOS version 5.7.20. The root cause, as seen in Inner Exception 2, is a System.ArgumentException with the message: “Parameter value ‘2.2083333333333333333333333333’ is out of range.”

This specific error points to an issue during the WorkPeriodEnd process in SambaPOS, where the system attempts to save changes to the database. The “out of range” error suggests that a numerical value being sent to the database (likely a decimal or float) exceeds the allowed precision or scale for the corresponding column in your SQL Server database.

In simpler terms: SambaPOS is trying to save a number with too many decimal places (e.g., 2.2083333333333333333333333333) into a database field that has a more limited capacity for decimal precision.

Common scenarios where this might occur during WorkPeriodEnd in SambaPOS:

Inventory Calculations: Inventory items, especially those with fractional quantities or highly precise unit costs/prices, might result in calculated values that exceed the database column’s precision. For example, if you’re tracking very small units or have complex recipes that lead to long decimal numbers for ingredient consumption.

Rounding Issues: SambaPOS might be performing calculations that result in numbers with many decimal places, and when it attempts to store these in the database, the database schema doesn’t allow for that level of precision.

Custom Reporting or Automation: If you have any custom rules, reports, or automation commands that perform calculations or update inventory/financial figures at the end of a work period, these could be generating the problematic “out of range” values.

Database Schema Mismatch: While less likely if it was previously working, it’s possible that the precision/scale settings of a specific column in your SambaPOS database were somehow altered, making them too restrictive for the data being saved.

To pinpoint the exact cause and resolve it, you would typically need to:

Identify the specific data field: While the error points to a parameter value, it doesn’t explicitly name the column. It’s likely related to inventory, sales, or financial data that gets summarized or updated during the work period end.

Examine your SambaPOS configuration:

Inventory Items: Check the “Decimal Places” setting for inventory items, particularly for units of measure and costs.

Product Pricing: Review any prices or cost calculations, especially for items sold in fractional quantities.

Account Definitions: If there are any custom accounts involved in work period calculations, check their configurations.

Automation Commands/Rules: Look for any rules that run at “Work Period End” and perform calculations or data updates.

Inspect the SQL Server Database: If you have access to your SQL Server database, you could identify tables that store inventory or work period summary data (e.g., PeriodicConsumptions, AccountTransactions, InventoryTransactions) and check the data type (e.g., DECIMAL(P, S), NUMERIC(P, S), FLOAT) and their precision and scale settings for relevant columns. You might find a column with a DECIMAL(X, Y) where Y (scale, number of digits after the decimal point) is too small.

Given the error occurs during WorkPeriodEnd, focusing on inventory and financial calculations that are finalized at that time is the most logical approach.

qawechi · June 24, 2025, 10:26pm

The error gets away by disabling inventory (I mean, not using inventory deduction section).