Update
Overview
Update waveware to load patches and error corrections, and to update system packages and all other system files of the active data world. You are informed about it in the Data World Management (in the column 'Status'), if you must execute this module.
For an update to a version 11.200, the initial version must be at least 11.180. This is checked before an update. If this is not the case, the following message is displayed with a link to an article in the waveware Online hHelp that explains the correct update sequence.
An update of the data world is no longer mandatory from waveware 11.200.1652 if the new version only differs in the last digit (e.g. from 11.200.1652.25 to 10.200.1652.30). In this case, the update is only offered if the data world has been manually deactivated beforehand. You are then free to carry out the data world update or to reactivate the data world without the update. If you suspend the data world update, you will receive no system package updates.
Create a backup, before you start the update. A relevant inquiry occurs:
Click on 'Create', to create a backup. In the following dialog you can select a backup directory, where the backup is to be saved (more information under 'Create backup'). If the creation of the backup fails, the update is not implemented as well. Click 'Update' to implement update without backup (not recommended).
When facing problematic cases, you are probably informed, that you should reset your system to the original state.
Click on 'Create', to create a backup. In the following dialog you can select a backup directory, where the backup is to be saved (more information under 'Create backup'). If the creation of the backup fails, the update is not implemented as well. Click 'Update' to implement update without backup (not recommended).
When facing problematic cases, you are probably informed, that you should reset your system to the original state.
During an update, all system package information is overwritten, the new one is considered as existing one. Moreover, rules are removed, as they are for example, expired, the assigned user rules as well as all system rules and resources are removed.
After the update, an HTML file with the name "wavewareUpdate%date&time%.html" appears in the default browser. This file is located in the Temp directory in the sub-folder 'LoyHutz'. You find hints, error messages and warnings in this file, which occurs during the update.
Messages
The following tables show possible messages that may appear and a corresponding recommendation for action.
Error Messages
| Message | Recommendations |
|---|---|
| The directory you entered does not exist. Please, check your entry. | Specify the right path to upgrade data world. |
| You try to use your own waveware system as an upgrade base. It is not possible. | Select a real upgrade data world. |
| The directory does not have the correct structure. Please, check whether you have selected the correct folder. + Missing file / missing folder. | The message specifies which file or folder is missing. If this is the case, you have selected a corrupt upgrade data world. Please, exclude only the data world from the delivery for an upgrade. |
| The imported packages are included in the selected upgrade data world. Such data world is not effective for an upgrade. Please, try again with a correct waveware system data world. | Please, exclude only the data world from the delivery for an upgrade. |
| Errors have occurred, when checking the package file. | You have selected a corrupt upgrade data world. Please, exclude only the data world for the delivery for an upgrade. |
| You can upgrade a waveware system only if it has the same version status. Version of the data world: (0). version of the waveware server: (1). | Update your entire system or refrain the upgrade attempt. This data world contains innovations, which you cannot use yet. |
| The comparison of the DEF file could not be executed, as errors occurred. | A critical error has occurred when comparing the DEF files. At this point, no changes can be implemented. Please, contact the support with the particular error message. |
| The database cannot be refreshed. All changes are withdrawn. | A critical error when changing the database. As database changes could be executed in a so called transaction, it can be withdrawn. There are no changes for this time. Please, contact the support with the particular error message. |
| Errors occurred when updating the package. | A critical error led to the interruption. Please, contact the support with the particular error message. |
Warnings
| Message | Recommendations |
|---|---|
| A filed is already available, to which a hierarchy (0) is assigned. In this table, two fields with an identical hierarchy cannot be located. Field (1), field type (2) (table: (3) - (4)). | Please, open the table after the upgrade with the designer and check why another field is assigned to this hierarchy and whether you really want it. |
| An attempt was made to import a field, which already exists with another field definition. FId: (0), Field type (1) – new (2) (Table: (3) – (4)). The previous field definition is retained. | The system brings about the changed fields. It can happen, if you make changes or if the system delivery was changed. The field remains unchanged. Perhaps, the rules depend on the filed type changes. As the data loss cannot be excluded, please check the field type change with the help of the Designer. |
| An attempt was made to import a field, which already exists with another field definition. The field is however assigned to another catalog. FId: (0), catalog (1) – new catalog (2) (Table: (3) – (4)). The previous field definition is retained. | The last line. However, the field type was not changed here, but only the assigned catalog. Catalog changes can have consequences, such as the record can no longer be saved, because the data is not available in another catalog. |
| The configuration file (package.conf) of the package (0) cannot be loaded. | If the configuration file of the package could not be loaded, it is not possible to upgrade this package. Please, contact the support with the particular error message. Probably, you must implement the data world upgrade again. |
| Package structure cannot be loaded. | The package structure specifies the order of the package in the package tree, in the system rule editor. Probably, the upgrade data world is corrupt. The upgrade has been continued, and if new system packages have been added, they do not appear in your structure. Please, contact the support, they can explain, how to adjust the structure on your own. |
| Package structure cannot be merged. | Probably, the upgrade data world is corrupt. The upgrade has been continued, and if new system packages have been added, they do not appear in your structure. Please, contact the support, they can explain, how to adjust the structure on your own. |
Hints
| Message | Recommendations |
|---|---|
| The DEF view file (0) was ignored as the hash value of the available DEF view file does not match. (Changes are not overwritten when updating). | This is merely a hint for you. You have changed DEF view files (so card interfaces and the like) with the Designer. At this point, you cannot overwrite your interface changes of the edited system file by Loy & Hutz. In the HTML file, an exact listing of the DEF view file content is located. You have an option to compare your DEF view with the delivery DEF view and to make manual adjustments. |
| The system rule (0) has a small version like in your system. The file is not overwritten. | You probably use an older upgrade data world.This is not a problem, however new rules are not overwritten through older rules. |
| The rule (0) was changed in the system version, but you still work with your own file. (Your changes were not overwritten through the update). | Your rule is still valid. To be able to view changes, there is only an option: you can rename your rule. Then, the system rule shines again. You can compare it with your rule and optionally retain, adjust or delete yours. If you want to retain your rule, you must change the name to the original one and hide the system rule again. |
| The image (0) was changed in the delivery. As you have changed the image, you still work with your own image. | Your image is still valid. To be able to view changes, there is only an option: you can rename the image. Then, the system image shines again. You can compare it with your image and optionally retain or delete yours. If you want to retain your image, you must change the name to the original one and hide the system image again. |
| The resource (0) has a small version like in your system. The file is not overwritten. | You probably use an older upgrade data world.This is not a problem, however new resources are not overwritten through older resources. |
| The resource (0) was changed in the delivery. As you have already changed this file,you still work with your own file. (Your changes were not overwritten through the update). | Your resource is still valid. To be able to view changes, there is only an option: you can rename your resource. Then, the system resource shines again. You can compare it with your resource and optionally retain, adjust or delete yours. If you want to retain your resource, you must change the name to the original one and hide the system resource again. |
| The web file (0) has a small version like in your system. The file is not overwritten. | You probably use an older upgrade data world.This is not a problem, however new web files are not overwritten through older web files. |
| The web file (0) was changed in the delivery. As you have already changed this file,you still work with your own file. (Your changes were not overwritten through the update). | Your web file is still valid. To be able to view changes, there is only an option: you can rename your web file. Then, the system web file shines again. You can compare it with your web file and optionally retain, adjust or delete yours. If you want to retain your web file, you must change the name to the original one and hide the system web file again. |
Update