SQL 2012 SP 1 error -

I have done and read all possible blogs but there is no solution on below error -Please let me know if someone has faced Similar issue :
Action required:
Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Feature failure reason:
An error occurred during the setup process of the feature.
Error details:
§ Error installing SQL Server Distributed Replay Controller
The RPC server is unavailable.
Error code: 0x84BB0001
Visit
http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xFB87BFDA%400x48149828&EvtType=0xFB87BFDA%400x48149828 to get help on troubleshooting.
Product Update:
Product Update has successfully applied KB 2674319 <http://support.microsoft.com/?id=2674319> and KB 2793634 <http://support.microsoft.com/kb/2793634>.
These updates have set the patch level of the Setup operation to 11.1.3128.0.
I have tried -Unistalling Reinstalling OS
SQL -2012 SP1 downloaded from MSDN -Fresh ISO Copy no go
THE RPC error will no go - Please suggest !!!
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Anand Shankar

Below is the error i get :- I have tried all steps above still no go
(01) 2014-04-15 16:05:02 Slp: Prompting user if they want to retry this action due to the following failure:
(01) 2014-04-15 16:05:02 Slp: ----------------------------------------
(01) 2014-04-15 16:05:02 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2014-04-15 16:05:02 Slp: Inner exceptions are being indented
(01) 2014-04-15 16:05:02 Slp:
(01) 2014-04-15 16:05:02 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
(01) 2014-04-15 16:05:02 Slp:     Message:
(01) 2014-04-15 16:05:02 Slp:         The RPC server is unavailable.
(01) 2014-04-15 16:05:02 Slp:        
(01) 2014-04-15 16:05:02 Slp:     HResult : 0x84bb0001
(01) 2014-04-15 16:05:02 Slp:         FacilityCode : 1211 (4bb)
(01) 2014-04-15 16:05:02 Slp:         ErrorCode : 1 (0001)
(01) 2014-04-15 16:05:02 Slp:     Data:
(01) 2014-04-15 16:05:02 Slp:       WatsonData = Domain
(01) 2014-04-15 16:05:02 Slp:       DisableRetry = true
(01) 2014-04-15 16:05:02 Slp:     Inner exception type: System.Runtime.InteropServices.COMException
(01) 2014-04-15 16:05:02 Slp:         Message:
(01) 2014-04-15 16:05:02 Slp:                 The RPC server is unavailable.
(01) 2014-04-15 16:05:02 Slp:                
(01) 2014-04-15 16:05:02 Slp:         HResult : 0x800706ba
(01) 2014-04-15 16:05:02 Slp:         Stack:
(01) 2014-04-15 16:05:02 Slp:                 at System.DirectoryServices.DirectoryEntries.Find(String name, String schemaClassName)
(01) 2014-04-15 16:05:02 Slp:                 at Microsoft.SqlServer.Configuration.Sco.User.LookupADEntry()
Let me know if any further suggestion .
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Anand Shankar

Similar Messages

  • Linked Server : SQL 2012 to 2000 error - Microsoft Distributed Transaction Coordinator (MS DTC) has stopped this transaction.

    Hi all,
      If any one has worked around this error and can help ?
    Msg 8522, Level 16, State 3, Line 1
    Microsoft Distributed Transaction Coordinator (MS DTC) has stopped this transaction.
      I am trying to connect from sql 2012 to 2000 server. Established linked server using native client 10. I am able to see catalogs and database and table. Just when I am trying to query i am getting above error. 
    any help is really appreciated. 
    Thanks
    Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

    Hi Logicinisde,
    What the new error message do you get after using the workarounds in this
    blog? Please post it for analysis.
    Besides, as SQL Server 2012 has stopped connecting to SQL Server 2000 via linked servers, personally I recommend you upgrade SQL Server 2000 to a higher version to make your queries or ETLs efficient.
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • SQL 2012 Cluster install - error msg

    Hi
    I am in the process of installing SQL server 2012 cluster, on the Instance configuration page where i gave "SQL Server Network Name" as  "appsqlclsA" and the "Named Instance" as "Ins01". I am getting the below
    error msg, i am not sure exactly what permissions i need.
    "The SQL Server failover cluster network name "appsqlclsA" is not valid. The name must be a valid DNS and Wins name.
    So what i understand is i do not have permission to create the virtual sql name account "appsqlclsA"" in the AD.
    But i need help finding exactly what permission i need.
    Thank you for your help

    Take a look at this
    TechNet article for assigning permissions in Active Directory to create the virtual computer object. Either you are granted the appropriate permissions or the virtual computer object be pre-staged prior to installation
    Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
    Blog |
    Twitter | LinkedIn
    SQL Server High Availability and Disaster Recover Deep Dive Course

  • SQL 2012 Log Shipping error 14261

    I have two servers and I had log shipping working but could not add any additional databases to the process.  I deleted all the log shipping and I am still unable to add the databases back to the log shipping configuration.  The process fails while
    trying to all the Secondary Log shipping configuration.  I get the following error: The specified @name ('Log shipping Primary Server Alert.') already exists. (.Net SqlClient Data Provider) and it specifically refers to my secondary server by name in
    the error also referencing the stored procedure sp_verify_alert.  I have not been able to find a solution.  Please help.

    You ran this on secondary?
    2. On the secondary server, execute sp_delete_log_shipping_secondary_database to delete the secondary database.
    sp_delete_log_shipping_secondary_database N'LogShipAdventureWorks'

  • Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5015. SQL 2012 SP1

    Hi,
    Please help. I was trying to remove a SQL 2012 SP1 two node clustered instance using setup (Mantenance -> Remove Node)
    I started by doing this on passive node (and was successful) but when I ran setup on active node just before finishing successfully I got this error:
    TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
    The following error has occurred:
    The resource 'BCK_SG1DB' could not be moved from cluster group 'SQL Server (SG1DB)' to cluster group 'Available Storage'. 
    Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5015.
    Description: The operation failed because either the specified cluster node is not the owner of the resource, or the node
    is not a possible owner of the resource.
    For help, click:
    http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xE8049925%25400x42B4DED7
    BUTTONS:
    OK
    I noticed that SG1DB instance was removed on both nodes but on Failover Cluster Manager -> Services and Applications the SQL server instance for SG1DB is still there. So I tried to delete it but got the error:
    Failed to delete SQL Server SG1DB. An error was encountered while deleting the cluster service or
    application SQL Server SG1DB. Could not move the resource to available storage. An error occured
    while moving the resource BCK_SG1DB to the clustered service or application Available Storage
    Any ideas why it failed or how could I delete the SQL server instance from Clauster?
    Thx

    Hello,
    Please read the following resource.
    https://support.microsoft.com/en-us/kb/kbview/313882?wa=wsignin1.0
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

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

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

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

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

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

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

  • Error while configuring SQL 2012 DB as a Subscriber to a Oracle Publisher.

    When Configuring the Subscription for Oracle as a publisher, we receive the following error message.
    Msg 18757, Level 16, State 4, Procedure sp_replpostcmd, Line 1
    Unable to execute procedure. The database is not published. Execute the procedure in a database that is published for replication.
    The Subscriber was dropped.
    Same message is received if add the subscription through script or through SQL Management studio.
    However Oracle as a publisher has been configured successfully on a SQL 2012 DB server, Which is also the  Distribution server
    using the following links. 
    https://msdn.microsoft.com/en-us/library/ms151243(v=sql.110).aspx
    https://msdn.microsoft.com/en-us/library/ms152481(v=sql.110).aspx
    Note: Same Steps successfully work from a SQL 2008 Machine. i.e If i use SQL 2008 machine to configure Oracle as a Publisher and then subscribe to SQL 2012 machine as Subscriber.
    Is there a known issue? or some extra steps for 2012 that are not documented. Any help will be much appreciated.
    Client Oracle Version:9i
    Subscriber DB Version: SQL Server 2012 SP2
    Thanks and Regards, Ibrahim Mehdi. MCSE-DataPlatform

    Yes . The SQL Server 2012 is EE.
    As Informed before, The Oracle Publisher configuration is working successfully without any error. It is giving the error provided while trying to create a subscriber to this Oracle Publisher.
    Thanks and Regards, Ibrahim Mehdi. MCSE-DataPlatform

  • SCOM 2012 R2 Report Server component install to SQL 2012 Sp1 error?

    Hi All
    Im having issues installing SCOM 2012 R2 Report Server component to a SQL 2012 Sp1 Server (which is a Windows 2012 R2 Standard server).  Im trying to install to the SQL Default server instance, note that the server also has a named instance
    which hosts the SCOM databases.  SQL Reporting Services is up and running fine (can access the web urls etc).  Im also using the SCOM install account wich has full SQL and SCOM Server admin rights for the install.  Ive checked that the Firewall
    is off locally on the SQL Server, Ive also checked that the existing SCOM components are all in a Healthy state in the SCOM console.
    The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
    Configurations document for further information.
    Ive attempted the install on a standalone SQL Server away from the SQL Server hosting the SCOM databases, but encounter the same error.  The full SCOM MSI Installer log details are below, line that appears most relevant is below but unsure why
    this would be the case (same account that I used for SQL install etc).  Any help much appreciated! : )
    Error: :getSQLInstanceVersion:  Unable to find the SRS Instance Key: MSSQLSERVER
    [11:51:46]: Debug: :CheckPrerequisites:  IsComputerNameValidTitle: Passed
    [11:51:46]: Debug: :
    [11:51:46]: Debug: :**************************************************
    [11:51:46]: Debug: :**************************************************
    [11:51:46]: Debug: :<![CDATA[CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x86: 0CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x64: 0]]>
    [11:51:46]: Debug: :
    [11:51:46]: Debug: :CheckPrerequisites:  AVIcodeAgentCheck: Passed
    [11:51:46]: Debug: :
    [11:51:46]: Debug: :**************************************************
    [11:51:46]: Always: :CheckPrerequisites: Return Value 0
    [11:51:46]: Always: :Entering Page: AdditionalPrerequisitesPage
    [11:51:48]: Always: :Entering Page: ShortEulaPage
    [11:51:48]: Always: :Displaying localized EULA for localization: en
    [11:51:48]: Always: :Displaying Eula: C:\Users\opsmgr\AppData\Local\SCOM\Setup\en\eula_en_notice.rtf
    [11:51:49]: Info: :Info:User has agreed to EULA.
    [11:51:50]: Always: :Entering Page: SelectManagementServerForReporting
    [11:52:08]: Info: :Info:Management Server matches the current version of setup.
    [11:52:08]: Always: :Entering Page: SelectReportingInstance
    [11:52:08]: Always: :SQL Server SRS Instance (escaped name) RS_MSSQLSERVER
    [11:52:08]: Info: :Attempting to get the SSRS version from:
    \\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER:__NAMESPACE
    [11:52:08]: Debug: :Path is
    \\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER\V11:MSReportServer_Instance
    [11:52:08]: Always: :SRS instance on WDC-SYSSQL01. Version 11.0.3000.0.
    [11:52:08]: Always: :No SRS instances on WDC-SYSSQL01.
    [11:52:08]: Error: :getSQLInstanceVersion:  Unable to find the SRS Instance Key: MSSQLSERVER
    [11:52:08]: Info: :Info: WDC-SYSSQL01 SRS version =
    [11:52:08]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
    [11:52:08]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
       at System.Version.Parse(String input)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
    [11:52:11]: Info: :Attempting to check SRS version
    [11:52:11]: Error: :getSQLInstanceVersion:  Unable to find the SRS Instance Key: MSSQLSERVER
    [11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
    [11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
    [11:52:11]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
       at System.Version.Parse(String input)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
    [11:52:28]: Info: :The user canceled setup
    [11:52:28]: Always: :Begin: Property bag dump.
    [11:52:28]: Always: :SetupStartTime = 26/03/2014 11:51:38
    [11:52:28]: Always: :Collection ProtectedProperties (System.Collections.ArrayList):
    [11:52:28]: Always: : [0] = ActionAccountPassword
    [11:52:28]: Always: : [1] = DASAccountPassword
    [11:52:28]: Always: :DefaultLogName = C:\Users\opsmgr\AppData\Local\SCOM\Logs\OpsMgrSetupWizard.log
    [11:52:28]: Always: :DefaultLogPath = C:\Users\opsmgr\AppData\Local\SCOM\Logs
    [11:52:28]: Always: :path = F:\Setup\AMD64\
    [11:52:28]: Always: :setupexepath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
    [11:52:28]: Always: :ArchitectureIs64Check = True
    [11:52:28]: Always: :OperationManagerAgentInstalled = 1
    [11:52:28]: Always: :Collection ListOfSupportedComponents (System.Collections.ArrayList):
    [11:52:28]: Always: : [0] = OMCONSOLE
    [11:52:28]: Always: : [1] = OMSERVER
    [11:52:28]: Always: : [2] = OMWEBCONSOLE
    [11:52:28]: Always: : [3] = OMREPORTING
    [11:52:28]: Always: :install = 1
    [11:52:28]: Always: :installpath = C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
    [11:52:28]: Always: :EulaFilesPath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
    [11:52:28]: Always: :HealthServiceTypeId = AB4C891F-3359-3FB6-0704-075FBFE36710
    [11:52:28]: Always: :hsPort = C51B7833-DA54-1653-D8FD-1A738EF8DED5
    [11:52:28]: Always: :ServerBlockReason = A Operations Manager agent was found on this computer. Please remove the agent and then run Setup again.
    [11:52:28]: Always: :ScreensLoaded = 1
    [11:52:28]: Always: :Collection ListOfSelectedComponents (System.Collections.ArrayList):
    [11:52:28]: Always: : [0] = OMREPORTING
    [11:52:28]: Always: :OMREPORTING = 1
    [11:52:28]: Always: :SelectDatabaseInstanceReloadScreenInformation = 1
    [11:52:28]: Always: :ReloadPrerequisitesPageChoice = PrerequisitesProgressPage
    [11:52:28]: Always: :LoadedPrerequisiteXmlFile = True
    [11:52:28]: Always: :PrerequisitesCheckXMLLoaded = True
    [11:52:28]: Always: :CountFilteredPrerequisites_Failed = 0
    [11:52:28]: Always: :CountFilteredPrerequisites_Warning = 0
    [11:52:28]: Always: :CountFilteredPrerequisites_PassedWithChoices = 0
    [11:52:28]: Always: :CountFilteredPrerequisites_Passed = 10
    [11:52:28]: Always: :PrerequisiteState = Passed
    [11:52:28]: Always: :XmlFilteredPrerequisites_Passed : Begin XML property
    [11:52:28]: Always: :<?xml version="1.0" encoding="utf-8"?><Root><Title TitleText="OMREPORTING"><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="memoryCheckTitle" descriptionBody="" descriptionTitle="ReportingMemCheckPassed" resolution="ReportingMemCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="ntfsCheckTitle" descriptionBody="" descriptionTitle="ntfsCheckPassed" resolution="ntfsCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="DriveSpaceCheckTitle" descriptionBody="" descriptionTitle="ServerDriveSpaceCheckPassed" resolution="ServerDriveSpaceCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="OSVersionCheckTitle" descriptionBody="" descriptionTitle="OSVersionCheckPassed" resolution="OSVersionCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="WindowsInstallerCheckTitle" descriptionBody="" descriptionTitle="WindowsInstallerCheckPassed" resolution="WindowsInstallerCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="RemoteRegistryCheckTitle" descriptionBody="" descriptionTitle="RemoteRegistryCheckPassed" resolution="RemoteRegistryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="PendingRebootCheckTitle" descriptionBody="" descriptionTitle="PendingRebootCheckPassed" resolution="PendingRebootCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="ActiveDirectoryCheckTitle" descriptionBody="" descriptionTitle="ActiveDirectoryCheckPassed" resolution="ActiveDirectoryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="IsComputerNameValidTitle" descriptionBody="" descriptionTitle="IsComputerNameValidPassed" resolution="IsComputerNameValidResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="AVIcodeAgentCheck" descriptionBody="" descriptionTitle="AVICodeAgentCheckPassed" resolution="AVICodeAgentCheckResolution" /></Title></Root>
    [11:52:28]: Always: :End XML property
    [11:52:28]: Always: :ManagementServer = WDC-SYSOPS01.landmarc.local
    [11:52:28]: Always: :DefaultSDKMachine = WDC-SYSOPS01.landmarc.local
    [11:52:28]: Always: :UserCanceledInstall = 1
    [11:52:28]: Always: :InstallSuccess = 1
    [11:52:28]: Always: :End: Property bag dump.
    [11:52:28]: Debug: :CEIP disabled. CEIP data will NOT be sent.
    [11:52:28]: Always: :Application Ended: Successful
    [11:52:28]: Always: :
    [2014-03-26T11:52:28.4724357+00:00]: Always: Trace Session Ended

    Hi,
    According to the error message:
    [11:52:11]: Error: :getSQLInstanceVersion:  Unable to find the SRS Instance Key: MSSQLSERVER
    [11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
    [11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
    The issue is SQL report server database related, I would like to suggest you create a new report database for SCOM and then check the reuslt. Please refer to the below links and follow it to set up SCOM 2012 R2:
    http://blogs.technet.com/b/kevinholman/archive/2013/01/16/opsmgr-2012-sp1-quickstart-deployment-guide.aspx
    In addition, here is thread for your reference also:
    http://social.technet.microsoft.com/Forums/en-US/3f883b7f-5a33-49f0-a40d-f3311e68609d/unable-to-connect-to-the-data-access-service-installing-report-server?forum=operationsmanagerreporting
    Regards,
    Yan Li
    Regards, Yan Li

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

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

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

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

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

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

  • Report service Integration (sql 2012 and SharePoint 2013) error Report Server WMI Provider error: Invalid namespace

    Report Server WMI Provider Error: Invalid namespace
    Domain Server, Sql2012 server and SP2013 Server (3 vm servers)
    the sql server reporting services service application and applications Proxy are installed and started (SP2013 Sever)
    the sql server PowerPivot system Service and SQL server Reporting Services Service are Started (in Services on Server)
    in sql server 2012 sp1 reporting service configured (web service URL and Report Manager URL are configured and tested,  the database report server mode is native) (SQl 2012 Server)
    under general Application Settings .. trying to setup the "Reporting Service Integration" give us the above error message (Report Server WMI Provider Error: Invalid namespace)
    I was looking for all blogs and TechNet material but without success.

    Follow these steps:
    1) Uninstall SSRS from the Database Engine server (MSSQLSERVER instance).
    2) Install SSRS on the SharePoint server using the "Reporting Services - SharePoint" install option during SQL Feature selection, no other services are required (e.g. you do not need to install Database Engine services).
    3) You should then see SSRS as a Service Instance in Central Admin -> Manage Services on Server, at which point you can also create an SSRS Service Application.
    While this guide (http://msdn.microsoft.com/en-us/library/jj219068.aspx#bkmk_install_SSRS) walks you through it, this is for a single server install where the Database Engine is also installed on SharePoint, not something you want to do.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Reporting Service Error Code 7403, on SCCM 2012 R2 with SQL 2012 SP1 CU6

    Dear All,
    I am facing issue to install Reporting Services Point on SCCM 2012 R2 with SQL 2012 SP1 CU6. getting error messages id 7403. please let me know if SQL 2012 SP1 CU6 is supported with SCCM 2012 R2 or not & if you have any solution on it.
    Error Message: The report server service is not running on Reporting Service Point server "SCCM2012"; start the service to enable reporting.

    I am getting below error msg when trying to browse both sites
    1) For Reports
    The report server cannot decrypt the
    symmetric key that is used to access sensitive or encrypted data in a report
    server database. You must either restore a backup key or delete all encrypted
    content. (rsReportServerDisabled)
    Get Online Help
    Keyset does not exist (Exception from
    HRESULT:
    0x80090016)
    2) For Reportserver
    Reporting Services Error
    The report server cannot decrypt the symmetric key that is used to access
    sensitive or encrypted data in a report server database. You must either restore
    a backup key or delete all encrypted content. (rsReportServerDisabled)
    Get Online Help
    Keyset does not exist (Exception from HRESULT: 0x80090016)
    SQL Server Reporting Services

  • Critical SMS_NOTIFICATION_SERVER ERROR sccm 2012 R2 WITH SQL 2012 SP1

    Environement
    SCCM 2012 R2
    SQL 2012 SP1
    On the same server
    In sccm console i have in Monitoring - System Status - Component Status
    critical SMS_NOTIFICATION_SERVER ERROR
    Here are the two error that keep popping up
    ERROR 1016
    Site Component Manager failed to install this component on this site system.
    Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in 60 minutes. To force Site Component Manager to immediately retry the installation, stop and restart
    Site Component Manager using the Configuration Manager Service Manager.
    Folowing message
    ERROR 4951
    Site Component Manager failed to install this component, because the Microsoft Installer File for this component (bgbisapi.msi) could not install.
    Refer to the BgbSetup.log, the bgbisapimsi.log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.
    Here are the 2 logs
    bgbsetuplog
    <02/28/14 09:00:53> ====================================================================
    <02/28/14 09:00:53> SMSBGB Setup Started....
    <02/28/14 09:00:53> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:TCI-SCCMR2-LAV SMSBGB 0
    <02/28/14 09:00:53> Installing Pre Reqs for SMSBGB
    <02/28/14 09:00:53>         ======== Installing Pre Reqs for Role SMSBGB ========
    <02/28/14 09:00:53> Found 1 Pre Reqs for Role SMSBGB
    <02/28/14 09:00:53> Pre Req SqlNativeClient found.
    <02/28/14 09:00:53> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
    <02/28/14 09:00:53> Pre Req SqlNativeClient is already installed. Skipping it.
    <02/28/14 09:00:53>         ======== Completed Installation of Pre Reqs for Role SMSBGB ========
    <02/28/14 09:00:53> Installing the SMSBGB
    <02/28/14 09:00:53> Passed OS version check.
    <02/28/14 09:00:53> IIS Service is installed.
    <02/28/14 09:00:53> SMSBGB already installed (Product Code: {A78E8003-2307-4B70-B7CD-1A07C0A31D21}).  Upgrading/Reinstalling SMSBGB
    <02/28/14 09:00:53> New SMSBGB is the same product code.  This is a minor upgrade.
    <02/28/14 09:00:53> Enabling MSI logging.  bgbisapi.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log
    <02/28/14 09:00:53> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration
    Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
    <02/28/14 09:01:01> bgbisapi.msi exited with return code: 0
    <02/28/14 09:01:01> Installation was successful.
    <02/28/14 09:01:01> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /u "D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
    <02/28/14 09:01:04> CTool::RegisterComPlusService: Failed to unregister D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
    <02/28/14 09:01:04> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /extlb /tlb:"D:\Program Files\SMS_CCM\microsoft.configurationmanager.bgbserverchannel.tlb" "D:\Program
    Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
    <02/28/14 09:01:07> CTool::RegisterComPlusService: Failed to register D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
    <02/28/14 09:01:07> Cannot register BGB server channel DLL D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.
    <02/28/14 09:01:07> Fatal MSI Error - bgbisapi.msi could not be install
    bgpisapi.log
    MSI (s) (00:60) [09:01:01:660]: Product: BGB http proxy -- Configuration completed successfully.
    MSI (s) (00:60) [09:01:01:661]: Windows Installer reconfigured the product. Product Name: BGB http proxy. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.
    MSI (s) (00:60) [09:01:01:665]: Deferring clean up of packages/files, if any exist
    MSI (s) (00:60) [09:01:01:665]: MainEngineThread is returning 0
    MSI (s) (00:04) [09:01:01:670]: RESTART MANAGER: Session closed.
    MSI (s) (00:04) [09:01:01:670]: No System Restore sequence number for this installation.
    === Logging stopped: 2/28/2014  9:01:01 ===
    MSI (s) (00:04) [09:01:01:674]: User policy value 'DisableRollback' is 0
    MSI (s) (00:04) [09:01:01:674]: Machine policy value 'DisableRollback' is 0
    MSI (s) (00:04) [09:01:01:674]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (00:04) [09:01:01:675]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (00:04) [09:01:01:677]: Note: 1: 2265 2:  3: -2147287035
    MSI (s) (00:04) [09:01:01:678]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (00:04) [09:01:01:678]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (00:04) [09:01:01:679]: Destroying RemoteAPI object.
    MSI (s) (00:B8) [09:01:01:679]: Custom Action Manager thread ending.
    MSI (c) (3C:B8) [09:01:01:686]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (3C:B8) [09:01:01:686]: MainEngineThread is returning 0
    MSI (c) (3C:B0) [09:01:01:690]: RESTART MANAGER: Session closed.
    === Verbose logging stopped: 2/28/2014  9:01:01 ===

    Problem not fixed SORRY GUY'S
    Environement
    1 SERVER
    WINDOWS SERVER 2012 R2
    SQL SERVER 2012 SP1
    SCCM 2012 R2
    ERROR in system center
    Message ID 1016
    Site Component Manager failed to install this component on this site system.
    Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in 60 minutes. To force Site Component Manager to immediately retry the installation, stop and restart
    Site Component Manager using the Configuration Manager Service Manager.
    Message ID
    4951
    Site Component Manager failed to install this component, because the Microsoft Installer File for this component (bgbisapi.msi) could not install.
    Refer to the BgbSetup.log, the bgbisapimsi.log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.
    BGPSETUP.LOG
    <03/05/14 09:49:33> ====================================================================
    <03/05/14 09:49:33> SMSBGB Setup Started....
    <03/05/14 09:49:33> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:TCI-SCCMR2-LAV SMSBGB 0
    <03/05/14 09:49:33> Installing Pre Reqs for SMSBGB
    <03/05/14 09:49:33>         ======== Installing Pre Reqs for Role SMSBGB ========
    <03/05/14 09:49:33> Found 1 Pre Reqs for Role SMSBGB
    <03/05/14 09:49:33> Pre Req SqlNativeClient found.
    <03/05/14 09:49:33> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
    <03/05/14 09:49:33> Pre Req SqlNativeClient is already installed. Skipping it.
    <03/05/14 09:49:33>         ======== Completed Installation of Pre Reqs for Role SMSBGB ========
    <03/05/14 09:49:33> Installing the SMSBGB
    <03/05/14 09:49:33> Passed OS version check.
    <03/05/14 09:49:33> IIS Service is installed.
    <03/05/14 09:49:33> SMSBGB already installed (Product Code: {A78E8003-2307-4B70-B7CD-1A07C0A31D21}).  Upgrading/Reinstalling SMSBGB
    <03/05/14 09:49:33> New SMSBGB is the same product code.  This is a minor upgrade.
    <03/05/14 09:49:33> Enabling MSI logging.  bgbisapi.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log
    <03/05/14 09:49:33> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration
    Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
    <03/05/14 09:49:41> bgbisapi.msi exited with return code: 0
    <03/05/14 09:49:41> Installation was successful.
    <03/05/14 09:49:41> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /u "D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
    <03/05/14 09:49:43> CTool::RegisterComPlusService: Failed to unregister D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
    <03/05/14 09:49:43> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /extlb /tlb:"D:\Program Files\SMS_CCM\microsoft.configurationmanager.bgbserverchannel.tlb" "D:\Program
    Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
    <03/05/14 09:49:45> CTool::RegisterComPlusService: Failed to register D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
    <03/05/14 09:49:45> Cannot register BGB server channel DLL D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.
    <03/05/14 09:49:45> Fatal MSI Error - bgbisapi.msi could not be installed.
    <03/05/14 09:49:45> ~RoleSetup().
    BGBISAPI.LOG
    === Verbose logging started: 3/5/2014  9:49:33  Build type: SHIP UNICODE 5.00.9600.00  Calling process: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe ===
    MSI (c) (08:C0) [09:49:33:974]: Resetting cached policy values
    MSI (c) (08:C0) [09:49:33:974]: Machine policy value 'Debug' is 0
    MSI (c) (08:C0) [09:49:33:974]: ******* RunEngine:
               ******* Product: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (08:C0) [09:49:33:974]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (08:C0) [09:49:33:974]: Grabbed execution mutex.
    MSI (c) (08:C0) [09:49:34:021]: Cloaking enabled.
    MSI (c) (08:C0) [09:49:34:021]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (08:C0) [09:49:34:025]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (C4:E4) [09:49:34:039]: Running installation inside multi-package transaction D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
    MSI (s) (C4:E4) [09:49:34:039]: Grabbed execution mutex.
    MSI (s) (C4:E8) [09:49:34:045]: Resetting cached policy values
    MSI (s) (C4:E8) [09:49:34:045]: Machine policy value 'Debug' is 0
    MSI (s) (C4:E8) [09:49:34:045]: ******* RunEngine:
               ******* Product: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
               ******* Action:
               ******* CommandLine: **********
    MSI (s) (C4:E8) [09:49:34:047]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (C4:E8) [09:49:34:053]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
    MSI (s) (C4:E8) [09:49:34:057]: SRSetRestorePoint skipped for this transaction.
    MSI (s) (C4:E8) [09:49:34:058]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
    MSI (s) (C4:E8) [09:49:34:060]: File will have security applied from OpCode.
    MSI (s) (C4:E8) [09:49:34:065]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi' against software restriction policy
    MSI (s) (C4:E8) [09:49:34:065]: SOFTWARE RESTRICTION POLICY: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi has a digital signature
    MSI (s) (C4:E8) [09:49:34:067]: SOFTWARE RESTRICTION POLICY: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi is permitted to run because the user token authorizes execution (system or service token).
    MSI (s) (C4:E8) [09:49:34:067]: MSCOREE not loaded loading copy from system32
    MSI (s) (C4:E8) [09:49:34:077]: End dialog not enabled
    MSI (s) (C4:E8) [09:49:34:077]: Original package ==> D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
    MSI (s) (C4:E8) [09:49:34:077]: Package we're running from ==> C:\Windows\Installer\3897f9.msi
    MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall Flags override found.
    MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall VersionNT override found.
    MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall ServicePackLevel override found.
    MSI (s) (C4:E8) [09:49:34:081]: APPCOMPAT: looking for appcompat database entry with ProductCode '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'.
    MSI (s) (C4:E8) [09:49:34:081]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (C4:E8) [09:49:34:094]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
    MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisablePatch' is 0
    MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'AllowLockdownPatch' is 0
    MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisableLUAPatching' is 0
    MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisableFlyWeightPatching' is 0
    MSI (s) (C4:E8) [09:49:34:095]: APPCOMPAT: looking for appcompat database entry with ProductCode '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'.
    MSI (s) (C4:E8) [09:49:34:095]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (C4:E8) [09:49:34:096]: Transforms are not secure.
    MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log'.
    MSI (s) (C4:E8) [09:49:34:096]: Command Line: REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR=D:\Program Files\SMS_CCM CCMSERVERDATAROOT=D:\Program Files\Microsoft Configuration Manager USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE
    SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1 CURRENTDIRECTORY=D:\Program Files\Microsoft Configuration Manager\bin\x64 CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=5384
    MSI (s) (C4:E8) [09:49:34:096]: Product Code passed to Engine.Initialize:           '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
    MSI (s) (C4:E8) [09:49:34:096]: Product Code from property table before transforms: '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
    MSI (s) (C4:E8) [09:49:34:096]: Product Code from property table after transforms:  '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
    MSI (s) (C4:E8) [09:49:34:096]: Product registered: entering maintenance mode
    MSI (s) (C4:E8) [09:49:34:096]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
    MSI (s) (C4:E8) [09:49:34:096]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is admin assigned: LocalSystem owns the publish key.
    MSI (s) (C4:E8) [09:49:34:096]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is managed.
    MSI (s) (C4:E8) [09:49:34:096]: MSI_LUA: Credential prompt not required, user is an admin
    MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
    MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
    MSI (s) (C4:E8) [09:49:34:096]: Entering CMsiConfigurationManager::SetLastUsedSource.
    MSI (s) (C4:E8) [09:49:34:096]: Specifed source is already in a list.
    MSI (s) (C4:E8) [09:49:34:096]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (C4:E8) [09:49:34:096]: Machine policy value 'DisableBrowse' is 0
    MSI (s) (C4:E8) [09:49:34:096]: Machine policy value 'AllowLockdownBrowse' is 0
    MSI (s) (C4:E8) [09:49:34:096]: Adding new sources is allowed.
    MSI (s) (C4:E8) [09:49:34:097]: Package name retrieved from configuration data: 'bgbisapi.msi'
    MSI (s) (C4:E8) [09:49:34:099]: Note: 1: 2262 2: AdminProperties 3: -2147287038
    MSI (s) (C4:E8) [09:49:34:099]: Machine policy value 'DisableMsi' is 1
    MSI (s) (C4:E8) [09:49:34:099]: Machine policy value 'AlwaysInstallElevated' is 0
    MSI (s) (C4:E8) [09:49:34:099]: User policy value 'AlwaysInstallElevated' is 0
    MSI (s) (C4:E8) [09:49:34:099]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is admin assigned: LocalSystem owns the publish key.
    MSI (s) (C4:E8) [09:49:34:099]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is managed.
    MSI (s) (C4:E8) [09:49:34:099]: Running product '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}' with elevated privileges: Product is assigned.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding REINSTALL property. Its value is 'ALL'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding REINSTALLMODE property. Its value is 'vmaus'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMINSTALLDIR property. Its value is 'D:\Program Files\SMS_CCM'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMSERVERDATAROOT property. Its value is 'D:\Program Files\Microsoft Configuration Manager'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSPORTS property. Its value is 'TRUE'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSPORTS property. Its value is '80'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSSSLPORTS property. Its value is 'TRUE'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSSSLPORTS property. Its value is '443'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSSSL property. Its value is 'TRUE'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSSSLSTATE property. Its value is '0'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMENABLELOGGING property. Its value is 'TRUE'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGLEVEL property. Its value is '1'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGMAXSIZE property. Its value is '1000000'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGMAXHISTORY property. Its value is '1'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'D:\Program Files\Microsoft Configuration Manager\bin\x64'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
    MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '5384'.
    MSI (s) (C4:E8) [09:49:34:100]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
    MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding MsiRestartManagerSessionKey property. Its value is '1ea81ab83bbb7c48a58c04b46f112051'.
    MSI (s) (C4:E8) [09:49:34:104]: RESTART MANAGER: Session opened.
    MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1'.
    MSI (s) (C4:E8) [09:49:34:104]: TRANSFORMS property is now:
    MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
    MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '200'.
    MSI (s) (C4:E8) [09:49:34:106]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming
    MSI (s) (C4:E8) [09:49:34:106]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Favorites
    MSI (s) (C4:E8) [09:49:34:108]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Network Shortcuts
    MSI (s) (C4:E8) [09:49:34:109]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Documents
    MSI (s) (C4:E8) [09:49:34:109]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
    MSI (s) (C4:E8) [09:49:34:110]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Recent
    MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\SendTo
    MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Templates
    MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\ProgramData
    MSI (s) (C4:E8) [09:49:34:112]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Local
    MSI (s) (C4:E8) [09:49:34:114]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Pictures
    MSI (s) (C4:E8) [09:49:34:124]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
    MSI (s) (C4:E8) [09:49:34:128]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
    MSI (s) (C4:E8) [09:49:34:129]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
    MSI (s) (C4:E8) [09:49:34:131]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
    MSI (s) (C4:E8) [09:49:34:132]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
    MSI (s) (C4:E8) [09:49:34:135]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
    MSI (s) (C4:E8) [09:49:34:137]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
    MSI (s) (C4:E8) [09:49:34:138]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
    MSI (s) (C4:E8) [09:49:34:139]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu
    MSI (s) (C4:E8) [09:49:34:141]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Desktop
    MSI (s) (C4:E8) [09:49:34:144]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
    MSI (s) (C4:E8) [09:49:34:144]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
    MSI (s) (C4:E8) [09:49:34:144]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
    MSI (s) (C4:E8) [09:49:34:156]: MSI_LUA: Setting AdminUser property to 1 because the product is already installed managed and per-machine
    MSI (s) (C4:E8) [09:49:34:156]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
    MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
    MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
    MSI (s) (C4:E8) [09:49:34:156]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
    MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'Windows User'.
    MSI (s) (C4:E8) [09:49:34:156]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
    MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding Installed property. Its value is '00:00:00'.
    MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\Windows\Installer\3897f9.msi'.
    MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi'.
    MSI (s) (C4:E8) [09:49:34:156]: Machine policy value 'MsiDisableEmbeddedUI' is 0
    MSI (s) (C4:E8) [09:49:34:156]: EEUI - Disabling MsiEmbeddedUI due to existing external or embedded UI
    MSI (s) (C4:E8) [09:49:34:156]: EEUI - Disabling MsiEmbeddedUI for service because it's not a quiet/basic install
    MSI (s) (C4:E8) [09:49:34:159]: Note: 1: 2205 2:  3: PatchPackage
    MSI (s) (C4:E8) [09:49:34:159]: Machine policy value 'DisableRollback' is 0
    MSI (s) (C4:E8) [09:49:34:159]: User policy value 'DisableRollback' is 0
    MSI (s) (C4:E8) [09:49:34:159]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
    MSI (s) (C4:E8) [09:49:34:159]: PROPERTY CHANGE: Adding QFEUpgrade property. Its value is '1'.
    === Logging started: 3/5/2014  9:49:34 ===
    MSI (s) (C4:E8) [09:49:34:161]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
    MSI (s) (C4:E8) [09:49:34:161]: PROPERTY CHANGE: Adding Preselected property. Its value is '1'.
    MSI (s) (C4:E8) [09:49:34:161]: APPCOMPAT: [DetectVersionLaunchCondition] Launch condition already passes.
    MSI (s) (C4:E8) [09:49:34:163]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
    MSI (s) (C4:E8) [09:49:34:163]: Doing action: INSTALL
    Action start 9:49:34: INSTALL.
    MSI (s) (C4:E8) [09:49:34:165]: Running ExecuteSequence
    MSI (s) (C4:E8) [09:49:34:165]: Doing action: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61
    MSI (s) (C4:E8) [09:49:34:166]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61'
    MSI (s) (C4:E8) [09:49:34:167]: PROPERTY CHANGE: Adding SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61 property. Its value is 'C:\Windows\SysWOW64\'.
    Action start 9:49:34: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61.
    MSI (s) (C4:E8) [09:49:34:167]: Doing action: System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61
    Action ended 9:49:34: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61. Return value 1.
    MSI (s) (C4:E8) [09:49:34:169]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61'
    MSI

  • Error 997. Overlapped I/O operation is in progress. When applying SQL 2012 SP2 to a FCI passive Node

    Hello
    I am upgrading my 2 node FCI cluster from SQL 2012 SP1 to SP2. I was able to update one node, then I did failover to the upgraded node but now I cannot update the other node (passive)
    I am getting "Error 997. Overlapped I/O operation is in progress"
    Any ideas ?
    Here is a piece of the log file
    MSI (s) (64:AC) [16:26:02:861]: SECREPAIR: A general error running CryptAcquireContext
    MSI (s) (64:AC) [16:26:02:861]: SECREPAIR: Crypt Provider not initialized. Error:0
    MSI (s) (64:AC) [16:26:02:861]: SECREPAIR: A general error running CryptAcquireContext
    MSI (s) (64:AC) [16:26:02:861]: SECREPAIR: Crypt Provider not initialized. Error:997
    MSI (s) (64:AC) [16:26:02:861]: SECUREREPAIR: Failed to CreateContentHash of the file: Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\1033_ENU_LP\x64\1033\license_SQLBI_OEM.rtf: for computing its hash. Error: 997
    MSI (s) (64:AC) [16:26:02:861]: SECREPAIR: Failed to create hash for the install source files
    MSI (s) (64:AC) [16:26:02:861]: SECUREREPAIR: SecureRepair Failed. Error code: 3e5E78034B8
    Action start 16:26:02: ProcessComponents.
    MSI (s) (64:AC) [16:26:02:876]: 
    Error 997. Overlapped I/O operation is in progress.
    MSI (s) (64:AC) [16:26:02:923]: Machine policy value 'DisableRollback' is 0
    MSI (s) (64:AC) [16:26:02:923]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    Action ended 16:26:02: ProcessComponents. Return value 3.
    MSI (s) (64:AC) [16:26:02:923]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (64:AC) [16:26:02:923]: No System Restore sequence number for this installation.
    MSI (s) (64:AC) [16:26:02:923]: Unlocking Server
    Action ended 16:26:02: INSTALL. Return value 3.
    Property(S): DiskPrompt = [1]
    Property(S): InstallMode = Typical
    Property(S): UpgradeCode = {6B5C1D2B-86A6-4714-9BC6-5E32D608E551}
    Property(S): WelcomeBmp = WelcomeBmp
    Property(S): OPENREADME = 1
    Property(S): CurrentSetupBootstrap_64 = c:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\
    Property(S): GAC_64 = c:\Windows\Gac\
    Property(S): GAC_32 = c:\Windows\Gac_32\
    Property(S): Ver_64 = c:\Program Files\Microsoft SQL Server\110\
    Property(S): SetupBootstrap_64 = c:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\
    Property(S): CurrentSetupHelpNative_64_1033 = c:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\1033_ENU_LP\x64\1033\help\
    Property(S): CurrentSetupBootstrapNative_64_1033 = c:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\1033_ENU_LP\x64\1033\
    Property(S): CurrentSetupBootstrapRes_64_1033 = c:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\Resources\1033\
    Property(S): Shared_64 = c:\Program Files\Microsoft SQL Server\110\Shared\
    Javier Villegas |
    @javier_vill | http://sql-javier-villegas.blogspot.com/
    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

    Judging by the error message I would say the setup is trying to access a network share that is no longer available to the node due to the failover. How many instances are installed in each node?
    Open resource monitor and, in the disk section, check which files are being accessed by I/O threads. See if there are any files in use that the SP2 installer would supposedly try to access.
    If possible, save the resource monitor results, failback the instance, and check disk usage in the other node to try to detect any abnormal disk access.

Maybe you are looking for

  • Multiple Nanos in Family one Nano update download?

    When ever a new version of the nano software comes up each sync takes awhile because it has to download the 54MB updater for each of my families memeber nano. Is there a way to have the download happen only once and yet update each individual nano wh

  • Pb pour desinstaller adobe acrobat  5.0.

    Dans windows 7 impossibilité de desinstaller ou modifier .adobe acrobat 5.0 message affiché : le fichier journal C:/Programfiles/common files/adobe/acrobat 5.0/NT/uninst.isu n'est pas le fichier requis ou ses données sont altérées. Abandon de la dési

  • Setting the Image Dimensions

    Hi, I'm trying to place objects at various points on a frame. I need to set the coordinates system so that the frame is divided from 1 to 255, (bottom left to top right) regardless of how big it is in pixels. Any suggestions? Thanks for your time, at

  • I can't download Lion on my MacBook Pro today is something wrong with the site?

    I am trying to download Lion for the first time. I have a MacBook Pro 2.6Ghz Intel Core 2 Duo with 4 GB 667 MHz DDR2 SDRAM and the Apple Store is not responding. Is anyone else having problems? Thanks

  • Re: Problems with Informix

    Before starting the node manager, make sure the environment variable LIBPATH includes the paths /usr/informix/lib:/usr/informix/lib/esql. Also make sure that the file /usr/informix/lib/esql/libsqlshr.a is there. Hope this helps. -Joon ----- Begin Inc