Will Sage 300 2016, allow upgrade from ?

Posted By fbifido over 8 years ago

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

0 Jay Converse Acumen over 8 years ago

1. No.
2. No.
3. You only need to Dbdump from other databases if they're not SQL. If you're on SQL, just upgrade
4. Contact your Sage Business Partner
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jay Converse Acumen over 8 years ago in reply to Jay Converse Acumen

FYI, database dump/load DOES work for other versions, it doesn't care about the versions at all.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fbifido over 8 years ago in reply to Jay Converse Acumen

Ok, sorry my BAD, my accpac 5.5A is on PSQL
the dump & load works ok, but Sage 300 ERP 2014, say that it can't use the data, because I move the data from Sage Accpac 5.5A to Sage 300 ERP 2014, and that I need to move the data to Accpac 5.6 first, which makes no sense to me, because Sage ERP 300 2014 is newer, so it should be able to convert the data been loaded to the MS-SQL database into the proper format.

Right now I am look for the a copy of AccPac 5.6 to install and Load the data into it, then dump the data again and the loaded into Sage 300 ERP 2014.

I hope that will fix this problem.

Thanks.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jay Converse Acumen over 8 years ago in reply to fbifido

1. Dbdump the 5.5 Pervasive data
2. Dbload to 5.5 SQL
3. Upgrade to 5.6
4. Detach/copy/attach the SQL database, and upgrade to 2014
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fbifido over 8 years ago in reply to Jay Converse Acumen

Thanks Jay, That's a lot cleaner than what I had plan.
now all I need is a copy of the 5.6 install iso?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jay Converse Acumen over 8 years ago in reply to fbifido

Yup.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 MusickInt over 8 years ago in reply to fbifido

Here is the Sage Accpac 5.6 install and Product Update 3
www.dropbox.com/.../AAACp-TeCzrLNMoZAtLXtFcaa
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fbifido over 8 years ago in reply to MusickInt

Thanks.

What I am getting from you-all comments is that you upgrade, your current installation of accpac, normally what the accpac agent does is:

1) Backup our current install of accpac.
2) Install the new accpac on a new server.
3) Convert all our data to the new accpac server.
4) Re-install all the workstation/client software and point it to the new accpac server.

This has been done about 3 times now.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ettienne Schwagele over 8 years ago in reply to fbifido

If you say it has been done 3 times - are there problems?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fbifido over 8 years ago in reply to Ettienne Schwagele

No, I just notices that every one was talking about upgrade in the sense of "a single install that keeps getting updated"
that's all.

Thanks, I just downloaded the 5.6, and did an image of my current running 5.5.

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) DBdump in 5.6 MS-SQL to USB
6) DBload from USB to 6.2 MS-SQL
7) Test that 6.2 sees the data, and not complain.
8) Done.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 fbifido over 8 years ago in reply to Ettienne Schwagele

No, I just notices that every one was talking about upgrade in the sense of "a single install that keeps getting updated"
that's all.

Thanks, I just downloaded the 5.6, and did an image of my current running 5.5.

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) DBdump in 5.6 MS-SQL to USB
6) DBload from USB to 6.2 MS-SQL
7) Test that 6.2 sees the data, and not complain.
8) Done.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 fbifido over 8 years ago in reply to fbifido

Current setup for this task:

VM01-Accpac1 (windows server 2003, Accpac 5.5, PSQL)
VM02-Accpac2 (windows server 2012R2, accpac 6.2, IIS)
VM03-SQL1 (windows server 2012R2, ms-sql server 2016tp2.2)
VM04-AD (Windows server 2012R2, AD/DNS/DHCP)
Thanks.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jay Converse Acumen over 8 years ago in reply to fbifido

Steps 5 and 6 should have been SQL backup and restore, not Dbdump.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ettienne Schwagele over 8 years ago in reply to fbifido

If your SQL database is on the VM SQL server then no need to dump the 5.6 database and load again before 6.2 upgrade - just point 6.2 to that same database. Unless you really have a need to do an extra dump and load.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fbifido over 8 years ago in reply to Jay Converse Acumen

Thanks. So I don't need Accpac when using MS-SQL to do database backup, dump, etc..
just do everything from the SQL Management Studio, as long as it have to do with the database ?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jay Converse Acumen over 8 years ago in reply to fbifido

Correct
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fbifido over 8 years ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ettienne Schwagele over 8 years ago in reply to fbifido

Bingo
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fbifido over 8 years ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ettienne Schwagele over 8 years ago in reply to fbifido

5.6 lanpaks are not database specific
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fbifido over 8 years ago 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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ettienne Schwagele over 8 years ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jay Converse Acumen over 8 years ago in reply to fbifido

You're not supposed to open them in 5.5 SQL.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fbifido over 8 years ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jay Converse Acumen over 8 years ago in reply to fbifido

q2) when you open them in 5.6
q3) as soon as everything is at 5.6
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ettienne Schwagele over 8 years ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fbifido over 8 years ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jay Converse Acumen over 8 years ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fbifido over 8 years ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jay Converse Acumen over 8 years ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ettienne Schwagele over 8 years ago in reply to fbifido

Read the Sage300ERP_UpgradeGuide.pdf in the \DOCS\62A\ENG folder.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fbifido over 8 years ago 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)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ettienne Schwagele over 8 years ago 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]
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fbifido over 8 years ago 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."
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ettienne Schwagele over 8 years ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fbifido over 8 years ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Sage 300

Will Sage 300 2016, allow upgrade from ?

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING