SSAS 2012 service not starting up

  • Dear All,

    I got SQL Server installed in a failover cluster environment. SQL Server, Agent Service & Analysis Service. Everything was working well. Without any apparent reason SSAS service stopped working one day. There was no installation of any sort before this event. Whenever I try to start SSAS, I get following error.

    I checked the log file and I see below entries.
    (3/26/2017 3:46:14 PM) Message: The Query thread pool now has 1 minimum threads, 10 maximum threads, and a concurrency of 8. Its thread pool affinity mask is 0x000000000000000f. (Source: \\?\L:\OLAP\Log\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x4121000A)
    (3/26/2017 3:46:14 PM) Message: The ParsingShort thread pool now has 4 minimum threads, 4 maximum threads, and a concurrency of 8. Its thread pool affinity mask is 0x000000000000000f. (Source: \\?\L:\OLAP\Log\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x4121000A)
    (3/26/2017 3:46:14 PM) Message: The ParsingLong thread pool now has 4 minimum threads, 4 maximum threads, and a concurrency of 8. Its thread pool affinity mask is 0x000000000000000f. (Source: \\?\L:\OLAP\Log\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x4121000A)
    (3/26/2017 3:46:14 PM) Message: The Processing thread pool now has 1 minimum threads, 64 maximum threads, and a concurrency of 8. Its thread pool affinity mask is 0x000000000000000f. (Source: \\?\L:\OLAP\Log\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x4121000A)
    (3/26/2017 3:46:14 PM) Message: The IOProcessing thread subpool with affinity 0x000000000000000f now has 1 minimum threads, 64 maximum threads, and a concurrency of 8. (Source: \\?\L:\OLAP\Log\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x4121000B)
    (3/26/2017 3:46:14 PM) Message: Failed to initialize SQLSQM timer. One of the following can be the source of the problem: registry doesn't contain all necessary information, server instance name can not be retrieved correctly, failure during timer creation, etc. (Source: \\?\L:\OLAP\Log\msmdsrv.log, Type: 3, Category: 289, Event ID: 0xC121001B)
    (3/26/2017 3:46:15 PM) Message: The service cannot be started: (Source: \\?\L:\OLAP\Log\msmdsrv.log, Type: 3, Category: 289, Event ID: 0xC1210000)
    (3/26/2017 3:46:15 PM) Message: Service stopped. (Source: \\?\L:\OLAP\Log\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210001)

    I did following activities to resolve the issue, which I found in different forums when googled.

    1. Cleared Windows Application Log and tried starting service. Didn't work.
    2. Gave specific permissions on C:\Program...\OLAP\bin folder and D:\OLAP\Config folder for domain user with which SSAS is configured. Didn't work.

    Any help would be appreciated.

    Thank you,

  • I would start by reviewing the error in the EVENT VIEWER

  • Below is the event specific on SSAS found in Failover Cluster Manager console

    Cluster resource 'Analysis Services' of type 'Generic Service' in clustered role 'SQL Server (MSSQLSERVER)' failed.
    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

    Generic service 'Analysis Services' failed with error '0'. Please examine the application event log.
    Generic service 'Analysis Services' failed with error '0'. Please examine the application event log.

    Below is error from Application Event Log

    Failed to initialize SQLSQM timer. One of the following can be the source of the problem: registry doesn't contain all necessary information, server instance name can not be retrieved correctly, failure during timer creation, etc.

  • AbdulGafoor GK - Monday, March 27, 2017 12:50 PM

    Below is the event specific on SSAS found in Failover Cluster Manager console

    Cluster resource 'Analysis Services' of type 'Generic Service' in clustered role 'SQL Server (MSSQLSERVER)' failed.
    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

    Generic service 'Analysis Services' failed with error '0'. Please examine the application event log.
    Generic service 'Analysis Services' failed with error '0'. Please examine the application event log.

    Below is error from Application Event Log

    Failed to initialize SQLSQM timer. One of the following can be the source of the problem: registry doesn't contain all necessary information, server instance name can not be retrieved correctly, failure during timer creation, etc.

    Is this a named instance or default instance?

    Sue

  • Default instance. I did post the same question in MSDN SQL Server forum as well. FYI only.

  • AbdulGafoor GK - Wednesday, March 29, 2017 10:19 AM

    Default instance. I did post the same question in MSDN SQL Server forum as well. FYI only.

    Dang...when it's a default, as you have probably seen already from researching it, there doesn't seem to be a good solution. Named instance is different.
    And some of those odd things that people did (such as clearing the event logs) I would suspect have nothing to do with whatever the problem is is.
    It looks like you are already aware of the needed things for the service account but I would suspect the issue is related to permissions somewhere. I'd double check those and especially check the permissions on the Config folder and it's files in the SSAS directory on both nodes. Not sure if you went over the permissions needed from Microsoft's docs but it's worth a check for all of the items - here is the link if you don't have it:
    Configure Service Accounts (Analysis Services)

    Sue

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply