A3. PostgreSQL is not supported for use with IUCLID 6. The only databases supported are JavaDB/Derby (free, as in no charge) and Oracle (commercial). For more information about software requirements please refer to the documentation section of this website.
A4. Tomcat is not supported for use with IUCLID 6. This is one of the major technical changes between IUCLID 5 and IUCLID 6. The Tomcat application server is replaced by GlassFish (version 3.1.2 or 4).
A5. Details of the OSs tested and supported by ECHA are available on the system requirements page of the IUCLID website.
A6. Yes. IUCLID 6 Desktop is available for Mac OS X from the download page of the IUCLID website.
Installation and system configuration
A9. Indeed, you should still use the version 5.6 of IUCLID to prepare dossiers for submission to ECHA for example, until the update of ECHA's submission tools. However you can install and migrate your data to IUCLID 6 already now. The migration from IUCLID 5 to IUCLID 6 copies data from one system to another so both systems can be used in parallel. Once the submission systems are updated to accept IUCLID 6 files, a final migration from IUCLID 5 to IUCLID 6 will have to be performed.
A22. This depends on whether users have been migrated from IUCLID 5 and whether the password of user SuperUser was changed via the Windows installation wizard. If neither of these were done, use the following credentials to log in to IUCLID 6 for the first time:
All credentials are case sensitive. For non-administrative use of IUCLID 6 it is recommended to use a user other than SuperUser. You can create new users whilst logged in as SuperUser.
IUCLID 6 Desktop version now also offer the option to work without user management. In that case the login step is by-passed.
If you have installed one of the IUCLID 5 Portable versions, please note that the credentials to login are admin / admin
A23. Technically it is possible to install IUCLID 5.6 Distributed and IUCLID 6 Server side by side on the same server. To do it you must first ensure that Tomcat (IUCLID 5) and Glassfish (IUCLID 6) use different ports. Such configuration should be used for test purposes only, because we do not support this for production.
To install IUCLID 6 Server, follow the steps from the installation manual which can be downloaded here.
A46. In case you do not remember which version of IUCLID is installed, you can download a small executable file to find out. Here is how to check your IUCLID 6 version:
- Download the IUCLID 6 version checker
- Extract the file to your IUCLID 6 installation folder, as below
- Execute the file by double-clicking it
- For a 32-bit version you should obtain the following result
- For a 64-bit version you should obtain the following result
Please note that there is only one updater provided for IUCLID 6 that will update your existing IUCLID 6 Desktop installation to the latest one, whether it is a 32-bit or a 64-bit installation.
A48. The following problems can be caused by insufficient system memory (RAM) being available to IUCLID 6 or its associated software tools:
- IUCLID 6 or a tool does not start;
- Unusually slow performance, especially when large files are handled;
- The error “Out of Memory exception” is output either to log files or the command line.
To avoid these problems, and to use resources most efficiently, consider the total RAM available to the computer, and how it is allocated to IUCLID 6 and each of its software tools. The recommended system resources for IUCLID 6 are stated here. Many problems like those given above can be solved simply by changing the values of certain system parameters in settings files. A detailed guide to memory management for IUCLID 6 and its tools, aimed at non-IT specialists, is provided in the document Java and Memory in IUCLID 6. What follows below is aimed at users with sufficient IT skills that they need to know only where to find the parameters.
IUCLID 6 and its tools are Java applications. Many problems relating to memory can be solved simply by increasing the maximum limit of allocation of RAM by increasing the value of the parameter Xmx for the relevant Java virtual machine (JVM). Where Xmx is set, Xms may also be set. The locations and default values are:
|Application||Default value||Settings file|
|IUCLID 6 Desktop||1 GB (-Xmx1024m)||<installation directory>\glassfish4\glassfish\domains\domain1\config\domain.xml|
|IUCLID 6 Server||4 GB (-Xmx4096m)||<installation directory>\glassfish4\glassfish\domains\domain1\config\domain.xml|
|IUCLID 6 Server (Client)||1 GB (-Xmx1024m)||<installation directory>\glassfish4\glassfish\domains\domain1\iuclid6\iuclid6-war-<version>.war\launch.jnlp|
|Migrator||2 GB (-Xmx2048m)||<IUCLID migrator>\bin\internal\migrator.cmd|
|Patch tool||1 GB (-Xmx1024m)||<IUCLID patch tool>\bin\internal\i6db-patch.cmd|
|Updater tool||1 GB (-Xmx1024m)||<IULCID updater tool>\bin\internal\updater.cmd|
|Start-up fixer tool||1 GB (-Xmx1024m)||<IULCID startup-fixer tool>\bin\internal\i6-startup-fixer.cmd|
A10. For migration of data, a migration tool is used. This tool migrates data from any supported IUCLID 5.6 database to any supported IUCLID 6 database. In addition, IUCLID 5.6 files with extension i5z can be imported into IUCLID 6.
A11. In order to migrate a IUCLID 5 database to IUCLID 6, it has to be upgraded to the latest version (5.6).
A12. It is a java application. It does not need GlassFish. It needs to connect to both databases, for example, PostgreSQL or Oracle on IUCLID 5 side, and Derby or Oracle on the IUCLID 6 side.
A14. The use of the migration tool would be recommended in that case.
A15. One pre-requisite for the migration to IUCLID 6 is to have upgraded the IUCLID 5 database to the latest version (IUCLID 5.6). Manuals are available on the IUCLID 5 website for the description of the IUCLID 5 update procedure.
A16. Yes, IUCLID 6 accepts the import of IUCLID 5.6 files. During import, the data is automatically migrated to the IUCLID 6 format. However, IUCLID 6 is not able to export data in the IUCLID 5 format.
A17. Yes. The migration tool migrates data from PostgreSQL to Derby databases. It connects to both IUCLID 5 and IUCLID 6 databases at the same time, and executes the migration from any supported IUCLID 5.6 database to any supported IUCLID 6 database.
A18. The migration tool is available for both the desktop and the server versions. However, it is not essential to use it in all cases because IUCLID 5.6 i5z files can be imported into IUCLID 6. The use of the migration tool is recommended for large amounts of data, for example, thousands of dossiers.
A19. Yes. If a IUCLID 6 server version is deployed and connected to a database, it is possible to migrate data to that database irrespective of whether the IUCLID 5 database was used with either a desktop or a server version. The IUCLID 6 database can then be used with either a desktop or server version of IUCLID 6.
A24. A migration function is built-in the Windows installer for IUCLID 6 Desktop. The function is accessed by clicking on the button Advanced, on the first page of the installer. It reads data from any supported type of IUCLID 5.6 database, and then writes it to a new IUCLID 6 embedded database. To perform a migration to an existing IUCLID 6 database of any type, use the migration tool that is supplied with the server versions of IUCLID 6. Its use is documented in a manual available here.
A33. The introduction of Instance Based Security (IBS) in IUCLID 6 allows data to be migrated and/or imported from different IUCLID 5 databases into one merged IUCLID 6 database in which access to the data is partitioned between Users and groups of Users.
Before attempting to merge IUCLID 5 databases, familiarise yourself thoroughly with the IBS functionality and consider what action to take (Cf. IUCLID 6 User Manual).
Some common scenarios are described here.
A34. The migration report generated by IUCLID 6 is a structured text file that can be imported in a spreadsheet programme like Excel for further analysis. You will find more information in the migration report presentation.
IUCLID functions and integration with other systems
A20. Web services are designed for using IUCLID 6 with external systems, but the integration with specific systems; such as IHS Intelligent Authoring, and SAP EHS, will have to be implemented by the users. ECHA will develop the integration of IUCLID 6 with, for example, Chesar 3 and the QSAR Toolbox. In addition, ECHA will provide guidelines on how to achieve integration with other systems.
A26. This problem can be caused by an antivirus program; or by a firewall or a proxy between the client and the server. There could be an intermediate proxy that rewrites requests or responses. Try to run the IUCLID 6 client locally on the server. If the client can run locally without this problem, you will have to configure your network so that the IUCLID 6 clients make direct connections to the server.
A30. A user with 'Access All' can view and update the accessibility of all sections in Role - Data access.
A user with 'Read/Write/Delete' rights to roles but with 'No access 'on a section in 'Data Access' cannot see or update the accessibility of that section for any role.
A user with 'Read/Write/Delete' rights to roles but with 'No access' to an entity in 'Permissions' can see and update the accessibility of that section for any role.
The visibility of data sections should be the same as for entities.
The work-round is that a user must have at least 'Read Access' to any section in order to be able to see and grant rights to it in 'Roles - Data Access'.
A39. The log files generated by IUCLID can be found in different locations according to your installation type:
IUCLID 6 Desktop: <IUCLID6 installation folder>\glassfish4\glassfish\domains\domain1\logs
- IUCLID 6 Desktop installer wizard: <IUCLID6 installation folder>\logs or i6inst\logs (in case the installation is not successful)
- IUCLID 6 Server
- Server side logs - from the IUCLID 6 server: <IUCLID6 installation folder>\glassfish4\glassfish\domains\domain1\logs
- Client side logs - from the computer where IUCLID 6 was used: C:\Users\<username>\iuclid6\<URL>\logs
- IUCLID 6 migration tool: folder “logs” in a folder where the migration tool was launched, or one level above. If the migration was executed with the IUCLID 6 Desktop installer wizard then the migrator logs will be in: <IUCLID6 installation folder>\logs
A49. At present, we can only ensure full compatibility between Chesar 3.3 and IUCLID 6.2.
Be aware that neither IUCLID nor Chesar updates are necessary for you to finalise your dossiers for the 2018 deadline. You can finalise both your Chesar files and IUCLID technical dossier using IUCLID 6.1.3 and Chesar 3.2.
Although Chesar 3.3 and IUCLID 6.1.3 are compatible in the majority of cases, some small issues may occur which may break the compatibility between the applications. At this moment we are aware of the following incompatibilities between those versions:
- If you select more than one option in the field “Regulatory status” at use level in Chesar Box 2 (available in Chesar when you tick the box “Show additional fields relevant for use description in IUCLID”), the export of uses to IUCLID and the generation of the full CSR will not be successful.
- Some issues appear in the generation of sections 1-8 of the CSR when generating the full CSR from Chesar, such as double printing of the hazard pictograms or display of the UUID instead of the name of the linked service life.
A21. Please note that if you request to download IUCLID 6 using the Mozilla Firefox browser, a security warning may be issued. You can dismiss the warning by clicking on the cross icon at the top right of the message window. This does not prevent the download process from continuing. We are working on how to prevent the warning.
A41. This means that IUCLID 6 tried to reserve the port 4848 (Glassfish Admin Console port) but it could not because something else is already listening on this port. Because of this IUCLID 6 could not start. In most cases this is caused by an instance of IUCLID 6 that is hanging, i.e. this instance was run but could not start and is stuck in some state still holding the port 4848 reserved.
The two most common causes for this are:
- Proxy issue.
- Lock file issue.
A proxy issue occurs when the proxy server is not bypassed for the local addresses. The lock file issue can occur after a collapse of the application. In that case a so-called lock file can remain on the filesystem preventing IUCLID 6 from starting. Please see below for further information on these causes.
1. Proxy issue
Sometimes users installing IUCLID 6 Desktop experience the following situation:
- Installation seems to be going OK until it reaches 99%.
- Then it stops.
When users try to start IUCLID 6 a warning appears saying “the required port 4848 is currently in use”.
The technical explanation of the issue: IUCLID 6 Desktop installs a server on the client computer. When the client runs IUCLID 6 then the client application attempts to connect to the (locally installed) server using URL “localhost”. However because of some configuration issue the client’s request for “localhost” is redirected to your proxy instead of connecting locally.
This issue can be fixed by applying one of the solutions below. We recommend you to try to address this with the first solution under the title “Probable solution for the proxy issue”. If this solution for some reason does not work then you can try to apply the workaround described below. The workaround should always work but will cause automatic update notification of IUCLID 6 not to work.
If you have started with IUCLID 6 v1.0.2 or later then the configuration part described under “1) Probable solution for the proxy issue” is already there and you only need to bypass proxy for the local addresses. However if you have IUCLID 6 v1.0.0 or have started with this version and upgraded it later then you will have to enter all configuration as described below.
Probable solution for the proxy issue
Please check the proxy settings via IE or Chrome. Specifically in the LAN Settings check if the “Use a proxy server for your LAN...” is selected or not.
If the “Use a proxy server for your LAN...” options is checked, then please apply the following options:
a) Check the Bypass proxy server for local addresses
b) In the Exceptions panel set the following addresses 127.0.0.1;localhost;0.0.0.0
After that adapt the domain.xml from <glassfish_installation>\glassfish\domains\domain1\config:
a) Stop IUCLID 6
b) Open the folder <IUCLID6>\glassfish4\glassfish\domains\domain1\config
c) Make a backup copy of the configuration file domain.xml for backup. You can copy it to a temporary folder.
d) Edit the configuration file <IUCLID6>\glassfish4\glassfish\domains\domain1\config\domain.xml with an editor like Notepad++
e) Make sure the java.net.useSystemProxies is set to true (this is so by default but in work-round below it would be changed to false)
f) Set the address of jmx-connector to localhost instead of 0.0.0.0
g) Set the address of jms-host to localhost instead of 0.0.0.0
h) Add the following jvm parameter:
i) Save the configuration file.
j) Start IUCLID 6.
See the snippets from domain.xml below.
<admin-service system-jmx-connector-name="system" type="das-and-server">
<java-config classpath-suffix="" system-classpath="">
Workaround for the proxy issue
In order to have your instance of IUCLID 6 working regardless of the above steps, you can change the value of the property java.net.useSystemProxies to false. However this is not the best solution since as a consequence in the future you will not be informed by IUCLID 6 about available updates for the program.
a) Stop IUCLID 6.
b) Open the folder <IUCLID6>\glassfish4\glassfish\domains\domain1\config
c) Make a backup copy of domain.xml for backup. You can copy it to a temporary folder.
d) Edit <IUCLID6>\glassfish4\glassfish\domains\domain1\config\domain.xml with an editor like Notepad++
e) Find a line like this:
Change it to:
f) Save the configuration file <IUCLID6>\glassfish4\glassfish\domains\domain1\config\domain.xml
g) Start IUCLID 6.
2. Lock file issue
This issue can occur on the systems which were successfully installed. Users that had been using IUCLID 6 Desktop successfully suddenly discover that it would not start. After each subsequent attempt to start the program the following window opens.
Restart of the computer does not help. In the log file server.log there is the entry like this:
Caused by: java.lang.Exception: [B3087] : The broker has detected an active lock file:
This file indicates that there is another copy of the broker running
The lock file prevents IUCLID 6 to fully start but it leaves a running Java process hanging that keeps the port 4848 reserved.
To address this perform the following actions:
a) Make sure that you have backups of your IUCLID data stored in a safe location;
b) Terminate IUCLID 6 by opening the Task manager and killing the corresponding Java process. To make sure that the proper Java process is killed you can:
i) Expand Java (in Windows 10)
ii) Display the Command Line column (pre-Win 10: View -> Select Columns -> Command Line). In the Command line, the value should be
JAVA_HOME/java.exe -cp C:\iuclid6\glassfish4\glassfish\modules\glassfish.jar ...
Alternatively you can re-start your computer;
c) After IUCLID 6 is stopped, open the folder
and then delete the lock file;
- Warning: <IUCLID6> above stands for the IUCLID 6 installation folder, e.g. c:\iuclid6
d) Launch IUCLID 6.
Fixed in IUCLID 6 1.3.0 (28th April 2017)
A43. This bug was introduced since IUCLID 6 version 1.1.0. We have now updated the installation packages on the IUCLID 6 website to prevent this error from hapenning.
The solution we found can also be applied by the IUCLID server administrator on existing IUCLID 6 installation where the error is detected:
- On the IUCLID server, update the file ‘client.settings.properties’ under ‘<IUCLID server installation folder>\ glassfish4\glassfish\domains\domain1\config’. Add the following new lines:
- After the update the content of the file should be similar to the one below:
- Save the file and close it.
- If you start the IUCLID 6 client again and you log in, the issue should not appear anymore. There is no need to restart the IUCLID server.
The issue was only a user interface issue and has been fixed in the IUCLID installation packages with a configuration change. There is no need to download and reinstall IUCLID 6, applying the fix above is enough.
A47. The issue 'Failed to update document. The document is missing.' occurs in IUCLID6 v1.2.0 Server version if Instance Based Security (IBS) is disabled and a standard user tries to update a document created by another user. You will find more detailed instructions on how to solve this issue in this file (1 MB).
In case you would have the same issue with a Desktop version, please contact the Helpdesk.
Fixed in IUCLID 6 1.2.0 (31st January 2017)
A38. The issue can occur in some cases when formatted text is copied from programs such as word processing tools, to rich text fields in IUCLID 6.
The workaround currently available is the following:
- Prepare the text directly in IUCLID 6 or copy non-formatted text (e.g. from programs like Notepad or Notepad++).
- Format the text in IUCLID 6.
A fix has been included in the September service release of IUCLID 6 (version 1.1.0). The fix will address the copying of formatted text from the most used text formatting software. For less standard programs the issue might still occur and should be reported to the ECHA Helpdesk.
A42. This issue is caused by a glitch in the template file generating CSR chapter 8 “PBT AND vPvB ASSESSMENT” (more specifically: “18.104.22.168.3. Toxicity assessment”). A fix for this issue will be available in the next IUCLID release planned for end of January 2016.
In the meantime, you can apply the following workaround in IUCLID:
- Go to section “2.3 PBT assessment” and edit the available record(s) (the summaries do not need to be modified)
- In the record(s), go to the following text field: “Results of detailed PBT /vPvB assessment” -> “Toxicity” -> “Evidence on non-T properties” -> “EC10 or NOEC>=0.01 mg/L for marine / freshwater organisms (long-term toxicity)”
- Enter relevant text in this field. Or, in case this is not applicable, insert n/a for example.
- Save the record and try to generate the CSR again.
Fixed in IUCLID 6 1.1.0 (30th September 2016)
A36. Certain operations in IUCLID 5, particularly the import of endpoint study records via the clipboard, may have created corrupted references in the IUCLID 5 database. The corrupted references should be fixed before migration to IUCLID 6 in order for the application to work correctly. This is described in detail in the Migration manual.
If your IUCLID 5 database contains corrupted references but you still executed the migration to IUCLID 6, you will experience issues related to the datasets that contain corrupted references. This will not be immediately visible, but the following occurrences are indicative of such an issue:
- Running the Validation Assistant gives a generic error (with NullPointer exception).
- Creation of a dossier and export fails (with a NullPointer exception).
- If you try to open an endpoint study record that contains corrupted references, IUCLID 6 will freeze with an “Operation in Progress” message and you need to restart the application.
The following approaches can be adopted to be able to continue working with datasets containing corrupted references, depending on your situation.
This approach resolves the issue of corrupted references prior to migration and no later fix is therefore expected to be needed for the IUCLID 6 database. It is the recommended option whenever the IUCLID 6 database has not yet been taken into use.
1. Fix all the corrupted references in the IUCLID 5.6 database with the help of the Attachment references corrector tool, included in the IUCLID 6 migration tool.
- Execute the tool in SCAN_MODE.
- Check the reports (auto_corrected_raw_data…txt and user_action_required_raw_data…txt).
- Fix manually all that you can fix (e.g. you will not be able to fix corrupted references inside dossiers because they are read-only).
- Execute the tool in FIX_MODE.
For further information on how to do this, see chapter 1.1.2 of the Migration manual.
2. Re-execute the migration to an empty IUCLID 6 database.
This approach addresses a situation where the IUCLID 6 database contains data that was entered/edited after the migration from IUCLID 5, and thereby a fresh migration from IUCLID 5 is not a feasible option. The approach is designed to resolve the issue where a registrant needs to edit a limited number of datasets and create new dossiers for submission. For a full IUCLID 6 database correction, including correction of corrupted references inside existing dossiers, it is recommended to apply approach 3 below.
- Make sure that you have valid backups of your IUCLID 5.6 and IUCLID 6 data stored in a safe location
- In IUCLID 5.6, manually fix the corrupted references in the dataset you have problems with in IUCLID 6. Detailed step-by-step instructions on how to locate and manually fix the corrupted references are provided in an annex: Finding and fixing corrupted references in IUCLID 5. Note that if you use the IUCLID 5 Attachment references corrector tool to locate the corrupted references, it is essential that you only run it in SCAN_MODE. Running it in FIX_MODE will not update the modification history of the amended endpoint study records, and they will not be imported during step d) of these instructions.
- After all the corrupted references have been fixed in the dataset, export the dataset from IUCLID 5.6.
- Import the dataset in the IUCLID 6 database that you are working with. Select “If newer than existing” for the “Overwrite mode” (see screenshot below). This will ensure that all changes that you had later made to the corresponding IUCLID 6 dataset are kept, while the fixed endpoint study records that previously contained corrupted references will be imported and replaced in your dataset.
- Check that the data has been correctly imported in IUCLID 6, in particular that you can open the documents where you corrected corrupted references in IUCLID 5.
A IUCLID 6 database patch tool has been developed to resolve the issue in those cases where the user has already migrated data containing corrupt references to the IUCLID 6 database. This tool can be downloaded here.
A37. An issue has been identified in IUCLID 6 when a user tries to edit a rich text in a dataset that has been migrated from IUCLID 5. The issue affects fields which were plain text fields in IUCLID 5, but in IUCLID 6 were changed to store rich (formatted) text. A fix has been included in the September service release of IUCLID 6 (version 1.1.0). The fix addresses the problem of the text not displaying correctly, and will not require a re-migration of the data.
More concretely, the issue is related to the handling of rich text format tags in IUCLID 6 by the user interface. The information is correctly stored in the database, but it is not properly displayed in the user interface.
The problem manifests itself in that the entered information does not appear to be saved, copy-paste into the field does not seem to work, the formatting options of the field do not produce the expected result, or that even if the text seems to have disappeared from the field in the user interface, it appears during printing. As explained above, the information is in fact stored, but does not display correctly in the IUCLID 6 user interface.
Affected IUCLID 6 fields include:
- Section 6 – Ecotoxicological information (endpoint summary), fields ‘Explanations on the hazard conclusion’
- Section 7 – Toxicological information (endpoint summary), fields ‘Explanation for hazard conclusion’
- Section 4-7 endpoint summaries, field ‘Description of key information’
If, in the meantime, you need to edit a rich text field which was migrated from IUCLID 5 and encounter the above-described problems, the following work-around can be applied:
- First, make sure you have a back-up of the dataset by exporting it and storing it in a safe location.
- In the field where you observe a problem (or you expect to observe a problem, based on the above description of the issue), click inside the field and select all the field content using the key combination CTRL+A. To ensure that all content is selected it is important to do the selection using this key combination and not try to do it using the mouse.
- Using the key combination CTRL+C, copy the contents of the field and paste into a program such as Notepad, which converts it to non-formatted text.
- Delete the contents of the field. Save. This removes the additional tags in the field that confuse the user interface display.
- Copy and paste (CTRL+V) the text back to the field, and continue editing as needed. The content should be properly displayed from now on.
If you follow the above instructions in detail, and it does not resolve your problem, we would very much appreciate if you could provide us with more information to identify the source of your issue. More concretely, we would be interested in obtaining the dataset and, in the case your problem results after copy-paste of formatted information into the migrated field, a file of the data you were trying to paste into the field.
We would kindly ask you to re-create this issue and send us the following information:
- Which of the following did you observe:
- Copy-paste of formatted text did not work (field empty)
- Copy-paste of formatted text worked, but upon saving the field was empty
- Manual entry of text did not work (field empty)
- Manual entry of text worked, but upon saving the field was empty
- Other than above (please explain)
- What type of data did you use:
- Was the issue observed in a migrated dataset, i.e. a dataset that you had created in IUCLID 5 and migrated or imported into IUCLID 6?
- If yes, was the document (record, summary) where you observed the issue newly created in IUCLID 6, or were you editing a document that had been migrated from IUCLID 5?
- Which were the IUCLID 6 fields where the problem was observed?
- Further information:
- For copy-paste: What type of data was copied when the paste failed? If you could send us the source data of the failed copy-paste operation as a file it would be very helpful.
- For manual text entry: Did the inability to save typed text occur after you had attempted to first paste information into the field? Or was the field completely unused (no information had previously been stored there) when you typed the text?
- Finally, please send us a dataset where the problem happened, i.e. where copy-paste did not work and later saving emptied the type text (please indicate the section, name of record/summary and field where you experienced the problem). To avoid sharing large files, and potentially sections with confidential information, you can choose to export only a particular section of IUCLID or you can contact the ECHA Helpdesk for further instructions on sharing confidential information.