Startup issues

When the Document Studio or Launcher clients do not start, review these issues and troubleshooting suggestions.

Verifying the Engineering Publishing application files
If you do not receive a specific error as to why the Document Studio or Launcher client is not starting, you can complete these steps to verify that the installation completed successfully.
Verifying the RPE_HOME environment variable
If you find that the Document Studio or Launcher applications are not opening files correctly, verify that the RPE_HOME environment variable is set to the correct path.
Verifying the TELELOGIC_LICENSE_FILE environment variable
Ensure that the TELELOGIC_LICENSE_FILE environment variable is set to the correct path.
Fixing Java Virtual Machine (JVM) cannot be created errors
If the Document Studio or the Launcher applications display the error Failed to create the Java Virtual Machine on startup, you can adjust the Java™ heap parameters in the product configuration files to improve performance.
Fixing an error 400 after logging into Publishing Document Builder
If the web browser displays an Error 400: RPENG license checkout failed after logging in to Publishing Document Builder, your application server might be configured to support the Transport Layer Security (TLS) 1.2 protocol. You must configure extra server settings to run Publishing Document Builder with an application server in TLS 1.2 mode.

Parent topic: Troubleshooting and support for Engineering Publishing