为什么SSAS每隔几秒钟就重新启动一次？

Question

我们有一个SQLServer2005AnalysisServer，它在本周末开始重新启动，似乎没有任何外部更改。

服务器的当前状态是，只要启用了SSAS服务，它就会继续重新启动。如果该服务被手动禁用，然后停止，则该服务将不再循环。但一旦启用，服务将再次开始循环。

互联网搜索找到了一些这种行为的例子，但没有一个似乎适用的解决方案。见，例如：服务级帐户- SQL 2005 SSAS连接到OLAP的错误。另见，例如：我不能连接到SSMS的分析服务..。

Brent Ozar 报告了一个类似的问题 on LessThanDot，但没有决议，最后一条是在2009年3月27日下午4:08

这是msmdsrv.log文件的一个片段：

(10/6/2014 3:21:43 PM) Message: The flight recorder was started. (Source: \\?\S:\CubeLog\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210005)
(10/6/2014 3:21:43 PM) Message: Service started. (Source: \\?\S:\CubeLog\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210000)
(10/6/2014 3:22:40 PM) Message: Service stopped. (Source: \\?\S:\CubeLog\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210001)
(10/6/2014 3:22:45 PM) Message: The flight recorder was started. (Source: \\?\S:\CubeLog\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210005)
(10/6/2014 3:22:45 PM) Message: Service started. (Source: \\?\S:\CubeLog\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210000)
(10/6/2014 3:23:41 PM) Message: Service stopped. (Source: \\?\S:\CubeLog\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210001)
(10/6/2014 3:23:47 PM) Message: The flight recorder was started. (Source: \\?\S:\CubeLog\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210005)
(10/6/2014 3:23:47 PM) Message: Service started. (Source: \\?\S:\CubeLog\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210000)
(10/6/2014 3:24:41 PM) Message: Service stopped. (Source: \\?\S:\CubeLog\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210001)
(10/6/2014 3:24:47 PM) Message: The flight recorder was started. (Source: \\?\S:\CubeLog\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210005)
(10/6/2014 3:24:47 PM) Message: Service started. (Source: \\?\S:\CubeLog\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210000)

系统日志的事件查看器一次又一次地具有：

"The SQL Server Analysis Services (MSSQLSERVER) service was successfully sent a stop control."
"The SQL Server Analysis Services (MSSQLSERVER) service was successfully sent a start control."
"The SQL Server Analysis Services (MSSQLSERVER) service was successfully sent a stop control."
"The SQL Server Analysis Services (MSSQLSERVER) service was successfully sent a start control."
"The SQL Server Analysis Services (MSSQLSERVER) service was successfully sent a stop control."
"The SQL Server Analysis Services (MSSQLSERVER) service was successfully sent a start control."
"The SQL Server Analysis Services (MSSQLSERVER) service was successfully sent a stop control."
etc....

似乎没有创建SQLDmprNNNN.mdmp文件。没有其他错误日志记录是我们知道的。

我们怎么知道出什么事了？是否有方法可以判断是否有任何第三方服务或进程正在循环SSAS服务？

我们还在SQL Server Central上发布了这个问题。

Answer 1

我们从来没有发现是什么导致服务停止，但我们能够阻止它的发生。我们对Server (而不是SSAS)服务帐户用户的SSAS服务的Stop权限设置了拒绝。

因此，似乎是作为Server的服务帐户用户为SSAS帐户发出停止命令。这是很久以前的事了，从那以后，我们就换了服务器，我们停止了挖掘，去弄清楚到底发生了什么。因此，这将是一个神秘的年代。