Web Service MBO Sync Exceptions After an Interface Change

Problem: After changes are made to a Web service interface, you see sync exceptions and related errors in the client log. Server log errors may also indicate that Unwired Server did not recognize the value of HTTP Header SOAPAction: http://sybase.com/getPersonalKey.

Explanation: If changes are made to the Web service interface, you must make corresponding changes to the Web Service mobile business object (MBO).

Solution:
  1. Change the connection profile for the new WSDL.
  2. Re-create the MBO.
  3. Redeploy the MBO.
Note: Alternatively, change the connection profile for the new WSDL, and do a refresh to recreate the MBO.
Related tasks
No Data or Images Appear on the Device
Binding an MBO to a Database Fails
Structure MBOs Not Automatically Generated After Rebinding
Multilevel Insert Operation Fails
Related reference
Troubleshooting MBOs
Troubleshooting Improperly Designed Mobile Business Objects
Database MBO Fails on Execution
Search Errors and the RTRIM Function
Update Operation Fails
Relationship Error
SQL Statement Yields Unexpected Results
Warning Message When Creating Relationships
Synchronization Fails if Binary Attributes Have Unspecified Length