Update
Back |
Level back
In general, an update is always a complete installation, thus not
patching an existing version, but replace it entirely.
The EULANDA.MSI basically replaces 2 files - eulanda.exe and the help
file eulanda.chm. No changes are made to the Windows® registry or any other
DLL file. After starting the software, the first thing is to update the
database reflecting the new structure. Because of the database update you
have to backup the
program and the database, creating a fallback, in case the update fails.
Plan of action
- Backup
Backup your
Data and the
old program version - eulanda.exe. Use an external backup software.
- Update (Please note: Any changes from more than half a
version number, require a new license key.)
- Via CD
Insert the EULANDA®-CD and install the software
on all workstations, where ever the software was installed prior.
The installation recognizes an existing installation and replace the
respective files. Alternatively you can click the button "update" in
the master menu of the EULANDA® ERP software and subsequently the
selection „Search
media for update files and install“.
The button is deactivated when the EULANDA® ERP never before was
installed on this particular PC - a program link allows you to
execute the program, but as for the system, the program was not
installed. In this case go to the PC from where you originally
installed the EULANDA® ERP Software and repeat the action.
The eulanda.msi file on the
CD will be found automatically.
- Via Download
You can load the update from our internet
server and there from the
Knowledge base. Check the download section for the latest
eulanda.msi update file. Safe this file on your desktop and start
the installed version. Right click in the menu and select from the
administration menu „Search
update from media and install“.
The button is deactivated when the EULANDA® ERP never before was
installed on this particular PC - a program link allows you to
execute the program, but as for the system, the program was not
installed. In this case go to the PC from where you originally
installed the EULANDA® ERP Software and repeat the action.
- Via Internet
Use the Update
button from the EULANDA® ERP software to check whether a newer
version is available and if yes, download and install the update.
The button is deactivated when the EULANDA® ERP never before was
installed on this particular PC - a program link allows you to
execute the program, but as for the system, the program was not
installed. In this case go to the PC from where you originally
installed the EULANDA® ERP Software and repeat the action.
An
update via the internet can be done up to that version, which still
is covered by the existing license number, e.g. you run software
version 2.0; on the Internet available versions 2.1, 2.5 and 3.0.
Version offered for update in this case will be version 2.1 only,
since this is the last version available of the 2.0x to 2.49 series.
Updating more than half a version number always require a new
license key and an installation CD (alternatively use the above
described download procedure
- Start EULANDA® ERP
Restart the EULANDA® ERP software after
the installation is done. On the next start the software checks whether
the database structure has to be updated, according to the new software
version or not. If a database update is required the software will
suggest a database backup in the next step. You'll need the
Administrator's account (sa) for the backup to start. Usually this is "sa"
with a blank password. When the backup is done, the database structure
will be updated. Aside this, the server program and the SQL Registry are
updated. The entire process may last from minutes to hours, depending on
the size of the database and the versions to cover.
Error - as usual - may have various reasons. Very likely are:
- Log-file full: When your file system is FAT32, the max. size of
files is limited to 4 GB. Converting the database, requires that all
changes are protocolled before the actual changes are applied. In
this case the file size required may be up to 10 times the size of
the actual database.
- SQL-Server out-dated: The SQL Server should have at least
Service Pack 3 installed. Within the EULANDA® ERP you'll find this
information using the dropdown menu "?" and there System
information.
The
SQL-Version number should end with at least "760". The SQL
Server can be
updated with patches from the EULANDA®-Product-CD .
- In case of errors, please check the file „EulandaUpdate.Log“,
found in the program folder of the EULANDA® ERP. If required, sent
this file to support@eulanda.de.
- Check data
Important: After an successful update it is
mandatory you'll check your data, report templates and Info Systems.
Only in case you do not find anything unusual, you can start using the
new version. If you encounter errors, you should rollback the entire
update - restore database and program.
- Update all workstations
It goes without saying that all
workstations in the same net require the same program version otherwise
unpredictable results can occur and / or severe damage can be done to
your database. To avoid this possibility we strongly recommend you only
use program links on all workstations. This way all updates can be
handled conveniently on the server, else you have to update each
individual PC, following the above mentioned procedure.
In case
individual workstations can not access the database, reason probably is
the Service Pack 3 or the Service Pack 2 from Windows® XP and or the
activated firewall. Check the hints in the chapter
Net work installation.
Tip
Because of the complexity and interaction of program and SQL server, an
update over several versions (e.g. version 1.2 to version 2.1) is not
possible. Therefore updates have to be done in steps of half a version
number (e.g. 1.2 to 1.5 to 2.0 etc). Older updates can be found in the
eulanda section of the newsgroup as archived files.
An new license number or registry key is required when passing every half
version number (e.g. 1.2 to 1.5 or from 1.8 to 2.0 etc) Without this key,
the database can be used as demo database only. The registry code is saved
in the client's database, therefore it can't be deleted by de-installing the
database and / or program.