Will Sage 300 2016, allow upgrade from ?

Hi,

1) Will the new Sage 300 2016 allow upgrade from older version ?

eg: Accpac 5.5?

2) What about the Database, will it help to migrate Data from AccPac 5.x, PSQL, to MS-SQL ?

3) The Database Dump & Load Application, does not work for different versions. WHY?

eg: Sage AccPac 5.5 Dump to Sage 300 2014 Load.  Why do I need to goto Sage AccPac 5.6 to move my data to "AccPac 6.2A" ?

4) Where can I get a copy of Sage AccPac 5.6 ISO file ?

Thanks.

Parents Reply Children
  • 0 in reply to fbifido
    1) Restore my image to a new VM.
    2) DBdump in 5.5 PSQL
    3) DBload in 5.5 to MS-SQL
    4) upgrade to 5.6
    5) Shutdown VM01-Accpac1
    6) Database-setup the 6.2 to the 5.6DB on the VM03-SQL1 MS-SQL
    7) Test that 6.2 sees the data, and not complain.
    8) Done.
  • 0 in reply to fbifido
    Done:
    1) Restore my image to a new VM.
    2) DBdump in 5.5 PSQL
    3) DBload in 5.5 to MS-SQL

    PSQL- has 7 database in Sage-Database setup, 2-SYS & 5-Companies(DSYS01/TSYS01,DPSH01/DP1201/DCP001/DFM001,TDC001)

    in step 3, I created new SYS & Company Database((1DSYS0/1TSYS0,1DPSH0/1DP120/1DCP00/1DFM00,1TDC00)
    now Accpac 5.5A has 4-SYS,10-Companies Database.

    just to test how its going. I tried to open/access the 1DCP00 Company, and got an error message, that I have reach my max user for my LanPak, I can still open the PSQL companies. So my LanPak is "Pervasive SQL" only.

    Anyway I will move on to step 4, and hope Sage 300 ERP 2014 30-days trial will have an "Open SQL LanPak"

    BRB.
  • 0 in reply to fbifido
    5.6 lanpaks are not database specific
  • 0 in reply to Ettienne Schwagele
    I have not install 5.6, so the lanpak in my reply was talking about v5.5A.
    -Why was I not able to access the Company database that was using MS-SQL ?
    -I don't see an option to add a MS-SQL LanPak to 5.5A

    4a) Uninstall SM 5.5A
    4b) Run Setup from 5.6A dvd
  • 0 in reply to fbifido
    5.5 uses database specific lanpaks, i.e. you cannot open a MS SQL database with a Pervasive lanpak. You can add a MS SQL lanpak in the license manager.
  • 0 in reply to fbifido
    You're not supposed to open them in 5.5 SQL.
  • 0 in reply to Jay Converse Acumen
    Sorry Jay, I was just curious.
    q2) At what point does accpac convert/upgrade the database to 5.6A.
    q3) I still have my PSQL server up and running, at what point of the migration should I shutdown my PSQL Server, or just leave it alone for now.

    I am now Installing AccPac 5.6A.
  • 0 in reply to fbifido
    q2) when you open them in 5.6
    q3) as soon as everything is at 5.6
  • 0 in reply to fbifido
    It converts when you open the company in 5.6
    Let Pervasive be for now, kill it once you do not need it.
  • 0 in reply to Ettienne Schwagele
    Just finish installed AccPac 5.6A.
    Note:
    4c) You must use the same Company Name as the one being upgrade(very stupid, the software can't see/detect/find this information?!?)

    Anyway, I add the MS-SQL LanPak(in v5.6A)

    I tried to open one of the PSQL-Companies Database, it say I have reach my max concurrent user
    I then tried to open one of the MS-SQL-Companies Database, I got "Incorrect version of Database software"

    in the licenses box, all the 5.6A, say ***Unregistered*** in the License to section.
    but there is a "0"(zero) in current users & PSQL.max users box for both 5.5A & 5.6A items.

    LanPak Users is empty

    Lic Manager/Lic - all the 5.5A have serial number & Activated
    Lic Manager/Lic - all the 5.6A have 000000000 and not activated(30-days trial)
    Lic Manager/Users - only the Lanpak Pervasive has serial number & activated.

    Why did it wipe out my 5.5A users?

    Did I miss something, no, no, no. it was like next, next, next, wait, finish, run.

    I am now going to restart, to see if the users shows up again.
  • 0 in reply to fbifido
    You don't open the Pervasive companies in 5.6, you open the SQL companies!

    And if your users are gone, you didn't copy the Site folder correctly.
  • 0 in reply to Jay Converse Acumen
    Sorry, there was nothing about copy data in the upgrade guide.
    if you are talking about the share data which is \\192.168.0.130\aaa_data\
    all that info is still there:
    \3rdParty
    \Company
    \Custom
    \Data
    \Samdata
    \Sample
    \Site
    \User
    \*.lic files

    Ok. So what did I miss. were must the Site data go?
    Thanks.
  • 0 in reply to fbifido
    Sorry, I'm totally done with this thread, and I won't be replying any further. You clearly don't have the technical skills to be doing this.
  • 0 in reply to Jay Converse Acumen

    e"You clearly don't have the technical skills to be doing this."
    I guest my skills are too limited to "Convert AccPac 5.5 PSQL DataBase to Sage 5.6 MS-SQL Database".

    So 30 years of technical skill, just don't cut it anymore.
    A+, Linux+, Network+, Security+, Network Admin/Arch, CCNA, Citrix, VMWare, Software BetaTesterIntaller(you have to learn to install software you have never use before and report any problems/bugs a normal user will encounter).

    I have learn to install Sage 300 ERP 2014, in just a few hrs.(very easy). getting the web UI up took a lot longer because of few good documentation from sage, but got a very good one from a Sage Representative.

    Note:
    I have never installed ACCPAC before, never used it before. The only reason this made it to my office is because the accounts department keeps complaining to the FC, about the problems they are having with the Sage Rep, they takes long too respond, or after they finish more or the same problems. Before Sage online came about, I ask the sage rep "Is there a web interface for Accpac", this was around our second update/refresh(we don't upgrade we replace the server).The answer is always no, when Sage came out with Sage Online, I ask can't we do that on-prem, answer no or use citrix.

    Now I was ask to look into an alternative solution to these accpac problems, my answer was at first no, because the accounts department was using outdated sage products. After getting a register letter from the partners. Well I don't need to say anymore about this matter.

    JUST LIKE TO THANK YOU, for all your help so far.

    (have a gotowebinar with citrix right now, so later)

  • 0 in reply to fbifido
    Sounds like you need a new Sage consultant.
    Jay and I have a long history with Sage, I have been in Sage 300 consulting for 20+ years - I started out on mainframes.
    A conversion of this nature is not something you stumble through blindly, it can cost you a lot in the end in terms of lost time and data problems. We see this every day in our line of work.
    The web part is a waste of time - don't even go there. I know it exists, but that's about it. New things are coming in the new version Sage 300 2016c, so wait and see. Your best option for remote/web access is Citrix/Terminal Server at this stage.
    Contact me offline if you want to discuss: [email protected]
  • 0 in reply to Ettienne Schwagele
    I have not given up on Accpac, I have told the FC, to wait on Sage 300c 2016. Then and only then I will give my report on other solutions.
    I did a google search to see what others have reported on this, and it seems like a lot of people have had problems moving from 5.5 to 5.6.

    Some useful info:
    www.ebsol.com.au/.../
    "The Sage ERP Accpac Version 5.5 Product Update 4 is required for those who are purchasing additional Lanpaks or switching Lanpaks from one database type to another. I.e. from Pervasive to MS-SQL."

    erp.ittoolbox.com/.../how-to-upgrade-accpac-from-52-to-53-then-to-54-2004658
    "Sometime if you are upgrading from Pervasive.SQL to MS SQL, you would need
    to complete the upgrade process in Pervasive and then migrate to MS SQL."
  • 0 in reply to fbifido
    The upgrade is simple, I have done hundreds of them. Moving from 5.5 to 5.6 is one of the simplest upgrades.
  • 0 in reply to Ettienne Schwagele
    upgrading the software is easy, but it seems as if the Database most of the upgrade problems are coming from.
    and it also seems when moving from another SQL to MS-SQL.
  • 0 in reply to fbifido
    It is simple if you follow the correct steps, the steps are detailed in the upgrade doc.
  • 0 in reply to Ettienne Schwagele

    One quick question:
    1) If I have 3 PC:
    VM-01, Windows Server 2003, Accpac 5.5A PU2, Pervasive 9.   1) upgrade to v5.5 PU4, do all post, then DBdump companydata
    VM-02, Windows Server 2003, Accpac 5.6A PU4, SQL Express 2014 2) fresh install of v5.6A & PU4, with MSSQL LanPak, DBload  companydata, then open Company, will be ask to upgrade Data to v5.6A, select Yes. and that it.
    VM-03, Windows Server 2003, File Service \\vm-03\storage\

    q) Can I user DBdump in VM-01 and save the files to \\vm-03\storage\db55a\, then turn off vm-01.
    Then use DBload on VM-02 and import the data from \\vm-03\storage\db55a\ into the SQL-express database.
             a) update VM-01 to v5.5A PU4, post all Company(post everything, as stated in the upgrade manual page 8 "Before Upgrading to Version 5.6"), step 4,5,7

    then open the database with Accpac 5.6A?

    Will this update the the Database to 5.6A ?

    if yes, will this be ok to try with Accpac 300c ?  Sage 300c or Sage 300 2016 or Accpac 6.3

    Thanks.

  • 0 in reply to Ettienne Schwagele
    The upgrade and conversion is something we do all the time. We would be glad to do the upgrade and conversion. That maybe the easiest solution. Musick International [email protected]
  • 0 in reply to fbifido
    What is Accpac 300c?
    You may run into a problem with SQL 2014 for 2 reasons, one is compatibility and another is db size (10GB max in express).
    You have to post all batches in 5.5, post the bank recs and then print & clear the bank rec posting journals before upgrading to 5.6 - this is where 99% of the upgrade problems come from.
  • 0 in reply to fbifido
    Hello MusickInt and all the community!

    May I ask to share the Accpac 5.6 installation files once more?

    Sage just answered "5.6 programs are no longer available for download. You may want to post this in the sage community forum", so you are my last hope to migrate from Accpac 5.5 to Sage 300 2016 :)