Messages 57W05 through 5RW19

Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.

SQL State Msg Type Number SQL Code Message Possible Cause
57W05 Error 2910 -1231L "Statement timed out: '%1!s!'" The statement failed because it did not complete within the allotted or specified time.

Click here for a list of possible parameters and odbc states.

5RW01 Error 2155 -280L "Publication '%1' not found" You misspelled the name of a publication, or you did not qualify a publication name with a user name.

Click here for a list of possible parameters and odbc states.

5RW02 Error 2156 -281L "Table '%1' has publications" You attempted to drop a table that has publications defined.

Click here for a list of possible parameters and odbc states.

5RW03 Error 2157 -282L "Subscription to '%1' for '%2' already exists" You attempted to create a subscription that already exists.

Click here for a list of possible parameters and odbc states.

5RW04 Error 2158 -283L "Subscription to '%1' for '%2' not found" You attempted to drop, start, or synchronize a subscription that does not exist.

Click here for a list of possible parameters and odbc states.

5RW05 Error 2159 -284L "User '%1' is already the publisher for this database" You attempted to GRANT PUBLISH to a user ID, when a publisher already exists.

Click here for a list of possible parameters and odbc states.

5RW06 Error 2160 -285L "User '%1' is not a remote user for this database" You attempted to execute a CREATE SUBSCRIPTION or PASSTHROUGH for a user that is not a remote user of this database. You must GRANT REMOTE or GRANT CONSOLIDATE for this user before proceeding with this operation.

Click here for a list of possible parameters and odbc states.

5RW07 Error 2161 -286L "Remote message type '%1' not found" You referred to a remote message type that is not defined in this database. Use CREATE REMOTE TYPE to define remote message types.

Click here for a list of possible parameters and odbc states.

5RW08 Error 2162 -287L "Passthrough statement inconsistent with current passthrough" Passthrough is additive, in that subsequent PASSTHROUGH statements add to the list of users receiving passthrough. The PASSTHROUGH statements must all be PASSTHROUGH ONLY or none should be PASSTHROUGH ONLY.

Click here for a list of possible parameters and odbc states.

5RW09 Error 2163 -288L "Remote statement failed" This SQLSTATE can be signaled within a trigger to prevent the SQL Remote Message Agent (dbremote) from displaying an error message in the output. This exception will only occur when a trigger or procedure signals it. This is useful for ignoring replication errors that are permitted by design.

Click here for a list of possible parameters and odbc states.

5RW10 Error 2403 -289L "Multiple consolidated users cannot be defined" You attempted to grant consolidated permissions when your database already has a consolidated user, or attempted to grant consolidated permissions to multiple users in a single statement.

Click here for a list of possible parameters and odbc states.

5RW11 Error 2411 -765L "Synchronization message type '%1' not found" You referred to a synchronization message type that is not defined in this database.

Click here for a list of possible parameters and odbc states.

5RW12 Error 2414 -767L "Cannot find synchronization subscription with the name '%1'" You misspelled the name of a synchronization subscription or you did not qualify it correctly with a user name.

Click here for a list of possible parameters and odbc states.

5RW13 Error 2415 -768L "Cannot subscribe to '%1'" Some publications cannot be subscribed to, such as a synchronization publication.

Click here for a list of possible parameters and odbc states.

5RW14 Error 2416 -769L "Cannot modify synchronization entry using ALTER PUBLICATION" You attempted to modify a synchronization entry using an ALTER PUBLICATION statement.

Click here for a list of possible parameters and odbc states.

5RW15 Error 2417 -770L "Cannot modify publication entry using ALTER SYNCHRONIZATION" You attempted to modify a publication entry using an ALTER SYNCHRONIZATION statement.

Click here for a list of possible parameters and odbc states.

5RW16 Error 2424 -777L "Cannot synchronize table '%1' since it does not have a primary key" Tables being synchronized must contain a primary key.

Click here for a list of possible parameters and odbc states.

5RW17 Error 2425 -778L "Must include primary key for table '%1' in the synchronization" The primary key of the table must be included in the synchronization entry.

Click here for a list of possible parameters and odbc states.

5RW18 Error 2426 -779L "Cannot create synchronization entry for table '%1' with BLOB primary key" You attempted to create a synchronization entry on a table with a BLOB primary key.

Click here for a list of possible parameters and odbc states.

5RW19 Error 2427 -780L "Cannot update primary key for table '%1' involved in a publication" 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.

Click here for a list of possible parameters and odbc states.


Created November 10, 2011. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com