https://wiki.heidler-strichcode.de/w/index.php?action=history&feed=atom&title=Update_Loading_Release 2026-10-25T19:57:26Z Versionsgeschichte dieser Seite in Wiki - Heidler Strichcode GmbH MediaWiki 1.35.2 https://wiki.heidler-strichcode.de/w/index.php?title=Update_Loading_Release&diff=5969&oldid=prev 2024-10-02T12:53:02Z

<p>Die Seite wurde neu angelegt: „<a href="index.php?title=Aktualisierung_Verladefreigabe" class="extiw" title="de:Aktualisierung Verladefreigabe">de::Aktualisierung Verladefreigabe</a> In this description, you will find all the necessary information to update a Loading Release (Service + Desktop). Please…“</p> <p><b>Neue Seite</b></p><div>[[de::Aktualisierung Verladefreigabe]]<br /> In this description, you will find all the necessary information to update a Loading Release (Service + Desktop). Please read this carefully. For any questions, please contact support directly at ([mailto:support@heidler-strichcode.de support@heidler-strichcode.de])<br /> <br /> = Directory Name / Service Name =<br /> The Loading Release is typically installed in the Heidler directory as LoadingReleaseService and LoadingReleaseDesktop.<br /> <br /> The name of the Windows service corresponds to the name of the installation directory. The Windows service only exists for LoadingReleaseService.<br /> <br /> = Compatibility =<br /> <br /> * In principle, all versions from Loading Release version 2.1.0 can be automatically updated to the latest version<br /> ** For older versions, please contact our support<br /> * Please note that you always need the latest version of LoadingReleaseService and LoadingReleaseDesktop<br /> ** We cannot guarantee functionality with version differences between these two applications<br /> <br /> = Update Duration / Downtime =<br /> No loading is possible during the update.<br /> <br /> Please plan approximately 10 minutes for the update of both applications.<br /> <br /> = Dependencies on Other Heidler Applications =<br /> There are no dependencies on other Heidler applications that need to be considered during updates.<br /> <br /> = What Needs to Be Done After the Update? =<br /> During the update, the Windows service is automatically stopped. It does not start automatically after running the setup. This must be done manually.<br /> <br /> == How Do I Check if the Application is Functioning Properly After the Update? ==<br /> After the Windows service has been restarted, the logs for the Loading Release should be checked. These are located in the main directory of the respective application in the Logs subfolder.<br /> <br /> ==== LoadingReleaseService ====<br /> &#039;&#039;&#039;service\root.log&#039;&#039;&#039;: This log records the start / stop of the Windows service as well as the individual loading processes.<br /> <br /> &#039;&#039;&#039;service\error.log&#039;&#039;&#039;: This log contains all application errors that occurred.<br /> <br /> ==== LoadingReleaseDesktop ====<br /> &#039;&#039;&#039;root.log&#039;&#039;&#039;: This log records the start / stop of the application as well as the individual loading processes.<br /> <br /> == What Tests Should I Conduct After the Update? ==<br /> After the service is started and the logs have been checked, a test shipment should be loaded and then blocked again.<br /> <br /> = Other Particulars =<br /> There are no further particulars.</div>

Jburggraf