Hauptmenü öffnen

Update HVS32DBArchiving

Version vom 2. Oktober 2024, 11:43 Uhr von Jburggraf (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „de::Aktualisierung HVS32DBArchivierung In this description, you will find all the necessary information to update an HVS32 DB Archiving (also known as DBA)…“)
(Unterschied) ← Nächstältere Version | Aktuelle Version (Unterschied) | Nächstjüngere Version → (Unterschied)

In this description, you will find all the necessary information to update an HVS32 DB Archiving (also known as DBA). Please read this carefully. For any questions, please contact support directly at (support@heidler-strichcode.de)

Directory Name / Service Name

The DBA is typically installed in the Heidler directory as HVS32DBService.

The name of the Windows service corresponds to the name of the installation directory.

Compatibility

  • All versions of DBA from version 3 can be updated to the latest version.
  • For older versions, please contact our support.

Update Duration / Downtime

No downtime is necessary.

The update can be applied in about 5 minutes.

Dependencies on Other Heidler Applications

There are no direct dependencies on other Heidler applications that need to be considered during an update.

What Needs to Be Done After the Update?

During the update, the Windows service is automatically stopped. It does not start automatically after running the setup. This must be done manually.

How Do I Check if the Application is Functioning Properly After the Update?

After the Windows service has been restarted, the DBA logs should be checked. These are located in the main directory in the Logs subfolder.

archive.log: This log records the start / stop of the Windows service, as well as the individual archiving steps.

error.log: This log contains all application errors that occurred.

Check both logs to see if the modules loaded successfully and if any error messages appear.

What Tests Should I Conduct After the Update?

After the service is started, the log should indicate the next upcoming archiving.

The log entry looks something like this:

Archiving will begin on Sat Nov 26 17:30:00 CET 2022

Please check the logs after the specified time for any errors that occurred during the archiving.

Other Particulars

There are no further particulars.