Cannot Start Unwired WorkSpace After Upgrade

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 configuration folders under <SUP Installation Root>\UnwiredPlatform\Eclipse.

Solution: The installation program saves clean p2 and configuration folders for recovery purposes. Follow these steps to recover a corrupted p2 and/or configuration folder:
  1. Ensure Unwired WorkSpace is shut down.
  2. Delete the p2 and configuration folders under <SUP Installation Root>\UnwiredPlatform\Eclipse.
  3. Unzip the clean p2 and configuration zip file (See the Installation Guide for zip file location) under <SUPInstallation Root>\UnwiredPlatform\Eclipse.
  4. Restart Unwired WorkSpace.
Related concepts
AutoCommit Option in JDBC Attributes or Operations
Related tasks
Unwired WorkSpace Crashes When Previewing or Test Executing Large Amounts of Data
Cannot Access sampledb
Cannot Access Sample Database After Switching Network Types
Data Source Connection Fails After Installing to a New Directory
Related reference
MS SQL Server Connection Errors
Mobile Business Object Errors
Preview Errors for a Web Service Mobile Business Object
Compiler Errors When Deploying Device Applications
Deploying to Unwired Server Fails
Deploying to Unwired Server in a Cluster Fails
Data Truncation for Attributes without Explicit Length
Input Parameters Fail to Generate for Complex Data Sources
Client Device Database Performance Issues after Primary Key Changed to Composite