How to Upgrade very old ESuite Project database 2.3/3.3 (1.7.1006) to latest ESuite 6.0 (1.17.1010)

We have an very old ESUite project and security database that we need to upgrade from ESuite Project database 2.3/3.3 (1.7.1006) to latest ESuite 6.0 (1.17.1010).

We tried on ESuite 6.0 but the automatic upgrade stops with a note on Access 97 and Access 2000 not compatible and we do not know how to best proceed.
1 person has
this question
+1
Reply
  • This reply was removed on 2013-02-04.
    see the change log
  • Some of the old ESuite shortcuts and tool does not work after the upgrade and some are missing.

    To get the tools and shortcuts to all ESuite tools to work, create a new project, delete all the files and folders except the ESuite tools and shortcuts. Copy and paste the folders, project.mdb and SecMandb.ujx from the upgraded project into the new EuroPS project.

    The project is still with old icons and shell. How do we best upgrade to new icons and shell keeping the old custom application windows, scripts and tags?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Some notes on how to upgrade an old ESuite project to latest FoxboroPAC OPSS version including latest shell application (notes based on upgrade to OPSS 6.1 from ESuite 2.X).

    The notes are based on instructions in the old and not up to date document “Eurotherm Suite Installation and Setup User Guide” and were made as a compliment to help with the update.

    Upgrade ESuite Project database

    1. Upgrade project database, follow instructions on page 87 in old document Eurotherm Suite Installation and Setup User Guide: "Upgrading a project database" - especially for "very" old ESuite projects that cannot be upgraded automatically.

    If required ask Eurotherm Support for assistance to upgrade the project databases.

    Upgrade to new Shell Application

    2. Create new project UPGRADE with correct shell app

    3. Run WindowMaker to convert/upgrade windows to new screen resolution if different compared to shell app resolution

    4. Create new project with the same name as the old project that will be upgraded to get correct shortcuts (also not to get common warning on build: directory read-only)
    Only required for an old project without short cuts etc, not required for recent project.

    5. Keep files and shortcuts in the new project root directory,
    remove all subfolders in the new project directory
    Only required for an old project without short cuts etc, not required for recent project.

    6. Copy all subfolders from the old project into the new project directory
    Only required for an old project without short cuts etc, not required for recent project.

    7. Build project. Verify if there is lines like:
    "The following tags have access names to a LINDATA IO server but were not processed this build"
    with a list of tags followed.
    These tags should be removed from the InTouch tag dictionary to make it easier to compare which tags that have been created locally.

    8. Run WindowMaker to convert/upgrade windows to new screen resolution if changed compared to old installation.

    9. Delete all tags that should be removed according to prior ESuite project build. Close WindowMaker.

    10. From InTouch application, select the customer project to be upgraded and do DBDump.
    Required for projects where local tags have been created and when there is no overview of which tags have been created.

    11. From InTouch application, select the UPGRADE shellapp project and do DBDump.
    Required for projects where local tags have been created and when there is no overview of which tags have been created.

    12. Compare the two DBdump csv files and make a list from the comparison for all local tags that will need to be created!
    ZZ-tags in old shellapp for the old project that has been deleted in new shellapp will not need to be re-created in the upgraded project based on new shell app.
    Required for projects where local tags have been created and when there is no overview of which tags have been created.

    13. Move the
    UPGRADE\FactorySuite\Clients\InTApps\UPGRADE
    folder into
    \FactorySuite\Clients\InTApps\
    folder.

    14. Delete the UPGRADE project.

    15. Rename the folder
    \FactorySuite\Clients\InTApps\
    as
    \FactorySuite\Clients\InTApps\BACKUP

    16. Rename the folder
    \FactorySuite\Clients\InTApps\UPGRADE
    as
    \FactorySuite\Clients\InTApps\
    Keep the old application name if it is with or without $-prefix.
    Newer projects will have a $-prefix in the application name (for instance the upgrade project: $UPGRADE).

    Upgrade EurothermSuite graphics, see page 87 in old doc Eurotherm Suite Installation and Setup User Guide: "Upgrading EurothermSuite graphics"

    17. Copy the following files from BACKUP to directory.
    Verify directories in config files, for instance if changed from D:\ to C:\
    Review content of files before overwriting new files with old files if new content has been added!
    a. Dhistcfg.ini
    b. EuroWiz.ini
    c. InTouch.ini
    d. Spc.ini
    e. Password.bin
    f. Alarm.cfg

    18. Verify if any changes has been done to Point Page csv files in \PtPgCnf\.
    These changes may have to be re-applied to the new Point Page csv files. If the csv files have not been altered between versions, you can overwrite them with your modified ones.

    19. Copy any configurations of
    a. ZZ_Faceplate.csv
    b. ZZ_OpGroup.csv
    c. ZZ_Trend.csv
    from BACKUp to directory

    20. Copy any project-specific file from BACKUp to directory.

    21. For a redundant system, verify primary server is not the development server, change to runtime server if required in Project Configuration

    22. Build the Alarm Groups ?
    In old backup folder: AlmGrp.cfg, should this be copied?

    23. Recreate local InTouch tags or import with DBLoad as of previous dbdump and tag comparison.

    24. In WindowMaker import all windows other than those that start with
    ZZ_ and
    Template Window
    from Backup application.
    Ensure Select "Use Existing Tags (Conserve Placeholders)"

    25. In WindowMaker import all scripts other than those that start with
    ZZ_,
    $ApplicationChanged (data change),
    $InactivityTimeout (data change),
    $InactivityWarning (data change),
    $Operator (data change),
    AlarmHistoryError (ActiveX),
    TagSelection (AtciveX),
    TextEntryChange (ActiveX)
    from Backup application.
    Select "Use Existing Tags (Conserve Placeholders)"

    26. If alarm codes need to be different from standard / If Alarm Colours need to be different from the standard, open the following mimics and update the wizards with your alarm colours as specified in Eurowiz.ini:
    a. FASCIA1 to FASCIA16: one wizard each window to select and OK
    b. ZZ_ALARMBANNER: change colours on alarm summary display (two line display)
    c. ZZ_ALARMPAGE: change colours on alarm summary display
    d. ZZ_BANNERALARMBUTTONS: all the button wizards must be selected and OKd
    e. ZZ_EXPANDEDALARMBUTTONS: all the button wizards must be selected and OKd.

    NOTE. Keep the shift key pressed whilst performing these actions to prevent moving the graphics. You can update the wizards by simply double-clicking the graphic and selecting OK or Enter. This reads the Eurowiz.ini file for the new colour settings.

    27. Change any Customized ZZ_ windows.

    28. Change hidden file in C:\EuroPS\\ufolder.ini. Remove $-sign in InTouch application folder name.
    Required for old projects where the InTouch application name and directory does not include the $-prefix.

    Upgrade to new Shell Application Completed!!

    Changes to Project Configuration

    29. Changes to Project Configuration:
    a. Verify for Computers that Local Project Path is set to correct Local path
    (If changes are to be made from original installation!)

    30. Verify User Variables in Project Configuration.

    31. Verify System Variables / System Setup in Project Configuration.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited