SQL Server Errors or Failures from Error: 35257 to Error: 35279

SQLServerF1

Error: 35257, Severity: 16, AlwaysOn Availability Groups Send Error (Error code 0x%X, “NOT OK”) was returned when sending a message for database ID %d. If the partner is running and visible over the network, retry the command using correctly configured partner-connection parameters

Error: 35259, Severity: 16, Database ‘%.*ls’ is already participating in a different availability group.
Error: 35260, Severity: 16, During an attempted database recovery, an availability database manager was not found for database id %d with availability group ID %d and group database ID %ls. Recovery was terminated. The most likely cause of this error is that the availability group
Error: 35261, Severity: 16, Attempt to perform an AlwaysOn Availability Groups operation on a system database, ‘%ls’, failed. System databases are not supported by AlwaysOn Availability Groups.

Error: 35262, Severity: 17, Skipping the default startup of database ‘%.*ls’ because the database belongs to an availability group (Group ID: %d). The database will be started by the availability group. This is an informational message only. No user action is required.
Error: 35263, Severity: 16, During the undo phase, a function call (%ls) to the primary replica returned an unexpected status (Code: %d). Check for a possible cause in the SQL Server error log for the primary replica. If an error occurred on the primary database, you might need to s
Error: 35264, Severity: 10, AlwaysOn Availability Groups data movement for database ‘%.*ls’ has been suspended for the following reason: “%S_MSG” (Source ID %d; Source string: ‘%.*ls’). To resume data movement on the database, you will need to resume the database manually. For infor
Error: 35265, Severity: 10, AlwaysOn Availability Groups data movement for database ‘%.*ls’ has been resumed. This is an informational message only. No user action is required.
Error: 35266, Severity: 10, AlwaysOn Availability Groups connection with %S_MSG database established for %S_MSG database ‘%.*ls’ on the availability replica with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is
Error: 35267, Severity: 10, AlwaysOn Availability Groups connection with %S_MSG database terminated for %S_MSG database ‘%.*ls’ on the availability replica with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is r

Error: 35268, Severity: 16, Synchronization of a secondary database, ‘%.*ls’, was interrupted, leaving the database in an inconsistent state. The database will enter the RESTORING state. To complete recovery and bring the database online, use current log backups from the primary dat
Error: 35269, Severity: 21, Synchronization of a secondary database, ‘%.*ls’, was interrupted, leaving the database in an inconsistent state. The database will be marked SUSPECT. To return the database to a consistent state, restore it from a clean database backup followed by all su
Error: 35270, Severity: 10, Received a corrupt FileStream transport message. The ‘%ls’ message section is invalid.
Error: 35272, Severity: 16, Either nvalid parameters were supplied for sys.sp_availability_group_command_internal or user does not have permissions to execute this procedure.
Error: 35273, Severity: 10, Bypassing recovery for database ‘%ls’ because it is marked as an inaccessible availability database. The session with the primary replica was interrupted while reverting the database to the common recovery point. Either the WSFC node lacks quorum or the c
Error: 35274, Severity: 10, Recovery for availability database ‘%ls’ is pending until the secondary replica receives additional transaction log from the primary before it complete and come online. Ensure that the server instance that hosts the primary replica is running.
Error: 35275, Severity: 16, A previous RESTORE WITH CONTINUE_AFTER_ERROR operation or being removed while in the SUSPECT state from an availability group left the ‘%.*ls’ database in a potentially damaged state. The database cannot be joined while in this state. Restore the database
Error: 35276, Severity: 17, Failed to allocate and schedule an AlwaysOn Availability Groups task for database ‘%ls’. Manual intervention may be required to resume synchronization of the database. If the problem persists, you might need to restart the local instance of SQL Server.
Error: 35278, Severity: 16, Availability database ‘%.*ls’, which is in the secondary role, is being restarted to resynchronize with the current primary database. This is an informational message only. No user action is required.
Error: 35279, Severity: 16, The attempt to join database ‘%.*ls’ to the availability group was rejected by the primary database with error ‘%d’. For more information, see the SQL Server error log for the primary replica.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 35210 to Error: 35233

SQLServerF1

Error: 35210, Severity: 16, Failed to modify options for availability replica ‘%.*ls’ in availability group ‘%.*ls’. The specified availability group does not contain an availability replica with specified name. Verify that availability group name and availability replica name are c

Error: 35211, Severity: 16, The %ls operation is not allowed. The operation attempted to change the configuration of availability replica ‘%.*ls’ to the asynchronous-commit availability mode with automatic failover, which is an invalid configuration. Either change the failover mod
Error: 35212, Severity: 16, The %ls operation is not allowed by the current availability-group configuration. This operation would exceed the maximum number of %d synchronous-commit availability replicas in availability group ‘%.*ls’. Change one of the existing synchronous-commit
Error: 35213, Severity: 16, The %ls operation is not allowed by the current availability-group configuration. This operation would exceed the maximum number of %d automatic failover targets in availability group ‘%.*ls’. Change one of the existing synchronous-commit replicas to th

Error: 35214, Severity: 16, The %ls operation failed for availability replica ‘%.*ls’. The minimum value for session timeout is %d. Retry the operation specifying a valid session-timeout value.
Error: 35215, Severity: 16, The %ls operation is not allowed on availability replica ‘%.*ls’, because automatic failover mode is an invalid configuration on a SQL Server Failover Cluster Instance. Retry the operation by specifying manual failover mode.
Error: 35217, Severity: 16, The thread pool for AlwaysOn Availability Groups was unable to start a new worker thread because there are not enough available worker threads. This may degrade AlwaysOn Availability Groups performance. Use the “max worker threads” configuration option
Error: 35220, Severity: 16, Could not process the operation. AlwaysOn Availability Groups replica manager is waiting for the host computer to start a Windows Server Failover Clustering (WSFC) cluster and join it. Either the local computer is not a cluster node, or the local cluster
Error: 35221, Severity: 16, Could not process the operation. AlwaysOn Availability Groups replica manager is disabled on this instance of SQL Server. Enable AlwaysOn Availability Groups, by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry t
Error: 35222, Severity: 16, Could not process the operation. AlwaysOn Availability Groups does not have permissions to access the Windows Server Failover Clustering (WSFC) cluster. Disable and re-enable AlwaysOn Availability Groups by using the SQL Server Configuration Manager. The

Error: 35223, Severity: 16, Cannot add %d availability replica(s) to availability group ‘%.*ls’. The availability group already contains %d replica(s), and the maximum number of replicas supported in an availability group is %d.
Error: 35224, Severity: 16, Could not process the operation. AlwaysOn Availability Groups failed to load the required Windows Server Failover Clustering (WSFC) library. Verify that the computer is a node in a WSFC cluster. You will need to restart the SQL Server instance to reload
Error: 35225, Severity: 16, Could not process the operation. The instance of SQL Server is running under WOW64 (Windows 32-bit on Windows 64-bit), which does not support AlwaysOn Availability Groups. Reinstall SQL Server in the native 64-bit edition, and re-enable AlwaysOn Availab
Error: 35226, Severity: 16, Could not process the operation. AlwaysOn Availability Groups has not started because the instance of SQL Server is not running as a service. Restart the server instance as a service, and retry the operation.
Error: 35228, Severity: 16, The attempt to set the failure condition level for availability group ‘%.*ls’ failed. The specified level value is out of the valid range [%u, %u]. Reenter the command specifying a valid failure condition level value.
Error: 35229, Severity: 16, The attempt to set the health check timeout value for availability group ‘%.*ls’ failed. The specified timeout value is less than %u milliseconds. Reenter the command specifying a valid health check timeout value.
Error: 35230, Severity: 16, The specified computer name is either an empty string or is longer than %d Unicode characters. Reenter the command specifying a valid computer name.
Error: 35231, Severity: 16, The specified server instance name, ‘%ls’, is invalid. Reenter the command specifying a valid instance name.
Error: 35232, Severity: 16, The specified endpoint URL ‘%.*ls’ is invalid. Reenter the command specifying the correct URL. For information about specifying the endpoint URL for an availability replica, see SQL Server Books Online.
Error: 35233, Severity: 16, Cannot create an availability group containing %d availability replica(s).

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 33308 to Error: 33418

SQLServerF1

Error: 33308, Severity: 10, The queue %d in database %d has activation enabled and contains unlocked messages but no RECEIVE has been executed for %u seconds.

Error: 33309, Severity: 10, Cannot start cluster endpoint because the default %S_MSG endpoint configuration has not been loaded yet.
Error: 33401, Severity: 16, FILESTREAM database options cannot be set on system databases such as ‘%.*ls’.
Error: 33402, Severity: 16, An invalid directory name ‘%.*ls’ was specified. Use a valid Windows directory name.
Error: 33403, Severity: 16, The case-sensitive or binary collation ‘%.*ls’ cannot be used with the COLLATE_FILENAME option. Change the collation to a case-insensitive collation type.
Error: 33404, Severity: 16, The database default collation ‘%.*ls’ is case sensitive and cannot be used to create a FileTable. Specify a case insensitive collation with the COLLATE_FILENAME option.
Error: 33405, Severity: 16, An error occurred during the %S_MSG %S_MSG operation on a FileTable object. (HRESULT = ‘0x%08x’).

Error: 33406, Severity: 16, An invalid filename, ‘%.*ls’, caused a FileTable check constraint error. Use a valid Windows filename.
Error: 33407, Severity: 16, An invalid path locator caused a FileTable check constraint error. The path locator cannot indicate a root row. Correct the path locator or use the default value.
Error: 33408, Severity: 16, The operation caused a FileTable check constraint error. A directory entry cannot have a data stream associated with the row. Remove the blob data or clear the is_directory flag.
Error: 33409, Severity: 16, The operation caused a FileTable check constraint error. A file entry cannot have a NULL value for the data stream associated with the row. Insert file data or use 0x to insert a zero length file.
Error: 33410, Severity: 16, An invalid path locator caused a FileTable check constraint error. The parent of a row’s path locator must be a directory, not a file. Correct the path locator to refer to a parent that is a directory.

Error: 33411, Severity: 16, The option ‘%.*ls’ is only valid when used on a FileTable. Remove the option from the statement.
Error: 33412, Severity: 16, The option ‘%.*ls’ is not valid when used with the ‘%.*ls’ syntax. Remove the option from the statement.
Error: 33413, Severity: 16, The option ‘%.*ls’ can only be specified once in a statement. Remove the duplicate option from the statement.
Error: 33414, Severity: 16, FileTable objects require the FILESTREAM database option DIRECTORY_NAME to be non-NULL. To create a FileTable in the database ‘%.*ls’, set the DIRECTORY_NAME option to a non-NULL value using ALTER DATABASE. Or, to set the DIRECTORY_NAME option to NULL, in
Error: 33415, Severity: 16, FILESTREAM DIRECTORY_NAME ‘%.*s’ attempting to be set on database ‘%.*s’ is not unique in this SQL Server instance. Provide a unique value for the database option FILESTREAM DIRECTORY_NAME to enable non-transacted access.
Error: 33416, Severity: 10, When the FILESTREAM database option NON_TRANSACTED_ACCESS is set to FULL and the READ_COMMITTED_SNAPSHOT or the ALLOW_SNAPSHOT_ISOLATION options are on, T-SQL and transactional read access to FILESTREAM data in the context of a FILETABLE is blocked.
Error: 33417, Severity: 16, An invalid path locator caused a FileTable check constraint error. The path locator has a level of %d, which is deeper than the limit of %d supported by FileTable. Reduce the depth of the directory hierarchy.
Error: 33418, Severity: 16, FILETABLE_DIRECTORY ‘%.*s’ attempting to be set on table ‘%.*s’ is not unique in the database ‘%.*s’. Provide a unique value for the option FILETABLE_DIRECTORY to this operation.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 30026 to Error: 30046

SQLServerF1

Error: 30026, Severity: 16, The search property list ‘%.*ls’ already exists in the current database. Duplicate search property list names are not allowed. Rerun the statement and specify a unique name for the search property list. For a list of the search property lists on the curre

Error: 30027, Severity: 10, The full-text index is in an inconsistent state because the search property list of the full-text index was reconfigured using the WITH NO POPULATION clause. To bring the full-text index into a consistent state, start a full population using the statement
Error: 30028, Severity: 17, Failed to get pipeline interface for ‘%ls’, resulting in error: 0x%X. There is a problem communicating with the host controller or filter daemon host.
Error: 30029, Severity: 17, The full-text host controller failed to start. Error: 0x%X.
Error: 30030, Severity: 16, The search property ‘%.*ls’ does not exist, or you do not have permission to perform this action. Verify that the correct search property is specified and that you have the permission required by the Transact-SQL statement. For a list of the search proper

Error: 30031, Severity: 17, A full-text master merge failed on full-text catalog ‘%ls’ in database ‘%.*ls’ with error 0x%08X.
Error: 30032, Severity: 16, The stoplist ‘%.*ls’ does not contain fulltext stopword ‘%.*ls’ with locale ID %d. Specify a valid stopword and locale identifier (LCID) in the Transact-SQL statement.
Error: 30033, Severity: 16, The stoplist ‘%.*ls’ already contains full-text stopword ‘%.*ls’ with locale ID %d. Specify a unique stopword and locale identifier (LCID) in the Transact-SQL statement.
Error: 30034, Severity: 16, Full-text stoplist ‘%.*ls’ cannot be dropped because it is being used by at least one full-text index. To identify which full-text index is using a stoplist: obtain the stoplist ID from the stoplist_id column of the sys.fulltext_indexes catalog view, and
Error: 30035, Severity: 16, The search property ‘%.*ls’ already exists in the search property list. Specify a search property name that is unique within the specified search property list. For a list of the search properties on the current database, use the sys.registered_search_pro

Error: 30036, Severity: 16, Search property list ‘%.*ls’ cannot be dropped because it is being used by at least one full-text index. To identify the full-text indexes that are using the search property list, obtain the search property list id from the property_list_id column of the
Error: 30037, Severity: 16, An argument passed to a fulltext function is not valid.
Error: 30038, Severity: 17, Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index.
Error: 30039, Severity: 17, Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. The batch for the indexing operation will automatically be retried using a smaller batch size.
Error: 30040, Severity: 10, During a full-text crawl of table or indexed view ‘%ls’, an unregistered property, ‘%ls’, was found in batch ID %d. This property will be indexed as part of the generic content and will be unavailable for property-scoped full-text queries. Table or indexe
Error: 30041, Severity: 10, The master merge started at the end of the full crawl of table or indexed view ‘%ls’ failed with HRESULT = ‘0x%08x’. Database ID is ‘%d’, table id is %d, catalog ID: %d.
Error: 30043, Severity: 16, Stopwords of zero length cannot be added to a full-text stoplist. Specify a unique stopword that contains at least one character.
Error: 30044, Severity: 16, The user does not have permission to alter the current default stoplist ‘%.*ls’. To change the default stoplist of the database, ALTER permission is required on both new and old default stoplists.
Error: 30045, Severity: 17, Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index.
Error: 30046, Severity: 16, SQL Server encountered error 0x%x while communicating with full-text filter daemon host (FDHost) process. Make sure that the FDHost process is running. To re-start the FDHost process, run the sp_fulltext_service ‘restart_all_fdhosts’ command or restart th

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 27156 to Error: 27178

SQLServerF1

Error: 27156, Severity: 16, The Integration Services server property, ‘%ls’, cannot be found. Check the name of the property and try again.

Error: 27157, Severity: 16, The environment ‘%ls’ already exists or you have not been granted the appropriate permissions to create it.
Error: 27158, Severity: 16, Error number, %d, occurred in the procedure, ‘%ls’, at line number, %d. The error message was: ‘%ls’ The error level was %d and the state was %d.
Error: 27159, Severity: 16, Data type of the input value is not supported.
Error: 27161, Severity: 10, Warning: the requested permission has already been granted to the user. The duplicate request will be ignored.
Error: 27162, Severity: 16, The property, ‘%ls’, cannot be changed because the Integration Services database is not in single-user mode. In Management Studio, in the Database Properties dialog box, set the Restrict Access property to single-user mode. Then, try to change the value o

Error: 27163, Severity: 16, The value for the Integration Services server property, ‘%ls’, is not valid. In Management Studio, in the Integration Services Properties dialog box, enter a valid value for this property.
Error: 27165, Severity: 10, Warning: During startup, the Integration Services server marked operation %I64d (type %d, status %d) as terminated. Please check the operation/event log for operation details.
Error: 27166, Severity: 16, The installed version of SQL Server does not support the installation of the Integration Services server. Update SQL Server, and then try installing the Integration Services server again.
Error: 27167, Severity: 16, Failed to change the encryption algorithm to ‘%ls’. An error occurred while encrypting the environment variables with the ‘%ls’ algorithm.
Error: 27168, Severity: 16, Failed to change the encryption algorithm to ‘%ls’. An error occurred while encrypting the parameter values using the ‘%ls’ algorithm.
Error: 27169, Severity: 16, Failed to create a log entry for the requested operation.

Error: 27170, Severity: 16, Failed to retrieve the project named ‘%ls’.
Error: 27171, Severity: 16, The value specified is not valid. A value of data type ‘%ls’ is required.
Error: 27172, Severity: 16, The certificate and symmetric key used to encrypt project ‘%ls’ does not exist or you do not have sufficient permissions.
Error: 27173, Severity: 16, The environment variable ‘%ls’ already exists.
Error: 27175, Severity: 16, The execution has already completed.
Error: 27176, Severity: 16, The parameter ‘%ls’ does not exist or you do not have sufficient permissions.
Error: 27177, Severity: 16, Environment names must be unique. There is already an environment named ‘%ls’.
Error: 27178, Severity: 16, Unable to execute the project named ‘%ls’. You do not have sufficient permissions.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 27059 to Error: 27112

SQLServerF1

Error: 27059, Severity: 16, Could not lookup object_id. The reference table or maintenance trigger could not be found.

Error: 27060, Severity: 16, The Error Tolerant Index table name provided is not a valid SQL identifier.
Error: 27061, Severity: 16, The Error Tolerant Index table name provided refers to a missing table. Check sys.tables.
Error: 27062, Severity: 16, An auxiliary Fuzzy Lookup table maintenance table is missing.

Error: 27063, Severity: 16, An auxiliary Fuzzy Lookup table maintenance table name is null. Maintenance cannot proceed.
Error: 27064, Severity: 16, The row deleted from the reference table could not be located in the reference table copy.
Error: 27065, Severity: 16, Fuzzy Lookup Table Maintenance is not installed or the Error Tolerant Index is corrupt.

Error: 27100, Severity: 16, The input parameter, ‘%ls’, cannot be null. Provide a valid value for this parameter.
Error: 27101, Severity: 16, The value specified for the input parameter, ‘%ls’, is not valid. Provide a valid value for this parameter.
Error: 27102, Severity: 16, The input parameter, ‘%ls’, cannot be empty. Provide a valid value for this parameter.
Error: 27103, Severity: 16, Cannot find the execution instance ‘%I64d’ because it does not exist or you do not have sufficient permissions.
Error: 27104, Severity: 16, Cannot find the folder ‘%ls’ because it does not exist or you do not have sufficient permissions.
Error: 27105, Severity: 16, Cannot find the operation ‘%I64d’ because it does not exist or you do not have sufficient permissions.
Error: 27106, Severity: 16, Cannot find the parameter ‘%ls’ because it does not exist.
Error: 27107, Severity: 16, The specified %ls already exists.
Error: 27108, Severity: 16, The path for ‘%ls’ cannot be found. The operation will now exit.
Error: 27109, Severity: 16, Cannot find the project ‘%ls’ because it does not exist or you do not have sufficient permissions.
Error: 27110, Severity: 16, Default permissions for the project cannot be granted to the user. Make sure that the user can be assigned these permissions.
Error: 27111, Severity: 16, Cannot find the reference ‘%I64d’ because it is not part of the project or you do not have sufficient permissions.
Error: 27112, Severity: 16, Unable to update the row in the table, ‘%ls’. Make sure that this row exists.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 25636 to Error: 25664

SQLServerF1

 

Error: 25636, Severity: 16, Source and comparator types of the predicate do not match.
Error: 25639, Severity: 16, The %S_MSG, “%.*ls”, exceeds the number of allowable bound actions.
Error: 25640, Severity: 16, Maximum event size is smaller than configured event session memory. Specify a larger value for maximum event size, or specify 0.
Error: 25641, Severity: 16, For %S_MSG, “%.*ls”, the parameter “%ls” passed is invalid. %ls
Error: 25642, Severity: 16, Mandatory customizable attributes are missing for %S_MSG, “%.*ls”.

Error: 25643, Severity: 16, The %S_MSG, “%.*ls”, can not be added to an event session that specifies no event loss.
Error: 25644, Severity: 16, The %S_MSG, “%.*ls”, cannot be bound to the event session.
Error: 25646, Severity: 16, The %S_MSG name, “%.*ls”, is invalid.
Error: 25647, Severity: 16, The %S_MSG, “%.*ls”, could not be found. Ensure that the object exists and the name is spelled correctly.
Error: 25648, Severity: 16, The %S_MSG, “%.*ls”, could not be found. Ensure that the package exists and the name is spelled correctly.

Error: 25649, Severity: 16, Two of the actions/predicates for %S_MSG, “%.*ls”, can not coexist. Please remove one.
Error: 25650, Severity: 16, For %S_MSG, “%.*ls” the customizable attribute, “%ls”, was specified multiple times.
Error: 25651, Severity: 16, For %S_MSG, “%.*ls”, the value specified for customizable attribute, “%ls”, did not match the expected type, “%ls”.
Error: 25653, Severity: 16, The %S_MSG, “%.*ls”, does not exist in the event session. Object cannot be dropped from the event session.
Error: 25654, Severity: 16, Insuficient buffer space to copy error message.
Error: 25655, Severity: 16, Internal Extended Event error: invalid message code.
Error: 25656, Severity: 16, Error validating action. %ls
Error: 25657, Severity: 16, Error validating predicate. %ls
Error: 25658, Severity: 16, The %S_MSG name “%.*ls” is not unique.
Error: 25664, Severity: 16, Internal Extended Event error: invalid package ID.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 
1 2 3