Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 764 | "Server not found and unable to automatically start" |
|---|---|
Constant | UNABLE_TO_CONNECT_OR_START |
SAP Sybase Error Number | 2410 |
SQL State | 08W55 |
SQL Code | -764L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | The client could not connect to a server, and was unable to automatically start a server. The automatic start may have failed because no database file was specified. |
| Error 765 | "Synchronization message type '%1' not found" |
|---|---|
Constant | NOT_SYNC_TYPE |
SAP Sybase Error Number | 2411 |
SQL State | 5RW11 |
SQL Code | -765L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of synchronization message type. |
Probable Cause | You referred to a synchronization message type that is not defined in this database. |
| Error 766 | "View references '%1', which is a temporary object. Views can only refer to permanent objects" |
|---|---|
Constant | VIEW_OVER_TEMP_OBJECT |
SAP Sybase Error Number | 2413 |
SQL State | 42U00 |
SQL Code | -766L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Temporary object name. |
Probable Cause | Views must refer only to permanent objects, not to temporary objects such as local temporary tables. |
| Error 767 | "Cannot find synchronization subscription with the name '%1'" |
|---|---|
Constant | SYNCHRONIZATION_NOT_FOUND |
SAP Sybase Error Number | 2414 |
SQL State | 5RW12 |
SQL Code | -767L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the subscription. |
Probable Cause | You misspelled the name of a synchronization subscription or you did not qualify it correctly with a user name. |
| Error 768 | "Cannot subscribe to '%1'" |
|---|---|
Constant | CANNOT_SUBSCRIBE |
SAP Sybase Error Number | 2415 |
SQL State | 5RW13 |
SQL Code | -768L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the publication. |
Probable Cause | Some publications cannot be subscribed to, such as a synchronization publication. |
| Error 769 | "Cannot modify synchronization entry using ALTER PUBLICATION" |
|---|---|
Constant | CANNOT_MODIFY_SYNC_AS_PUB |
SAP Sybase Error Number | 2416 |
SQL State | 5RW14 |
SQL Code | -769L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Probable Cause | You attempted to modify a synchronization entry using an ALTER PUBLICATION statement. |
| Error 770 | "Cannot modify publication entry using ALTER SYNCHRONIZATION" |
|---|---|
Constant | CANNOT_MODIFY_PUB_AS_SYNC |
SAP Sybase Error Number | 2417 |
SQL State | 5RW15 |
SQL Code | -770L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Probable Cause | You attempted to modify a publication entry using an ALTER SYNCHRONIZATION statement. |
| Error 771 | "Event '%1' not found" |
|---|---|
Constant | EVENT_NOT_FOUND |
SAP Sybase Error Number | 2418 |
SQL State | WE001 |
SQL Code | -771L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the event that could not be found. |
Probable Cause | You have attempted to reference an event with a name that does not exist in the database. |
| Error 772 | "Event '%1' already exists" |
|---|---|
Constant | EVENT_ALREADY_EXISTS |
SAP Sybase Error Number | 2419 |
SQL State | WE002 |
SQL Code | -772L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the event that already exists. |
Probable Cause | You have attempted to create an event with a name that already exists in the database. |
| Error 773 | "Schedule '%1' for event '%2' not found" |
|---|---|
Constant | SCHEDULE_NOT_FOUND |
SAP Sybase Error Number | 2420 |
SQL State | WE003 |
SQL Code | -773L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the schedule that could not be found. |
Parameter 2 | Name of the event being scheduled. |
Probable Cause | You have attempted to reference a schedule with a name that does not exist in the database for the named event. |
| Error 774 | "Schedule '%1' for event '%2' already exists" |
|---|---|
Constant | SCHEDULE_ALREADY_EXISTS |
SAP Sybase Error Number | 2421 |
SQL State | WE004 |
SQL Code | -774L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the schedule that already exists. |
Parameter 2 | Name of the event being scheduled. |
Probable Cause | You have attempted to create a schedule with a name that already exists in the database for the named event. |
| Error 777 | "Cannot synchronize table '%1' since it does not have a primary key" |
|---|---|
Constant | CANNOT_SYNC_TABLE_WITHOUT_PK |
SAP Sybase Error Number | 2424 |
SQL State | 5RW16 |
SQL Code | -777L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the table. |
Probable Cause | Tables being synchronized must contain a primary key. |
| Error 778 | "Must include primary key for table '%1' in the synchronization" |
|---|---|
Constant | PK_NOT_IN_SYNC_ARTICLE |
SAP Sybase Error Number | 2425 |
SQL State | 5RW17 |
SQL Code | -778L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the table. |
Probable Cause | The primary key of the table must be included in the synchronization entry. |
| Error 779 | "Cannot create synchronization entry for table '%1' with BLOB primary key" |
|---|---|
Constant | BLOB_IN_SYNC_TABLE_PK |
SAP Sybase Error Number | 2426 |
SQL State | 5RW18 |
SQL Code | -779L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the table. |
Probable Cause | You attempted to create a synchronization entry on a table with a BLOB primary key. |
| Error 780 | "Cannot update primary key for table '%1' involved in a publication" |
|---|---|
Constant | ARTICLE_PK_CANNOT_BE_UPDATED |
SAP Sybase Error Number | 2427 |
SQL State | 5RW19 |
SQL Code | -780L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the table. |
Probable Cause | The primary key of a table involved in a publication cannot be updated. The prevent_article_pkey_update database option can be set to Off to allow updates to the primary key of the table involved in the publication. |
| Error 782 | "Cannot register '%1' since another exclusive instance is running" |
|---|---|
Constant | SAME_EXCLUSIVE_APP_RUNNING |
SAP Sybase Error Number | 2429 |
SQL State | 5RW21 |
SQL Code | -782L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the application. |
Probable Cause | You attempted to start an application, but another exclusive instance of the same application is already registered. |
| Error 783 | "Cannot register another '%1' as an exclusive application" |
|---|---|
Constant | SAME_APP_RUNNING |
SAP Sybase Error Number | 2430 |
SQL State | 5RW22 |
SQL Code | -783L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the application. |
Probable Cause | You attempted to register an exclusive application but another instance of the same application is already registered. |
| Error 784 | "Cannot register connection because of invalid application cookie" |
|---|---|
Constant | CANNOT_REG_CONN |
SAP Sybase Error Number | 2431 |
SQL State | 5RW23 |
SQL Code | -784L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Probable Cause | Application registration cannot be found for the given cookie. |
| Error 785 | "Cannot deregister application because of invalid cookie" |
|---|---|
Constant | DEREG_APP_NOT_FOUND |
SAP Sybase Error Number | 2432 |
SQL State | 5RW24 |
SQL Code | -785L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Probable Cause | The application has not been registered successfully or it was previously deregistered. |
| Error 786 | "Cannot deregister '%1' since active registered connection exists" |
|---|---|
Constant | DEREG_APP_IN_USE |
SAP Sybase Error Number | 2433 |
SQL State | 5RW25 |
SQL Code | -786L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the application. |
Probable Cause | You attempted to deregister an application while there are still active connections registered to that application. |