Part of Slepp's Projects — Pastebin — TURL — Imagebin — Filebin
Feedback -- English French German Japanese
Create Upload Newest Tools Donate
Sign In | Create Account

Paste Actions

Download Raw
Embed
pBox URL
Post to Twitter
Remove Paste

Paste Details

Raw format, 1 year 5 days old, and 97 hits.

Advertising

Miscellany
Wednesday, May 16th, 2012 at 12:08:33pm MDT 

  1. 2012-05-16 13:49:23.28 Server      Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
  2.         Nov 24 2008 13:01:59
  3.         Copyright (c) 1988-2005 Microsoft Corporation
  4.         Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
  5.  
  6. 2012-05-16 13:49:23.28 Server      (c) 2005 Microsoft Corporation.
  7. 2012-05-16 13:49:23.28 Server      All rights reserved.
  8. 2012-05-16 13:49:23.28 Server      Server process ID is 2988.
  9. 2012-05-16 13:49:23.28 Server      Authentication mode is MIXED.
  10. 2012-05-16 13:49:23.28 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\LOG\ERRORLOG'.
  11. 2012-05-16 13:49:23.28 Server      This instance of SQL Server last reported using a process ID of 5880 at 5/16/2012 1:48:21 PM (local) 5/16/2012 5:48:21 PM (UTC). This is an informational message only; no user action is required.
  12. 2012-05-16 13:49:23.28 Server      Registry startup parameters:
  13. 2012-05-16 13:49:23.28 Server            -d C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\master.mdf
  14. 2012-05-16 13:49:23.28 Server            -e C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\LOG\ERRORLOG
  15. 2012-05-16 13:49:23.28 Server            -l C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\mastlog.ldf
  16. 2012-05-16 13:49:23.29 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
  17. 2012-05-16 13:49:23.29 Server      Detected 4 CPUs. This is an informational message; no user action is required.
  18. 2012-05-16 13:49:23.35 Server      Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.
  19. 2012-05-16 13:49:23.47 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
  20. 2012-05-16 13:49:23.63 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
  21. 2012-05-16 13:49:25.76 Server      Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
  22. 2012-05-16 13:49:25.76 Server      Database mirroring has been enabled on this instance of SQL Server.
  23. 2012-05-16 13:49:25.77 spid5s      Starting up database 'master'.
  24. 2012-05-16 13:49:25.82 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
  25. 2012-05-16 13:49:25.91 spid5s      SQL Trace ID 1 was started by login "sa".
  26. 2012-05-16 13:49:25.93 spid5s      Starting up database 'mssqlsystemresource'.
  27. 2012-05-16 13:49:25.94 spid5s      The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
  28. 2012-05-16 13:49:26.11 spid5s      Server name is 'NTFS4\SQL2005'. This is an informational message only. No user action is required.
  29. 2012-05-16 13:49:26.11 spid9s      Starting up database 'model'.
  30. 2012-05-16 13:49:26.53 Server      The certificate was successfully loaded for encryption.
  31. 2012-05-16 13:49:26.57 Server      Server is listening on [ 'any' <ipv4> 2270].
  32. 2012-05-16 13:49:26.57 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQL2005 ].
  33. 2012-05-16 13:49:26.57 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQL2005\sql\query ].
  34. 2012-05-16 13:49:26.57 Server      Server is listening on [ 127.0.0.1 <ipv4> 2271].
  35. 2012-05-16 13:49:26.57 Server      Dedicated admin connection support was established for listening locally on port 2271.
  36. 2012-05-16 13:49:26.59 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
  37. 2012-05-16 13:49:26.88 spid12s     Starting up database 'msdb'.
  38. 2012-05-16 13:49:26.88 spid14s     Starting up database 'MHCSecurity'.
  39. 2012-05-16 13:49:26.88 spid13s     Starting up database 'MHC'.
  40. 2012-05-16 13:49:26.93 Logon       Error: 18456, Severity: 14, State: 16.
  41. 2012-05-16 13:49:26.93 Logon       Login failed for user 'sa'. [CLIENT: 10.20.30.104]
  42. 2012-05-16 13:49:26.93 Logon       Error: 18456, Severity: 14, State: 16.
  43. 2012-05-16 13:49:26.93 Logon       Login failed for user 'sa'. [CLIENT: 10.20.30.104]
  44. 2012-05-16 13:49:26.93 spid15s     Starting up database 'MHC_2005'.
  45. 2012-05-16 13:49:26.93 spid16s     Starting up database 'MHCSecurity_2005'.
  46. 2012-05-16 13:49:28.08 spid9s      Clearing tempdb database.
  47. 2012-05-16 13:49:29.67 spid14s     CHECKDB for database 'MHCSecurity' finished without errors on 2012-04-16 22:00:00.703 (local time). This is an informational message only; no user action is required.
  48. 2012-05-16 13:49:29.99 spid9s      Starting up database 'tempdb'.
  49. 2012-05-16 13:49:30.03 spid12s     The Service Broker protocol transport is disabled or not configured.
  50. 2012-05-16 13:49:30.03 spid12s     The Database Mirroring protocol transport is disabled or not configured.
  51. 2012-05-16 13:49:30.03 spid12s     Service Broker manager has started.
  52. 2012-05-16 13:49:30.05 Logon       Error: 18456, Severity: 14, State: 16.
  53. 2012-05-16 13:49:30.05 Logon       Login failed for user 'sa'. [CLIENT: 10.20.30.104]
  54. 2012-05-16 13:49:33.41 spid13s     Analysis of database 'MHC' (5) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
  55. 2012-05-16 13:49:33.76 spid13s     25 transactions rolled forward in database 'MHC' (5). This is an informational message only. No user action is required.
  56. 2012-05-16 13:49:33.82 spid13s     0 transactions rolled back in database 'MHC' (5). This is an informational message only. No user action is required.
  57. 2012-05-16 13:49:33.82 spid13s     Recovery is writing a checkpoint in database 'MHC' (5). This is an informational message only. No user action is required.
  58. 2012-05-16 13:49:34.02 spid13s     CHECKDB for database 'MHC' finished without errors on 2012-04-16 22:00:00.950 (local time). This is an informational message only; no user action is required.
  59. 2012-05-16 13:49:34.65 spid5s      Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
  60. 2012-05-16 13:49:34.65 spid5s      Recovery is complete. This is an informational message only. No user action is required.
  61. 2012-05-16 13:49:34.84 spid27s     Error: 28005, Severity: 16, State: 2.
  62. 2012-05-16 13:49:34.84 spid27s     An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.
  63. 2012-05-16 13:49:34.84 spid19s     Error: 28005, Severity: 16, State: 2.
  64. 2012-05-16 13:49:34.84 spid19s     An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.
  65. 2012-05-16 13:49:34.84 spid17s     Error: 28005, Severity: 16, State: 2.
  66. 2012-05-16 13:49:34.84 spid17s     An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.
  67. 2012-05-16 13:49:34.84 spid16s     Error: 28005, Severity: 16, State: 2.
  68. 2012-05-16 13:49:34.84 spid16s     An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.
  69. 2012-05-16 13:49:34.85 spid17s     Error: 28005, Severity: 16, State: 2.
  70. 2012-05-16 13:49:34.85 spid17s     An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.
  71. 2012-05-16 13:49:34.85 spid19s     Error: 28005, Severity: 16, State: 2.
  72. 2012-05-16 13:49:34.85 spid19s     An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.
  73. 2012-05-16 13:49:34.85 spid19s     Error: 28005, Severity: 16, State: 2.
  74. 2012-05-16 13:49:34.85 spid19s     An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.
  75. 2012-05-16 13:49:34.87 spid19s     Error: 28005, Severity: 16, State: 2.
  76. 2012-05-16 13:49:34.87 spid19s     An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.
  77. 2012-05-16 13:49:34.87 spid17s     Error: 28005, Severity: 16, State: 2.
  78. 2012-05-16 13:49:34.87 spid17s     An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.
  79. 2012-05-16 13:49:34.87 spid19s     Error: 28005, Severity: 16, State: 2.
  80. 2012-05-16 13:49:34.87 spid19s     An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.
  81. 2012-05-16 13:49:34.87 spid19s     Error: 28005, Severity: 16, State: 2.
  82. 2012-05-16 13:49:34.87 spid19s     An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.
  83. 2012-05-16 13:49:34.90 spid19s     Error: 28005, Severity: 16, State: 2.

advertising

Update the Post

Either update this post and resubmit it with changes, or make a new post.

You may also comment on this post.

update paste below
details of the post (optional)

Note: Only the paste content is required, though the following information can be useful to others.

Save name / title?

(space separated, optional)



Please note that information posted here will expire by default in one month. If you do not want it to expire, please set the expiry time above. If it is set to expire, web search engines will not be allowed to index it prior to it expiring. Items that are not marked to expire will be indexable by search engines. Be careful with your passwords. All illegal activities will be reported and any information will be handed over to the authorities, so be good.