Добро пожаловать в форум, Guest  >>   Войти | Регистрация | Поиск | Правила | В избранное | Подписаться
Все форумы / Microsoft SQL Server Новый топик    Ответить
Топик располагается на нескольких страницах: [1] 2 3   вперед  Ctrl      все
 MSSQLSERVER служба была запущена, затем остановлена  [new]
M275
Member

Откуда:
Сообщений: 20
Добрый день, форумчане. Есть такая программа Оазис, она перестала запускаться, в ТП сказали перезапустить службу "MSSQLSERVER". Эта служба не перезапускается, пишет служба была запущена, затем остановлена. В журнале событий винды ошибка: "Error: 9003, Severity: 20, State: 1 The LSN (12:275:1) passed to log scan in database 'model' is invalid." SQL 2008 R2, Win7 Ultimate SP1
19 май 15, 16:35    [17662611]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
M275
Member

Откуда:
Сообщений: 20
Вторая же ошибка в журнале событий "SuperSocket info: FillAddress(MSAFD Tcpip [TCP/IPv6]) : Error 0."
19 май 15, 16:37    [17662627]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
Glory
Member

Откуда:
Сообщений: 104751
M275
В журнале событий винды

Смотрите лучше лог запуска самого MSSQLSERVER
19 май 15, 16:38    [17662637]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
M275
Member

Откуда:
Сообщений: 20
Glory
M275
В журнале событий винды

Смотрите лучше лог запуска самого MSSQLSERVER

Сам файл ERRORLOG
автор
2015-05-19 16:49:30.77 Server Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86)
Dec 10 2010 10:56:29
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 6.1 (Build 7601: Service Pack 1)

2015-05-19 16:49:30.92 Server (c) 2005 Microsoft Corporation.
2015-05-19 16:49:30.92 Server All rights reserved.
2015-05-19 16:49:30.92 Server Server process ID is 1856.
2015-05-19 16:49:30.92 Server Authentication mode is WINDOWS-ONLY.
2015-05-19 16:49:30.92 Server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2015-05-19 16:49:30.94 Server This instance of SQL Server last reported using a process ID of 936 at 19.05.2015 16:47:25 (local) 19.05.2015 12:47:25 (UTC). This is an informational message only; no user action is required.
2015-05-19 16:49:30.94 Server Registry startup parameters:
2015-05-19 16:49:30.94 Server -d C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2015-05-19 16:49:30.94 Server -e C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2015-05-19 16:49:30.94 Server -l C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2015-05-19 16:49:31.14 Сервер SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-05-19 16:49:31.14 Сервер Detected 4 CPUs. This is an informational message; no user action is required.
2015-05-19 16:49:33.86 Сервер Ошибка: 8313, серьезность: 16, состояние: 1.
2015-05-19 16:49:33.86 Сервер Error in mapping SQL Server performance object/counter indexes to object/counter names. SQL Server performance counters are disabled.
2015-05-19 16:49:33.92 Сервер Ошибка: 3409, серьезность: 16, состояние: 1.
2015-05-19 16:49:33.92 Сервер Performance counter shared memory setup failed with error -1. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions.
2015-05-19 16:49:34.87 Сервер 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.
2015-05-19 16:49:37.61 Сервер Database mirroring has been enabled on this instance of SQL Server.
2015-05-19 16:49:38.11 spid5s Starting up database 'master'.
2015-05-19 16:49:40.03 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2015-05-19 16:49:41.17 spid5s SQL Trace ID 1 was started by login "sa".
2015-05-19 16:49:41.41 spid5s Starting up database 'mssqlsystemresource'.
2015-05-19 16:49:41.55 spid5s The resource database build version is 9.00.5000. This is an informational message only. No user action is required.
2015-05-19 16:49:43.28 spid7s Starting up database 'model'.
2015-05-19 16:49:43.31 spid5s Server name is 'SVETLANAPC\SPS'. This is an informational message only. No user action is required.
2015-05-19 16:49:43.37 spid5s Starting up database 'msdb'.
2015-05-19 16:49:44.53 spid7s Clearing tempdb database.
2015-05-19 16:49:46.15 Сервер A self-generated certificate was successfully loaded for encryption.
2015-05-19 16:49:46.21 Сервер Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SPS ].
2015-05-19 16:49:46.21 Сервер Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SPS\sql\query ].
2015-05-19 16:49:46.24 Сервер Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2015-05-19 16:49:46.38 Сервер SQL Server is now ready for client connections. This is an informational message; no user action is required.
2015-05-19 16:49:46.99 spid7s Starting up database 'tempdb'.
2015-05-19 16:49:47.60 spid5s Recovery is complete. This is an informational message only. No user action is required.
2015-05-19 16:49:47.80 spid10s The Service Broker protocol transport is disabled or not configured.
2015-05-19 16:49:47.82 spid10s The Database Mirroring protocol transport is disabled or not configured.
2015-05-19 16:49:48.35 spid10s Service Broker manager has started.
2015-05-19 16:59:57.98 Сервер Server resumed execution after being idle 580 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2015-05-19 16:59:58.13 spid51 Starting up database 'SPS.Client3.DB'.
2015-05-19 17:01:21.73 spid15s 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.
2015-05-19 17:01:21.73 spid15s 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.
2015-05-19 17:01:21.73 spid15s 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.
2015-05-19 17:01:52.46 spid51 Starting up database 'SPS.Client3.DB'.
2015-05-19 17:02:12.93 spid51 Starting up database 'SPS.Client3.DB'.
2015-05-19 17:02:17.51 spid51 Starting up database 'SPS.Client3.DB'.
2015-05-19 17:13:24.24 spid15s SQL Server has encountered 3 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2015-05-19 17:13:24.24 spid15s SQL Server has encountered 3 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2015-05-19 17:13:24.24 spid15s SQL Server has encountered 3 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2015-05-19 17:32:34.16 Сервер Server resumed execution after being idle 240 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2015-05-19 17:32:34.26 spid51 Starting up database 'SPS.Client3.DB'.
2015-05-19 17:38:14.79 spid22s 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.
2015-05-19 17:38:14.79 spid22s 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.
2015-05-19 17:38:14.79 spid22s 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.
19 май 15, 16:44    [17662676]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
Glory
Member

Откуда:
Сообщений: 104751
M275
Сам файл ERRORLOG

По этому логу сервер успешно стартовал и работает
19 май 15, 16:47    [17662711]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
M275
Member

Откуда:
Сообщений: 20
Glory,
Только этот лог изменяется при попытках запуска программы, думаете проблема тогда в самой программе Оазис?
19 май 15, 16:52    [17662734]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
Glory
Member

Откуда:
Сообщений: 104751
M275
Только этот лог изменяется при попытках запуска программы,

И вы предоставите подтверждение своих слов ?
19 май 15, 16:53    [17662749]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
o-o
Guest
уже кто-то писал про этот "оазис",
я помню, он берет и без спроса стартует ДЕФОЛТНЫЙ инстанс.
ТС утверждает, что сервер 2008 R2, а лог приводит от именованного 2005-ого.
я думаю, дефолтный не запустился и он же причина проблем "оазиса"
19 май 15, 16:54    [17662759]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
M275
Member

Откуда:
Сообщений: 20
Glory
M275
Только этот лог изменяется при попытках запуска программы,

И вы предоставите подтверждение своих слов ?

По дате изменения логов
есть ещё ERRORLOG.1
автор
2015-05-19 16:40:04.64 Server Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86)
Dec 10 2010 10:56:29
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 6.1 (Build 7601: Service Pack 1)

2015-05-19 16:40:04.72 Server (c) 2005 Microsoft Corporation.
2015-05-19 16:40:04.72 Server All rights reserved.
2015-05-19 16:40:04.72 Server Server process ID is 936.
2015-05-19 16:40:04.72 Server Authentication mode is WINDOWS-ONLY.
2015-05-19 16:40:04.72 Server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2015-05-19 16:40:04.72 Server This instance of SQL Server last reported using a process ID of 3920 at 12.05.2015 12:26:31 (local) 12.05.2015 8:26:31 (UTC). This is an informational message only; no user action is required.
2015-05-19 16:40:04.72 Server Registry startup parameters:
2015-05-19 16:40:04.72 Server -d C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2015-05-19 16:40:04.74 Server -e C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2015-05-19 16:40:04.74 Server -l C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2015-05-19 16:40:04.80 Сервер SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-05-19 16:40:04.80 Сервер Detected 4 CPUs. This is an informational message; no user action is required.
2015-05-19 16:40:06.86 Сервер Ошибка: 8313, серьезность: 16, состояние: 1.
2015-05-19 16:40:06.86 Сервер Error in mapping SQL Server performance object/counter indexes to object/counter names. SQL Server performance counters are disabled.
2015-05-19 16:40:06.87 Сервер Ошибка: 3409, серьезность: 16, состояние: 1.
2015-05-19 16:40:06.87 Сервер Performance counter shared memory setup failed with error -1. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions.
2015-05-19 16:40:07.76 Сервер 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.
2015-05-19 16:40:10.94 Сервер Database mirroring has been enabled on this instance of SQL Server.
2015-05-19 16:40:11.52 spid5s Starting up database 'master'.
2015-05-19 16:40:12.61 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2015-05-19 16:40:13.96 spid5s SQL Trace ID 1 was started by login "sa".
2015-05-19 16:40:14.14 spid5s Starting up database 'mssqlsystemresource'.
2015-05-19 16:40:14.19 spid5s The resource database build version is 9.00.5000. This is an informational message only. No user action is required.
2015-05-19 16:40:15.22 spid7s Starting up database 'model'.
2015-05-19 16:40:15.25 spid5s Server name is 'SVETLANAPC\SPS'. This is an informational message only. No user action is required.
2015-05-19 16:40:15.31 spid5s Starting up database 'msdb'.
2015-05-19 16:40:16.42 spid7s Clearing tempdb database.
2015-05-19 16:40:17.92 Сервер A self-generated certificate was successfully loaded for encryption.
2015-05-19 16:40:18.03 Сервер Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SPS ].
2015-05-19 16:40:18.03 Сервер Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SPS\sql\query ].
2015-05-19 16:40:18.06 Сервер Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2015-05-19 16:40:18.09 Сервер SQL Server is now ready for client connections. This is an informational message; no user action is required.
2015-05-19 16:40:20.30 spid7s Starting up database 'tempdb'.
2015-05-19 16:40:21.57 spid5s Recovery is complete. This is an informational message only. No user action is required.
2015-05-19 16:40:21.85 spid10s The Service Broker protocol transport is disabled or not configured.
2015-05-19 16:40:21.91 spid10s The Database Mirroring protocol transport is disabled or not configured.
2015-05-19 16:40:22.99 spid10s Service Broker manager has started.
2015-05-19 16:47:25.59 Сервер SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2015-05-19 16:47:26.37 spid10s Service Broker manager has shut down.
2015-05-19 16:47:26.37 spid10s Error: 17054, Severity: 16, State: 1.
2015-05-19 16:47:26.37 spid10s The current event was not reported to the Windows Events log. Operating system error = 1717(Неизвестный интерфейс.). You may need to clear the Windows Events log if it is full.
2015-05-19 16:47:28.06 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

и ERRORLOG.2
автор
2015-05-19 14:08:39.09 Server Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86)
Dec 10 2010 10:56:29
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 6.1 (Build 7601: Service Pack 1)

2015-05-19 14:08:39.15 Server (c) 2005 Microsoft Corporation.
2015-05-19 14:08:39.15 Server All rights reserved.
2015-05-19 14:08:39.15 Server Server process ID is 2104.
2015-05-19 14:08:39.15 Server Authentication mode is WINDOWS-ONLY.
2015-05-19 14:08:39.16 Server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2015-05-19 14:08:39.16 Server This instance of SQL Server last reported using a process ID of 3372 at 18.05.2015 20:29:27 (local) 18.05.2015 16:29:27 (UTC). This is an informational message only; no user action is required.
2015-05-19 14:08:39.16 Server Registry startup parameters:
2015-05-19 14:08:39.16 Server -d C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2015-05-19 14:08:39.16 Server -e C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2015-05-19 14:08:39.16 Server -l C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2015-05-19 14:08:39.29 Сервер SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-05-19 14:08:39.29 Сервер Detected 4 CPUs. This is an informational message; no user action is required.
2015-05-19 14:08:42.03 Сервер Ошибка: 8313, серьезность: 16, состояние: 1.
2015-05-19 14:08:42.03 Сервер Error in mapping SQL Server performance object/counter indexes to object/counter names. SQL Server performance counters are disabled.
2015-05-19 14:08:42.07 Сервер Ошибка: 3409, серьезность: 16, состояние: 1.
2015-05-19 14:08:42.07 Сервер Performance counter shared memory setup failed with error -1. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions.
2015-05-19 14:08:43.11 Сервер 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.
2015-05-19 14:08:46.08 Сервер Database mirroring has been enabled on this instance of SQL Server.
2015-05-19 14:08:46.92 spid4s Starting up database 'master'.
2015-05-19 14:08:48.49 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2015-05-19 14:08:49.69 spid4s SQL Trace ID 1 was started by login "sa".
2015-05-19 14:08:50.19 spid4s Starting up database 'mssqlsystemresource'.
2015-05-19 14:08:50.38 spid4s The resource database build version is 9.00.5000. This is an informational message only. No user action is required.
2015-05-19 14:08:51.50 spid7s Starting up database 'model'.
2015-05-19 14:08:51.57 spid4s Server name is 'SVETLANAPC\SPS'. This is an informational message only. No user action is required.
2015-05-19 14:08:51.60 spid4s Starting up database 'msdb'.
2015-05-19 14:08:52.19 spid7s Clearing tempdb database.
2015-05-19 14:08:53.63 Сервер A self-generated certificate was successfully loaded for encryption.
2015-05-19 14:08:53.69 Сервер Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SPS ].
2015-05-19 14:08:53.69 Сервер Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SPS\sql\query ].
2015-05-19 14:08:53.72 Сервер Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2015-05-19 14:08:53.94 Сервер SQL Server is now ready for client connections. This is an informational message; no user action is required.
2015-05-19 14:08:54.78 spid7s Starting up database 'tempdb'.
2015-05-19 14:08:55.54 spid4s Recovery is complete. This is an informational message only. No user action is required.
2015-05-19 14:08:55.78 spid10s The Service Broker protocol transport is disabled or not configured.
2015-05-19 14:08:55.79 spid10s The Database Mirroring protocol transport is disabled or not configured.
2015-05-19 14:08:56.21 spid10s Service Broker manager has started.
2015-05-19 14:19:02.68 Сервер Server resumed execution after being idle 576 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2015-05-19 14:19:02.80 spid51 Starting up database 'SPS.Client3.DB'.
2015-05-19 14:25:22.86 spid15s 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.
2015-05-19 14:25:22.86 spid15s 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.
2015-05-19 14:25:22.86 spid15s 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.
2015-05-19 14:30:45.33 spid51 Starting up database 'SPS.Client3.DB'.
2015-05-19 14:38:05.53 spid19s 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.
2015-05-19 14:38:05.53 spid19s 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.
2015-05-19 14:38:05.53 spid19s 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.
2015-05-19 14:40:47.39 spid51 Starting up database 'SPS.Client3.DB'.
2015-05-19 14:54:57.64 spid12s 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.
2015-05-19 14:54:57.64 spid12s 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.
2015-05-19 14:54:57.64 spid12s 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.
2015-05-19 16:31:23.56 Сервер SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2015-05-19 16:31:26.08 spid10s Service Broker manager has shut down.
2015-05-19 16:31:26.08 spid10s Error: 17054, Severity: 16, State: 1.
2015-05-19 16:31:26.08 spid10s The current event was not reported to the Windows Events log. Operating system error = 1717(Неизвестный интерфейс.). You may need to clear the Windows Events log if it is full.
2015-05-19 16:31:27.49 spid4s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
19 май 15, 16:56    [17662774]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
Minamoto
Member

Откуда: Москва
Сообщений: 1162
M275, это тот же инстанс.
Ищите ERRORLOG от дефолтного инстанса.
19 май 15, 16:58    [17662788]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
M275
Member

Откуда:
Сообщений: 20
o-o
уже кто-то писал про этот "оазис",
я помню, он берет и без спроса стартует ДЕФОЛТНЫЙ инстанс.
ТС утверждает, что сервер 2008 R2, а лог приводит от именованного 2005-ого.
я думаю, дефолтный не запустился и он же причина проблем "оазиса"

Ну вообще в списке программ и компонентов присутствует и MS SQL 2005, установленные одновременно с 2008. Если Вы знаете как помочь, буду рад :)
19 май 15, 16:59    [17662801]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
Glory
Member

Откуда:
Сообщений: 104751
M275
По дате изменения логов
есть ещё ERRORLOG.1

Здесь нет ничего о том, что сервер не работает

M275
и ERRORLOG.2

И здесь тоже нет

И причме тут вообще дата изменения лога ? Файл лога создается при запуске, предыдущие файлы сохраняются

И как правильно заметил о-о Server Microsoft SQL Server 2005 - 9.00.5000.00 совсем не похож на SQL 2008 R2
19 май 15, 17:01    [17662814]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
o-o
Guest
M275
в ТП сказали перезапустить службу "MSSQLSERVER"

вы вот это перезапустили?

у вас там видимо есть как минимум 2 службы:
1. SQL Server(SPS)
2. SQL Server(MSSQLSERVER)

вам сказали перезапустить вторую
вы лог привели от первой, и перезапустили, судя по времени, тоже не тот экземпляр
19 май 15, 17:01    [17662817]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
o-o
Guest
похоже, винда х64
(ну лично мой сервер пишет про свою: on Windows NT 6.1 <X86> (Build 7601: Service Pack 1)),
а сервер 2005 х32.
наверное, тот второй, он х64.
посмотрите, поди кроме C:\Program Files (x86)\Microsoft SQL Server\,
есть еще каталог
C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER,
в нем проблемный инстанс
19 май 15, 17:09    [17662905]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
M275
Member

Откуда:
Сообщений: 20
o-o
M275
в ТП сказали перезапустить службу "MSSQLSERVER"

вы вот это перезапустили?

у вас там видимо есть как минимум 2 службы:
1. SQL Server(SPS)
2. SQL Server(MSSQLSERVER)

вам сказали перезапустить вторую
вы лог привели от первой, и перезапустили, судя по времени, тоже не тот экземпляр


Сказали перезапустить 2, в логах 2 она находится в папке MSSQL есть только SQLAGENT
автор
2015-05-08 13:29:53 - ? [100] Microsoft SQLServerAgent version 8.00.2039 (x86 unicode retail build) : Process ID
2015-05-08 13:29:53 - ? [100] Microsoft SQLServerAgent version 8.00.2039 (x86 unicode retail build) : Process ID 2776
2015-05-08 13:29:53 - ? [101] SQL Server SVETLANAPC version 8.00.2039 (0 connection limit)
2015-05-08 13:29:53 - ? [102] SQL Server ODBC driver version 6.01.7601
2015-05-08 13:29:53 - ? [103] NetLib being used by driver is DBMSSHRN.DLL; Local host server is
2015-05-08 13:29:54 - ? [310] 4 processor(s) and 4096 MB RAM detected
2015-05-08 13:29:54 - ? [339] Local computer is SVETLANAPC running Windows NT 6.1 (7601) Service Pack 1
2015-05-08 13:29:57 - ! [000] Unable to locate entry point for AXSCPHST.DLL in Не найден указанный модуль (reason: 跐棼)
2015-05-08 13:29:57 - ! [125] Subsystem 'ActiveScripting' could not be loaded (reason: Initialization failed [subsystem code 0])
2015-05-08 13:29:57 - ! [364] The Messenger service has not been started - NetSend notifications will not be sent
2015-05-08 13:29:57 - ? [129] SQLSERVERAGENT starting under Windows NT service control
2015-05-08 13:29:57 - + [260] Unable to start mail session (reason: No mail profile defined)
2015-05-08 13:29:57 - + [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
2015-05-08 16:52:30 - ! [LOG] Unable to read local eventlog (reason: Неизвестный интерфейс)
2015-05-08 16:52:30 - ? [130] SQLSERVERAGENT stopping because of Windows shutdown...
2015-05-08 16:52:32 - ! [298] SQLServer Error: 1364, Не удается создать контекст SSPI [SQLSTATE HY000]
2015-05-08 16:52:32 - ! [382] Logon to server '(local)' failed (SaveAllSchedules)
2015-05-08 16:52:33 - ? [098] SQLServerAgent terminated (normally)
19 май 15, 17:12    [17662924]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
Glory
Member

Откуда:
Сообщений: 104751
M275
Сказали перезапустить 2

Ну и где лог то от SQL Server(MSSQLSERVER) ? А не от SQL Server(SPS)
19 май 15, 17:13    [17662933]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
M275
Member

Откуда:
Сообщений: 20
o-o
похоже, винда х64
(ну лично мой сервер пишет про свою: on Windows NT 6.1 <X86> (Build 7601: Service Pack 1)),
а сервер 2005 х32.
наверное, тот второй, он х64.
посмотрите, поди кроме C:\Program Files (x86)\Microsoft SQL Server\,
есть еще каталог
C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER,
в нем проблемный инстанс

Да винда х64 и есть такая папка, ERRORLOG там:
автор
2015-05-19 16:49:37.21 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

2015-05-19 16:49:37.49 Server (c) Microsoft Corporation.
2015-05-19 16:49:37.49 Server All rights reserved.
2015-05-19 16:49:37.49 Server Server process ID is 2112.
2015-05-19 16:49:37.52 Server System Manufacturer: 'Gigabyte Technology Co., Ltd.', System Model: 'P61-S3-B3'.
2015-05-19 16:49:37.54 Server Authentication mode is WINDOWS-ONLY.
2015-05-19 16:49:37.56 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2015-05-19 16:49:37.68 Server This instance of SQL Server last reported using a process ID of 844 at 19.05.2015 16:47:25 (local) 19.05.2015 12:47:25 (UTC). This is an informational message only; no user action is required.
2015-05-19 16:49:37.68 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2015-05-19 16:49:38.12 Сервер SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-05-19 16:49:38.15 Сервер Detected 4 CPUs. This is an informational message; no user action is required.
2015-05-19 16:49:40.28 Сервер 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.
2015-05-19 16:49:45.82 Сервер Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-05-19 16:49:46.68 spid6s Starting up database 'master'.
2015-05-19 16:49:47.16 spid6s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2015-05-19 16:49:48.42 spid6s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2015-05-19 16:49:49.48 spid6s SQL Trace ID 1 was started by login "sa".
2015-05-19 16:49:49.60 spid6s Starting up database 'mssqlsystemresource'.
2015-05-19 16:49:49.63 spid6s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2015-05-19 16:49:50.83 spid10s Starting up database 'model'.
2015-05-19 16:49:50.85 spid6s Server name is 'SVETLANAPC\SQLEXPRESS'. This is an informational message only. No user action is required.
2015-05-19 16:49:50.97 spid6s Информация: не найдено языков, для которых поддерживается полнотекстовый поиск.
2015-05-19 16:49:51.01 spid6s Starting up database 'msdb'.
2015-05-19 16:49:52.03 Сервер A self-generated certificate was successfully loaded for encryption.
2015-05-19 16:49:52.06 Сервер Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2015-05-19 16:49:52.06 Сервер Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2015-05-19 16:49:52.13 Сервер Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2015-05-19 16:49:52.25 spid10s Clearing tempdb database.
2015-05-19 16:49:52.55 Сервер 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.
2015-05-19 16:49:52.55 Сервер SQL Server is now ready for client connections. This is an informational message; no user action is required.
2015-05-19 16:49:56.19 spid10s Starting up database 'tempdb'.
2015-05-19 16:49:57.50 spid13s The Service Broker protocol transport is disabled or not configured.
2015-05-19 16:49:57.53 spid13s The Database Mirroring protocol transport is disabled or not configured.
2015-05-19 16:49:58.41 spid13s Service Broker manager has started.
2015-05-19 16:49:58.59 spid6s Recovery is complete. This is an informational message only. No user action is required.
19 май 15, 17:14    [17662941]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
Glory
Member

Откуда:
Сообщений: 104751
M275
Да винда х64 и есть такая папка, ERRORLOG там:

И там мы тоже видим, что все хорошо

"2015-05-19 16:49:52.55 Сервер SQL Server is now ready for client connections. This is an informational message; no user action is required."
19 май 15, 17:15    [17662949]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
o-o
Guest
аааа, я знаю, кто "был запущен, а потом остановлен".
это ТС вместо службы сервера запустил агента.
а он в Экспрессе липовый.
его запускаешь, а он пишет: был запущен и остановлен. точно!
19 май 15, 17:21    [17662990]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
Glory
Member

Откуда:
Сообщений: 104751
И кстати другой сервер - он тоже не MSSQLSERVER, а Server name is 'SVETLANAPC\SQLEXPRESS'
19 май 15, 17:22    [17663001]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
o-o
Guest
Glory
И кстати другой сервер - он тоже не MSSQLSERVER, а Server name is 'SVETLANAPC\SQLEXPRESS'

ого!
M275, покажите картинкой свой Configuration Manager,
раскройте узел со всеми серверами, мы тогда скажем, сколько у вас чего,
запущены или нет, и где их искать
19 май 15, 17:25    [17663030]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
M275
Member

Откуда:
Сообщений: 20
Glory
M275
Сказали перезапустить 2

Ну и где лог то от SQL Server(MSSQLSERVER) ? А не от SQL Server(SPS)

Вот
автор
2013-05-16 13:42:17.53 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 6.1 (Build 7601: Service Pack 1)

2013-05-16 13:42:17.53 server Copyright (C) 1988-2002 Microsoft Corporation.
2013-05-16 13:42:17.53 server All rights reserved.
2013-05-16 13:42:17.53 server Server Process ID is 2612.
2013-05-16 13:42:17.53 server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
2013-05-16 13:42:18.14 server SQL Server is starting at priority class 'normal'(4 CPUs detected).
2013-05-16 13:42:18.20 server Performance monitor shared memory setup failed: -1
2013-05-16 13:42:18.20 server SQL Server configured for thread mode processing.
2013-05-16 13:42:18.20 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2013-05-16 13:42:18.28 spid2 Starting up database 'master'.
2013-05-16 13:42:18.45 spid2 Server name is 'SVETLANAPC'.
2013-05-16 13:42:18.45 spid2 Skipping startup of clean database id 5
2013-05-16 13:42:18.45 spid2 Skipping startup of clean database id 6
2013-05-16 13:42:18.45 spid2 Skipping startup of clean database id 7
2013-05-16 13:42:18.45 spid2 Skipping startup of clean database id 8
2013-05-16 13:42:18.45 spid2 Skipping startup of clean database id 9
2013-05-16 13:42:18.45 spid2 Starting up database 'msdb'.
2013-05-16 13:42:18.46 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2013-05-16 13:42:18.46 spid5 Starting up database 'model'.
2013-05-16 13:42:18.48 server SQL server listening on 192.168.0.27: 1433.
2013-05-16 13:42:18.48 server SQL server listening on 127.0.0.1: 1433.
2013-05-16 13:42:18.51 server SQL server listening on TCP, Shared Memory, Named Pipes.
2013-05-16 13:42:18.51 server SQL Server is ready for client connections
2013-05-16 13:42:20.57 spid5 Clearing tempdb database.
2013-05-16 13:42:24.88 spid5 Starting up database 'tempdb'.
2013-05-16 13:42:24.92 spid2 Recovery complete.
2013-05-16 13:42:26.64 spid51 Using 'xpsqlbot.dll' version '2000.80.2039' to execute extended stored procedure 'xp_qv'.
2013-05-16 15:15:54.77 server SQL Server terminating because of system shutdown.

o-o
аааа, я знаю, кто "был запущен, а потом остановлен".
это ТС вместо службы сервера запустил агента.
а он в Экспрессе липовый.
его запускаешь, а он пишет: был запущен и остановлен. точно!

Теперь я вообще ничего не понимаю :(
o-o
Glory
И кстати другой сервер - он тоже не MSSQLSERVER, а Server name is 'SVETLANAPC\SQLEXPRESS'

ого!
M275, покажите картинкой свой Configuration Manager,
раскройте узел со всеми серверами, мы тогда скажем, сколько у вас чего,
запущены или нет, и где их искать

Сейчас
19 май 15, 17:29    [17663058]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
Glory
Member

Откуда:
Сообщений: 104751
M275
Glory
пропущено...

Ну и где лог то от SQL Server(MSSQLSERVER) ? А не от SQL Server(SPS)

Вот
автор
2013-05-16 13:42:17.53 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 6.1 (Build 7601: Service Pack 1)

2013-05-16 13:42:17.53 server Copyright (C) 1988-2002 Microsoft Corporation.
2013-05-16 13:42:17.53 server All rights reserved.
2013-05-16 13:42:17.53 server Server Process ID is 2612.
2013-05-16 13:42:17.53 server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
2013-05-16 13:42:18.14 server SQL Server is starting at priority class 'normal'(4 CPUs detected).
2013-05-16 13:42:18.20 server Performance monitor shared memory setup failed: -1
2013-05-16 13:42:18.20 server SQL Server configured for thread mode processing.
2013-05-16 13:42:18.20 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2013-05-16 13:42:18.28 spid2 Starting up database 'master'.
2013-05-16 13:42:18.45 spid2 Server name is 'SVETLANAPC'.
2013-05-16 13:42:18.45 spid2 Skipping startup of clean database id 5
2013-05-16 13:42:18.45 spid2 Skipping startup of clean database id 6
2013-05-16 13:42:18.45 spid2 Skipping startup of clean database id 7
2013-05-16 13:42:18.45 spid2 Skipping startup of clean database id 8
2013-05-16 13:42:18.45 spid2 Skipping startup of clean database id 9
2013-05-16 13:42:18.45 spid2 Starting up database 'msdb'.
2013-05-16 13:42:18.46 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2013-05-16 13:42:18.46 spid5 Starting up database 'model'.
2013-05-16 13:42:18.48 server SQL server listening on 192.168.0.27: 1433.
2013-05-16 13:42:18.48 server SQL server listening on 127.0.0.1: 1433.
2013-05-16 13:42:18.51 server SQL server listening on TCP, Shared Memory, Named Pipes.
2013-05-16 13:42:18.51 server SQL Server is ready for client connections
2013-05-16 13:42:20.57 spid5 Clearing tempdb database.
2013-05-16 13:42:24.88 spid5 Starting up database 'tempdb'.
2013-05-16 13:42:24.92 spid2 Recovery complete.
2013-05-16 13:42:26.64 spid51 Using 'xpsqlbot.dll' version '2000.80.2039' to execute extended stored procedure 'xp_qv'.
2013-05-16 15:15:54.77 server SQL Server terminating because of system shutdown.

Здесь тоже все замечательно
2013-05-16 13:42:18.48 server SQL server listening on 192.168.0.27: 1433.
2013-05-16 13:42:18.48 server SQL server listening on 127.0.0.1: 1433.
2013-05-16 13:42:18.51 server SQL server listening on TCP, Shared Memory, Named Pipes.
2013-05-16 13:42:18.51 server SQL Server is ready for client connections

И это SQL2000, а не SQL 2008 R2
19 май 15, 17:31    [17663079]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
o-o
Guest
дефолтный-то и вовсе 2000-ый,
да еще и пыль с него не стирали с 2013-ого года.
в тихом омуте черти водятся
19 май 15, 17:33    [17663087]     Ответить | Цитировать Сообщить модератору
 Re: MSSQLSERVER служба была запущена, затем остановлена  [new]
o-o
Guest
M275
пропущено...
Здесь тоже все замечательно
2013-05-16 13:42:18.51 server SQL Server is ready for client connections

вы не дочитали до happy end-а:
2013-05-16 15:15:54.77 server SQL Server terminating because of system shutdown.

показывайте уже зоопарк картинкой, а то рабочий день заканчивается :)
19 май 15, 17:36    [17663101]     Ответить | Цитировать Сообщить модератору
Топик располагается на нескольких страницах: [1] 2 3   вперед  Ctrl      все
Все форумы / Microsoft SQL Server Ответить