Problem: After applying private patches, temporary fixes, or manually
changing plugin contents, SAP Mobile WorkSpace fails to start.
If SAP Mobile WorkSpace fails to start in any of
these scenarios, you may have a corrupt p2 and/or
configuration folder under SMP_HOME\Eclipse.
Solution: Follow the instructions of the temporary fix or private patch, and
extract the clean
p2 and
configuration
folders from the patch for recovery purposes. Follow these steps to recover from
corrupt
p2 and
configuration folders:
- Ensure SAP Mobile WorkSpace is
shut down.
- Delete the p2 and
configuration folders under SMP_HOME\Eclipse.
- Unzip the clean Eclipse p2 and
configuration folders from the
temporary fix or private patch, and copy these folders to SMP_HOME\MobileSDKxx\Eclipse\
.
- Restart SAP Mobile WorkSpace.