Cannot Start Unwired WorkSpace After Modifying Plugins

Problem: After applying private patches, temporary fixes, or manually changing plugin contents, Unwired WorkSpace fails to start.

If Unwired WorkSpace fails to start in any of these scenarios, you may have a corrupt p2 and/or configuration folder under <UnwiredPlatform_InstallDir>\UnwiredPlatform\Eclipse.

Solution: The installation program saves clean p2 and configuration folders for recovery purposes. Follow these steps to recover corrupt p2 and configuration folders:
  1. Ensure Unwired WorkSpace is shut down.
  2. Delete the p2 and configuration folders under <UnwiredPlatform_InstallDir>\UnwiredPlatform\Eclipse.
  3. Unzip the clean Eclipse3.7_p2_configuration.zip file, located in <UnwiredPlatform_InstallDir>\UnwiredPlatform\Eclipse after installation into the <UnwiredPlatform_InstallDir>\UnwiredPlatform\Eclipse directory.
  4. Restart Unwired WorkSpace.
Parent topic: Troubleshoot Mobile Business Object Development
Related concepts
AutoCommit Option for JDBC MBOs Using an ASE Data Source
Troubleshoot Code Generation
Related tasks
Unwired WorkSpace Crashes When Previewing or Test Executing Large Amounts of Data
Cannot Access Sample Database After Switching Network Types
Data Source Connection Fails After Installing to a New Directory
Attribute Length Set Incorrectly for Operation and Load Arguments
Related reference
JDBC Connection Errors
Mobile Business Object Errors
Preview Errors for a Web Service Mobile Business Object with date/time Types
Deployment and Code Generation Errors For MBOs That Use Large Datatypes
Deploying to Unwired Server Fails
Deploying to Unwired Server in a Cluster Fails
Input Parameters Fail to Generate for Complex Data Sources