Troubleshooting startup issues with Developer Studio

When you start , you might encounter certain issues such as you cannot log in to or you get an error message related to the Java Runtime Environment (JRE). See the guidelines described here to obtain the appropriate log files and to resolve any startup issues with . Alternatively, you can create a BMC Support case.

Symptoms

You get an error message related to the JRE while starting .
You cannot import or export a .def file.
You cannot log in to .

Scope

One or more users might experience the symptoms.

Resolution

Perform the following steps to troubleshoot startup issues with :

Step	Task	Description
1.	Review the configuration.	Verify that the Java path in the devstudio.ini file is correct. For more information, see the knowledge article 000309625.
2.	Unlock the workspace.	If terminates abnormally, the workspace directory might get locked. If this occurs, restart to unlock the workspace and to select or create another workspace.
3.	Review the configuration.	In the devstudio.ini file, verify that the following items are correct: Java heap size and maximum metaspace size Java path for the -vm option The following is a sample devstudio.ini file: -clean -vm C:\Program Files\Java\<Java_Home_Folder>\bin\javaw.exe -vmargs -Xms512m -Xmx2048m -XX:PermSize=64M -XX:MaxPermSize=256M -XX:+UseCompressedOops -Xverify:none -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+CMSIncrementalPacing
4.	Enable logs.	Enable Java debug logging for . To know how to enable Java debug logging for , see Enabling-Java-debug-logging-for-Developer-Studio or see the knowledge article 000210649. Note: Enabling Java debug logging creates the javaapi.log file.
5.	Collect the logs.	Review the data in the log file to identify any symptoms or error messages. The log file is located at: Users\Administrator\DeveloperStudio\workspace\.metadata. Copy the log file to another location and then review it so that it does not get overwritten. The log file might be huge in size depending upon the volume. See the table to troubleshoot issues based on the symptoms and error messages.
6.	Create a BMC Support case.	Collect and send logs and detailed information when creating a case with BMC Support: Provide the following information as part of your case: Name of the user who faced a startup issue with Login information Time when the issue occurred Any error messages received Include the devstudio.ini file from the \BMC Software\ARSystem\DeveloperStudio folder. Collect the following logs: arerror.log javaapi.log (See step 4 in this table.) Log file from the Users\Administrator\DeveloperStudio\workspace\.metadata folder. Attach the log file to your case. You can attach a log file of size up to 2 GB. You can also upload the file on FTP. For more information, see Steps to send logs, files, screenshots, etc to BMC Support for a Remedy Product related case.
7.	Analyze the log file.	You can review the log file to identify error messages or behaviors. See the table to identify the possible symptoms and solutions.

After you determine a specific symptom or error message, use the following table to identify the solution:

Symptom	Location	Action	Reference
When you start , you get ERROR (623): Authentication failed.	On screen	Verify that the user has access to and the password entered is correct. On the Login page of , click Edit Server List and then verify the server and port information.	N/A
When you start , you get A Java Runtime Environment Error, No Java Virtual machine was found.	On screen	Edit the devstudio.ini file available in the same folder as that of the DevStudio.exe file, typically C:\ProgramFiles\BMCSoftware\ARSystem\DeveloperStudio Verify the Java path in the devstudio.ini file. -vm C:\Program Files\Java\<Java_Home_Folder>\bin\javaw.exe	Step 2 in the Resolution section

Troubleshooting startup issues with Developer Studio

Symptoms

Scope

Resolution

Related topic

On this page