PDS for OpenEdge doesn't start and the following error is recorded in the workspace's .log file: " The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.".

In another instance the following was found in the .log file in <workspace>.metadata:

!MESSAGE Warnings while parsing the key bindings from the 'org.eclipse.ui.commands' extension point
!MESSAGE Cannot bind to an undefined command: plug-in='com.openedge.pdt.oestudio', id='com.progress.tools.editor.scb'
!MESSAGE Bundle com.openedge.keybinding.hook not found.

In another instance the following was found in the .log file in <workspace>.metadata:
java.lang.IllegalStateException: BundleContext is no longer valid
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl.checkValid(BundleContextImpl.java:931)
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl.removeBundleListener(BundleContextImpl.java:303)
 at com.openedge.pdt.core.OECommonServicesPlugin$1.bundleChanged(OECommonServicesPlugin.java:157)
 

- Applied Service Pack on Windows 7 and other updates.
- PDS was working without problems before applying Windows patches.
- OpenEdge was uninstalled and reinstalled but that didn't help.
- PDS just hangs while starting but then it just dies and never opens. 
- First message in the log file might be: !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
- Adding -clean as a startup parameter to PDS for OpenEdge did not help.
- Adding -clearPersistedState as a startup parameter to PDS for OpenEdge did not help.

This might happen when:

• sometimes the computer is put into a hibernate state many times when the Eclipse is still working or
• resources get called too early before the instance of workspace can be created, or
• Eclipse did not shutdown correctly.

And Eclipse might hang or crash with the following messages (check <workspace>\.metadata\.log):

!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

Or the following messages may be contained in the .log file:
!MESSAGE Warnings while parsing the key bindings from the 'org.eclipse.ui.commands' extension point
​!MESSAGE Cannot bind to an undefined command: plug-in='com.openedge.pdt.oestudio', id='com.progress.tools.editor.scb'
!MESSAGE Bundle com.openedge.keybinding.hook not found.

 

 

There are different ways this problem can be resolved:

1. Rename <workspace>\.metadata\.plugins\org.eclipse.core.resources\.root\.indexes folder and restart Eclipse. 
2. Go to: \.metadata\.plugins\org.eclipse.core.resources and remove the file .snap. Or remove file: .metadata\.plugins\org.eclipse.core.resources\.projects\<project>\.markers.snap.
3. Rename <workspace>\.metadata\.plugins directory and restart PDS. If this solution is applied, all projects must to be imported and configure Workspace again.
4. Rename/remove .metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi file to restore the workspace to a working state .
   A new workbench.xmi file will be re-generated.
5. If nothing else addresses the issue, create a (new) clean workspace. Import the old project into the new workspace and reconfigure all settings/preferences in the new workspace.
   
   * Backup constantly any workspace and it's preferences. 

References to other Documentation:

Progress article(s):
 PDSOE getting to splash screen but crashes.
 How to migrate Progress Developer Studio for OpenEdge settings between Workspaces