Services configuration for sql server 2008r2 in a Windows Cluster

Hello,
We have a Windows Server 2008 Cluster with Sql Server 2008r2 installed on node 2; when node 2 fails (we don't still know why, it's a 'bluescreen' long history), the service goes from node2 to node1, but sometimes the services are not automatically activated.
What is the theoretical startup settings for sql services (for the sql and the agent), manual, disabled, automatic... ?
Also, sometimes, the service for the sql server in node2 stops, but we don't know why, and we are not able to see any significant information on the event viewer. How can we trace why Sql Server stopped ?
Thanks !

>What is the theoretical startup settings for sql services
Manual.  The cluster will start them.
>How can we trace why Sql Server stopped ?
Look in the SQL Server Log.
David
David http://blogs.msdn.com/b/dbrowne/

Similar Messages

  • Will Cumulative Update 12 for SQL Server 2008R2 SP2 fix: Warning: Unable to Verify TimeStamp for Path\ProgramName?

    Hello,
    I had a server crash recently and our outsource hosting tech support suggested applying Cumulative Upade 12 for SQL server 2008R2 SP2 to fix the issue.  The exception from our dump file "Warning: Unable to Verify TimeStamp for Path\ProgramName"
    is not in the list of hotfixes for this CU.  Do you know if this will fix this issue?  The CU warns not to apply the CU if your issue id not addressed by the CU.  Here is a portion of the dump file with the relevant error:
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (7e8.2ab4): Unknown exception - code 000042ac (first/second chance not available)
    ntdll!NtWaitForSingleObject+0xa:
    00000000`777412fa c3              ret
    0:240> .sympath srv*c:\Websymbols*http://msdl.microsoft.com/download/symbols;
    Symbol search path is: srv*c:\Websymbols*http://msdl.microsoft.com/download/symbols
    Expanded Symbol search path is: srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
    0:240> .reload /f
    .Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlservr.exe
    ..........Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlos.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlos.dll
    ...............Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\opends60.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for opends60.dll
    .......Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\BatchParser.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for BatchParser.dll
    ....Unable to load image C:\Program Files\Microsoft SQL Server\100\Shared\instapi10.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for instapi10.dll
    *** ERROR: Module load completed but symbols could not be loaded for instapi10.dll
    ..Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\sqlevn70.rll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlevn70.rll
    *** ERROR: Module load completed but symbols could not be loaded for sqlevn70.rll
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    .................Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\ftimport.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ftimport.dll
    .Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\msfte.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for msfte.dll
    *** ERROR: Module load completed but symbols could not be loaded for msfte.dll
    ...........Unable to load image C:\Windows\System32\sqlncli10.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlncli10.dll
    ...Unable to load image C:\Windows\System32\1033\SQLNCLIR10.RLL, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SQLNCLIR10.RLL
    *** ERROR: Module load completed but symbols could not be loaded for SQLNCLIR10.RLL
    ..Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\xpsqlbot.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for xpsqlbot.dll
    .Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\XPStar.DLL, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for XPStar.DLL
    .Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlscm.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlscm.dll
    ...*** ERROR: Module load completed but symbols could not be loaded for odbcint.dll
    ...Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\XPStar.RLL, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for XPStar.RLL
    Thank you,
    Steve -

    The error message appears to be related to a debug session and not come from the actual crash.
    So all I know is that you hade a server crash. I don't even know exactly what that means. Did Windows bite the dust? Or was it only SQL Server?
    Assuming the latter, I would expect the SQL Server errorlog to have some information (and that would be ERRORLOG.1 or earlier, since the server have been restarted), but if SQL Server died the output may be incomplete.
    There may be also dump files, but as I rarely look into these, I am not sure how to interpret them. But I am quite confident that "Unable to verify TimeStamp..." is not the reason SQL Server went down.
    I would suggest the following course:
    *  If the server is not critical, do nothing. As long as it has onlyl happened once, it has only happened once.
    *  If the server is critical, open a case with Microsoft if you are not able to figure out the reason yourself. The key here is "Unknown exception - code 000042ac".
    *  If it happens again, you should absolutely open a case. An important thing here is whether the stack dump is identical or something different. If the stack dumps are identical, you may have hit a bug in SQL Server or the OS, and applying CUs or OS
    fixes could help if it is a known issue. If the stack dump is something else, you have ghosts in the machine - that is, bad hardware.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Service Account for SQL Server Agent on SQL Server 2008 R2

    This SQL Server instance is SQL Server 2008 R2 (10.50.4000).  We had Active Domain Service accounts created to run the service accounts for SQL Server and SQL Server Agent.
    It has become company policy to alter the service accounts that run SQL Server and SQL Server Agent.  Currently, both were running under the Local System Accounts.  We have altered the SQL Server but we are having issues with the SQL Server Agent. 
    I am told by another DBA that
    "The agent is requiring elevated rights.  It will startup if it has local admin rights, but not with domain accounts without admin rights."
    So I was wondering if anyone has come across this issue and how did they resolve it.
    lcerni

    "The agent is requiring elevated rights.  It will startup if it has local admin rights, but not with domain accounts without admin rights."
    This is completely not true. It is indeed possible to run agent as a domain account without giving it local admin. Chances are you'll need to update the local acls by adding the account to the local security groups. Please see this article for more information:
    http://technet.microsoft.com/en-us/library/ms143504(v=sql.105).aspx
    Edit: In addition, it'll need rights to SQL server for that account to connect and do its work. It will need to be given sysadmin:
    http://technet.microsoft.com/en-us/library/ms191543.aspx
    Sean Gallardy | Blog |
    Twitter

  • Which .exe file I should choose to apply SP2 for SQL Server 2008r2 Enterprise Edition 64Bit

    Hi All,
    Which .exe file I should choose to apply SP2 for SQL Server 2008r2 Enterprise Edition 64Bit.
    And what is the difference between below .exe files. 
    SQLServer2008R2SP2-KB2630458-x64-ENU.exe
    SQLServer2008R2SP2-KB2630458-IA64-ENU.exe
    Grateful to your time and support. Regards, Shiva

    Good day
    Shiva Shakthi,
    I have change the type of the thread to a question, as this is a question :-)
    please chose the right type next time. If you have a question then use a question thread (this is the default), and that will let you mark the answers that you get.
    Have a nice day :-)
    [Personal Site] [Blog] [Facebook]

  • While installing the SQL Server 2008R2 edition in Windows 7 professional servicepack1 is not installing?

    Hi frnz ,
    while am  installing the SQL Server 2008R2 edition in Windows 7 professional servicepack1 machine is not instlling properly.
    am follwing the installtion stups.
    instiall two stups is going fine next .after completion of the following setup install comp( see the screen shoot below)nothing is happens ,its not going foreword further stups.
    Can some one please help me out for this......
    I will found in the Task manager the set up file is Running....

    Hi Ychinnari,
    Based on your description, you fail to install SQL Server 2008 R2 on Windows 7 SP1.
    According to the screenshot, we need to verify that if SQL Server 2008 R2 setup disappears when installing setup support files. If so, please post the error message from  SQLSetup.log file of the temp folder for analysis. Click on start->run and
    type %temp %  and press enter, you will navigate to the temp folder. For more details, you can review this
    blog.  Also, please help to collect the summary and detail logs, by default, the logs can be found in: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log.
    In addition, there are some proposals for you troubleshooting this issue.
    1. Ensure that your system meets the
    hardware and software requirements for installing SQL Server 2008 R2.
    2. Make sure that you install SQL Server 2008 R2 with a admin account, and please choose “Run as administrator” to  complete installation.
    3. Make sure that previous installations of SQL Server has been uninstalled completely from your computer. For more details, please review the similar blog:
    SQL Server 2008 R2 Setup starts and then disappears.
    4. Stop any Anti-Virus software when installing SQL Server 2008 R2.
    Thanks,
    Lydia Zhang

  • Group managed service accounts for SQL Server

    Hey guys,
    Unfortunately I missed that (g/s)MSAs aren't supported yet for SQL Servers but I'm using them without any worries since ages.
    As i digged a bit deeper I could find different informations due to the related TechNet entrys. So it seems Microsofts Informations about (s)MSAs and gMSAs aren't consistent.
    I'm not a SQL Server guy and use SQL only for System Center testing stuff so i would like to get a real world exps of SQL Server guys.
    Should I continue using gMSAs or are there any worries I should know?
    some sources I found so far:
    Not supported:
    "Hi Adam,
    Thank you for your feedback. Windows Server 2012 Group Managed Service Account is not currently supported as SQL 2012 released earlier than Windows Server 2012. We will consider to support gMSA in future SQL Server release.
    Regards,
    Min He, Program Manager, SQL Server"
    11.2012 -
    https://connect.microsoft.com/SQLServer/feedback/details/767211/gmsa-for-sql-server-failover-Clusters
    gMSA are not yet available, are not yet supported for SQL Server.  gMSA exist and are available and supported in Windows Server 2012 and higher.  SQL does not support them , but
    from an OS perspective, they exist and are supported.    
    http://blogs.msdn.com/b/sqlosteam/archive/2014/02/19/msa-accounts-used-with-sql.aspx
    Within the FAQ Task Scheduler isn't supported as well ...
    http://technet.microsoft.com/en-us/library/ff641729%28WS.10%29.aspx
    ... but also PFEs using them for Tasks... this is confusin... 0o
    http://blogs.msdn.com/b/arvindsh/archive/2014/02/03/managed-service-accounts-msa-and-sql-2012-practical-tips.aspx
    supported?:
    Configure Windows Service Accounts and Permissions
    ... New Account Types Available with Windows 7 and Windows Server 2008 R2
    http://technet.microsoft.com/en-us/library/ms143504(v=sql.110).aspx#Default_Accts
    The MSA must be created in the Active Directory by the domain administrator before SQL Server setup can use it for SQL Server services.
    others sources won't mentioning s/gMSAs...
    I couldn't find clear informations about using gMSA for SQL Server 2014. 
    only the same page which also Looks like the page for 2008 R2 and SQL 2012.
    Configure Windows Service Accounts and Permissions
                SQL Server 2014        
    http://msdn.microsoft.com/en-us/library/ms143504.aspx
    annoying topic so far... ;) 

    Hi Enrico
    aside from what Dan says about the risk for support, on which I agree, the following thread may clear it up a bit:
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/acb2048c-ffce-4d44-b882-6aafc7eb689d/managed-service-accounts-to-run-sql-server-service?forum=sqlsecurity
    Andreas Wolter (Blog |
    Twitter)
    MCM - Microsoft Certified Master SQL Server 2008
    MCSM - Microsoft Certified Solutions Master Data Platform, SQL Server 2012
    www.andreas-wolter.com |
    www.SarpedonQualityLab.com

  • Question : Service Accounts for SQL Server 2012

    Hello,
    I am planning to create AD accounts for SQL Server 2012 services that will be installed on Windows 2012 server.
    I was reading the following
    Configure Windows Service Accounts and Permissions
    and
    Windows Privileges and Rights
    Is there a recommendation / document that would list that assocation of SQL Server Services with Actvie Directory service accounts / privileges required for installation and starting the services.
    Isn't it recommended to create separate account for every service and they should not be local accounts ?
    Hope to hear soon as to what industry standards are being followed for production systems ?
    Thank you very much in advance.
    Regards
    Nikunj

    From MSDN:
    Each service in SQL Server represents a process or a set of processes to manage authentication of SQL Server operations with Windows. Each service can be configured to use its own service account. This facility is exposed
    at installation. SQL Server provides a special tool, SQL Server Configuration Manager, to manage the services configuration.
    When choosing service accounts, consider the principle of least privilege. The service account should have exactly the privileges that it needs to do its job and no more privileges. You also need to consider account isolation; the service accounts should
    not only be different from one another, they should not be used by any other service on the same server. Do not grant additional permissions to the SQL Server service account or the service groups.
    From Glen Berry's Blog:
    You should request that a dedicated domain user account be created for use by the SQL Server service. This should just be a regular, domain account with no special rights on the domain. You do not need or want this account to be a local admin on the machine
    where SQL Server will be installed. The SQL Server setup program will grant the necessary rights on the machine to that account during installation.
    You will also want a separate, dedicated domain user account for the SQL Server Agent service. If you are going to be installing and using other SQL Server related services such as SQL Server Integration Services (SSIS), SQL Server Reporting Services (SSRS),
    or SQL Server Analysis Services (SSAS), you will want dedicated domain accounts for each service. The reason you want separate accounts for each service is because they require different rights on the local machine, and having separate accounts is both more
    secure and more resilient, since a problem with one account won’t affect all of the SQL Server Services.
    Depending on your organization, getting these domain accounts created could take anywhere from minutes to weeks to complete, so make sure to allow time for this. For each one of these accounts, you will need their logon credentials for the SQL Server setup
    program. You are going to want to make sure that the accounts don’t have a temporary password that must be changed during the next login. If they are set up that way, make sure to change them to use a strong password, and record this information in a secure
    location.
    Please Mark This As Answer if it solved your issue
    Please Mark This As Helpful if it helps to solve your issue
    Thanks,
    Shashikant

  • MS14-044 for SQL Server 2008 Standard on Windows Server 2003?

    MS14-044 was recently released and states that it applied to MS SQL Server 2008 SP3, yet the patches available for this security bulletin do not list Windows Server 2003 in the supported operating systems. Does MS14-044 not apply to SQL Server running
    on Windows Server 2003? If it does apply, why isn't there an update available to run on Windows Server 2003?

    Hi Chasg76,
    According to your description, the patches available for MS14-044 do not list Windows Server 2003 in the supported operating systems and you want to know whether MS14-044 applies to SQL Server running on Windows Server
    2003.
    Based on my test, KB2977321 applies to SQL Server 2008 Service Pack 3 product and it does apply to SQL Server 2008 SP3 running on Windows Server 2003.
    I installed SQL Server 2008 Service Pack 3 in Windows Server 2003 SP2 x86. After the service pack 3 installation completed, KB2977321 was offered in the Automatic Update.
    Besides, you can manually install the update by downloading the update form the Download Center web site as well.
    I also tried the manually installation and I downloaded the Security Update for SQL Server 2008 Service Pack 3 (KB2977321) from this web: Security Update for SQL Server 2008 Service Pack 3 (KB2977321) (https://technet.microsoft.com/library/security/MS14-044),
    it was installed successfully.
    After installed security upgrade, I checked the file attributes and compared to this article: MS14-044: Description of the security update for SQL Server 2008 SP3 (GDR): August 12, 2014(http://support.microsoft.com/kb/2977321/en-us).
    The result is the same.
    According to my test, MS14-044 applies to SQL Server running on Windows Server 2003 even though Windows Server 2003 is not listed in the supported operating systems.
    Best regards,
    Qiuyun Yu

  • Help! Licence for SQL Server 2008 VM on Windows 2012

    I am confused by latest Microsoft Virtual server licence for SQL Server 2008. 
    We have a Hyper-V host running Windows Server 2012 R2 Datacenter. Displayed in its Task Manager, it has 16 cores and 32 logical processors (with hyper-threading turned on). A SQL Server VM is running on this host with 10 Virtual processors (showing from Hper-V
    Manager). The SQL Server edition is SQL Server 2008 Standard. 
    We are using "Per Core Licensing Model". Now, the question is how many licences we need to purchase for the above SQL Server?
    There are "SQL Server 2008 Licensing Guide", "Microsoft SQL Server 2012 Virtualization Licensing Guide" and "Microsoft SQL Server 2014 Licensing Guide". But none of them covers this scenario, which is running SQL Server 2008 on
    Windows 2012 Hyper-V host Server.
    Could you please provide me your opinion: Should I license 10 cores for the SQL Server VM or license 5 cores (because the hyper-threading on physical server) ? Thank you very much in advance! 

    I am confused by latest Microsoft Virtual server licence for SQL Server 2008. 
    We have a Hyper-V host running Windows Server 2012 R2 Datacenter. Displayed in its Task Manager, it has 16 cores and 32 logical processors (with hyper-threading turned on). A SQL Server VM is running on this host with 10 Virtual processors (showing from Hper-V
    Manager). The SQL Server edition is SQL Server 2008 Standard. 
    We are using "Per Core Licensing Model". Now, the question is how many licences we need to purchase for the above SQL Server?
    There are "SQL Server 2008 Licensing Guide", "Microsoft SQL Server 2012 Virtualization Licensing Guide" and "Microsoft SQL Server 2014 Licensing Guide". But none of them covers this scenario, which is running SQL Server 2008 on
    Windows 2012 Hyper-V host Server.
    Could you please provide me your opinion: Should I license 10 cores for the SQL Server VM or license 5 cores (because the hyper-threading on physical server) ? Thank you very much in advance!

  • How configure reporting services configuration with sql server business development studio

    I have installed sql server 2008 r2 mixed mode(sql server authentication) with native mode
    I want to run report using reporting  services config manager.
    I made report in ssrs and I have configured reporting services configuration and  web url from RSCM( reporting  services config manager), i put on ssrs report.
    report is build and deployed but when i take deployed url on Internet explorer, it shows the window below:
    when I put the password nothing happened . if I put url in google chrome then it shows authentication required window like the same in IE
    if I passed username=(levent/sa) and password then goes on window but does not see on page,  if I passed only administrator name (levent) not passed sql server login name (sa) then does not close 'Authentication window'
    'Computer connect net with modem'
    before i tried on earlier PC, it worked fine.
    setting is below link like this.
    only set service Account is Use_built=NetworkSrvice 
    link
    http://www.azurecurve.co.uk/2012/02/how-to-configure-sql-server-reporting-services-in-order-to-deploy-reporting-services-reports-in-gp/
    what is the problem 
    Plz give suggestion quickly

    Hi tusharshinde,
    Per my understanding that when you log in the report Manager you got the pop-up window ask for credential, you try to enter  the SA account and the window account as the username and password but both not work, right?
    Your issue related to the authentication. As you mentioned you have choose the ”Network Service” as the Service account, generally using this account in RSCM and RSWindowsNegotiate is added to the RSReportServer.config file as the default setting. With this
    setting, the report server can accept requests from client applications requesting Kerberos or NTLM authentication. If Kerberos is requested and the authentication fails, the report server switches to NTLM authentication and prompts the user for credentials
    unless the network is configured to manage authentication transparently.
    The issue can be caused by many factors and please check one by one.
    Did you enter the username and password for three times and got blank page or got some error? If you got some error, please provide the error information.
    you can delete the specific Authorization Types inside rsreportserver.config  file, open path:” \Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\rsreportserver.config”. 
    Search the file for the “AuthenticationTypes” section. Remove RSWindowsNegotiate and RSWindoeBasic to ensure only “RSWindowsNTLM” is specified in the file rsreportserver.config file.
    Before do any modification, back up the files and remember to restart the ReportServer instance in the RSCM after the modification.
    If step1 doesn’t work ,please also do the trusted Site Setting in the Browser, article with details steps for your reference:
    http://technet.microsoft.com/en-us/library/bb630430.aspx 
    Please check the Report Manager's authentication mode.Have a look in the Report Manager's web.config file to check if you can find below information under the <system.web> (Path is “C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting
    Services\ReportManager\Web.config ” ).
    authentication mode="Windows"
    identity impersonate="True"
    Similar threads for your reference:
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/23c5daa0-3232-4e8c-89c9-4526960c9d14/ssrs-2008-credentials-login-prompt?forum=sqlreportingservices
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/0778e2ca-0fb1-4b5c-996c-6e327b5e1473/user-logon-credentials-for-ssrs-web-server-setup?forum=sqlreportingservices
    Please tried to provide us more details information, if the problem still exists:
    Did you login in the report manager locally or remotely via Browser and which URL you are using to login the Report manager?
    Did you modified some configuration file before and what did you modified?
    Did your windows account have the right permission to access the report manager?
    Any problem, please feel free to ask.
    Regards
    Vicky Liu

  • Use rptproj SSRS for SQL Server 2008R2 in VS 2010 (and/or VS 2012 better(

    In my company, I use VS 2008 and SQLServer 2008R2, and I have rptproj projects in VS 2008.
    The rptproj project has several rdl files.
    I would like use VS 2010 or VS 2012 with SSRS and SQLServer 2008R2.
    SSDT, which was introduced with SQL Server 2012. I suggest not possible migration rpt projects in VS 2008 to VS 2010 / VS 2012
    Any alternative solution to do it ?
    I have seen, but I'm confused it
    http://stackoverflow.com/questions/12503976/how-to-edit-ssrs-2008r2-reports-in-visual-studio-2012/16112721#16112721
    Iko says
    You can now use Visual Studio 2010 to edit .rtproj report projects and .rdl reports.
    You need VS10 SP1, then install the Data Tools for VS10, followed by the installation of SQL Server Express 2012 with Reporting Services and Data Tools.
    Reference: http://stackoverflow.com/a/14599850/206730
    But I'm confused about it.
    www.kiquenet.com/profesional

    Hi Kiquenet,
    According to your description, you installed VS 2008 and SQL Server 2008 R2, and create Reporting Services projects. Now you want to use VS 2010 or VS 2012 to open and manage the reports.
    SQL Server Data Tools - Business Intelligence for Visual Studio 2012 supports versions of SQL Server 2012 or lower, we can directly download Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2012 from
    https://www.microsoft.com/en-us/download/details.aspx?id=36843, then select SQL Server Data Tools - Business Intelligence for Visual Studio 2012 and SQL Client Connectivity SDK as
    new shard features to install.
    We can open the projects in both Visual Studio 2012 and Visual Studio 2010. For local mode only (that is, when not connected to SQL Server), we won’t get the design-time experience for controls that are associated with the viewer in Visual Studio 2008, but
    the project will function correctly at runtime. If we add a feature that’s specific to Visual Studio 2012, the report schema is upgraded automatically and you can no longer open the project in Visual Studio 2008.
    If you have any more questions, please feel free to ask.
    Thanks,
    Wendy Fu
    Wendy Fu
    TechNet Community Support

  • Use SIA service account for SQL Server reporting connections (BIP4.1)

    Is it possible to use the SIA service account as a proxy for a SQL Server connection using OLE DB? This way, anytime a report was refreshed, the SIA service account would be used when authenticating to the reporting database? This is a common pattern in software development to minimize database maintenance (when there is sufficient security being enforced at the application layer - BOBJ provides this).
    This would make SQL Server database security management very easy for the DBAs (just add the BOBJ service account to the database and assign dbreader).
    I would think this would be an option, but a Relational Connection only provides the following 3 Authentication modes when using the IDT to create and publish a Relational Connection (OLEDB/MSSQL):
    Use BusinessObjects credential mapping
    This takes the username and password from the "Database Credentials" section of the BusinessObjects User object for the user in the current session. It passes the info as hard-coded SQL authentication.
    Use single sign-on when refreshing reports at view time
    This is ONLY for end-to-end single-sign-on (as the error message in the next paragraph specifies) and uses the Windows AD credentials for the user in the current session. It is this method of authentication that I'd like to use, i.e. Windows Integrated Security, but I'd like to have the SIA account act as the account that makes the connection, not end-to-end.
    Use specified username and password
    This is for hard-coding usernames and passwords (only SQL authentication in OLE DB).
    I've tried leaving the "Cache security context" option OFF in Windows AD Authentication settings, hoping it would default to using the service account for authentication to the database... to no avail. It fails during tests in the IDT with the message:
    "Single Sign-On failed in the CMS. Please contact your system administrator for details. : The authentication provider (secWinAD) associated with this logon session does not have inter-process Single Sign-On enabled. Contact your system administrator for details. (FWB 00019)"
    Alternatively, a SQL user could be hard-coded into the connection (same simple maintenance on the DBA side), but we'd really like to rely on Windows Integrated Security if possible!
    Is there a way?
    Any help is greatly appreciated!
    David

    Hey David,
    Did you ever solve this? We get the same SSO error when indexing information spaces in Explorer.
    Thanks,
    Brandon

  • I am trying to update CU3 on SQL Server 2008R2 SP2 on a cluster passive server by rollipatch upgrade i am getting the below said error

    2014-03-08 13:28:51 SQLEngine: : File versions : ['D:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\SQSRVRES.DLL':2009.2009.4266.0], ['C:\Windows\system32\SQSRVRES.DLL':2009.2009.4266.0].
    2014-03-08 13:28:51 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-03-08 13:28:51 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls
    2014-03-08 13:28:51 Slp: Sco: Attempting to get registry value C:\Windows\system32\SQSRVRES.DLL
    2014-03-08 13:28:51 SQLEngine: : Incrementing value for DLL C:\Windows\system32\SQSRVRES.DLL, current value = 6
    2014-03-08 13:28:51 Slp: Sco: Attempting to get registry value C:\Windows\system32\SQSRVRES.DLL
    2014-03-08 13:28:51 Slp: Sco: Attempting to set value C:\Windows\system32\SQSRVRES.DLL
    2014-03-08 13:28:51 Slp: SetValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls, Name = C:\Windows\system32\SQSRVRES.DLL
    2014-03-08 13:28:51 SQLEngine: : Leaving ConfigureSQLEngineResourceType
    2014-03-08 13:28:51 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-03-08 13:28:51 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\Setup
    2014-03-08 13:28:51 Slp: Sco: Attempting to get registry value PatchLevel
    2014-03-08 13:28:51 SQLEngine: --PerfmonRegistration: Checking whether to patch performance counters for service 'MSSQLSERVER'
    2014-03-08 13:28:51 SQLEngine: --PerfmonRegistration: Getting perfmon DLL name from key at 'System\CurrentControlSet\Services\MSSQLSERVER\Performance'
    2014-03-08 13:28:51 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-03-08 13:28:51 Slp: Sco: Attempting to open registry subkey System\CurrentControlSet\Services\MSSQLSERVER\Performance
    2014-03-08 13:28:51 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
    2014-03-08 13:28:51 Slp: The registry key System\CurrentControlSet\Services\MSSQLSERVER\Performance is missing.
    2014-03-08 13:28:51 Slp: The configuration failure category of current exception is ConfigurationFailure
    2014-03-08 13:28:51 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
    2014-03-08 13:28:51 Slp: Microsoft.SqlServer.Configuration.SqlEngine.MissingRegistryKeyException: The registry key System\CurrentControlSet\Services\MSSQLSERVER\Performance is missing.
    2014-03-08 13:28:51 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.Globals.GetSqlRegistryKeyHKLM(ServiceContainer context, String key, String machineName, Boolean createIfNotFound)
    2014-03-08 13:28:51 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.PerfmonRegistration.GetDLLNameFromRegistry()
    2014-03-08 13:28:51 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.PerfmonRegistration.NeedToPatch()
    2014-03-08 13:28:51 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.PatchPerfmonCounters(EffectiveProperties properties)
    2014-03-08 13:28:51 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.Patch(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
    2014-03-08 13:28:51 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
    2014-03-08 13:28:51 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
    2014-03-08 13:28:51 Slp: Exception: Microsoft.SqlServer.Configuration.SqlEngine.MissingRegistryKeyException.
    2014-03-08 13:28:51 Slp: Source: Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.
    2014-03-08 13:28:51 Slp: Message: The registry key System\CurrentControlSet\Services\MSSQLSERVER\Performance is missing..
    2014-03-08 13:28:52 Slp: Watson Bucket 1 
     Original Parameter Values 
    2014-03-08 13:28:52 Slp: Parameter 0 : SQL2008@RTM@KB2754552 
    2014-03-08 13:28:52 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.SqlEngine.Globals.GetSqlRegistryKeyHKLM 
    2014-03-08 13:28:52 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.SqlEngine.Globals.GetSqlRegistryKeyHKLM 
    2014-03-08 13:28:52 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.SqlEngine.MissingRegistryKeyException@1306@30 
    2014-03-08 13:28:52 Slp: Parameter 4 : Microsoft.SqlServer.Configuration.SqlEngine.MissingRegistryKeyException@1306@30 
    2014-03-08 13:28:52 Slp: Parameter 5 : SqlEngineConfigAction_patch_configrc 
    2014-03-08 13:28:52 Slp: Parameter 6 : PATCH@CONFIGRC@SQL_ENGINE_CORE_INST 
    2014-03-08 13:28:52 Slp: 
     Final Parameter Values 
    2014-03-08 13:28:52 Slp: Parameter 0 : SQL2008@RTM@KB2754552 
    2014-03-08 13:28:52 Slp: Parameter 1 : 0x4E0712AD 
    2014-03-08 13:28:52 Slp: Parameter 2 : 0x4E0712AD 
    2014-03-08 13:28:52 Slp: Parameter 3 : 0x2F2F19BE@1306@30 
    2014-03-08 13:28:52 Slp: Parameter 4 : 0x2F2F19BE@1306@30 
    2014-03-08 13:28:52 Slp: Parameter 5 : SqlEngineConfigAction_patch_configrc 
    2014-03-08 13:28:52 Slp: Parameter 6 : 0x94D05575 
    Sangamesh ms

    Hi,
    Backup system\CurrentControlSet\Services\MSSQLSERVER\ first.
    For loading the performance counter, we need a perf-<instancename>sqlctr.ini file, a sqlctr.h file matching the .ini file, and the
    registry key under System\CurrentControlSet\Services\MSSQLSERVER\Performance.
    According the description, I understand that it is missing the correct perf-<instancename>sqlctr.ini and the
    registry in your environment.
    I suggest you manually add the registry key values under the
    System\CurrentControlSet\Services\MSSQLSERVER\Performance with referring the value of registry on other working machine. Also I copy the perf-<instancename>sqlctr.ini file from other working
    machine as they are both SQL Server 2008 R2.  Then, restart the server.
    You can reload the system performance counter by lodctr /R and lodctr /T:MSSQLSERVER to set the SQL Server performance counter service as trusted.
    Lodctr
    http://technet.microsoft.com/en-us/library/hh875560.aspx
    Thanks.
    Tracy Cai
    TechNet Community Support

  • SSMS for SQL Server 2012 Express on Windows Embedded 8 Standard

    Hello,
    I have installed SQL Server 2012 Express with Advanced Tools (SQLEXPRADV_x64_ENU.exe, downloaded from MS website) on Windows Embedded 8 Standard 64-bit. But, when I try to find SQL Server Management Studio, I realized it's not installed (same installation
    package works fine on my Windows 8.1 Pro 64-bit laptop, where SSMS gets installed). How do I fix this? And any other ways for trouble-shooting DBs on Windows Embedded 8 Standard?
    Thanks,
    Jay

    Below is the content of a summary file for the installation. BTW, I also try to find its ConfigurationFile.ini file for future installation on other computers, but it's not in the folder specified in the summary file either (see below).
    Thanks.
    Overall summary:
      Final result:                  Passed
      Exit code (Decimal):           0
      Start time:                    2014-04-15 13:57:59
      End time:                      2014-04-15 14:13:29
      Requested action:              Install
    Machine Properties:
      Machine name:                  AIMB-584
      Machine processor count:       4
      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 Service Pack 1
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      SPLevel:                       0
      Installation location:         c:\e089c9dde791653620\x64\setup\
      Installation edition:          Express
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Disabled
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    true
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, RS, BIDS, BOL, SSMS, SNAC_SDK, LOCALDB
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SQLEXPRESS
      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:                    SQLEXPRESS
      INSTANCENAME:                  SQLEXPRESS
      ISSVCACCOUNT:                  NT AUTHORITY\Network Service
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  NT Service\ReportServer$SQLEXPRESS
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           AIMB-584\User
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140415_135512\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Basic
      Status:                        Passed
      Feature:                       SQL Server Data Tools
      Status:                        Passed
      Feature:                       Reporting Services - Native
      Status:                        Passed
      Feature:                       Database Engine Services
      Status:                        Passed
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Passed
      Feature:                       SQL Server Replication
      Status:                        Passed
      Feature:                       SQL Browser
      Status:                        Passed
      Feature:                       Documentation Components
      Status:                        Passed
      Feature:                       SQL Writer
      Status:                        Passed
      Feature:                       LocalDB
      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\20140415_135512\SystemConfigurationCheck_Report.htm

  • Installation Error for SQL Server 2008 R2 on windows vista

    2014-09-20 07:49:26 Slp: ----------------------------------------
    2014-09-20 07:49:26 Slp: Setting: TIMESTAMP
    2014-09-20 07:49:26 Slp: Value specified: 20140920_074907
    2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
    2014-09-20 07:49:26 Slp: ----------------------------------------
    2014-09-20 07:49:26 Slp: Setting: LOGMARKER
    2014-09-20 07:49:26 Slp: Value specified: _ComponentUpdate
    2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
    2014-09-20 07:49:26 Slp: ----------------------------------------
    2014-09-20 07:49:26 Slp: Setting: INSTALLMEDIAPATH
    2014-09-20 07:49:26 Slp: Value specified: C:\Downloaded\SQL Server 2008\x86\setup\
    2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
    2014-09-20 07:49:26 Slp: ----------------------------------------
    2014-09-20 07:49:26 Slp: Setting: MEDIALAYOUT
    2014-09-20 07:49:26 Slp: Value specified: Full
    2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
    2014-09-20 07:49:26 Slp: ----------------------------------------
    2014-09-20 07:49:26 Slp: Completed Action: ProcessChainerCommandLineArguments, returned True
    2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:26 Slp: Running Action: ProcessMediaChainerConfigFileArguments
    2014-09-20 07:49:26 Slp: Completed Action: ProcessMediaChainerConfigFileArguments, returned True
    2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:26 Slp: Running Action: ProcessChainerConfigFileArguments
    2014-09-20 07:49:26 Slp: Completed Action: ProcessChainerConfigFileArguments, returned True
    2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:26 Slp: Running Action: ProcessSlipstreamParameters
    2014-09-20 07:49:26 Slp: Completed Action: ProcessSlipstreamParameters, returned True
    2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:26 Slp: Skipping Action: SetRoleAndUIModeForExpressMedia
    2014-09-20 07:49:26 Slp: Action is being skipped due to the following restrictions: 
    2014-09-20 07:49:26 Slp: Condition "IsMediaExpress" did not pass as it returned false and true was expected.
    2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:26 Slp: Running Action: ValidateChainerSetting
    2014-09-20 07:49:26 Slp: -- PidPublicConfigObject : ValidateSettings is normalizing input pid=[PID value hidden]
    2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : NormalizePid found null or empty pid
    2014-09-20 07:49:26 Slp: -- PidPublicConfigObject : ValidateSettings proceeding with normalized pid=[PID value hidden]
    2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : Initialize is initializing using input pid=[PID value hidden]
    2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : NormalizePid found null or empty pid
    2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : Initialize proceeding with normalized pid=[PID value hidden]
    2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : Initialize called ValidatePid, output is pid=[PID value hidden] validateSuccess=True output editionId=EVAL(0x2467BCA1)
    2014-09-20 07:49:27 Slp: -- PidPublicConfigObject : ValidateSettings initialized private object, result is initializeResult=Success
    2014-09-20 07:49:27 Slp: Completed Action: ValidateChainerSetting, returned True
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: ProcessFeatureCommandLineArguments
    2014-09-20 07:49:27 Slp: ----------------------------------------
    2014-09-20 07:49:27 Slp: Completed Action: ProcessFeatureCommandLineArguments, returned True
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: ProcessMediaFeatureConfigFileArguments
    2014-09-20 07:49:27 Slp: Completed Action: ProcessMediaFeatureConfigFileArguments, returned True
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: ProcessFeatureConfigFileArguments
    2014-09-20 07:49:27 Slp: Completed Action: ProcessFeatureConfigFileArguments, returned True
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: StartSqmSession
    2014-09-20 07:49:27 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-09-20 07:49:27 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
    2014-09-20 07:49:27 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
    2014-09-20 07:49:27 Slp: Completed Action: StartSqmSession, returned True
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: ValidateSettingsAgainstScenario
    2014-09-20 07:49:27 Slp: Scenario: ComponentUpdate
    2014-09-20 07:49:27 Slp: Completed Action: ValidateSettingsAgainstScenario, returned True
    2014-09-20 07:49:27 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: SetComponentUpdateScenarioFlags
    2014-09-20 07:49:27 Slp: Completed Action: SetComponentUpdateScenarioFlags, returned True
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: ExecuteInitWorkflow
    2014-09-20 07:49:27 Slp: Workflow to execute: 'INITIALIZATION'
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: InitializeMsiExtension
    2014-09-20 07:49:29 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-09-20 07:49:29 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100\Bootstrap
    2014-09-20 07:49:29 Slp: Completed Action: InitializeMsiExtension, returned True
    2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:29 Slp: Skipping Action: InitializeConfigAction
    2014-09-20 07:49:29 Slp: Action is being skipped due to the following restrictions: 
    2014-09-20 07:49:29 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableExternalMsiConfiguration set" did not pass as it returned false and true was expected.
    2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:29 Slp: Skipping Action: RunDiscoveryAction
    2014-09-20 07:49:29 Slp: Action is being skipped due to the following restrictions: 
    2014-09-20 07:49:29 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableDiscoverableProducts set" did not pass as it returned false and true was expected.
    2014-09-20 07:49:29 Slp: Completed Action: ExecuteInitWorkflow, returned True
    2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:29 Slp: Running Action: ExecuteStartUiWorkflow
    2014-09-20 07:49:29 Slp: Workflow to execute: 'STARTUI'
    2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:29 Slp: Running Action: InstallWizard
    2014-09-20 07:49:29 Slp: Start Action: ComponentUpdate
    2014-09-20 07:49:29 Slp: Configuration file: C:\Downloaded\SQL Server 2008\x86\configuration.uicfg
    2014-09-20 07:49:30 Slp: Adding registration information 'ShowWizard' for type 'Microsoft.SqlServer.Management.ActionHandlerInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'InstallWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'InstallClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'AddNode' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'RemoveNode' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'PrepareClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'CompleteClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'UninstallWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'UpgradeWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'ComponentUpdate' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'RepairWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'RunRulesUI' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'EditionUpgradeWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'PatchWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'RemovePatchWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'PrepareImageWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'CompleteImageWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: -- SkuPublicConfigObject : Calling SkuPublicConfigObject.Calculate.
    2014-09-20 07:49:31 Slp: Completed Action: InstallWizard, returned True
    2014-09-20 07:49:31 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:31 Slp: Running Action: GatherUserSettings
    2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings is normalizing input pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid is normalizing input pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid added dashes to pid, output pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings proceeding with normalized pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Initialize is initializing using input pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid is normalizing input pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Initialize proceeding with normalized pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Read lcid 1033 from CultureInfo
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Pid validation of input pid '[PID value hidden]' succeeded, resulting edition is 'DATA_CENTER' channel 'OEM'
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Initialize called ValidatePid, output is pid=[PID value hidden] validateSuccess=True output editionId=DATA_CENTER(0xC5AA9665)
    2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings initialized private object, result is initializeResult=Success
    2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings is normalizing input pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid is normalizing input pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid added dashes to pid, output pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings proceeding with normalized pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings found pid=[PID value hidden] is already validated and initialized.
    2014-09-20 07:50:22 Slp: License file: C:\Downloaded\SQL Server 2008\1033_ENU_LP\x86\1033\License_DC_OEM.rtf
    2014-09-20 07:50:25 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-09-20 07:50:25 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
    2014-09-20 07:50:25 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
    2014-09-20 07:50:25 Slp: License file: C:\Downloaded\SQL Server 2008\1033_ENU_LP\x86\1033\License_DC_OEM.rtf
    2014-09-20 07:50:25 Slp: Completed Action: GatherUserSettings, returned True
    2014-09-20 07:50:25 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:25 Slp: Running Action: RegisterRetryHandler
    2014-09-20 07:50:25 Slp: Completed Action: RegisterRetryHandler, returned True
    2014-09-20 07:50:25 Slp: Completed Action: ExecuteStartUiWorkflow, returned True
    2014-09-20 07:50:25 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:25 Slp: Running Action: NotifyProgressCountDisplay
    2014-09-20 07:50:26 Slp: Completed Action: NotifyProgressCountDisplay, returned True
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Running Action: ExecuteCalculateScenarioWorkflow
    2014-09-20 07:50:26 Slp: Workflow to execute: 'CALCULATESCENARIO'
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Running Action: ClearCalculatedState
    2014-09-20 07:50:26 Slp: Completed Action: ClearCalculatedState, returned True
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Skipping Action: SetUninstallEnableInstallMatchingByInstanceId
    2014-09-20 07:50:26 Slp: Action is being skipped due to the following restrictions: 
    2014-09-20 07:50:26 Slp: Condition "Is the user's scenario set to Uninstall" did not pass as it returned false and true was expected.
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Skipping property ArgInstanceName of class: SetFeatureInstallStateAction
    2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s): 
    2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableDiscoverableProducts set" did not pass as it returned false and true was expected.
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Skipping property ArgSqlInstanceId of class: SetFeatureInstallStateAction
    2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s): 
    2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableInstallMatchingByInstanceId set" did not pass as it returned false and true was expected.
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Skipping property ArgASInstanceId of class: SetFeatureInstallStateAction
    2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s): 
    2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableInstallMatchingByInstanceId set" did not pass as it returned false and true was expected.
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Skipping property ArgRSInstanceId of class: SetFeatureInstallStateAction
    2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s): 
    2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableInstallMatchingByInstanceId set" did not pass as it returned false and true was expected.
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Running Action: SetFeatureInstallStateAction
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_Cpu32: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_fulltext_Cpu32: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_Cpu32: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_Cpu32: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_spi_Cpu32: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_rs_Cpu32: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_rs_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_rs_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_rs_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_Cpu32: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_Cpu32: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_bids_Cpu32: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_bids_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_bids_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_Cpu32: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_Cpu32: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:29 Slp: Error: Action "Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction" threw an exception during execution.
    2014-09-20 07:50:29 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Value cannot be null.
    2014-09-20 07:50:29 Slp: Parameter name: productVersion ---> System.ArgumentNullException: Value cannot be null.
    2014-09-20 07:50:29 Slp: Parameter name: productVersion
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion(String value)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallPropertyByProductCode(PackageInstallProperty pkg, String prodCode)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallProperty(PackageInstallProperty pkg)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.ExecuteAction(String actionId)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
    2014-09-20 07:50:29 Slp:    --- End of inner exception stack trace ---
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
    2014-09-20 07:50:29 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
    2014-09-20 07:50:29 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Value cannot be null.
    2014-09-20 07:50:29 Slp: Parameter name: productVersion ---> System.ArgumentNullException: Value cannot be null.
    2014-09-20 07:50:29 Slp: Parameter name: productVersion
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion(String value)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallPropertyByProductCode(PackageInstallProperty pkg, String prodCode)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallProperty(PackageInstallProperty pkg)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.ExecuteAction(String actionId)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
    2014-09-20 07:50:29 Slp:    --- End of inner exception stack trace ---
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2014-09-20 07:50:33 Slp: Received request to add the following file to Watson reporting: C:\Users\Kimi Raikkonen\AppData\Local\Temp\tmpB4ED.tmp
    2014-09-20 07:50:33 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2014-09-20 07:50:33 Slp: Inner exceptions are being indented
    2014-09-20 07:50:33 Slp: 
    2014-09-20 07:50:33 Slp: Exception type: System.ArgumentNullException
    2014-09-20 07:50:33 Slp:     Message: 
    2014-09-20 07:50:33 Slp:         Value cannot be null.
    2014-09-20 07:50:33 Slp:         Parameter name: productVersion
    2014-09-20 07:50:33 Slp:     Stack: 
    2014-09-20 07:50:33 Slp:         at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion(String value)
    2014-09-20 07:50:33 Slp:         at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallPropertyByProductCode(PackageInstallProperty pkg, String prodCode)
    2014-09-20 07:50:33 Slp:         at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallProperty(PackageInstallProperty pkg)
    2014-09-20 07:50:33 Slp:         at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.ExecuteAction(String actionId)
    2014-09-20 07:50:33 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    2014-09-20 07:50:33 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
    2014-09-20 07:50:43 Slp: Watson Bucket 1 
     Original Parameter Values 
    2014-09-20 07:50:43 Slp: Parameter 0 : SQL Server 2008 R2@RTM@ 
    2014-09-20 07:50:43 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion 
    2014-09-20 07:50:43 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion 
    2014-09-20 07:50:43 Slp: Parameter 3 : System.ArgumentNullException@-2147467261 
    2014-09-20 07:50:43 Slp: Parameter 4 : System.ArgumentNullException@-2147467261 
    2014-09-20 07:50:43 Slp: Parameter 5 : SetFeatureInstallStateAction 
    2014-09-20 07:50:43 Slp: 
     Final Parameter Values 
    2014-09-20 07:50:43 Slp: Parameter 0 : SQL Server 2008 R2@RTM@ 
    2014-09-20 07:50:43 Slp: Parameter 1 : 0x2AA348CC 
    2014-09-20 07:50:43 Slp: Parameter 2 : 0x2AA348CC 
    2014-09-20 07:50:43 Slp: Parameter 3 : 0xF15156D0 
    2014-09-20 07:50:43 Slp: Parameter 4 : 0xF15156D0 
    2014-09-20 07:50:43 Slp: Parameter 5 : SetFeatureInstallStateAction 
    2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_, Win32 error
    2
    2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_, Win32 error 2
    2014-09-20 07:50:44 Slp: Value cannot be null.
    Parameter name: productVersion
    2014-09-20 07:50:44 Slp: Watson bucket for exception based failure has been created
    2014-09-20 07:50:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey 
    2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
    2014-09-20 07:50:44 Slp: Sco: Attempting to get registry value DW0200
    2014-09-20 07:50:46 Slp: Submitted 1 of 1 failures to the Watson data repository
    2014-09-20 07:50:46 Slp: 
    2014-09-20 07:50:46 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:46 Slp: 
    2014-09-20 07:50:46 Slp: Error result: 1269611253
    2014-09-20 07:50:46 Slp: Result facility code: 940
    2014-09-20 07:50:46 Slp: Result error code: 47861

    2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_, Win32
    error 2
    2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_, Win32 error 2
    2014-09-20 07:50:44 Slp: Value cannot be null.
    Parameter name: productVersion
    2014-09-20 07:50:44 Slp: Watson bucket for exception based failure has been created
    2014-09-20 07:50:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey 
    2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
    2014-09-20 07:50:44 Slp: Sco: Attempting to get registry value DW0200
    2014-09-20 07:50:46 Slp: Submitted 1 of 1 failures to the Watson data repository
    2014-09-20 07:50:46 Slp: 
    2014-09-20 07:50:46 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:46 Slp: 
    2014-09-20 07:50:46 Slp: Error result: 1269611253
    2014-09-20 07:50:46 Slp: Result facility code: 940
    2014-09-20 07:50:46 Slp: Result error code: 47861
    Hi,
    For above error the error code is 2 which means system cannot find the file specified. It is saying it is unable to write at location which means SQL server account does not have access to
    C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    You can manually go to the location and add required rights may be installable is corrupt
    Now did you ran SQL server setup as administrator. Always right click on setup.exe file and select run as administrator.
    Please make sure you disable antivirus running on machine. Also if you have any registry scanner software which scans registry remove it as well.
    Below thread might be helpful
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/d425791a-9a7c-4c16-9e93-d348ecde3a3f/sql-server-2008-r2-install-fails-on-win-2008-r2-x64-std-server-with-workflowxmltext-msg-error-help?forum=sqlsetupandupgrade
    Can you also post summary.txt file
    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

Maybe you are looking for