Repair: IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), has been truncated before page %S_PGID and will be rebuilt.

Details
Product: SQL Server
Event ID: 7915
Source: MSSQLServer
Version: 9.00.1281.60
Symbolic Name: DBCC2_REPAIR_IAM_CHAIN_REBUILT
Message: Repair: IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), has been truncated before page %S_PGID and will be rebuilt.
   
Explanation

This is an information message sent by REPAIR that indicates that the specified Index Allocation Map (IAM) chain was patched so that it could be rebuilt. This patching may have required the allocation of a new head of the IAM chain or the removal of bad pages from the chain.

Possible Causes

For explanations, see the previous errors.

   
User Action

None

Related:

The repair statement was not processed. This level of repair is not supported when the database is in emergency mode.

Details
Product: SQL Server
Event ID: 7901
Source: MSSQLServer
Version: 9.00.1281.60
Symbolic Name: DBCC2_DATABASE_IN_EMERGENCY_MODE
Message: The repair statement was not processed. This level of repair is not supported when the database is in emergency mode.
   
Explanation

The database is in emergency, or bypass mode, and a repair level other than REPAIR_ALLOW_DATA_LOSS has been specified. Repairs cannot be made in emergency mode unless REPAIR_ALLOW_DATA_LOSS is specified.

Possible Causes

Not applicable

   
User Action

None

Related:

The %S_MSG protocol transport cannot listen on port %d because it is in use by another process.

Details
Product: SQL Server
Event ID: 9692
Source: MSSQLServer
Version: 9.00.1281.60
Symbolic Name: SB2_CANT_LISTEN_PORT_IN_USE
Message: The %S_MSG protocol transport cannot listen on port %d because it is in use by another process.
   
Explanation

Another program on the computer is using the TCP port indicated.

   
User Action

Run netstat -aon to determine what program is using the port. Disable that application or specify a different port for Service Broker.

Related:

Could not write a checkpoint record in database ID %d because the log is out of space. Contact the database administrator to truncate the log or allocate more space to the database log files.

Details
Product: SQL Server
Event ID: 3619
Source: MSSQLServer
Version: 9.00.1281.60
Symbolic Name: SYS_NOLOG
Message: Could not write a checkpoint record in database ID %d because the log is out of space. Contact the database administrator to truncate the log or allocate more space to the database log files.
   
Explanation

The transaction log is out of disk space.

   
User Action

Truncate the log to release some space, or allocate more space to the log. For more information see, “Managing a Full Transaction Log” in SQL Server 2005 Books Online.

Related:

A nonrecoverable I/O error occurred on file “%ls:” %ls.

Details
Product: SQL Server
Event ID: 3271
Source: MSSQLServer
Version: 9.00.1281.60
Symbolic Name: DMPIO_IO_ERROR
Message: A nonrecoverable I/O error occurred on file “%ls:” %ls.
   
Explanation

This is a general error that occurs when the operating system raises an error while performing I/O during a backup or restore operation. In most situations the cause is simply that the backup medium is full.

The error may include additional text from the operating system indication that the disk is full. When performing a backup or restore operation with third-party backup software an additional message may occur indicating that the backup failed. The message may look similar to the following text:

“2005-08-02 16:05:16.04 spid55 Error: 18210, Severity: 16, State: 1. 2005-08-02 16:05:16.04 spid55 BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device ‘VDINULL’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).”

This is an indication that the backup software requested a termination of the backup or restore operation.

   
User Action

Perform the following tasks as appropriate:

  • Review the underlying system error messages and SQL Server error messages preceding this one to identify the cause of the failure.

  • Ensure that the backup and restore medium has sufficient space.

  • Correct any errors raised by third-party backup and restore software.

Related:

The transaction log for database ‘%.*ls’ is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Details
Product: SQL Server
Event ID: 9002
Source: MSSQLServer
Version: 9.00.1281.60
Symbolic Name: LOG_IS_FULL
Message: The transaction log for database ‘%.*ls’ is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
   
Explanation

The database log is out of space. The log_reuse_wait_desc column in sys.databases describes why space in the log cannot be reused.

   
User Action

Use sys.databases to determine why the log is full and then correct the condition. For more information, see “sys.databases (Transact-SQL)” in SQL Server 2005 Books Online.

Related:

The repair statement was not processed. The database cannot be in read-only mode.

Details
Product: SQL Server
Event ID: 2596
Source: MSSQLServer
Version: 9.00.1281.60
Symbolic Name: DBCC_DATABASE_IN_READ_ONLY_MODE
Message: The repair statement was not processed. The database cannot be in read-only mode.
   
Explanation

This message indicates that the database is in read-only mode. Repairs are not possible when a database is in read-only mode.

Possible Causes

Not applicable

   
User Action

None

Related: