We are being forced to down grade back to V10 as V11 when using Sage link with 11.01 does not work due to “Overflow error” . Contract support have had this problem with them for over two weeks and it is impossible to get any sort of date for its resolution from the development team. Our orders have backed up seriously since we upgraded as we can not transfer them. Hence the need to go back to a version that actually works. Any tips on going backwards?
-
Import the latest v10 snapshot you have, hopefully you took one just before upgrading. Import that into V10 and away you go as you were. V10 and V11 can be installed on the same machine and work independent of each other, so just use v11 to finalise the sales you have in there. A refresh website from within v10 once you have downloaded any orders and suspended ordering in v11 should be all you need. -
Thanks for that. Any idea if the records of the good people that have created accounts that that their account information will be retained for when/if they get V11 working with sage link?Originally posted by leehack View PostComment
-
As you will have to import the v10 snapshot back into v11 once you are happy v10 is ok to carry on with, i suspect they will be lost.Comment
-
Is there anyway to workround:
___________________________
FATAL ERRORS
The imported snapshot version (11.0.1.0.0.0.LMFA) is newer than this version of Actinic.
Actinic can only import a site created by version 10.0.4.0.0.0.LDZA or earlier.
____________________________---
So the last 14 days of orders are not lost, and we can attempt to get the orders into sage that failed due to overflow errors in V11.01?Comment
-
You will need to revert to a snapshot taken prior to upgrading to V10, the software cannot import a V11 snapshot into V10 which is what it says you are trying to do.
Did you take a snapshot immediately prior to the upgrade.Comment
-
Yes we have the last V10 snapshot. But it is the 300 plus orders taken on V11.01 that we want to be able the push through with sage link. Is there a way of just exporting from V11 and importing into V10 the orders only. This will obviously lose any site development but that is the least of our concerns now.Comment
-
You can try Import Orders in v10 and browser to the v11 database. This may work.
This would replace all orders in the database so back up well first.Comment
-
Support have strongly advised that I do not attempt to import orders taken in v11 to v10 as it will cause a lot of database problems. So I am waiting on the development team which is currently creating a new of the software build to test. This should provide them with more information as to what is causing this and why.
Thank you all for the suggestions. I guess I just have to patient.Comment
-
The development team came up with a new build that fixed the problem of transferring into sage. This version has not gone through the full QA procedure but has got me out of a hole, so fingers crossed we can stay with v11.01.Comment
-
Rich, I've changed the thread title to "Issue with v11 to Sage transfer" as I think that's a little more informative.
Hope that's ok.
ChrisComment
-
V10 and V11 Link
We are still using Actinic V10, but have updated Sage to Sage 2012, and updated the link to the latest version. We have had an "Overflow" error box come up when exporting from Actinic into Sage, but identified it as related to one order only, and could separately export the orders after it by not selecting the "faulty" one on the second attempt. We then manually entered the faulty order into Sage. We have not been able to find why the isolated order produced an "overflow" message.
I am wondering whether Rich's problem may be because of the Link software which he must have upgraded, rather than to Version 11. I am also wondering whether he could have exported some of the orders, as the Overflow message may not have been referring to all of them.
SarahComment
-
A new Actinic link for Sage is now available with a fix for this issue and can be downloaded from this page .Comment
-
Thank you
I have download the Actinic Link upgrade/fix for the Overflow problem and that is now fine. Thanks.
SarahComment
Comment