Faq

How can I verify/change Java settings used by aSISt: 32-bit or 64-bit?

In order to check  the Java version used by aSISt: 32-bit or 64-bit, please follow one of the steps:

  • Alt -A  ->  About aSISt 
  • Alt – A -> Settings -> Local -> JVM settings 

 

If a computer with installed aSISt supports 64-bit operating system, while the aSISt settings indicate 32-bit JVM version, then using aSISt Settings, please follow steps below:

  • change Java settings from 32-bit to 64-bit version:

Alt – A -> Settings -> Local -> JVM settings -> Use 64 bit JVM

  • increase memory assigned for aSISt:

Alt – A -> Settings -> Local -> Memory management

ATTENTION! From version 5.28.1 the aSISt application can work only on a computer with a 64-bit operating system.

How to check the version of the aSISt application?

To check the version of your aSISt application, please run the “about aSISt” function, selecting:

Alt-A  -> about aSISt

The application window also presents information about database version and database type (ORACLE or DERBY).

I am not sure if I downloaded update file from the aSISt website completely. How can I check it?

Since 5.16.2 version of the aSISt application, the link to the file with checksums is available at the lower part of the update package.

To be sure that downloaded file is correct, please create checksums from the file and compare with the checksums available on our website.

Which files should I send to the aSISt support team in case of problems with application?

In case of any problems with the aSISt application, please attach the file with logs to the email addressed to: support@asist-xbrl.eu

To generate logs, please run the “About aSISt” function (ALT+A -> About aSISt) and in the new window click the “Dump debug data” button.

The “dump.zip” file doesn’t contain report data. It includes information about the operation of the application when problem occurred.

What should I do to transfer the aSISt application with Derby database to a new computer?

To transfer the aSISt application from current computer to a new workstation, please:

1. make a backup of derby database using the “Preparing backup” function (ALT+A -> “Preparing backup”),

2. download full version of aSISt from our website (https://support.asist-xbrl.eu/en/downloads),

3. install the aSISt application on the new computer using downloaded file,

4. from the old aSISt home directory please copy to the new aSISt home directory file:

  • aSISt.license,

and catalogues:

  • derbydb,
  • preferences (If you would like to have the same user’s settings on the new workstation just like you had on the old one).

5. Update the aSISt application to the current version using:

  • local update (using file/files downloaded from our website),
  • automatic update (If you have an internet connection and the proper address for update config file).

6. On the new computer upload file with backup that was created from the old database.

 

Please go to the Settings (ALT+A -> Settings), click on the LOCAL tab, and next go to tabs:

  • Memory management and add more memory moving the slider further, but it is not advised to move it to the end of the scale (The amount of available memory depends on the amount of RAM available on your computer).
What should I do to transfer the aSISt application with Oracle database to a new computer?

To transfer the aSISt application with Oracle database it is needed to move to a new server:

  • Oracle database (It can be made using Oracle tools (it is possible to use standard import and export tools).), and:
  • aSISt application

 

To move the aSISt application from an old workstation to the new, please:

1. download the full aSISt version from our website (https://support.asist-xbrl.eu/en/downloads),

2. install the aSISt application on the new workstation using downloaded file,

3. from the old aSISt home directory please copy to the new aSISt home directory files:

  • aSISt.license,
  • db.properties,

and catalogue:

  • preferences (If you would like to have the same user’s settings on the new workstation just like you had on the old one).

The db.properties file contains information about: URL address to the Oracle database, user name and password for aSISt user. It is possible to make changes in the file, if something is incorrect.

4. update the aSISt application to the newest version (ALT+A -> Update).

There are two ways to update the aSISt application:

  • local update (using file/files downloaded from our website), or
  • automatic update (If you have an internet connection and the proper address for update config file).

 

If your computer is running a 64-bit version of Windows, please go to the Settings (ALT+A -> Settings), click on the LOCAL tab, and next go to the tabs:

  • JVM settings, and select Use 64-bit JVM,
  • Memory management and add more memory moving the slider further, but it is not advised to move it to the end of the scale (the amount of available memory depends on the amount of RAM memory available on your computer).
How I can delete report?

It is not possible to delete a report in the aSISt application, but it is possible to make changes in settings defined during creating a report. In this case please choose “Report” in the menu, and next click “Settings”. You will be able to:

  • add or delete forms from the report,
  • make changes in explicit and typed dimensions.

 

It is impossible to change:

  • report’s type,
  • report’s period, and
  • consolidation’s type.
What should I do if my aSISt application works too slow?

If your application works to slow, please:

  • compare aSISt requirements with parameters of your computer

Requirements for the aSISt application are available at: https://support.asist-xbrl.eu/sites/default/files/documentation/aSISt_tranSIS-system_requirements.pdf

 

If your computer is running a 64-bit version of Windows, go to the Settings (ALT+A -> Settings), click on the LOCAL tab, and go to tabs:

  • JVM settings, and select: Use 64-bit JVM,
  • Memory management and add more memory moving the slider further, but it is not advised to move it to the end of the scale (the amount of available memory depends on the amount of RAM available on your computer).

 

Please notice that the application needs more time when the report is opened for the first time with a new taxonomy.

How can I enable blanked (greyed out) cells on the report’s table in the aSISt application?

From version 5.16 of the aSISt application it is possible to activate explicit dimensions from cell’s level (right mouse button – “Enable Cell”).

If the “Enable cell” function is unavailable, it means that the cell is deactivated because of taxonomy and it is impossible to activate it.

When do I need to update Oracle database additionally? How can I update Oracle database?

In case of the aSISt application update to the full version (when the second value after the point changes, for example  in case of update to versions: 5.15, 5.16, 5.17,…) it is necessary to additionally update the Oracle database.

To update Oracle database please:

  1. run update (local or from internet),
  2. during update, click “OK”, when there will be a question about the update method: with or without the database

 

Update with the database:

  • it is only necessary once per workstation
  • can only be made when
    • aSISt is running only on this particular workstation, and additionally:
    • no other workstations are subject to updates.

 

When updating next workstations the update is made only in the application.

 

If, during the update on the first workstation, you have omitted the database update and updated only the application, the database must be updated during the next workstation update.

 

If, during the update on all workstations, you have omitted the database update, then please contact aSISt support team with the request about script for updating Oracle database, and next:

  • In CMD run sqlplus,
  • Log in using login and password for the aSISt Oracle user,
  • Run script using: @<path_for_the_script> i.e. @C:Oracleoracle.sql,
  • Save changes using command: commit.

If you still can’t find solution, go ahead to contact with us

Report issue