Introduction

This article explains how to resolve server startup failures.

    Event Viewer Details

Maximum entries in the event log prevent service startup

The MSSQLServerOlapService will not start if it cannot add entries to the application event log. SQL Server 2008 and 2008 R2 customers reported getting this error when the event log was full. This bug does not seem to occur in later versions, or on installations that have recent service packs applied.

To resolve this error immediately, clear the event log or change logging properties to allow overwrite (default):

In the Event Viewer, right-click Application Logs and select Clear Log. You will have the option of saving its contents prior to deletion.
Alternatively, right-click Application Logs and select Properties. Choose "Overwrite events as needed (oldest events first)".        

   Installation error prevents service from starting

This error is known to occur if there was a problem installing Analysis Services.  To resolve this error, uninstall and re-install Analysis Services to address this problem:

• Use the Programs and Features Uninstall/Change to uninstall Analysis Services. You can uninstall just this service, leaving other features intact.
• Use SQL Server installation media to install Analysis Services.

Other reasons why the service fails to start

MSSQLServerOlapService fails to start, investigate the following potential causes:

Port configuration: The service cannot open a port. See Configure the Windows Firewall to Allow Analysis Services Access for more information.

        File permissions: The service cannot create or open required files. File permission problems are more likely to occur if you change accounts using scripts or tools that do not update file permissions when changing a service account. Use SQL Server Configuration Manager to update accounts. See Configure Service Accounts (Analysis Services) for more information.

Resources

The following links also reference this error:

        (log file is full)        

        http://social.msdn.microsoft.com/Forums/en-US/sqlanalysisservices/thread/221be6b0-d57f-4d2c-8f03-1ffa77b51541

        http://connect.microsoft.com/SQLServer/feedback/details/387163/mssqlolapservice-start-request-failed#details        

        https://connect.microsoft.com/SQLServer/feedback/details/615587/ssas-service-wont-start-after-install-until-application-log-is-purged        

        (master.vmp file is corrupt)        

        http://social.msdn.microsoft.com/Forums/en-US/sqlanalysisservices/thread/70245c43-b1ab-4087-8af0-524479a1feb7        

Note: Use extreme caution when deleting the master.vmp file. Delete it only if you are fixing an installation problem or are repairing a system that does not have data you care about. The master.vmp file contains the object GUIDs of all database objects. Deleting it will permanently disable all existing databases, requiring either a database restore or rebuild. See http://blogs.msdn.com/b/sqlserverfaq/archive/2009/07/08/tampering-master-vmp-file-may-result-in-losing-all-analysis-services-databases.aspx for more information.