The SQL Server Analysis Service Started and Then Stopped
- Knowledge Assistant
- Moriah Yorkey
When attempting to start a SQL analysis service on a server the following error is thrown: The SQL Server Analysis Services (MSSQLSERVER) service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
SQL
Cubes
SaaS
AWS
Datacenter
OnPrem
EERP
Two files generated by the SQL Analysis Service have become corrupted at some point and will need to be be regenerated.
Connect to the server which the SQL Analysis Service is installed
In EERP AWS that would be the Web Servers in your assigned pod
In the Yarmouth Datacenter that is the Cubes server
In On Premise, this is typically the database server
Browse to the Server that the SQL Analysis Service is installed in
This can be found by opening Services → right click on the SQL Analysis Service in question → Properties → Path to Executable will show the location
Once you have browsed to this location:
Copy the msmdsrv.ini and msmdsrv.bak files to the server desktop
Delete original the msmdsrv.ini and msmdsrv.bak files in the Config folder
Go back to Services and restart the SQL Analysis Service and those two files should regenerate automatically and the Analysis Service should remain running.
If this SQL Analysis Service is Case-Sensitive more steps are required
Open SSMS on a server that has connection access to the SQL Analysis Service that you have just fixed.
Click Connect → Analysis Services... → Select/Enter your SQL Analysis Service's name → right click on the Analysis Service within SSMS and click Properties → Language/Collation → enable Case-Sensitive → Ok
Right click on the Analysis Service within SSMS and click Properties → Security → add relevant/necessary security groups needs for the analysis service.
If unsure of what groups to add please compare with another server that is currently in use.
Note: if you need additional assistance, contact TSM support for resolution
Â