Exception thrown while opening table

Hello,
Kindly help out to resolve this issue,i discovered that open table can not be open again instead it

The Exception Message is shown below
[Exception Info 1]

Top-level Exception
Type: System.Data.Entity.Core.EntityCommandExecutionException
Message: Calling ‘Read’ when the data reader is closed is not a valid operation.
Source: EntityFramework
Stack Trace: at System.Data.Entity.Core.Common.Internal.Materialization.Shaper1.HandleReaderException(Exception e) at System.Data.Entity.Core.Common.Internal.Materialization.Shaper1.StoreRead()
at System.Data.Entity.Core.Common.Internal.Materialization.Shaper1.RowNestedResultEnumerator.MoveNext() at System.Data.Entity.Core.Common.Internal.Materialization.Shaper1.ObjectQueryNestedEnumerator.TryReadToNextElement()
at System.Data.Entity.Core.Common.Internal.Materialization.Shaper1.ObjectQueryNestedEnumerator.MoveNext() at System.Data.Entity.Internal.LazyEnumerator1.MoveNext()
at System.Collections.Generic.List1..ctor(IEnumerable1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source) at Samba.Persistance.Data.Dao.Query[T](Expression1 predictate, Expression`1[] includes)
at Samba.Persistance.Implementations.InventoryDao.GetTickets(DateRange dateRange)
at Samba.Services.Implementations.InventoryModule.ConsumptionBuilder.BuildPeriodicConsumption() in C:\Users\Vehbi\Documents\Source\Repos\sambapos-v5-pro\Samba.Services\Implementations\InventoryModule\ConsumptionBuilder.cs:line 63
at Samba.Services.Implementations.InventoryModule.InventoryService.DoWorkPeriodEnd(WorkPeriod currentWorkPeriod, WorkPeriod previousWorkPeriod) in C:\Users\Vehbi\Documents\Source\Repos\sambapos-v5-pro\Samba.Services\Implementations\InventoryModule\InventoryService.cs:line 191
at Samba.Services.Implementations.InventoryModule.InventoryWorkperiodProcessor.ProcessWorkPeriodEnd(WorkPeriod currentWorkPeriod, WorkPeriod previousWorkperiod) in C:\Users\Vehbi\Documents\Source\Repos\sambapos-v5-pro\Samba.Services\Implementations\InventoryModule\InventoryWorkperiodProcessor.cs:line 25
at Samba.Presentation.Services.Implementations.WorkPeriodModule.WorkperiodClient.StopWorkPeriod(String description)

Inner Exception 1
Type: System.Data.SqlClient.SqlException
Message: SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0xaaaaaaaa; actual signature: 0xfffffffe). It occurred during a read of page (1:36408) in database ID 5 at offset 0x00000011c70000 in file ‘C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA\SambaPos5.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Source: .Net SqlClient Data Provider
Stack Trace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action1 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.SqlDataReader.TryHasMoreRows(Boolean& moreRows)
at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)
at System.Data.SqlClient.SqlDataReader.Read()
at System.Data.Entity.Core.Common.Internal.Materialization.Shaper`1.StoreRead()


Your database is corrupted. Or your hard drive is going bad. It is not a sambapos issue but there are things you can try. I see this happens most when databases are hosted on laptops or slower older systems or slower hard drives or power goes out a lot and the system isn’t shutdown properly often.

You can do what it suggests and try a full DBB CHECKDB

I did DATABASE Check…but still not correct it.

It may not be fixable. You can try to create a fresh new database in a new system and restore an older backup maybe. One before it got corrupted.