Error while undoing logged operation in database ‘%.*ls’. Error at log record ID %S_LSN.

Details
Product: SQL Server
Event ID: 3314
Source: MSSQLServer
Version: 10.0
Component: SQLEngine
Symbolic Name: ERR_LOG_RID2
Message: During undoing of a logged operation in database ‘%.*ls’, an error occurred at log record ID %S_LSN. Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
   
Explanation

This is the rollup error for undo recovery. There should be a previous error logged in the Windows event log indicating the specific failure.

   
User Action

Restore database, file or page from backup or repair database.

   
   
Version: 8.0
Component: SQL Engine
Message: Error while undoing logged operation in database ‘%.*ls’. Error at log record ID %S_LSN.
   
Explanation
The recovery process could not undo (roll back) one or more transactions in the specified database. This error will be accompanied by a more specific error in the SQL Server error log and/or the event log.
   
User Action
HARDWARE FAILURE

Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows NT system and application logs and the SQL Server error log to see if the error occurred as the result of hardware failure. Fix any hardware related problems.

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

Finally, you might find it beneficial to switch to a completely new hardware system, including 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.

DBCC CHECKDB

If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC CHECKDB with the appropriate repair clause to repair the corruption.

CAUTION: If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider before executing this statement.

If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your primary support provider.

Related:

Database backed up: Database: %1, creation date(time): %2(%3), pages dumped: %4!d!, first LSN: %5, last LSN: %6, number of dump devices: %9!d!, device information: (%10).

Details
Product: sql server
Event ID: 18264
Source: mssqlserver
Version: 8.0
Component: SQL Engine
Message: Database backed up: Database: %1, creation date(time): %2(%3), pages dumped: %4!d!, first LSN: %5, last LSN: %6, number of dump devices: %9!d!, device information: (%10).
   
Explanation
This informational message indicates that a full database backup has completed successfully. This message is written to the application event log and the SQL Server error log every time a backup finishes.
   
User Action
  • If the message is filling up your application Event Viewer logs, you can change properties of the log by setting the “Maximum log size” or choosing a different option under “When maximum log size is reached”.
  • If the message is causing your SQL Server error log to grow too large, you can execute the sp_cycle_errorlog stored procedure to create a new log. To increase the number of SQL Server error logs retained, follow the steps in Knowledge Base article 196909.
  • You can enable the trace flag 3226. This trace flag will prevent all informational BACKUP and RESTORE messages from being written to the SQL Server error log and the NT application event log. Informational BACKUP and RESTORE messages include 18264, 18265, 18266, 18267, 18268, 18269, 18270, 18271, 18276, and 18277. Be aware that alerts for BACKUP and RESTORE informational messages will no longer fire, since they rely on an entry in the NT application event log. See “Using Startup Options” in Books Online for detailed instructions on enabling a trace flag with the -T startup option.

Related:

Cannot recover the master database. Exiting.

Details
Product: SQL Server
Event ID: 3417
Source: MSSQLServer
Version: 10.0
Component: SQLEngine
Symbolic Name: REC_BADMASTER
Message: Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
   
Explanation

SQL Server cannot start the
master
database. If the
master
or
tempdb
cannot be brought online, SQL Server cannot run. This error is usually preceded by other errors. Review error logs to find the root cause.

   
User Action

Restore backup of the database or repair the database.

   
   
Version: 9.00.1281.60
Symbolic Name: REC_BADMASTER
Message: Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
   
Explanation

SQL Server cannot start the master database. If the master or tempdb cannot be brought online, SQL Server cannot run. This error is usually preceded by other errors. Review error logs to find the root cause.

   
User Action

Restore backup of the database or repair the database.

   
   
Version: 9.0
Component: SQLEngine
Symbolic Name: REC_BADMASTER
Message: Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
   
Explanation

SQL Server cannot start the
master
database. If the
master
or
tempdb
cannot be brought online, SQL Server cannot run. This error is usually preceded by other errors. Review error logs to find the root cause.

   
User Action

Restore backup of the database or repair the database.

   
   
Version: 8.0
Component: SQL Engine
Message: Cannot recover the master database. Exiting.
   
Explanation
The master database is not in a recoverable state.
   
User Action
HARDWARE FAILURE

Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows NT system and application logs and the SQL Server error log to see if the error occurred as the result of hardware failure. Fix any hardware related problems.

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

Finally, you might find it beneficial to switch to a completely new hardware system, including 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.

DBCC CHECKDB

If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC CHECKDB with the appropriate repair clause to repair the corruption.

CAUTION: If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider before executing this statement.

If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your primary support provider.

Related:

Could not allocate space for object ‘%.*ls’ in database ‘%.*ls’ because the ‘%.*ls’ filegroup is full.

Details
Product: SQL Server
Event ID: 1105
Source: MSSQLServer
Version: 10.0
Component: SQLEngine
Symbolic Name: NO_MORE_SPACE_IN_FG
Message: Could not allocate space for object ‘%.*ls’%.*ls in database ‘%.*ls’ because the ‘%.*ls’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
   
Explanation

No disk space is available in a filegroup.

   
User Action

The following actions may make space available in the filegroup:

  • Turn on autogrow.

  • Add more files to the file group.

  • Free disk space by dropping index or tables that are no longer needed.

  • For more information, see “Troubleshooting Insufficient Data Disk Space” in SQL Server Books Online.

   
   
Version: 9.00.1281.60
Symbolic Name: NO_MORE_SPACE_IN_FG
Message: Could not allocate space for object ‘%.*ls’%.*ls in database ‘%.*ls’ because the ‘%.*ls’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
   
Explanation

No disk space is available in a filegroup.

   
User Action

The following actions may make space available in the filegroup:

  • Turn on autogrow.

  • Add more files to the file group.

  • Free disk space by dropping index or tables that are no longer needed.

  • For more information, see “Troubleshooting Insufficient Data Disk Space” in SQL Server Books Online.

   
   
Version: 9.0
Component: SQLEngine
Symbolic Name: NO_MORE_SPACE_IN_FG
Message: Could not allocate space for object ‘%.*ls’%.*ls in database ‘%.*ls’ because the ‘%.*ls’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
   
Explanation

No disk space is available in a filegroup.

   
User Action

The following actions may make space available in the filegroup:

Turn on autogrow.

Add more files to the file group.

Free disk space by dropping index or tables that are no longer needed.

For more information, see “Troubleshooting Insufficient Data Disk Space” in SQL Server Books Online.

   
   
Version: 8.0
Component: SQL Engine
Message: Could not allocate space for object ‘%.*ls’ in database ‘%.*ls’ because the ‘%.*ls’ filegroup is full.
   
Explanation

The specified filegroup has run out of free space.

   
User Action

To gain more space, you can free disk space on any disk drive containing a file in the full filegroup, allowing files in the group to grow. Or you can gain space using a data file with the specified database.

Freeing disk space

You can free disk space on your local drive or on another disk drive. To free disk space on another drive:

  1. Move the data files in the filegroup with an insufficient amount of free disk space to a different disk drive.
  2. Detach the database by executing sp_detach_db.
  3. Attach the database by executing sp_attach_db, pointing to the moved files.

Using a data file

Another solution is to add a data file to the specified database using the ADD FILE clause of the ALTER DATABASE statement. Or you can enlarge the data file by using the MODIFY FILE clause of the ALTER DATABASE statement, specifying the SIZE and MAXSIZE syntax.

Related:

%1: %2 failure on backup device ‘%3’. Operating system error %4.

Details
Product: SQL Server
Event ID: 18210
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: %1: %2 failure on backup device ‘%3’. Operating system error %4.
   
Explanation
This message indicates that an I/O error was reported by the operating system after a file handle was successfully opened. The error occurs when reading from or writing to a device specified as part of a BACKUP or RESTORE command, often when there is not enough disk space available for a write operation. This error may also be seen if third-party software that uses a virtual device to perform SQL Server backups cancels the operation.
   
User Action
The steps to take will depend upon the operating system error received.

  • Verify that the specified path has sufficient disk space for the file.
  • Test to see if the problem is isolated to this particular server, path, or file.
  • Run hardware diagnostics to verify that the media specified in the path is healthy.
  • If the operating system error only returns a number and not any text, you can open a command prompt and execute NET HELPMSG with the operating system error number as the parameter. In many cases, this will return text that can help you to isolate the problem.
  • If you received this error while using third-party backup software, check that application’s logs to see if it canceled the backup operation, and if so, why.

Related:

%1: Backup device ‘%2’ failed to %3. Operating system error = %4.

Details
Product: SQL Server
Event ID: 18204
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: %1: Backup device ‘%2’ failed to %3. Operating system error = %4.
   
Explanation
This message indicates that the operating system was unable to open or close a backup device (disk, tape, or pipe) specified as part of a BACKUP or RESTORE command. For more information on backup devices, refer to the Books Online topics, “Backup Devices” and “BACKUP.”
   
User Action
The steps to take will depend upon the operating system error received.

  • Cut and paste the path and file name specified in the BACKUP or RESTORE command into Windows Explorer. This will help to verify that the path is actually valid.
  • If you specify a mapped drive in the command, switch to a UNC instead and retry the command. In most cases, a service such as SQL Server Agent is not aware of drives that are mapped for individual Windows users, so a service is usually not able to execute commands that involve a mapped drive.
  • Verify that the Windows account used to start the SQL Server service has permissions to access the server specified and to traverse through the specified path. Also verify that this account has the permissions necessary to open the file for the specified type of operation.
  • If you are accessing a file that already exists, ensure that the file is not locked by another process and that it is not marked as read-only.
  • Test to see if the problem is isolated to this particular server, path, or file.
  • Run hardware diagnostics to verify that the media specified in the path is healthy.
  • If the operating system error only returns a number and not any text, you can open a command prompt and execute NET HELPMSG with the operating system error number as the parameter. In many cases, this will return text that can help you to isolate the problem.

Related: