How to use V3 database with V4?

emre · December 22, 2013, 12:15pm

You can easily use V3 database with V4.

If you are using compact sql, duplicating SambaPOS3.sdf file and renaming it as SambaPOS4.sdf should be enough.
If you are using SQL Server you can change database name by using new connection string feature.

If a database migration needed you can run SambaPOS4 setup again to trigger database migration.

kylemclean · December 23, 2013, 12:51pm

Is it possible to migrate from V3.0.28 BETA to V4?

emre · December 23, 2013, 3:57pm

You should upgrade to V3.0.34.

andlcp · December 27, 2013, 8:03pm

Hello, im using SambaPOS2.99C at my restaurant. I tried to upgrade it to 3.0.34 and V4 renaming SambaData2.sdf to SambaPOS4.sdf, and in both attemps i got the same error. This error: http://img20.imageshack.us/img20/6030/mk7h.jpg

Any ideas why im getting this error?

Thank you and congratulations, SambaPOS is an awesome POS.

emre · December 27, 2013, 8:26pm

hello @andlcp. We don’t have migration path from V2 yet.
You can try clean installing V4. Thanks.

marikoglu · March 27, 2014, 2:57pm

ben beceremedım ama nerde yanlıs yaptıgımıda anlayamadım oldum olası bu db ısın benı cıleden cıkartır zaten resımlerını eklıyorum umarım faydası olur

ıkısınıde denıyorum ama malesef acılmıyor

Isaac · March 27, 2014, 5:15pm

Try this:

Data Source=SERVERNAME\SQLEXPRESS; User Id=sa; Password=sambapos.1234; Database=SambaPOS3;

Change SERVERNAME with the name of your PC

or

Data Source=LOCALHOST\SQLEXPRESS; User Id=sa; Password=sambapos.1234; Database=SambaPOS3;

marikoglu · March 27, 2014, 5:56pm

Tankyor for your help . I can tray

marikoglu · March 28, 2014, 8:39am

MALESEF IKISIDE OLMADI . ısaac verdıgı yontemlerıde denedım olmadı

Isaac · March 28, 2014, 10:58am

Try renaming you database to SambaPOS4 in SQL Server Management Studio:

and then Install the latest SambaPOS 4 setup again to start database migration.

then change connection string to:

Data Source=LOCALHOST\SQLEXPRESS; User Id=sa; Password=sambapos.1234;

Make sure you take a backup of your database before doing any of the above.

What version of v3 was you using?

marikoglu · March 29, 2014, 10:42am

sambapos dırek sql ıle calıstırdım database bolumune sambaPOS4 dıye bır db attı onu sıldım v3 hazırlamıs oldugum sambaPOS3 adını sambaPOS4 olarak degıstırdım oda acmadı

sole bır hata verdı

[General Info]

Application: SambaPOS
Version: 4.1.27 BETA
Region: en
DB: SQ
Machine: MARIKOGLUPC
User: marikoglu
Date: 29.03.2014
Time: 10:38

User Explanation:

marikoglu 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.

Value cannot be null.
Parameter name: source

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)\SambaPOS4”)

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)\SambaPOS4”)

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.

Value cannot be null.
Parameter name: source

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)\SambaPOS4”)

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)\SambaPOS4”)

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.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
Samba.Infrastructure, Version=1.0.0.0
FluentValidation, Version=3.4.0.0
Samba.Domain, Version=1.0.0.0
DevExpress.Xpf.Grid.v13.2, Version=13.2.7.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
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
DevExpress.Xpf.Grid.v13.2.Core, Version=13.2.7.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
DevExpress.Xpf.Core.v13.2, Version=13.2.7.0
PropertyTools, Version=2012.4.14.1

[System Info]

Operating System
-Microsoft Windows 7 Ultimate
–CodeSet = 1254
–CSDVersion = Service Pack 1
–CurrentTimeZone = 120
–FreePhysicalMemory = 4426736
–OSArchitecture = 64-bit
–OSLanguage = 1055
–ServicePackMajorVersion = 1
–ServicePackMinorVersion = 0
–Version = 6.1.7601

Machine
-MARIKOGLUPC
–Manufacturer = To be filled by O.E.M.
–Model = To be filled by O.E.M.
–TotalPhysicalMemory = 8485437440
–UserName = marikoglupc\marikoglu

Isaac · March 29, 2014, 11:42am

@marikoglu

What was the last version of v3 you was using?

You might have to install v3.0.34 run the setup so it updates the database, and then run v4 in order to successfully trigger database migration.

If you do the above please remember to rename your database back to SambaPOS3.

If you do not have any success maybe attach a backup of your database here and maybe JohnS or Emre can have a look to see what is going on.

marikoglu · March 29, 2014, 11:57am

the is my db file pleas check

http://www.dosya.tc/server26/2lN3AT/data.rar.html

Isaac · March 29, 2014, 1:12pm

@marikoglu

I installed SambaPOS3 v3.0.34 added a few products and then installed v4 to trigger migration and it did not work.

I would probably suggest you start a fresh v4 configuration. Sorry.

emre · March 29, 2014, 2:04pm

@marikoglu problem Teras Masaları tipinin Entity Name ayarının boş olmasından kaynaklanıyor. Eğer düzeltme imknanın varsa V3 üzerinden düzeltip tekrar atmayı deneyebilirsin. Ya da bir sonraki sürümü bekleyebilirsin.

marikoglu · March 29, 2014, 2:07pm

emre bey cok tesekkur ederım cok sagolun hemen duzeltıyorum