The conversation with ID ‘%.*ls’ and initiator: %d references a missing conversation group ‘%.*ls’. Run DBCC CHECKDB to analyze and repair the database.

Details
Product: SQL Server
Event ID: 8443
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: SB_DIALOG_WO_CONV_GROUP
Message: The conversation with ID ‘%.*ls’ and initiator: %d references a missing conversation group ‘%.*ls’. Run DBCC CHECKDB to analyze and repair the database.
   
Explanation

The metadata layer returned NULL for the conversation group. The database has been corrupted in some way. One possible source of corruption is a disk error.

   
User Action

Run DBCC CHECKDB in repair mode to bring the database back into a consistent state. It may delete messages if necessary to restore consistency. Investigate system error logs to see if this error was caused by another failure in the system.

Related:

%ls: Operating system error %ls encountered.

Details
Product: SQL Server
Event ID: 17053
Source: MSSQLServer
Version: 10.0
Component: SQLEngine
Symbolic Name: OS_ERROR
Message: %ls: Operating system error %ls encountered.
   
Explanation

Generic operating system error occurred. Not clear what the resulting state is.

   
User Action

Usually this is in conjunction with some other error and should be used to help diagnose that failure. Examples would include reads or writes to data or log files that fail, registry read/write operations, or other unexpected Win32API failures.

Related:

Could not obtain information about Windows NT group/user ‘%ls’.

Details
Product: SQL Server
Event ID: 8198
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Could not obtain information about Windows NT group/user ‘%ls’.
   
Explanation
A process executed within SQL Server or from the SQL Server Agent, such as the xp_logininfo stored procedure, a scheduled job, or a replication agent, needs to verify the credentials of a Windows-authenticated login. The attempt to retrieve those credentials on the domain failed for an unspecified reason.

One common cause of this error is a manually created domain group with the name “everyone.” This name conflicts with the built-in hidden group of the same name. Other conflicts between objects in a domain can also cause the problem, as can insufficient permissions to retrieve the information about the objects.

There are many other root causes for this error; many of them are described in more detail in Microsoft Knowledge Base article 834124.

   
User Action
  • If you can see a domain group called “everyone,” rename or delete that group to avoid a conflict with the hidden group “everyone” that is built in to the domain.
  • Verify trust relationships and firewall settings between any domains involved.
  • Verify that the account used to lookup the domain credentials has sufficient permissions to perform the operation. This account may be the logged-on user or the account used to start either the SQL Server or SQL Server Agent service, depending on the context.
  • Check whether there are any local or global groups, computers, or domain names in any of the local or trusted domains that have the same name as any of the other objects. If there is overlap, rename one or more objects to avoid the duplication.
  • For more information about additional troubleshooting steps, see Microsoft Knowledge Base article 834124.

Related:

OLE Automation objects are not supported in fiber mode.

Details
Product: SQL Server
Event ID: 8149
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: OLE Automation objects are not supported in fiber mode.
   
Explanation
Fiber mode, also known as lightweight pooling, is not a supported SQL Server configuration option if you use OLE Automation objects.

By default, SQL Server uses one thread per active SPID or user process. These threads work in a pooled configuration to keep the number of threads manageable. The advanced configuration option lightweight pooling (which is sometimes referred to as “fiber mode”) uses Windows NT “fiber” support to handle several execution contexts with a single thread.

You do not need to use fiber mode except in very rare circumstances. Lightweight pooling is only even potentially useful if all of the following conditions are met. You still must determine if it is actually useful through careful controlled testing:

  • Large multiprocessor servers are in use.
  • All servers are running at or near maximum capacity.
  • A lot of context switching occurs (greater than 20,000 per second).

For more information about how to determine the proper SQL Server configuration settings, see Microsoft Knowledge Base article 319942.

   
User Action
Turn off the lightweight pooling option.

exec sp_configure ‘show advanced’, 1
RECONFIGURE
exec sp_configure ‘lightweight pooling’, 0
RECONFIGURE WITH OVERRIDE

The setting takes effect after stopping and restarting the SQL Server instance.

Related:

System table pre-checks: Object ID O_ID has chain linkage mismatch. P_ID1->next = P_ID2, but P_ID2->prev = P_ID3. Check statement terminated due to unrepairable error.

Details
Product: SQL Server
Event ID: 7987
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC2_PRE_CHECKS_CHAIN_LINKAGE_MISMATCH
Message: System table pre-checks: Object ID O_ID has chain linkage mismatch. P_ID1->next = P_ID2, but P_ID2->prev = P_ID3. Check statement terminated due to unrepairable error.
   
Explanation

The first phase of a DBCC CHECKDB is to do primitive checks on the data pages of critical system tables. If any errors are found, they cannot be repaired; therefore, the DBCC CHECKDB terminates immediately.

The next page pointer of page P_ID1 points to page P_ID2; however, the previous page pointer of page P_ID2 points to page P_ID3 but not back to page P_ID1, as it should.

   
User Action
Look for Hardware Failure

Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs.

If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor.

Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system.

Restore from Backup

If the problem is not hardware related and a known clean backup is available, restore the database from the backup.

Run DBCC CHECKDB

Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Service and Support (CSS).

Related:

System table pre-checks: Object ID O_ID has cross-object chain linkage. Page P_ID1 points to P_ID2 in alloc unit ID A_ID1 (should be A_ID2). Check statement terminated due to unrepairable error.

Details
Product: SQL Server
Event ID: 7986
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC2_PRE_CHECKS_CROSS_OBJECT_LINKAGE
Message: System table pre-checks: Object ID O_ID has cross-object chain linkage. Page P_ID1 points to P_ID2 in alloc unit ID A_ID1 (should be A_ID2). Check statement terminated due to unrepairable error.
   
Explanation

The first phase of a DBCC CHECKDB is to do primitive checks on the data pages of critical system tables. If any errors are found, they cannot be repaired; therefore, the DBCC CHECKDB terminates immediately. The next page pointer of page P_ID1 in the data level of the specified object points to a page, P_ID2, in a different object.

   
User Action
Look for Hardware Failure

Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs.

If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor.

Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system.

Restore from Backup

If the problem is not hardware related and a known clean backup is available, restore the database from the backup.

Run DBCC CHECKDB

Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Customer Service and Support (CSS).

Related:

System table pre-checks: Object ID O_ID. Page P_ID has unexpected page type PAGETYPE. Check statement terminated due to unrepairable error.

Details
Product: SQL Server
Event ID: 7984
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC2_PRE_CHECKS_BAD_PAGE_TYPE
Message: System table pre-checks: Object ID O_ID. Page P_ID has unexpected page type PAGETYPE. Check statement terminated due to unrepairable error.
   
Explanation

A page with a type other than DATA_PAGE was found in the data level of the specified object. This error is raised during the first phase of the DBCC CHECKDB command checks. During this phase, DBCC CHECKDB performs primitive checks on the data pages of critical system base tables.

Note:

If any errors are found in the system tables, the errors cannot be repaired; therefore, the DBCC CHECKDB command ends immediately.

   
User Action
Look for Hardware Failure

Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs.

If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor.

Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system.

Restore from Backup

If the problem is not hardware related and a known clean backup is available, restore the database from the backup.

Run DBCC CHECKDB

Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Service and Support (CSS).

Related:

User ‘%.*ls’ does not have permission to run DBCC %ls for database ‘%.*ls’.

Details
Product: SQL Server
Event ID: 7983
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: User ‘%.*ls’ does not have permission to run DBCC %ls for database ‘%.*ls’.
   
Explanation
You do not have permission to run the specified DBCC statement.
   
User Action
Use a login which has the appropriate permissions. See the Books Online topic for the specific DBCC statement to see what permissions are necessary to execute it.

Related:

Permission to execute DBCC %ls denied.

Details
Product: SQL Server
Event ID: 7956
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Permission to execute DBCC %ls denied.
   
Explanation
DBCC INPUTBUFFER permissions default to members of the sysadmin fixed server role only, who can see any SPID. Other users can see any SPID they own. Permissions are not transferable.

Note that only DBCC INPUTBUFFER will raise the above message. A permission check failure for other DBCC statements will raise message 7983, “User ‘%.*ls’ does not have permission to run DBCC %ls for database ‘%.*ls’.”

   
User Action
Any login that needs to see the INPUTBUFFER for a SPID other than its own should be added to the sysadmin fixed server role.

Related:

Table error: Filestream directory exists for column ID C_ID of object ID O_ID, index ID I_ID, partition ID PN_ID, but that column is not a Filestream column.

Details
Product: SQL Server
Event ID: 7936
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC2_FS_ORPHANED_COLUMN_DIRECTORY
Message: Table error: Filestream directory exists for column ID C_ID of object ID O_ID, index ID I_ID, partition ID PN_ID, but that column is not a Filestream column.
   
Explanation

During DBCC CHECKDB, a Filestream directory was found for the specified column C_ID; however, the data type of the column is not Filestream.

   
User Action
Look for Hardware Failure

Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs.

If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor.

Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system.

Restore from Backup

If the problem is not hardware related and a known clean backup is available, restore the database from the backup.

Run DBCC CHECKDB

Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Customer Service and Support (CSS).

Related: