Over the weekend I noticed a schedule DB integrity check failing. The DB size is about 225GB and in the past have had no issues. At first I received two emails with errors like this:[quote]DESCRIPTION: Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x80004005. You need to restart SQL Server to use CLR integration features.DESCRIPTION: A read of the file 'E:\VDBs\CORELIBRARY.mdf' at offset 0x000004c44f0000 succeeded after failing 3 time(s) with error: 23(Data error (cyclic redundancy check).). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.[/quote]Which I thought was odd, and after looking at the job that ran the CHECKDB, I decided to run it myself:[code="sql"]DBCC CHECKDB('SSRS') WITH ALL_ERRORMSGS , NO_INFOMSGS[/code]This was the output:[quote]Msg 6512, Level 16, State 27, Line 6Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x80004005. You need to restart SQL Server to use CLR integration features.Msg 6512, Level 16, State 27, Line 6Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x80004005. You need to restart SQL Server to use CLR integration features.[/quote]There's no other messages outputted to the screen.Has anyone encountered this error before when running a DBCC CHECKDB?
↧