RTA Knowledge Base

Initial Steps to be followed:

Follow the instructions below, unless instructed otherwise follow the steps sequentially.

1. Is the installation media valid?

Verify that the correct installation media is being used. Sometimes the ISO image can become corrupted.

  • Verify the MD5 hash if necessary with somebody who has successfully installed by using the windows cmd line.
  • example: certutils -hashfile C:/Path/To/InstalledImage.iso md5

(please contact the hotline support team if you need a value to compare against)

2. How was the installation performed?

If the installation was performed using the individual product installers, try using the RTA-CAR common installer instead.

3. Did the RTA-CAR common installer report an error?

If the RTA-CAR common installer reports an error to the user then the first task is to determine which RTA-CAR component is reporting the error.

  • If no error is reported go to the section 6. ISOLAR-AB launching without any errors

4. Does running the individual component installer fix the issue?

Report an issue with the RTA-CAR common installer to the system team.

5. Is the component a plugin to ISOLAR-AB? (BSW, RTE-Plugin, OS-Plugin)

If the component is not a plugin then report the issue to the component development team.

Otherwise proceed to the next step.

6. Is ISOLAR-A/B launching without any errors?

If ISOLAR is launching without any errors proceed to the next step.

Otherwise proceed to troubleshooting 9. ISOLAR-AB start-up.

7. Is the plugin installed correctly?

Determine installed plugins by running "ISOLAR-AB_CLI.exe -noSplash -application org.eclipse.equinox.p2.director -listInstalledRoots -profile DefaultProfile"

  • Verify that the component plugin is in the list, then proceed to next step else:
  • If the component plugin is not in the list then refer to the plugin install logs from "C:\ETASData\configurations\*\configuration\*.log"
  • If the logs do not suggest a solution then refer the problem to the plugin team.


8. Are all required licenses available?

Check that all the licenses required for the complete RTA-CAR solution are available.

If the licenses are all available and the components are installed but the problem still persists then refer the issue to the system team.


9. Troubleshooting ISOLAR-AB start-up

Verify that ISOLAR-AB installed correctly. The installation log can be found in “C:\ProgramData\ETAS\SETUP\Logs”

Common reasons for installation failure:

  • Not enough space
  • No permission to write to the installation directory

Refer to the startup logs in the user workspace eg. “C:\ETASData\ISOLAR-AB\workspace\.metadata”

Try the configuration clean up script in "C:\Program Files\ETAS\ISOLAR-AB* \CleanUpConfig.bat”


10. Contact the Support Hotline

If after following the above steps and you are still facing installation issues then please contact the support hotline

Important

When contacting the support hotline please include as much detail as possible including all the log files mentioned in this document



Installer Issues Diagram

The above steps can be visualised in the following diagram:



Additional FAQs regarding Installation

Can the Installers be ran silently?

Yes, they have to be installed via their individual components via the command line. The arguments needed are as follows:

ToolArguments
ISOLAR-A/B/VerySilent /EULAAccepted
RTA-BSW/VerySilent /EULAAccepted
RTA-RTE/VerySilent /SuppressMsgBoxes /EULAAccepted
RTA-OS/VerySilent /SuppressMsgBoxes

What privileges should the installer be run with?

Ensure that the installer is ran with administration privileges.