Database mirroring and service accounts

Hi,
I am trying to configure database mirroring with sql server 2012.
My principal instance and my mirror instance are on different server.
Both SQL Server service run with NT SERVICE\MSSQLSERVER.
Now when I am configuring database mirroring, which service account should I use ?
database account or server account ?
Instead of using domain account, can I :
1- create local account on my two server
2- Add these 2 logins in my 2 instances.
3- use these local account for configuring database mirroring.
regards

You should use domain account as I consider them more secured. What is database account there is nothing like that account here means valid windows login or domain account having privileges oon system.
Please read below
http://msdn.microsoft.com/en-us/library/ms189434.aspx
Setup a login account for DB Mirroring
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

Similar Messages

  • JMS based message service and Service account in OSB

    Hi forum,
    I have query regarding JMS base messaging service and Service account.
    My OSB service:
    I have created one OSB service which of type JMS
    configuration :
    General :Messaging
    Messaging: Request type :XML response type :none
    Transport:JMS
    JMS Transport: Destination Type queue., JMS Service account :.........(browse)
    My requirement is to provide security to JMS proxy.
    I have seen one option available in JMS transport is JMS Service Account.
    I dont have a idea about using service accounts in JMS.
    can any one pls give idea about JMS service account in JmS.How to provide security to jms proxy...
    If u have any documents pls share me
    Thanks & regards,
    Krishna.

    In your weblogic console go to your JMS Modules > ***JMSModule >****Queue >Roles >Policies. Add a user to the queue.This user should be there in the security realm of the weblogic console.
    Create a service account with the same user name password and use it in your OSB to read or write to the queue.

  • Difference between Database Mirroring and Cloning?

    Hi,
    Can anybody tell me the exact difference between Database Mirrorring and cloning?
    Is database mirroring and multiplexing same?
    Thanks
    Rajesh

    cannot be kept current automatically with the source database It is possible using manually scripted code to automatically update a cloned database to in effect build your own mirrowing process. This is basically a description of home grown Data Guard and is how many sites maintained a ready to use backup prior to Oracle introducing Data Guard.
    The best way to create a clone database today is probably to use the rman duplicate command.
    The clone could be the base for use with a mirrowing process you are setting up or used for other purposes such as providing a consistent frozen snapshot of production for special reporting. It could become the unit test or system test environment or perhaps be used for diaster recovery purposes.
    A clone is a one-time event. Mirrowing is an ongoing process.
    HTH -- Mark D Powell --

  • Database Mirroring and Replication in SQL Server 2008 R2

    I have configured the mirroring and replication between 4 servers (A,B,C,D).i.e, Mirroring between A to B and C to D, Replication between A and C. The configuration was a success and I am able test the replication(B to C) when I have failed over the mirroring
    dbs(A to B). The replication works fine after the mirroring fail over but I am not able to check its status in the Replication monitor. When I am having any insert in a table which is replicated in B, it is reflected back to C..it means the replication is
    working fine.
    Any thought on how I can view the status of replication from mirrored server. I tried adding the publisher in the monitor, but no luck. If I check the snapshot agent status, it says could not retrieve the info, same with the log reader agent status.
    Any suggestions on this please.
    Thanks, Siri

    For example in your case...
    Server A is principal and Server B is Mirror with either Manual or Automatic Failover.
    Server A is replicated to Server B ( publisher & B is subscriber )
    In Server A Database named Test_Mirror_Replication is configured for both mirroring and Replication.
    Now you have failed over your Database 'Test_Mirror_Replication' from Server A to Server B.
    After the Failover Server A will act as Mirror for DB 'Test_Mirror_Replication' & Server B will act as Principal for DB 'Test_Mirror_Replication'
    Hope my understanding is correct ?
    If yes then have you tried monitoring the replication after registering in other instance with current principal database sql instance name ? I mean current Publisher database name sql instance ? not your old sql instance name which was before the mirroring
    role change or failover...
    Hope you are trying with mirror database server name ?
    Raju Rasagounder MSSQL DBA

  • Database Mirroring and replication

    Hi,
    can mirroring and replication is possible on same instance of sql
    of sql server 2008. if yes then please provide the  information.
    thanks in advance.

    You may need to use traceflag 1448 to get this to work.
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • Reverse database mirroring - and is this the right approach?

    Here is my scenario. I have 2 database servers, P and M, to serve our production website. P = Principal; M = Mirror.
    After some time my Principal crashes. No problem, I've got M, it's been synchronizing, and it has all latest data. So I repoint my production web server to hit the Mirror. Still, all is good.
    Now comes the part where I'm fuzzy, and I need to know if my understanding is correct...
    The Principal comes back online, but my website is still pointing at the Mirror. I want to repoint the site back to Principal. But P now has old data. Maybe it's been down 3 days and M has 100,000 new records that don't exist in P. When P came back online,
    did transaction logs begin shipping from M to P to get P back in sync? Would it do that if a Witness were in place? How does P get caught up with all latest data? Do I have to do a full backup and restore from M to P? Is there a way this can be set up to just
    gracefully (or even easy manual) get P updated and synced? Can the Principal/Mirror roles be easily swapped between the 2 servers? Does that happen automatically with a Witness in place?
    Thanks in advance for any help.

    First, mirroring is being removed for "AlwaysOn" technology.  I would not recommend using it in SQL 2012.  However, if you are talking about prior versions, then...
    When the failover occurs, the old mirror, now primary, attempts to send updates back to the old principal, now mirror.  This is completely automatic and requires nothing manual to happen.
    However, if the now mirror is down for a long period of time, the transaction log on the principal will continue to grow and grow until it is able to deliver the transactions to the mirror.
    You can setup your website with a "Failover Partner=" in the connection string and the failover/failback will be completely invisible to your application.
    I would suggest reading:
    http://technet.microsoft.com/en-us/library/ms189852.aspx
    http://technet.microsoft.com/en-us/library/cc917713.aspx

  • Service SID and setup account for DB engine service

    SQL supports service isolation of access control through granting permissions to the service SID. However, we also can give the privileges to service account. Which one of the service
    SID  and service account has higher priority? If we give the conflicting permissions to service SID and service account, which one will work?

    Hi smileahpu,
    In short, for account rights/privileges, there are two general types Allow and Deny. The "Allow" rights/privileges are combined, and the "Deny" rights/privileges are exclused. The DENY(SE_DENY) rights override the corresponding account
    rights. In this case, either the service account or the service sid is denied on a right, the service is denied on the right.
    To be more detailed, we need to go through the following topics:
    How does system validate a process's privileges while accessing securable objects
    How does per-service SID work while accessing securable objects
    How does Access Control work
    How a process accesses securable objects:
    The system uses an access token to identify the user when a thread(or a process) interacts with a securable object or tries to perform a system task that requires privileges.
    An access token is an object that describes the security context of a process or thread.
    Access token contains lots of information. Two of them are:
    •The security identifier (SID) for the user's account
    •A list of the privileges held by either the user or the user's groups
    Please review the following article for more information:
    http://msdn.microsoft.com/en-us/library/windows/desktop/aa374909(v=vs.85).aspx
    How does per-service SID work while accessing securable objects
    For a service without per-Service SID enable, we can image the security context is just from the user(service account). With per-Service SID enabled, we can make a security context that is not just a user, but a user AND a particular process.
    Actually, the per-Service SID's SID and privilege are included the access token directly.
    By checking with Windbg, we can see the service SID was included.
    0:072> !token
    Thread is not impersonating. Using process token...
    TS Session ID: 0
    User: S-1-5-21-3485830563-343820118-176642512-1008
    User Groups:
     00 S-1-5-21-3485830563-343820118-176642512-513
        Attributes - Mandatory Default Enabled
     01 S-1-1-0
        Attributes - Mandatory Default Enabled
     02 S-1-5-21-3485830563-343820118-176642512-1009
        Attributes - Mandatory Default Enabled
     03 S-1-5-32-545
        Attributes - Mandatory Default Enabled
     04 S-1-5-6
        Attributes - Mandatory Default Enabled
     05 S-1-2-1
        Attributes - Mandatory Default Enabled
     06 S-1-5-11
        Attributes - Mandatory Default Enabled
     07 S-1-5-15
        Attributes - Mandatory Default Enabled
     08 S-1-5-113
        Attributes - Mandatory Default Enabled
     09 S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003 < -- service SID
        Attributes - Default Enabled Owner
     10 S-1-5-5-0-274023807
        Attributes - Mandatory Default Enabled Owner LogonId
     11 S-1-2-0
        Attributes - Mandatory Default Enabled
     12 S-1-5-64-10
        Attributes - Mandatory Default Enabled
     13 S-1-16-12288
        Attributes - GroupIntegrity GroupIntegrityEnabled
    Primary Group: S-1-5-21-3485830563-343820118-176642512-513
    Privs:
     00 0x000000003 SeAssignPrimaryTokenPrivilege     Attributes -
     01 0x000000005 SeIncreaseQuotaPrivilege          Attributes -
     02 0x000000013 SeShutdownPrivilege               Attributes -
     03 0x000000017 SeChangeNotifyPrivilege           Attributes - Enabled Default
     04 0x000000019 SeUndockPrivilege                 Attributes -
     05 0x00000001d SeImpersonatePrivilege            Attributes - Enabled Default
     06 0x00000001e SeCreateGlobalPrivilege           Attributes - Enabled Default
     07 0x000000021 SeIncreaseWorkingSetPrivilege     Attributes -
     08 0x000000022 SeTimeZonePrivilege               Attributes -
    Auth ID: 0:105545a6
    Impersonation Level: Anonymous
    TokenType: Primary
    Is restricted token: no.
    SandBoxInert: 0
    Elevation Type: 1 (Default)
    Mandatory Policy: TOKEN_MANDATORY_POLICY_VALID_MASK
    Integrity Level: S-1-16-12288
    Process Trust Level: (null)
    Token Virtualized: Disabled
    UIAccess: 0
    IsAppContainer: 0
    Device Groups:
    How does Access Control work
    Please check from the following article for more information:
    http://technet.microsoft.com/en-us/library/cc740104(v=ws.10).aspx
    In addition, the following articles are helpful for understanding the concepts discussed in this reply:
    http://msdn.microsoft.com/en-us/library/windows/desktop/bb545671(v=vs.85).aspx
    http://msdn.microsoft.com/en-us/library/windows/desktop/ms684880(v=vs.85).aspx
    http://technet.microsoft.com/en-us/library/cc781716(v=ws.10).aspx
    http://blogs.technet.com/b/voy/archive/2007/03/22/per-service-sid.aspx
    Thanks,
    Jinchun Chen

  • BizTalk Service Account and Groups

    Hi,
    I need to install BizTalk server 2013 in Development server, please let me know the list of BizTalk service Account and What are all the groups need to  be created.
    Regards, Aboorva Raja R Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Hi
    You can find complete list of service accounts and groups on
    Windows Group and User Accounts in BizTalk Server MSDN page.
    These accounts needs to be created in your Active Directory server. 
    I would suggest you to have a look of
    Installing BizTalk Server 2010 in a Basic Multi-Computer Environment: The need for a Domain Controller – Windows Groups and Service Accounts (Part 2) blog post . Although this is for BizTalk 2010, but this may give you some idead about Accounts used in
    BizTalk setup.
    Also please have a read of
    Installation Overview for BizTalk Server 2013 and 2013 R2 
    Feel free to post any errors you get while installing. 
    Greetings,HTH
    Naushad Alam
    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or
    Mark As Answer
    alamnaushad.wordpress.com

  • Database Mirroring problem

    I'm getting an error setting up Mirrroring that I cannot seems to fix. I'm using a setup of two SQL servers with no witness, both running SQL Server 2008 R2. I setup the perms on Primary, Backup Full the database in question (MMS Database to test) and then
    restore that using NO Recovery on the Secondary. I then setup the Security Wizard on the Primary, after which it sets up the end-points correctly on both servers using the service account which is local admin and Sysadmin on both boxes. However, when I then
    choose to start mirroring, I consistently get a 1418 error saying that the server cannot be reached or does not exist. I have verified that the FQDN and port 5022 is open using Netstat and using telnet and TCP protocol is enabled on both boxes. 
    Any other suggestions? Any obvious perms I might have forgotten to copy across? I've copied App Pool, CA, Content Access, Cache and Service accounts to the secondary box as logins with no fixed roles. Both End Points for Database Mirroring list as started. 

    Hi Robin,
    According to your description, my understanding is that the error occurred when mirroring the databases.
    Did you use Kerberos authentication in SharePoint?
    If yes, when you run the SQL Server service under a domain account or under a local account, the attempt to create the SPN will fail in most cases because the domain account and the local account do not have the right to set their own SPNs. When the SPN
    creation is not successful, this means that no SPN is set up for the computer that is running SQL Server, so the communication between the servers will fail.
    So I recommend to configure the SPN for SQL, please refer to the link below:
    http://support.microsoft.com/kb/811889/en-us
    Here is a similar issue for you to take a look:
    http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=191014
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • SP2010 Application Pool Service Account fails to login to master database on a SQL Server mirror

    This is a weird problem that just started showing up, cause unknown. Could go in this forum or in SQL 2008...I put it here because for me the context is SP2010.
    We have 2 SQL servers (2008 R2 with SP1). Each server has 2 named instances, the second being a mirror for the other server's main instance. In other words, the named instance /SQL has a /SQLMirror on the other server and vice versa.
    The error is: Login failed for user 'domain\sharepointapppoolaccount'. Reason: Failed to open the explicitly specified database.
    As best I can tell, the specified database is "master" on the mirror instance. I am unaware of any reason for the app pool account to be connecting to the master on the mirror (the master database itself is NOT mirrored). There is nothing
    in the user mapping that would suggest any reason to try connecting. And there are no equivalent errors in the main instance (SQL).
    SP2010 Event ID 18456 - Why would a service account try to connect to the master database?

    Hi,
    When the principal server(SQL) disconnects clients from the principal database, then the mirror server(SQL) will take charge of clients’ requests.
    So the error is regarding to the mirror server may be due to that the mirror server is taking charge of the clients’ request instead of the principal server when the principal is becomes unavailable.
    I recommend to grant sysadmin permissions to the service account in SQL(mirror server) to see if the issue still occurs.
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • Database Mirroring Login Accounts

    I need to setup database mirroring between 2 separate SQL 2012 instances. The documentation states that if the 2 server instances are running under different user accounts then these need to be manually created on both instances. Is this login account the
    account that was used when installing SQL or is it the account assigned to run the SQL server service account?
    Thanks
    Alistair

    If the server instances run as different user accounts, user logins on the server instance that hosts the principal server or primary replica must be manually reproduced on the server instance that hosts the mirror server or on every server instance that
    hosts a secondary replica. For more information, see Create a Login for a Different Account and Grant
    Connect Permission, later in this topic.
    I am still unsure what it means when it refers to
    'If the server instances run as different user accounts'. Is this the account that shows in services under our instance 'SQL Server (MSSQLSERVER)?
    Thanks
    Did you read below example(http://technet.microsoft.com/en-us/library/ms366346.aspx#CreateLogin)
    For example, for the server instance sqlA, which runs under loginA, to connect to the server instance sqlB, which runs under loginB, loginA must be in the
    syslogins table on sqlB, and loginB must be in the syslogins table on sqlA. In addition, for a database mirroring session that includes a witness server instance (sqlC) and in which the three server instances run under different
    domain accounts, the following logins must be created:
    On instance...
    Create logins for and grant connection permission to ...
    sqlA
    sqlB and sqlC
    sqlB
    sqlA and sqlC
    sqlC
    sqlA and sqlB
    Note
    It is possible to connect with the network service account by using the machine account instead of a domain user. If the machine account is used, it must be added as a user on the other server instance.
    Is it still unclear
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Service accounts for the Workspace Database service permission Error while creating Tabular Mode from PowerPivot

    Hi All,
    Please help me out against this issue. I have spent so much (3 working days) time just figuring out what is the issue and its solution.
    I am learning Tabular Mode and trying to create a mode based on PowerPivot model. I am getting following error message:
    'The PowerPivot workbook could not be imported. The service account for the workspace database server does not have permission to read from the PowerPivot workbook.'
    Here is my infrastructure:
    1. SSAS in Tabular Mode is installed on my Windows 8 Laptop
    2. PowerPivot is also in my laptop
    3. There is only my account (as Admin of course) for SSAS
    Here are my questions:
    1. What is this error and how can I cope with that? A step by step explanation would be highly appreciated :-)
    2. Do I need to change something in Windows settings or in SSAS?
    3. I am confused about my workspace database server as well, Do I have to install SSAS twice; one for development and one for workspace?
     Looking forward for the expert advise.
    Tahir
    Thanks, TA

    Hi,
    I suspect you might have more luck if you try the SSAS forum: http://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlanalysisservices
    Regards
    Jamie
    ObjectStorageHelper<T> – A WinRT utility for Windows 8 |
    http://sqlblog.com/blogs/jamie_thomson/ |
    @jamiet |
    About me

  • DataBase unavailable and Mirrored Db role has chnaged.

    Hello All,
    We got below errors in our principal and Mirror db servers.
    1) The mirroring connection to "TCP://servername.domain.com:5022" has timed out for database "Db name" after 10 seconds without a response.  Check the service and network connections.(Mirror Server).
    2) Database mirroring is inactive for database 'DB Name'. This is an informational message only. No user action is required.(Pricipal)
    2) The command failed because the database mirror is busy. Reissue the command later. .(Pricipal)
    3) The mirrored database "Db" is changing roles from "PRINCIPAL" to "MIRROR" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action
    is required. .(Pricipal)
    Before the first error we got an alert that db is unavailable. After 1 min of this alert the issue has started.
    After a successful fail-over of that particular db to mirror again it was rolled back to principle automatically. After that I can see a server shut down with below errors.and mirroring failed on all the dbs.
    Database mirroring connection error 4 'The connection was closed by the remote end, or an error occurred while receiving data: 55(The specified network name is no longer available.)'' for 'TCP://Server Name.Domain.com:5022'.(Mirror)
    Database mirroring connection error 4 'An error occurred while receiving data: '1054(An existing connection was forcibly closed by the remote host.)'.' 'TCP://Server Name.Domain.com:5022'. .(Mirror)
    SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required. (Pricipal)
    The connection has been lost with Microsoft Distributed Transaction Coordinator (MS DTC). Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) will begin once the connection is re-established.
    This is an informational message only. No user action is required. (Pricipal)
    SQL Server cannot accept new connections, because it is shutting down. The connection has been closed. [CLIENT: IP. (Pricipal)
    I am very confused that why this db unavailable before the issue. I don’t have any information about this.
    Can some body help me to find out the root cause why this unexpected fail over and
     sql shutdown.

    Hello,
    It looks like something was updated or done to the end system as:
     'An error occurred while receiving data: '1054(An existing connection was forcibly closed by the remote host.)'
    Is generally caused by a firewall. Please double check software and hardware firewalls (including endpoint protection software) and make sure the exceptions for port 5022 tcp exist.
    -Sean
    The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

  • How to use the mirrored and log shipped secondary database for update or insert operations

    Hi,
    I am doing a DR Test where I need to test the mirrored and log shipped secondary database but without stopping the mirroring or log shipping procedures. Is there a way to get the data out of mirrored and log shipped database to another database for update
    or insert operations?
    Database snapshot can be used only for mirrored database but updates cannot be done. Also the secondary database of log shipping cannot used for database snapshot. Any ideas of how this can be implemented?
    Thanks,
    Preetha

    Hmm in this case I think you need Merge Replication otherwise it breaks down the purpose of DR...again in that case.. 
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • SQl Server Installation failing for Database Engine and Its Services

    Hi,
    I was trying to install SQL SERVER 2008 R2 on VM having 500 GB hard disk and 16 GB RAM.
    OS is Windows Server 2008
    But it fails for Database Engine.
    Installation Details are as Below.
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2068119551
      Exit facility code:            1211
      Exit error code:               1
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2014-10-13 18:41:01
      End time:                      2014-10-13 19:26:32
      Requested action:              Install
      Log with failure:              C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0x476BF04A%400xBB814387
    Machine Properties:
      Machine name:                  KVS-IN-WFAN092
      Machine processor count:       4
      OS version:                    Windows Server 2008 R2
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         di-softwareSoftwaresSQLSQL_2008_R2_Enterprisex64setup
      Installation edition:          ENTERPRISE
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 NT AUTHORITYNETWORK SERVICE
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CONFIGURATIONFILE:             C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,SSMS,ADV_SSMS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT AUTHORITYLOCAL SERVICE
      FTSVCPASSWORD:                 *****
      HELP:                          False
      IACCEPTSQLSERVERLICENSETERMS:  False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:Program FilesMicrosoft SQL Server
      INSTALLSHAREDWOWDIR:           C:Program Files (x86)Microsoft SQL Server
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:Program FilesMicrosoft SQL Server
      INSTANCEID:                    SQLServer
      INSTANCENAME:                  SQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITYNetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITYNETWORK SERVICE
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           KRONOSENGsuperuser
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    1
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354SystemConfigurationCheck_Report.htm
    And Error in log file are maily as below.
    2014-10-13 19:26:27 Slp: Completed Action: SqlBrowserConfigAction_install_Startup_Cpu32, returned True
    2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
    2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11
    dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-10-13 19:26:27 Slp: Action "SqlBrowserConfigEngAction_install_Startup_Cpu64" will return false due to the following conditions:
    2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: SqlBrowserConfigEngAction_install_Startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested
    for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-10-13 19:26:27 Slp: Action "SqlEngineConfigAction_install_startup_Cpu64" will return false due to the following conditions:
    2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: SqlEngineConfigAction_install_startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested
    for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-10-13 19:26:27 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
    2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant
    features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-10-13 19:26:27 Slp: Action "AgentInstall_AgentInstallStartup_Cpu64" will return false due to the following conditions:
    2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: AgentInstall_AgentInstallStartup_Cpu64 The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results:
    ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
    2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There
    are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
    2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature
    is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-10-13 19:26:27 Slp: Action "FulltextConfigAction_install_startup_Cpu64" will return false due to the following conditions:
    2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: FulltextConfigAction_install_startup_Cpu64 The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature is tested for results:
    ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
    2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There
    are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-10-13 19:26:27 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
    2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are
    2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
    2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64.
    There are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
    2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features.
    The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-10-13 19:26:27 Slp: Completed Action: PostMsiTimingConfigAction, returned True
    2014-10-13 19:26:27 Slp: Completed Action: ExecuteStandardTimingsWorkflow, returned True
    2014-10-13 19:26:27 Slp: ----------------------------------------------------------------------
    2014-10-13 19:26:27 Slp: Running Action: ExecuteExtendedTimingsWorkflow
    Thanks,
    Mahesh

    I have uploaded detail.txt at below url.
    http://m.uploadedit.com/b041/1413264342685.txt
    Hi Mahesh,
    According to log file, I find the message ‘The setup100.exe.config file was not found, therefore the DTSWizard and SQLWatson app config files were not replaced’. It seems that the SQL Server setup file is not complete. Please check that if the SQL Server
    setup file is corrupted, if it is corrupted, please download it again and reinstall SQL Server 2008 R2.
    However, if there’s no problem with the setup file, please check that if there is third-party software such as anti-virus software on your computer blocking the process of SQL Server installation. In addition, make sure that you choose ‘Run as administrator’
    to launch the setup and configure SQL Server service accounts appropriately with administrator permission during the installation.
    For more details about this error, please review the following similar thread.
    http://answers.flyppdevportal.com/categories/sqlserver/sqlsetupandupgrade.aspx?ID=ad794a97-09ae-4aae-9d68-0b06f9af3e16
    Thanks,
    Lydia Zhang

Maybe you are looking for