11-18-2016 10:13 AM
Need tips to assist in restoring act 8 database to new install of act 18. Error as attached. Followed all steps to create backup.
11-30-2016 04:02 AM - edited 11-30-2016 04:05 AM
Hi Philtron,
Upgrading from Act! versions 7 & 8 (2005 & 2006 respectively) to a recent version of Act will cause this error. This is due to the versions of Microsoft SQL that are in use.
Act v7 & 8 used SQL 2000. When Microsoft developed SQL 2014, which is used in new installations of v18, they did not include a direct upgrade path for databases from SQL 2000 to SQL 2014. To get around this issue, it is necessary to upgrade the database using a version of SQL that has an upgrade path to SQL 2014. This can be either SQL 2005, 2008, or 2012.
To do this for your database backup, you'll need to follow the steps below:
I apologise for this inconvenience, but this is a limitation of Microsoft SQL.
11-19-2016 05:31 AM
Did you do a restore or restore as?
make sure restore as.
Jon Klubnik| ActTrainer.com
(866)710 4228
ACT! Certified Consultant / ACT! Premier Trainer / ACT! Hosting Provider
11-20-2016 11:06 AM
If you are upgrading from Act 8 to Act 18 please have a look at this KB article
http://kb.act.com/app/answers/detail/a_id/38225/~/how-to-upgrade-to-act!-v18-from-a-previous-version
11-29-2016 12:16 PM
Thanks for your reply. I did restore as. Attached is the error produced. To be clear, the ACT 8/2006 database was on an XP machine, and ACT 18 is on a Windows 10 PC. In the old ACT, I went to backup, and created a new backup file, and then on Windows 10 I attempted restore as and selected the zip file created from the backup.
11-30-2016 04:02 AM - edited 11-30-2016 04:05 AM
Hi Philtron,
Upgrading from Act! versions 7 & 8 (2005 & 2006 respectively) to a recent version of Act will cause this error. This is due to the versions of Microsoft SQL that are in use.
Act v7 & 8 used SQL 2000. When Microsoft developed SQL 2014, which is used in new installations of v18, they did not include a direct upgrade path for databases from SQL 2000 to SQL 2014. To get around this issue, it is necessary to upgrade the database using a version of SQL that has an upgrade path to SQL 2014. This can be either SQL 2005, 2008, or 2012.
To do this for your database backup, you'll need to follow the steps below:
I apologise for this inconvenience, but this is a limitation of Microsoft SQL.
11-30-2016 09:06 AM
Thanks, I will attempt that and update the post.
12-28-2016 01:48 PM
This worked perfectly. Definitely takes a while.