Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

#

Installation, Technical and License Issue

Answer

101

After starting the Tagger, it displays the error message "...no valid license found...".

Please, activate the license by adding a license key and clicking on Activate License (Info → License→ Serial Number).

102

When activating a license with license key, the error "The LicenseSpot server cannot be reached at this time" appears.

The Tagger does not seem to have internet access and cannot activate and download the license via internet. The connected server URL is https://app.licensespot.com. To solve this issue, whitelist the above mentioned URL or contact xbrl-support@amana.lucanet.com to get an offline license file.

Please try out the following steps:

  • go to Settings →  XBRL Processor Settings → Proxy Settings;

  • If you have a proxy server, please select "Own proxy" and add the settings; otherwise select "System proxy;";

  • Now try to activate the license again.

Image Removedimage-20240214-150026.pngImage Added

If the activation still does not work, please contact us about manually activating the license, as described in Installation and Update.

103

You receive a new license key after the old license expired, but it is not possible to activate the new license.

It is necessary to remove the old license before activating the new one.

To do so, go to Info → License → Open License Folder and remove the license file displayed in the folder, or simply click on the "Delete License" button.

Restart the Tagger and activate the License with your new license key again.

104

How can I go back to an older version of the XBRL Tagger after updating it?

When updating the XBRL Tagger, one old version will always be preserved. For instance, if updating from version 1.9.10 to 1.9.11, the version 1.9.10 is still installed. It can be started manually, by running the AMANA.XBRL.Tagger.exe in the users local AppData folder, which can usually be found here:

C:\Users\user.name\AppData\Local\AMANA\app-1.9.10\AMANA.XBRL.Tagger.exe

105

The Tagger user interface looks ugly, fonts and controls (boxes) are not in the right place.

This happens due to scaling issues when activating scaling of the Windows Desktop and usually when working with multiple monitors. The issue usually can be solved by:

  1. Activating Windows display setting "Fix blurry apps" https://support.microsoft.com/en-gb/help/4091364/windows-10-fix-blurry-apps

  2. Restart the computer (real restart, no sleep mode).

106

The Tagger main window is empty when starting the Tagger.

This happens when a custom scaling is defined in the display settings of the Windows operating system. To fix this issue:

  1. Please disable the custom scale rate in the display settings like described here: https://support.microsoft.com/en-us/windows/view-display-settings-in-windows-10-37f0e05e-98a9-474c-317a-e85422daa8bb

  2. Log off and log on again

  3. Start the Tagger, the issue should be resolved.

107

How can I compare my ESEF XHTML report with my audited financial statements in PDF?

  1. The XHTML must be converted into a PDF, for this purpose the XBRL Auditor can be used or also a web browser like Chrome. Using the scale function it should be ensured that the page breaks do not differ.

  2. Using a PDF comparison tool, you can then make the differences between the contents visible. Various third-party tools are available for this purpose:

    1. PDiff Pro - is a lightweight PDF comparison tool that can easily compare only the content (even of tables), without taking into account the different formats.
      https://www.csci.de/en/pdiff/

    2. Adobe Acrobat - is also suitable, but it is slower and more sensitive to different formats. When comparing, the option "Compare text only" should be enabled.
      https://helpx.adobe.com/acrobat/using/compare-documents.html

  3. In the last step, a manual visual inspection of the formatting can be carried out:
    a.    Are the page breaks correct
    b.    Have headers and footnotes been transferred correctly.
    c.    Are graphics displayed correctly in the ESEF report.

...