SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 New to SQL Server Administration
 adventureworks2008 database suspected
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

liveinla
Starting Member

5 Posts

Posted - 12/19/2013 :  02:26:02  Show Profile  Reply with Quote
I am learning SQL using an evaluation CD in a book. I have successfully install the SQL 2008 server on my computer running on Vista, but a few days later I found out that one of the sample database is marked with suspected? I am very new to this, would someone give me some idea how to avoid it in the future and how to fix it.
Is it because I use different account name for my computer log-in and server log-in?

2013-11-28 22:19:00.35 Server (c) 2005 Microsoft Corporation.
2013-11-28 22:19:00.35 Server All rights reserved.
2013-11-28 22:19:00.35 Server Server process ID is 2516.
2013-11-28 22:19:00.35 Server System Manufacturer: 'Hewlett-Packard', System Model: 'HP Pavilion dv6700 Notebook PC'.
2013-11-28 22:19:00.35 Server Authentication mode is MIXED.
2013-11-28 22:19:00.35 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2013-11-28 22:19:00.35 Server This instance of SQL Server last reported using a process ID of 2356 at 11/28/2013 11:18:38 AM (local) 11/28/2013 7:18:38 PM (UTC). This is an informational message only; no user action is required.
2013-11-28 22:19:00.35 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2013-11-28 22:19:00.36 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-11-28 22:19:00.36 Server Detected 2 CPUs. This is an informational message; no user action is required.
2013-11-28 22:19:00.68 Server SQL Server is not configured to use all of the available system memory. To enable SQL Server to use more memory, set the awe enabled option to 1 by using the sp_configure stored procedure.
2013-11-28 22:19:00.97 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.
2013-11-28 22:19:01.37 Server Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-11-28 22:19:01.60 spid7s Starting up database 'master'.
2013-11-28 22:19:01.71 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2013-11-28 22:19:01.76 spid7s Resource governor reconfiguration succeeded.
2013-11-28 22:19:01.76 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2013-11-28 22:19:01.76 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
<{39B75A24-0837-4CEC-AFDF-B960027AE07E}>RsFxNso initialized. InstanceId = 00000001
<{50080099-5EC4-4EAF-A2A2-63C3DA97F8EB}>FsAgent is initialized
<{09C4480B-DBA4-49B7-956F-68A8B8B2445D}>FsAgent is up and running
2013-11-28 22:19:01.77 spid7s FILESTREAM: effective level = 2, configured level = 2, file system access share name = 'MSSQLSERVER'.
2013-11-28 22:19:01.85 spid7s SQL Trace ID 1 was started by login "sa".
2013-11-28 22:19:01.85 spid7s Starting up database 'mssqlsystemresource'.
2013-11-28 22:19:01.90 spid7s The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
2013-11-28 22:19:03.92 spid7s Server name is 'IBM-PC'. This is an informational message only. No user action is required.
2013-11-28 22:19:03.92 spid15s Starting up database 'model'.
2013-11-28 22:19:04.33 Server A self-generated certificate was successfully loaded for encryption.
2013-11-28 22:19:04.36 spid15s Clearing tempdb database.
2013-11-28 22:19:04.44 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2013-11-28 22:19:04.44 Server Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2013-11-28 22:19:04.50 Server Server is listening on [ ::1 <ipv6> 1434].
2013-11-28 22:19:04.50 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2013-11-28 22:19:04.50 Server Dedicated admin connection support was established for listening locally on port 1434.
2013-11-28 22:19:04.52 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2013-11-28 22:19:04.52 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2013-11-28 22:19:04.78 spid15s Starting up database 'tempdb'.
2013-11-28 22:19:05.07 spid19s The Service Broker protocol transport is disabled or not configured.
2013-11-28 22:19:05.07 spid19s The Database Mirroring protocol transport is disabled or not configured.
2013-11-28 22:19:05.09 spid19s Service Broker manager has started.
2013-11-28 22:19:23.00 Logon Error: 18456, Severity: 14, State: 38.
2013-11-28 22:19:23.00 Logon Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-11-28 22:19:24.18 Logon Error: 18456, Severity: 14, State: 38.
2013-11-28 22:19:24.18 Logon Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-11-28 22:19:29.26 Logon Error: 18456, Severity: 14, State: 38.
2013-11-28 22:19:29.26 Logon Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-11-28 22:19:34.66 spid22s Starting up database 'msdb'.
2013-11-28 22:19:34.66 spid23s Starting up database 'ReportServer'.
2013-11-28 22:19:34.66 spid25s Starting up database 'ReportServerTempDB'.
2013-11-28 22:19:34.66 spid26s Starting up database 'Northwind'.
2013-11-28 22:19:34.66 spid27s Starting up database 'AdventureWorks2008'.
2013-11-28 22:19:34.66 spid28s Starting up database 'AdventureWorksDW2008'.
2013-11-28 22:19:34.67 spid29s Starting up database 'Travel'.
2013-11-28 22:19:34.67 spid30s Starting up database 'SQLOnline1'.
2013-11-28 22:19:35.11 spid27s Error: 5511, Severity: 23, State: 10.
2013-11-28 22:19:35.11 spid27s FILESTREAM's file system log record 'placeholder.txt' under log folder '\\?\C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\Documents\$FSLOG' is corrupted.
2013-11-28 22:19:35.12 spid27s Error: 3414, Severity: 21, State: 1.
2013-11-28 22:19:35.12 spid27s An error occurred during recovery, preventing the database 'AdventureWorks2008' (database ID 8) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2013-11-28 22:19:35.31 spid7s Recovery is complete. This is an informational message only. No user action is required.
2013-11-28 22:19:39.64 spid51 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer.
2013-11-28 22:19:39.88 spid51 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServerTempDB.
2013-11-28 22:21:15.11 spid18s A new instance of the full-text filter daemon host process has been successfully started.
2013-11-29 00:00:14.78 spid30s This instance of SQL Server has been using a process ID of 2516 since 11/28/2013 10:19:35 PM (local) 11/29/2013 6:19:35 AM (UTC). This is an informational message only; no user action is required.
2013-11-29 16:34:10.11 spid53 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer.
2013-11-29 16:34:10.61 spid53 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServerTempDB.
2013-11-29 20:57:01.20 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2013-11-29 20:57:11.92 Logon Error: 18456, Severity: 14, State: 23.
2013-11-29 20:57:11.92 Logon Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Access to server validation failed while revalidating the login on the connection. [CLIENT: <local machine>]
2013-11-29 20:57:12.99 spid51 Error: 17054, Severity: 16, State: 1.
2013-11-29 20:57:12.99 spid51 The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
2013-11-29 20:57:13.21 spid51 Error: 18056, Severity: 20, State: 23.
2013-11-29 20:57:13.21 spid51 The client was unable to reuse a session with SPID 51, which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
2013-11-29 20:57:24.19 spid19s Service Broker manager has shut down.
2013-11-29 20:57:28.93 spid7s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Sorry for the log post and thanks in advance,

dave

Edited by - liveinla on 12/19/2013 03:05:37

tkizer
Almighty SQL Goddess

USA
36594 Posts

Posted - 12/19/2013 :  13:05:02  Show Profile  Visit tkizer's Homepage  Reply with Quote
It looks like you might have a hardware issue. You'll need to run disk diagnostics and also check the event log.

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

liveinla
Starting Member

5 Posts

Posted - 12/19/2013 :  19:15:38  Show Profile  Reply with Quote
thanks tara,

I found on the web there were many people has the same problem with the CD ( Microsoft SQL Server 2008 Database Development 70-433 Training kit ).

I delete the suspected database, and copy the database from the CD again. It works for now, but I know after a while, the adventureWorks2008 database would be put in suspected state again.

I still want to get to the bottom of this, here is what I find in the event log after I ran the chkdsk (after I did the above); I only list the errors in the log.

1) Failed to unload app domain DefaultDomain. The following exception occurred: Error while unloading appdomain. (Exception from HRESULT: 0x80131015). Source: SQL Server Reporting Services (MSSQLSERVER)

2)Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.

Warning:
1)
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

DETAIL -
2 user registry handles leaked from \Registry\User\S-1-5-21-2068968968-3818898803-2217961339-1000:
Process 1112 (\Device\HarddiskVolume1\Program Files\Tencent\QQPCMgr\8.7.10488.206\QQPCRTP.exe) has opened key \REGISTRY\USER\S-1-5-21-2068968968-3818898803-2217961339-1000
Process 1112 (\Device\HarddiskVolume1\Program Files\Tencent\QQPCMgr\8.7.10488.206\QQPCRTP.exe) has opened key \REGISTRY\USER\S-1-5-21-2068968968-3818898803-2217961339-1000\Software\Microsoft\Windows\CurrentVersion\Uninstall
Event ID: 1530




Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.06 seconds. Powered By: Snitz Forums 2000