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:

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:

Cannot open or query registry key ‘%.*ls’.

Details
Product: SQL Server
Event ID: 7629
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Cannot open or query registry key ‘%.*ls’.
   
Explanation
A full-text process was not able to open the specified registry key. The specified key may be missing, or the Microsoft Search or Microsoft SQL Server startup account may not have permission to read the specified registry key.
   
User Action
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, see Microsoft Knowledge Base article 256986.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

If the specified key was manually deleted and it is the only key missing, it may be possible to restore the key from a backup of the registry. Depending on the key, some values may be server-, instance-, or catalog-specific, and the values may not be the same on different instances or over time. If the key cannot be restored, you may need to reinstall MSSearch, Full-Text, and/or SQL Server, depending on the key.

If the key exists, either the Search startup account or the SQL Server instance startup account will need to be granted sufficient permissions on the specified registry key, depending on which process failed.

Related:

Full-text query failed because full-text catalog ‘%ls’ is not yet ready for queries.

Details
Product: SQL Server
Event ID: 7623
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Full-text query failed because full-text catalog ‘%ls’ is not yet ready for queries.
   
Explanation
This error could occur under any of these circumstances:

  • The Microsoft Search service is not started.
  • If the SQL Server instance is clustered, the full-text resource is not online.
  • The specified catalog has not been populated.
  • The specified catalog has been disabled by some method outside of SQL Server, such as a direct registry update or an MSSearch administrative tool.
   
User Action
Follow these steps:

  • Verify that the Microsoft Search service is started.
  • If the SQL Server instance is clustered, also verify that the full-text resource for the specified SQL Server instance is online.
  • Rebuild and repopulate the specified catalog.

    EXEC sp_fulltext_catalog ‘fulltext_catalog_name’ , ‘rebuild’
    EXEC sp_fulltext_catalog ‘fulltext_catalog_name’ , ‘start_full’

  • Check the Event Viewer logs for errors related to Microsoft Search or that occur around the same tme as this error.

Related:

An unknown full-text failure (%x) occurred in function %hs on full-text catalog ‘%ls’.

Details
Product: SQL Server
Event ID: 7608
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: An unknown full-text failure (%x) occurred in function %hs on full-text catalog ‘%ls’.
   
Explanation
This error can occur in various circumstances. Often it is related to permissions or missing files.
   
User Action
  • Search the Microsoft Knowledge Base for information on the variable text that will appear between “full-text failure” and “occurred in function” in the message.
  • Search the Microsoft Knowledge Base for information on the variable text that will appear between “occurred in function” and “on full-text catalog” in the message.
  • To lessen the chance of a permissions issue, always use Enterprise Manager to change the account used to start the SQL Server service. When you chance the account through Enterprise Manager, all of the appropriate permissions are automatically granted to the SQL Server startup account.
  • Verify that the Schema.txt file located under the config folder for your instance of SQL Server has header information indicating it is a SQL Server schema file.
  • For more information about common resolutions to this problem, see Microsoft Knowledge Base article 295772.

Related:

Search on full-text catalog ‘%ls’ for database ID %d, table ID %d with search condition ‘%ls’ failed with unknown result (%x).

Details
Product: SQL Server
Event ID: 7607
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Search on full-text catalog ‘%ls’ for database ID %d, table ID %d with search condition ‘%ls’ failed with unknown result (%x).
   
Explanation
The full-text query failed for an unspecified reason.
   
User Action
Follow these steps:

  • Check the Event Viewer logs for errors that occur at the same time as this error. If there are other errors, troubleshoot them first.
  • Stop and restart the Microsoft Search service, and then retry your full-text command. Warning: the Microsoft Search service may be used by multiple instances of SQL Server or by other applications.
  • Rebuild the full-text catalog.
  • If you have restored your \Program Files\Microsoft SQL Server\MSSQL${YourInstanceName}\FTDATA\SQLServer${YourInstanceName}\Config directory from a backup, verify that the backup was taken when the Microsoft Search and MSSQLServer services were stopped. If they were not, restore a copy that was taken when the services were not running.

Related:

Could not find full-text index for database ID %d, table ID %d. Use sp_fulltext_table to deactivate then activate this index.

Details
Product: SQL Server
Event ID: 7606
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Could not find full-text index for database ID %d, table ID %d. Use sp_fulltext_table to deactivate then activate this index.
   
Explanation
The specified full-text index is unavailable.
   
User Action
Execute sp_fulltext_table with @action = ‘deactivate’. Then execute sp_fulltext_table with @action = ‘activate’. If you still receive this error, drop and recreate the full-text index.

Related:

Full-text catalog ‘%ls’ has been lost. Use sp_fulltext_catalog to rebuild and to repopulate this full-text catalog.

Details
Product: SQL Server
Event ID: 7605
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Full-text catalog ‘%ls’ has been lost. Use sp_fulltext_catalog to rebuild and to repopulate this full-text catalog.
   
Explanation
Either:

  • The full-text path and file name no longer exists as specified in the registry for this catalog.
  • The full-text catalog is corrupted or for other reasons the catalog cannot be mounted by the MSSearch service.
   
User Action
Try these actions in order. If any step succeeds, skip the remaining steps.

  1. Execute sp_fulltext_catalog with @action = ‘rebuild’ for the catalog listed in the message. If this does not resolve your error, try the remaining steps and, if necessary, retry this step.
  2. Drop any full-text indexes associated with the specified catalog. Then drop the full-text catalog using sp_fulltext_catalog with @action = ‘drop’ for the catalog listed in the message. Then add back first the catalog and indexes, in that order. If this does not resolve your error, try the remaining steps, and then, if necessary, retry this step.
  3. Execute sp_fulltext_service with the clean_up parameter. If this does not resolve your error, try the remaining steps and, if necessary, retry this step.
  4. Verify that the following registry keys do not have a subkey with the same name as the full-text catalog specified in the message.

    For a default instance:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Gather\SQLServer
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Gathering Manager\Applications\SQLServer\Projects
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Indexer\SQLServer

    For a named instance:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Gather\SQLServer$InstanceName
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Gathering Manager\Applications\SQLServer$InstanceName\Projects
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Indexer\SQLServer$InstanceName

    WARNING: If you use Registry Editor incorrectly, you may cause serious problems requiring you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

    Do not follow these next steps unless you are completely removing the specified catalog:

    • Backup your registry.
    • If the path specified in the keys exists, then delete the last folder from the hard drive. For example, if the keys under the SQL0000500005 keys point to C:\Program Files\Microsoft SQL Server\MSSQL$Instance1\FTDATA\SQL0000500005, then delete just the SQL0000500005 subdirectory.
    • Delete all of the registry keys that have the same name as the full-text catalog.

    Related: