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.

 

Leave a Reply

Your email address will not be published. Required fields are marked *