Is Integration service mandatory while configuring SQL Server in Cluster

Hi All,
SQL 2012: Standard Edition
I have configured DB Cluster on Windows Server 2008R2.
While selecting the features I have only preferred default services not any Analysis, Reporting or
Integrations.
After the DB Cluster is successfully setup I am warned  by colleagues that it is not possible to create
SSIS Packages (I do agree and client does not have requirement on this as well) but also informed that even
SQL Maintenance plans like Rebuild, Reorganize, update statistics or backups and etc.,
are not possible to configure. Is that true?
I am worried and immediately checked by configuring backup
maintenance plan in both the nodes and
could ableto
create and run the plans successfully. Now it is clear that integration service is not required to configure maintenance plans but
still concerned about these maintenance plans whether they get any issues in
future executions. And also please clarify whether selecting or not selecting Analysis, Reporting or Integrations
effect Always On high availability if I want to configure.
Please suggest. Thank You
Regards,
Kalyan
Grateful to your time and support. Regards, Shiva

Nope you dont have to install those feature if you are not going to use them.
You don't need SSIS installed to execute maint plans:
http://sqlblog.com/blogs/tibor_karaszi/archive/2009/08/26/do-maintenance-plans-require-ssis.aspx
http://beyondrelational.com/modules/2/blogs/104/posts/11777/sql-server-execute-package-utility-requires-integration-services-to-be-installed-by-one-of-these-edi.aspx
http://sivasql.blogspot.in/2009/05/do-we-need-ssis-to-create-maintenance.html

Similar Messages

  • SETUP ERROR WHILE INSTALLING SQL SERVER 2008 R2

    Hi ,
    I'm coming across the following error while installing Microsoft SQL Server 2008R2
    SQL Server Setup has encountered the following error:
    The required MSI package 'D:\SQL Sever 2008 R2 Developer Edition\x86\setup\sql_engine_core_shared_msi\sql_engine_core_shared.msi' doesn't exist.
    Error code 0x84B20001.
    I tried reinstalling the same. But results the same.
    Please suggest. :)

    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
    rerun SQL Server Setup.
      Exit code (Decimal):           -2068709375
      Exit facility code:            1202
      Exit error code:               1
      Exit message:                  The required MSI package 'D:\softwares\SQL Sever 2008 R2 Developer Edition\x86\setup\sql_engine_core_shared_msi\sql_engine_core_shared.msi'
    doesn't exist.
      Start time:                    2013-12-31 20:47:50
      End time:                      2013-12-31 20:55:44
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0xD2FD83B3%400xC2B0B50B%401202%401
    Machine Properties:
      Machine name:                  SAMPLE-PC
      Machine processor count:       2
      OS version:                    Windows 7
      OS service pack:              
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2005                                                         
    Tools                                    1033                
    Express Edition      9.2.3042        No       
      Sql Server 2005                                                         
    ToolsClient                              1033                
    Express Edition      9.2.3042        No       
      Sql Server 2005                                                         
    ToolsClient\Connectivity                 1033                 Express Edition     
    9.2.3042        No       
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services                
    1033                 Express Edition      10.1.2531.0     No       
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication                  
    1033                 Express Edition      10.1.2531.0     No       
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         D:\softwares\SQL Sever 2008 R2 Developer Edition\x86\setup\
      Installation edition:          DEVELOPER
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 TEST
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  TEST
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            SAMPLE-PC\SAMPLE
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\ConfigurationFile.ini
      CUSOURCE:                     
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,SSMS,ADV_SSMS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
      FTSVCPASSWORD:                 *****
      HELP:                          False
      IACCEPTSQLSERVERLICENSETERMS:  False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    TEST
      INSTANCENAME:                  TEST
      ISSVCACCOUNT:                  TEST
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                    
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  SAMPLE-PC\TEST
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 TEST
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           SAMPLE-PC\SAMPLE
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    0
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Analysis Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Integration Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Business Intelligence Development Studio
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\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.ChainerInvalidOperationException
        Message:
            The required MSI package 'D:\softwares\SQL Sever 2008 R2 Developer Edition\x86\setup\sql_engine_core_shared_msi\sql_engine_core_shared.msi' doesn't exist.
        Data:
          ChainerInvalidOperationExceptionData = InstallPackage
          DisableWatson = true
        Stack:
            at Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia, InstallAction pkgAction)
            at Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
            at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)

  • Errro while installing sql server 2012 express edition on Windows 8 -64 version

    Hi,
    Im trying to install sql server 2012 express edition on windows 8 machine(64 bit),however im getting same error every time.
    The following error has occurred:
    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337
    i've googled and checked all prerequisite which is already installed.so not finding the reason behind this error.  
    it would be great if any one can help on resolving this error.
    Thanks in advance
    Regards
    Ritesh

    Hi ,
    Thanks for help. here is the log summary text
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2068051679
      Start time:                    2014-02-05 12:30:44
      End time:                      2014-02-05 12:36:21
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
      Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.
    Machine Properties:
      Machine name:                  IDEA-PC
      Machine processor count:       4
      OS version:                    Future Windows Version
      OS service pack:              
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services                
    1033                 Developer Edition    10.50.1600.1    No       
      SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         SQL Server Replication                  
    1033                 Developer Edition    10.50.1600.1    No       
      SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text and Semantic Extractions for Search 1033                
    Developer Edition    10.50.1600.1    No       
      SQL Server 2008 R2                                                      
    Management Tools - Basic                 1033                 Developer Edition   
    10.50.1600.1    No       
      SQL Server 2008 R2                                                      
    Management Tools - Complete              1033                 Developer Edition    10.50.1600.1   
    No       
      SQL Server 2008 R2                                                      
    Client Tools Connectivity                1033                 Developer Edition    10.50.1600.1   
    No       
      SQL Server 2008 R2                                                      
    Client Tools Backwards Compatibility     1033                 Developer Edition    10.50.1600.1    No       
      SQL Server 2008 R2                                                      
    Client Tools SDK                         1033                
    Developer Edition    10.50.1600.1    No       
      SQL Server 2008 R2                                                      
    Integration Services                     1033                 Developer Edition   
    10.50.1600.1    No       
    Package properties:
      Description:                   Microsoft SQL Server 2012 Service Pack 1
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      SPLevel:                       0
      Installation location:         c:\b33170cf028067db5b8335d2\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:         Disabled
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:            
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    true
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, 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:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SQLFASHION
      INSTANCENAME:                  SQLFASHION
      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:                  <empty>
      SQLCOLLATION:                  Latin1_General_CI_AI
      SQLSVCACCOUNT:                 NT Service\MSSQL$SQLFASHION
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           idea-pc\lenovo
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\ConfigurationFile.ini
    Detailed results:
      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:                SQL Server Common Files
      Component error code:          2337
      Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\sql_common_core_Cpu64_1.log
      Error description:             The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337.
      Error help link:              
      Feature:                       SQL Server Replication
      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:                SQL Server Common Files
      Component error code:          2337
      Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\sql_common_core_Cpu64_1.log
      Error description:             The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337.
      Error help link:              
      Feature:                       SQL Client Connectivity
      Status:                        Passed
      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\SystemConfigurationCheck_Report.htm

  • The unattended installation failed while installing SQL Server 2008 R2 ????

    Hi gurus,
    I got an error while installing SQL Server 2008 R2 in Windows 2008 R2 standard 64 bit operating system.
    LOG file*
    Customized installation of SQL Server 2008R2 for SAP *
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlWriter_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Business Intelligence Development Studio
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SystemConfigurationCheck_Report.htm
    1/16/2012 10:13:34 PM
    Message Box "Installation failed"
    The unattended installation failed.
      Installation Step: The unattended installation failed.
      Return Code:       -2068052377
      Log File:          C:\Windows\SQL4SAP.log
    Check the log file above.
    See SAP note 1144459 for known issues.
    Result: vbOK
    Registry settings (2/2):
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{2b9034f3-b661-4d36-a5ef-60ab5a711ace}
    WRITE(REG_DWORD): 4
    1/16/2012 10:37:32 PM
    Quit script with return code 1
    Please help me out with this issue.
    REGARDS,
    Raj

    Hello Raj,
    MS SQL DB installation specific steps for SAP system is clearly documented in SAP Installation guide. Please download from SMP, read it carefully and install as mentioned in the guide.
    Hope it helps.
    Thanks,
    Siva Kumar

  • Attempted to perform an unauthorized operation error on windows 8.1 while installing SQL server 2008

    Hi,
    I am getting the error "Attempted to perform an unauthorized operation" on windows 8.1 while installing
    SQL server 2008.
    The specific error is The error is Attempted to perform an unauthorized operation."
    at stepSqlBrowserConfigAction_install_ConfigNonRC_Cpu32 .
    I have tried everything from copying to the C drive. I am the admin on the machine. I also checked access in registry. It already has acesss to HKLM\System\CurrentControlSet\Control\WMI\security
    Can someone comment on how to resolve this issue. I also tried NT
    AUTHORITY\SYSTEM but getting the same error.
    Any help would be appreciated.

    Hello,
    Please note that SQL Server 2008 requires Service Pack 3 (SP3) to make it compatible with
    Windows 8.1. Please perform an slipstream installation of SQL Server 2008 + SP3:
    http://support.microsoft.com/kb/955392
    If it fails again, please share with us the Summary.txt log file and the details.txt log file. The following article
    may help you locate those files on disk::
    http://msdn.microsoft.com/en-us/library/ms143702(v=sql.100).aspx
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Service Accounts for Reporting Service in SQL Server Failover Cluster setup

    I am setting up 2 Report Services (SSRS) in SQL Failover Clustering (Version: 2012SP1) on Windows 2012, as part of scale out architecture.
    There are 2 options to configure the service account for SSRS:
    Option 1) Using domain accounts, as what I have done for DB Engine and SQL Agent.
    Option 2) accept the default, which is virtual account for SSRS. Per documentation URL:
    http://msdn.microsoft.com/en-us/library/ms143504.aspx
    which is the recommended one? is it option 2?
    There is security note on above URL as well, but does not clearly mention that option 1 is not recommended.
    Security Note:  Always run SQL Server services by using the lowest possible user rights. Use a MSA or  virtual account when possible. When MSA and virtual accounts are not possible, use a specific low-privilege user account or domain account instead
    of a shared account for SQL Server services. Use separate accounts for different SQL Server services. Do not grant additional permissions to the SQL Server service account or the service groups. Permissions will be granted through group membership or granted
    directly to a service SID, where a service SID is supported.
    Thanks very much for your help!

    Hi Luo Donghua,
    In SQL Server Failover Cluster Instance, personally two options can run well. If you use the virtual account for SQL Server Reporting Service. Virtual accounts in Windows Server 2008 R2 and Windows 7 are managed local accounts that provide the features to
    simplify service administration. The virtual account is auto-managed, and the virtual account can access the network in a domain environment.
    Of cause, you can also use domain accounts in your clustering. 
    Just make sure your service account is set up here, or that it is using a proper built-in account.For more information, see:http://ermahblerg.com/2012/11/08/cluster-ssrs-in-2008/
    Thanks,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Cluster resource 'Analysis Services' of type 'Generic Service' in clustered role 'SQL Server' failed.

    Windows Server 2012 R2
    SQL Server 2012
    After a recent cluster failover from node 1 to node 2, the Analysis Services role is in a failed state, with the service stopped. When attempting to start the service, there are two error messages captured in Failover Cluster Manager:
    Log Name:      System
    Source:        Microsoft-Windows-FailoverClustering
    Date:          4/10/2014 11:48:49 AM
    Event ID:      1042
    Task Category: Generic Service Resource
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:      HQ-HASQL-1.sbgnet.int
    Description:
    Generic service 'Analysis Services (HASQL)' failed with error '1067'. Please examine the application event log.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
        <EventID>1042</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>16</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-04-10T15:48:49.752168200Z" />
        <EventRecordID>26212</EventRecordID>
        <Correlation />
        <Execution ProcessID="9036" ThreadID="14748" />
        <Channel>System</Channel>
        <Computer>HQ-HASQL-1.sbgnet.int</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="ResourceName">Analysis Services (HASQL)</Data>
        <Data Name="Status">1067</Data>
      </EventData>
    </Event>
    Log Name:      System
    Source:        Microsoft-Windows-FailoverClustering
    Date:          4/10/2014 11:48:49 AM
    Event ID:      1069
    Task Category: Resource Control Manager
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:      HQ-HASQL-1.sbgnet.int
    Description:
    Cluster resource 'Analysis Services (HASQL)' of type 'Generic Service' in clustered role 'SQL Server (HASQL)' failed.
    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster
    Manager or the Get-ClusterResource Windows PowerShell cmdlet.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
        <EventID>1069</EventID>
        <Version>1</Version>
        <Level>2</Level>
        <Task>3</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-04-10T15:48:49.752168200Z" />
        <EventRecordID>26213</EventRecordID>
        <Correlation />
        <Execution ProcessID="6464" ThreadID="9076" />
        <Channel>System</Channel>
        <Computer>HQ-HASQL-1.sbgnet.int</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="ResourceName">Analysis Services (HASQL)</Data>
        <Data Name="ResourceGroup">SQL Server (HASQL)</Data>
        <Data Name="ResTypeDll">Generic Service</Data>
      </EventData>
    </Event>
    With just these generic error messages being present, this has been difficult to diagnose. Some research has yielded possible resolutions of the Event Viewer log being full, .NET corruption, missing registry entries, but none of those seem to be the issue
    (Event Viewer logs cleared, Analysis services is working on the same physical servers in a different cluster, and the registry entries was only a supported issue for SQL Server 2008 and 2008 R2).
    Any help would be greatly appreciated.

    Bring up Configuration Manager, look at binary path for SSAS.  Make sure BOTH folders exist.  Sometimes with failovers mappings get screwed up.

  • Activate Reporting Services on My Sharepoint SQL SERVER Databse ?

    Hi,
    I have small sharepoint farm (1 FW and 1 SQL).
    I can't find if it's recommended or not to activate and use Reporting Services on the SHAREPOINT SQL SERVER Instance ?
    I wouldn't want to decrease my global farm performance.
    Thank you for helping.
    Regards

    SSRS integrated must run on a server that has SharePoint installed and joined to the farm. That will have a significant impact on the SQL Database Engine server from a memory contention and CPU utilization perspective.
    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.

  • SQM uploader error while configuring BizTalk Server

    Hi, 
    I am getting following error while configuring BizTalk Server 2013 on Windows Azure VM
    Log Name:      Application
    Source:        Application Error
    Date:          8/26/2013 1:08:46 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      BizTalk2013VM
    Description:
    Faulting application name: SqmUploader.exe, version: 3.10.229.0, time stamp: 0x50fe35e2
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b8479b
    Exception code: 0xe0434352
    Fault offset: 0x0000000000009e5d
    Faulting process id: 0x988
    Faulting application start time: 0x01cea27eec7ba1b4
    Faulting application path: C:\Program Files (x86)\Microsoft BizTalk Server 2013\CEIP\SqmUploader.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: 2acf119c-0e72-11e3-9e61-00155d6120c3
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-08-26T17:08:46.000000000Z" />
        <EventRecordID>32154</EventRecordID>
        <Channel>Application</Channel>
        <Computer>BizTalk2013VM</Computer>
        <Security />
      </System>
      <EventData>
        <Data>SqmUploader.exe</Data>
        <Data>3.10.229.0</Data>
        <Data>50fe35e2</Data>
        <Data>KERNELBASE.dll</Data>
        <Data>6.1.7601.18015</Data>
        <Data>50b8479b</Data>
        <Data>e0434352</Data>
        <Data>0000000000009e5d</Data>
        <Data>988</Data>
        <Data>01cea27eec7ba1b4</Data>
        <Data>C:\Program Files (x86)\Microsoft BizTalk Server 2013\CEIP\SqmUploader.exe</Data>
        <Data>C:\Windows\system32\KERNELBASE.dll</Data>
        <Data>2acf119c-0e72-11e3-9e61-00155d6120c3</Data>
      </EventData>
    </Event>
    Any help will be highly appreciated.

    Hi Nilesh,
    Following article should help you:
    http://social.technet.microsoft.com/wiki/contents/articles/11426.windows-azure-biztalk-services-resources-on-the-technet-wiki.aspx
    I hope this helps!!!!!!
    Maheshkumar S. Tiwari|BizTalk Developer Interview Questions and Answers
    http://tech-findings.blogspot.com/

  • Error while installing SQL Server 2012 X64 SP2,

    Error while installing SQL Server 2012 X64 SP2,
     When I installed the SQL Server 2012 X64 SP1, I got the attached error.
     What might be the issue here?
     Thank you
     Best
    Jamal

    Hello,
    Are you trying to install SQL Server on a compressed or encrypted drive? SQL Server won’t install on a drive/folder with these attributes.
    Are you trying to install SQL Server on a ReFS file system? It is not supported on SQL Server 2012.
    Disable any security/antivirus software and download the media again. Mount the media (.ISO file) and try to install again.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • How to hide product key page while installing SQL server 2012 ?

    I need to hide the product key page while installing SQL server 2012 enterprise edition
    I was trying to use the following command
    Setup.exe /ACTION=Install /FEATURES=SQL /INSTANCENAME=Intuition /PID=<My product Key.
    /IACCEPTSQLSERVERLICENSETERMS
    The product key was applied , but the install screen is being shown with the Product key i have provided and it is in editable mode.
    Is there any way i can hide this SQL server product key page ?
    The reason is we are including SQL setup in our application and as per Microsoft policy we should not reveal the product key to user. If we are able to hide this from installing page , we can hide the installation command in some exe.
    Note : Customers need fulfledged versions so we can't install SQLExpress.

    Hello,
    Could you try using /Q or /QS parameter?
    http://msdn.microsoft.com/en-us/library/ms144259(v=sql.110).aspx
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Getting error while installing sql server std 2008 R2 on win 7 prof. sp1 64bit

    Hi,
    I am getting error while installing sql server std 2008 R2 on win 7 prof. sp1 64bit. I have already tried all option but fail to installation
    an error during the installation of assembly micro soft.vc80.crt

    Hi,
    I am getting error while installing sql server std 2008 R2 on win 7 prof. sp1 64bit. I have already tried all option but fail to installation
    an error during the installation of assembly micro soft.vc80.crt
    Can you please post summary.txt file here.Below link will help you in finding it.
    http://technet.microsoft.com/en-us/library/ms143702(v=sql.105).aspx
    Also with error you posted I guess it is a known issue .You need to install below package and then continue with fresh installation
    http://www.microsoft.com/en-gb/download/details.aspx?id=15336
    Please make sure before beginning fresh installation you make sure previous failed installation is removed completely.Use add remove program to remove failed SQL Server.If yu still face issue please post summary.txt file here
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Error while installing SQL Server 2008 R2 in Windows 7 SP1 machine

    Hi Team,
    Error while installing SQL Server 2008 R2 in Windows 7 SP1 machine. I can confirm this machine has .Net
    Feature enabled and with Latest version.
    TITLE: Microsoft SQL Server 2008 R2 Setup
    The following error has occurred:
    Error 25541.Failed to open XML file C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config, system error: -2147024786
    Regards,
    Muthukumar.S.P.

    Hi,
    Can you follow workaround mentioned in below msdn blog
    http://blogs.msdn.com/b/astebner/archive/2007/11/01/5826719.aspx
    As per the blog you have to open the msi log files which must be located at
    C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log
    In MSI log files search for the error mentioned in blog. Below link will help you read setup log files
    http://msdn.microsoft.com/en-gb/library/ms143702%28v=sql.105%29.aspx
    PS: Please read links carefully and patiently and if it does not solves issue please post summary.txt file and details.txt file on skydrive for analysis
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Articles

  • Error While Installing SQL SERVER 2012 on Windows Serrver 2012 R2

    I encounter the following errors while installing SQL SERVER on Windows SERVER 2012 R2, can anybody help me out?
    dotdazzle

    If you are using any system account then password is not needed. From the screenshot I see NT Authority\....  so you don't need password.
    Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog |
    Team Blog | @Twitter
    Author: SQL Server 2012 AlwaysOn -
    Paperback, Kindle

  • Can Reporting Services 2005 report on SQL Server 2012 database?

    We would like to upgrade our SQL Server from Standard 2005 to Enterprise/Standard 2012. Unfortunately, we also have a lot of reports based on Reporting Services 2005. If possible we would like avoid upgrading them at this time.
    Is it possible to run Reporting Services 2005 of SQL Server 2012? If yes then is there pre-requiste  like drivers  or dll or any other to connect SSRS 2005 to SQL server 2012?  
    If we run Reporting Services 2005 of SQL Server 2012  then do we will face performance lag issue due to version difference of SSRS 2005 and SQL server 2012?

    Moderators,
    Can anyone merge this -
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2c44351c-35b4-4208-a2b7-88fc810d53ff/can-reporting-services-2005-report-on-sql-server-2012-database?forum=sqlreportingservices
    sathya - www.allaboutmssql.com ** Mark as answered if my post solved your problem and Vote as helpful if my post was useful **.

Maybe you are looking for

  • Cumulative customer balance per item

    Hello everybody, I am looking for displaying a cumulative balance per item in a open item report. In the report, my customer want to see in a new column the cumulative balance per item. I searched in the standard report but I did not see how to calcu

  • Is it possible to print a list of files bet specific dates in PSE7?

    I am trying to print a list of all the photos inc the shot date so I can check I have scrapbook layouts for all the photos in 2009.  I can organise the photos in date order using the thumbnail view but I can't sit there with my albums and check the l

  • Set Video out

    HI , Just bought the apple composite AV cable so I can watch movies from my ipod touch on TV. But I'm having trouble actually getting it to work. In the manual I got with the composite AV cable its says 'set your ipod to send a video signal out' I ha

  • Safari 3.0.4 crashes when entering form data

    Hello, After updating to 3.0.4 here at work on windoze, I am getting consistant crashes when trying to type in any kind of form data. This includes PW fields as well as text entry fields such as this topic composition window. I can click to place the

  • Regd - Spool request

    Dear all, I have a requirement, to download the list output in PDF format. I am using the following code. This program converts the list output into spool request. But the problem is it is having number of pages is 0(We can see in SP01). Could you pl