Troubleshooting startup issues with Developer Studio
When you start Developer Studio, you might encounter certain issues such as you cannot log in to Developer Studio 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 Developer Studio. Alternatively, you can create a BMC Support case.
- You get an error message related to the JRE while starting Developer Studio.
- You cannot import or export a .def file.
- You cannot log in to Developer Studio.
One or more users might experience the symptoms.
Perform the following steps to troubleshoot startup issues with Remedy Developer Studio:
|1.||Review the configuration.||Verify that the Java path in the devstudio.ini file is correct. For more information, see the knowledge article 000101704.|
|2.||Unlock the workspace.||If Developer Studio terminates abnormally, the workspace directory might get locked. If this occurs, restart Developer Studio to unlock the workspace and to select or create another workspace.|
|3.||Review the Developer Studio configuration.|
In the devstudio.ini file, verify that the following items are correct:
The following is a sample devstudio.ini file:
Enable Java debug logging for Developer Studio.
To know how to enable Java debug logging for Developer Studio, see Enabling Java debug logging for Remedy Developer Studio or see the knowledge article 000025307.
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:
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:
|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:
|When you start Developer Studio, you get ||On screen|
When you start Developer Studio, you get
Step 2 in the Resolution section