Timeslips migration fails converting 2015 database to 2019 Firebird Database

SUGGESTED

Migrating from Timeslips 2015 to Timeslips 2019 and installation went well however the database conversion fails. I click on Sage TimeSlips 2019 and the "This Database Must Be Converted" dialogue appears. I choose "Make database available for entire network" and enter the database name, etc. The backup runs fine and the conversion starts, about 1:45 into it the Sage TimeSlips Database Conversion window says "not responding" and eventually I have to close out the window. Always freezes in the same place "Converting Features Table." 

Database freezes

  • 0
    SUGGESTED

    I wouldn't kill it.  I'd let it sit for quite a bit longer. 1:45 is nowhere near long enough. As in maybe 15 minutes and see if it moves past the Features Table.

    "Not responding" is just Windows way of saying (I always hear it as a whiny 2 year old in my head) "Timeslips isn't talking to me...Timeslips? Timeslips? Moooooommmmm, Timeslips isn't talking to me." Well, Timeslips might be busy for a bit and not have much to say to Windows. So Windows can just wait, IMHO.

    Nancy Duhon, Esq.

    Duhon Technology Solutions, LLC

    Master Certified Consultant for Sage Timeslips

    Providing individual Consultations and Third Party Remote Desktop Support - including older/unsupported versions.

    404-325-9779

    [email protected]

  • 0 in reply to Nancy Duhon

    I let it sit for 24 hours. It fails at 1:45.

  • 0 in reply to WORKS2019

    Sounds like there's a problem that needs to be fixed in v2015 before you upgrade. There was an issue in v2015 with the features table that was fixed with a service release. I wonder if you had the service release installed? Do you have the ability to go back to 2015? If so, check what release level you are on in Help > About Timeslips. Run database verification > Look for errors. If it is what I think it is, it's not hard to fix and the cost for me to assist would not be high. Alternatively, you can try contacting Timeslips technical support and ask them about help with converting. 

    Note to others - Always run database verification on your current version before starting the upgrade process. 

  • 0 in reply to Caren2

    There was a problem with the Features tables in the 2015 database. We copied new files and it still failed from the server but actually didn't lock up rather gave an actual error in the log file. After reviewing the log files we ran the conversion from a workstation and it worked. Important to note we ran database verification and it didn't show any errors.