SQL Server service would not start

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2005 Forums

SQL Server Administration (2005)

SQL Server service would not start

Author

Topic

jzurbo77
Starting Member

21 Posts

Posted - 2010-05-01 : 22:55:56

Hi
Looks like I got a table corrupted in a database. I then truncated the table and pasted data into it from a backup copy. The paste operation was working slow but finished OK and I was able to query it just fine (from Management Studio). But then I lost connection to the SQL Server. Checked Services - it is stopped. Tried to restart - it fails (timeout). I renamed files with "offending" database hoping that Server will come up without it - no luck. What should I do? I hope not reinstall the whole server...
Thanks
John

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-05-02 : 04:27:09

What's in the latest error log? The service will always attempt to start, and it will log any problems it has into the error log.

Error log's just a text file. File name is ERRORLOG. Where it is depends on how you installed SQL.

--
Gail Shaw
SQL Server MVP

jzurbo77
Starting Member

21 Posts

Posted - 2010-05-02 : 08:50:03

I found ERRORLOG, actually two of them, one for MSSQL.1 (probably my SQL Server S2005A) and another for MSSQL.4 (probably SQLEXPRESS).

Latest entries in MSSQL.1 are
( nothing after 2010-05-01 16:51:54.61 even though I tried to start the servoce few times... should I clear Windows Log? How do I know if it is full?)

External dump process returned no errors.

2010-05-01 15:41:32.79 spid57 Error: 5242, Severity: 22, State: 1.
2010-05-01 15:41:32.79 spid57 An inconsistency was detected during an internal operation in database 'MOCDEV_Local'(ID:9) on page (1:2959). Please contact technical support. Reference number 4.
2010-05-01 15:41:32.84 spid57 ex_raise2: Exception raised, major=52, minor=42, state=1, severity=22, attempting to create symptom dump
2010-05-01 15:41:32.85 spid57 Using 'dbghelp.dll' version '4.0.5'
2010-05-01 15:41:32.85 spid57 **Dump thread - spid = 57, PSS = 0x06539350, EC = 0x06539358
2010-05-01 15:41:32.85 spid57 *
2010-05-01 15:41:32.85 spid57 * User initiated stack dump. This is not a server exception dump.
2010-05-01 15:41:32.85 spid57 *
2010-05-01 15:41:32.85 spid57 ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0058.txt
2010-05-01 15:41:32.85 spid57 * *******************************************************************************
2010-05-01 15:41:32.85 spid57 *
2010-05-01 15:41:32.85 spid57 * BEGIN STACK DUMP:
2010-05-01 15:41:32.85 spid57 * 05/01/10 15:41:32 spid 57
2010-05-01 15:41:32.85 spid57 *
2010-05-01 15:41:32.85 spid57 * ex_raise2: Exception raised, major=52, minor=42, state=1, severity=22
2010-05-01 15:41:32.85 spid57 *
2010-05-01 15:41:32.85 spid57 * Input Buffer 160 bytes -
2010-05-01 15:41:32.85 spid57 * delete from stg_SAP_Func_LocT where substring(Funct_Loc,1,2)
2010-05-01 15:41:32.85 spid57 * != 'so'
2010-05-01 15:41:32.86 spid57 *
2010-05-01 15:41:32.86 spid57 *
2010-05-01 15:41:32.86 spid57 * MODULE BASE END SIZE
2010-05-01 15:41:32.86 spid57 * sqlservr 01000000 02C1FFFF 01c20000
2010-05-01 15:41:32.86 spid57 * ntdll 7C900000 7C9AEFFF 000af000
2010-05-01 15:41:32.86 spid57 * kernel32 7C800000 7C8F5FFF 000f6000
2010-05-01 15:41:32.86 spid57 * MSVCR80 78130000 781CAFFF 0009b000
2010-05-01 15:41:32.86 spid57 * msvcrt 77C10000 77C67FFF 00058000
2010-05-01 15:41:32.86 spid57 * MSVCP80 7C420000 7C4A6FFF 00087000
2010-05-01 15:41:32.86 spid57 * ADVAPI32 77DD0000 77E6AFFF 0009b000
2010-05-01 15:41:32.86 spid57 * RPCRT4 77E70000 77F01FFF 00092000
2010-05-01 15:41:32.86 spid57 * Secur32 77FE0000 77FF0FFF 00011000
2010-05-01 15:41:32.86 spid57 * sqlos 344D0000 344D4FFF 00005000
2010-05-01 15:41:32.86 spid57 * USERENV 769C0000 76A73FFF 000b4000
2010-05-01 15:41:32.86 spid57 * USER32 7E410000 7E4A0FFF 00091000
2010-05-01 15:41:32.86 spid57 * GDI32 77F10000 77F58FFF 00049000
2010-05-01 15:41:32.86 spid57 * WINMM 76B40000 76B6CFFF 0002d000
2010-05-01 15:41:32.86 spid57 * opends60 333E0000 333E6FFF 00007000
2010-05-01 15:41:32.86 spid57 * NETAPI32 5B860000 5B8B4FFF 00055000
2010-05-01 15:41:32.86 spid57 * IMM32 76390000 763ACFFF 0001d000
2010-05-01 15:41:32.86 spid57 * psapi 76BF0000 76BFAFFF 0000b000
2010-05-01 15:41:32.86 spid57 * instapi 48060000 48069FFF 0000a000
2010-05-01 15:41:32.86 spid57 * sqlevn70 4F610000 4F7B8FFF 001a9000
2010-05-01 15:41:32.86 spid57 * rsaenh 68000000 68035FFF 00036000
2010-05-01 15:41:32.86 spid57 * AUTHZ 776C0000 776D1FFF 00012000
2010-05-01 15:41:32.86 spid57 * MSCOREE 33D60000 33DA5FFF 00046000
2010-05-01 15:41:32.86 spid57 * ole32 774E0000 7761CFFF 0013d000
2010-05-01 15:41:32.86 spid57 * msv1_0 77C70000 77C93FFF 00024000
2010-05-01 15:41:32.86 spid57 * iphlpapi 76D60000 76D78FFF 00019000
2010-05-01 15:41:32.86 spid57 * WS2_32 71AB0000 71AC6FFF 00017000
2010-05-01 15:41:32.86 spid57 * WS2HELP 71AA0000 71AA7FFF 00008000
2010-05-01 15:41:32.86 spid57 * kerberos 71CF0000 71D3BFFF 0004c000
2010-05-01 15:41:32.86 spid57 * cryptdll 76790000 7679BFFF 0000c000
2010-05-01 15:41:32.86 spid57 * MSASN1 77B20000 77B31FFF 00012000
2010-05-01 15:41:32.86 spid57 * schannel 767F0000 76816FFF 00027000
2010-05-01 15:41:32.86 spid57 * CRYPT32 77A80000 77B14FFF 00095000
2010-05-01 15:41:32.86 spid57 * COMRES 77050000 77114FFF 000c5000
2010-05-01 15:41:32.86 spid57 * XOLEHLP 34070000 34075FFF 00006000
2010-05-01 15:41:32.86 spid57 * MSDTCPRX 6E560000 6E5CBFFF 0006c000
2010-05-01 15:41:32.86 spid57 * MSVCP60 76080000 760E4FFF 00065000
2010-05-01 15:41:32.86 spid57 * MTXCLU 750F0000 75102FFF 00013000
2010-05-01 15:41:32.86 spid57 * VERSION 77C00000 77C07FFF 00008000
2010-05-01 15:41:32.86 spid57 * WSOCK32 71AD0000 71AD8FFF 00009000
2010-05-01 15:41:32.86 spid57 * CLUSAPI 76D10000 76D21FFF 00012000
2010-05-01 15:41:32.86 spid57 * OLEAUT32 77120000 771AAFFF 0008b000
2010-05-01 15:41:32.86 spid57 * RESUTILS 750B0000 750C1FFF 00012000
2010-05-01 15:41:32.86 spid57 * FwcWsp 34090000 340C4FFF 00035000
2010-05-01 15:41:32.86 spid57 * mswsock 71A50000 71A8EFFF 0003f000
2010-05-01 15:41:32.86 spid57 * DNSAPI 76F20000 76F46FFF 00027000
2010-05-01 15:41:32.86 spid57 * winrnr 76FB0000 76FB7FFF 00008000
2010-05-01 15:41:32.86 spid57 * WLDAP32 76F60000 76F8BFFF 0002c000
2010-05-01 15:41:32.86 spid57 * hnetcfg 343A0000 343F7FFF 00058000
2010-05-01 15:41:32.86 spid57 * SHLWAPI 77F60000 77FD5FFF 00076000
2010-05-01 15:41:32.86 spid57 * comctl32 773D0000 774D2FFF 00103000
2010-05-01 15:41:32.86 spid57 * comctl32 66B90000 66C29FFF 0009a000
2010-05-01 15:41:32.86 spid57 * wshtcpip 71A90000 71A97FFF 00008000
2010-05-01 15:41:32.86 spid57 * rasadhlp 76FC0000 76FC5FFF 00006000
2010-05-01 15:41:32.86 spid57 * security 71F80000 71F83FFF 00004000
2010-05-01 15:41:32.86 spid57 * msfte 674D0000 67728FFF 00259000
2010-05-01 15:41:32.86 spid57 * dbghelp 67730000 67844FFF 00115000
2010-05-01 15:41:32.86 spid57 * WINTRUST 76C30000 76C5DFFF 0002e000
2010-05-01 15:41:32.86 spid57 * IMAGEHLP 76C90000 76CB7FFF 00028000
2010-05-01 15:41:32.86 spid57 * xpsp2res 67B40000 67E04FFF 002c5000
2010-05-01 15:41:32.86 spid57 * dssenh 68100000 68125FFF 00026000
2010-05-01 15:41:32.86 spid57 * NTMARTA 77690000 776B0FFF 00021000
2010-05-01 15:41:32.86 spid57 * SAMLIB 71BF0000 71C02FFF 00013000
2010-05-01 15:41:32.86 spid57 * ntdsapi 767A0000 767B2FFF 00013000
2010-05-01 15:41:32.86 spid57 * CLBCATQ 76FD0000 7704EFFF 0007f000
2010-05-01 15:41:32.86 spid57 * sqlncli 68130000 68356FFF 00227000
2010-05-01 15:41:32.86 spid57 * comdlg32 763B0000 763F8FFF 00049000
2010-05-01 15:41:32.86 spid57 * SHELL32 7C9C0000 7D1D6FFF 00817000
2010-05-01 15:41:32.86 spid57 * SQLNCLIR 00800000 00832FFF 00033000
2010-05-01 15:41:32.86 spid57 * HIPIS0e0015b 687F0000 68805FFF 00016000
2010-05-01 15:41:32.86 spid57 * hipi 67E50000 67E83FFF 00034000
2010-05-01 15:41:32.86 spid57 * HIPQA 6AF70000 6AF78FFF 00009000
2010-05-01 15:41:32.86 spid57 * mfehida 680E0000 680E6FFF 00007000
2010-05-01 15:41:32.86 spid57 * HcApi 68940000 6894DFFF 0000e000
2010-05-01 15:41:32.86 spid57 * KevlarSigs 68960000 68980FFF 00021000
2010-05-01 15:41:32.86 spid57 * Apphelp 77B40000 77B61FFF 00022000
2010-05-01 15:41:32.86 spid57 * xpstar90 68D70000 68DBAFFF 0004b000
2010-05-01 15:41:32.86 spid57 * SQLSCM90 68DC0000 68DC8FFF 00009000
2010-05-01 15:41:32.86 spid57 * ODBC32 74320000 7435CFFF 0003d000
2010-05-01 15:41:32.86 spid57 * BatchParser90 68DE0000 68DFEFFF 0001f000
2010-05-01 15:41:32.86 spid57 * ATL80 7C630000 7C64AFFF 0001b000
2010-05-01 15:41:32.86 spid57 * odbcint 68F50000 68F66FFF 00017000
2010-05-01 15:41:32.86 spid57 * xpstar90 68F70000 68F95FFF 00026000
2010-05-01 15:41:32.86 spid57 * dbghelp 69060000 69174FFF 00115000
2010-05-01 15:41:32.86 spid57 *
2010-05-01 15:41:32.86 spid57 * Edi: 67423EF0: 00138188 00550028 004B004E 004F004E 004E0057 0030002B
2010-05-01 15:41:32.87 spid57 * Esi: 00000000:
2010-05-01 15:41:32.87 spid57 * Eax: 67423DD4: 000042AC 00000000 00000000 7C812AEB 00000000 0000000C
2010-05-01 15:41:32.87 spid57 * Ebx: FFFFFFFF:
2010-05-01 15:41:32.87 spid57 * Ecx: 67424444: 00000000 0001003F 00000000 00000000 00000000 00000000
2010-05-01 15:41:32.87 spid57 * Edx: FFFFFFFF:
2010-05-01 15:41:32.87 spid57 * Eip: 7C812AEB: 10C2C95E 0FFF8500 FF93368E FC558BFF 0F0C5589 7D8B16B7
2010-05-01 15:41:32.87 spid57 * Ebp: 67423E24: 67423E68 021AE96C 000042AC 00000000 00000000 00000000
2010-05-01 15:41:32.87 spid57 * SegCs: 0000001B:
2010-05-01 15:41:32.87 spid57 * EFlags: 00000246:
2010-05-01 15:41:32.87 spid57 * Esp: 67423DD0: 06539350 000042AC 00000000 00000000 7C812AEB 00000000
2010-05-01 15:41:32.87 spid57 * SegSs: 00000023:
2010-05-01 15:41:32.87 spid57 * *******************************************************************************
2010-05-01 15:41:32.87 spid57 * -------------------------------------------------------------------------------
2010-05-01 15:41:32.87 spid57 * Short Stack Dump
2010-05-01 15:41:32.87 spid57 7C812AEB Module(kernel32+00012AEB)
2010-05-01 15:41:32.87 spid57 021AE96C Module(sqlservr+011AE96C)
2010-05-01 15:41:32.87 spid57 021B2880 Module(sqlservr+011B2880)
2010-05-01 15:41:32.87 spid57 021B242D Module(sqlservr+011B242D)
2010-05-01 15:41:32.87 spid57 015C4F15 Module(sqlservr+005C4F15)
2010-05-01 15:41:32.87 spid57 010B6518 Module(sqlservr+000B6518)
2010-05-01 15:41:32.87 spid57 023D1135 Module(sqlservr+013D1135)
2010-05-01 15:41:32.87 spid57 015BAA85 Module(sqlservr+005BAA85)
2010-05-01 15:41:32.87 spid57 010621E5 Module(sqlservr+000621E5)
2010-05-01 15:41:32.87 spid57 01062131 Module(sqlservr+00062131)
2010-05-01 15:41:32.87 spid57 0107B56E Module(sqlservr+0007B56E)
2010-05-01 15:41:32.87 spid57 0107AEAD Module(sqlservr+0007AEAD)
2010-05-01 15:41:32.87 spid57 015B41EB Module(sqlservr+005B41EB)
2010-05-01 15:41:32.87 spid57 010A9DB8 Module(sqlservr+000A9DB8)
2010-05-01 15:41:32.87 spid57 010A9D36 Module(sqlservr+000A9D36)
2010-05-01 15:41:32.87 spid57 010A9D05 Module(sqlservr+000A9D05)
2010-05-01 15:41:32.87 spid57 010D13F5 Module(sqlservr+000D13F5)
2010-05-01 15:41:32.87 spid57 010A9B0A Module(sqlservr+000A9B0A)
2010-05-01 15:41:32.87 spid57 010D1AC1 Module(sqlservr+000D1AC1)
2010-05-01 15:41:32.87 spid57 0102298A Module(sqlservr+0002298A)
2010-05-01 15:41:32.87 spid57 010411FB Module(sqlservr+000411FB)
2010-05-01 15:41:32.87 spid57 01040EC3 Module(sqlservr+00040EC3)
2010-05-01 15:41:32.87 spid57 010067D3 Module(sqlservr+000067D3)
2010-05-01 15:41:32.87 spid57 010068F9 Module(sqlservr+000068F9)
2010-05-01 15:41:32.87 spid57 01006609 Module(sqlservr+00006609)
2010-05-01 15:41:32.87 spid57 010DAF6C Module(sqlservr+000DAF6C)
2010-05-01 15:41:32.87 spid57 010DAE8C Module(sqlservr+000DAE8C)
2010-05-01 15:41:32.87 spid57 010DAB54 Module(sqlservr+000DAB54)
2010-05-01 15:41:32.88 spid57 010DACF1 Module(sqlservr+000DACF1)
2010-05-01 15:41:32.88 spid57 781329BB Module(MSVCR80+000029BB)
2010-05-01 15:41:32.89 spid57 78132A47 Module(MSVCR80+00002A47)
2010-05-01 15:41:33.03 spid57 * -------------------------------------------------------------------------------
2010-05-01 15:41:33.04 spid57 Stack Signature for the dump is 0xE9E36EAE
2010-05-01 15:41:33.83 spid57 External dump process return code 0x20000001.
External dump process returned no errors.

2010-05-01 15:41:33.84 spid57 Error: 5242, Severity: 22, State: 1.
2010-05-01 15:41:33.84 spid57 An inconsistency was detected during an internal operation in database 'MOCDEV_Local'(ID:9) on page (1:2959). Please contact technical support. Reference number 4.
2010-05-01 15:47:09.16 spid57 Error: 3314, Severity: 21, State: 4.
2010-05-01 15:47:09.16 spid57 During undoing of a logged operation in database 'MOCDEV_Local', an error occurred at log record ID (241:3976:50). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
2010-05-01 15:47:09.21 spid57 Error: 9001, Severity: 21, State: 5.
2010-05-01 15:47:09.21 spid57 The log for database 'MOCDEV_Local' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
2010-05-01 15:47:09.24 spid57 Error: 3314, Severity: 21, State: 4.
2010-05-01 15:47:09.24 spid57 During undoing of a logged operation in database 'MOCDEV_Local', an error occurred at log record ID (241:3976:51). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
2010-05-01 15:47:09.24 spid57 Error: 9001, Severity: 21, State: 1.
2010-05-01 15:47:09.24 spid57 The log for database 'MOCDEV_Local' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
2010-05-01 15:47:09.30 spid57 Error: 3314, Severity: 21, State: 5.
2010-05-01 15:47:09.30 spid57 During undoing of a logged operation in database 'MOCDEV_Local', an error occurred at log record ID (227:741:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
2010-05-01 15:47:09.37 spid20s SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2010-05-01 15:47:09.38 spid20s SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2010-05-01 15:47:09.38 spid20s SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2010-05-01 15:47:09.39 spid20s Starting up database 'MOCDEV_Local'.
2010-05-01 15:47:10.12 spid20s Analysis of database 'MOCDEV_Local' (9) is 91% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
2010-05-01 15:47:10.13 spid20s Analysis of database 'MOCDEV_Local' (9) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
2010-05-01 15:47:10.14 spid20s Recovery of database 'MOCDEV_Local' (9) is 0% complete (approximately 90 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2010-05-01 15:47:10.90 spid20s Recovery of database 'MOCDEV_Local' (9) is 1% complete (approximately 67 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2010-05-01 15:47:11.97 spid20s Recovery of database 'MOCDEV_Local' (9) is 2% complete (approximately 66 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2010-05-01 15:47:11.97 spid20s 2 transactions rolled forward in database 'MOCDEV_Local' (9). This is an informational message only. No user action is required.
2010-05-01 15:47:11.97 spid20s Recovery of database 'MOCDEV_Local' (9) is 2% complete (approximately 66 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2010-05-01 15:47:12.36 spid20s Recovery of database 'MOCDEV_Local' (9) is 31% complete (approximately 5 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2010-05-01 15:47:16.53 spid20s Recovery of database 'MOCDEV_Local' (9) is 100% complete (approximately 0 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2010-05-01 15:47:16.53 spid20s 1 transactions rolled back in database 'MOCDEV_Local' (9). This is an informational message only. No user action is required.
2010-05-01 15:47:16.53 spid20s Recovery is writing a checkpoint in database 'MOCDEV_Local' (9). This is an informational message only. No user action is required.
2010-05-01 16:51:41.39 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2010-05-01 16:51:49.00 spid12s Service Broker manager has shut down.
2010-05-01 16:51:49.00 spid12s Error: 17054, Severity: 16, State: 1.
2010-05-01 16:51:49.00 spid12s The current event was not reported to the Windows Events log. Operating system error = 1717(The interface is unknown.). You may need to clear the Windows Events log if it is full.
2010-05-01 16:51:54.61 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-05-02 : 09:21:55

Nothing to do with the windows event log.

Are you sure that the service hasn't started? If you try to connect to SQL, can you?
From the error log, there's some nasty corruption in your one database (hope you have a backup), but there's no indication that the service isn't starting, just that it's taking lots of time to start (and that may cause the Services app to assume there was a timeout or failure to start)

--
Gail Shaw
SQL Server MVP

jzurbo77
Starting Member

21 Posts

Posted - 2010-05-02 : 09:35:10

Well, when I attach that database to SQLEXPRESS it works just fine and yes, I do have backup... My attempts to start the service end up with timeout...

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-05-02 : 11:49:16

Sure, the attempts to start the service timeout, that doesn't mean that the service didn't start. If SQL's taking a long, long time to recover databases (possible), then the services app may timeout, but the service still start (eventually). Can you connect to the SQL instance after trying to start it? If you refresh the services app, does it show stopped or started?
Can you try starting the service from the SQL config manager, rather than from Services

I ask, because there's nothing in the log you posted to indicate that startup failed. So unless there's more that you didn't post, there's no reason for startup to have failed. In fact, it looks like the service started successfully and then stopped due to a system shutdown.

quote:

2010-05-01 16:51:41.39 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.

--
Gail Shaw
SQL Server MVP

jzurbo77
Starting Member

21 Posts

Posted - 2010-05-02 : 12:39:19

It shows service as Stopped...
regarding that message about shutdown - I rebooted my PC but SQL Server did not come up after that...
I tried to start from SQL Config Mgr - same result.
And no, I can not connect to the instance...
And I posted everything I found in ERRORLOG for that instance (last records, not entire file...)

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-05-03 : 03:11:01

Try moving (or deleting) the files for the MOCDEV_Local database. (Assuming you have a backup)

--
Gail Shaw
SQL Server MVP

jzurbo77
Starting Member

21 Posts

Posted - 2010-05-03 : 09:43:49

I did that. Does not change a thing. I attached that database to SQLEXPRESS and it is working just fine with it... I renamed (for a minute) folder DATA in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data - still can not start the service - it does not respond in the timely fashion... Can I increase waiting time - maybe it just needs few more seconds? The "Error reporting" was set to NO in my instance Advanced properties, I changed it to YES but nothing shows up in ERRORLOG (maybe I need to flush it somehow?)
Thanks

jzurbo77
Starting Member

21 Posts

Posted - 2010-05-03 : 10:31:15

After looking into control panel->administrative tools->events>System I found the problem! I changed my NT Account password and needed to change it on my SQL Server instance!! Once I did that I was able to start the service and connect to it from Management Studio!! Thanks for your help, Gail!!

The only problem remains is that I still can not start Reporting Service even though I did change the password for Execution Account - it still complains that password is not good... Should I post another question?

p.s. I am curious why SQL Server posts info about bad password ONLY into the System log and not in its own ERRORLOG or to Application log...

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-05-03 : 10:33:14

Yes. New question = new thread.

--
Gail Shaw
SQL Server MVP

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-05-03 : 10:57:35

Because when the password's bad, the SQL service doesn't even begin to start up. It's not SQL that posts the bad password info into the event log, it's Windows. When the credentials are bad, Windows cannot start the service at all.

--
Gail Shaw
SQL Server MVP

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources