SQL Server Performance

Can't bring Server up (sqlservr.exe -c -T3608)

Discussion in 'SQL Server 2005 General DBA Questions' started by nupe02, Feb 8, 2009.

  1. nupe02 New Member

    My msdb was hose so from the comma prompt I typed "sqlservr.exe -c -T3608), because I was going to recreate a new one.
    after waiting about 2hrs, I try to start it up in "Services" but I got :
    Error: 8355, Severity: 16, State: 1.
    2009-02-08 08:41:05.26 spid5s Server-level event notifications can not be delivered. Either Service Broker is disabled in msdb, or msdsb failed to start. Event notifications in other databases could be affected as well. Bring msdb online, or enable Service Broker.
    2009-02-08 08:41:05.26 spid5s Recovery is complete. This is an informational message only. No user action is required.
    could get it to come up in manage studio either. But at the commad window where I type the sqlservr...statement it display this message:

    2009-02-08 10:39:50.79 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
    2009-02-08 10:39:50.80 Server Dedicated admin connection support was established for listening locally on port 1434.
    2009-02-08 10:39:51.04 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098, state: 15. 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-02-08 10:39:51.04 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2009-02-08 10:39:51.05 spid19s Starting up database 'msdb'.
    2009-02-08 10:39:51.05 spid19s Error: 17207, Severity: 16, State: 1.
    2009-02-08 10:39:51.05 spid19s FCB::Open: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'C:program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAMSDBData.mdf'. Diagnose and correct the operating system error, and retry the operation.
    2009-02-08 10:39:51.05 spid19s Error: 17204, Severity: 16, State: 1.
    2009-02-08 10:39:51.05 spid19s FCB::Open failed: Could not open file C:program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAMSDBData.mdf for file number 1. OS error: 2(The system cannot find the file specified.).
    2009-02-08 10:39:51.05 spid19s Error: 5120, Severity: 16, State: 101.
    2009-02-08 10:39:51.05 spid19s Unable to open the physical file "C:program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAMSDBData.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
    2009-02-08 10:39:51.07 spid19s Error: 17207, Severity: 16, State: 1.
    2009-02-08 10:39:51.07 spid19s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'C:program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAMSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.
    2009-02-08 10:39:51.07 spid19s File activation failure. The physical file name "C:program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAMSDBLog.ldf" may be incorrect.
    2009-02-08 10:39:53.93 spid18s CHECKDB for database 'XXXXX' finished without errors on 2007-08-28 10:39:42.473 (local time). This is an informational message only; no user action is required.
    2009-02-08 10:39:53.94 spid4s Error: 8355, Severity: 16, State: 1.
    2009-02-08 10:39:53.94 spid4s Server-level event notifications can not be delivered. Either Service Broker is disabled in msdb, or msdsb failed to start. Event notifications in other databases could be affected as well. Bring msdb online, or enable Service Broker.
    2009-02-08 10:39:53.94 spid4s Recovery is complete. This is an informational message only. No user action is required.
    2009-02-08 10:39:54.10 spid51s Using 'xpstar90.dll' version '2005.90.3042' to execute extended stored procedure 'xp_regdeletevalue'. This is an informational message only; no user action is required.
    2009-02-08 10:39:54.29 spid51s SQL Trace ID 2 was started by login "sa".
    2009-02-08 10:39:54.30 spid51s SQL Trace ID 3 was started by login "sa".
    2009-02-08 10:39:54.33 spid51s SQL Trace ID 4 was started by login "sa".
    2009-02-08 10:45:36.91 spid52 Using 'xplog70.dll' version '2005.90.3042' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
    and seems to be hanging, I have no commad prompt yet What To Do, should I keep waitting a few more hour? HELP.
  2. rohit2900 Member

Share This Page