Troubleshoot
Use troubleshooting tips to resolve common
issues. Topics provide information to help isolate and correct
problems.
- Troubleshooting Data Connection Errors
Problem: When you create a data connection and select IBM DB2.IDS and U2 servers as the data source and then drag and drop a table onto the Mobile Application Diagram to create a mobile business object, an error displays from the IBM .NET driver stating that no data connection was defined when you click the Validate Syntax button.
- Troubleshooting Deployment Errors
Problem: Deploying to a server fails when both attribute mapping and parameter mapping are identical in a mobile business object relationship.
- Troubleshooting a Mobile Business Object Created From a Web Service With an Optional Parameter
Problem: If you create a mobile business object from a Web service that has an optional parameter, a validation error occurs if you do not enter a value for the optional parameter.
- Troubleshooting a Mobile Business Object Created From an Oracle Table With bfile and Long Data Types
Problem: Data cannot be retrieved from the backend database when certain mobile business objects, which were created from an Oracle table with bfile and long data types, are deployed.
- Troubleshooting a Mobile Business Object Created Using SQL
Problem: SCHLOSS fails to parse isnull() with arguments and generates a syntax error.
- Troubleshooting a Web Service Mobile Business Object After an Interface Change
After creating a Web Service connection profile and defining a mobile business object (MBO) from that connection profile, if there are changes to the Web Service interface itself, for example, a function parameter’s data type or a parameter is removed or added, you must delete the xsd and generated subdirectories from Unwired WorkSpace and recreate any MBO based on the changed Web Service data source.
- Troubleshooting Mobile Business Object Creation Using a SQL Server OLEDB or Native Driver
Problem: If connect to a SQL Server OLEDB or a SQL Server Native driver and are creating a mobile business object (MBO) from a view based on a complex SQL statement, the generated SQL statement will not be not correct.
- Troubleshooting Insert Operations Using OLEDB With ASE
Problem: If you connect to ASE using OLEDB, select query is not auto-generated after the insert query when you create insert operations for the mobile business object even though the primary key of the table is auto_increment.
- Troubleshooting ODBC Driver Errors
Problem: If Sybase Unwired Platform is installed and you then install a standalone version of SQL Anywhere 10 and uninstall SQL Anywhere 10, after the standalone version of SQL Anywhere 10 is installed, the registry may be changed, so the ODBC driver cannot be found. An error displays when you try to use the ODBC driver.
- Troubleshooting Opening a Generated Form
Problem: Opening a generated form causes a stack trace error.
- Troubleshooting SAP Errors
Problem: After creating an SAP connection profile, an error displays when trying to either connect to or ping SAP.
- Troubleshooting a SQL Statement Containing a Null
Problem: If you use a database other than Sybase, when there is a comparison operator in a definition SQL statement followed by a parameter, for example: "select * from ... where columnA = '@OP["parameterA"=""]'", and the default value of this parameter is set to Null, you do not get the expected results in runtime.
- Troubleshooting SQL Generated Using an Oracle ODBC Connection
Problem: If you create an operation by dragging and dropping a stored procedure from the Service Explorer onto a mobile business object, if you are using an Oracle ODBC connection, the default SQL will be missing parameters.
- Troubleshooting the UDDI Server
Problem: The wizard used to add a Web service cannot find the Sybase UDDI server or Web services published on the Sybase UDDI server.
- Validation Rules and Error Messages
Understanding and resolving Unwired WorkSpace validation errors helps ensure that mobile business objects (and the device applications that interact with them) perform as expected in an enterprise environment.
Created September 17, 2009. Send feedback on this help topic to Sybase Technical Publications:
pubs@sybase.com