SSRS sevice start with error after clean 2008 install?
in [Server Configuration]
|
From: mttc on 2 Dec 2009 16:23 New machine with 2003 R2 SP2 & SQL 2008 SP1. the SSRS have error to start, and after two fail, the service start. the problem seem like SSRS start before DB start. Here the Log file, and Event msg: 2009-12-01 16:04:21.81 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64) Mar 29 2009 10:11:52 Copyright (c) 1988-2008 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 <X64> (Build 3790: Service Pack 2) 2009-12-01 16:04:21.90 Server (c) 2005 Microsoft Corporation. 2009-12-01 16:04:21.90 Server All rights reserved. 2009-12-01 16:04:21.90 Server Server process ID is 1480. 2009-12-01 16:04:21.90 Server Authentication mode is MIXED. 2009-12-01 16:04:21.90 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log \ERRORLOG'. 2009-12-01 16:04:21.93 Server This instance of SQL Server last reported using a process ID of 1472 at 01/12/09 16:02:38 (local) 01/12/09 14:02:38 (UTC). This is an informational message only; no user action is required. 2009-12-01 16:04:21.93 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 2009-12-01 16:04:22.03 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2009-12-01 16:04:22.03 Server Detected 16 CPUs. This is an informational message; no user action is required. 2009-12-01 16:04:22.13 Server Large Page Extensions enabled. 2009-12-01 16:04:22.14 Server Large Page Granularity: 2097152 2009-12-01 16:04:22.14 Server Large Page Allocated: 32MB 2009-12-01 16:04:22.16 Server Large Page Allocated: 32MB 2009-12-01 16:04:22.49 Server Using locked pages for buffer pool. 2009-12-01 16:04:23.15 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. 2009-12-01 16:04:23.16 Server Lock partitioning is enabled. This is an informational message only. No user action is required. 2009-12-01 16:04:24.34 Server Node configuration: node 0: CPU mask: 0x000000000000ff00 Active CPU mask: 0x000000000000ff00. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 2009-12-01 16:04:24.34 Server Node configuration: node 1: CPU mask: 0x00000000000000ff Active CPU mask: 0x00000000000000ff. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 2009-12-01 16:04:24.63 spid9s Starting up database 'master'. 2009-12-01 16:04:25.14 spid9s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required. 2009-12-01 16:04:25.77 spid9s Resource governor reconfiguration succeeded. 2009-12-01 16:04:25.80 spid9s SQL Server Audit is starting the audits. This is an informational message. No user action is required. 2009-12-01 16:04:25.90 spid9s SQL Server Audit has started the audits. This is an informational message. No user action is required. 2009-12-01 16:04:26.03 spid9s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'. 2009-12-01 16:04:26.70 spid9s SQL Trace ID 1 was started by login "sa". 2009-12-01 16:04:26.76 spid9s Starting up database 'mssqlsystemresource'. 2009-12-01 16:04:26.79 spid9s The resource database build version is 10.00.2531. This is an informational message only. No user action is required. 2009-12-01 16:04:27.09 spid12s Starting up database 'model'. 2009-12-01 16:04:27.10 spid9s Server name is 'D-SERVER'. This is an informational message only. No user action is required. 2009-12-01 16:04:27.41 spid12s Clearing tempdb database. 2009-12-01 16:04:27.49 spid12s Starting up database 'tempdb'. 2009-12-01 16:04:27.79 spid15s The Service Broker protocol transport is disabled or not configured. 2009-12-01 16:04:27.79 spid15s The Database Mirroring protocol transport is disabled or not configured. 2009-12-01 16:04:27.83 Server A self-generated certificate was successfully loaded for encryption. 2009-12-01 16:04:27.86 Server Server is listening on [ 'any' <ipv4> 1433]. 2009-12-01 16:04:27.90 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. 2009-12-01 16:04:27.90 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ]. 2009-12-01 16:04:27.92 Server Server is listening on [ 127.0.0.1 <ipv4> 1434]. 2009-12-01 16:04:27.92 Server Dedicated admin connection support was established for listening locally on port 1434. 2009-12-01 16:04:27.94 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. 2009-12-01 16:04:27.94 Server SQL Server is now ready for client connections. This is an informational message; no user action is required. 2009-12-01 16:04:27.95 spid15s Service Broker manager has started. 2009-12-01 16:04:28.42 Logon Error: 18456, Severity: 14, State: 38. 2009-12-01 16:04:28.42 Logon Login failed for user 'NT AUTHORITY \SYSTEM'. Reason: Failed to open the explicitly specified database. [CLIENT: 10.0.0.4] 2009-12-01 16:04:29.32 Logon Error: 18456, Severity: 14, State: 38. 2009-12-01 16:04:29.32 Logon Login failed for user 'NT AUTHORITY \SYSTEM'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>] 2009-12-01 16:04:34.45 Logon Error: 18456, Severity: 14, State: 38. 2009-12-01 16:04:34.45 Logon Login failed for user 'NT AUTHORITY \SYSTEM'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>] 2009-12-01 16:04:44.46 Logon Error: 18456, Severity: 14, State: 38. 2009-12-01 16:04:44.46 Logon Login failed for user 'NT AUTHORITY \SYSTEM'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>] 2009-12-01 16:04:57.89 spid19s Starting up database 'msdb'. 2009-12-01 16:04:57.89 spid22s Starting up database 'ReportServerTempDB'. 2009-12-01 16:04:57.89 spid21s Starting up database 'shuvunew'. 2009-12-01 16:04:57.89 spid20s Starting up database 'ReportServer'. 2009-12-01 16:05:00.36 spid9s Recovery is complete. This is an informational message only. No user action is required. 2009-12-01 16:05:05.27 spid51 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer. 2009-12-01 16:05:05.33 spid51 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServerTempDB. On App Event ================================= Event Type: Failure Audit Event Source: MSSQLSERVER Event Category: Logon Event ID: 18456 Date: 02/12/09 Time: 08:22:48 User: NT AUTHORITY\SYSTEM Computer: D-SERVER Description: Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>] For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: MSSQLSERVER Event Category: Server Event ID: 17137 Date: 02/12/09 Time: 08:23:02 User: N/A Computer: D-SERVER Description: Starting up database 'ReportServerTempDB'. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: MSSQLSERVER Event Category: Server Event ID: 17137 Date: 02/12/09 Time: 08:23:02 User: N/A Computer: D-SERVER Description: Starting up database 'ReportServer'. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: MSSQLSERVER Event Category: Server Event ID: 17137 Date: 02/12/09 Time: 08:23:02 User: N/A Computer: D-SERVER Description: Starting up database 'msdb'. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: MSSQLSERVER Event Category: Server Event ID: 3408 Date: 02/12/09 Time: 08:23:05 User: N/A Computer: D-SERVER Description: Recovery is complete. This is an informational message only. No user action is required. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: MSSQLSERVER Event Category: Server Event ID: 5084 Date: 02/12/09 Time: 08:23:09 User: NT AUTHORITY\SYSTEM Computer: D-SERVER Description: Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: MSSQLSERVER Event Category: Server Event ID: 5084 Date: 02/12/09 Time: 08:23:09 User: NT AUTHORITY\SYSTEM Computer: D-SERVER Description: Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServerTempDB. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: SQL Server Reporting Services (MSSQLSERVER) Event Category: None Event ID: 0 Date: 02/12/09 Time: 08:23:53 User: N/A Computer: D-SERVER Description: Service started successfully. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. And on System Event ======================= Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7022 Date: 02/12/09 Time: 08:23:52 User: N/A Computer: D-SERVER Description: The SQL Server Reporting Services (MSSQLSERVER) service hung on starting. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: Service Control Manager Event Category: None Event ID: 7036 Date: 02/12/09 Time: 08:23:53 User: N/A Computer: D-SERVER Description: The SQL Server Reporting Services (MSSQLSERVER) service entered the running state. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. After some minut I see more one Error, I not sure if it blong to main problem: Event Type: Error Event Source: DCOM Event Category: None Event ID: 10016 Date: 02/12/09 Time: 08:40:53 User: NT AUTHORITY\NETWORK SERVICE Computer: D-SERVER Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {BA126AD1-2166-11D1-B1D0-00805FC1270E} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
|
Pages: 1 Prev: Urgent linked server error 18456 issue Next: Reducing a database |