In this technical guide we'll resolve several issues that can arise when porting a legacy database from version 12 to 14.
Preliminary steps:
- Delete orphaned property records via Settings, Misc
- Delete duplicate activity via Settings, Misc
- Delete online website photo logs via Settings, Misc (re-upload photos)
- Delete empty property / contact records via LE / CE, check for associated activity records
Run the version 14 updater, in the Migrate Data window open Advanced to display the error log.
While the Migrator is running, open Task Manager and right click the process to open the file location so that the Migrator can be restarted later on.
%AppData%\Roaming\Spartner\Temp
When prompted to upgrade to SalesPartner 14 click no. Copy the error log contents to Notepad.
Firstly we'll close the migrator then delete SYSTEM-BAK.DB from C:\spartner\Data. This is a corrupt file that is not required.
Now we'll restart the migrator from the location discovered above. Each error in the log must be resolved so that the migration can proceed.
CONTACT Copy Error:Not exact read/write.
File: C:\spartner\Data\Contact.MB
Table: C:\spartner\Data\Contact.MB
LISTINGS Copy Error:Out of memory
REALENZ_MAIN Copy Error:[FireDAC][Phys][SQLite] ERROR: no such table: REALENZ_MAIN
SYSTEM-BAK Exec Error:[FireDAC][Phys][SQLite] ERROR: near "-": syntax error
SYSTEM-BAK Copy Error:[FireDAC][Phys][SQLite] ERROR: near "-": syntax error
SYSTEM Copy Error:'-227250587.0' is not a valid timestamp
Select Contact.DB and Copy Data
Select Listings.DB and Copy Data
Select RealENZ_Main.DB and Create Table, then Copy Data
SYSTEM-BAK (deleted earlier)
Select System.DB and Copy Data.
Select Listings.DB and Copy Data
Select RealENZ_Main.DB and Create Table, then Copy Data
SYSTEM-BAK (deleted earlier)
Select System.DB and Copy Data.
Finally click Begin and the upgrade sequence will resume. If the migration has run successfully, the SystemFile will be intact upon launching and the database will not be empty. Migrations of this scale are completed in a SalesPartner lab virtual machine (with a system checkpoint in place), then restored from a backup into the production instance.
Addendum
Duplicate data fields
In another lab the version 12 sample contained a couple of duplicate data files that were logged as errors during the migration. The solution is to delete the extra files (example pictured) before running or restarting the migration. You can identify them by the number next to the file name.
Empty advert cost records
For an office with advertising costing and tracking records the following error was encountered during the migration against the AdvertSizeCost.DB table:
Field 'ListOrder' must have a value.
The solution is to close the migrator and open SalesPartner, Settings, Protected Settings, Data Explorer. Then Execute
UPDATE AdvertSizeCost SET ListOrder = 9999 WHERE ListOrder IS NULL
RSS Feed
