The Client Object API supports exception classes for queries and for the messaging client.
    
            
            
            - Sybase.Mobile.ApplicationRuntimeException  – thrown when a call to start the connection, register the application, or
                        unregister the application cannot be completed due to an error. 
 - Sybase.Mobile.ConnectionPropertyException  – thrown when a call to start the connection, register the application, or
                        unregister the application cannot be completed due to an error in a
                        connection property value or application identifier 
 - Sybase.Mobile.ApplicationTimeoutException – thrown when a call to start the connection, register the application, or
                        unregister the application times out. 
 - Sybase.Persistence.LoginRequiredException  – thrown when the client application does not login to the server. 
 - Sybase.Persistence.NoSuchOperationException  – thrown when trying to access operation metadata that does not exist in class
                        metadata. 
 - Sybase.Persistence.NoSuchAttributeException  – thrown when trying to access an attribute that does not
                        exist in class or entity metadata and thrown by a dynamic query method (such
                        as ExecuteQuery) if the Query passed in selects for an attribute that does
                        not exist in the MBO queried. 
 - Sybase.Persistence.ObjectNotFoundException  – thrown when trying to load an MBO that is not inside the local database. 
                    
 - Sybase.Persistence.ObjectNotSavedException  – thrown when a BigBinary or BigString method is called that requires the
                        object to already exist in the database.
 - Sybase.Persistence.PersistenceException  – thrown when trying to access the local database. 
 - Sybase.Persistence.ProtocolException  – thrown when an exception occurs during protocol version mismatch. 
 - Sybase.Persistence.StreamNotOpenException  – thrown when a BigBinary or BigString method is called that requires the
                        object to be open. 
 - Sybase.Persistence.StreamNotClosedException  – thrown when a BigBinary or BigString method is called that requires the
                        object to not be open. 
 - Sybase.Persistence.SynchronizeException  – thrown when an error occurs during synchronization. 
 - Sybase.Persistence.SynchronizeRequiredException  – thrown when synchronization is needed. 
 - Sybase.Persistence.WriteAppendOnlyException  – thrown if a BigBinary or BigString method is called that writes to the
                        middle of a value where only appending is allowed by the underlying
                        database. 
 - Sybase.Persistence.WriteOverLengthException  – thrown if the platform requires the length to be predetermined before write
                        and a BigBinary or BigString method is called that writes past the
                        predetermined length.