Product:

Microsiga Protheus

Versions:

11

Step by Step:

1. PREPARING THE CURRENT VERSION FOR MIGRATION

- Prepare a test base, making a cold backup (all services stopped) and consistent (of appropriate folders and database) of production base.

- If your Data Base is Relational (use DBACCESS), you must run the verification process of duplicated records for all companies. Wizard executed from CHECKDUPL routine via Configurator, which has the updating of the standard data dictionary in the SYSTEMLOAD as a requirement. To download the dictionary, follow the procedures of this link: Update Protheus 11 Data Dictionary

Creates in the Protheus_Data folder, the MIGRATION folder, and unzip the full data dictionary of the 11.8 version. In the verification of duplicity the SX2.UNQ, use version 11.8 as reference for verification.

- See Instructions for the verification of duplicities in the link: CheckDupl Routine – Checks the Integrity of Duplicated Records
 
2. UPDATING THE SYSTEM

You must update the Binary, RPO, Update and LIB. Procedure of updating in the link:

Basic updating of Protheus 11

3. UPDATING THE DATA DICTIONARY

You must update the Data Dictionary files (sxsbra.txt) and Fields Help in the Systemload folder Procedure of update in the link:

Data Dictionary:

Update Protheus 11 Data Dictionary

Fields Helps:

Update the Fields Help

 
4. UPDATING THE MODULES MENU

You must update the files .xnu (menus of modules). To download files, access:

- Customer Portal: http://suporte.totvs.com

- Menu Downloads and Updating - Protheus Line

- Microsiga Protheus Version 11

- All - Category:Module Menu

- Download the file MENUS - BRASIL Note: if versions are not being displayed, in "Filters of packages", select "All packages available", then select the category again. To update it:

- Stop Protheus (Appserver) server - Backup files .xnu of \Protheus_Data\system folder - Remove all menu files of folder system (.xnu).

- Copy .xnu files downloaded from the portal for this folder.

- Restart the Protheus server (Appserver) Remember the customized menus need to be redone, as there are routines of version 11 that do not exist in the RPO of the version 11.

5. CLEANING FOLDERS

- Delete files *.DBF of directory SYSTEMLOAD

- Delete the files *.IDX of directory SYSTEMLOAD

- Delete file *.TSK of directory APPSERVER

- Delete file *.LOG of directory SYSTEM

6. RUN COMPATIBILITY PROGRAM OF MIGRATION

- Open the SmartClient and, Initial Program, enter MP710TO110

- Click Next - Enter Login and Password of Admin, the press key TAB

- Select box Update 11 R? for 11.8 then click OK - Click Next - On the screen Data Directory, click Next

- In Configuration of Update execution, we indicate keep the options Log of Critical Error and Adjust automatically errors enabled, remembering the option to automatically adjust errors run base changes by the system itself

- NO, select Keep existing log

- Click Next / Next - Wait compatibility program process. If during the process, critical errors that cannot be automatically adjusted arise, they must be MANUALLY adjusted, using as base the Critical Errors link (below), or inquiring the Support if the error is not listed

CRITICAL ERRORS

In case of critical error, the customer must make the proper adjustments, then delete file in which directives of installation (mpupd.tsk) found in the directory "...\bin\appserver", then run routine MP710TO110 again. Not deleting this file, migration continues from the point it previously stopped. Link with adjustment of the most common critical errors: Most common critical errors in migrations

At the end of the migration, contact any module, enter menu Help/About, then check information of the new release.  

Notes: