SQL Server Performance

SQL Server is terminating due to 'stop' request from Service Control Manager.

Discussion in 'General DBA Questions' started by Luis Martin, May 28, 2009.

  1. Luis Martin Moderator

    The following is the last two rows in errorlog.
    2009-05-27 15:43:51.32 spid140 Invalid buffer received from client..
    2009-05-28 01:05:40.90 spid2 SQL Server is terminating due to 'stop' request from Service Control Manager.
    In that time integrity check was working in two databases (the job begin at 1:00).
    Plenty of space, etc., W3k sp1, sql 2000 sp4 last fix.
    After stop, the two databases was settings to suspect (after sql service up at 9:00).
    The only way to get those on line was restore.
    My question is: What are the reasons for "sql server is terminating....". Manual is one of them. Is there any other?
  2. moh_hassan20 New Member

    It may be terminated by software.
    can you review windows system log, application log and security log for the time before 2009-05-28 01:05:40.90
    If you have auditing system, you may find records that help.
    i don't think that Invalid buffer received from client (about 10 hours before stopping)is the reason.
  3. Luis Martin Moderator

    "It may be terminated by software": How?
    I can't find more information in error log or event viewer.
    About "Invalid buffer....." is because some part of application was writen in .Net (there is some article in MS about it) and I don´t think, also, that error could stop sql service.
    The big question is still on the table (Satya, Frank, Adriaan, Madhi, Mohammed, Dinesh, and all of you members...): How many differents way Service Control Manager could stop sql server?
    I need some input from you before Monday noon.
    Thanks,
  4. satya Moderator

  5. Luis Martin Moderator

    Some part of it, yes. But I don´t think (I read that article before) can stop sql service.
  6. FrankKalis Moderator

    No, I don't think either, that "Invalid buffer..." can cause SQL Server to stop.
    Has anything changed on that box? Any update to a software component perhaps?
  7. Luis Martin Moderator

    As far I know, nothing.
  8. FrankKalis Moderator

    [quote user="Luis Martin"]As far I know, nothing.[/quote]
    ...and you got that from the customer, right? [;-)]
  9. Luis Martin Moderator

    Yeap.
    The hardware/software people are free lance.
    The Implementation people are free lance.
    I'm free lance.
    All of us (and some more) have remote acces to the server (hardware/software people have the responsabiltity).
    So, anyone can stop the service when Integrity jobs was running.
    Now, why a manual stop can live suspect both databases?. That is normal when integrity job is running?. I don't think so.
  10. moh_hassan20 New Member

    So, Email all free lance hardware/software people and ask them who do that and why.
    Put a procedure for stopping/rebooting the database server and, email it to all staff.
    It should be one (or two) administrator server who mange user account and password and remote login rights for all free lance people.
    if you reviewed the security event, you will find information record who, when,workstation who logged near the stopping time.[;)]

  11. gurucb New Member

    Hi Guys,
    Sorry to pitch in late... but both of these errors are not related. See the time stamps!!!!
    2009-05-27 15:43:51.32 spid140 Invalid buffer received from client..
    2009-05-28 01:05:40.90 spid2 SQL Server is terminating due to 'stop' request from Service Control Manager.
    Did Windows get restarted (may be due to patch at OS level)
  12. satya Moderator

    If this is occuring regularly then PROFILER is best to catch up the back operations and if not you may need to chalk out all the processes/jobs/changes on SQL to catch the culprit.
  13. Luis Martin Moderator

    Once again.
    In this case, no maitenance job running. No user. No nothing.
    This is the errorlog:
    2009-06-16 23:55:10.32 server Microsoft SQL Server 2000 - 8.00.2273 (Intel X86)
    Mar 7 2008 22:19:58
    Copyright (c) 1988-2003 Microsoft Corporation
    Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

    2009-06-16 23:55:10.32 server Copyright (C) 1988-2002 Microsoft Corporation.
    2009-06-16 23:55:10.32 server All rights reserved.
    2009-06-16 23:55:10.32 server Server Process ID is 6044.
    2009-06-16 23:55:10.32 server Logging SQL Server messages in file 'c:mssql2kMSSQLlogERRORLOG'.
    2009-06-16 23:55:10.34 server SQL Server is starting at priority class 'normal'(4 CPUs detected).
    2009-06-16 23:55:10.43 server SQL Server configured for thread mode processing.
    2009-06-16 23:55:10.45 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
    2009-06-16 23:55:10.57 server Attempting to initialize Distributed Transaction Coordinator.
    2009-06-16 23:55:11.06 server Failed to obtain TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
    2009-06-16 23:55:11.06 spid3 Starting up database 'master'.
    2009-06-16 23:55:11.20 server Using 'SSNETLIB.DLL' version '8.0.2039'.
    2009-06-16 23:55:11.20 spid5 Starting up database 'model'.
    2009-06-16 23:55:11.21 spid3 Server name is 'SERVER3'.
    2009-06-16 23:55:11.23 spid10 Starting up database 'Dbl1'.
    2009-06-16 23:55:11.23 spid8 Starting up database 'msdb'.
    2009-06-16 23:55:11.23 spid9 Starting up database 'Frio'.
    2009-06-16 23:55:11.23 spid11 Starting up database 'Pronto1'.
    2009-06-16 23:55:11.28 spid10 Cannot associate files with different databases.
    2009-06-16 23:55:11.28 spid10 Device activation error. The physical file name 'C:Mssql2kMSSQLDataDbl1_1.ndf' may be incorrect.
    2009-06-16 23:55:11.28 spid10 Data File C:Mssql2kMSSQLDataDbl1_2.ndf does not exist - unable to activate.
    2009-06-16 23:55:11.28 spid10 Device activation error. The physical file name 'C:Mssql2kMSSQLDataDbl1_2.ndf' may be incorrect.
    2009-06-16 23:55:11.29 spid10 Cannot associate files with different databases.
    2009-06-16 23:55:11.29 spid10 Log file 'C:Mssql2kMSSQLDataDbl1_log.ldf' does not match the primary file. It may be from a different database or the log may have been rebuilt previously.
    2009-06-16 23:55:11.34 spid9 Cannot associate files with different databases.
    2009-06-16 23:55:11.34 spid9 Device activation error. The physical file name 'C:Mssql2kMSSQLDataFrio_1.ndf' may be incorrect.
    2009-06-16 23:55:11.39 spid9 Cannot associate files with different databases.
    2009-06-16 23:55:11.39 spid9 Log file 'C:Mssql2kMSSQLDataFrio_log.ldf' does not match the primary file. It may be from a different database or the log may have been rebuilt previously.
    2009-06-16 23:55:11.43 spid5 Clearing tempdb database.
    2009-06-16 23:55:11.45 server SQL server listening on 192.168.0.160: 1433.
    2009-06-16 23:55:11.45 server SQL server listening on 127.0.0.1: 1433.
    2009-06-16 23:55:11.53 server SQL server listening on TCP, Shared Memory, Named Pipes.
    2009-06-16 23:55:11.78 server SQL Server is ready for client connections
    2009-06-16 23:55:12.18 spid5 Starting up database 'tempdb'.
    2009-06-16 23:55:12.18 spid5 Analysis of database 'tempdb' (2) is 100% complete (approximately 0 more seconds)
    2009-06-16 23:55:12.34 spid3 Recovery complete.
    2009-06-16 23:55:12.34 spid3 SQL global counter collection task is created.
    2009-06-17 08:37:57.90 spid51 Using 'xpstar.dll' version '2000.80.2273' to execute extended stored procedure 'sp_MSgetversion'.
    2009-06-17 08:54:18.56 spid53 Using 'xplog70.dll' version '2000.80.2039' to execute extended stored procedure 'xp_cmdshell'.
    2009-06-17 08:54:18.68 spid53 Using 'C:program FilesSQLZIP SoftwareSQLZIPlaunchsqlzip.dll' version 'UNKNOWN' to execute extended stored procedure 'xp_loadsqlzipmt'.
    2009-06-17 09:45:17.15 spid53 Starting up database 'Frio'.
    2009-06-17 09:45:17.17 spid53 Bypassing recovery for database 'Frio' because it is marked IN LOAD.
    2009-06-17 09:45:19.18 spid53 Starting up database 'Frio'.
    2009-06-17 09:45:19.20 spid53 Bypassing recovery for database 'Frio' because it is marked IN LOAD.
    2009-06-17 09:45:19.43 spid53 Recovery is checkpointing database 'Frio' (5)
    2009-06-17 09:45:19.50 spid53 Starting up database 'Frio'.
    2009-06-17 09:45:19.81 backup Database restored: Database: Frio, creation date(time): 2009/05/28(12:02:16), first LSN: 213342:4038:1, last LSN: 213342:4112:1, number of dump devices: 1, device information: (FILE=1, TYPE=PIPE: {'\.pipeSQLZIP-Frio-3237F773-9530-4930-8CF1-9F99F56B69F5'}).
    2009-06-17 10:32:11.50 spid55 DBCC CHECKALLOC (Frio) executed by SERVER3Administrator found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 2 seconds.
    2009-06-17 10:34:24.87 spid54 Starting up database 'Dbl1'.
    2009-06-17 10:34:24.92 spid54 Bypassing recovery for database 'Dbl1' because it is marked IN LOAD.
    2009-06-17 10:34:28.90 spid54 Starting up database 'Dbl1'.
    2009-06-17 10:34:28.92 spid54 Bypassing recovery for database 'Dbl1' because it is marked IN LOAD.
    2009-06-17 10:34:32.42 spid54 Recovery is checkpointing database 'Dbl1' (6)
    2009-06-17 10:34:32.68 spid54 Starting up database 'Dbl1'.
    2009-06-17 10:34:35.78 backup Database restored: Database: Dbl1, creation date(time): 2009/05/28(12:05:23), first LSN: 329380:21219:3, last LSN: 329380:21975:1, number of dump devices: 1, device information: (FILE=1, TYPE=PIPE: {'\.pipeSQLZIP-Dbl1-75EF479C-2AFC-47EF-AB64-D372C447FD6D'}).
    2009-06-17 10:35:55.86 spid53 DBCC CHECKALLOC (Dbl1) executed by SERVER3Administrator found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 9 seconds.
    2009-06-17 10:36:40.75 spid54 Using 'xpsqlbot.dll' version '2000.80.2039' to execute extended stored procedure 'xp_qv'.
    2009-06-17 10:37:33.89 spid55 DBCC CHECKDB (Frio) executed by SERVER3Administrator found 0 errors and repaired 0 errors. Elapsed time: 0 hours 4 minutes 16 seconds.
    2009-06-17 10:47:42.87 spid55 DBCC CHECKDB (Dbl1) executed by SERVER3Administrator found 0 errors and repaired 0 errors. Elapsed time: 0 hours 8 minutes 54 seconds.
    2009-06-17 11:22:51.21 backup Database backed up: Database: Frio, creation date(time): 2009/06/17(09:03:00), pages dumped: 1293944, first LSN: 213343:3477:1, last LSN: 213343:6521:1, number of dump devices: 1, device information: (FILE=1, TYPE=PIPE: {'\.pipeSQLZIP_Frio'}).
    2009-06-17 13:08:48.82 backup Database backed up: Database: DBL1, creation date(time): 2009/06/17(09:06:09), pages dumped: 2721544, first LSN: 329382:18889:1, last LSN: 329382:23424:1, number of dump devices: 1, device information: (FILE=1, TYPE=PIPE: {'\.pipeSQLZIP_DBL1'}).
    2009-06-17 13:19:30.84 backup Database backed up: Database: Frio, creation date(time): 2009/06/17(09:03:00), pages dumped: 1294296, first LSN: 213344:15683:7, last LSN: 213344:16167:1, number of dump devices: 1, device information: (FILE=1, TYPE=PIPE: {'\.pipeSQLZIP_Frio'}).
    2009-06-17 18:05:03.23 backup Database backed up: Database: Frio, creation date(time): 2009/06/17(09:03:00), pages dumped: 1295296, first LSN: 213350:4904:2, last LSN: 213350:5127:1, number of dump devices: 1, device information: (FILE=1, TYPE=PIPE: {'\.pipeSQLZIP_Frio'}).
    2009-06-17 18:09:21.96 backup Database backed up: Database: DBL1, creation date(time): 2009/06/17(09:06:09), pages dumped: 2723128, first LSN: 329386:3920:1, last LSN: 329386:6349:1, number of dump devices: 1, device information: (FILE=1, TYPE=PIPE: {'\.pipeSQLZIP_DBL1'}).
    To me someone stop the sql service (23:53), change something in datafiles names, start sql service (23:55) and forget to start sqlagent.
    No reboot at all.
    What do you think?

Share This Page