Deploying to Unwired Server in a Cluster Fails

Problem: Deployment fails when you deploy a mobile business object (MBO) to Unwired Server in a cluster.

Explanation: When you deploy a package into a Sybase Unwired Platform cluster, you must be connected to the Unwired Server designated as the primary server in the cluster. If not, deployment fails and you see a message similar to following in the server logs:

YYYY-MM-DD HH:MM:SS.SSS WARN    MMS          Thread-466
[com.sybase.sup.server.SUPDomain] On Non primary servers, you could not
execute createDsyncDataZip()
java.lang.Exception: Current server is not primary, request rejected.

Solution: Set up a connection profile to the server that has become the primary, and deploy using that connection. See Sybase Unwired WorkSpace - Mobile Business Object Development > Configure > Configure - Eclipse Development Environment > Creating a Sybase Unwired Server Connection Profile for how to create a new Sybase Unwired Server connection profile.

Related concepts
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 Parameters
Related reference
JDBC 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
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