SQL Server 2012 Reporting Services, Report Manager - Page not found

Hi all,
I am working on migrating reports to a new server so we can upgrade to a new machine and to SQL Server 2012 SP2.  The machine is up and running on Windows Server 2012 and I have installed SQL Server EE 2012 SP2.  I have imported the three databases
from 2008R2
* Report Server
* ReportServer TempDB
* RSSubscribers
I have re-applied the encryption keys and I was thinking that everything was good to go until I went to try and manage the subscriptions on a report.  I select a report, use the drop arrow to get to manage
and then try to select any of the options such as subscriptions and I get a "Page Not Found Error"
If I take the URL and paste it in another browser, putting the previous server name in, it works fine.  So, the URL works fine...  I have no idea as to what I should do to figure out the problem.  I am considering rebuilding the whole install
just to see if that would fix it.
Thanks

Hi SqlDude,
According to your description, you have bind SSL to a Reporting Services URL Reservation. Now you find in your Report Manager, the Subscription page still start with "http://". Right?
In this scenario, we need to change setting in rsreportserver.config file. Go to rsreportserver.config in "\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer". Find <Add Key="SecureConnectionLevel" Value="0"/>.
Change the value into "3".
Acceptable values are: 
3 Most secure—Use SSL for absolutely everything.
2 Secure—Use SSL for rendering and methods that pass credentials but don't insist on it for all SOAP calls.
1 Basic Security—Accepts http but rejects any calls that might be involved in the passing of credentials.
0 Least Secure—Don't use SSL at all.
Besides, if you want to submit a feedback to Microsoft, please feel free to submit
your situation on our product to the following link:
https://connect.microsoft.com/SQLServer/Feedback.
If you have any other questions, please feel free to ask.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Similar Messages

  • Microsoft OLE DB Provider for SQL Server 2012 Analysis Services Error Code = 0x80040E05

    I've been running a package for 6 months without any issues that pulls data from a cube via MDX and moves it to a database.
    We've recently moved to a new server x64 and the connections all succeed but at runtime (in 64 = T&F) I get the following error:
    [SRC AdExchange [87]] Error: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E05.
    An OLE DB record is available.  Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services."  Hresult: 0x00000001  Description: "Error Code = 0x80040E05, External Code = 0x00000000:.".
    [SSIS.Pipeline] Error: SRC AdExchange failed the pre-execute phase and returned error code 0xC0202009.
    I've installed SQL_AS_OLEDB, SQL_AS_ADOMD from Microsoft® SQL Server® 2012 SP1 Feature Pack
    Why is my connection failing?

    The server has a 10Gbps network connection.
    I've installed CU6 for SQL Server 2012 SP1
    http://support.microsoft.com/kb/2874879/en-us#hfi
    I'm still getting the same error at runtime in BIDS:
    [SRC AdExchange [87]] Error: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E05.
    An OLE DB record is available.  Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services."  Hresult: 0x00000001  Description: "Error Code = 0x80040E05, External Code = 0x00000000:.".
    [SSIS.Pipeline] Error: SRC AdExchange failed the pre-execute phase and returned error code 0xC0202009.
    Looking at the errorlog, everything looks normal until:
    Launched startup procedure 'sp_ssis_startup'.
    Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
    Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
    Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
    Using 'xpstar.dll' version '2011.110.3000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
    Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
    Using 'xplog70.dll' version '2011.110.2100' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
    AppDomain 2 (SSISDB.dbo[runtime].1) created.
    Unsafe assembly 'microsoft.sqlserver.integrationservices.server, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil' loaded into appdomain 2 (SSISDB.dbo[runtime].1).
    Unsafe assembly 'microsoft.sqlserver.integrationservices.server, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil' loaded into appdomain 2 (SSISDB.dbo[runtime].1).
    AppDomain 3 (master.sys[runtime].2) created.
    Software Usage Metrics is enabled.
    SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
    Service Broker manager has shut down.
    Error: 17054, Severity: 16, State: 1.
    The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
    .NET Framework runtime has been stopped.
    SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
    The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ MSSQLSvc/XXXXXXXXXX.com ] for the SQL Server service. Error: 0xffffffff, state: 63. Administrator should deregister this SPN manually to avoid client authentication
    errors.
    The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ MSSQLSvc/XXXXXXXXXX.com:1433 ] for the SQL Server service. Error: 0xffffffff, state: 63. Administrator should deregister this SPN manually to avoid client authentication
    errors.
    Wondering about the unsafe assembly in SSIS and deregistering the SPN..
    Anyone have any ideas on how to resolve this?
    Thanks!

  • SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x80004005 Description: "Internal error: An une

    SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.  An OLE DB record is available.  Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services."  Hresult: 0x80004005
     Description: "Internal error: An unexpected error occurred (file 'pcxmlacommon.cpp', line 43, function 'PCFault::RaiseError').
    I'm getting above error in the pre- execute phase of a DFT when I'm trying to fetch data from a SSAS cube using mdx query.
    I'm using OLE DB provider for connecting to cube.
    I got one resolution for Error Code 0X8004005, which asked me to add 'Format= Tabular' in cube's connection string. It does not seem to work either. Can any one help me out on this???

    You are probably missing an update.
    I saw a MS Connect post https://connect.microsoft.com/SQLServer/feedback/details/250920/error-using-oledb-or-datareader-to-get-analysis-services-data where that suggestion was proposed as a fix, but is for an older SQL Server version.
    So do there is a question if you pull data from SQL Server 2012 SSAS using SSIS 2012 (so no other build is involved).
    Arthur My Blog

  • Virtual Lab: Exploring SQL Server 2012 Integration Services - Setup script fails

    I am trying to work through a Lab, but cannot get past the Setup script stage.
    The lab is "Exploring SQL Server 2012 Integration Services". I have tried this several times (with new lab instances) and the result is always the same.
    I double click the Setup command ... Press 2 ... when the popup dialog appears I press Ok ... the progress bar completes and the messages in the text box seem to indicate everything has completed (last line says "Done"). I click Close as per the
    instructions and then the script moves to the "Configure SQL Server" stage.
    After a short delay a number of error messages appear: "Could not open a connection ... Login / timeout expired" etc - basically it can't find or can't connect to the server.
    I expected these labs to work seamlessly  :)
    Anyone know what's going wrong here?
    Thanks,
    Larry

    I am moving it to SSIS.
    Kalman Toth Database & OLAP Architect
    SELECT Video Tutorials 4 Hours
    New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

  • Sql Server 2012 - Standard/Custom Reports in SSMS

    Hi,
    I want to develop my own Custom Reports in Sql Server. I want to know the underlying report logic (tables used, joins etc) of the existing
    Standard reports thru SSMS. Is it possible to locate the source code (.rdl) of these Standard Reports to get an idea about the underlying logic which could be used in my Custom Reports ?
    I am using Sql Server 2012
    Thanks

    Hello,
    The standard reports are embedded in an assembly, you can not get the source RDL reports ... without conflicting copyrights.
    Customer reports are pretty easy, the database connection is passed from SSMS to the report, just design the report as you like, see
    Custom Reports in Management Studio
    You can get my customer reports for SSMS 2005 (you can upgrade them to your used version) as an example here:
    https://onedrive.live.com/?cid=D974FC8F54C88BA9&id=D974FC8F54C88BA9%21132
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • SQL Server 2012 Analysis Services Deployment Wizard broken after SP1

    I have installed SQL Server 2012 SP1, now I cannot edit Data Source Connection Strings anymore in the Deployment Wizard.
    When clicking the button labeled "..." I get an error "Could not load file or assembly 'Microsoft.Data.ConnectionUI, Version=8.0.0.0' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference".
    This happened on two different 2008 R2 servers and local windows 7 desktop, SP1 Cumulative Update 1 does not fix the error.
    Please help!

    I managed to fix it by modifying the Workaround from Microsoft a bit.
    Microsoft Fix: https://support.microsoft.com/en-us/kb/2809127/
    Summary of fix:
    Open the following configuration file in a text editor, such as Notepad, as an administrator:
    <var class="sbody-var" style="box-sizing:border-box;"><system drive>:</var>\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Microsoft.AnalysisServices.Deployment.exe.config
    2. Insert the runtime XML tags after the </startup> tag in the configuration section:<configuration>
    <startup>
    <requiredRuntime version="v4.0.30319" safemode="true" />
    </startup>
    <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
    <assemblyIdentity name="Microsoft.Data.ConnectionUI" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
    <bindingRedirect oldVersion="8.0.0.0-9.0.0.0" newVersion="10.0.0.0"/>
    </dependentAssembly>
    <dependentAssembly>
    <assemblyIdentity name="Microsoft.Data.ConnectionUI.Dialog" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
    <bindingRedirect oldVersion="8.0.0.0-9.0.0.0" newVersion="10.0.0.0"/>
    </dependentAssembly>
    </assemblyBinding>
    </runtime>
    </configuration>
    What i did to make it work:
    <configuration>
      <startup>
        <requiredRuntime version="v4.0.30319" safemode="true" />
      </startup>
      <runtime>
                    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
                                    <dependentAssembly>
                                    <assemblyIdentity name="Microsoft.Data.ConnectionUI" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
                                    <bindingRedirect oldVersion="10.0.0.0" newVersion="8.0.0.0"/>
                                    </dependentAssembly>
                    <dependentAssembly>
                                    <assemblyIdentity name="Microsoft.Data.ConnectionUI.Dialog" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
                                    <bindingRedirect oldVersion="10.0.0.0" newVersion="8.0.0.0"/> 
                  </dependentAssembly>
                    </assemblyBinding>
       </runtime>
    </configuration>
    Instead of redirecting from version 8 and 9 to 10, i reverted it and made sure it uses version 8.

  • Sql Server 2012 Integration Services Catalog views - cpu usage history

    Hi,
    I am new to SQL Server 2012. I have deployed and executed a SSIS package on the Integration Services catalog.
    Now, to analyze the performance of the executed package I wish to query the SSISDB catalog views to retrieve the cpu & memory usage history. Please let me know in which catalog view/table I can find this info. 
    There is a column named "Process_Id" in the "catalog.operations" table. Can we tie this id to the Sql Server pid/kid and then retrieve the cpu
    usage history ?
    ** I am using Sql Server 2012 **
    Thanks

    Hi All,
    Thanks all for your inputs. One final question - 
    As I mentioned earlier, the Sql Server 2012 catalog views
    DO NOT  capture various performance metrics
    (e.g. cpu usage history, memory usage history etc) of
    an executing SSIS package . However, I am cognizant of the fact that it is possible to retrieve this exact info
    (ie. cpu usage history, memory usage history etc) for
    a Sql-Server internally generated SPID (present in [sys].[dm_exec_sessions]).
    The approach is to find a way to join/relate the catalog provided "Process_id" to the Sql Server generated internal SPIDs in a session. If I am successful in joining these 2 process ids together,
    it will allow me to gather all the information available from both sides - ie the catalog views + the sql-server internal process SPIDs of the session. Thus, by tagging the SSIS pprocess_id to
    its sql-server session it will allow to retrieve the resource usage details by the executed SSIS process.
    **Please also let me know if the above could be achieved by any other approach.
    Any help is appreciated.
    Thanks

  • Local SQL Server 2012 (express) ColdFusion 10 Datasource will not connect?

    Hello
    There are several methods to do this out there, not one has worked for me. First, configuring SQL Server by
    enabling TCIP connections
    Setting IP1 & IP2 Address to 127.0.0.1
    setting all TCP Ports to 1433 (IP1 through IP7)
    Leave all TCP Dynamic Ports blank
    enable Named Pipes
    restart SQL Server
    Then in Studio:
    Security tab under the DB you want to connect to
    create a new user
    give user a user name and login name
    default Schema- dbo
    Then in CF Admin:
    Server: 127.0.0.1
    Port: 1433
    User Name: login name from above
    Connection verification failed for data source: appraiseriLOCAL
    java.sql.SQLInvalidAuthorizationSpecException: [Macromedia][SQLServer JDBC Driver][SQLServer]Login failed for user 'Nu-PC\Nu'.
    The root cause was that: java.sql.SQLInvalidAuthorizationSpecException: [Macromedia][SQLServer JDBC Driver][SQLServer]Login failed for user 'Nu-PC\Nu'.
    Any help with this will prevent more hair-pulling.
    Thanks

    I had the same problem connecting to SQL Server Express 2008 in an Amazon EC2 instance but I followed the instructions step-by-step in the following link and was able to connect with CF.
    http://www.linglom.com/it-support/enable-remote-connection-on-sql-server-2008-express/

  • [Forum FAQ] Reporting Service Point cannot be installed on a Site System Server running SQL Server 2012 SP1

    Symptom: When you install Reporting Service Point role on a Site System Server running SQL Server
    2012 SP1, you may encounter an issue that the Reporting Service Point role cannot be installed. The error log “srsrpMSI.log” and “srsrpsetup.log” may throw the error as shown in Figure 1 and Figure 2.
    03:32:03:764]:
    MainEngineThread is returning 1618
    Figure 1: Error -1
    <03/03/14 03:32:03>
    srsrp.msi exited with return code: 1618
    Figure 2: Error -2
    Reason: All the two logs indicate an error return code 1618. From the KB below you may know what
    the return code means.
    ERROR_INSTALL_ALREADY RUNNING 
    1618
    Another installation is already in progress. Complete that installation before proceeding with this install.
    KB link:
    http://support.microsoft.com/kb/290158 “it is related to an Office Suite KB, anyway, the MSI return code is the same meaning”
    You can look into Resource Manager and Event Viewer to find the other currently running MSI installation. You may get a warning in Event Log that means the MSI wants to install a SQL Server
    related Component (Figure 3). The Resource Manager confirms this (Figure 4).
    Event Log:
    Event ID: 1004
    Source: Msinstaller
    Level: Warning
    Detection of product '{A7037EB2-F953-4B12-B843-195F4D988DA1}',
    feature 'SQL_Tools_ANS', component '{0CECE655-2A0F-4593-AF4B-EFC31D622982}' failed.  The resource '' does not exist.
    Figure 3: Event Log
    Figure 4: Resource Manager
    Resolution: the error is exactly what the following KB describes.
    KB Link:
    http://support.microsoft.com/kb/2793634
    After we resolve the SQL Server 2012 issue, the Reporting Service Role is installed successfully.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    This implies that ODP.NET does NOT need to be installed on a client. However, I cannot find OraOPs9.dll on a machine with Client Release 9.2 installed. Should OraOps?.dll automatically come with a Client installation of 9.2 or higher?
    ODP.NET needs to be installed on the client. OraOps9.dll is part of ODP.NET, not the Oracle Client.
    Also, if an application is built with the 10g ODP.NET, can it be run from a machine with OraOps9.dll?
    If an application is built with 10g ODP.NET, it can be run with 9.2 ODP.NET as long as you do not use any 10g APIs. The new features in 10g ODP.NET are included in the doc and the ODP.NET FAQ for your reference.

  • SQL Server 2012 Cumulative update package 2 (CU2) for SQL Server 2012 Service Pack 2 - why only for x86 ?

    Hey guys...
    Im a little bit confused... i wanted to download the newest hotfixes for SQL server 2012...
    But the download for :
    2983175 Cumulative update package 2 (CU2) for SQL Server 2012 Service Pack
    is only for the platform: x86 available ... but my SQL server 2012 is running in a x64 environment...
    (when i checked the older cumulative updates... they're all only for x86.. can someone tell me why ? )
    thanks and regards,
    Dominic

    There doesn't exist an SQL Express "Standard". It's two different editions.
    For Express there are three 32bit/64bit editions:
    Express, Express with Tools and Express with Advanced Services.
    Express with Tools is essentially Express with Management Studio Tools, Express with Advanced Services adds also BI (Business Intelligence) + Reporting Services.
    As for where you can apply the cumulative update, on the link you can see this:
        Microsoft SQL Server 2012 Service Pack 2, when used with:
            Microsoft SQL Server 2012 Analysis Services
            Microsoft SQL Server 2012 Developer
            Microsoft SQL Server 2012 Enterprise
            Microsoft SQL Server 2012 Express
            Microsoft SQL Server 2012 Business Intelligence
            Microsoft SQL Server 2012 Standard
            Microsoft SQL Server 2012 Web
    "If there's nothing wrong with me, maybe there's something wrong with the universe!"

  • I get one or the other error when i install SQL server 2012 SP1 in my Lab server

    I get multiple errors when i install SQL server 2012 SP1 In my lab server.
    Not sure why i keep getting different errors all the time when i install SQL server 2012 & 2012 SP1.
    Below are error codes, screen shots and also a log of the error.
    1.  Eror code 0X84B40000
    Also dint understand any thing from this article related to the above error 
    http://social.technet.microsoft.com/Forums/sqlserver/en-US/5b6cc928-0db8-4fe4-a5d3-21672225f0ca/i-get-error-code-0x84b40000-when-trying-to-install-sql-server-mgmt-studio-to-an-existing-sql?forum=sqlexpress
    2. Eror code 0x851A001A
    Can any one plz help as i always get one or the other error.
    ====================================
    Screen shot: 
    Please note the below screen shot has given the error code 0x851A001A which is same in case of failure of all the other features which have failed during this installation. Hence i have uploaded only one screen shot.
    2. Log file content.
    =================================
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893606
      Start time:                    2014-05-04 21:15:35
      End time:                      2014-05-04 21:51:45
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for RS:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
    Machine Properties:
      Machine name:                  SERVER1
      Machine processor count:       2
      OS version:                    Windows Server 2008 R2
      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 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Database Engine Services                 1033      
              Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            SQL Server Replication                   1033      
              Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033                
    Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Data Quality Services                    1033    
                Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSAS11.MSSQLSERVER             Analysis Services                        1033  
                  Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSRS11.MSSQLSERVER             Reporting Services - Native              1033        
            Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Management Tools - Basic  
                  1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Management Tools - Complete  
               1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Client Tools Connectivity  
                 1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Client Tools Backwards Compatibility
        1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Client Tools SDK      
                      1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Integration Services    
                    1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Reporting Services - SharePoint
                                                       11.0.2100.60    No        
    Package properties:
      Description:                   Microsoft SQL Server 2012 Service Pack 1
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      SPLevel:                       0
      Installation location:         F:\x64\setup\
      Installation edition:          Enterprise
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      false
      AGTSVCACCOUNT:                 ms\sql
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      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:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                true
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, RS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SCOM
      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:                    SCOM
      INSTANCENAME:                  SCOM
      ISSVCACCOUNT:                  NT AUTHORITY\Network Service
      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$SCOM
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 ms\sql
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           MS\Gautam, MS\SCOM Users
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    1
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\ConfigurationFile.ini
    Detailed results:
      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, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       Database Engine Services
      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, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      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, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      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, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       SQL Browser
      Status:                        Passed
      Feature:                       SQL Writer
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\SystemConfigurationCheck_Report.htm

    Sorry about the error in the path, but you find the files that's the main thing.
    Indeed it is a certificate problem:
    2014-05-04 21:47:43.56 spid12s Error: 17190, Severity: 16, State: 1.
    2014-05-04 21:47:43.56 spid12s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2014-05-04 21:47:43.56 spid12s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
    2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
    2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
    2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
    2014-05-04 21:47:43.57 spid12s Error: 17826, Severity: 18, State: 3.
    2014-05-04 21:47:43.57 spid12s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-05-04 21:47:43.57 spid12s Error: 17120, Severity: 16, State: 1.
    2014-05-04 21:47:43.57 spid12s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    I've recall that I've tried to help people with this error before, but I'm sure they were able to sort it out.
    Anyway, this blog post,
    http://blogs.msdn.com/b/sqljourney/archive/2012/10/09/sql-2008-service-fails-to-come-online-with-a-valid-certificate-could-not-be-found-and-it-is-not-possible-to-create-a-self-signed-certificate.aspx
    suggests the issue is a corrupted user profile, and you should try to use a different service account.
    This blog also seems to have a simple solution, but I cannot vouch for that it will work:
    http://www.beejblog.com/2012/02/sql-server-solved-unable-to-initialize.html
    Erland Sommarskog, SQL Server MVP, [email protected]

  • 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

  • Failure to install SQL Server 2012 SP1 CU8/9 with a "Failed to retrieve data for this request." error

    Hi all,
    Has anyone come across SQL Server 2012 SP1 CU8/9 failing to install with a “Failed to retrieve data for this request.” error.
    The error is too generic for a useful search on web, for me at least anyway.
    Had no problems patching a whole bunch of other servers in the same environment.
    I’m no good at reading these error logs. For some reason the primary replica is referenced in the detailed log???
    The CU8/9 patch has been run by both Domain Admins and local Admin with no luck.
    We are trying to patch a secondary failover replica. (SharePoint 2013 is installed on this server.)
    This is from the summary log:
    Overall summary:
      Final   result:                    The patch installer has failed to update the shared features. To determine   the reason for failure,
    review the log files.
      Exit code   (Decimal):             -2146233088
      Exit facility   code:            19
      Exit error   code:                 5376
      Exit   message:                    Failed to retrieve data for this request.
      Start   time:                      2014-04-10 11:51:11
      End   time:                        2014-04-10 11:51:49
      Requested   action:                Patch
      Exception help link:            
    http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3412.0&EvtType=0xB2652E58%400xDC80C325&EvtType=0xB2652E58%400xDC80C325
    Machine Properties:
      Machine   name:                    VMSPDB2
      Machine processor   count:       4
      OS version:                      Future Windows Version
      OS service   pack:                
      OS   region:                       Australia
      OS   language:                     English (United States)
      OS   architecture:                 x64
      Process   architecture:          64 Bit
      OS   clustered:                    Yes
    Product features discovered:
      Product                Instance               Instance ID                     
    Feature                                    Language              
    Edition                Version         Clustered  Configured
      SQL Server   2012        MSSQLSERVER            MSSQL11.MSSQLSERVER              Database
    Engine Services                   1033                   Enterprise Edition  
    11.1.3000.0     No           Yes      
      SQL Server   2012        MSSQLSERVER          MSSQL11.MSSQLSERVER              SQL Server  
    Replication                     1033                   Enterprise
    Edition     11.1.3000.0       No           Yes      
      SQL Server   2012        MSSQLSERVER            MSSQL11.MSSQLSERVER              Full-Text
    and Semantic Extractions for Search   1033                   Enterprise Edition   11.1.3000.0       No        
    Yes        
      SQL Server   2012        MSSQLSERVER            MSSQL11.MSSQLSERVER              Data
    Quality Services                      1033                  
    Enterprise Edition   11.1.3000.0       No           Yes      
      SQL Server   2012                                                           
    Management   Tools -   Basic                   1033                  
    Enterprise Edition   11.1.3000.0       No           Yes      
      SQL Server   2012                                                           
    Management Tools - Complete                1033                   Enterprise Edition  
    11.1.3000.0       No           Yes      
      SQL Server   2012                                                           
    Client Tools Connectivity                  1033                   Enterprise Edition  
    11.1.3000.0     No           Yes      
      SQL Server   2012                                                           
    SQL Server Data   Tools                      1033                  
    Enterprise Edition   11.1.3000.0       No           Yes      
      SQL Server   2012                                                           
    Integration   Services                       1033                  
    Enterprise Edition   11.1.3000.0       No           Yes      
    Package properties:
        Description:                     Microsoft SQL Server 2012 Service Pack 1
        ProductName:                     SQL Server 2012
        Type:                            RTM
        Version:                         11
        SPLevel:                         1
      KBArticle:                       KB2931078
        KBArticleHyperlink:             
    http://support.microsoft.com/?kbid=2931078
        PatchType:                       QFE
        AssociatedHotfixBuild:         0
        Platform:                        x64
        PatchLevel:                      11.1.3412.0
        ProductVersion:                  11.1.3000.0
        GDRReservedRange:                10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0
        PackageName:                     SQLServer2012-KB2931078-x64.exe
      Installation   location:           e:\90a192411a98d1f6dc\x64\setup\
    User Input Settings:
        ACTION:                          Patch
        ALLINSTANCES:                    false
        CLUSTERPASSIVE:                  false
        CONFIGURATIONFILE:              
      ENU:                             false
        HELP:                            false
      IACCEPTSQLSERVERLICENSETERMS:    false
        INDICATEPROGRESS:                false
        INSTANCEID:                      <empty>
        INSTANCENAME:                    <empty>
        QUIET:                           false
        QUIETSIMPLE:                     false
        SQMREPORTING:                    false
        UIMODE:                          Normal
        X86:                             false
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report   file:                 The rule result report file is not available.
    Exception summary:
    The following is an exception stack listing   the exceptions in outermost to innermost order
    Inner exceptions are being indented
    Exception type:   Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException
        Message:
            Failed to retrieve data for   this request.
        HResult : 0x80131500
        Data:
          HelpLink.ProdName   = Microsoft SQL Server
            HelpLink.BaseHelpUrl =
    http://go.microsoft.com/fwlink
            HelpLink.LinkId = 20476
            HelpLink.EvtType =
    0xB2652E58@0xDC80C325
          DisableWatson   = true
        Stack:
            at   Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object   connectionInfo, Request request)
            at   Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.ProcessDTbl(DataTable   dt, Int32 level)
            at   Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectSqlDiscoveryData(String   machineName)
            at   Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectDiscoveryData(String   machineName)
            at   Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1   machineNames, String discoveryDocRootPath, String   clusterDiscoveryDocRootPath)
            at   Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String   actionId)
            at   Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId,   TextWriter errorStream)
            at   Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter   statusStream, ISequencedAction actionToRun, ServiceContainer context)
        Inner exception type:   System.ComponentModel.Win32Exception
            Message:
                    Not   all privileges or groups referenced are assigned to the caller.
            HResult : 0x80004005
            Error : 1300
              Stack:
                    at   Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege.SetPrivilege(Boolean   enable)
                      at Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege..ctor(String   privilege)
                      at Microsoft.SqlServer.Configuration.Sco.SqlRegistry.GetLocallyCachedLocalMachineSubKey(ServiceContainer   ctx, String machineName, SqlRegistryKey
    key)
                      at   Microsoft.SqlServer.Discovery.DiscoveryUtils.TryLocallyCacheRegistryKey(ServiceContainer   ctx, String machineName, SqlRegistryKey
    machineKey, String registryPath,   RegistryView regView, String regPath, RegistryAccess registryAccess,   Boolean& alreadyCached)
                      at   Microsoft.SqlServer.Discovery.DiscoveryUtils.GetLocalMachineSubKey(ServiceContainer   ctx, String machineName, RegistryView regView,
    String regPath, RegistryAccess   registryAccess)
                      at   Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String   machineName, RegistryView regView)
                      at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.LoadSql2kInstanceList(String   machineName)
                      at Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
                      at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
                      at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req,   Object ci)
                      at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object   connectionInfo, Request request)
                      at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object   connectionInfo, Request request)
    And the tail of the detailed log:
    (01) 2014-04-10 11:51:29 Slp: Completed Action:   InitializeMsiExtension, returned True
    (01) 2014-04-10 11:51:30 Slp:   ----------------------------------------------------------------------
    (01) 2014-04-10 11:51:30 Slp: Running Action:   AddPackageModifierSourcesAction
    (01) 2014-04-10 11:51:30 Slp: Completed Action:   AddPackageModifierSourcesAction, returned True
    (01) 2014-04-10 11:51:30 Slp:   ----------------------------------------------------------------------
    (01) 2014-04-10 11:51:30 Slp: Running Action:   InitializeConfigAction
    (01) 2014-04-10 11:51:30 Slp: Completed Action:   InitializeConfigAction, returned True
    (01) 2014-04-10 11:51:30 Slp:   ----------------------------------------------------------------------
    (01) 2014-04-10 11:51:30 Slp: Running Action:   RunRemoteDiscoveryAction
    (01) 2014-04-10 11:51:31 Slp: Running discovery on local   machine
    (01) 2014-04-10 11:51:33 Slp: Discovery on local machine   is complete
    (01) 2014-04-10 11:51:33 Slp: Running discovery on remote   machine: VMSPDB1
    (01) 2014-04-10 11:51:35 Slp: Discovery on VMSPDB1 failed due to exception
    (01) 2014-04-10 11:51:36 Slp:   Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException: Failed to   retrieve data for this request. ---> System.ComponentModel.Win32Exception:   Not all privileges or groups referenced are
    assigned to the caller.
      at   Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege.SetPrivilege(Boolean   enable)
       at   Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege..ctor(String   privilege)
       at   Microsoft.SqlServer.Configuration.Sco.SqlRegistry.GetLocallyCachedLocalMachineSubKey(ServiceContainer   ctx, String machineName, SqlRegistryKey key)
       at   Microsoft.SqlServer.Discovery.DiscoveryUtils.TryLocallyCacheRegistryKey(ServiceContainer   ctx, String machineName, SqlRegistryKey machineKey, String registryPath,   RegistryView regView, String regPath, RegistryAccess
    registryAccess,   Boolean& alreadyCached)
       at   Microsoft.SqlServer.Discovery.DiscoveryUtils.GetLocalMachineSubKey(ServiceContainer   ctx, String machineName, RegistryView regView, String regPath, RegistryAccess   registryAccess)
       at   Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String   machineName, RegistryView regView)
       at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.LoadSql2kInstanceList(String   machineName)
       at   Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
       at   Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
       at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request   req, Object ci)
       at   Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object   connectionInfo, Request request)
       at   Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object   connectionInfo, Request request)
       --- End of inner exception stack trace ---
       at   Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object   connectionInfo, Request request)
       at   Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.ProcessDTbl(DataTable   dt, Int32 level)
       at   Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectSqlDiscoveryData(String   machineName)
       at   Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectDiscoveryData(String   machineName)
       at   Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1   machineNames, String discoveryDocRootPath, String   clusterDiscoveryDocRootPath)
    (01) 2014-04-10 11:51:36 Slp: Error: Action   "Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction"   threw an exception during execution.
    (01) 2014-04-10 11:51:36 Slp:   Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Failed   to retrieve data for this request. --->   Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException: Failed to  
    retrieve data for this request. ---> System.ComponentModel.Win32Exception:   Not all privileges or groups referenced are assigned to the caller.
    (01) 2014-04-10 11:51:36 Slp:    at   Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege.SetPrivilege(Boolean   enable)
    (01) 2014-04-10 11:51:36 Slp:    at   Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege..ctor(String   privilege)
    (01) 2014-04-10 11:51:36 Slp:    at   Microsoft.SqlServer.Configuration.Sco.SqlRegistry.GetLocallyCachedLocalMachineSubKey(ServiceContainer   ctx, String machineName, SqlRegistryKey key)
    (01) 2014-04-10 11:51:36 Slp:    at   Microsoft.SqlServer.Discovery.DiscoveryUtils.TryLocallyCacheRegistryKey(ServiceContainer   ctx, String machineName, SqlRegistryKey machineKey, String registryPath,   RegistryView
    regView, String regPath, RegistryAccess registryAccess,   Boolean& alreadyCached)
    (01) 2014-04-10 11:51:36 Slp:    at   Microsoft.SqlServer.Discovery.DiscoveryUtils.GetLocalMachineSubKey(ServiceContainer   ctx, String machineName, RegistryView regView, String regPath, RegistryAccess   registryAccess)
    (01) 2014-04-10 11:51:36 Slp:    at   Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String   machineName, RegistryView regView)
    (01) 2014-04-10 11:51:36 Slp:    at   Microsoft.SqlServer.Discovery.DiscoveryEnumObject.LoadSql2kInstanceList(String   machineName)
    (01) 2014-04-10 11:51:36 Slp:    at   Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
    (01) 2014-04-10 11:51:36 Slp:    at   Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
    (01) 2014-04-10 11:51:36 Slp:    at   Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req,   Object ci)
    (01) 2014-04-10 11:51:36 Slp:    at   Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object   connectionInfo, Request request)
    (01) 2014-04-10 11:51:36 Slp:    at   Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object   connectionInfo, Request request)
    (01) 2014-04-10 11:51:36 Slp:    --- End of   inner exception stack trace ---
    (01) 2014-04-10 11:51:39 Slp: Received request to add the   following file to Watson reporting:   C:\Users\HS2\AppData\Local\Temp\tmp6614.tmp
    (01)   2014-04-10 11:51:39 Slp: The following is an exception stack listing the   exceptions in outermost to innermost order
    (01)   2014-04-10 11:51:39 Slp: Inner exceptions are being indented
    (01)   2014-04-10 11:51:39 Slp:
    (01)   2014-04-10 11:51:39 Slp: Exception type:   Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException
    (01)   2014-04-10 11:51:39 Slp:     Message:
    (01)   2014-04-10 11:51:39 Slp:           Failed to retrieve data for this request.
    (01)   2014-04-10 11:51:39 Slp:     HResult : 0x80131500
    (01) 2014-04-10 11:51:39 Slp:       Data:
    (01) 2014-04-10 11:51:39   Slp:       HelpLink.ProdName = Microsoft SQL   Server
    (01) 2014-04-10 11:51:39   Slp:       HelpLink.BaseHelpUrl =
    http://go.microsoft.com/fwlink
    (01) 2014-04-10 11:51:39   Slp:       HelpLink.LinkId = 20476
    (01) 2014-04-10 11:51:39 Slp:       Stack:
    (01) 2014-04-10 11:51:39   Slp:         at   Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object   connectionInfo, Request request)
    (01) 2014-04-10 11:51:39   Slp:         at   Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.ProcessDTbl(DataTable   dt, Int32 level)
    (01) 2014-04-10 11:51:39   Slp:         at   Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectSqlDiscoveryData(String   machineName)
    (01) 2014-04-10 11:51:39   Slp:         at   Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectDiscoveryData(String   machineName)
    (01) 2014-04-10 11:51:39   Slp:         at   Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1   machineNames, String discoveryDocRootPath,
    String   clusterDiscoveryDocRootPath)
    (01) 2014-04-10 11:51:39   Slp:         at   Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String   actionId)
    (01) 2014-04-10 11:51:39   Slp:         at   Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId,   TextWriter errorStream)
    (01) 2014-04-10 11:51:39   Slp:         at   Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter   statusStream, ISequencedAction actionToRun, ServiceContainer
    context)
    (01)   2014-04-10 11:51:39 Slp:     Inner exception type:   System.ComponentModel.Win32Exception
    (01)   2014-04-10 11:51:39 Slp:           Message:
    (01)   2014-04-10 11:51:39   Slp:                   Not all privileges or groups referenced are assigned to the caller.
    (01)   2014-04-10 11:51:39   Slp:                  
    (01)   2014-04-10 11:51:39 Slp:           HResult : 0x80004005
    (01)   2014-04-10 11:51:39 Slp:           Error : 1300
    (01) 2014-04-10 11:51:39   Slp:         Stack:
    (01) 2014-04-10 11:51:39   Slp:                   at   Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege.SetPrivilege(Boolean  
    enable)
    (01) 2014-04-10 11:51:39   Slp:                   at Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege..ctor(String   privilege)
    (01) 2014-04-10 11:51:39   Slp:                   at   Microsoft.SqlServer.Configuration.Sco.SqlRegistry.GetLocallyCachedLocalMachineSubKey(ServiceContainer  
    ctx, String machineName, SqlRegistryKey key)
    (01) 2014-04-10 11:51:39   Slp:                   at Microsoft.SqlServer.Discovery.DiscoveryUtils.TryLocallyCacheRegistryKey(ServiceContainer   ctx,
    String machineName, SqlRegistryKey machineKey, String registryPath,   RegistryView regView, String regPath, RegistryAccess registryAccess,   Boolean& alreadyCached)
    (01) 2014-04-10 11:51:39   Slp:                   at   Microsoft.SqlServer.Discovery.DiscoveryUtils.GetLocalMachineSubKey(ServiceContainer  
    ctx, String machineName, RegistryView regView, String regPath, RegistryAccess   registryAccess)
    (01) 2014-04-10 11:51:39   Slp:                   at   Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String  
    machineName, RegistryView regView)
    (01) 2014-04-10 11:51:39   Slp:                   at   Microsoft.SqlServer.Discovery.DiscoveryEnumObject.LoadSql2kInstanceList(String   machineName)
    (01) 2014-04-10 11:51:39   Slp:                   at Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
    (01) 2014-04-10 11:51:39   Slp:                   at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
    (01) 2014-04-10 11:51:39   Slp:                   at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req,   Object ci)
    (01) 2014-04-10 11:51:39   Slp:                   at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object   connectionInfo, Request request)
    (01) 2014-04-10 11:51:39 Slp:                   at   Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object   connectionInfo, Request request)
    (01) 2014-04-10 11:51:44 Slp: Watson Bucket 2
     Original Parameter Values
    (01) 2014-04-10 11:51:44 Slp: Parameter 0 : SQL Server  
    2012@RTM@KB2931078
    (01) 2014-04-10 11:51:44 Slp: Parameter 1 :   Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process
    (01) 2014-04-10 11:51:44 Slp: Parameter 2 :   Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege.SetPrivilege
    (01) 2014-04-10 11:51:44 Slp: Parameter 3 :
    Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException@-2146233088  
    (01) 2014-04-10 11:51:44 Slp: Parameter 4 :
    System.ComponentModel.Win32Exception@-2147467259  
    (01) 2014-04-10 11:51:44 Slp: Parameter 5 :   RunRemoteDiscoveryAction
    (01) 2014-04-10 11:51:44 Slp: Parameter 8 : 1300
    (01) 2014-04-10 11:51:44 Slp:
     Final Parameter Values
    (01) 2014-04-10 11:51:44 Slp: Parameter 0 : SQL Server  
    2012@RTM@KB2931078
    (01) 2014-04-10 11:51:44 Slp: Parameter 1 : 0x6785B09D
    (01) 2014-04-10 11:51:44 Slp: Parameter 2 : 0xB2652E58
    (01) 2014-04-10 11:51:44 Slp: Parameter 3 : 0x74E34741
    (01) 2014-04-10 11:51:44 Slp: Parameter 4 : 0xDC80C325
    (01) 2014-04-10 11:51:44 Slp: Parameter 5 :   RunRemoteDiscoveryAction
    (01) 2014-04-10 11:51:44 Slp: Parameter 8 : 0xA05EFA62
    (01) 2014-04-10 11:51:45 Slp: Sco: Attempting to write   hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL   Server\110\Setup   Bootstrap\Log\20140410_115053\Registry_SOFTWARE_Microsoft_Microsoft SQL  
    Server.reg_
    (01) 2014-04-10 11:51:45 Slp: The following exception   occurred while preparing registry logs during Watson failure processing: Not   all privileges or groups referenced are assigned to the caller.
    (01) 2014-04-10 11:51:45 Slp: Sco: Attempting to write   hklm registry key Uninstall to file C:\Program Files\Microsoft SQL   Server\110\Setup   Bootstrap\Log\20140410_115053\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    (01) 2014-04-10 11:51:45 Slp: The following exception   occurred while preparing registry logs during Watson failure processing: Not   all privileges or groups referenced are assigned to the caller.
    (01) 2014-04-10 11:51:45 Slp: Sco: Attempting to write   hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL   Server\110\Setup Bootstrap\Log\20140410_115053\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    (01) 2014-04-10 11:51:45 Slp: The following exception   occurred while preparing registry logs during Watson failure processing: Not   all privileges or groups referenced are assigned to the caller.
    (01) 2014-04-10 11:51:45 Slp: Sco: Attempting to write   hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL   Server\110\Setup   Bootstrap\Log\20140410_115053\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft  
    SQL Server.reg_
    (01) 2014-04-10 11:51:45 Slp: The following exception   occurred while preparing registry logs during Watson failure processing: Not   all privileges or groups referenced are assigned to the caller.
    (01) 2014-04-10 11:51:45 Slp: Sco: Attempting to write   hklm registry key Uninstall to file C:\Program Files\Microsoft SQL   Server\110\Setup   Bootstrap\Log\20140410_115053\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    (01) 2014-04-10 11:51:45 Slp: The following exception   occurred while preparing registry logs during Watson failure processing: Not   all privileges or groups referenced are assigned to the caller.
    (01) 2014-04-10 11:51:45 Slp: Sco: Attempting to write   hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL   Server\110\Setup Bootstrap\Log\20140410_115053\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
    (01) 2014-04-10 11:51:45 Slp: The following exception   occurred while preparing registry logs during Watson failure processing: Not   all privileges or groups referenced are assigned to the caller.
    (01) 2014-04-10 11:51:46 Slp: Failed to retrieve data for   this request.
    (01) 2014-04-10 11:51:46 Slp: Watson bucket for exception   based failure has been created
    (01) 2014-04-10 11:51:46 Slp: Sco: Attempting to create   base registry key HKEY_LOCAL_MACHINE, machine
    (01) 2014-04-10 11:51:46 Slp: Sco: Attempting to open   registry subkey Software\Microsoft\Microsoft SQL Server\110
    (01) 2014-04-10 11:51:46 Slp: Sco: Attempting to get   registry value EnableErrorReporting
    (01) 2014-04-10 11:51:46 Slp: WER: Successfully read app   consent from registry Software\Microsoft\Microsoft SQL   Server\110\EnableErrorReporting=0.
    (01) 2014-04-10 11:51:46 Slp: WER: Application level   consent value '0' was mapped to consent status 'WerConsentDenied'
    (01) 2014-04-10 11:51:46 Slp: WER: Result of the   submission:: 'WerDisabled'
    (01) 2014-04-10 11:51:46 Slp: WER: Submitted 1 of 1   failures to the Watson data repository
    (01) 2014-04-10 11:51:46 Slp: Sco: File   'C:\Windows\system32\Cluster.exe' does not exist
    (01) 2014-04-10 11:51:46 Slp: Failed to collect cluster   logs, cannot find Cluster.exe under system directory.
    (01) 2014-04-10 11:51:46 Slp: Dumping final cluster state.
    (01) 2014-04-10 11:51:49 Slp: Completed dumping final   cluster state.
    (01) 2014-04-10 11:51:51 Slp:
    (01) 2014-04-10 11:51:51 Slp:   ----------------------------------------------------------------------
    (01) 2014-04-10 11:51:51 Slp:
    (01)   2014-04-10 11:51:51 Slp: Error result: -2146233088
    (01)   2014-04-10 11:51:51 Slp: Result facility code: 19
    (01)   2014-04-10 11:51:51 Slp: Result error code: 5376
    (01)   2014-04-10 11:51:51 Slp: SQM Service: Sqm does not have active session.

    Hello SQL Ranger,
    Thanks for posting the detailed log. I dont have exact solution for this but I can give you some hint what could be reason patch has failed below message points to fact that there is some issue with account which is used to install CU patch.Have alook at
    below log.It says that when patch was trying to get details from other node in cluster it was not able to.
    01) 2014-04-10 11:51:33 Slp: Discovery on local machine is complete
    (01) 2014-04-10 11:51:33 Slp: Running discovery on remote machine: VMSPDB1
    (01) 2014-04-10 11:51:35 Slp: Discovery on VMSPDB1 failed due to exception
    (01) 2014-04-10 11:51:36 Slp: Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException: Failed to retrieve data for this request. ---> System.ComponentModel.Win32Exception: Not all privileges or groups referenced are assigned to the caller.
    IMO I strongly feel it is issue with the account. Microsoft has also documented about this for SQL Server 2008 .Have a look at following links
    http://support.microsoft.com/default.aspx?scid=kb;en-US;2000257
    Please also assign privilege mentioned in below link
    http://www.bradg.co.za/?p=12
    Hope this helps
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Excel 2007 Download Error from SQL Server 2012

    Thank you for your help/comments in advance
    We are running SQL Server 2012, downloading SSRS reports into Excel 2007.
    The report renders to the monitor just fine.
    Most downloads are fine but we get an error with the largest downloads (common denominator) but can be hit or miss.  Usually a second try it will download.  Today we tried numerous times and kept getting the error.
    I saw a link to a service pack fix ...https://msdn.microsoft.com/en-us/library/dd255234(v=sql.110).aspx which somewhat fits my issue.
    The Report Server Log (O:\MSRS11.MSSQLSERVER\Reporting Services\LogFiles\ReportServerService__04_01_2015.log) gives the following error message:
    library!ReportServer_0-2!29bc!04/01/2015-15:02:01:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: Invalid offset for item.  ReferenceID: fffffffffffffffe, Offset: -2, Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
    An internal error occurred on the report server. See the error log for more details.;
    library!ReportServer_0-2!29bc!04/01/2015-15:02:12:: i INFO: Dump result: External dump process return code 0x20000001.
    External dump process returned no errors.
    processing!ReportServer_0-2!29bc!04/01/2015-15:02:12:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
    An internal error occurred on the report server. See the error log for more details.;
    library!ReportServer_0-2!29bc!04/01/2015-15:02:12:: w WARN: Microsoft.ReportingServices.Diagnostics.Utilities.RSException: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See
    the error log for more details. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for
    more details.
       at Microsoft.ReportingServices.RdlExpressions.ReportRuntime.RegisterRuntimeErrorInExpression(VariantResult& result, Exception e, IErrorContext iErrorContext, Boolean isError)
       at Microsoft.ReportingServices.RdlExpressions.ReportRuntime.EvaluateTextRunValueExpression(TextRun textRun)
       at Microsoft.ReportingServices.ReportProcessing.OnDemandReportObjectModel.TextRunImpl.GetResult(IReportScopeInstance romInstance)
       at Microsoft.ReportingServices.OnDemandReportRendering.InternalTextRunInstance.EvaluateOriginalValue()
       at Microsoft.ReportingServices.OnDemandReportRendering.InternalTextRunInstance.get_ProcessedWithError()
       at Microsoft.ReportingServices.Rendering.SPBProcessing.TextBox.WriteCustomNonSharedItemProps(RPLElementProps nonSharedProps, RPLWriter rplWriter, PageContext pageContext)
       at Microsoft.ReportingServices.Rendering.SPBProcessing.PageItem.WriteNonSharedItemProps(RPLElementProps elemProps, RPLWriter rplWriter, PageContext pageContext)
       at Microsoft.ReportingServices.Rendering.SPBProcessing.TextBox.WriteItemToStream(RPLWriter rplWriter, PageContext pageContext)
       at Microsoft.ReportingServices.Rendering.SPBProcessing.TextBox.CalculatePage(RPLWriter rplWriter, PageItemHelper lastPageInfo, PageContext pageContext, PageItem[] siblings, RepeatWithItem[] repeatWithItems, Double parentTopInPage, Double&
    parentPageHeight, Interactivity interactivity)
       at Microsoft.ReportingServices.Rendering.SPBProcessing.Rectangle.CalculatePage(RPLWriter rplWriter, PageItemHelper lastPageInfo, PageContext pageContext, PageItem[] siblings, RepeatWithItem[] repeatWithItems, Double parentTopInPage, Double&
    parentPageHeight, Interactivity interactivity)
       at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.TablixContext.AddRowMemberContent(TablixMember rowMember, Int32 rowIndex, Int32 colIndex, Int32 rowSpan, Int32 colSpan, Byte memberState, Int32 defTreeLevel, LevelInfo childLevelInfo,
    Double updateWidth)
       at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.TablixContext.AddRowMember(TablixMember rowMember, Int32 rowIndex, Int32 colIndex, Int32 rowSpan, Int32 colSpan, Byte memberState, Int32 defTreeLevel, LevelInfo childLevelInfo)
       at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateRowMemberChildren(Tablix tablix, TablixMember rowMemberParent, InnerToggleState parentToggleState, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex,
    Int32 parentColIndex, Int32 level, TablixContext context, Boolean& advanceRow, LevelInfo& parentLevelInfo, List`1& ignoreTotals, Boolean keepTogether)
       at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateTablixItems(Tablix tablix, TablixContext context)
       at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CalculatePage(RPLWriter rplWriter, PageItemHelper lastPageInfo, PageContext pageContext, PageItem[] siblings, RepeatWithItem[] repeatWithItems, Double parentTopInPage, Double&
    parentPageHeight, Interactivity interactivity)
       at Microsoft.ReportingServices.Rendering.SPBProcessing.ReportBody.CalculatePage(RPLWriter rplWriter, PageItemHelper lastPageInfo, PageContext pageContext, PageItem[] siblings, RepeatWithItem[] repeatWithItems, Double parentTopInPage, Double&
    parentPageHeight, Interactivity interactivity)
       at Microsoft.ReportingServices.Rendering.SPBProcessing.ReportSection.CalculatePage(RPLWriter rplWriter, Int32 page, Int32 totalPages, Int32 regionPageNumber, Int32 regionTotalPages, Boolean firstSectionOnPage, Boolean lastSection, Interactivity
    interactivity, Double heightToBeUsed, PageItemHelper& lastBodyInfo, Boolean& delayedHeader, Boolean& delayedFooter, Boolean& lastSectionOnPage)
       at Microsoft.ReportingServices.Rendering.SPBProcessing.Report.NextPage(RPLWriter rplWriter, ReportSectionHelper& lastPageInfo, Int32 page, Int32 totalPages, Interactivity interactivity, Boolean hasPaginationChunk)
       at Microsoft.ReportingServices.Rendering.SPBProcessing.SPBProcessing.GetReportNextPage(Stream& stream, Boolean collectPageBookmarks)
       at Microsoft.ReportingServices.Rendering.SPBProcessing.SPBProcessing.GetNextPage(RPLReport& rplReport, Boolean collectPageBookmarks)
       at Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties,
    CreateAndRegisterStream createAndRegisterStream)
       --- End of inner exception stack trace ---
       at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.HandleRenderingException(ReportRenderingException rex)
       at Microsoft.ReportingServices.ReportProcessing.Execution.RenderReport.Execute(IRenderingExtension newRenderer)
       at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderSnapshot(RenderingContext rc, ProcessingContext pc)
       at Microsoft.ReportingServices.Library.RenderFromSnapshot.DoRendering(ProcessingContext pc, RenderingContext rc)
       at Microsoft.ReportingServices.Library.RenderFromSnapshot.CallProcessingAndRendering(ProcessingContext pc, RenderingContext rc, OnDemandProcessingResult& result)
       at Microsoft.ReportingServices.Library.RenderStrategyBase.ExecuteStrategy(OnDemandProcessingResult& processingResult)
    The user sees the following on her monitor when downloading ...

    Hi Mark,
    As you know this is an known issue in the SSRS 2012 and the fix for this issue was first released in Cumulative Update 3 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article
    in the Microsoft Knowledge Base:
    2723749Cumulative update package 3 for SQL Server 2012
    More details information in below article:
    http://support.microsoft.com/en-us/kb/2707015
    As I have tested on my loacal environment and can't reproduce the issue and you have also mentioned that that you didn't meet the issue now. If you got the issue next time, please feel free to let us know if the hotfix will work or not.
    Regards,
    Vicky Liu
    Vicky Liu
    TechNet Community Support

  • Package migration from SSIS 2008 R2 to SQL server 2012

    hi guys:
      My company has decided to use Sql server 2012 for the database service, Integration service as well as analysis service
      The first question is which tool I should install to run packages ? in SQL Server 2008 R2, I've installed BIDS which is inside the disk.
      Also do I need to install any visual studio tools? I was under the impression that the BIDS 2008 was using kinda shell visual studio. 
     Thanks
     Hui
    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    Hi cat_ca,
    To develop package in SQL Server 2012 Integration Services, we use the SQL Server Data Tools (SSDT 2012) which can be installed from the SQL Server 2012 install media. The SSDT 2012 use Visual Studio 2010 shell by default and can be integrated into Visual
    Studio 2010. By installing SQL Server Data Tools - Business Intelligence for Visual Studio 2012, we can also integrate SSDT 2012 into Visual Studio 2012. However, SSDT 2012 cannot be integrated into Visual Studio 2013. As far as I know, the SSDT 2014 released
    in SQL Server 2014 RTM will use the Visual Studio 2013 shell and can be integrated into Visual Studio 2013.
    Regards,
    Mike Yin
    TechNet Community Support

Maybe you are looking for

  • Ibook g3 getting aol broardband

    I have only just got my ibook g3 and i wanted the internet for it but the connection i had with my windows pc is a usb ADSL modem from AOL and BT. I have the broardband disc but my ibook does not auto run it and so it does not install the drivers tha

  • Final cut express (FCE) fails to launch

    I googled a solution and the one that worked was to create a new user account on the mac and reload FCE.  This worked for about a week but today we have fail to launch.  I am so frustrated. can someone please give me a solution.  I now have two user

  • FICO Waited average Calculation Details identification

    SAP : ECC 6.0 Vertical : Chemicals Module : FICO in Standard setup Issue : Understanding WA mechanism 1. Invoce Date to Final Amt Recied from Customer withut cheq Bounce cases. Mechanism followed is FIFO no manual Bill booking.  possible. 1 Comp. wit

  • Unable to post asset in F-90

    Hi Experts, we have implemented asset accounting i.e. the basic asset accounting configurations are done in the year 2008 and there are no legacy assets to take in to SAP in FY 2008.  Since there were no assets we did not perform any deprecition run

  • ArrayList indices (Phrase counter follow-up)

    Hi everybody-- I finally figured out how to get code onto this computer I'm working with, so here's what I'm trying to do for anyone that doesn't remember. I'm using TuringPest's suggestion to go through my word list once, and then delete any index t