Use this section to diagnose and resolve common installation, update, run time, and uninstallation issues.

Symptom Likely cause Resolution
Eclipse does not start after installation or upgrade. The plugin cache is stale or a file conflict exists. Restart Eclipse with the -clean option and use Eclipse artifact cleanup. If residual files remain and continue to cause problems, collect the Eclipse installation details and error log before contacting Progress Support.
Progress Developer Studio for OpenEdge (Developer Studio) does not appear in Install New Software. Architect_Repo might not be added correctly, or the repository is incomplete or corrupted. Add Architect_Repo again using Help > Install New Software > Add > Local. Use the already extracted Architect_Repo supplied by the correct OpenEdge installer.
Installation fails with a dependency error. The Eclipse version or dependency repositories are not compatible with the Developer Studio release. Verify that Eclipse 4.38, 4.39, or 4.40 and Java 21 are installed. Confirm that the matching Eclipse release and Eclipse Orbit repositories are configured, or that the approved offline dependency arrangement is available.
Eclipse displays Unable to locate OpenEdge 13.1 installation. No supported DLC is installed or the supported DLC was removed after installation. Install or restore OpenEdge 13.1, confirm the DLC configuration, and restart Eclipse.
OpenEdge project wizards or ABL options are missing. The OpenEdge Editor perspective is not active. Switch to Window > Perspective > Open Perspective > Other > OpenEdge Editor.
The Class Browser is unavailable in Eclipse 4.38, 4.39, and 4.40. Microsoft Edge WebView2 Runtime is not installed. Install the required Microsoft Edge WebView2 run time separately.
Progress-specific keyboard shortcuts do not work. Progress Scheme is not selected. Open Window > Preferences > General > Keys and select Progress Scheme.
Developer Studio menus or views are available after uninstalling it. Residual plugin files remain in the Eclipse plugins folder. Restart Eclipse with -clean. If needed, remove leftover files from the plugins and features directories after Eclipse is closed.
Eclipse crashes on startup with a JVM error, after switching to JDK 21. A third-party agent is injecting incompatible JVM options. Remove or update the conflicting tool and check JAVA_TOOL_OPTIONS and _JAVA_OPTIONS for incompatible flags.
The update is not detected after adding a newer repository. The old site entry is still registered or Eclipse is resolving from a cached site. Remove the old site entry from Help > Install New Software > Manage and add the newer Feature Repository.
Installation reports missing plugins or unresolved dependencies, after Architect_Repo is added into Eclipse. The Eclipse release update site or its corresponding Eclipse Orbit update site is missing, configured incorrectly, or multiple release and Orbit site pairs are enabled. Before installing from Architect_Repo, configure the Eclipse release update site and the corresponding Eclipse Orbit update site for the installed Eclipse version. Enable only that matching release and Orbit pair to prevent split-package issues, and then retry the installation.
A prompt warns that the software contains unsigned content. The Developer Studio bundles are not signed with a public certificate. Verify that Architect_Repo was obtained from the approved OpenEdge installer. If Eclipse displays the unsigned-content prompt, review the listed content and select the trust option required by the security policy of your organization.