Cluster SQL 2012 on Windows 2008 R2

Hi
Presently, i have a cluster SQL 2012 on windows 2008 R2 (2 nodes), i need to add a new server in cluster.
My question, it's possible to add WINDOWS 2012 SERVER with SQL 2012?
(2 nodes with Windows 2008 R2, 1 node with Windows 2012 and all nodes with SQL 2012)
If yes, do you have a link that
confirms this?
Thanks

No. This is not possible. Microsoft Windows Cluster required all the Member Nodes to have same OS to the Same version level. Even you cannot use Windows Server 2008 on one node with Windows Server 2008 R2 on another node.
Thanks and Regards Alankar Chakravorty MCITP Database Administrator SQL Server 2008 MCITP Database Administrator SQL Server 2005

Similar Messages

  • Trouble installing/using SQL Developer on Windows 2008 R2

    I need help installing sql developer.
    I am running Windows 2008 R2.
    I tried installing the 64 bit version, and when it asked for the path to the JDK, it complains that it doesn't exists. Can someone PLEASE point me to which JDK I need to install?
    I tried installing the 32 bit versionand it installs fine, but then gives me the error that it can't load AMD 64-bit dll on a IA 32 bit platform.
    PLEASE HELP. How can I run SQL Developer on Windows 2008 R2?
    Links to the exact versions of what to install would be very very helpful.
    Thank you!

    The versions required are in the release notes.
    If you install the 64-bit SQLDeveloper you need a 64-bit JDK.
    If you install the 32-bit SQLDeveloper you need a 32-bit JDK.
    If your operating is 32-bit, you need a 32-bit SQLDeveloper.
    Note that you need a JDK not a JRE
    Edited by: Jim Smith on Apr 4, 2011 9:04 PM to fix 32/64 bit errors.

  • SCEP 2012 Client in Windows 8 / 2012 - in Windows 2008 Domain- Not Syncing -/ Not Compatiable

    Dear All ,
    With lots of Hardship I had installed SCEp 2012 in Windows 2012 Virtual machine in WIndows 2008 Domain.
    SCCM 2012 Server in Windows 2008 Server with Sql 2008 was - performing well and there was no issues until our COmpany planned to Convert the Windows 2008 Server to  Windows 2012 Server ( AD is 2008)
    WSUS is not Fully synching with SCCM 2012 ( previously it was )
    Software Updates not pushing properly and to top all the SCEP client is not compatible with win 8.1 pro or win 2012 server
    Error: Failed to download content id 16787046. Error: Access is denied.
    Package:
      Success: The software updates were placed in the existing package:
    •     Deployment Package(JUN2014)
    Software updates that will be downloaded from the internet
      Error: Update for Forefront Endpoint Protection 2010 Client - 4.1.522.0 (KB2780435)
    Errors
        Failed to download content id 16787046. Error: Access is denied.
    Language Selection:
     English
    But the service account has full access - administrative rights and the administrator of the system
    please advise on this

    Hi,
    All the software updates downloaded failed?
    Are there any errors in PatchDownloader.log? If you use Automatic deployment rule, please also check ruleengine.log.
    Please add the account with Full rights to the source share (both NTFS and Share permissions) where the Deployment Package is located.
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Unable to connect to SQL 2012 on Windows VM from gallery

    I had deployed new virtual machine from the gallery, windows 2012 with sql 2012 but fail to login with default authentication
    I had followed the directions as in: "Provisioning a SQL Server Virtual Machine on Windows Azure"  (http://www.windowsazure.com/en-us/documentation/articles/virtual-machines-provision-sql-server/)
     but fail to login to SQL with the following error:
    ===================================
    Cannot connect to R10PROJDEPLOY.
    ===================================
    Login failed for user 'R10PROJDEPLOY\R10Admin'. (.Net SqlClient Data Provider)
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
    Server Name: R10PROJDEPLOY
    Error Number: 18456
    Severity: 14
    State: 1
    Line Number: 65536
    in the past I had used same procedure to work with windows Server 2008 & SQL 2008 and managed to login well, any hint could be wrong?

    Hi,
    To connect to the Database Engine from another computer, configure SQL Server for mixed mode authentication.
    Add the port number after the server name.
    Also try connecting with the IP address.
    If no progress, please check the error message in ‘\Program Files\Microsoft SQL Server\MSSQL11.<instance name> \MSSQL\Log\ERRORLOG’
    Hope it helps.
    Tracy Cai
    TechNet Community Support

  • SQL 2012 Install on 2008 OS or 2012 OS

    What advantage is there to installing SQL 2012 onto OS 2012 vs OS 2008 R2. Are there benefits to installing SQL 2012 to OS 2012. Better memory managment etc...

    What advantage is there to installing SQL 2012 onto OS 2012 vs OS 2008 R2. Are there benefits to installing SQL 2012 to OS 2012. Better memory managment etc...
    Memory management of SQL server is not directly related to OS.If you are installing SQL Server 2012 on any OS (2008 Re or 2012) you will get benefit of memory changes in SQL Server 2012.
    Below link has comparisoon between R2 and 2012
    https://blogs.technet.com/b/ieitpro/archive/2013/01/29/hyper-v-comparison-windows-server-2008-r2-vs-windows-server-2012.aspx
    I would suggest to go for Windows 2012 .
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • SQL 2000 LINKED SERVER ERROR 7303 WITH SQL 2012 ON WINDOWS SERVER 2012 R2

    Hi all,
    I have a problem with SQL Server 2012 and a linked server for SQL 2000 database.
    System specification:
    Windows server 2012 64 bit
    SQL SERVER 2012 64 bit
    REMOTE SERVER SQL 2000 32 bit
    I've installed sql native client 32bit,create a SYSTEM DSN odbc connection with "SQL Server" driver named "MYSERVER".
    Create a linked server with the query below in SQL 2012:
    EXEC master.dbo.sp_addlinkedserver @server =N'MYSERVER', @srvproduct=N'MYSERVER', @provider=N'MSDASQL', @datasrc =N'MYSERVER', @location=N'System';
    EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'MySERVER',@useself=N'True',@locallogin=NULL,@rmtuser=NULL,@rmtpassword=NULL
    GO
    but when i browse the linked server i receved error 7303.

    You need 64-bit MSDASQL. It is the bitness of the server you are connecting from that matters. 64-bit executables cannot hook into 32-bit DLL.
    However, I suspect that you will not get things to work anyway. At least I have not seen anyone this far who has been able to set up a linked server from SQL 2012 to SQL 2000. I know that when I tried this, the following providers had this result:
    SQLNCLI11 - does not support connections to SQL 2000.
    SQLNCLI10 - failed with some obscure message that I don't recall.
    SQLNCLI - Don't recall that the problem was here.
    SQLOLEDB - SQLOLEDB is always replaced with the most recent version of SQLNCLI, so this fails because of lack of support.
    I don't think I got through all version of the ODBC drivers, though.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Oracle RAC Cluster Health Monitor on Windows 2008 R2 64Bit

    Hello colleaques,
    i run a 2-node RAC Cluster 11.2.0.2 64Bit on Windows 2008 R2 64bit. I did installl the Berkeley DB Version 4.6.21 succesfully.
    After that i installed the crfpack.zip (CHM) as described in the README.txt.
    F:\Software\ClusterHealthcheck\install>perl crfinst.pl -i eirac201,eirac202 -b F:\BerkeleyDB -m eirac201
    Performing checks on nodes: "eirac201 eirac202" ...
    Assigning eirac202 as replica
    Installing on nodes "eirac202 eirac201" ...
    Generating cluster wide configuration file for eirac202...
    Generating cluster wide configuration file for eirac201...
    Configuration complete on nodes "eirac202 eirac201" ...
    Please run "perl C:\"program files"\oracrf\install\crfinst.pl -f, optionally specifying BDB location with -b <bdb location> as Admin
    user on each node to complete the install process.
    F:\Software\ClusterHealthcheck\install>c:
    C:\Users\etmtst>cd \
    C:\>cd "Program Files"
    C:\Program Files>cd oracrf
    C:\Program Files\oracrf>cd install (on both nodes as described in the README.txt)
    C:\Program Files\oracrf\install>perl crfinst.pl -f -b F:\BerkeleyDB
    01/30/12 16:42:21 OracleOsToolSysmService service installed
    Installation completed successfully at C:\"program files"\oracrf...
    C:\Program Files\oracrf\install>runcrf
    01/30/12 16:44:03 StartService(OracleOsToolSysmService) failed:(1053) The service did not respond to the start or control request i
    n a timely fashion.
    01/30/12 16:44:03 OracleOsToolSysmService service started
    It says here OracleOsToolSysmService was started, but it was not !!!
    Manual starting gives the same error. !!!!
    Please has anybody had the same problem ??
    regards and greetings, Abraham

    There will be a new version of the Standalone CHM/OS for Windows that will work with 11.2.0.2 and earlier versions available on OTN in the near future. The older version that you are using has not been tested and due to the infrastructure changes in 11.2 it is not expected it will work. The integrated CHM/OS that is included as part of the 11.2.0.3 GI installation does work as does the new GUI (CHMOSG) now available for download.

  • How to convert sql 2012 database to 2008

    i have 2012 sql database file (.mdf ans .ldf ) how to connect same database in 2008 sql server . please help me its very urgent 

    i have 2012 sql database file (.mdf ans .ldf ) how to connect same database in 2008 sql server . please help me its very urgent 
    Hi,
    You cannot attach or restore(if you have a backup) msf and ldf file of SQL Server 2012 to SQL server 2008 its not allowed it will flash error. If its urgent you need to manually script out table definition with constraints and then create same table in SS
    2012 and then transfer data using import/export wizard
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Articles

  • Error while trying to upgrade SQL 2008 (SP2) to SQL 2012: There was a failure to calculate the applicability of setting LICENSEPATH.

    Hi,
    I am trying to upgrade one of our SQL Server Enterprise (2008 (SP2)) to 2012. I am using the upgrade option but it gives me the following error:
    Error Code 0x85640002: There was a failure to calculate the applicability of setting LICENSEPATH
    We have downloaded the image from our Volume Licensing account. Also, the same image was used to install SQL 2012 on Windows Server 2012 R2 servers without any issues.
    Below is the install summary.txt. I have tried everywhere but no go. Would really appreciate any assistance.
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2057043966
      Exit facility code:            1380
      Exit error code:               2
      Exit message:                  There was a failure to calculate the applicability of setting LICENSEPATH.
      Start time:                    2014-02-28 10:58:49
      End time:                      2014-02-28 10:58:58
      Requested action:              RunRules
      Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0x0BA02FC6%400x294A9FD9&EvtType=0x0BA02FC6%400x294A9FD9
    Machine Properties:
      Machine name:                  xxxxxxx
      Machine processor count:       2
      OS version:                    Windows Server 2008 R2
      OS service pack:               Service Pack 1
      OS region:                     U.A.E.
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Package properties:
      Description:                   Microsoft SQL Server 2012
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      SPLevel:                       0
      Installation location:         D:\x64\setup\
      Installation edition:          
    User Input Settings:
      ACTION:                        RunRules
      CONFIGURATIONFILE:             
      ENU:                           true
      FEATURES:                      
      HELP:                          false
      INDICATEPROGRESS:              false
      INSTANCENAME:                  <empty>
      PID:                           *****
      QUIET:                         true
      QUIETSIMPLE:                   false
      RULES:                         GlobalRules
      UIMODE:                        Normal
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140228_105848\ConfigurationFile.ini
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file:               The rule result report file is not available.
    Exception summary:
    The following is an exception stack listing the exceptions in outermost to innermost order
    Inner exceptions are being indented
    Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingApplicabilityException
        Message:
            There was a failure to calculate the applicability of setting LICENSEPATH.
        HResult : 0x85640002
            FacilityCode : 1380 (564)
            ErrorCode : 2 (0002)
        Data:
          SettingId = LICENSEPATH
          WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingApplicabilityException@2
          DisableWatson = true
        Stack:
            at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateApplicability()
            at Microsoft.SqlServer.Configuration.BootstrapExtension.ValidateChainerSettingAction.ExecuteAction(String actionId)
            at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
        Inner exception type: Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingValueException
            Message:
                    There was a failure to calculate the default value of setting LICENSEPATH.
            HResult : 0x85640001
                    FacilityCode : 1380 (564)
                    ErrorCode : 1 (0001)
            Data:
              SettingId = LICENSEPATH
              WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingValueException@1
            Stack:
                    at Microsoft.SqlServer.Chainer.Infrastructure.Setting`1.CalculateValue()
                    at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallQueuedSubscriberDelegates()
                    at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.Publish(Publisher publisher)
                    at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateApplicability()
            Inner exception type: System.ArgumentException
                Message:
                            Culture ID 3072 (0x0C00) is not a supported culture.
                            Parameter name: culture
                Stack:
                            at System.Globalization.CultureInfo..ctor(Int32 culture, Boolean useUserOverride)
                            at System.Globalization.CultureTable.GetCultures(CultureTypes types)
                            at Microsoft.SqlServer.Configuration.SetupExtension.LcidUtilities.GetLangPackParentFolderForLcid(String lcid)
                            at Microsoft.SqlServer.Configuration.SetupExtension.LcidUtilities.GetLcidFolder(ServiceContainer context, String baseFolderFullPath)
                            at Microsoft.SqlServer.Configuration.SetupExtension.LicensePathSetting.DefaultValue()
                            at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallFunctionWhileAutosubscribing[T](SubscriberDelegate
    subscriberDelegate, Int32 priority, AutosubscribingFunctionDelegate`1 function)
                            at Microsoft.SqlServer.Chainer.Infrastructure.Setting`1.CalculateValue()
    Regards,
    Mohammed

    Culture ID 3072 (0x0C00) is not a supported culture.
                            Parameter name: culture
    This appears to be the root problem. It seems that the regional settings on this machine is messed up. 0x0C00 is an unusual LCID, they do not normally not end in two zeroes.
    is there a custom culture installed on this machine?
    Review the regional settings and also check the System locale. If it looks spooky, set it to Arabic - U.A.E. if this is where you are located.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Data Protection Manager 2012 on Hyper-V Windows 2008 R2 and NAS connectivity

    Hi, we currently use Symantec Backup Exec 2010/2012 on Windows 2008 R2 servers storing the data on two LAN-connected NAS servers. As part of our MS licensing package, we have obtained System Center 2012. I'm seeing if DPM can replace our BE software, but
    I'm running into a major hurdle, I can't connect (Add) either of the NAS machines. I see on DPM posts where you need to have a physical connection to the NAS (iSCSi or fiber channel) not an option on the NAS (Thecus N8800 & N8900 (no ability to add cards)
    and SMB 3.0 (appears to be a Windows 2012-only option ... I dread 2012 and don't want to move to it right now). Can my virtualized (hyper-v) W2008 R2 server see a non-connected NAS and if so, how do I pull this off.
    Thanks

    Hi 
    DPM needs local storage to connect to. you cannot use a NAS or USB device to backup to like with other backup software.

  • Multiple dev environments of CRM 2011 on one SQL 2012 server

    Hello,
    I have requirement to install multiple development servers of CRM 2011 which would use one SQL 2012 Server. 
    As you know, you need separate CRM 2011 Reporting Extensions, which means that Reporting Services (SSRS) should be installed not in SQL 2012 server but in the same server as CRM 2011. For SSRS (on CRM 2011 server) I want to use SQL 2008R2 Express (licensing
    issues).
    Is it possible to use SQL 2008R2 Express only for SSRS, while CRM 2011 is using SQL 2012 on different server?
    I get errors while creating organization:
    System.Web.Services.Protocols.SoapException: The feature: "Customizing security roles" is not supported in this edition of Reporting Services.
    Environment information:
    CRM 2011 on Windows Server 2008 R2. In the same server SSRS 2008 R2 on SQL 2008 R2 Express
    CRM database in different machine with SQL 2012 on Windows Server 2012.
    Regards, 
    Jonas

    SQL Express is not supported for Dynamics CRM.  Plus, the only way to have completely separate installations of Dynamics CRM pointing to one server for SQL is to used named instances of SQL Server on the Windows server you're installing SQL. 
    So you literally would have to install SQL multiple times on that one box.
    Instead of going through all that effort, why not just install Dynamics CRM once, and then make multiple CRM deployments using the CRM Deployment Manager? You can make as many CRM environments as you need with a single install of Dynamics CRM. This works
    great in dev environments where you need multiple instances for multiple devs. Plus, it gives you exactly one point of administration when it comes to the CRM install, and is a lot more supportable.
    The postings on this site are solely my own and do not represent or constitute Hitachi Solutions' positions, views, strategies or opinions.

  • Error during unattended install of SQL 2012 (..setting 'CLTRESULTDIR' does not exist.)

    Hi ALl,
    I'm trying an automated install of SQL 2012 on WIndows 2012, but I keep running into this error (using a configuration.ini file generated by running through setup and grabbing it just before I clicked 'OK')
    Contents of summary log:
    Overall summary:
       Final result:                  Failed: see details below
       Exit code (Decimal):           -2068578304
       Exit facility code:            1204
       Exit error code:               0
       Exit message:                  The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not
    exist.
       Start time:                    2015-01-09 10:19:12
       End time:                      2015-01-09 10:20:07
       Requested action:              Install
    Setup completed with required actions for features.
     Troubleshooting information for those features:
       Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Replication:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for FullText:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for DQ:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for AS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for RS_SHP:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for RS_SHPWFE:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for DQC:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for SDK:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for DREPLAY_CTLR:    SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for DREPLAY_CLT:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for BIDS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for SNAC:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for SNAC_SDK:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for BOL:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.
     Machine Properties:
       Machine name:                  IDCSQLTST11
       Machine processor count:       2
       OS version:                    Future Windows Version
       OS service pack:              
       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
       ProductName:                   SQL Server 2012
       Type:                          RTM
       Version:                       11
       SPLevel:                       0
       Installation location:         E:\SQL_Server_2012_StandardEdition\x64\setup\
       Installation edition:          Standard
    Product Update Status:
       None discovered.
    User Input Settings:
       ACTION:                        Install
       ADDCURRENTUSERASSQLADMIN:      false
       AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
       AGTSVCPASSWORD:                <empty>
       AGTSVCSTARTUPTYPE:             Automatic
       ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
       ASCOLLATION:                   Latin1_General_CI_AS
       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:              Manual
       ASSYSADMINACCOUNTS:            DOMAINAA\SQLADMINS
       ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
       BROWSERSVCSTARTUPTYPE:         Disabled
       CLTCTLRNAME:                  
       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:             E:\SQL_Server_2012_StandardEdition\ConfigurationFile.ini
       CTLRSTARTUPTYPE:               Manual
       CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
       CTLRSVCPASSWORD:               <empty>
       CTLRUSERS:                     DOMAINAA\user12345
       ENABLERANU:                    false
       ENU:                           true
       ERRORREPORTING:                false
       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
       FILESTREAMLEVEL:               0
       FILESTREAMSHARENAME:           <empty>
       FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
       FTSVCPASSWORD:                 <empty>
       HELP:                          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:                         true
       QUIETSIMPLE:                   false
       ROLE:                         
       RSINSTALLMODE:                 DefaultNativeMode
       RSSHPINSTALLMODE:              SharePointFilesOnlyMode
       RSSVCACCOUNT:                  NT Service\ReportServer
       RSSVCPASSWORD:                 <empty>
       RSSVCSTARTUPTYPE:              Manual
       SAPWD:                         <empty>
       SECURITYMODE:                  SQL
       SQLBACKUPDIR:                  <empty>
       SQLCOLLATION:                  Latin1_General_CI_AS
       SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
       SQLSVCPASSWORD:                <empty>
       SQLSVCSTARTUPTYPE:             Automatic
       SQLSYSADMINACCOUNTS:           DOMAINAA\SQLADMINS
       SQLTEMPDBDIR:                  F:\TempDB
       SQLTEMPDBLOGDIR:               <empty>
       SQLUSERDBDIR:                  E:\SQLData
       SQLUSERDBLOGDIR:               D:\SQLLog
       SQMREPORTING:                  false
       TCPENABLED:                    1
       UIMODE:                        Normal
       UpdateEnabled:                 true
       UpdateSource:                  MU
       X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\ConfigurationFile.ini
    Detailed results:
       Feature:                       Database Engine Services
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Server Replication
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Full-Text and Semantic Extractions for Search
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Data Quality Services
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Analysis Services
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Reporting Services - Native
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Reporting Services - SharePoint
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Reporting Services Add-in for SharePoint Products
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Data Quality Client
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Integration Services
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Client Tools Connectivity
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Management Tools - Complete
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Client Tools SDK
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Client Tools Backwards Compatibility
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Distributed Replay Controller
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Distributed Replay Client
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Server Data Tools
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Management Tools - Basic
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Client Connectivity
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Client Connectivity SDK
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Writer
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Documentation Components
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Browser
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\SystemConfigurationCheck_Report.htm
    Exception summary:
     The following is an exception stack listing the exceptions in outermost to innermost order
     Inner exceptions are being indented
    Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
         Message:
             The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
         HResult : 0x84b40000
             FacilityCode : 1204 (4b4)
             ErrorCode : 0 (0000)
         Data:
           SQL.Setup.FailureCategory = InputSettingValidationFailure
           DisableWatson = true
         Stack:
             at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
             at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
             at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
             at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
         Inner exception type: Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException
             Message:
                     The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
             HResult : 0x87d00006
                     FacilityCode : 2000 (7d0)
                     ErrorCode : 6 (0006)
             Data:
               DirectoryPath = C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
               SettingName = CLTRESULTDIR
               WatsonData = 
    Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException@6

    Hello,
    Open the configuration file with notepad, then go to the “features” variable. On the following article you will find what
    means each parameter:
    http://msdn.microsoft.com/en-us/library/ms144259(v=sql.110).aspx#Feature
    You will also find the list of features supported by each edition on the following article:
    http://msdn.microsoft.com/en-us/library/Cc645993(v=sql.110).aspx
    For example, it seems you have DQ and DQC on that configuration file, please remove them with their corresponding commas.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com
    Thanks Albert that worked when I just selected the main features and excluded ones like DQ and DRC. Thing is why would the standard media allow you to install enterprise features, create a configuration file with these enterprise features and then fail?? Why
    would Microsoft tease you like that? Frustrating since I spent hours on this ..

  • Failed to install ms sql 2012, it shows 1406 Could not write value to key \SOFTWARE. Verify that you have sufficient access to that key, or contact your support personnel. error

    Hi friends,
    i have tried to install ms sql 2012 on windows 8.1 pro 64 bit  but it got failed due to the following error 1406 Could not write value  to key \SOFTWARE.   Verify that you have sufficient access to that key, or contact your support personnel.. 
     I had run the set up file as administrator. I have ony one user account on my laptop. I have seen in the regestry about permission of user. There is full control to the user. I have also tried the solution related to this issue that are available in
    this forum and other.
    I have also attache the detail.txt log file here
    So i am heartily requesting you guys if you have the solution then please post your solution as soon as possible. 
    Thanks in  advance!!!

    Looks like this is a permission issue with account you logged in in your operating system or account if any you chooses to run you SQL Server installation . Or for executing setup file try using run as administrator.
    http://www.sperrysoftware.com/kb/questions/7/How+to+Troubleshoot+a+%22Error+1406%3A+Could+not+write+value...%22+or+%22Error+1406%3A+Could+not+write+InstanceIndex+to+key...%22+error+message
    http://support.microsoft.com/kb/913559
    Raju Rasagounder Sr MSSQL DBA

  • SSRS 2012 rendering issue/Enabling Anonymous access - Upgraded SSRS from SQL 2005 to SQL 2012.

    Hi,
    I just recently upgraded SQL 2005 SSRS to SQL 2012 SSRS. Everything is working great other than small issue.
    Sounds like some authentication issue. SQL 2005 SSRS - IIS, we enabled anonymous access and we never had this problem. SQL 2012 SSRS /WIN 2008 R2 -  I am not sure how to enable anonymous access.
    If anyone can help me on this? I really appreciate your help.
    Thanks,
    Vel
    Vel Thavasi

    Hi Vel,
    According your description, you want to know how the enable anonymous access to SSRS 2012. Right?
    In SSRS 2008 or later version, we are not using IIS any more. If we want to configure the authentication, we need to configure in RSReportServer.config. This file locate at:
    <drive>:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer
    However, in SSRS 2012, Anonymous authentication is not supported on report server. Please see:
    Authentication with the Report Server
    In this scenario, we need to custom an authentication type to achieve the "Anonymous" goal. Please refer to the link:
    Configure Custom or Forms Authentication on the Report Server
    If you have any question, please feel free to ask.
    Best Regards,
    Simon Hou

  • Ehp4 downtime in HA ( windows 2008)

    Hello gurus ,
                             Before the downtime phase , we got the message at node2 where the ehpi tool is running
    "You are running a so-called High-availibility setup.To enter the downtime it is necassary to stop the ASCS instance manually on the remote host. In addition also the sapstartsrv and saposcol processes on the remote host must be stopped."
    1. We have set the node1 to pause state in failover cluster management tool in windows 2008 .
    2. we have stopped the SAPSID cluster instance at node1 . ( However the Dialog Instance goes yellow after this , disp+work : running but message server unavailable)
    3. we have stopped the saposcol server at node1.
    Is that enough or do we need to perform more steps.
    Please suggest.
    Regards
    Regards

    Should i stop all the instances on node1....Any thoughts .... ?
    I stopped all application servers on node1 , including ASCS cluster SAPSID  and moved ahead with the installation. The node1 is still in pause state  at the failover cluster management tool
    Regards
    Edited by: Tech GCCIA on Oct 18, 2010 1:38 PM
    Edited by: Tech GCCIA on Oct 18, 2010 1:47 PM

Maybe you are looking for

  • Xls File format

    I use SAP 6.0 and I am having difficulty with the downloading of excel reports. Here is my issue. I run a report in SAP and save it locally as a xls file.  This seems fine but the reality is the file is not a true xls file When I go to open it using

  • Illustrator 10 printing issue

    I have a client thatinstalled Illustrator 10 a while back with no problems. Then she installed CS2 with still no problems. I installed CS3 at her request and it seemed fine at first. She now says that when she boots up and just uses Illustrator 10 an

  • Macbook air needs space availiable

    Im trying to download the new OS X Mavericks! Its telling me that 'I could not complete my purchase because i need 4.93 GB of available space to download OS X Mavericks. Remove items fromyour startup disk to increase available space." How do I do tha

  • How BPEL human task becomes to state 'Withdrawn'

    All, what causes human task to go to 'Withdrawn' state. The reason i know is deleting associated bpel process. Are there any other events which causes this ? Regards, Praveen

  • Need of Datasource for the BP Master in CRM

    Dear Friends, I need of your help in finding out the proper datasource in BW3.5 which can provide me the information regarding the SalesArea in BP Master (Region, Sales District, Sales Office, Business Partner Code, Business Partner  Name). Thanks &