April 6, 2018 at 6:56 am
I'm trying to install Analysis Services 2017 Developer on my machine.
I've unstalled and re-installed a couple of times.
The service won't start, giving the error info below.
Any ideas what I may have incorrect?
TIA for any advice,
Doug
_______________________________________________________
TITLE: Microsoft SQL Server 2017 Setup
------------------------------
The following error has occurred:
The service could not be started. Reason: Service 'MSOLAP$DOUGDEV' start request failed.
------------------------------
BUTTONS:
OK
------------------------------
April 6, 2018 at 8:14 am
I haven't done a 2017 installation, so something may have changed. But I'm surprised to see the Analysis Services service not running under "NT Service\MSSQLServerOLAPService." This is the managed service account for Analysis Services. Your example seems like it's a machine name, which you would use when making requests across machines. Are you changing the default at some point?
April 6, 2018 at 8:58 am
I should have mentioned that this is to a Named Instance, which I believe is why the MSOLAP is in the name.
The default instance has Analysis Services on it and it does use NT Service\MSSQLServerOLAPService
April 6, 2018 at 9:03 am
I've never done a named instance installation before, so I'm going to bow out.
April 6, 2018 at 10:45 am
doug2hora - Friday, April 6, 2018 6:56 AMI'm trying to install Analysis Services 2017 Developer on my machine.
I've unstalled and re-installed a couple of times.
The service won't start, giving the error info below.
Any ideas what I may have incorrect?TIA for any advice,
Doug
_______________________________________________________TITLE: Microsoft SQL Server 2017 Setup
------------------------------The following error has occurred:
The service could not be started. Reason: Service 'MSOLAP$DOUGDEV' start request failed.
------------------------------
BUTTONS:OK
------------------------------
Sometimes - especially if it's security on the folders - the Application event log on the server has more information. I would check that for any error messages around the same time as the error starting the service.
Sue
April 6, 2018 at 12:32 pm
Thanks Sue.
The idea to look at the Application log gave me enough info to try to guess what the error was (though I still don't understand why it had this problem) so I could get past it.
Long story............I had originally created the SSAS for the Named Instance as a Tabular server. I didn't really want this as the default instance was already that.
In Visual Studio I had already created a project against this instance as tabular before I ran into the server issue as I was experimenting with a MultiDimensional project.
I uninstalled and re-installed SSAS as MultiDimensiona for this instancel. For some reason, the system was picking up this project existed that had been tied to the Name Instance and was a Tabular project. Now that I was changing the server to Multi, it wasn't happy. Why/how the system was looking at this project during the start of the SSAS service, I don't understand.
Anyway.........I removed the folders that were related to this project and now the service starts successfully.
Thanks for the advice/hint to make me look at what the Application log had in it.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply