MSIT SAP - SQL 2012 AS startup failure (Watson) at end of named instance setup - by EricHoll

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 786328 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 5/3/2013 2:05:03 PM
Access Restriction Public

Description

SQL Server 2012 AS named instance service MSOLAP$MSSQL_RTP startup failure (Watson error) occurred at end of named instance setup/install.  Service status StopPending found, even though StartPending expected; subsequent manual service start attempt was successful.

Please see attached DR Watson CAB generated during setup.

Detail.txt excerpt:

(01) 2013-03-04 09:32:28 Slp: Sco: Service status is StopPending. StartPending status expected
(01) 2013-03-04 09:32:28 AS: Warning: Exception: (Utility) Service 'MSOLAP$MSSQL_RTP' start request failed.
(01) 2013-03-04 09:32:28 AS: Result: (Utility) Error
(01) 2013-03-04 09:32:28 AS: Exception: Service 'MSOLAP$MSSQL_RTP' start request failed.
(01) 2013-03-04 09:32:28 AS: Result: Error
(01) 2013-03-04 09:32:28 AS: Exception:The service could not be started. Reason:  Service 'MSOLAP$MSSQL_RTP' start request failed.
(01) 2013-03-04 09:32:28 AS: Result: Error
(01) 2013-03-04 09:32:28 Slp: Configuration action failed for feature Analysis_Server_Full during timing StartupFinalize and scenario StartupFinalize.
(01) 2013-03-04 09:32:28 Slp: The service could not be started. Reason:  Service 'MSOLAP$MSSQL_RTP' start request failed.
(01) 2013-03-04 09:32:28 Slp: The configuration failure category of current exception is ConfigurationFailure
(01) 2013-03-04 09:32:28 Slp: Configuration action failed for feature Analysis_Server_Full during timing StartupFinalize and scenario StartupFinalize.
(01) 2013-03-04 09:32:28 Slp: System.ApplicationException: The service could not be started. Reason:  Service 'MSOLAP$MSSQL_RTP' start request failed.
(01) 2013-03-04 09:32:28 Slp:    at Microsoft.SqlServer.Configuration.AnalysisServices.ASConfigurationPrivate.HandleServiceStartUp()
(01) 2013-03-04 09:32:28 Slp:    at Microsoft.SqlServer.Configuration.AnalysisServices.ASConfigurationPrivate.Install_Startup(Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2013-03-04 09:32:28 Slp:    at Microsoft.SqlServer.Configuration.AnalysisServices.ASConfigurationPrivate.InstallImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2013-03-04 09:32:28 Slp:    at Microsoft.SqlServer.Configuration.AnalysisServices.ASConfigurationPrivate.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)
(01) 2013-03-04 09:32:28 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2013-03-04 09:32:28 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2013-03-04 09:32:28 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2013-03-04 09:32:28 Slp: Inner exceptions are being indented
(01) 2013-03-04 09:32:28 Slp: 
(01) 2013-03-04 09:32:28 Slp: Exception type: System.ApplicationException
(01) 2013-03-04 09:32:28 Slp:     Message: 
(01) 2013-03-04 09:32:28 Slp:         The service could not be started. Reason:  Service 'MSOLAP$MSSQL_RTP' start request failed.
(01) 2013-03-04 09:32:28 Slp:     Data: 
(01) 2013-03-04 09:32:28 Slp:       SQL.Setup.FailureCategory = ConfigurationFailure
(01) 2013-03-04 09:32:28 Slp:       WatsonConfigActionData = INSTALL@STARTUPFINALIZE@ANALYSIS_SERVER_FULL
(01) 2013-03-04 09:32:28 Slp:       WatsonExceptionFeatureIdsActionData = System.String[]
(01) 2013-03-04 09:32:28 Slp:     Stack: 
(01) 2013-03-04 09:32:28 Slp:         at Microsoft.SqlServer.Configuration.AnalysisServices.ASConfigurationPrivate.HandleServiceStartUp()
(01) 2013-03-04 09:32:28 Slp:         at Microsoft.SqlServer.Configuration.AnalysisServices.ASConfigurationPrivate.Install_Startup(Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2013-03-04 09:32:28 Slp:         at Microsoft.SqlServer.Configuration.AnalysisServices.ASConfigurationPrivate.InstallImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2013-03-04 09:32:28 Slp:         at Microsoft.SqlServer.Configuration.AnalysisServices.ASConfigurationPrivate.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)
(01) 2013-03-04 09:32:28 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2013-03-04 09:32:28 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
Sign in to post a comment.
Posted by Microsoft on 8/20/2013 at 1:17 PM
We are closing this item. If you encounter this issue again in the future feel free to open a new case.

Thanks
Posted by EricHoll on 8/20/2013 at 12:25 PM
This was encountered for a one-time POC effort, and we have no further plans for additional installations or re-installing the POC instance at this time. Sorry about that.

Thanks,
Eric
Posted by Microsoft on 8/20/2013 at 12:00 PM
Can you confirm if this still occurs on SQL 2012 SP1, or on the latest CU of SQL 2012 RTM?
Posted by Sethu Srinivasan on 5/8/2013 at 4:03 PM
Do you still see this issue in SQL 2012 SP1 as well?
You can download SQL 2012 SP1 from http://www.microsoft.com/en-us/download/details.aspx?id=35575