Repeated Errors in SQL Server log file

I have hundreds of these errors saying 'Login failed for user 'Reporting' The user is not associated with a trusted SQL Server connection [CLIENT: ip address]
The ip address is that of the server that sql server is installed on.
Looking in my log file, all looks good until I get to Service Broker manager has started, then I get Error: 18452, Severity: 14 State: 1 then these two lines repeat about every minute, for the last 3 days!
I think I must have just missed a tick box somewhere, but where?
I have been into one of the databases, and input  and checked data, both via an application I wrote and SQL Server Management Studio.
I am also having trouble connecting using my application to connect to the database, I can only connect if I use a Windows administrator account (this SQL Server 2005 running on a Windows 2003 Server, with the app on PC running Windows 2000)

Hello Graham,
did you find any solutions for that problem? I'm discovering a similar problem. The state of my error message is 5. According to the following source http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx this means the user is not known. This is correct. Neither the SQL-Server nor the Windows system has such a userid.
The faulty user name is 'Reporting'. What is that user used for? I have set up other SQL Server 2005 servers but was never asked for such a name.
Greetings,
Frank

Similar Messages

  • How to Open Or read SQL Server log file .ldf

    Hi all,
    How to Open Or read SQL Server log file .ldf
    When ever we create database from sql server, it's create two file. (1) .mdf (2) .ldf.
    I want to see what's available inside the .ldf file.
    Thanks,
    Ashok

    I am not too sure but may be the below two undocumented commands might yield the desired result.
    DBCC Log
    Fn_dblog function
    Refer these links for more info,
    http://www.mssqlcity.com/Articles/Undoc/SQL2000UndocDBCC.htm
    http://blogs.sqlserver.org.au/blogs/greg_linwood/archive/2004/11/27/37.aspx
    http://searchsqlserver.techtarget.com/tip/0,289483,sid87_gci1173464,00.html
    Some 3rd party tools like Log Explorer can do the job for you.
    http://www.lumigent.com/products/le_sql.html
    - Deepak

  • Crystal Report 2008 results "Password did not match error" in SQL Server Log

    Hi,
    I am trying to develop some crystal reports using Crystal Report 2008 SP4 to connect to SQL server 2008 through RDO (ODBC). My problem is that anytime Crystal Report is trying to establish a connection with SQL Server, first it tries to connect with the wrong password and results the following error message in SQL Server log:
    Login failed for user 'peyman'. Reason: Password did not match that for the login provided. [CLIENT: 192.168.2.198]
    The login name 'peyman' is the right one as I have quoted the same in setting up ODBC System DSN using "SQL Server Native Client 10". But somehow Crystal Report is taking its chance and trying to connect before prompting me for the password. After this error logged to SQL server side, I can see Crystal Report pops up the prompt to enter DSN password. After supplying password to this prompt, Crystal Report works fine and pulls the data and renders the report without having any more incorrect password error logged to SQL Server.
    The attached file shows the step I am taking to regenerate the issue. I need this to be fixed as anytime uses any of these reports and tries to render it with crystal runtime engine the same error message raises in SQL Server side and logged in the log file.
    Thanks,

    Hi Peyman,
    This is the way it should work, In CR designer when you open the report it does nothing. As soon as you hit the Refresh button then CR tries to use the connection saved with the report. It assumes what is saved with the report is a valid server and connection info. CR simply tries to verify the server is still active.
    If you don't want it to fail in CRD then before opening any report Click the File, Log on Database option and connect. Now when refreshing reports it won't log the failed.
    In the SDK it does the same thing, it assumes the Server info is the same and does try to connect to verify the Server does exist. It only takes a few milli-seconds to do this
    To stop this from happening set the log on info first then it won't log the attempt to connect, it's checking to see if Trusted is allowed.
    TIMESTAMP    THREAD_ID    FILENAME    LINE_NUMBER    LOGGED_DATA    LEVEL
    2014-6-2 8:30:11.439    57320    .\QESession.cpp    444    Set Product View Locale: 4105    20
    2014-6-2 8:30:11.439    57320    .\QESession.cpp    478    Set Preferred View Locale: 4105    20
    2014-6-2 8:30:11.439    57320    .\QESession.cpp    500    Set Process Locale: 4105    20
    2014-6-2 8:30:11.440    57320    .\qecommon.cpp    117    This property is currently in a read-only state and cannot be modified. File Name: ".\QEProperty.cpp". Line: 217    1
    2014-6-2 8:30:11.967    57208    .\QESession.cpp    444    Set Product View Locale: 4105    20
    2014-6-2 8:30:11.967    57208    .\QESession.cpp    478    Set Preferred View Locale: 4105    20
    2014-6-2 8:30:11.967    57208    .\QESession.cpp    500    Set Process Locale: 4105    20
    2014-6-2 8:30:11.968    57208    .\qecommon.cpp    117    This property is currently in a read-only state and cannot be modified. File Name: ".\QEProperty.cpp". Line: 217    1
    2014-6-2 8:30:11.999    57208    .\QESession.cpp    444    Set Product View Locale: 1033    20
    2014-6-2 8:30:12.4    57320    .\qecommon.cpp    117    This value is write-only. File Name: ".\QEProperty.cpp". Line: 145    1
    2014-6-2 8:30:56.278    57208    .\odbcapi.cpp    301    Beginning COdbcapi::DriverConnect    20
    2014-6-2 8:30:56.342    57208    .\odbcapi.cpp    335    Ending COdbcapi::DriverConnect    20
    2014-6-2 8:30:56.342    57208    .\connect.cpp    2170    SQLDriverConnect succeeded: DSN = 192.168.13.172, User ID = sa, Password = ********    10
    2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
    2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 854    1
    2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
    2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
    2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 854    1
    2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
    2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 854    1
    2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 916    1
    2014-6-2 8:30:56.348    57208    .\QERowset.cpp    1184    Beginning CQERowset::readFirstRecord    20
    2014-6-2 8:30:56.348    57208    .\QERowset.cpp    2149    Beginning CQERowset::restart    20
    2014-6-2 8:30:56.348    57208    .\QERowset.cpp    2370    Beginning CQERowset::execute    20
    2014-6-2 8:30:56.353    57208    .\DbQueryBuilder.cpp    514    Query Targets: sqlncli10, ODBC3SQLServer    10
    2014-6-2 8:30:56.353    57208    .\DbQueryBuilder.cpp    525    Successfully built query:    SELECT "Orders"."Customer ID", "Orders"."Employee ID"   FROM   "xtreme"."dbo"."Orders" "Orders"    10
    2014-6-2 8:30:56.353    57208    .\odbcapi.cpp    875    Beginning COdbcapi::ExecDirect    20
    2014-6-2 8:30:56.354    57208    .\odbcapi.cpp    884    Finishing COdbcapi::ExecDirect    20
    2014-6-2 8:30:56.354    57208    .\rowset.cpp    220    SQLExecDirect succeeded:  SELECT "Orders"."Customer ID", "Orders"."Employee ID" FROM   "xtreme"."dbo"."Orders" "Orders"    10
    2014-6-2 8:30:56.354    57208    .\QERowset.cpp    2814    bindToField succeeded: Orders.Customer ID is using client buffer    10
    2014-6-2 8:30:56.354    57208    .\QERowset.cpp    2814    bindToField succeeded: Orders.Employee ID is using client buffer    10
    Notice it doesn't try to connect first if I set the log on info first using code.
    So nothing we can do to stop SQL server from logging this info. Check with the DBA, possibly they can "filter" out the application attempts to connect or change your work flow in the app.
    If you have a Preview Button to view the report then simply add your Database log on info prompt there if Connectioninfo.Trusted is not true:
    mainSecureDB = rpt.Database.Tables[tableIndex].LogOnInfo.ConnectionInfo.IntegratedSecurity;
    if mainSecureDB = false then prompt the user for log on info and set accordingly, if it is true the it should not fail when it connects.
    This is simply a matter of changing your App work flow...
    Thanks
    Don

  • SQL Server log file

    We are facing one issue can anyone please help me out.
    Logs are getting full in below path . Can we remove the logs ? is it archive logs ?
    Path : H:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA

    If T-Log backups are configured then the log automatically get truncated once backup is compelted. If you dont have backups configured and you dont want to save the transactions you can manually truncate it
    Hi,
    From SQL Server 2008 onwards truncate_only is removed, it is replaced by
    backup log db_name to disk='Null'
    Also if your log is growing AND YOU DONT NEED POINT IN TIME RECOVERY switch recovery model to simple it will force checkpoint and logs will get truncated( If transaction does not requires the log) . Avoid using backup log to null or truncate only.
    Swapna,
    >>Also if you dont want the transactions to be saved then you can set the recovery model and Simple
    This is incorrect language used saving/committing transaction does not depends on recovery model. Recovery model only controls logging and recovery. if transaction is committed it will be present in database no matter what recovery model you use.
    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 Wiki Articles

  • Connection Error in Presentation Server log file - Socket:524

    Hi All,
    Earlier I had issues with starting presentation server , so i installed OBIEE again.
    I started all the services and Started oc4j.
    And i'm able to open the Administrator tool. But get error in IE while opening presentation server.
    When i opened the saw0log file from this location "C:\OracleBIData\web\log" ,this is the error i see
    Type: Error
    Severity: 42
    Time: Thu Apr 08 11:08:06 2010
    File: project/webcomm/socket.cpp Line: 892
    Properties: ThreadID-1736
    Location:
         saw.rpc.client.impl.verify
         saw.rpc.client.impl.initFixedRPC
         saw.rpc.client.endpoint.noncluster.initFixedLenRPC
         saw.rpc.ping.send
         saw.threads
    An error occurred during execution of "connect". No connection could be made because the target machine actively refused it.
    [Socket:524]
    Type: Error
    Severity: 42
    Time: Thu Apr 08 11:10:08 2010
    File: project/webcomm/socket.cpp Line: 892
    Properties: ThreadID-1736
    Location:
         saw.rpc.client.impl.verify
         saw.rpc.client.impl.initFixedRPC
         saw.rpc.client.endpoint.noncluster.initFixedLenRPC
         saw.rpc.ping.send
         saw.threads
    An error occurred during execution of "connect". No connection could be made because the target machine actively refused it.
    [Socket:524]
    Type: Error
    Severity: 42
    Time: Thu Apr 08 11:12:10 2010
    File: project/webcomm/socket.cpp Line: 892
    Properties: ThreadID-1736
    Location:
         saw.rpc.client.impl.verify
         saw.rpc.client.impl.initFixedRPC
         saw.rpc.client.endpoint.noncluster.initFixedLenRPC
         saw.rpc.ping.send
         saw.threads
    An error occurred during execution of "connect". No connection could be made because the target machine actively refused it.
    [Socket:524]
    Please help me where to change the connection details.
    Thanks
    Mehaboob

    Step : 1: Check your NQSCONFIG.ini file and in Repository section should be like
    [ REPOSITORY ]
    Star = bise1.rpd, DEFAULT;
    or
    [ REPOSITORY ]
    bise1 = bise1.rpd, DEFAULT;
    Step : 2 : Open ODBC Data source Administration ->System DSN and then Select AnalyticsWeb - Oracle BI Server
    In Oracle BI Server LoginId and Password window you should check and enable the Change the default repository to
    Here the name should be Star or bise1 ( Refer step:1:)
    Click next and enable Change the default catalog to and select the Database (highlighted gray to blue color)
    Leave others are default.
    Note : whatever repository will be put under change Default repository section will be override by the DEFAULT settings in NQSCONFIG.ini .You can tick “Connect to Oracle BI Server to obtain default settings for the additional configuring”, so that RPD connection will be established as per the definition in .ini file after BI server restart.
    Plz award points, if it helpful,
    Thanks,
    Balaa...

  • SQL Server Logs

    Hi,
    I am getting an errors in SQL Server Logs.
    Its eating up all my space from C: Drive.
    now it says 0 bytes left.
    What could be an issue???
    Please help. its urgent.
    Regards, Kunjay Shah

    Hello,
    Meanwhile you can limit the error log size with the following instruction:
    USE
    [master];
    GO
    EXEC
    xp_instance_regwrite
    N'HKEY_LOCAL_MACHINE',
    N'Software\Microsoft\MSSQLServer\MSSQLServer',
    N'ErrorLogSizeInKb',
    REG_DWORD, 5120;
    GO
    For more information, please read the following article:
    http://support.microsoft.com/kb/2199578/en-us
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • System Center 2012 R2 install: SQL server Data file and log file

    This might be a dumb question, but I can't find the answer anywhere.  
    I'm installing a new instance of  System Center 2012 R2 on a new server, I'm stuck on the SQL Server data file section.  Everytime I put in a path, it says that tne path does not exist.  I'm I supposed to be creating some sort of SQL Server
    data file and log file before this installation, I didn't get this prompt when installing System Center 2012 SP1 or hen I upgraded from System Center 2012 SP1 to System Center 2012 R2
    My SQL is on a different server
    Thank you in advanced

    Have you reviewed the setup.log?
    On a side note, why would you put the database file on the same drive as the OS? That defeats the whole purpose of having a remote SQL Server. Why use a remote SQL Server in the first place.
    Jason | http://blog.configmgrftw.com

  • I see most recent file is called sql server log shipping work file

    What is "SQL server log shipping work file"?

    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/62a6556e-6655-4d19-9112-1788cf7bbcfc/wrk-file-in-logshipping-2005
    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

  • Repeatedly the same error in the omsca.log file during 11g installation

    Hi Experts,
    One of my customer is getting the below error in the OMSCA.log file:
    java.lang.Exception: CREATING_WEBTIER_INST_FAILED
         at oracle.sysman.omsca.adapter.wls.OMSWLSAdapter.adapterConfigWebTier(OMSWLSAdapter.java:1808)
         at oracle.sysman.omsca.framework.OMSGenericAdapter.configWebTier(OMSGenericAdapter.java:306)
    I have checked his setup and pre-reqs,all seems to be perfectly fine.
    Kindly let me some pointers related to this issue.
    SR:3-4090870221
    I have uploaded the log file here.
    Regards
    Sumani
    Edited by: 893642 on Oct 28, 2011 1:13 AM

    Here some screenshots, this error came back all few minutes!

  • Logical sql in log file.

    Can someone please tell me how to see the complete sql query in the log file. If I run the same query the sql is not being produced I looked in the server log file and also manage sessions log file. It just says all columns from 'Subject Area'. I want to see all the joins and filters as well. Even for repeated queries how can I see complete sql. I set my logging level to 2.

    http://lmgtfy.com/?q=obiee+disable+query+caching
    http://catb.org/esr/faqs/smart-questions.html#homework

  • 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

  • Overlapped I/O error installing SQL Server Express 2014 on Win 8.1

    Hi,
    I'm attempting to install SQL2014 on a SurfacePro3 running Win 8.1.  Despite much searching I've not found anything that gets me past this problem.
    I've tried:
    Uninstalling a update KB2918614 which was highlighted as a potential issue
    The login is the only account on the machine (not networked)
    Used "Run as Administrator"
    Even tried setting up a new User Account not linked to MS
    Run from the SETUP.EXE in the extracted files (with "Run As Admin")
    The Summary log is below:
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2068053019
      Start time:                    2014-12-03 10:40:32
      End time:                      2014-12-03 10:59:53
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for Adv_SSMS:        Use the following information to resolve the error, and then try the setup process again.
      Next step for Conn:            Use the following information to resolve the error, and then try the setup process again.
      Next step for SDK:             Use the following information to resolve the error, and then try the setup process again.
      Next step for BC:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SSMS:            Use the following information to resolve the error, and then try the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
      Next step for Browser:         Use the following information to resolve the error, and then try the setup process again.
      Next step for ComponentUpdate: Use the following information to resolve the error, and then try the setup process again.
    Machine Properties:
      Machine name:                  JASONSURFACE
      Machine processor count:       4
      OS version:                    Windows 8
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United Kingdom)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered  Configured
    Package properties:
      Description:                   Microsoft SQL Server 2014 
      ProductName:                   SQL Server 2014
      Type:                          RTM
      Version:                       12
      SPLevel:                       0
      Installation location:         C:\Temp\SQL2014\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, CONN, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             C:\MSSQL
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SQLEXPRESS2014
      INSTANCENAME:                  SQLEXPRESS2014
      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:                  <empty>
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  C:\MSSQL\BackUp
      SQLCOLLATION:                  Latin1_General_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS2014
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           JASONSURFACE\Jason, JasonSurface\Administrator, BUILTIN\Administrators, Jason, NT AUTHORITY\Local account, NT AUTHORITY\LOCAL SERVICE, NT AUTHORITY\NETWORK SERVICE, NT AUTHORITY\SERVICE, NT AUTHORITY\SYSTEM
      SQLTEMPDBDIR:                  C:\MSSQL\Temp
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  C:\MSSQL\Data
      SQLUSERDBLOGDIR:               C:\MSSQL\Logs
      SQMREPORTING:                  false
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      UpdateEnabled:                 true
      UpdateSource:                  MU
      USEMICROSOFTUPDATE:            false
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141203_104031\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft Visual Studio 2010 Redistributables
      Component error code:          997
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141203_104031\VC10Redist_Cpu64_1.log
      Error description:             Error 997.Overlapped I/O operation is in progress.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=vc_red.msi%40ProcessComponents%40997
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft Visual Studio 2010 Redistributables
      Component error code:          997
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141203_104031\VC10Redist_Cpu64_1.log
      Error description:             Error 997.Overlapped I/O operation is in progress.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=vc_red.msi%40ProcessComponents%40997
      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft Visual Studio 2010 Redistributables
      Component error code:          997
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141203_104031\VC10Redist_Cpu64_1.log
      Error description:             Error 997.Overlapped I/O operation is in progress.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=vc_red.msi%40ProcessComponents%40997
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft Visual Studio 2010 Redistributables
      Component error code:          997
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141203_104031\VC10Redist_Cpu64_1.log
      Error description:             Error 997.Overlapped I/O operation is in progress.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=vc_red.msi%40ProcessComponents%40997
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft Visual Studio 2010 Redistributables
      Component error code:          997
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141203_104031\VC10Redist_Cpu64_1.log
      Error description:             Error 997.Overlapped I/O operation is in progress.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=vc_red.msi%40ProcessComponents%40997
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft Visual Studio 2010 Redistributables
      Component error code:          997
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141203_104031\VC10Redist_Cpu64_1.log
      Error description:             Error 997.Overlapped I/O operation is in progress.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=vc_red.msi%40ProcessComponents%40997
      Feature:                       SQL Browser
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft Visual Studio 2010 Redistributables
      Component error code:          997
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141203_104031\VC10Redist_Cpu64_1.log
      Error description:             Error 997.Overlapped I/O operation is in progress.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=vc_red.msi%40ProcessComponents%40997
      Feature:                       SQL Writer
      Status:                        Passed
      Feature:                       SQL Client Connectivity
      Status:                        Passed
      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed
      Feature:                       Setup Support Files
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft Visual Studio 2010 Redistributables
      Component error code:          997
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141203_104031\VC10Redist_Cpu64_1.log
      Error description:             Error 997.Overlapped I/O operation is in progress.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=vc_red.msi%40ProcessComponents%40997
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141203_104031\SystemConfigurationCheck_Report.htm

    Sorry for late reply.  The VC++ download did not install as it 'requires X64' -looking at the top of the log it states that the OS is 'future X64'
    OS Version = 6.2.9200, Platform 2
    OS Description = Future OS - x64 
    OS Version Information 
    Environment details:
    CommandLine = c:\ccbfb742b64e9fa3860db0da73\Setup.exe 
    TimeZone = GMT Standard Time
    Initial LCID = 2057
    Environment details 
    SetupResources.dll missing from 2057 directory
    Entering Function: LocalizedData::CreateLocalizedData
    succeeded
    Entering Function: EngineData::CreateEngineData
    Using Simultaneous Download and Install mechanism
    succeeded
    MaintenanceMode determination: evaluating
    EnterMaintenanceModeIf
    Exists: evaluating
    Exists evaluated to false
    MaintenanceMode determination evaluates to 'not in maintenance mode'
    Operation Type:
    Operation: Installing
    Operation Type 
    Package details: Microsoft Visual C++
    2010 x64 Redistributable Setup
    Package Name = Microsoft Visual C++ 2010 x64 Redistributable Setup
    Package Version = 10.0.40219
    Package details 
    User Experience Data Collection Policy:
    User Experience Data Collection Policy: UserControlled
    User Experience Data Collection Policy 
    Entering Function: UiDataT<class
    ccmdlineswitches="">::CreateUiDataT</class>
    succeeded
    Global Block Checks: Checking for global
    blockers
    BlockIf: Microsoft Visual C++
    2010 Redistributable is not supported on this operating system.
    And: evaluating
    Equals: evaluating
    Equals evaluated to true
    GreaterThan: evaluating
    GreaterThan evaluated to false
    And evaluated to false
    BlockIf evaluated to false
    BlockIf: This setup program requires
    an x64 platform. It cannot be installed on this platform.
    And: evaluating
    Equals: evaluating
    Equals evaluated to true
    Not: evaluating
    Equals: evaluating
    Equals evaluated to true
    Not evaluated to false
    And evaluated to false
    BlockIf evaluated to false
    BlockIf: A newer version of Microsoft
    Visual C++ 2010 Redistributable has been detected on the machine.
    And: evaluating
    Equals: evaluating
    Equals evaluated to true
    LessThan: evaluating
    LessThan evaluated to false
    And evaluated to false
    BlockIf evaluated to false
    Global Block Checks no blocking conditions found
    Applicability for Installing: evaluating
    each item
    Determining state: of c:\ccbfb742b64e9fa3860db0da73\vc_red.cab
    Exists: evaluating
    Exists evaluated to false
    Determining state of c:\ccbfb742b64e9fa3860db0da73\vc_red.cab - available but not verified yet
    Determining state: of c:\ccbfb742b64e9fa3860db0da73\vc_red.msi
    Exists: evaluating
    Exists evaluated to false
    Determining state of c:\ccbfb742b64e9fa3860db0da73\vc_red.msi - available but not verified yet
    Determining state: of c:\ccbfb742b64e9fa3860db0da73\vc_red.msi
    Exists: evaluating
    Exists evaluated to false
    Determining state of c:\ccbfb742b64e9fa3860db0da73\vc_red.msi - authored action for this item is NoOp
    Determining state: of MSIServer
    Determining state of MSIServer - payload not required for this item to perform action.
    Exists: evaluating
    Exists evaluated to false
    Exists: evaluating
    Exists evaluated to false
    Applicability for Installing determination is complete
    Applicability Result Count:
    Number of applicable items: 3
    Applicability Result Count 
    Action: System Requirement Checks
    Action: Disk space check for items
    being downloaded
    Action complete
    Action: Enumerating incompatible processes
    Action complete
    Action: Enumerating incompatible services
    Action complete
    Action complete
    Action: Downloading and/or Verifying
    Items
    c:\ccbfb742b64e9fa3860db0da73\vc_red.cab:
    Verifying signature for vc_red.cab
    c:\ccbfb742b64e9fa3860db0da73\vc_red.cab Signature verified successfully for vc_red.cab
    c:\ccbfb742b64e9fa3860db0da73\vc_red.msi:
    Verifying signature for vc_red.msi
    c:\ccbfb742b64e9fa3860db0da73\vc_red.msi Signature verified successfully for vc_red.msi
    Action complete
    Exists: evaluating
    Exists evaluated to false
    Exists: evaluating
    Exists evaluated to false
    Action: Performing actions on all Items
    Action: Performing Action on MSI at
    c:\ccbfb742b64e9fa3860db0da73\vc_red.msi
    Returning IDOK. INSTALLMESSAGE_ERROR [Error 997.Overlapped I/O operation is in progress. ]
    MSI (c:\ccbfb742b64e9fa3860db0da73\vc_red.msi) Installation failed. Msi Log: Microsoft
    Visual C++ 2010 x64 Redistributable Setup_20141219_081422871-MSI_vc_red.msi.txt
    PerformOperation returned 1603 (translates to HRESULT = 0x80070643)
    Action complete
    OnFailureBehavior for this item is to Rollback.
    Action: Performing actions on all Items
    Action complete
    Action complete
    Final Result: Installation failed with error code: (0x80070643), "Fatal error during installation. " (Elapsed time: 0 00:00:05).

  • MOF Syntax Error Installing SQL Server 2014 Express

    I am trying to install SQL Server 2014 Express With Tools on a fully updated Win 8.1 system having already installed Visual Studio Community 2013 with Update 4. During the installation of SQL Server, I am getting a "MOF Syntax Error".
    I found this http://support.microsoft.com/kb/2387686 on the web but I can't see that that applies to me as I would have thought that any suggested fixes from this article would have been already installed
    or corrected in Win 8.1 or SQL Server 2014. Neither do I know what fix I should install anyway.
    An entry on this forum suggested that running Winmgmt /salvagerepository command fixed the problem. I ran the command in the Command Prompt and a /verifyrepository said it was consistent. However, the error still occurred when I installed SQL Server.
    Can anyone help with this?

    Hi wagham,
    From your description, you encounter the error when installing SQL Server 2014 Express on Windows 8.1. For further analysis, please help to post the summary and detail logs which locate under 
    %ProgramFiles%\Microsoft SQL Server\120\Setup Bootstrap\Log. For more details about viewing SQL Server setup log files, you can refer to this
    article.
    Additionally, based on my research, “MOF Syntax Error” could be caused by various reasons, such as insufficient account permissions, corrupted .NET Framework and so on. There are some proposals for you installing SQL Server 2014 Express as follows.
    1. Make sure that the account you use to install SQL Server has admin rights. If you are using a domain administrator, please ensure that it is added to local administrator group.
    2. Make sure that you right-click the SQL Server setup file (setup.exe) and choose “Run as administrator” to complete the installation.
    3. Check that if the .NET Framework is corrupted on your system. You can verify the installation state of the .NET Framework via the
    .NET Framework Setup Verification Tool. If the .NET Framework is corrupted, please
    repair it using
    .NET Framework Repair Tool, then reinstall SQL Server.
    Here is a similar blog about “MOF Syntax Error” for your reference.
    http://sqlservertimes2.com/?p=641
    Thanks,
    Lydia Zhang

  • Problem specifying SQL Loader Log file destination using EM

    Good evening,
    I am following the example given in the 2 Day DBA document chapter 8 section 16.
    In step 5 of 7, EM does not allow me to specify the destination of the SQL Loader log file to be on a mapped network drive.
    The question: Does SQL Loader have a limitation that I am not aware of, that prevents placing the log file on a network share or am I getting this error because of something else I am inadvertently doing wrong ?
    Note: I have placed the DDL, load file data and steps I follow in EM at the bottom of this post to facilitate reproducing the problem *(drive Z is a mapped drive)*.
    Thank you for your help,
    John.
    DDL (generated using SQL developer, you may want to change the space allocated to be less)
    CREATE TABLE "NICK"."PURCHASE_ORDERS"
        "PO_NUMBER"      NUMBER NOT NULL ENABLE,
        "PO_DESCRIPTION" VARCHAR2(200 BYTE),
        "PO_DATE" DATE NOT NULL ENABLE,
        "PO_VENDOR" NUMBER NOT NULL ENABLE,
        "PO_DATE_RECEIVED" DATE,
        PRIMARY KEY ("PO_NUMBER") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS NOCOMPRESS LOGGING TABLESPACE "USERS" ENABLE
      SEGMENT CREATION DEFERRED PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING STORAGE
        INITIAL 67108864
      TABLESPACE "USERS" ;
    Load.dat file contents
    1, Office Equipment, 25-MAY-2006, 1201, 13-JUN-2006
    2, Computer System, 18-JUN-2006, 1201, 27-JUN-2006
    3, Travel Expense, 26-JUN-2006, 1340, 11-JUL-2006
    Steps I am carrying out in EM
    log in, select data movement -> Load Data from User Files
    Automatically generate control file
    (enter host credentials that work on your machine)
    continue
    Step 1 of 7 ->
      Data file is located on your browser machine
      "Z:\Documentation\Oracle\2DayDBA\Scripts\Load.dat"
       click next
    step 2 of 7 ->
      Table Name
      nick.purchase_orders
      click next
    step 3 of 7 ->
      click next
    step 4 of 7 ->
      click next
    step 5 of 7 ->
      Generate log file where logging information is to be stored
      Z:\Documentation\Oracle\2DayDBA\Scripts\Load.LOG
      Validation Error
      Examine and correct the following errors, then retry the operation:
      LogFile - The directory does not exist.

    Hi John,
    But, i did'nt found any error when i am going the same what you did.
    My Oracle Version is 10.2.0.1 and using Windows xp. See what i did and i got worked
    1.I created one table in scott schema :
    SCOTT@orcl> CREATE TABLE "PURCHASE_ORDERS"
      2  (
      3      "PO_NUMBER"      NUMBER NOT NULL ENABLE,
      4      "PO_DESCRIPTION" VARCHAR2(200 BYTE),
      5      "PO_DATE" DATE NOT NULL ENABLE,
      6      "PO_VENDOR" NUMBER NOT NULL ENABLE,
      7      "PO_DATE_RECEIVED" DATE,
      8      PRIMARY KEY ("PO_NUMBER") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS NOCOMPRESS LOGGING TABLESPACE "USERS" ENABLE
      9  )
    10  TABLESPACE "USERS";
    Table created.I logged into em Maintenance-->Data Movement-->Load Data from User Files-->My Host Credentials
    Here i total 3 text boxes :
    1.Server Data File : C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
    2.Data File is Located on Your Browser Machine : z:\load.dat <--- Here z:\ means other machine's shared doc folder; and i selected this option (as option button click) and i created the same load.dat as you mentioned.
    3.Temporary File Location : C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\ <--- I did'nt mentioned anything.
    Step 2 of 7 Table Name : scott.PURCHASE_ORDERS
    Step 3 of 7 I just clicked Next
    Step 4 of 7 I just clicked Next
    Step 5 of 7 I just clicked Next
    Step 6 of 7 I just clicked Next
    Step 7 of 7 Here it is Control File Contents:
    LOAD DATA
    APPEND
    INTO TABLE scott.PURCHASE_ORDERS
    FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
    PO_NUMBER INTEGER EXTERNAL,
    PO_DESCRIPTION CHAR,
    PO_DATE DATE,
    PO_VENDOR INTEGER EXTERNAL,
    PO_DATE_RECEIVED DATE
    And i just clicked on submit job.
    Now i got all 3 rows in purchase_orders :
    SCOTT@orcl> select count(*) from purchase_orders;
      COUNT(*)
             3So, there is no bug, it worked and please retry if you get any error/issue.
    HTH
    Girish Sharma

  • SQL Server Assertion: File: "logmgr.cpp" , line=5512

    Hi All,
    We are using Sql Server 2005 Express , 
    we got the below exception of Sql Server Assertion
    2014-11-17 00:26:12.59 spid51      Error: 17066, Severity: 16, State: 1.
    2014-11-17 00:26:12.59 spid51      SQL Server Assertion: File: <"logmgr.cpp">, line=5512 Failed Assertion = '!(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)'. This error may be timing-related. If the error persists after rerunning
    the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
    2014-11-17 00:26:12.61 spid51      Error: 3624, Severity: 20, State: 1.
    2014-11-17 00:26:12.61 spid51      A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running
    DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support. 
    2014-11-17 00:27:34.81 Server      Using 'dbghelp.dll' version '4.0.5'
    2014-11-17 00:27:34.81 Server      ***Unable to get thread context - no pss
    2014-11-17 00:27:34.81 Server      * *******************************************************************************
    2014-11-17 00:27:34.81 Server      *
    2014-11-17 00:27:34.81 Server      * BEGIN STACK DUMP:
    2014-11-17 00:27:34.81 Server      *   11/17/14 00:27:34 spid 0
    2014-11-17 00:27:34.81 Server      *
    2014-11-17 00:27:34.81 Server      * Non-yielding Scheduler
    2014-11-17 00:27:34.81 Server      *
    2014-11-17 00:27:34.81 Server      * *******************************************************************************
    2014-11-17 00:27:34.81 Server      Stack Signature for the dump is 0x000003E6
    2014-11-17 00:27:35.75 Server      External dump process return code 0x20000001.
    External dump process returned no errors.
    2014-11-17 00:27:35.75 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    99%. Interval: 75000 ms.
    2014-11-17 00:28:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 135953 ms.
    2014-11-17 00:29:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 195953 ms.
    2014-11-17 00:30:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 255953 ms.
    2014-11-17 00:31:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 315953 ms.
    2014-11-17 00:32:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 375953 ms.
    2014-11-17 00:33:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 435953 ms.
    2014-11-17 00:34:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 495953 ms.
    2014-11-17 00:35:05.77 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
    2014-11-17 00:35:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 555953 ms.
    2014-11-17 00:36:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    97%. Interval: 615953 ms.
    2014-11-17 00:37:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 675953 ms.

    Assertion error are usually some corruption in SQL Server database. And non yielding scheduler seems like bug what is output of
    select @@Version
    Did you tried running dbcc checkdb on SQL Server 2005 database
    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 Wiki Article
    MVP

Maybe you are looking for

  • Exception JComboox :Exception in thread "AWT-EventQueue-0" java.lang.NullPo

    Hi, I mapped a vector object to the JComboBox. I'm using the observer pattern to update the ComboBox box whenever there is an message receives.If an update is received I just add the data to the vector and to refresh the ComboBox bu calling the Updat

  • HP Pavilion All-in-One MS237 Desktop PC : Shuts down

    Hello  can someone please help me I have an all in one computer an after I'm on foe a few minutes it shuts down  Thank you

  • FRM-40735 on the Web, in client/server without error

    We have 2 types of Form modules. Type 1 are simple multirecord modules, which uses PL/SQL library module PL1.plx. Type 2 are complex (master-detail) modules, which uses PL/SQL library module PL2.plx. In client/server, both types of Form modules work

  • How to Compile this prog. i DOS prompt.

    Hey Friends, I don't know how to compile this prog. on DOS prompt, kindly tell. // My Java Prog. package package1; import java.awt.Graphics; import java.lang.Number; import java.io.*; import java.net.*; import java.util.*; import java.awt.Color; impo

  • No Music In Seychelles iTunes Store

    Hi All, I just changed my store account from UK to Seychelles, and to my utter disapointment, there is no music on the latter store. Looking for people with the same problem. Cheers.