Edition Required for SSAS 2012 Multidim Partitoning Feature

I want to know what the edition requirement is for the SSAS 2012 Multidim Partitioning feature.  In 2008 I recall that enterprise edition was required, but I cannot tell what the requirement is for 2012.  Thanks.
Mark

Actually, the BI edition also supports SSAS partitions
http://msdn.microsoft.com/en-us/library/cc645993.aspx#SSAS. BI edition doesn't support partitioning in the DB Engine though so each SSAS partition would likely most efficiently be sourced from a separate DB Engine table rather than being aligned to the
partitioning function used to partition a single fact table.
HTH, Martin
<a href="http://martinsbiblog.spaces.live.com" target="_blank">http://martinmason.wordpress.com</a>

Similar Messages

  • What oracle edition required for sap ecc and ep in one box

    hi friends
    what oracle edition required for sap ecc  installation which supports the  HA and disaster recovery plan
    10g
    1. Oracle Database Standard Edition One 10 g
    2. Oracle Database Standard Edition  10g
    3.Oracle Database Enterprise Edition  10g
    3. Oracle Database Express Edition  10g
    4. Oracle Database Personal Edition  10g
    thanks in advance  friends
    regards
    raja

    hi,
    I believe that SAP only support enterprises edition one because you'll get all database features.
    ardhian
    http://sapbasis.wordpress.com

  • SSIS Connection Manager: MSOLAP100 where is the one for SSAS 2012 ?

    I have an SSIS project under SSDT, that should process a SSAS 2012 Cube, when I setup the connection, the SSIS Connection Manager gives me only MSOLAP100 as a possible connection manager type. From my understanding this is the one for SQL 2008 R2. Where
    is the one for SSAS 2012 and how can I enable it ?
    I feel this is a bug in SSDT:
    I used another UI dialog and could create a new connection like this:
    Still it says ConnectionManagerType MSOLAP100, however in the connection string I now have Provider=MSOLAP.5, this seems to be another SSDT bug.

    If this issue can be reproduced in multiple machines, then you can you can submit a feedback at
    http://connect.microsoft.com/SQLServer/Feedback and hope it is released in the next release of service pack or product.

  • SQL Server 2012 Edition required for my case??

    Hi,
    I am setting up a SharePoint 2013 BI environment with minimal servers. Below is the configuration:
    1) WFE1 - Front End Server Role
    2) APP1 - Application Server Role with SSRS 2012, SSAS in SharePoint mode.
       SQL Server 2012 BI edition is used here for SSRS and SSAS in SharePoint mode
    3) DB Server  - SharePoint content databases only
    - Can this SQL Server be standard edition ? or does this server also need to have minimum BI features which means it should be BI or Enterprise edition?
    Thanks
    Sandeep
    Sandeep Nakarmi www.snakarmi.me

    Hi Sandeep,
    Thanks for posting your query, Below are the URLs that describe the situation to USE the SQL SERVER Standard or Enterprise Edition for BI features. Kindly go through these URLs once to get the difference.
    http://searchsqlserver.techtarget.com/feature/When-to-consider-SQL-Server-Enterprise-Edition
    http://searchsqlserver.techtarget.com/feature/SQL-Server-Standard-Edition-Why-its-worth-the-cost
    Of course, you will get more features for BI in as sequence SQL Server Edition mentioned below
    Express < Standard < Enterprise
    Moreover, browse the below mentioned URL to enable BI features in SharePoint
    http://blogs.technet.com/b/ldusolier/archive/2014/05/19/use-of-bi-capabilities-in-sharepoint-2013-with-sql-server-2012.aspx
    I hope this is helpful to you, mark it as Helpful.
    If this works, Please mark it as Answered.
    Regards,
    Dharmendra Singh (MCPD-EA | MCTS)
    Blog : http://sharepoint-community.net/profile/DharmendraSingh

  • What are the host network requirements for a 2012 R2 failover cluster using fiber channel?

    I've seen comments on here regarding how the heartbeat signal isn't really required anymore - is that true?  We started using Hyper-V in its infancy and have upgraded gleefully every step of the way.  With 2012 R2, we also upgraded from 1gb iSCSI
    to 8GB Fiber Channel.  Currently, I have three NICs in use on each host.  One for "No cluster communication" on it's own VLAN.  Another for "Allow cluster network communication on this network" but NOT allowing clients, on
    a different VLAN.  And lastly the public network which allows cluster comms and clients on it (public VLAN).
    Is it still necessary to have all three of these NICs in use?  If the heartbeat isn't necessary any more, is there any reason to not have two public IPs and do away with the rest of the network?  (two for fault tolerance)  Does Live Migration
    still use Ethernet if FC is available?  I wasn't sure what all has changed with these requirements since Hyper-V first came out.
    If it matters, we have 5 servers w/160GB RAM, 8 NICs, dual HBAs connected to redundant FC switches, going to two SANs.  We're running around 30 VMs right now.  
    Can someone share their knowledge with me regarding the proper setup for my environment?  Many Thanks!

    Hi,
    You can setup cluster with a single network but that leaves you with single point of failure on the Networking front, it is still recommended to have a heartbeat network.
    Live migration would still happen though Ethernet, it has nothing to do with FC. Don't get confused, you had iSCSI for storage which used one of your VLAN and now you have FC for your storage.
    Your hardware specs looks good. You can set up the following networks -
    1. Public Network - Team two or more NICs (based on bandwidth aggregation)
    2. Heartbeat Network - Don't use teamed Adaptor
    3. Live Migration - Team two or more NICs (based on bandwidth aggregation)
    Plan properly and draw guidelines to visualize and to remove single point of failure at all points.
    Feel free to ask if you have some more queries.
    Regards
    Prabhash

  • SharePoint 2013: Edition requirement for multi tier setup.

    Dear all,
    I am planning to setup a high availability 3-tier SharePoint farm.
    My question is which edition of SharePoint 2013 should i purchase? Standard version or enterprise version?
    My requirement is just a simple document management system.
    Any help/guides would be much appreciated.
    Many thanks 
    Regards
    vinay

    You can use any edition for high availability on the SharePoint side: Foundation, Standard, or Enterprise.
    SQL Server is a different story, you'll want to look at the options for high availability available with each edition of SQL Server.
    http://msdn.microsoft.com/en-us/library/cc645993.aspx#High_availability
    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.

  • Hardware requirement for SSAS

    We have a requirement to load 50 Billion FACT rows from Netezza in a SSAS Cube . We plan to have a MOLAP cube. Please suggest what should be the ideal SSAS Server hardware requirement to handle this request.

    there is not enough detail here to properly answer your question.
    how wide is the fact table?
    what is the size of the fact table in the RDBMS?
    how many dimensions?
    query response requirements?
    budget?
    etc
    btw, I'm a bit curious, so if you don't mind me asking...why are you going to place a SSAS Cube on top of Netezza?
    BI Developer and lover of data (Blog |
    Twitter)

  • Ports Required for SCCM 2012 Distribution point

    I think below are the port need to open for distribution point instalaltion
    Site Server -- > Distribution Point
    SMB 445 TCP
    RPC Endpoint Mapper 135 UDP and TCP
    RPC dynamic TCP
    my question here is for install Distribution point instalaltion , only
    Site Server -- > Distribution Point one way port open  is enough? or do we need to open both ways?

    One way is enough for a standard Distribution Point. All distribution is initiated by your Primary site server by the Package Transfer Manager.
    Regards,
    Nickolaj Andersen | www.scconfigmgr.com | @Nickolaja

  • BWA Requirement for MSSQL 2012

    Hello Friends,
    We are planning to migrate our platform combination to Microsoft 2012 & SQL 2012 database. Currently we are heavily dependent on BWA and we are using 7.20 Release 29 with Oracle database on BW system.
    I would like to understand based on your experience what will happen to our BWA environment after ORACLE --> SQL migration.
    is all connectivity methods would still be supported?
    how does the roll ups work (functionally)?
    does MS-2012 db has any issues working out with BWA?
    how MS-SQL 2012 column store would play in this situation?
    Any timely information would help us estimating the efforts and approach.
    Thanks,
    Kamal Bhargava

    Hi Kamal,
    As a best recommendation please continue to use BWA, as it offers faster solution to your whole BW system and not only the database. As of any incompatibility of SQL with BWA it's unknown, as it should work, in other words you should not encounter any issues as per BWA PAM link below:
    https://service.sap.com/sap/support/pam?hash=s%3DBusiness%2520Warehouse%2520Accelerator%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D01200314690900002143%26pt%3Dg%257Cd
    Regards,
    Diego Seben.

  • Required access for SCCM 2012 R2 Client End

    Hi all,
    What is minimum level of access required for SCCM 2012 client machines management ( Deploy , Discovery , agent install …etc) , we have an account called clientdeploy , is that account is mandatory
    to have local administrators  privilege on all client machine to manage everything , is that Microsoft recommended one ?
    Sengo

    No, Not required this account to be local admin in all client.
    If you want access required for sccm 2012, for deploying app., O.s and managing client, this account must be member of sms group such as configmgr remote control users for remote tool
    For more details, you can refer below link
    http://technet.microsoft.com/en-us/library/hh427337.aspx
    Also I recommended to ask your question in
    SCCM Forum
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

  • Hotfix for server 2012 as similar to server 2008 - KB 2135160

    Is there any hotfix available as similar to server 2008  - KB 2135160   same required for  HyperV
    2012 

    We are implementing EMC networker backup on HyperV 2012. When backup stat the server stop randomly. 
    Based on the event logged on server after log check the following was found :
    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009e (0xfffffa80622fe900, 0x000000000000003c, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052814-26676-01.
    During further analysis of the dumps:
    16: kd> .bugcheck
    Bugcheck code 0000009E
    Arguments fffffa80`62361780 00000000`0000003c 00000000`00000000 00000000`00000000
    16: kd> !process fffffa8062361780
    GetPointerFromAddress: unable to read from fffff801521cf000
    PROCESS fffffa8062361780
        SessionId: none  Cid: 0c74    Peb: 7f615f18000  ParentCid: 0454
        DirBase: 103c70000  ObjectTable: fffff8a001d2f040  HandleCount: <Data Not Accessible>
       clussvc.exe
        VadRoot fffffa80623949d0 Vads 385 Clone 0 Private 4314. Modified 1724. Locked 35.
        DeviceMap fffff8a00000c5d0
        Token                             fffff8a001d34930
        ReadMemory error: Cannot get nt!KeMaximumIncrement value.
        fffff78000000000: Unable to get shared data
        ElapsedTime                       00:00:00.000
        UserTime                          00:00:00.000
        KernelTime                        00:00:00.000
        QuotaPoolUsage[PagedPool]         0
        QuotaPoolUsage[NonPagedPool]      0
        Working Set Sizes (now,min,max)  (7821, 50, 345) (31284KB, 200KB, 1380KB)
        PeakWorkingSetSize                8056
        VirtualSize                       128 Mb
        PeakVirtualSize                   133 Mb
        PageFaultCount                    140829
        MemoryPriority                    BACKGROUND
        BasePriority                      13
        CommitCharge                      5761
            *** Error in reading nt!_ETHREAD @ fffffa806231b680
    16: kd> !thread
    GetPointerFromAddress: unable to read from fffff801521cf000
    THREAD fffff88003540540  Cid 0000.0000  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 10
    Not impersonating
    GetUlongFromAddress: unable to read from fffff801520eecf0
    Owning Process            fffff801521c9200       Image:         <Unknown>
    Attached Process          fffffa80610d9040       Image:         System
    fffff78000000000: Unable to get shared data
    Wait Start TickCount      83923437    
    Context Switch Count      81662025            
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    UserTime                  00:00:00.000
    KernelTime                00:00:00.000
    Win32 Start Address nt!KiIdleLoop (0xfffff80151efa960)
    Stack Init fffff8800355dc90 Current fffff8800355dc20
    Base fffff8800355e000 Limit fffff88003558000 Call 0
    Priority 16 BasePriority 0 UnusualBoost 0 ForegroundBoost 0 IoPriority 0 PagePriority 0
    Child-SP          RetAddr           : Args to Child                                              
                : Call Site
    fffff880`0355d7f8 fffff880`054df845 : 00000000`0000009e fffffa80`62361780 00000000`0000003c 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0355d800 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : netft!NetftProcessWatchdogEvent+0xdd
    The defunct process is the CLUSVC.exe which is the cluster service.
    EMC support checked further for a fix for this issue, and found that it’s a reported issue with Hyper-V and this following article has the hotfix patch for 2008 R2: KB 2135160
    Now stuck for solution for Hyper 2012, is there any hotfix available?
    Plz help
    Regards
    Nitin

  • SQL Server 2012 installation failure An error occurred for a dependency of the feature causing the setup process for the feature to fail.

    I am installing SQL Server 2012 Developer (from ISO image written on DVD), my machine has Windows 7 (Edit: Windows 7 with service pack 1) on it. This machine already has SQL Express and SQL 2008 R2 Express installed in it.
    On running 2012 setup it goes fine from Setup Support Rules to Installation Progress. In  Installation Progress after some progress installation fails.
    Windows show the following components couldn't installed:
    Managment Tools Complete  Failed. Client Tools Connectivity Failed. Client Tools SDK Failed. Client Tools Backwards Compantibility Failed. Managment Tools Basic Failed. SQL Server Data Tools Failed. Reporting Services -Native Failed. Database Engine
    Services Failed. Data Quality Services Failed. full-Text and Semantic Extractins for Search Failed. SQL Server Replication Failed. Integration Services Failed. Analysis Services Failed. SQL Client Connectivity SDK Failed.
    In detail for failure of every component it provide these details:
    Action required:
    Use the following information to resolve the error, and then try the setup process again.
    Feature failure reason:
    An error occurred for a dependency of the feature causing the setup process for the feature to fail.
    In summary log file it provide the following details:
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2068643839
      Start time:                    2012-07-31 16:23:37
      End time:                      2012-07-31 16:33:32
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for Adv_SSMS:        Use the following information to resolve the error, and then try the setup process again.
      Next step for Conn:            Use the following information to resolve the error, and then try the setup process again.
      Next step for SDK:             Use the following information to resolve the error, and then try the setup process again.
      Next step for BC:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SSMS:            Use the following information to resolve the error, and then try the setup process again.
      Next step for BIDS:            Use the following information to resolve the error, and then try the setup process again.
      Next step for RS:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
      Next step for DQ:              Use the following information to resolve the error, and then try the setup process again.
      Next step for FullText:        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.
      Next step for IS:              Use the following information to resolve the error, and then try the setup process again.
      Next step for AS:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SNAC_SDK:        Use the following information to resolve the error, and then try the setup process again.
    Machine Properties:
      Machine name:                  Haansi-PC
      Machine processor count:       4
      OS version:                    Windows 7
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      SQL Server 2005      SQLEXPRESS           MSSQL.1                       
    Database Engine Services                 1033                 Express Edition     
    9.4.5000        No        
      SQL Server 2005      SQLEXPRESS           MSSQL.1                       
    SQL Server Replication                   1033                 Express Edition     
    9.4.5000        No        
      SQL Server 2005      SQLEXPRESS           MSSQL.1                       
    SharedTools                              1033                
    Express Edition      9.4.5000        No        
      SQL Server 2005                                                         
    Tools                                    1033                
    Express Edition      9.4.5000        No        
      SQL Server 2005                                                         
    ToolsClient                              1033                
    Express Edition      9.4.5000        No        
      SQL Server 2005                                                         
    ToolsClient\Connectivity                 1033                 Express Edition     
    9.4.5000        No        
      SQL Server 2008 R2   SQLSERVER08EXPR2     MSSQL10_50.SQLSERVER08EXPR2    Database Engine Services                 1033                
    Express Edition      10.50.1617.0    No        
      SQL Server 2008 R2   SQLSERVER08EXPR2     MSSQL10_50.SQLSERVER08EXPR2    SQL Server Replication                   1033                
    Express Edition      10.50.1617.0    No        
      SQL Server 2008 R2                                                      
    Management Tools - Basic                 1033                 Express Edition     
    10.50.1617.0    No        
      SQL Server 2012                                                         
    LocalDB                                  1033                
    Express Edition      11.0.2318.0     No        
      SQL Server 2012                                                         
    Reporting Services - SharePoint                                                   
    11.0.2100.60    No        
    Package properties:
      Description:                   Microsoft SQL Server 2012
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      SPLevel:                       0
      Installation location:         F:\x64\setup\
      Installation edition:          Developer
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      false
      AGTSVCACCOUNT:                 NT Service\SQLAgent$SS2012
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Data
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  TABULAR
      ASSVCACCOUNT:                  NT Service\MSOLAP$SS2012
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Manual
      ASSYSADMINACCOUNTS:            PC\Haansi
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, BIDS, CONN, IS, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SS2012
      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:                    SS2012
      INSTANCENAME:                  SS2012
      ISSVCACCOUNT:                  NT Service\MsDtsServer110
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  NT Service\ReportServer$SS2012
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Manual
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQL$SS2012
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           Haansi-PC\Haansi
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    0
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       SQL Server Data Tools
      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.
      Feature:                       Reporting Services - Native
      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.
      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.
      Feature:                       Data Quality 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.
      Feature:                       Full-Text and Semantic Extractions for Search
      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.
      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.
      Feature:                       Integration 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.
      Feature:                       Analysis 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.
      Feature:                       SQL Client Connectivity SDK
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, and then 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\20120731_161013\SystemConfigurationCheck_Report.htm

    Please help. 
    I did what you suggested, but, still got error message to install SQL server data tools: Here is the log.
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2068037632
      Start time:                    2014-09-29 15:05:38
      End time:                      2014-09-29 15:15:55
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for SSDTBI_VS2012:   Use the following information to resolve the error, and then try the setup process again.
    Machine Properties:
      Machine name:                  MSBI
      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:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered  Configured
      SQL Server 2008                                                          Management Tools - Basic  
                  1033                 Express Edition      10.0.1600.22    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Database Engine Services                 1033      
              Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            SQL Server Replication                   1033      
              Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033                
    Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Data Quality Services                    1033    
                Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSAS11.MSSQLSERVER             Analysis Services                        1033  
                  Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSRS11.MSSQLSERVER             Reporting Services - Native              1033        
            Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Management Tools - Basic  
                  1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Management Tools - Complete  
               1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Client Tools Connectivity  
                 1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Client Tools Backwards Compatibility
        1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Client Tools SDK      
                      1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          SQL Server Data Tools    
                   1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Integration Services    
                    1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Reporting Services - SharePoint
                                                       11.0.2100.60    No         Yes    
    Package properties:
      Description:                   Microsoft SQL Server 2012 Service Pack 1
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      Installation location:         C:\9f7a58aa5d6d76ffe6be968a4ad339f5\x86\setup\
      Installation edition:          Express
      Slipstream:                    True
      SP Level                       1
      Patch Level:                   11.1.3128.0
    Product Update Status:
      Success: KB 2674319, KB 2793634
    Product Updates Selected for Installation:
      Title:                         Service Pack 1
      Knowledge Based Article:       KB 2674319
      Version:                       11.1.3000.0
      Architecture:                  x86
      Language:                      1033
      Title:                         SQL Server 2012 SP1 GDR Product Update
      Knowledge Based Article:       KB 2793634
      Version:                       11.1.3128.0
      Architecture:                  x86
      Language:                      All
      Update Source:                 MU
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 <empty>
      AGTSVCPASSWORD:                <empty>
      AGTSVCSTARTUPTYPE:             Manual
      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:                    false
      ENU:                           true
      ERRORREPORTING:                true
      FEATURES:                      SSDTBI_VS2012, 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 (x86)\Microsoft SQL Server\
      INSTANCEID:                    <empty>
      INSTANCENAME:                  <empty>
      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:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 <empty>
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           <empty>
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  true
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\ConfigurationFile.ini
    Detailed results:
      Feature:                       SQL Server Data Tools - Business Intelligence for Visual Studio 2012
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft Visual Studio Tools for Applications 2012
      Component error code:          0x80044000
      Component log file:            C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\VSTA2012_LangsSupport_Cpu32_1.log
      Error description:             VS Shell 2012 installation has failed with exit code -2147205120.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3436.0&EvtType=VSTA2012_LangsSupport%40Install%400x-2147205120
      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 (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\SystemConfigurationCheck_Report.htm

  • When I highlight photo's in bridge and then click open in camera raw this message comes up... Camera Raw Editing Is not enabled...Camera raw editing requires that a qualifying product has been launched at least once to enable this feature. I have used cam

    When I highlight photo's in bridge and then click open in camera raw this message comes up... Camera Raw Editing Is not enabled...Camera raw editing requires that a qualifying product has been launched at least once to enable this feature. I have used camera raw a different way but it won't seem to work with bridge.

    Have you opened Photoshop or any other Adobe app that Bridge works with?  You need to do this if you've upgraded PS or just signed up for CC.

  • Is there a 32 Bit edition available for windows server 2012 and windows server 2008

    Dear All,
    Is there a 32 Bit edition available for windows server 2012 and windows server 2008?
    Regards,
    Ahmed

    Hi,
    Quote:
    All editions of Windows Server 2008 R2 are 64-bit only.
    Reference link below(session Supported upgrade paths):
    https://technet.microsoft.com/en-us/library/dd379511(v=ws.10).aspx
    And based on MS official description about system requirement for Windows Server 2012/2012 R2, we may find out that they only has 64 bit OS.
    Best Regards,
    Eve Wang
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Certificate Requirement for Microsoft RDS 2012

    Hi All,
    I planning to deploy RDS VDI and remote app service, Please help me to understand the certificate
    requirement for server authentication, publication, SSO , etc.
    Internet URL is
    https://RDSVDI.domain.net
    My servers are in .local 
    RD Licensing Server--------RDSLICSVR.Domain.LOCAL
    RD Connection Broker-----RDSCB.Domain.LOCAL
    RD Web Access------------RDSWEBSVR.Domain.LOCAL
    RD Session Host-----------RDSSHSVR.Domain.LOCAL
    RD Visualization Host-------RDSVHSVR.Domain.LOCAL
    RD Gateway Server -------RDGWSVR.Domain.LOCAL
    What kind of Certificate do i required to launch Desktop and RemoteApp without any error.

    Hi,
    1. I would recommend a wildcard certificate (*.domain.net) purchased from a trusted public authority such as GoDaddy, VeriSign, Thawte, etc.  This wildcard certificate would be used for all RDS purposes.
    2. On the internal network you will need to create a DNS zone for domain.net with A records pointing to the private ip addresses, similar to the following:
    rdsvdi.domain.net --> private ip address of your RD Web server
    rdscb.domain.net --> private ip address of your RD Connection Broker
    rdsgwsvr.domain.net --> private ip address of your RD Gateway server (this is only needed if you want to use RDG for internal users)
    3. On the Internet you will need DNS records similar to the following:
    rdsvdi.domain.net --> public ip address for your RD Web server
    rdgwsvr.domain.net --> public ip address for your RD Gateway server
    4. You will need to change the published FQDN for your RDS deployment to rdscb.domain.net using the cmdlet below:
    Change published FQDN for Server 2012 or 2012 R2 RDS Deployment
    http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
    5. You may need to modify your RD RAP in RD Gateway Manager. For example, you could edit the properties of the RD RAP, Network Resource tab, and select Allow users to connect to any network resource.
    6. You should make sure that all client PCs have RDP 8.1 Client (6.3.9600) installed for best results connecting to Server 2012 R2.
    7. For domain-joined PCs you may choose to set the SHA thumbprint of your certificate via group policy setting so that they will not be prompted when launching RemoteApps.
    8. It is preferred for users to use IE to connect to RD Web Access and select the Private option if possible (as long as the PC is not public).  When prompted they should Allow the Activex control to run.
    -TP

Maybe you are looking for

  • Error 472 in job queue process + ORA-472: PMON  process terminated with err

    Hi, I've an Oracle Database 11g Release 11.1.0.6.0 - 64bit Production With the Real Application Clusters option. Yesterday instance on node1 crashed. This is the extract of alert log: Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB

  • Issue with BLOB support

    All, I'm trying to use the APEX_UTIL.GET_BLOB_FILE_SRC function in a report. I'm calling the function in a report as the src attribute for an img element as follows: APEX_UTIL.GET_BLOB_FILE_SRC('P41_IMAGE_LOCATION', id). P41_IMAGE_LOCATION is configu

  • Selective Cache-control in the web server

    I am using weblogic 8.1 as the app server and Sun one 6.1 as the web server In my obj.conf of the web server we have this PathCheck fn="set-cache-control" control="private" This caches all the pages. But I don't want some pages to be cached in our si

  • Hi i got giving a iphone in a different country was wondering if i can get it unlocked?

    Hi i got giving a iphone 4 in a different country was wondering if i can get it unlocked? so that i can use another sim

  • Asset # does'nt get de-activated.

    Hi all, My environment is EAM in oracle ebs 11i I am trying to de-activate an asset after closing all work orders associated with it. But EAM does'nt let me deactivate it stating that some work order is still pending for this asset number. All work o