SQL Server 2008 R2 Enterprise installation fails on Windows 2008 R2 cluster
-
jeudi 11 août 2011 17:55
Hello:
I have attempted to install SQL Server 2008 R2 on the primary node of my Win 2008 Server cluster and the installation proceeded all the way to the end and completed with failures, i.e the SQL2008 server instance is installed but cannot be started on the node. Error messages in the last pane of the installation were:
- Database engine services - Failed
- SQL Server replication - Failed
- Full-Text search - Failed
Management Tools (basic and complete) as well as Reporting services succeeded.
Last pane was:
- Your SQL Server R2 failover cluster installation completed with failures.
- Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
My cluster configuration passed all the MS validation tests.
My SQL intallation pased all the configuration tests during the installation process.
Checking in SQL Configuration Manager I see all the services running except the SQL Server Agent:
- SQL full-text filter daemon launcher - running
- SQL Server (MSSQLSERVER) - running
- SQL Server Reporting sevices - running
- SQL Server Browser - running
- SQL Server Agent (MSSQLSERVER) - stopped
I have tried starting the sql server agent without success. The domain service account doesn't work, nor does local administrator account.
I tried repairing from the installation disk but it failed. I don't really want to uninstall SQL, I'm also worried the SQL server instance will stick around somewhere in the registry and prevent me from installing with my preferred instance name.
Any ideas how to fix this? It's funny how it passes all the tests during the (lengthy) installation process but then fails out. Thanks!
Toutes les réponses
-
jeudi 11 août 2011 20:32Modérateur
Hello,
Please post in this thread the content of the summary.txt log file.
http://msdn.microsoft.com/en-us/library/ms143702(v=SQL.105).aspxRegards,
Alberto Morillo
SQLCoffee.com -
jeudi 11 août 2011 21:03
Contents of C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Summary.txt:
* * * * * * * * * * * * * * * * * * * * * * * * * *
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): 204557340
Exit facility code: 1073
Exit error code: 19484
Exit message: Object reference not set to an instance of an object.
Start time: 2011-08-11 09:26:42
End time: 2011-08-11 09:30:15
Requested action: Repair
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110811_092246\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0x4901ECF6%400x44A889F9Cluster properties:
Machine name: TSQL1A
Product Instance Instance ID Feature Language Edition Version Clustered
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER SQL Server Replication 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text Search 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER Reporting Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 Management Tools - Basic 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 Management Tools - Complete 1033 Standard Edition 10.50.1600.1 NoMachine name: TSQL1B
Product Instance Instance ID Feature Language Edition Version ClusteredMachine Properties:
Machine name: TSQL1A
Machine processor count: 2
OS version: Windows Server 2008 R2
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: YesProduct features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER SQL Server Replication 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text Search 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER Reporting Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 Management Tools - Basic 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 Management Tools - Complete 1033 Standard Edition 10.50.1600.1 NoPackage properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 1
Installation location: D:\x64\setup\
Installation edition: STANDARDUser Input Settings:
ACTION: Repair
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASCONFIGDIR: Config
ASDOMAINGROUP: <empty>
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110811_092246\ConfigurationFile.ini
ENU: True
FAILOVERCLUSTERGROUP: <empty>
FAILOVERCLUSTERNETWORKNAME: <empty>
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
PASSPHRASE: *****
QUIET: False
QUIETSIMPLE: False
SQLDOMAINGROUP: <empty>
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: *****
UIMODE: Normal
X86: FalseConfiguration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110811_092246\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x2841E06E@1204@2
Configuration error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110811_092246\Detail.txtFeature: SQL Client Connectivity
Status: Failed: see logs for details
MSI status: Passed
Configuration status: PassedFeature: SQL Client Connectivity SDK
Status: Failed: see logs for details
MSI status: Passed
Configuration status: PassedFeature: SQL Writer
Status: Failed: see logs for details
MSI status: Passed
Configuration status: PassedFeature: SQL Browser
Status: Failed: see logs for details
MSI status: Passed
Configuration status: PassedFeature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x2841E06E@1204@2
Configuration error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110811_092246\Detail.txtFeature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x2841E06E@1204@2
Configuration error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110811_092246\Detail.txtFeature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: PassedFeature: SQL Compact Edition Tools
Status: Failed: see logs for details
MSI status: Passed
Configuration status: PassedFeature: SQL Compact Edition Runtime
Status: Failed: see logs for details
MSI status: Passed
Configuration status: PassedFeature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: PassedFeature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Passed
Configuration status: PassedRules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110811_092246\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indentedException type: System.NullReferenceException
Message:
Object reference not set to an instance of an object.
Data:
DisableWatson = true
Stack:
at Microsoft.SqlServer.Configuration.SetupExtension.UpgradeIncompleteFeatureConfigEventHandler.ValidateClusterStateForRepair(PackageAttribute packageAttribute, FeatureAttribute featureAttribute, String instanceId, ActionKey sender)
at Microsoft.SqlServer.Configuration.SetupExtension.UpgradeIncompleteFeatureConfigEventHandler.FeatureConfigurationExecutionEventHandler(Object sender, FeatureConfigScenarioEventArgs eventArgs, Boolean runValidation, Boolean featureFailed)
at Microsoft.SqlServer.Configuration.SetupExtension.UpgradeIncompleteFeatureConfigEventHandler.PreFeatureConfigurationExecutionEventHandler(Object sender, Object[] objectArray)
at Microsoft.SqlServer.Chainer.Infrastructure.NotificationHandler.Invoke(Object notification, Object[] objectArray)
at Microsoft.SqlServer.Chainer.Infrastructure.NotificationService.OnNotify(Object eventKey, Object notification, Object[] objectArray)
at Microsoft.SqlServer.Configuration.ConfigExtension.ConfigFeatureActionListener.PreFeatureConfigurationExecutionEventHandler(ActionKey key, TextWriter loggingStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionMetadata.NotifyPreExecution(ActionKey actionToRun, TextWriter loggingStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
at Microsoft.SqlServer.Chainer.TimingConfigAction.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun) -
jeudi 11 août 2011 21:16
It looks from other posts that I will probably have to uninstall and re-install SQL 2008 R2.
:-(
Just wondering if there is anything else to check first in case it fails again at the install stage.
-
vendredi 12 août 2011 02:31Modérateur
Hello,
I would prefer a clean install, especially on a cluster. This way I have the peace of mind that future updates and service packs will not fail because of some leftover.
If you are putting a database on a cluster is because is critical and you need high availability.
My suggestion is uninstall and perform a clean install.
Hope this helps.Regards,
Alberto Morillo
SQLCoffee.com -
vendredi 12 août 2011 02:52Modérateur
Hi,
From the setup summary, the SQL Server instance you have installed is not clustered but a stand-alone instance on each Windows Failover cluster nodes. Please choose to install an Failover Cluster when installing SQL Server.
Currently, I would recommend you uninstall the existing failed/incomplete installation and then reinstall SQL Server failover cluster. Here is a KB article about uninstall SQL Server 2008 (applies to 2008 R2 as well): http://support.microsoft.com/kb/955404.
Hope this helps.
Best Regards
Alex Feng | Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. -
vendredi 12 août 2011 15:26
Thanks for the input. Just to be clear, initially this was a clean install on Windows 2008 R2 EE cluster, not standalone....but you have to install one node at a time. The summary file seems to show the results of the "repair" process which didn't work.
I'm going to uninstall SQL 2008 and try again running the install locally.
-
vendredi 12 août 2011 15:57
Okay I followed MS uninstallation procedure and it won't uninstall cleanly for some reason:
Description:
SQL Server 2008 R2 Setup has encountered an error.
Problem signature:
Problem Event Name: SQL100Exception
Problem Signature 01: SQL Server 2008 R2@RTM@
Problem Signature 02: 0x05AA5881
Problem Signature 03: 0x05AA5881
Problem Signature 04: 0x1C2074D8@1216@1
Problem Signature 05: 0x1C2074D8@1216@1
Problem Signature 06: SqlEngineConfigAction_remove_unconfigrc
Problem Signature 07: 0x5F5738E6
Problem Signature 08: Unknown
Problem Signature 09: Unknown
Problem Signature 10: Unknown
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033
Additional information about the problem:
LCID: 1033
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
-
vendredi 12 août 2011 16:05
Final pane of the uninstallation procedure:
Setup process complete
feature name status
database engine services failed
sql server replication failed
full text search success
reporting services success
management tools - complete success
management tools- basic success
sql compact edition tools failed
sql browser failed -
vendredi 12 août 2011 16:29Modérateur
Hello,
Please try to manually uninstall SQL Server with the following resources:
http://support.microsoft.com/kb/955404
http://social.msdn.microsoft.com/Forums/en/sqlexpress/thread/4d6158a1-b601-428c-aad4-a1716e76de1a
http://support.microsoft.com/kb/909967Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
vendredi 12 août 2011 16:42okay, will do.
-
vendredi 12 août 2011 18:16
Manual uninstallation procedure produced the following error:
SQL Server Setup failure.
SQL Server setup has encountered the following error:
The specified value for setting “WORKFLOW” is invalid. The expected values are:
None
RemovePatch
Uninstall
Install
Upgrade
Patch
Repair
LandingPage
ClusterReport
RunRules
PrepareFailoverCluster
CompleteFailoverCluster
InstallFailoverCluster
removeNode
Addnode
EditionUpgrade
Bootstrap
ComponentUddate
Help
RebuildDatabase
Rundiscovery
Error Code 0x84B40002
Tried uninstalling SQL Server 2008 R2 from the control panel, but it fails out with the following:
The following error has occurred:
The SQl Server failover cluster instance " could not be found as a cluster resource.
and....
The following error has occurred:
There was an error attempting to remove the configuration of the product which prevents any other action from occurring. The current configuration of the product is being cancelled as a result.
Setup process complete
Feature Name Status
Database engine services failed
SQL server replication failed
SQL writer failed
SQL browser failed
I followed installation procedures for SQL exactly and the SQL Installation rules were green all the way through prior to it failing out right at the end. Now I can’t even uninstall it . So that means I can’t repair it or re-install SQL 2008 Server, either. It's looking as though I'll have to destroy the cluster and reinstall the Windows 2008 Server OS in order to delete SQL Server.
-
vendredi 12 août 2011 19:33Modérateur
Hello,
What about the instructions given by YoYo Yu:
http://social.msdn.microsoft.com/Forums/en/sqlexpress/thread/4d6158a1-b601-428c-aad4-a1716e76de1aHope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
lundi 15 août 2011 16:28
Hi Alberto, still having install errors right at the end while attempting to install on one of the cluster nodes.
Here is the summary text:
----------------------------------------------------
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893608
Exit facility code: 1306
Exit error code: 24
Exit message: Failed: see details below
Start time: 2011-08-14 15:03:35
End time: 2011-08-14 15:45:16
Requested action: InstallFailoverCluster
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110814_150139\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0xD15B4EB2%400x4BDAF9BA%401306%4024Cluster properties:
Machine name: TSQL1B
Product Instance Instance ID Feature Language Edition Version ClusteredMachine name: TSQL1A
Product Instance Instance ID Feature Language Edition Version ClusteredMachine Properties:
Machine name: TSQL1B
Machine processor count: 2
OS version: Windows Server 2008 R2
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: YesProduct features discovered:
Product Instance Instance ID Feature Language Edition Version ClusteredPackage properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: D:\x64\setup\
Installation edition: STANDARDUser Input Settings:
ACTION: InstallFailoverCluster
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: OUR_COMPANY\svc.Test2008.cluster
AGTSVCPASSWORD: *****
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110814_150139\ConfigurationFile.ini
CUSOURCE:
ENU: True
ERRORREPORTING: False
FAILOVERCLUSTERDISKS: Cluster Disk 2
FAILOVERCLUSTERGROUP: SQL Server (MSSQLSERVER)
FAILOVERCLUSTERIPADDRESSES: <empty>
FAILOVERCLUSTERNETWORKNAME: TSQL2008
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: M:\SQL2008 Data\System
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: OUR_COMPANY\svc.Test2008.cluster
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: M:\SQL2008 Backup
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLDOMAINGROUP: <empty>
SQLSVCACCOUNT: OUR_COMPANY\svc.Test2008.cluster
SQLSVCPASSWORD: *****
SQLSYSADMINACCOUNTS: OUR_COMPANY\JMaloan,OUR_COMPANY
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: M:\SQL2008 Data\DB
SQLUSERDBLOGDIR: M:\SQL2008 Data\Log
SQMREPORTING: False
UIMODE: Normal
X86: FalseConfiguration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110814_150139\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x4BDAF9BA@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110814_150139\Detail.txtFeature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x4BDAF9BA@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110814_150139\Detail.txtFeature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x4BDAF9BA@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110814_150139\Detail.txtFeature: Reporting Services
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: Management Tools - Complete
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: PassedRules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110814_150139\SystemConfigurationCheck_Report.htm
-
lundi 15 août 2011 18:09Modérateur
Hello,
Try to post here the content of the following log or extract the errors from it and post them in this thread:
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110814_150139\Detail.txt
Hope this helps.Regards,
Alberto Morillo
SQLCoffee.com -
lundi 15 août 2011 21:41
Hi, Alberto.....the errors in the Details file are listed below.
My version of SQL 2008 R2 is 10.50.1600.1.
***************************************************************************
2011-08-14 15:44:42 SQLEngine: : Checking Engine checkpoint 'StartEngineService'
2011-08-14 15:44:42 SQLEngine: --SqlServerServiceSCM: Starting SQL via SCM (-mSqlSetup -f -Q-qSQL_Latin1_General_CP1_CI_AS -T4022 -T4010 -T3659 -T3610)...
2011-08-14 15:44:42 Slp: Sco: Attempting to start service MSSQLSERVER
2011-08-14 15:44:42 Slp: Sco: Attempting to open SC Manager
2011-08-14 15:44:42 Slp: Sco: Attempting to open service handle for service MSSQLSERVER
2011-08-14 15:44:43 Slp: Sco: Service MSSQLSERVER started
2011-08-14 15:44:43 Slp: Sco: Attempting to close service handle for service MSSQLSERVER
2011-08-14 15:44:43 Slp: Sco: Attempting to close SC Manager
2011-08-14 15:44:43 Slp: Sco: Attempting to get service process id for service MSSQLSERVER
2011-08-14 15:44:43 Slp: Sco: Attempting to open SC Manager
2011-08-14 15:44:43 Slp: Sco: Attempting to open service handle for service MSSQLSERVER
2011-08-14 15:44:43 Slp: Invoking QueryServiceStatusEx Win32 API
2011-08-14 15:44:43 Slp: Sco: Attempting to close service handle for service MSSQLSERVER
2011-08-14 15:44:43 Slp: Sco: Attempting to close SC Manager
2011-08-14 15:44:43 Slp: Sco: Returning service process id 4428
2011-08-14 15:44:43 SQLEngine: : Checking Engine checkpoint 'GetSqlServerProcessHandle'
2011-08-14 15:44:43 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete' tobe created
2011-08-14 15:44:44 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete' orsql process handle to be signaled
2011-08-14 15:44:44 SQLEngine: : Checking Engine checkpoint 'WaitSqlServerStartEvents'
2011-08-14 15:44:44 SQLEngine: --SqlServerServiceSCM: SQL Server process has died while waiting for SQLServer to start. Process id: 4428
2011-08-14 15:44:44 SQLEngine: Copying 'M:\SQL2008 Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG' to'C:\Program Files\Microsoft SQL Server\100\Setup
Bootstrap\Log\20110814_150139\SQLServer_ERRORLOG_2011-08-14T15.44.44.txt' ...
2011-08-14 15:44:44 Slp: Sco: Attempting to set file full path to 'M:\SQL2008Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'
2011-08-14 15:44:44 Slp: Sco: Attempting to normalize directory path 'M:\SQL2008Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'
2011-08-14 15:44:44 Slp: Sco: Attempting to check if file 'M:\SQL2008Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG' exists
2011-08-14 15:44:44 Slp: Sco: Attempting to copy file 'M:\SQL2008Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG' to file 'C:\Program Files\Microsoft SQL
Server\100\Setup Bootstrap\Log\20110814_150139\SQLServer_ERRORLOG_2011-08-14T15.44.44.txt'
2011-08-14 15:44:44 Slp: Sco: Attempting to check if file 'M:\SQL2008Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG' exists
2011-08-14 15:44:44 Slp: Sco: Attempting to normalize directory path 'C:\Program Files\Microsoft SQLServer\100\Setup Bootstrap\Log\20110814_150139\SQLServer_ERRORLOG_2011-08-14T15.44.44.txt'
2011-08-14 15:44:44 Slp: Sco: Attempting to set file full path to 'C:\Program Files\Microsoft SQLServer\100\Setup Bootstrap\Log\20110814_150139\SQLServer_ERRORLOG_2011-08-14T15.44.44.txt'
2011-08-14 15:44:44 Slp: Sco: Attempting to normalize directory path 'C:\Program Files\Microsoft SQLServer\100\Setup Bootstrap\Log\20110814_150139\SQLServer_ERRORLOG_2011-08-14T15.44.44.txt'
2011-08-14 15:44:44 Slp: Sco: Attempting to check if directory path 'M:\SQL2008Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG' is equal to path 'C:\Program Files\Microsoft SQL
Server\100\Setup Bootstrap\Log\20110814_150139\SQLServer_ERRORLOG_2011-08-14T15.44.44.txt'
2011-08-14 15:44:44 Slp: Sco: Attempting to check if directory path 'M:\SQL2008Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG' is equal to path 'C:\Program Files\Microsoft SQL
Server\100\Setup Bootstrap\Log\20110814_150139\SQLServer_ERRORLOG_2011-08-14T15.44.44.txt'
2011-08-14 15:44:44 Slp: Sco: Attempting to normalize directory path 'M:\SQL2008Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'
2011-08-14 15:44:44 Slp: Sco: Attempting to normalize directory path 'C:\Program Files\Microsoft SQLServer\100\Setup Bootstrap\Log\20110814_150139\SQLServer_ERRORLOG_2011-08-14T15.44.44.txt'
2011-08-14 15:44:44 Slp: Sco: Attempting to get security descriptor for file 'M:\SQL2008Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'
2011-08-14 15:44:44 Slp: Sco: Attempting to check if file 'M:\SQL2008Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG' exists
2011-08-14 15:44:44 Slp: Sco: Returning security descriptorO:S-1-5-21-4058887266-946947433-1674420217-11191G:DUD:AI(A;ID;FA;;;S-1-5-21-4058887266-946947433-1674420217-1
1191)(A;ID;FA;;;SY)(A;ID;FA;;;BA)(A;ID;FA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)(
A;ID;0x1201ff;;;S-1-5-80-344959196-2060754871-2302487193-2804545603-1466107430)
2011-08-14 15:44:44 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRCand scenario ConfigRC.
2011-08-14 15:44:44 Slp: Wait on the Database Engine recovery handle failed. Check the SQL Server error logfor potential causes.
2011-08-14 15:44:44 Slp: The configuration failure category of current exception is ConfigurationFailure
2011-08-14 15:44:44 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRCand scenario ConfigRC.
2011-08-14 15:44:45 Slp: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException: Wait on theDatabase Engine recovery handle failed. Check the SQL Server error log for potential causes.
2011-08-14 15:44:45 Slp: atMicrosoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql)
2011-08-14 15:44:45 Slp: atMicrosoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.ConfigSQLServerSystemDatabases(EffectivePr
operties properties, Boolean isConfiguringTemplateDBs, Boolean useInstallInputs)
2011-08-14 15:44:45 Slp: atMicrosoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.DoCommonDBStartConfig(ConfigActionTiming
timing)
2011-08-14 15:44:45 Slp: atMicrosoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
2011-08-14 15:44:45 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(StringactionId, TextWriter errorStream)
2011-08-14 15:44:45 Slp: Exception: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException.
2011-08-14 15:44:45 Slp: Source: Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.
2011-08-14 15:44:45 Slp: Message: Wait on the Database Engine recovery handle failed. Check the SQL Servererror log for potential causes..
2011-08-14 15:44:45 Slp: Watson Bucket 1
Original Parameter Values2011-08-14 15:44:45 Slp: Parameter 0 : SQL Server 2008 R2@RTM@
2011-08-14 15:44:45 Slp: Parameter 1 :
Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart
2011-08-14 15:44:45 Slp: Parameter 2 :
Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart
2011-08-14 15:44:45 Slp: Parameter 3 :
Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException@1306@24
2011-08-14 15:44:45 Slp: Parameter 4 :
Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException@1306@24
2011-08-14 15:44:45 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
2011-08-14 15:44:45 Slp: Parameter 6 : INSTALL@CONFIGRC@SQL_ENGINE_CORE_INST
2011-08-14 15:44:45 Slp:
Final Parameter Values2011-08-14 15:44:45 Slp: Parameter 0 : SQL Server 2008 R2@RTM@
2011-08-14 15:44:45 Slp: Parameter 1 : 0xD15B4EB2
2011-08-14 15:44:45 Slp: Parameter 2 : 0xD15B4EB2
2011-08-14 15:44:45 Slp: Parameter 3 : 0x4BDAF9BA@1306@24
2011-08-14 15:44:45 Slp: Parameter 4 : 0x4BDAF9BA@1306@24
2011-08-14 15:44:45 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
2011-08-14 15:44:45 Slp: Parameter 6 : 0x9C5770A6
2011-08-14 15:44:47 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server
to file C:\Program Files\Microsoft SQL Server\100\Setup
Bootstrap\Log\20110814_150139\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2011-08-14 15:44:47 Slp: Sco: Attempting to write hklm registry keySOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup
Bootstrap\Log\20110814_150139\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2011-08-14 15:44:47 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to fileC:\Program Files\Microsoft SQL Server\100\Setup
Bootstrap\Log\20110814_150139\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2011-08-14 15:44:47 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MicrosoftSQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup
Bootstrap\Log\20110814_150139\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
2011-08-14 15:44:47 Slp: Sco: Attempting to write hklm registry keySOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL
Server\100\Setup
Bootstrap\Log\20110814_150139\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2011-08-14 15:44:47 Slp: Sco: Attempting to write hklm registry keySOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup
Bootstrap\Log\20110814_150139\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2011-08-14 15:44:53 Slp: Wait on the Database Engine recovery handle failed. Check the SQL Server error logfor potential causes.
2011-08-14 15:44:53 Slp: Watson bucket for exception based failure has been created
2011-08-14 15:45:01 Slp: Error: Action "SqlEngineDBStartConfigAction_install_configrc_Cpu64" failed duringexecution.
2011-08-14 15:45:01 Slp: Completed Action: SqlEngineDBStartConfigAction_install_configrc_Cpu64, returnedFalse
2011-08-14 15:45:01 Slp: Sco: Attempting to get instance feature flag UpgradeIncomplete for featureSQL_Engine_Core_Inst, instance MSSQL10_50.MSSQLSERVER, machine name TSQL1B
2011-08-14 15:45:01 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine TSQL1B
2011-08-14 15:45:01 Slp: Sco: Attempting to open registry subkey
2011-08-14 15:45:01 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQLServer\MSSQL10_50.MSSQLSERVER\UpgradeIncompleteState
2011-08-14 15:45:01 Slp: Sco: Attempting to get registry value SQL_Engine_Core_Inst
2011-08-14 15:45:01 Slp: Sco: Attempting to get feature configuration state for feature SQL_Engine_Core_Inst,instance MSSQL10_50.MSSQLSERVER
2011-08-14 15:45:01 Slp: Sco: Attempting to get instance feature flag ConfigurationState for featureSQL_Engine_Core_Inst, instance MSSQL10_50.MSSQLSERVER, machine name TSQL1B
2011-08-14 15:45:01 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine TSQL1B
2011-08-14 15:45:01 Slp: Sco: Attempting to open registry subkey
2011-08-14 15:45:01 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQLServer\MSSQL10_50.MSSQLSERVER\ConfigurationState
2011-08-14 15:45:01 Slp: Sco: Attempting to get registry value SQL_Engine_Core_Inst
2011-08-14 15:45:01 Slp: Sco: Attempting to get instance feature flag UpgradeIncomplete for featureSQL_Engine_Core_Inst, instance MSSQL10_50.MSSQLSERVER, machine name TSQL1B
2011-08-14 15:45:01 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine TSQL1B
2011-08-14 15:45:01 Slp: Sco: Attempting to open registry subkey
2011-08-14 15:45:01 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQLServer\MSSQL10_50.MSSQLSERVER\UpgradeIncompleteState
2011-08-14 15:45:01 Slp: Sco: Attempting to get registry value SQL_Engine_Core_Inst
2011-08-14 15:45:01 Slp: Sco: Attempting to get feature configuration state for feature SQL_Engine_Core_Inst,instance MSSQL10_50.MSSQLSERVER
2011-08-14 15:45:01 Slp: Sco: Attempting to get instance feature flag ConfigurationState for featureSQL_Engine_Core_Inst, instance MSSQL10_50.MSSQLSERVER, machine name TSQL1B
2011-08-14 15:45:01 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine TSQL1B
2011-08-14 15:45:01 Slp: Sco: Attempting to open registry subkey
2011-08-14 15:45:01 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQLServer\MSSQL10_50.MSSQLSERVER\ConfigurationState
2011-08-14 15:45:01 Slp: Sco: Attempting to get registry value SQL_Engine_Core_Inst
2011-08-14 15:45:01 Slp: Sco: Attempting to get instance feature flag UpgradeIncomplete for featureSQL_Engine_Core_Inst, instance MSSQL10_50.MSSQLSERVER, machine name TSQL1B
2011-08-14 15:45:01 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine TSQL1B
2011-08-14 15:45:01 Slp: Sco: Attempting to open registry subkey
2011-08-14 15:45:01 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQLServer\MSSQL10_50.MSSQLSERVER\UpgradeIncompleteState
2011-08-14 15:45:01 Slp: Sco: Attempting to get registry value SQL_Engine_Core_Inst
2011-08-14 15:45:01 Slp: Sco: Attempting to get feature configuration state for feature SQL_Engine_Core_Inst,instance MSSQL10_50.MSSQLSERVER
2011-08-14 15:45:01 Slp: Sco: Attempting to get instance feature flag ConfigurationState for featureSQL_Engine_Core_Inst, instance MSSQL10_50.MSSQLSERVER, machine name TSQL1B
2011-08-14 15:45:01 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine TSQL1B
2011-08-14 15:45:01 Slp: Sco: Attempting to open registry subkey
2011-08-14 15:45:01 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQLServer\MSSQL10_50.MSSQLSERVER\ConfigurationState
2011-08-14 15:45:01 Slp: Sco: Attempting to get registry value SQL_Engine_Core_Inst
2011-08-14 15:45:01 Slp: Action "AgentScriptConfiguration_install_rc_Cpu64" will return false due to thefollowing conditions:
2011-08-14 15:45:01 Slp: Condition "Feature dependency condition for action:AgentScriptConfiguration_install_rc_Cpu64 The condition tests feature:
SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for
results: ValidateResult, Result." did not pass as it returned false and true was expected.
2011-08-14 15:45:01 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:01 Slp: Action "RS_RunInstallScriptsAction_Cpu64" will return false due to the followingconditions:
2011-08-14 15:45:01 Slp: Condition "Feature dependency condition for action: RS_RunInstallScriptsAction_Cpu64The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant
features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and
true was expected.
2011-08-14 15:45:01 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:01 Slp: Action "SqlEngineDBStopConfigAction_install_configrc_Cpu64" will return false due tothe following conditions:
2011-08-14 15:45:01 Slp: Condition "Feature dependency condition for action:SqlEngineDBStopConfigAction_install_configrc_Cpu64 The condition tests feature:
SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for
results: ValidateResult, Result." did not pass as it returned false and true was expected.
2011-08-14 15:45:01 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:01 Slp: Action"ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_ConfigRC_postmsi" will return false due to
the following conditions:
2011-08-14 15:45:01 Slp: Condition "Feature dependency condition for action:ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_ConfigRC_postmsi The condition tests
feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested
for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2011-08-14 15:45:01 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
*
*
*
*
*2011-08-14 15:45:01 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_ConfigRC_postmsi"
will return false due to the following conditions:
2011-08-14 15:45:01 Slp: Condition "Feature dependency condition for action:ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_ConfigRC_postmsi The condition tests feature:
SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature is tested for results:
ValidateResult, Result." did not pass as it returned false and true was expected.
2011-08-14 15:45:01 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
*
*
*
*
2011-08-14 15:45:11 Slp: Action"ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due
to the following conditions:
2011-08-14 15:45:11 Slp: Condition "Feature dependency condition for action:ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests
feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is
tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2011-08-14 15:45:11 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:11 Slp: Action "SqlBrowserConfigEngAction_install_Startup_Cpu64" will return false due tothe following conditions:
2011-08-14 15:45:11 Slp: Condition "Feature dependency condition for action:SqlBrowserConfigEngAction_install_Startup_Cpu64 The condition tests feature:
SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for
results: ValidateResult, Result." did not pass as it returned false and true was expected.
2011-08-14 15:45:11 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:11 Slp: Action "SqlEngineConfigAction_install_startup_Cpu64" will return false due to thefollowing conditions:
2011-08-14 15:45:11 Slp: Condition "Feature dependency condition for action:SqlEngineConfigAction_install_startup_Cpu64 The condition tests feature:
SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for
results: ValidateResult, Result." did not pass as it returned false and true was expected.
2011-08-14 15:45:11 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:11 Slp: Action"ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to
the following conditions:
2011-08-14 15:45:11 Slp: Condition "Feature dependency condition for action:ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests
feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested
for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2011-08-14 15:45:11 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:11 Slp: Action "AgentInstall_AgentInstallStartup_Cpu64" will return false due to thefollowing conditions:
2011-08-14 15:45:11 Slp: Condition "Feature dependency condition for action:AgentInstall_AgentInstallStartup_Cpu64 The condition tests feature:
MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for
results: ValidateResult, Result." did not pass as it returned false and true was expected.
2011-08-14 15:45:11 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:11 Slp: Action"ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false
due to the following conditions:
2011-08-14 15:45:11 Slp: Condition "Feature dependency condition for action:ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests
feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There are 3 dependant features. The feature is
tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2011-08-14 15:45:11 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:11 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Startup_postmsi"will return false due to the following conditions:
2011-08-14 15:45:11 Slp: Condition "Feature dependency condition for action:ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Startup_postmsi The condition tests feature:
SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature is tested for results:
ValidateResult, Result." did not pass as it returned false and true was expected.
2011-08-14 15:45:11 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:11 Slp: Action "FulltextConfigAction_install_startup_Cpu64" will return false due to thefollowing conditions:
2011-08-14 15:45:11 Slp: Condition "Feature dependency condition for action:FulltextConfigAction_install_startup_Cpu64 The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64.
There are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as
it returned false and true was expected.
2011-08-14 15:45:11 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:12 Slp: Action"ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return
false due to the following conditions:
2011-08-14 15:45:12 Slp: Condition "Feature dependency condition for action:ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition
tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature
is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2011-08-14 15:45:12 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:12 Slp: Action"ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false
due to the following conditions:
2011-08-14 15:45:12 Slp: Condition "Feature dependency condition for action:ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests
feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested
for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2011-08-14 15:45:12 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:12 Slp: Action"ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will
return false due to the following conditions:
2011-08-14 15:45:12 Slp: Condition "Feature dependency condition for action:ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The
condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There are 3 dependant
features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and
true was expected.
2011-08-14 15:45:12 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:12 Slp: Action"ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_StartupFinalize_postmsi" will return false due to
the following conditions:
2011-08-14 15:45:12 Slp: Condition "Feature dependency condition for action:ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_StartupFinalize_postmsi The condition tests feature:
SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature is tested for results:
ValidateResult, Result." did not pass as it returned false and true was expected.
2011-08-14 15:45:12 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
*
*
*
*
*
*2011-08-14 15:45:13 Slp: Sco: Attempting to set value SQL_Browser_Redist
2011-08-14 15:45:13 Slp: SetValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQLServer\100\ConfigurationState, Name = SQL_Browser_Redist
2011-08-14 15:45:13 Slp: Action"ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Finalize_finalize" will return false due
to the following conditions:
2011-08-14 15:45:13 Slp: Condition "Feature dependency condition for action:ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Finalize_finalize The condition tests
feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is
tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was
expected.
2011-08-14 15:45:13 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:13 Slp: Action "cluster_group_cluster_finalconfig_Cpu64" will return false due to thefollowing conditions:
2011-08-14 15:45:13 Slp: Condition "Feature dependency condition for action:cluster_group_cluster_finalconfig_Cpu64 The condition tests feature:
SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for
results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2011-08-14 15:45:13 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:13 Slp: Action"ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Finalize_finalize" will return false due
to the following conditions:
2011-08-14 15:45:13 Slp: Condition "Feature dependency condition for action:ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Finalize_finalize The condition tests
feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested
for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2011-08-14 15:45:13 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:13 Slp: Action"ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Finalize_finalize" will return
false due to the following conditions:
2011-08-14 15:45:13 Slp: Condition "Feature dependency condition for action:ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Finalize_finalize The condition
tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There are 3 dependant features. The
feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and
true was expected.
2011-08-14 15:45:13 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:13 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Finalize_finalize"will return false due to the following conditions:
2011-08-14 15:45:13 Slp: Condition "Feature dependency condition for action:ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Finalize_finalize The condition tests feature:
SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature is tested for results:
ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2011-08-14 15:45:13 Slp: Condition is false because the required featureSQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2011-08-14 15:45:13 Slp: Completed Action: FinalizeTimingConfigAction, returned True
2011-08-14 15:45:13 Slp: ----------------------------------------------------------------------
2011-08-14 15:45:13 Slp: Running Action: CreateARPRegKeyAction
2011-08-14 15:45:13 Slp: Completed Action: CreateARPRegKeyAction, returned True
2011-08-14 15:45:13 Slp: ----------------------------------------------------------------------
2011-08-14 15:45:13 Slp: Skipping Action: RunRefreshDiscoveryAction
2011-08-14 15:45:13 Slp: Action is being skipped due to the following restrictions:
2011-08-14 15:45:13 Slp: Condition "Do any product features match one of the expected scenarios" did not passas it returned false and true was expected.
2011-08-14 15:45:13 Slp: ----------------------------------------------------------------------
2011-08-14 15:45:13 Slp: Running Action: NotifyProgressComplete
2011-08-14 15:45:13 Slp: Sco: Attempting to set file full path to 'C:\Program Files\Microsoft SQLServer\100\Setup Bootstrap\SQLServer2008R2\x64\setup100.exe.config'
2011-08-14 15:45:13 Slp: Sco: Attempting to normalize directory path 'C:\Program Files\Microsoft SQLServer\100\Setup Bootstrap\SQLServer2008R2\x64\setup100.exe.config'
2011-08-14 15:45:13 Slp: Sco: Attempting to check if file 'C:\Program Files\Microsoft SQL Server\100\SetupBootstrap\SQLServer2008R2\x64\setup100.exe.config' exists
2011-08-14 15:45:13 Slp: The setup100.exe.config file was not found, therefore the DTSWizard and SQLWatsonapp config files were not replaced
2011-08-14 15:45:13 Slp: Completed Action: NotifyProgressComplete, returned True
2011-08-14 15:45:14 Slp: ----------------------------------------------------------------------
2011-08-14 15:45:14 Slp: Skipping Action: DeleteUninstalledPatchRegistryAndCacheFolderAction
2011-08-14 15:45:14 Slp: Action is being skipped due to the following restrictions:
2011-08-14 15:45:14 Slp: Condition "Do any of the specified features match the expected scenario Uninstall"did not pass as it returned false and true was expected.
2011-08-14 15:45:14 Slp: Completed Action: ExecuteExtendedTimingsWorkflow, returned True
2011-08-14 15:45:14 Slp: ----------------------------------------------------------------------
2011-08-14 15:45:14 Slp: Running Action: ExecuteCloseWorkflow
2011-08-14 15:45:14 Slp: Workflow to execute: 'CLOSE'
2011-08-14 15:45:14 Slp: ----------------------------------------------------------------------
2011-08-14 15:45:14 Slp: Running Action: ProduceStatusLogs
2011-08-14 15:45:15 Slp: Completed Action: ProduceStatusLogs, returned True
2011-08-14 15:45:15 Slp: ----------------------------------------------------------------------
2011-08-14 15:45:15 Slp: Running Action: FinalizeProgressStatus
2011-08-14 15:45:15 Slp: Completed Action: FinalizeProgressStatus, returned True
2011-08-14 15:45:15 Slp: ----------------------------------------------------------------------
2011-08-14 15:45:15 Slp: Running Action: RebootMessageAction
2011-08-14 15:45:15 Slp: Completed Action: RebootMessageAction, returned True
2011-08-14 15:45:15 Slp: ----------------------------------------------------------------------
2011-08-14 15:45:15 Slp: Skipping Action: FinishPage
2011-08-14 15:45:15 Slp: Action is being skipped due to the following restrictions:
2011-08-14 15:45:15 Slp: Condition "Is the user's scenario set to EditionUpgrade" did not pass as it returnedfalse and true was expected.
2011-08-14 15:45:15 Slp: ----------------------------------------------------------------------
2011-08-14 15:45:15 Slp: Running Action: CloseUI
2011-08-14 15:45:15 Slp: Stop action skipped in UI Mode Full
2011-08-14 15:45:15 Slp: Completed Action: CloseUI, returned True
2011-08-14 15:45:16 Slp: Completed Action: ExecuteCloseWorkflow, returned True
2011-08-14 15:45:16 Slp: Completed Action: ExecuteCompleteWorkflow, returned True
2011-08-14 15:45:22 Slp:
2011-08-14 15:45:22 Slp:
2011-08-14 15:45:22 Slp: ----------------------------------------------------------------------
2011-08-14 15:45:22 Slp:
2011-08-14 15:45:22 Slp: Error result: -2061893608
2011-08-14 15:45:22 Slp: Result facility code: 1306
2011-08-14 15:45:22 Slp: Result error code: 24
2011-08-14 15:45:22 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2011-08-14 15:45:22 Slp: Sco: Attempting to open registry subkey
2011-08-14 15:45:22 Slp: Sco: Attempting to open registry subkeySoftware\Microsoft\PCHealth\ErrorReporting\DW\Installed
2011-08-14 15:45:22 Slp: Sco: Attempting to get registry value DW0201
2011-08-14 15:45:29 Slp: Submitted 1 of 1 failures to the Watson data repository -
lundi 15 août 2011 22:56Modérateur
Hello,
Please try to create a local user account with strong password and add it to the local administrators group. Run SQL Server setup and provide that account as SQL Server service account.
The account you are using to run setup, should also have local administrative privileges on the server
Regards,
Alberto Morillo
SQLCoffee.com -
mardi 16 août 2011 00:50Modérateurplease provide us the content of ERRORLOG.
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110814_150139\SQLServer_ERRORLOG_2011-08-14T15.44.44.txt
Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
--------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------------------------------------------------------------------
My Blog | Team Blog | @Twitter -
mardi 16 août 2011 15:45
Balmukund, here are the contents from C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110814_150139\SQLServer_ERRORLOG_2011-08-14T15.44.44:
2011-08-14 15:44:43.49 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)2011-08-14 15:44:43.49 Server (c) Microsoft Corporation.
2011-08-14 15:44:43.49 Server All rights reserved.
2011-08-14 15:44:43.49 Server Server process ID is 4428.
2011-08-14 15:44:43.49 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2011-08-14 15:44:43.49 Server Authentication mode is MIXED.
2011-08-14 15:44:43.49 Server Logging SQL Server messages in file 'M:\SQL2008 Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2011-08-14 15:44:43.51 Server Registry startup parameters:
-d M:\SQL2008 Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e M:\SQL2008 Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l M:\SQL2008 Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2011-08-14 15:44:43.51 Server Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q SQL_Latin1_General_CP1_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
2011-08-14 15:44:43.51 Server Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2011-08-14 15:44:43.51 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-08-14 15:44:43.51 Server Detected 2 CPUs. This is an informational message; no user action is required.
2011-08-14 15:44:43.62 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2011-08-14 15:44:43.63 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2011-08-14 15:44:43.73 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2011-08-14 15:44:43.74 Server Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action is required.
2011-08-14 15:44:43.76 spid7s Warning ******************
2011-08-14 15:44:43.76 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2011-08-14 15:44:43.79 spid7s Starting up database 'master'.
2011-08-14 15:44:43.85 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2011-08-14 15:44:43.96 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = ''.
2011-08-14 15:44:43.96 spid7s Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
2011-08-14 15:44:43.96 spid7s Starting up database 'mssqlsystemresource'.
2011-08-14 15:44:44.00 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2011-08-14 15:44:44.59 spid7s Password policy update was successful.
2011-08-14 15:44:44.60 spid8s Starting up database 'model'.
2011-08-14 15:44:44.61 spid7s Server name is 'TSQL1B'. This is an informational message only. No user action is required.
2011-08-14 15:44:44.79 Server A self-generated certificate was successfully loaded for encryption.
2011-08-14 15:44:44.80 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2011-08-14 15:44:44.80 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2011-08-14 15:44:44.82 spid8s Clearing tempdb database.
2011-08-14 15:44:44.82 spid8s Error: 5123, Severity: 16, State: 1.
2011-08-14 15:44:44.82 spid8s CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'M:\SQL2008 Data\DB\tempdb.mdf'.
2011-08-14 15:44:44.83 spid8s Error: 5123, Severity: 16, State: 1.
2011-08-14 15:44:44.83 spid8s CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'M:\SQL2008 Data\DB\tempdb.mdf'.
2011-08-14 15:44:44.83 spid10s A new instance of the full-text filter daemon host process has been successfully started.
2011-08-14 15:44:44.85 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098, state: 15. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2011-08-14 15:44:44.85 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2011-08-14 15:44:44.86 spid8s Error: 17204, Severity: 16, State: 1.
2011-08-14 15:44:44.86 spid8s FCB::Open failed: Could not open file M:\SQL2008 Data\DB\tempdb.mdf for file number 1. OS error: 2(The system cannot find the file specified.).
2011-08-14 15:44:44.86 spid8s Error: 5120, Severity: 16, State: 101.
2011-08-14 15:44:44.86 spid8s Unable to open the physical file "M:\SQL2008 Data\DB\tempdb.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
2011-08-14 15:44:44.86 spid8s Error: 1802, Severity: 16, State: 4.
2011-08-14 15:44:44.86 spid8s CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
2011-08-14 15:44:44.86 spid8s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized. -
mardi 16 août 2011 22:17
I rolled back to a previous snapshot and re-installed SQL 2008 R2 slipstreamed with SP1 onto the first node and essentially got the same errors...."wait on the database engine recovery handle failed".
Prior to the installation I re-ran cluster validation tests and got passes across the board. I'm thinking the clustered storage won't allow SQL application to write to it....
***********************************************
2011-08-16 13:02:02.26 Server Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
Jun 17 2011 00:54:03
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)2011-08-16 13:02:02.26 Server (c) Microsoft Corporation.
2011-08-16 13:02:02.26 Server All rights reserved.
2011-08-16 13:02:02.26 Server Server process ID is 2088.
2011-08-16 13:02:02.26 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2011-08-16 13:02:02.26 Server Authentication mode is MIXED.
2011-08-16 13:02:02.26 Server Logging SQL Server messages in file 'M:\SQL2008 Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2011-08-16 13:02:02.26 Server Registry startup parameters:
-d M:\SQL2008 Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e M:\SQL2008 Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l M:\SQL2008 Data\System\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2011-08-16 13:02:02.26 Server Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q SQL_Latin1_General_CP1_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
-T 902
2011-08-16 13:02:02.28 Server Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2011-08-16 13:02:02.28 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-08-16 13:02:02.28 Server Detected 2 CPUs. This is an informational message; no user action is required.
2011-08-16 13:02:02.42 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2011-08-16 13:02:02.46 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2011-08-16 13:02:02.56 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2011-08-16 13:02:02.57 Server Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action is required.
2011-08-16 13:02:02.58 spid5s Warning ******************
2011-08-16 13:02:02.58 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.
2011-08-16 13:02:02.59 spid5s Starting up database 'master'.
2011-08-16 13:02:02.67 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2011-08-16 13:02:02.78 spid5s FILESTREAM: effective level = 0, configured level = 0, file system access share name = ''.
2011-08-16 13:02:02.78 spid5s Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
2011-08-16 13:02:02.78 spid5s Starting up database 'mssqlsystemresource'.
2011-08-16 13:02:02.83 spid5s The resource database build version is 10.50.2500. This is an informational message only. No user action is required.
2011-08-16 13:02:03.68 spid5s Password policy update was successful.
2011-08-16 13:02:03.69 spid9s Starting up database 'model'.
2011-08-16 13:02:03.84 spid5s Server name is 'TSQL1B'. This is an informational message only. No user action is required.
2011-08-16 13:02:03.92 Server A self-generated certificate was successfully loaded for encryption.
2011-08-16 13:02:03.92 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2011-08-16 13:02:03.92 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2011-08-16 13:02:03.97 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098, state: 15. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2011-08-16 13:02:03.97 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2011-08-16 13:02:04.01 spid9s Clearing tempdb database.
2011-08-16 13:02:04.02 spid9s Error: 5123, Severity: 16, State: 1.
2011-08-16 13:02:04.02 spid9s CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'M:\SQL2008 Data\DB\tempdb.mdf'.
2011-08-16 13:02:04.02 spid9s Error: 5123, Severity: 16, State: 1.
2011-08-16 13:02:04.02 spid9s CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'M:\SQL2008 Data\DB\tempdb.mdf'.
2011-08-16 13:02:04.03 spid9s Error: 17204, Severity: 16, State: 1.
2011-08-16 13:02:04.03 spid9s FCB::Open failed: Could not open file M:\SQL2008 Data\DB\tempdb.mdf for file number 1. OS error: 2(The system cannot find the file specified.).
2011-08-16 13:02:04.03 spid9s Error: 5120, Severity: 16, State: 101.
2011-08-16 13:02:04.03 spid9s Unable to open the physical file "M:\SQL2008 Data\DB\tempdb.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
2011-08-16 13:02:04.03 spid9s Error: 1802, Severity: 16, State: 4.
2011-08-16 13:02:04.03 spid9s CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
2011-08-16 13:02:04.03 spid9s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2011-08-16 13:02:04.06 spid10s A new instance of the full-text filter daemon host process has been successfully started. -
mardi 16 août 2011 22:50Modérateur The cause of the problem is
CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'M:\SQL2008 Data\DB\tempdb.mdf'.
Please give full control to SQL Service account on highlighted path.
Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
--------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------------------------------------------------------------------
My Blog | Team Blog | @Twitter- Marqué comme réponse BalmukundMicrosoft Employee, Moderator lundi 22 août 2011 09:45
-
mercredi 17 août 2011 19:22
Thanks, Balmukund:
I gave the sql service account "full control" of all storage and it still failed out right at the end of the installation. Does SQL Server 2008 R2 work well with mount points? I'm starting to think it just won't work with this folder structure....
M:\ <----- Mount Point
M:\SQL2008 Backup
M:\SQL2008 Data\
\DB
\Log
\System
SUMMARY:
******************************
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2066808829
Exit facility code: 1231
Exit error code: 3
Exit message: Failed: see details below
Start time: 2011-08-17 11:26:57
End time: 2011-08-17 11:47:25
Requested action: InstallFailoverCluster
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110817_112412\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0x88792597%400xBB814387Cluster properties:
Machine name: TSQL1B
Product Instance Instance ID Feature Language Edition Version ClusteredMachine name: TSQL1A
Product Instance Instance ID Feature Language Edition Version ClusteredMachine Properties:
Machine name: TSQL1B
Machine processor count: 2
OS version: Windows Server 2008 R2
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: YesProduct features discovered:
Product Instance Instance ID Feature Language Edition Version ClusteredPackage properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: C:\New Install Folder\x64\setup\
Installation edition: STANDARDUser Input Settings:
ACTION: InstallFailoverCluster
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: OUR_COMPANY\svc.Test2008.cluster
AGTSVCPASSWORD: *****
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110817_112412\ConfigurationFile.ini
CUSOURCE:
ENU: True
ERRORREPORTING: False
FAILOVERCLUSTERDISKS: Cluster Disk 2
FAILOVERCLUSTERGROUP: TSQL2008
FAILOVERCLUSTERIPADDRESSES: <empty>
FAILOVERCLUSTERNETWORKNAME: TSQL2008
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: M:\SQL2008 Data\System
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: OUR_COMPANY\svc.Test2008.cluster
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: M:\SQL2008 Backup
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLDOMAINGROUP: <empty>
SQLSVCACCOUNT: OUR_COMPANY\svc.Test2008.cluster
SQLSVCPASSWORD: *****
SQLSYSADMINACCOUNTS: OUR_COMPANY\jmaloan
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: M:\SQL2008 Data\DB
SQLUSERDBLOGDIR: M:\SQL2008 Data\Log
SQMREPORTING: False
UIMODE: Normal
X86: FalseConfiguration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110817_112412\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: PassedFeature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: PassedFeature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: PassedFeature: Reporting Services
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: Management Tools - Complete
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: PassedRules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110817_112412\SystemConfigurationCheck_Report.htm
-
jeudi 18 août 2011 02:00Modérateur
Hi,
SQL Server 2005 and onward failover clusters support to use mount points for storage. However, during the initial installation of failover cluster, please don't user mount points. After installation, you can add mount points to the failover cluster group and create your database on mount points. For more information: http://blogs.technet.com/b/patricg/archive/2005/11/25/415097.aspx, http://support.microsoft.com/kb/819546.
Best Regards
Alex Feng | Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Marqué comme réponse Stephanie LvModerator lundi 22 août 2011 09:21
-
lundi 22 août 2011 21:20
Alex:
Yes the issue was using mount points in the cluster storage. SQL 2008 doesn’t like installing anything to mount points for some reason, but you need to configure the LUNs as mount points in SnapDrive if you want to use them that way for the cluster.
Solution was to create subfolders on the LUNs and install SQL 2008 R2 to the subfolders – I just called them “Data”, i.e. M:\SQL2008 Data\System\Data instead of M:\SQL2008 Data\System.....otherwise the install fails right at the end with some weird permissions errors.
I had to rebuild one of my virtual servers due to failed SQL 2008 install which could not be backed-out, rebuild the cluster, add the subfolders to the shared storage, then proceed with the installation of SQL 2008 R2.
Thanks for the help. :-)
.png)
