Trying to migrate from v3 to v4 getting errors

hash · April 27, 2015, 10:16pm

I`m trying to migrate fromV3.034 to V4.182
But there are so many problems -

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

Application: SambaPOS
Version:     4.1.82
Region:      en
DB:          SQ
Machine:     HASHWORK
User:        Игорь
Date:        27.04.2015
Time:        22:14

User Explanation:

Игорь 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) Недопустимое имя столбца "EntityTypeId".
Недопустимое имя столбца "EntityTypeId".

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:\SambaPOS3")

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:\SambaPOS3")

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) Недопустимое имя столбца "EntityTypeId".
Недопустимое имя столбца "EntityTypeId".

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:\SambaPOS3")

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:\SambaPOS3")

    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]

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
-Майкрософт Windows 8.1 Корпоративная
--CodeSet = 1251
--CSDVersion = 
--CurrentTimeZone = 180
--FreePhysicalMemory = 4215468
--OSArchitecture = 64-разрядная
--OSLanguage = 1049
--ServicePackMajorVersion = 0
--ServicePackMinorVersion = 0
--Version = 6.3.9600

Machine
-HASHWORK
--Manufacturer = Sony Corporation
--Model = VPCZ21Z9R
--TotalPhysicalMemory = 8501657600
--UserName = hashwork\HASHWORK\Игорь

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

What to do with it and how to migrate?

Jesse · April 27, 2015, 10:20pm

You were on version 3.034, 3.035 is the latest version and the instructions say to upgrade to 3.035 before migrating to v4. When did this error occur? Can you explain what you were doing when it happened?

You might try installing 3.035 and load a backup of your database. Then upgrade to v4.1.82

hash · April 28, 2015, 9:43am

Ok. But previously in tutorial it was 3.034. Nevermind. I I set up 3.035, open work period, close Samba, open Samba V4.1.82, error is the same. One question - is it need to be reinstalled (Samba4) every time? Is it need to be installed to the same folder? Here is the error

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

Application: SambaPOS
Version:     4.1.82
Region:      en
DB:          SQ
Machine:     HASHWORK
User:        Игорь
Date:        28.04.2015
Time:        9:39

User Explanation:

Игорь 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) Недопустимое имя столбца "EntityTypeId".
Недопустимое имя столбца "EntityTypeId".

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:\SambaPOS3")

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:\SambaPOS3")

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) Недопустимое имя столбца "EntityTypeId".
Недопустимое имя столбца "EntityTypeId".

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:\SambaPOS3")

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:\SambaPOS3")

    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]

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
-Майкрософт Windows 8.1 Корпоративная
--CodeSet = 1251
--CSDVersion = 
--CurrentTimeZone = 180
--FreePhysicalMemory = 4572760
--OSArchitecture = 64-разрядная
--OSLanguage = 1049
--ServicePackMajorVersion = 0
--ServicePackMinorVersion = 0
--Version = 6.3.9600

hash · May 2, 2015, 8:40pm

As I can understand, there is no way to migrate?

Jesse · May 2, 2015, 9:04pm

There is, you did something wrong or there is something configured wrong and v4 caught it. It looks like it can’t access your v3 directory. Maybe permission issue?