Vantage 4.0 to 5.20 Experience

Yahoo Archive
1
Todd-

I will take a look at this for our next try at moving to 5.1. One thing
that may also need to be done during PRE-UPGRADE is to TURN OFF any backup
software. I tried to upgrade to 5.1 a few months ago and never got to 5.0
because I believe the system backup [ArcServe] kicked in during the Database
Conversion process for 5.0. I was able to successfully upgrade to 5.1 on a
test basis a few weeks prior, however, I do not believe any of the
conversion was running while ArcServe was.

Just my 2 cents.

Thanks!

Rick Ludwig
Corporate Controller
Metal Spinners, Inc.

-----Original Message-----
From: Todd Caughey [mailto:caugheyt@...]
Sent: Thursday, October 10, 2002 9:18 AM
To: 'Vantage@...'
Subject: [Vantage] Vantage 4.0 to 5.20 Experience

Thought I would share my experience with the 4 to 5.2 conversion. Warning
what follows is long. Also, your site may be really different so use with
caution. But I hope my experience sparks some ideas that can make it go
smoother for other people. Good luck.
-Todd Caughey
Harvey Vogel Mfg. Co.
----------------------------------------------------------------------------
----------------------------


Here is a more or less random list of things I encountered while upgrading
from 4.00 to 5.20 which might get overlooked in the process. Plus some
general observations about things like time required for various phases.
Some of this has been covered on-line and possibly in the documentation but
I thought it would be good to put in one place. Perhaps to make the process
smoother for others. Most of this is just a list of some of the steps I did
in addition to the more detailed steps in the upgrade guide for each
version. There were probably many things I missed and got lucky about. My
apologies if this wraps oddly in e-group email. Also, I'm not sure how well
extrapolating run times from my database size would work since a lot might
depend on number of jobs or orders or transactions at a particular site but
I provide it as a rough guide.

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office"
/>

Background:

Running on IBM Netfinity 5500

- 1 Xeon 550Mhz CPU, 512MB RAM, 2 SCSI drive sets (OS & DB)

- 100Mbps net (for moving backup files to another server)

- Starting DB .d1 file size - 535MB - on Vantage 2 years

- 40 users + 10 Data Collection



Pre-Upgrade:

- Ran upgrade process on a test server and had user group reviews of
changes - #1 biggest advice - TEST SERVER

- This process took 2 months and in real conversion avoided lots of bad
problems

- Closed all groups (batches)

- Ran Cost Capture up to moment (validated all labor entries first since no
edit after)

- Ran WIP report, A/R Aging report and A/P Aging report (to save initial
values)

- Removed all users from system and closed all sessions (ProMon)

- Ran Vantage backup twice (two separate runs - 6 min. each)

- Copied one backup to another server and burned to CD (ours fits on one CD
w/o zipping)

- Backed up the other backup file to tape

- Checked disk space and cleaned out several old backup files and other junk
5GB of 9GB free

- Per Epicor advice stopped all DB's with ProControl, Stopped ProService and
Admin Service

- SET Progress 9.0B services to MANUAL start



4.0 to 5.0 Upgrade:

- Progress 9.1A install hung installing Microsoft Data Access Component
(MDAC) version 2.1

- Retried the install 6 times (and entered #@%^%$& codes each time)

- got some great late night e-group advice from Ted Kitch to install MDAC
2.5

- downloaded MDAC 2.5 from Microsoft and installed, P9.1A then ran fine
to end

- highly recommend installing MDAC 2.5 before you start

- Rest of install went fine

- Restored 4.0 DB to EPIC50 location (using ProRest)

- Setup DB in Progress Explorer

- Per instructions started and stopped DB

Note: when you restart DB immediately after a stop wait a couple minutes
otherwise it might generate an error - wait and try again and it seemed to
work OK

- IDXBUILD took 35 minutes

- Schema Change (crash protection off) took 1 hour

- DB Conversions on first access to Vantage took 1 hour

- Total time (not counting MDAC delay) for 4.0 to 5.0 - 8hrs



5.0 - 5.10 Upgrade:

- Backed up 5.0 DB and copied to other server and burned to CD

- Backup file shrank by 100MB (20%) due to Idxbuild ?

- Stopped DB and services - set 9.1A services to manual start

- Installed Progress 9.1C no problem

- Install 9.1C patch - must reboot - check services status after

- Installed 5.10 and Client (on server) w/o problems

- Turning crash protection off got error with MMC

- per Epicor Support downloaded & ran RegProgDLL.exe from Epicor site
(Progress area)

- Schema change took 25 minutes

- DB conversion on first startup took 55 minutes

- Total time for 5.10 upgrade - 3 hours



5.10 - 5.20 Upgrade:

- Backup 5.10 DB and copy to other server and burn CD

- backup size re-grew a bit to 450MB

- Cleaned out 5.00 DB and backup.1 since not needed anymore - left folders &
software

- Upgrade process went without any issues at all

- Schema Change took 18 minutes

- Conversions took 24 minutes

- Total time for 5.20 upgrade - just under 2 hours



Client Upgrades:

- 5.20 Client install is a LOT slower than 4.0 and requires a reboot

- found that doing 4-5 in a cluster at same time was fastest

- be sure to uninstall 9.0B (or whatever) and re-map drive to Epic52

- Note: on remap some would open folder and others not found that if I
unchecked "reconnect" box and re-checked it then it would force folder open
(faster access to client install)

- on shop floor PCs if DataCollection.vtg is in startup change it to Plant
Floor.vtg



Report Builder:

- had to open and save each report to get it to check for missing fields

- biggest field change was where quantity field is now OurQty (added Our)

- Type (on job) is now JobType so conflicted with calc field in a few
reports

NOTE: had to change on 4.0 then make other changes under 5,.20

- when running reports from within Vantage you might get Convmap.cp not
found

you may need to edit Progress.ini (in Progress\bin) to replace all
references to locations messed up due to mapped drive letter - example
change from v:\epic52\progress to v:\progress

- had to go through every custom report link and re-point to new location
in epic52



Crystal Reports:

- major issue with some (not all) users getting dll\crpe32.dll not found

- ended up copying vangate\dll contents to user's VntgWk52 folder

- installed CR 8.5 (and have lost report distribution wizard at moment -
trying to reinstall)

- opened each report, set location to VntgWK52, verify DB

- a couple report (like ARForm) lost some links



Other things:

- must change vantage backup

- Edit BACKVAN.BAT to use correct DB location (epic52)

- Make sure a copy if VNTGBKUP.BAT exists in Progress\bin folder

- edit reference to progress\bin location (to be epic52) as needed

- check vantage.ini (and again progress.ini) and make sure references to
\epic52\ are really needed if the mapped drive letter already includes it -
take out as necessary - save a copy of the original file before editing

- move your VBP routines from the old vbp folder to epic52\vantage\vbp

- these would be any .p and .r routines called by Vantage Basic forms -
if you have any

- if you have ABOM and Engineering Workbench - check security settings on
new menu options

- expect client startup to be a lot slower and splash screen to go away
really fast leaving users wondering if Vantage is going to start so they try
to start again - consider restricting multiple sessions and modifying the
splash screen image (in Vantage\bitmap).



Dangling Issues:

- Run Cost Capture before first WIP report - otherwise old closed jobs show
up

- Don't hang around in Customer Shipment Tracker - can lock invoicing Get
Shipments process

- ODBC compatibility questions with P9.1D (we don't use ODBC much but might
in future)



[Non-text portions of this message have been removed]



Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
2
Thought I would share my experience with the 4 to 5.2 conversion. Warning
what follows is long. Also, your site may be really different so use with
caution. But I hope my experience sparks some ideas that can make it go
smoother for other people. Good luck.
-Todd Caughey
Harvey Vogel Mfg. Co.
----------------------------------------------------------------------------
----------------------------


Here is a more or less random list of things I encountered while upgrading
from 4.00 to 5.20 which might get overlooked in the process. Plus some
general observations about things like time required for various phases.
Some of this has been covered on-line and possibly in the documentation but
I thought it would be good to put in one place. Perhaps to make the process
smoother for others. Most of this is just a list of some of the steps I did
in addition to the more detailed steps in the upgrade guide for each
version. There were probably many things I missed and got lucky about. My
apologies if this wraps oddly in e-group email. Also, I'm not sure how well
extrapolating run times from my database size would work since a lot might
depend on number of jobs or orders or transactions at a particular site but
I provide it as a rough guide.

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office"
/>

Background:

Running on IBM Netfinity 5500

- 1 Xeon 550Mhz CPU, 512MB RAM, 2 SCSI drive sets (OS & DB)

- 100Mbps net (for moving backup files to another server)

- Starting DB .d1 file size - 535MB - on Vantage 2 years

- 40 users + 10 Data Collection



Pre-Upgrade:

- Ran upgrade process on a test server and had user group reviews of
changes - #1 biggest advice - TEST SERVER

- This process took 2 months and in real conversion avoided lots of bad
problems

- Closed all groups (batches)

- Ran Cost Capture up to moment (validated all labor entries first since no
edit after)

- Ran WIP report, A/R Aging report and A/P Aging report (to save initial
values)

- Removed all users from system and closed all sessions (ProMon)

- Ran Vantage backup twice (two separate runs - 6 min. each)

- Copied one backup to another server and burned to CD (ours fits on one CD
w/o zipping)

- Backed up the other backup file to tape

- Checked disk space and cleaned out several old backup files and other junk
5GB of 9GB free

- Per Epicor advice stopped all DB's with ProControl, Stopped ProService and
Admin Service

- SET Progress 9.0B services to MANUAL start



4.0 to 5.0 Upgrade:

- Progress 9.1A install hung installing Microsoft Data Access Component
(MDAC) version 2.1

- Retried the install 6 times (and entered #@%^%$& codes each time)

- got some great late night e-group advice from Ted Kitch to install MDAC
2.5

- downloaded MDAC 2.5 from Microsoft and installed, P9.1A then ran fine
to end

- highly recommend installing MDAC 2.5 before you start

- Rest of install went fine

- Restored 4.0 DB to EPIC50 location (using ProRest)

- Setup DB in Progress Explorer

- Per instructions started and stopped DB

Note: when you restart DB immediately after a stop wait a couple minutes
otherwise it might generate an error - wait and try again and it seemed to
work OK

- IDXBUILD took 35 minutes

- Schema Change (crash protection off) took 1 hour

- DB Conversions on first access to Vantage took 1 hour

- Total time (not counting MDAC delay) for 4.0 to 5.0 - 8hrs



5.0 - 5.10 Upgrade:

- Backed up 5.0 DB and copied to other server and burned to CD

- Backup file shrank by 100MB (20%) due to Idxbuild ?

- Stopped DB and services - set 9.1A services to manual start

- Installed Progress 9.1C no problem

- Install 9.1C patch - must reboot - check services status after

- Installed 5.10 and Client (on server) w/o problems

- Turning crash protection off got error with MMC

- per Epicor Support downloaded & ran RegProgDLL.exe from Epicor site
(Progress area)

- Schema change took 25 minutes

- DB conversion on first startup took 55 minutes

- Total time for 5.10 upgrade - 3 hours



5.10 - 5.20 Upgrade:

- Backup 5.10 DB and copy to other server and burn CD

- backup size re-grew a bit to 450MB

- Cleaned out 5.00 DB and backup.1 since not needed anymore - left folders &
software

- Upgrade process went without any issues at all

- Schema Change took 18 minutes

- Conversions took 24 minutes

- Total time for 5.20 upgrade - just under 2 hours



Client Upgrades:

- 5.20 Client install is a LOT slower than 4.0 and requires a reboot

- found that doing 4-5 in a cluster at same time was fastest

- be sure to uninstall 9.0B (or whatever) and re-map drive to Epic52

- Note: on remap some would open folder and others not found that if I
unchecked "reconnect" box and re-checked it then it would force folder open
(faster access to client install)

- on shop floor PCs if DataCollection.vtg is in startup change it to Plant
Floor.vtg



Report Builder:

- had to open and save each report to get it to check for missing fields

- biggest field change was where quantity field is now OurQty (added Our)

- Type (on job) is now JobType so conflicted with calc field in a few
reports

NOTE: had to change on 4.0 then make other changes under 5,.20

- when running reports from within Vantage you might get Convmap.cp not
found

you may need to edit Progress.ini (in Progress\bin) to replace all
references to locations messed up due to mapped drive letter - example
change from v:\epic52\progress to v:\progress

- had to go through every custom report link and re-point to new location
in epic52



Crystal Reports:

- major issue with some (not all) users getting dll\crpe32.dll not found

- ended up copying vangate\dll contents to user's VntgWk52 folder

- installed CR 8.5 (and have lost report distribution wizard at moment -
trying to reinstall)

- opened each report, set location to VntgWK52, verify DB

- a couple report (like ARForm) lost some links



Other things:

- must change vantage backup

- Edit BACKVAN.BAT to use correct DB location (epic52)

- Make sure a copy if VNTGBKUP.BAT exists in Progress\bin folder

- edit reference to progress\bin location (to be epic52) as needed

- check vantage.ini (and again progress.ini) and make sure references to
\epic52\ are really needed if the mapped drive letter already includes it -
take out as necessary - save a copy of the original file before editing

- move your VBP routines from the old vbp folder to epic52\vantage\vbp

- these would be any .p and .r routines called by Vantage Basic forms -
if you have any

- if you have ABOM and Engineering Workbench - check security settings on
new menu options

- expect client startup to be a lot slower and splash screen to go away
really fast leaving users wondering if Vantage is going to start so they try
to start again - consider restricting multiple sessions and modifying the
splash screen image (in Vantage\bitmap).



Dangling Issues:

- Run Cost Capture before first WIP report - otherwise old closed jobs show
up

- Don't hang around in Customer Shipment Tracker - can lock invoicing Get
Shipments process

- ODBC compatibility questions with P9.1D (we don't use ODBC much but might
in future)



[Non-text portions of this message have been removed]