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 |
|---|---|---|---|---|---|
| WW127 | Error | 2988 | -1299L | "Drop multiplex server is allowed only in a multiplex setup." | Drop multiplex server is allowed only in a multiplex setup. Click here for a list of possible parameters and odbc states. |
| WW128 | Error | 2989 | -1300L | "Cannot add first multiplex server with excluded status." | Users are not allowed to add the first multiplex server with status excluded. Click here for a list of possible parameters and odbc states. |
| WW129 | Error | 2990 | -1301L | "Cannot create multiplex server with role coordinator." | Users are not allowed to create a multiplex server with role as coordinator. Click here for a list of possible parameters and odbc states. |
| WW130 | Error | 2995 | -1307L | "Database mirroring options are not supported for this database" | The current database does not have catalog support for database mirroring servers and options. To use this feature, upgrade your database to the most recent version. Click here for a list of possible parameters and odbc states. |
| WW131 | Error | 2996 | -1308L | "Mirror server \"%1\" not found" | The named mirror server was not found in the database. Click here for a list of possible parameters and odbc states. |
| WW132 | Error | 2997 | -1309L | "Mirror server \"%1\" already exists" | An attempt was made to create a mirror server that already exists in the database. Click here for a list of possible parameters and odbc states. |
| WW133 | Error | 2998 | -1310L | "Mirror server \"%1\" is referenced by another server" | An attempt was made to drop a mirror server that is referenced by another mirror server in the database. Click here for a list of possible parameters and odbc states. |
| WW134 | Error | 2999 | -1311L | "Principal mirror servers are already defined" | An attempt was made to create a mirror server without a parent server, but two principal mirror servers are already defined in the database. Click here for a list of possible parameters and odbc states. |
| WW135 | Error | 3000 | -1312L | "Mirror server \"%1\" is not a valid parent server" | An attempt was made to define a parent for a mirror server that would result in a cycle. Click here for a list of possible parameters and odbc states. |
| WW136 | Error | 3001 | -1314L | "Cannot force failover when current server is marked as preferred" | An attempt was made to execute ALTER DATABASE SET PARTNER FAILOVER but the current server is marked as preferred. Attempting to force a failover in this situation is not allowed. Click here for a list of possible parameters and odbc states. |
| WW137 | Error | 3002 | -1319L | "Synchronization schema changes and script versions are not supported for this database" | The current database does not have catalog support for synchronization schema changes and script versions. To use this feature, upgrade your database to the most recent version. Click here for a list of possible parameters and odbc states. |
| WW138 | Error | 3003 | -1325L | "Column subset for table '%1' in publication '%2' does not match that specified in publication '%3'" | The columns included for a table must be identical for all subscribed publications which reference the table. Click here for a list of possible parameters and odbc states. |
| WW139 | Error | 3004 | -1321L | "Table or view '%1' is not valid for use with this statement" | The named table or view cannot be used with this statement. For example, the statement may not allow temporary tables or views. Click here for a list of possible parameters and odbc states. |
| WW140 | Error | 3005 | -1322L | "A synchronization schema change is already in progress" | A START SYNCHRONIZATION SCHEMA CHANGE statement is already in progress. Click here for a list of possible parameters and odbc states. |
| WW141 | Error | 3006 | -1323L | "Subscription to publication '%1' for '%2' omitted from statement" | A START SYNCHRONIZATION SCHEMA CHANGE statement lists a table that will be modified, but a subscription which refers to that table was omitted from the statement. Click here for a list of possible parameters and odbc states. |
| WW142 | Error | 3007 | -1324L | "Connection is not allowed to have table locks when executing this statement" | An attempt was made to execute a statement by a connection that is holding table locks. Because the statement could release all locks, including those held before the statement started, the locks must be released before the statement can be executed. Click here for a list of possible parameters and odbc states. |
| WW143 | Error | 3010 | -1328L | "Table '%1' must synchronize to be in publication '%2'" | A publication cannot contain a table with a SYNCHRONIZE OFF constraint; all tables in a publication must synchronize. You attempted to add a table with a SYNCHRONIZE OFF constraint to a publication, or to alter a table to use SYNCHRONIZE OFF when the table is already in a publication. Click here for a list of possible parameters and odbc states. |
| WW144 | Error | 3012 | -1332L | "Feature '%1' is unknown or invalid" | You attempted to lock or unlock an unknown feature. Click here for a list of possible parameters and odbc states. |
| WW145 | Error | 3013 | -1333L | "Feature '%1' was not locked by this connection" | You attempted to unlock a feature that was not previously locked by this connection. Click here for a list of possible parameters and odbc states. |
| WW146 | Error | 3014 | -1334L | "Feature '%1' is locked by another connection" | You attempted to use a feature that was previously locked by another connection. Click here for a list of possible parameters and odbc states. |