Export (0) Print
Expand All

Errors 28000 - 29999

Error

Severity

Event logged

Description (message text)

28000

16

No

The decrypted session key has an unexpected size.

28001

16

No

A corrupted message has been received. It contains invalid flags. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.

28002

16

No

Cannot start service broker manager. Operating system error: %ls.

28003

16

No

An internal service broker error occurred. Operating system error: %ls.

28004

16

No

This message could not be delivered because the '%S_MSG' action cannot be performed in the '%.*ls' state.

28005

16

No

An exception occurred while enqueueing a message in the target queue. Error: %d, State: %d. %.*ls

28006

14

No

User does not have permission to %S_MSG the conversation '%.*ls' in state '%.*ls'. Only members of the sysadmin fixed server role and the db_owner fixed database role have this permission.

28007

16

No

A corrupted message has been received. The highest seen message number must be greater than the acknowledged message number. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.

28008

16

No

The conversation handle '{%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}' is invalid.

28009

16

No

The crypto API has detected bad data while trying to perform a decryption operation.

28010

16

No

This message could not be delivered because it contains an invalid acknowledged message number. Highest expected message number: %I64d. Acknowledged message number: %I64d, fragment number: %d.

28011

16

No

This message could not be delivered because its %S_MSG has expired or is invalid.

28012

16

No

The Service Broker in the target database is unavailable: '%S_MSG'.

28013

16

No

The service broker is administratively disabled.

28014

16

No

The database is in read-only mode.

28015

16

No

The database is in single-user mode.

28016

16

No

The message has been dropped because the service broker in the target database is unavailable: '%S_MSG'.

28017

16

No

The message has been dropped because the target service broker is unreachable.

28018

16

No

The database is a replica of a mirrored database.

28019

16

No

System error %d occurred while creating a new message element GUID for this forwarded message.

28020

16

No

Could not create user token for user %d in database %d.

28021

16

No

One or more messages could not be delivered to the local service targeted by this dialog.

28022

10

No

An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate is not yet valid.

28023

10

No

An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate has expired.

28024

16

Yes

The security certificate bound to database principal (Id: %i) is not yet valid. Either wait for the certificate to become valid or install a certificate that is currently valid.

28025

16

Yes

The security certificate bound to database principal (Id: %i) has expired. Create or install a new certificate for the database principal.

28026

10

No

Connection handshake failed. Not enough memory available. State %d.

28027

10

No

Connection handshake failed. There is no compatible %S_MSG. State %d.

28028

10

No

Connection handshake failed. Could not send a handshake message because the connection was closed by peer. State %d.

28029

10

No

Connection handshake failed. Unexpected event (%d) for current context (%d). State %d.

28030

10

No

Connection handshake failed. A call to the SQL Server Network Interface failed: (%x) %ls. State %d.

28031

10

No

Connection handshake failed. An OS call failed: (%x) %ls. State %d.

28032

10

No

A previously existing connection with the same peer was detected during connection handshake. This connection lost the arbitration and it will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State %d.

28033

10

No

A new connection was established with the same peer. This connection lost the arbitration and it will be closed. All traffic will be redirected to the newly opened connection. This is an informational message only. No user action is required. State %d.

28034

10

No

Connection handshake failed. The login '%.*ls' does not have CONNECT permission on the endpoint. State %d.

28035

10

No

Connection handshake failed. The certificate used by the peer is invalid due to the following reason: %S_MSG. State %d.

28036

10

No

Connection handshake failed. The certificate used by this endpoint was not found: %S_MSG. Use DBCC CHECKDB in master database to verify the metadata integrity of the endpoints. State %d.

28037

10

No

Connection handshake failed. Error %d occurred while initializing the private key corresponding to the certificate. The SQL Server errorlog and the Windows event log may contain entries related to this error. State %d.

28038

10

No

Connection handshake failed. The handshake verification failed. State %d.

28039

10

No

Connection handshake failed. The receive SSPI packet is not of type of the negotiated package. State %d.

28040

10

No

A corrupted message has been received. The adjacent error message header is invalid.

28041

16

No

A corrupted message has been received. The encrypted payload offset is invalid (%d).

28042

16

No

A corrupted message has been received. The arbitration request header is invalid.

28043

16

No

A corrupted message has been received. The arbitration response header is invalid.

28044

16

No

A corrupted message has been received. It is not encrypted and signed using the currently configured endpoint algorithm. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.

28045

10

No

Connection handshake failed. The certificate used by the peer does not match the one in MASTER database with same issuer name and serial number. State %d.

28046

10

Yes

%S_MSG Login succeeded for user '%.*ls'. Authentication mode: %.*ls. %.*ls

28047

10

Yes

%S_MSG login attempt failed with error: '%.*ls'. %.*ls

28048

10

Yes

%S_MSG login attempt by user '%.*ls' failed with error: '%.*ls'. %.*ls

28050

10

No

The session keys for this conversation could not be created or accessed. The database master key is required for this operation.

28051

10

No

Could not save a dialog session key. A master key is required in the database to save the session key.

28052

16

No

Cannot decrypt session key while regenerating master key with FORCE option.

28053

16

No

Service Broker could not upgrade conversation session keys in database '%.*ls' to encrypted format (Error: %d). The Service Broker in this database was disabled. A master key is required to the database in order to enable the broker.

28054

16

No

Service Broker needs to access the master key in the database '%.*ls'. Error code:%d. The master key has to exist and the service master key encryption is required.

28055

16

No

The certificate '%.*ls' is not valid for endpoint authentication. The certificate must have a private key encrypted with the database master key and current UTC date has to be between the certificate start date and the certificate expiration date.

28056

16

No

This message could not be delivered because the user with ID %i in database ID %i does not have control permission on the service. Service name: '%.*ls'.

28057

10

No

Service Broker in database '%.*ls' has a pending conversation upgrade operation. A database master key in the database is required for this operation to complete.

28058

16

No

Service Broker could not upgrade this conversation during a database upgrade operation.

28059

16

No

Connection handshake failed. The received premaster secret of size %d does not have the expected size of %d. State %d.

28060

16

No

The AES encryption algorithm is only supported on Windows XP, Windows Server 2003 or later versions.

28061

16

No

A corrupted message has been received. The adjacent message integrity check signature could not be validated.

28062

16

No

A corrupted message has been received. The signed dialog message header is invalid.

28063

16

No

A corrupted message has been received. A required variable data field is not present: %S_MSG. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.

28064

16

No

A corrupted message has been received. A string variable data field is not a valid UNICODE string: %S_MSG. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.

28065

16

No

A corrupted message has been received. The unsigned dialog message header is invalid. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.

28066

16

No

A corrupted message has been received. The security dialog message header is invalid. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.

28067

16

No

A corrupted message has been received. The encrypted offset of the envelope does not match the payload encrypted offset. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.

28068

16

No

A corrupted message has been received. The envelope payload is bigger than the message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.

28069

16

Yes

Unexpected session key when encrypting a dialog message.

28070

10

No

Connection handshake failed. The received SSPI message Confirm status is unexpected. State %d.

28072

16

No

A serious error occurred in the Service Broker message transmitter (operation %i): Error: %i, State: %i. Message transmission will resume in %i seconds.

28073

16

No

An out of memory condition has occurred in the Service Broker message transmitter (operation %i). Message transmission will resume in %i seconds.

28074

16

No

Service Broker could not upgrade conversation with conversation_handle '%ls'. Use END CONVERSATION ... WITH CLEANUP to delete this conversation, then try again to enable the broker. Use ALTER DATABASE ... SET ERROR_BROKER to error all conversations in this database. Use ALTER DATABASE ... SET NEW_BROKER to delete all conversations in this database.

28075

10

No

The broker in the sender's database is in single user mode. Messages cannot be delivered while in single user mode.

28076

10

No

Could not query the FIPS compliance mode flag from registry. Error %ls.

28077

10

No

%S_MSG transport is running in FIPS compliance mode. This is an informational message only. No user action is required.

28078

10

No

The RC4 encryption algorithm is not supported when running in FIPS compliance mode.

28079

10

No

Connection handshake failed. The received SSPI packet is not of the expected direction. State %d.

28080

10

No

Connection handshake failed. The %S_MSG endpoint is not configured. State %d.

28081

10

No

Connection handshake failed. An unexpected status %d was returned when trying to send a handshake message. State %d.

28082

10

No

Connection handshake failed. An unexpected internal failure occurred when trying to marshal a message. State %d.

28083

16

No

The database principal '%.*ls' cannot be used in a remote service binding because it cannot own certificates. Remote service bindings cannot be associated with 1) roles, 2) groups or 3) principals mapped to certificates or asymmetric keys.

28084

10

No

An error occurred in Service Broker internal activation while trying to scan the user queue '%ls' for its status. Error: %i, State: %i. %.*ls This is an informational message only. No user action is required.

28085

16

No

The activated task was ended because the associated queue was dropped.

28086

16

No

The activated task was ended because either the queue or activation was disabled.

28087

16

No

The activated task was aborted because the invoked stored procedure '%ls' did not execute RECEIVE.

28088

16

No

The activated task was aborted due to an error (Error: %i, State %i). Check ERRORLOG or the previous "Broker:Activation" trace event for possible output from the activation stored procedure.

28089

16

No

The database principal '%.*ls' cannot be used in a remote service binding because it cannot own certificates. This is a special user for backward compatibility with implicitly connected user schemas.

28090

16

No

An error occurred while deleting sent messages from the transmission queue, Error: %i, State: %i. Verify that no other operation is locking the transmission queue, and that the database is available.

28098

10

No

A previously existing connection with the same peer was found after DNS lookup. This connection will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State %d.

28099

10

No

During the database upgrade process on database '%.*ls', a user object '%S_MSG' named '%.*ls' was found to already exist. That object is now reserved by the system in this version of SQL Server. Because it already exists in the database, the upgrade process is unable to install the object. Remove or rename the user object from the original (pre-upgraded) database on an older version of SQL Server and then retry the database upgrade process by using CREATE DATABASE FOR ATTACH. Functionality that relies on the reserved object may not function correctly if you continue to use the database in the current state.

28101

16

No

User '%.*ls\%.*ls' does not have permission to debug the requested client connection.

28102

16

No

Batch execution is terminated because of debugger request.

28201

10

No

SQLSQM.EXE cannot be launched. This can either be caused if the required information in the registry is missing or corrupted or SQLSQM.EXE cannot be found.

28102

16

No

Batch execution is terminated because of debugger request.

28201

10

No

SQLSQM.EXE cannot be launched. This can either be caused if the required information in the registry is missing or corrupted or SQLSQM.EXE cannot be found.

29001

16

No

To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO).

29003

16

No

Invalid parameter combinations.

29004

16

No

Unknown property specified: %s.

Community Additions

ADD
Show:
© 2014 Microsoft