New Error Reporter? Or different type of issue?

V5 Question
1

Ok, not had a crash/error for a while, has the reports changed or is this a different type of error?

Was trying to switch database and got crash and now this is all I get?

-----------------------------
[General Info]

Application: SambaPOS
Version:     5.1.54
Region:      en
DB:          SQ
Machine:     JTR-PC
User:        JTR
Date:        17/11/2015
Time:        20:23

User Explanation:

JTR said ""
-----------------------------

[Exception Info 1]

Top-level Exception
Type:        System.ComponentModel.Composition.CompositionException
Message:     The composition produced a single composition error. The root cause is provided below. Review the CompositionException.Errors property for more detailed information.

1) Invalid column name 'DefaultStates'.
Invalid column name 'DefaultValue'.
Invalid column name 'MaskType'.
Invalid column name 'ValueMappings'.

Resulting in: An error occurred while executing the command definition. See the inner exception for details.

Resulting in: An exception occurred while trying to create an instance of type 'Samba.Modules.TicketModule.TicketModule'.

Resulting in: Cannot activate part 'Samba.Modules.TicketModule.TicketModule'.
Element: Samba.Modules.TicketModule.TicketModule -->  Samba.Modules.TicketModule.TicketModule -->  DirectoryCatalog (Path="C:\Program Files (x86)\SambaPOS5")

Resulting in: Cannot get export 'Samba.Modules.TicketModule.TicketModule (ContractName="Microsoft.Practices.Prism.Modularity.IModule")' from part 'Samba.Modules.TicketModule.TicketModule'.
Element: Samba.Modules.TicketModule.TicketModule (ContractName="Microsoft.Practices.Prism.Modularity.IModule") -->  Samba.Modules.TicketModule.TicketModule -->  DirectoryCatalog (Path="C:\Program Files (x86)\SambaPOS5")

Resulting in: An exception occurred while initializing module 'TicketModule'.

  • The exception message was: The composition produced a single composition error. The root cause is provided below. Review the CompositionException.Errors property for more detailed information.

    1. Invalid column name ā€˜DefaultStatesā€™.
      Invalid column name ā€˜DefaultValueā€™.
      Invalid column name ā€˜MaskTypeā€™.
      Invalid column name ā€˜ValueMappingsā€™.

    Resulting in: An error occurred while executing the command definition. See the inner exception for details.

    Resulting in: An exception occurred while trying to create an instance of type ā€˜Samba.Modules.TicketModule.TicketModuleā€™.

    Resulting in: Cannot activate part ā€˜Samba.Modules.TicketModule.TicketModuleā€™.
    Element: Samba.Modules.TicketModule.TicketModule --> Samba.Modules.TicketModule.TicketModule --> DirectoryCatalog (Path=ā€œC:\Program Files (x86)\SambaPOS5ā€)

    Resulting in: Cannot get export ā€˜Samba.Modules.TicketModule.TicketModule (ContractName=ā€œMicrosoft.Practices.Prism.Modularity.IModuleā€)ā€™ from part ā€˜Samba.Modules.TicketModule.TicketModuleā€™.
    Element: Samba.Modules.TicketModule.TicketModule (ContractName=ā€œMicrosoft.Practices.Prism.Modularity.IModuleā€) --> Samba.Modules.TicketModule.TicketModule --> DirectoryCatalog (Path=ā€œC:\Program Files (x86)\SambaPOS5ā€)

Check the InnerException property of the exception for more information. If the exception occurred
while creating an object in a DI container, you can exception.GetRootException() to help locate the
root cause of the problem.

Resulting in: An exception occurred while calling the 'OnImportsSatisfied' method on type 'Microsoft.Practices.Prism.MefExtensions.Modularity.MefModuleManager'.

Resulting in: Cannot activate part 'Microsoft.Practices.Prism.MefExtensions.Modularity.MefModuleManager'.
Element: Microsoft.Practices.Prism.MefExtensions.Modularity.MefModuleManager -->  Microsoft.Practices.Prism.MefExtensions.Modularity.MefModuleManager -->  AssemblyCatalog (Assembly="Microsoft.Practices.Prism.MefExtensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35")

Resulting in: Cannot get export 'Microsoft.Practices.Prism.MefExtensions.Modularity.MefModuleManager (ContractName="Microsoft.Practices.Prism.Modularity.IModuleManager")' from part 'Microsoft.Practices.Prism.MefExtensions.Modularity.MefModuleManager'.
Element: Microsoft.Practices.Prism.MefExtensions.Modularity.MefModuleManager (ContractName="Microsoft.Practices.Prism.Modularity.IModuleManager") -->  Microsoft.Practices.Prism.MefExtensions.Modularity.MefModuleManager -->  AssemblyCatalog (Assembly="Microsoft.Practices.Prism.MefExtensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35")

Source:      System.ComponentModel.Composition
Stack Trace: at System.ComponentModel.Composition.Hosting.CompositionServices.GetExportedValueFromComposedPart(ImportEngine engine, ComposablePart part, ExportDefinition definition)
   at System.ComponentModel.Composition.Hosting.CatalogExportProvider.GetExportedValue(CatalogPart part, ExportDefinition export, Boolean isSharedPart)
   at System.ComponentModel.Composition.Hosting.CatalogExportProvider.CatalogExport.GetExportedValueCore()
   at System.ComponentModel.Composition.Primitives.Export.get_Value()
   at System.ComponentModel.Composition.ExportServices.GetCastedExportedValue[T](Export export)
   at System.ComponentModel.Composition.Hosting.ExportProvider.GetExportedValueCore[T](String contractName, ImportCardinality cardinality)
   at Microsoft.Practices.Prism.MefExtensions.MefBootstrapper.InitializeModules()
   at Samba.Presentation.Bootstrapper.InitializeModules()
   at Microsoft.Practices.Prism.MefExtensions.MefBootstrapper.Run(Boolean runWithDefaultConfiguration)
   at Samba.Presentation.App.RunInReleaseMode()

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

[Assembly Info]

mscorlib, Version=4.0.0.0
DevExpress.Xpf.LayoutControl.v14.1, Version=14.1.11.0
System.Xml, Version=4.0.0.0
DevExpress.Xpf.Grid.v14.1, Version=14.1.11.0
System, Version=4.0.0.0
DevExpress.Xpf.Grid.v14.1.Core, Version=14.1.11.0
WindowsBase, Version=4.0.0.0
System.Xaml, Version=4.0.0.0
Samba.Domain, Version=1.0.0.0
System.Core, Version=4.0.0.0
PresentationFramework, Version=4.0.0.0
Samba.Infrastructure, Version=1.0.0.0
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
System.ComponentModel.Composition, Version=4.0.0.0
PresentationCore, Version=4.0.0.0
DevExpress.Xpf.Core.v14.1, Version=14.1.11.0
Samba.Services, Version=1.0.0.0
Samba.Presentation.Services, Version=1.0.0.0
System.Windows.Forms, Version=4.0.0.0
System.Drawing, Version=4.0.0.0
Stateless, Version=1.0.0.0
PropertyTools, Version=2012.4.14.1
Samba.Localization, Version=1.0.0.0
ReachFramework, Version=4.0.0.0
Samba.Infrastructure.Data, Version=1.0.0.0
EntityFramework, Version=6.0.0.0
FluentValidation, Version=3.4.0.0
Omu.ValueInjecter, Version=2.3.0.0
Microsoft.Practices.ServiceLocation, Version=1.0.0.0
Microsoft.CSharp, Version=4.0.0.0
Samba.Persistance, Version=1.0.0.0

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

[System Info]

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

Machine
-JTR-PC
--Manufacturer = Gigabyte Technology Co., Ltd.
--Model = To be filled by O.E.M.
--TotalPhysicalMemory = 8551956480
--UserName = JTR-PC\JTR

-----------------------------
2

Got back to the origional database I was on by editing the setting file.
Guessing itā€™s to do with a newer version as donā€™t think I used that database for a couple of versions.

3

How are you switching? It should auto migrate.

4

Looks like a SQL error to me. I have seen those before in SambaPOS, but they had to do with one of my SQL scripts.

It may be that the ā€œupgradeā€ is failing, because the DB you are switching to is missing some structural information. That would be my guess.

1 Like