API tools faq
paste
Advertisement
Guest User

MSSQL_log

a guest
Jun 27th, 2017
76
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.83 KB | None | 0 0
raw download clone embed print report
  1. Msg 5120, Level 16, State 5, Line 1
  2. Unable to open the physical file "D:\HistorianDatabase\TagsAndAlarms\HistorianStorage_20131114_0_2.ndf". Operating system error 2: "2(The system cannot find the file specified.)".
  3. Msg 5120, Level 16, State 5, Line 1
  4. Unable to open the physical file "D:\HistorianDatabase\TagsAndAlarms\HistorianStorage_20131114_0_3.ndf". Operating system error 2: "2(The system cannot find the file specified.)".
  5. Msg 5120, Level 16, State 5, Line 1
  6. Unable to open the physical file "D:\HistorianDatabase\TagsAndAlarms\HistorianStorage_20131114_0_4.ndf". Operating system error 2: "2(The system cannot find the file specified.)".
  7. Msg 5120, Level 16, State 5, Line 1
  8. Unable to open the physical file "D:\HistorianDatabase\TagsAndAlarms\HistorianStorage_20131114_0_6.ndf". Operating system error 2: "2(The system cannot find the file specified.)".
  9. Msg 5173, Level 16, State 1, Line 1
  10. One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup.
  11. Msg 5173, Level 16, State 1, Line 1
  12. One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup.
  13. Msg 5173, Level 16, State 1, Line 1
  14. One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup.
  15. Msg 5173, Level 16, State 1, Line 1
  16. One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup.
  17. Msg 5173, Level 16, State 1, Line 1
  18. One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup.
  19. Msg 945, Level 14, State 2, Line 1
  20. Database 'HistorianStorage' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
  21. Msg 5069, Level 16, State 1, Line 1
  22. ALTER DATABASE statement failed.
  23. Msg 945, Level 14, State 2, Line 2
  24. Database 'HistorianStorage' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
  25. Msg 824, Level 24, State 2, Line 1
  26. SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x00000000; actual signature: 0x61f87350). It occurred during a read of page (21:0) in database ID 7 at offset 0000000000000000 in file 'D:\HistorianDatabase\TagsAndAlarms\HistorianStorage_20131114_0_5.ndf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
  27. Msg 824, Level 24, State 2, Line 1
  28. SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x00000000; actual signature: 0x34233610). It occurred during a read of page (23:0) in database ID 7 at offset 0000000000000000 in file 'D:\HistorianDatabase\TagsAndAlarms\HistorianStorage_20131114_0_7.ndf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
  29. Msg 824, Level 24, State 2, Line 1
  30. SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0xc9bb63f1). It occurred during a read of page (24:0) in database ID 7 at offset 0000000000000000 in file 'D:\HistorianDatabase\TagsAndAlarms\HistorianStorage_20131114_1_8.ndf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
  31. Msg 5243, Level 22, State 8, Line 1
  32. An inconsistency was detected during an internal operation. Please contact technical support.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!