Not able to use Sql Server 2012 Intellisenese

I am not able to use Sql Server Intellisence .
I refer following links
http://blog.sqlauthority.com/2009/03/31/sql-server-2008-intellisense-does-not-work-enable-intellisense/
http://www.mssqltips.com/sqlservertip/2591/troubleshooting-intellisense-in-sql-server-management-studio-2012/

Hi,
Check the below link. Hope it helps
http://msdn.microsoft.com/en-us/library/ms173434(v=SQL.110).aspx
You need to refresh it if at all you have created new schema and added tables to it. Go to the editor pane in SQL Server Management Studio, and press CTRL+SHIFT+R.
Regards, PS

Similar Messages

Using SQL Server 2012 Express with Bitocker

Hello,
I'm currently working on getting our SQL Server Express database working with BitLocker but I am coming across a few problems. Here is my scenario:
The OS is partitioned into two volumes (C and D).
The C volume contains the OS and Software, while the D volume is primarily used for the database files (logs, back, and mdf).
The D volume is encrypted using BitLocker
The database connects using the SA account (SQL Server Authentication)
From what I understand, BitLocker must be enabled with the same account that the SQL Server is running on. So what I have done is change the SQL Server service account to the user account (lets say its called User) via SQL Configuration Manager. While staying
logged into User account, I then enable BitLocker via Control Panel -> System and Security -> BitLocker Drive Encryption. I then reboot and then while the software is trying to connect to the database I get the following exception:
'login failed for user sa'.
Is there anything I need to do to get this working? Thanks for the help.

Hi moncadad,
When you turn off BitLocker, does the database also show “Recovery Pending”? If so, the simplest cause for “Recovery Pending” might be that a disk spin-up was slow, or a disk became full. Please read this
blog to fix the issue, then check if you can successfully connect to the database after you turn on BitLocker.
However, if you are not able to view the database contents only after you turn on BitLocker, I suspect that there are some issues about configuring BitLocker. As far as I know, Bitlocker must be performed by a member of Local Admins Group, please make sure
that your account is a member of Local Admins Group on your computer.
Also I would like to recommend you post the question in the
Microsoft Bitlocker Administration and Monitoring (MBAM) forum to get better support. For more details about configuring SQL Server with Bitlocker, please review the following similar articles.
Using SQL Server 2012 Standard with Bitlocker
How can I retrieve my BitLocker recovery key from MBAM in Windows PE
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

Using SQL Server 2012 SSIS to Extract Data From SAP

Hi
What is the current best practice for using SQL Server 2012 SSIS to extract data from SAP R3? Please note we are looking for a solution that does not use SAP BW or SAP OHS.
Ideally we would like to build our ETL SSIS process to make a .NET call to an SAP RFC procedure and avoid using web services.
With SS2012 can we use any of these without using SAP BW:
- SAP .NET Connector
- MS ADO .NET
- BizTalk .NET 3.0 Adapter
Thanks and take care,
Shayne

Hi Shayne,
You can use the .NET Framework Data Provider for mySAP Business Suite along with SQL Server Integration Service (SSIS) to import data from an SAP system into SQL Server database tables, flat files, or other compatible destination types. You can create an SSIS
package that can be executed to import data from an SAP system.
You must use the SQL Server Import and Export wizard to import data into the SQL Server database. You must provide a select query to specify data to be imported. The query must confirm to the semantics supported by the Data Provider for SAP. You can start the
SQL Server Import Export Wizard either from the SQL Server Management Studio or from an Integration Service project in Visual Studio. Detail steps please see:
Importing SAP Data Using SQL Server Management Studio:
http://msdn.microsoft.com/en-us/library/cc185161(v=bts.10).aspx
Importing SAP Data Using Visual Studio:
http://msdn.microsoft.com/en-us/library/cc185254(v=bts.10).aspx
Please feel free to ask if you have any question.
Thanks,
Eileen
Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

Not able to install SQL server on windows 7 - Installation halts during pre-installation.

Hi Team,
Am not able to install SQL Server on my windows. i have checked several links and sites. But nothing helped. Following is captured in the boot strap logs.
2014-09-19 12:31:48 Slp: Running Action: StartSqmSession
2014-09-19 12:31:48 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-09-19 12:31:48 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
2014-09-19 12:31:48 Slp: Sco: Attempting to get registry value CustomerFeedback
2014-09-19 12:31:48 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
2014-09-19 12:31:48 Slp: Completed Action: StartSqmSession, returned True
2014-09-19 12:31:48 Slp: ----------------------------------------------------------------------
2014-09-19 12:31:48 Slp: Running Action: ValidateSettingsAgainstScenario
2014-09-19 12:31:48 Slp: Scenario: RunRules
2014-09-19 12:31:48 Slp: Completed Action: ValidateSettingsAgainstScenario, returned True
2014-09-19 12:31:48 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True
2014-09-19 12:31:48 Slp: ----------------------------------------------------------------------
2014-09-19 12:31:48 Slp: Running Action: RunDiscoveryAction
2014-09-19 12:31:48 Slp: Running discovery on local machine
2014-09-19 12:31:48 Slp: Discovery on local machine is complete
2014-09-19 12:31:48 Slp: Completed Action: RunDiscoveryAction, returned True
2014-09-19 12:31:48 Slp: ----------------------------------------------------------------------
2014-09-19 12:31:48 Slp: Running Action: DiscoverClusterData
2014-09-19 12:31:48 Slp: Completed Action: DiscoverClusterData, returned True
2014-09-19 12:31:48 Slp: ----------------------------------------------------------------------
2014-09-19 12:31:48 Slp: Running Action: RunStandaloneRules
2014-09-19 12:31:48 Slp: Running in UI mode, unattended rules execution skipped.
2014-09-19 12:31:48 Slp: Completed Action: RunStandaloneRules, returned True
2014-09-19 12:31:48 Slp: ----------------------------------------------------------------------
2014-09-19 12:31:48 Slp: Running Action: RunRulesUI
2014-09-19 12:31:48 Slp: Start Action: RunRulesUI
2014-09-19 12:31:48 Slp: Configuration file: D:\Setup\SQL2008_R2\Standard Edition\x64\configuration.uicfg
2014-09-19 12:31:48 Slp: Adding registration information 'ShowWizard' for type 'Microsoft.SqlServer.Management.ActionHandlerInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'InstallWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'InstallClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'AddNode' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'RemoveNode' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'PrepareClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'CompleteClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'UninstallWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'UpgradeWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'ComponentUpdate' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'RepairWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'RunRulesUI' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'EditionUpgradeWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'PatchWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'RemovePatchWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'PrepareImageWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:48 Slp: Adding registration information 'CompleteImageWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-19 12:31:49 Slp: Rules to be checked: OsVersionCheck;ThreadHasAdminPrivilegeCheck;RebootRequiredCheck;WmiServiceStateCheck;AclPermissionsFacet;MediaPathLength;SetupCompatibilityCheck
2014-09-19 12:31:49 Slp: If any rule does not pass, setup can still continue: True
2014-09-19 12:31:49 Slp: Adding rule result notification channel: RulesEngineNotificationChannel
2014-09-19 12:31:49 Slp: Loading rule: OsVersionCheck
2014-09-19 12:31:49 Slp: Creating rule target object: Microsoft.SqlServer.Configuration.SetupExtension.FacetOsInfo
2014-09-19 12:31:49 Slp: Send result to channel : RulesEngineNotificationChannel
2014-09-19 12:31:50 Slp: Loading rule: ThreadHasAdminPrivilegeCheck
2014-09-19 12:31:50 Slp: Creating rule target object: Microsoft.SqlServer.Configuration.SetupExtension.FacetAdminCheck
2014-09-19 12:31:50 Slp: Send result to channel : RulesEngineNotificationChannel
2014-09-19 12:31:50 Slp: Loading rule: RebootRequiredCheck
2014-09-19 12:31:50 Slp: Creating rule target object: Microsoft.SqlServer.Configuration.SetupExtension.FacetRebootRequired
2014-09-19 12:31:50 Slp: Send result to channel : RulesEngineNotificationChannel
2014-09-19 12:31:50 Slp: Loading rule: WmiServiceStateCheck
2014-09-19 12:31:50 Slp: Creating rule target object: Microsoft.SqlServer.Configuration.SetupExtension.WmiServiceInfo
2014-09-19 12:31:50 Slp: Send result to channel : RulesEngineNotificationChannel
2014-09-19 12:31:50 Slp: Loading rule: AclPermissionsFacet
2014-09-19 12:31:50 Slp: Creating rule target object: Microsoft.SqlServer.Configuration.SetupExtension.AclPermissionsFacet
2014-09-19 12:31:50 Slp: Send result to channel : RulesEngineNotificationChannel
2014-09-19 12:31:50 Slp: Loading rule: MediaPathLength
2014-09-19 12:31:50 Slp: Creating rule target object: Microsoft.SqlServer.Configuration.SetupExtension.MediaPathLenghtFacet
2014-09-19 12:31:50 Slp: Send result to channel : RulesEngineNotificationChannel
2014-09-19 12:31:50 Slp: Loading rule: SetupCompatibilityCheck
2014-09-19 12:31:50 Slp: Creating rule target object: Microsoft.SqlServer.Configuration.SetupExtension.SetupCompatibilityCheck
2014-09-19 12:31:50 Slp: Send result to channel : RulesEngineNotificationChannel
2014-09-19 12:31:50 Slp: Executing rules engine...
2014-09-19 12:31:50 Slp: Completed Action: RunRulesUI, returned True
2014-09-19 12:31:50 Slp: ----------------------------------------------------------------------
2014-09-19 12:31:50 Slp: Running Action: GatherUserSettings
2014-09-19 12:31:50 Slp: Start rule execution, total number of rules loaded: 7
2014-09-19 12:31:50 Slp: Initializing rule : Minimum operating system version
2014-09-19 12:31:50 Slp: Rule applied features : ALL
2014-09-19 12:31:50 Slp: Rule is will be executed : True
2014-09-19 12:31:50 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.FacetOsInfo
2014-09-19 12:31:50 Slp: Rule 'OsVersionCheck' detection result: major=6, minor=1, SP=1
2014-09-19 12:31:50 Slp: Evaluating rule : OsVersionCheck
2014-09-19 12:31:50 Slp: Rule running on machine: J1018165WIN7LT
2014-09-19 12:31:50 Slp: Rule evaluation done : Succeeded
2014-09-19 12:31:50 Slp: Rule evaluation message: The operating system version meets the minimum requirements for this product.
2014-09-19 12:31:50 Slp: Send result to channel : RulesEngineNotificationChannel
2014-09-19 12:31:50 Slp: Initializing rule : Setup administrator
2014-09-19 12:31:50 Slp: Rule applied features : ALL
2014-09-19 12:31:50 Slp: Rule is will be executed : True
2014-09-19 12:31:50 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.FacetAdminCheck
2014-09-19 12:31:50 Slp: Rule 'ThreadHasAdminPrivilegeCheck' Result: Running thread has administrator privilege.
2014-09-19 12:31:50 Slp: Evaluating rule : ThreadHasAdminPrivilegeCheck
2014-09-19 12:31:50 Slp: Rule running on machine: J1018165WIN7LT
2014-09-19 12:31:50 Slp: Rule evaluation done : Succeeded
2014-09-19 12:31:50 Slp: Rule evaluation message: The account running SQL Server Setup has administator rights on the computer.
2014-09-19 12:31:50 Slp: Send result to channel : RulesEngineNotificationChannel
2014-09-19 12:31:50 Slp: Initializing rule : Restart computer
2014-09-19 12:31:50 Slp: Rule applied features : ALL
2014-09-19 12:31:50 Slp: Rule is will be executed : True
2014-09-19 12:31:50 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.FacetRebootRequired
2014-09-19 12:31:50 Slp: Rule 'RebootRequiredCheck' results: IsRebootNotRequired=True
2014-09-19 12:31:50 Slp: Evaluating rule : RebootRequiredCheck
2014-09-19 12:31:50 Slp: Rule running on machine: J1018165WIN7LT
2014-09-19 12:31:50 Slp: Rule evaluation done : Succeeded
2014-09-19 12:31:50 Slp: Rule evaluation message: The computer does not require a restart.
2014-09-19 12:31:50 Slp: Send result to channel : RulesEngineNotificationChannel
2014-09-19 12:31:50 Slp: Initializing rule : Windows Management Instrumentation (WMI) service
2014-09-19 12:31:50 Slp: Rule applied features : ALL
2014-09-19 12:31:50 Slp: Rule is will be executed : True
2014-09-19 12:31:50 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.WmiServiceInfo
2014-09-19 12:31:50 Slp: Rule 'WmiServiceStateCheck' detection result: WMI Service is running
2014-09-19 12:31:50 Slp: Evaluating rule : WmiServiceStateCheck
2014-09-19 12:31:50 Slp: Rule running on machine: J1018165WIN7LT
2014-09-19 12:31:50 Slp: Rule evaluation done : Succeeded
2014-09-19 12:31:50 Slp: Rule evaluation message: The Windows Management Instrumentation (WMI) service is running.
2014-09-19 12:31:50 Slp: Send result to channel : RulesEngineNotificationChannel
2014-09-19 12:31:50 Slp: Initializing rule : Consistency validation for SQL Server registry keys
2014-09-19 12:31:50 Slp: Rule applied features : ALL
2014-09-19 12:31:50 Slp: Rule is will be executed : True
2014-09-19 12:31:50 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.AclPermissionsFacet
2014-09-19 12:31:50 Slp: Launching external tool: D:\Setup\SQL2008_R2\Standard Edition\x64\FixSqlRegistryKey_x64.exe
2014-09-19 12:31:50 Slp: ------------------------------------------------------------
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\Client - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\Client\SuperSocketNetLib - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\Client\SuperSocketNetLib\LastConnect - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100 - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\10.50 - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\Bootstrap - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\Bootstrap\Setup - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\Bootstrap R2 - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\Bootstrap R2\1033 - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\Bootstrap R2\1033\CurrentVersion - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\Bootstrap R2\CurrentVersion - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\Bootstrap R2\MSIRefCount - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\ConfigurationState - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\Tools - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\Tools\ClientSetup - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\Tools\Shortcut - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\Tools\Shortcut\SQL Server Installation Center R2 - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MSRS10_50.MSSQLSERVER - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Setup - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MSRS10_50.MSSQLSERVER1 - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MSRS10_50.MSSQLSERVER1\Setup - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\RefCount - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\RefCount\SqlRsFx0150 - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\RefCount\SqlSupport10R2 - OK.
2014-09-19 12:31:50 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\RefCount\sql_ssms - OK.
2014-09-19 12:31:50 Slp: ------------------------------------------------------------
2014-09-19 12:31:50 Slp: D:\Setup\SQL2008_R2\Standard Edition\x64\FixSqlRegistryKey_x64.exe exit code: 0
2014-09-19 12:31:50 Slp: Launching external tool: D:\Setup\SQL2008_R2\Standard Edition\x64\FixSqlRegistryKey_x86.exe
2014-09-19 12:31:50 Slp: ------------------------------------------------------------
2014-09-19 12:31:51 Slp: ------------------------------------------------------------
2014-09-19 12:31:51 Slp: D:\Setup\SQL2008_R2\Standard Edition\x64\FixSqlRegistryKey_x86.exe exit code: 0
2014-09-19 12:31:51 Slp: Rule 'AclPermissionsFacet' detection result: AreSqlAclPermissionsCanonical= True
2014-09-19 12:31:51 Slp: Evaluating rule : AclPermissionsFacet
2014-09-19 12:31:51 Slp: Rule running on machine: J1018165WIN7LT
2014-09-19 12:31:51 Slp: Rule evaluation done : Succeeded
2014-09-19 12:31:51 Slp: Rule evaluation message: SQL Server registry keys are consistent and can support SQL Server installation or upgrade.
2014-09-19 12:31:51 Slp: Send result to channel : RulesEngineNotificationChannel
2014-09-19 12:31:51 Slp: Initializing rule : Long path names to files on SQL Server installation media
2014-09-19 12:31:51 Slp: Rule applied features : ALL
2014-09-19 12:31:51 Slp: Rule is will be executed : True
2014-09-19 12:31:51 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.MediaPathLenghtFacet
2014-09-19 12:31:51 Slp: Rule 'MediaPathLength' INSTALLMEDIAPATH length is 47
2014-09-19 12:31:51 Slp: Evaluating rule : MediaPathLength
2014-09-19 12:31:51 Slp: Rule running on machine: J1018165WIN7LT
2014-09-19 12:31:51 Slp: Rule evaluation done : Succeeded
2014-09-19 12:31:51 Slp: Rule evaluation message: The SQL Server installation media is not too long.
2014-09-19 12:31:51 Slp: Send result to channel : RulesEngineNotificationChannel
2014-09-19 12:31:51 Slp: Initializing rule : SQL Server Setup Product Incompatibility
2014-09-19 12:31:51 Slp: Rule applied features : ALL
2014-09-19 12:31:51 Slp: Rule is will be executed : True
2014-09-19 12:31:51 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.SetupCompatibilityCheck
2014-09-19 12:31:51 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-09-19 12:31:51 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\100\Bootstrap\Incompatibilities
2014-09-19 12:31:51 Slp: Searching for reg path SOFTWARE\Microsoft\Microsoft SQL Server\100\Bootstrap\Incompatibilities. Open subkey result is False
2014-09-19 12:31:51 Slp: Regkey not present. No incompatibilities
2014-09-19 12:31:51 Slp: Incompatibility detected = False
2014-09-19 12:31:51 Slp: Evaluating rule : SetupCompatibilityCheck
2014-09-19 12:31:51 Slp: Rule running on machine: J1018165WIN7LT
2014-09-19 12:31:51 Slp: Rule evaluation done : Succeeded
2014-09-19 12:31:51 Slp: Rule evaluation message: Setup has not detected any incompatibilities.
2014-09-19 12:31:51 Slp: Send result to channel : RulesEngineNotificationChannel
2014-09-19 12:31:51 Slp: Saving results to datastore...
2014-09-19 12:31:51 Slp: Saved to directory.......C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140919_123143\SystemConfigurationCheck_Report.htm
2014-09-19 12:31:51 Slp: Sco: Attempting to create directory C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140919_123143\resources
2014-09-19 12:31:51 Slp: Sco: Attempting to create directory C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140919_123143\resources, security descriptor
2014-09-19 12:31:51 Slp: Sco: Attempting to set directory full path
2014-09-19 12:31:51 Slp: Sco: Attempting to normalize directory path C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140919_123143\resources
2014-09-19 12:31:51 Slp: Sco: Directory 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140919_123143\resources' already exists, skipping creation, moving to set security descriptor.
2014-09-19 12:31:51 Slp: Sco: Attempting to set security descriptor for directory C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140919_123143\resources, security descriptor
2014-09-19 12:31:51 Slp: Sco: Attempting to check if directory C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140919_123143\resources exists
2014-09-19 12:31:51 Slp: Sco: SDDL is NULL/empty and overwriteSecurityDescriptor is false, so nothing to do, return.
2014-09-19 12:31:51 Slp: Generating HTML report by applying XsltTransformation and saving to Log folder...
2014-09-19 12:31:51 Slp: Rules evaluation report is available now at C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140919_123143\SystemConfigurationCheck_Report.htm
2014-09-19 12:31:54 Slp: Completed Action: GatherUserSettings, returned True
2014-09-19 12:31:54 Slp: ----------------------------------------------------------------------
2014-09-19 12:31:54 Slp: Running Action: Progress
2014-09-19 12:31:54 Slp: Completed Action: Progress, returned True
2014-09-19 12:31:54 Slp: ----------------------------------------------------------------------
2014-09-19 12:31:54 Slp: Running Action: Close
2014-09-19 12:31:54 Slp: Stop Action
2014-09-19 12:31:54 Slp: Completed Action: Close, returned True
2014-09-19 12:31:55 Slp:
2014-09-19 12:31:55 Slp:
2014-09-19 12:31:55 Slp: ----------------------------------------------------------------------
2014-09-19 12:31:55 Slp:
2014-09-19 12:31:55 Slp: Setup result: 0

Hi,
Iam try to install Microsoft SQL Server 2008 R2 on Windows 7.
Following is the contents from summary file.
Overall summary:
Final result: Passed
Exit code (Decimal): 0
Exit message: Passed
Start time: 2014-09-19 12:31:55
End time: 2014-09-19 12:32:16
Requested action: ComponentUpdate
Machine Properties:
Machine name: J1018165WIN7LT
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: D:\Setup\SQL2008_R2\Standard Edition\x64\setup\
Installation edition: STANDARD
User Input Settings:
ACTION: ComponentUpdate
CONFIGURATIONFILE:
ENU: True
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
PASSPHRASE: *****
PID: *****
QUIET: False
QUIETSIMPLE: False
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140919_123143\ConfigurationFile.ini
Detailed results:
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140919_123143\SystemConfigurationCheck_Report.htm

Can we use SQL Server 2012 Web Edition as a witness server in mirroring?

Hi All,
Can we use SQL Server 2012 Web Edition as a witness server in mirroring?
Grateful to your time and support. Regards, Shiva

Hi All,
Can we use SQL Server 2012 Web Edition as a witness server in mirroring?
Grateful to your time and support. Regards, Shiva
As Per BOL
We strongly recommend that the witness reside on a separate computer from the partners. Database mirroring partners are supported only by SQL Server 2005 Standard and later versions and by SQL Server 2005 Enterprise Edition and later versions.
Witnesses, in contrast, are also supported by SQL Server 2005 Workgroup and later versions and by SQL Server 2005 Express Edition and later versions. Except during an upgrade from an earlier version of SQL Server, the server instances in a
mirroring session must all be running the same version of SQL Server. For example, a SQL Server 2005 witness is supported when you are upgrading from a SQL Server 2005 mirroring configuration but cannot be added to an existing or new SQL Server 2008 or later
mirroring configuration.
A witness can run on any reliable computer system that supports any of these editions of SQL Server. However, we recommend that every server instance that is used as a witness correspond to the minimum configuration that is required for the SQL Server Standard
version that you are running. For more information about these requirements
http://technet.microsoft.com/en-us/library/ms175191.aspx#SwHwRecommendations
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

RDL Reports are not working after installing SQL Server 2012 Service Pack 2 in the SharePoint integration Mode

I am using Reporting Service Integration mode with SharePoint. SSRS is installed on separated machine of SharePoint stacks in Integration Mode. Everything was working properly and I could create/edit/modify RDL reports(parameters, Datasource, Subscription)
inside SharePoint and Document Libraries.
But after installing SQL Server 2012 Service Pack 2, on opening RDL reports inside SharePoint I receive this error message.
The permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation
I should mention that SSRS is installed in the SharePoint integration Mode and there is no SSRS management console.

Hi Hedayat-Abedijoo,
According to your description, you are using Reporting Services in SharePoint Integrated mode, and everything worked fine before you install SQL Server 2012 Service Pack 2. After the package is installed, when you open RDL reports, the error occurred: The
permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation.
According to my search, there may be two reasons for the problem:
This is caused when the application pool account that runs the SharePoint Web application you are on in IIS and the application pool account that SharePoint believes is running the site differ. This happens if the application pool account is changed directly
in IIS instead of through SharePoint (using the approved method).
This error can be caused when Kerberos authentication has been set up correctly and delegation in a double hop scenario will succeed, but Reporting Services integration has been set up for Trusted Account rather than Windows Authentication. This causes
SharePoint to continue to impersonate the logged-on user when contacting Reporting Services; when Reporting Services compares the application pool account to the user account making the request, they are not equal.
In this case, we can solve the problem by changing the application pool account in IIS back to the previous account and set AuthenticationTypes to RSWindowsNTLM only. For detail information, please refer to 8.3 “The permissions granted to user 'Domain\User'
are insufficient for performing this operation” in the document:http://msdn.microsoft.com/en-us/library/ee384252(SQL.100).aspx
If you have any questions, please feel free to let me know.
Thanks,
Wendy Fu

EHP2 - EHP7 Upgrade Path using SQL Server 2012/Win Server 2012 R2

Hi Guys.
I have question regarging Upgrade Roadmap for a ERP 6 EHP2 system based on NW 7.01 which I would like to Upgrade to ERP6 EHP7 SP7
Source System is
Windows 2012
SQL Server 2008 R2
EHP2 for ERP 6.0 SPS Level 14
Target System
Windows 2012
SQL Server 2012
EHP7 for ERP 6.0 SP 7 based on NW 7.4 SP 9
During Upgrade checks it says I must Upgrade Database first before continue since DB Release is too low for NW 7.4 SP9 as stated in Note
1951491 - Minimal DB system platform requirements for SAP NetWeaver 7.4 SP08
So, at this point I agree i have to update SQL Server to 2012 before next step
Now, my concern is that my Source System does not have the minimum NW SP level (14) to run under SQL Server 2012 which is 26.
Im currently running SAP Kernel 721 EXT Level 401 which is above mininum
According to Note 1651862 - Release planning for Microsoft SQL Server 2012 that would not be possible
Existing systems of SAP products that are out of SAP maintenance can be upgraded to SQL Server 2012 in order to prepare a SAP upgrade, if they match the SAP NetWeaver Support Package requirements defined below.
SAP products prior to SAP NetWeaver 7.0 are not supported at all on SQL Server 2012.
Required minimum SAP Netweaver Support Package Stacks (SPSs) for SQL Server 2012 (SAP ABAP, SAP ABAP+JAVA stacks)
SAP NETWEAVER 7.0 - SPS 26 (SAP BASIS 26, SAP BW 28)
SAP EHP1 FOR SAP NETWEAVER 7.0 - SPS 11 (SAP BASIS 11, SAP BW 11)
SAP EHP2 FOR SAP NETWEAVER 7.0 - SPS 11 (SAP BASIS 11, SAP BW 11)
SAP EHP3 FOR SAP NETWEAVER 7.0 - SPS 03 (SAP BASIS 03, SAP BW 03)
SAP NETWEAVER 7.1 - SPS 14 (SAP BASIS SP14)
SAP EHP1 FOR SAP NETWEAVER 7.1 EhP1 - SPS 10(SAP BASIS SP10, SAP BW SP10)
SAP NetWeaver 7.2 - no restriction
SAP NETWEAVER 7.3 - SPS 07 (SAP BASIS 07, SAP BW 07)
SAP EHP1 FOR SAP NETWEAVER 7.3 - SPS 03 (SAP BASIS 03, SAP BW 03)
If your system is running on a SPS lower than the one required above, you have to apply the minimum required SPS before upgrading/migrating to SQL Server 2012.
If you install a NetWeaver product on SQL Server 2012, the required SPS for your product must be applied immediately after the installation - see SAP note 1676665, section I for more information.
But performing the Upgrade would be technically possible? I mean not for productive use but technicaly during that time the Database is Upgrade and during SUM Execution.
According to the note it states if you install a Netweaver Product in SQL Server 2012, SPS must be applied immediately, so is kinda ambigous what SAP is saying.
Best
Martin

Hi Martin,
For a test scenario, there's no harm in trying it (other than spending a lot of time on it, but hopefully that will prove not to be a waste). Generally, I expect you'll be fine upgrading your DBMS even though you aren't on the required minimum SP yet. The main thing you'll be missing out on is the updates to DBACOCKPIT, but once you do your EhP upgrade (with sps update included), you'll be putting that in place.
So, you could try this on your sandbox system and see if there are any problems. I assume the intent is to start the EhP upgrade as soon as the DBMS upgrade is done, right? In other words, you won't be actually using the system without the required SP except to run the EhP upgrade?
Alternatively, you could do a minimal support pack update, perhaps just a Basis SP only, to the minimum SP needed for your current release, then do the DBMS upgrade, then proceed with the EhP upgrade. This would be the safest procedure, but, as I said, I expect you can probably get away without going to this level without much problem. Again, the idea would be minimizing the time between the start and end of the total project on each system (DEV, QAS, PRD, etc).
Regards,
Matt

Optional feature not implemented while using SQL server

Hi to all
I am using SQL server.
I have written a stored procedure in SQL server and it is taking the datetime data type as one parameter.
I have written the following java code to call that procedure.
Calendar calendar= Calendar.getInstance();
cs.setDate(4,new java.sql.Date(calendar.getTime().getTime()));
cs.execute();
waiting for reply.
datetime is the 4th parameter.

the question has been resolve.the datasource with excel is not schema!

Sharepoint 2007 using sql server 2012 database server

We still have an old SharePoint 2007 farm that runs on SQL Server 2008 and Reporting Services 2008. I would like to migrate this app over to SQL Server 2012. From what I gather SharePoint 2007 supports SQL 2012 if you are running WSS service pack 3 and
SharePoint server service pack 3 I am already on SP3. So my question is who all here is running SharePoint 2007 on SQL 2012 and have you had any problems?

Yes I have an environment that is SPS 2007 wSP3 and SQL Server 2012, and have been doing this for 2 months. So far, no problems. There have been issies with User Profile services, but those turned out to be unrelated.
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

SCOM 2012 R2 installtion wizard not able to contact SQL server cluster

Hi,
This is about the error faced while installing SCOM 2012 R2.
My customer has SQL 2012 SP1 cluster installed. I am trying to install the SCOM 2012 R2 with this installed SQL cluster. The SQL cluster is installed with default instance and with AAG (Always on Availability Group).
The edition of SQL server is, SQL Server Enterprise edition with SP1
After check services on both the SQL nodes found that SQL Full text is not installed (as the related SQL Full text service not present in the services.msc) on any of the SQL cluster node & SQL Browser service is not running.
The running services for SQL are, SQL Server (MSSQLSERVER) & SQL Server Agent (MSSQLSERVER).
When I started to install the SCOM 2012 R2, Within a SCOM 2012 wizard, On the Configure the Operational Database screen, entered only the name of SQL cluster & no instance as it is with default instance MSSQLSERVER.
I faced error as, This SQL Server could not be found.
After installed SQL full text, the service is showing in services.msc as "SQL Full-text Filter Daemon Launcher (MSSQLSERVER)".
Now when I started to install the SCOM 2012 R2, Within a SCOM 2012 wizard, On the Configure the Operational Database screen, entered only the name of SQL cluster & no instance as it is with default instance MSSQLSERVER.
I faced error as, The installed version of SQL Server could not be verified or is not supported.
Followings test carried out for the connectivity between SCOM 2012 MS &SQL Cluster
Ping SQL Cluster successfully
Telnet SQL Cluster for port 1433 successfully
Tracert SQL Cluster – completed successfully with single hops.
The windows firewall is off on both sides
The SQL services running on the Active node 1 of the cluster are as follows:
SQL Full Text Filter Daemon Launcher (MSSQLSERVER) -- Running & Manual
SQL Server (MSSQLSERVER) -- Running & Automatic
SQL Server Agent (MSSQLSERVER) -- Running & Automatic
SQL serve Browser - Stopped & Manual
SQL Server VSS Writer -- Running & Automatic
The SQL services running on the Passive node 2 of the cluster are as follows:
SQL Full Text Filter Daemon Launcher (MSSQLSERVER) -- Running & Manual
SQL Server (MSSQLSERVER) -- Running & Automatic
SQL Server Agent (MSSQLSERVER) -- Stopped & Automatic
SQL serve Browser - Stopped & Manual
SQL Server VSS Writer -- Running & Automatic
The SQL Server Agent (MSSQLSERVER) service is not running on the second node. It is running only on first node which is active.
The account used to install SCOM has the local admin privilege on the SQL server
To ping the cluster use the cluster name & it solved the whole FQDN of cluster in ping result. When ping with IP address with -a it not resolve to name.
Is any one can provide their valuable inputs.
Regards,
SandeepK

Hi SandeepK,
Before Installing Operations Manager on an availability group, please
1. Make sure to use the Group listener Name and port when installing Operations Manager for the databases that are going to be added to the availability databases.
2. The first management server will use the Group listener to get the primary SQL instance, and will install the databases on that instance.
System Requirements: System Center 2012 R2 Operations Manager
http://technet.microsoft.com/en-us/library/dn249696.aspx#BKMK_ClusterConfig
Niki Han
TechNet Community Support

I am not able to install sql server 2008 r2 sp2

hi,
I have installed sql server 2008 r2 rtm and want to update to sp2 and have installed sp2 from microsoft website and then i installed CU1 for sp2. All installation did successfully but still it is not showing the updated version info.I am checking the
version info from Help>About. Please tell me what to do next?
Thanks and regards.

Hello,
Please run the discovery report. Maybe you have more than one instance of SQL Server installed on that computer and you updated just one of them. Make sure you click to select all the instances shown on the “Select Features” page of SQL Server setup.
http://learnsqlwithbru.com/2012/01/04/installing-sql-server-2008-service-pack-3-on-multiple-instances/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Using SQL Server 2012 FileTables

I like to know how to use SQL 2012 SP1 File Tables with SharePoint 2013 SP1

File tables are not supported with SharePoint content databases. SharePoint specifically just uses FILESTREAM for RBS.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SQL Server 2012 - Cannot Use Network Drive as a Backup Device

Hello Community,
I am using SQL Server 2012 and I am trying to add a mapped drive as a backup device, but I am not even to see that drive from SQL Server. Has anyone else had this issue and if so can you help me resolve it?
Thanks!
Tom
Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award -
Linked-In - SharePoint Gypsy

Hey David,
I checked the drive and share permissions, and the service account for SQL Server, in this case named "sqlsvc" has been granted full permission to both. I tried the script but it also failed, the code is below:
DATABASE[TestDb]TO
DISK=N'\\sqlclus02\SharePointBackup\TestDb.bak'WITHNOFORMAT,NOINIT,
NAME=N'TestDb-Full
Database Backup',SKIP,NOREWIND,NOUNLOAD,
STATS=10
Also, I haven't been able to confirm that the sqlsvc account is a domain account, but I do know the server is clustered.
Thanks!
Tom
Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award -
Linked-In - SharePoint Gypsy

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Unable to install sql server 2012

I am trying to install sql server 2012. I need it to run a trial version of Xactimate. I get the following error during the installation process on the SQL Server Installation Center box : The feature you are trying to use is on a network resource that
is unavailable. Click ok to try again, or enter an alternate path to a folder containing the installation package 'sqlbrowser.msi' in the box below.
Use source: c:\9bc690235b2703df7a6704fa\1033_ENU_LP\x86\setup\

Hello,
Based on the following Xactware support document from two years ago (2012), Xactimate supports SQL Server 2005 and SQL Server 2008.
The document does not say Xactimate supports SQL Server 2012.
http://www.xactware.com/pdf/27/xactimate-27.5-network-install-guide.pdf
As mentioned on page #3 of the installation guide (above link), “If you do not already have SQL Server Express installed on your server,
you can use the version of SQL Server Express that is available on your Xactimate Version 27 DVD. Xactware recommends you use the Xactimate Setup—Network batch file. When you use this batch file, the Xactware instance is automatically created, the network
protocols are enabled, and the correct user name and password is set.”
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Not able to use Sql Server 2012 Intellisenese

Similar Messages

Maybe you are looking for