B2c - MS SQL SERVER Catalog Integration
Dear SAP,
As of now we are using ISA B2C application, which is connecting R3 system to download catalog data. Due to performance issues because of rfc, we need to integrate Catalog data which is in our SQL SERVER Database. Do you have any interfaces to connect MS SQL database also?
If it is not there, What are the ways that we have to connect backend (MS SQL SERVER Catalog data) which will result in less impact on presentation layer (JSP's and action classes)?
Regards,
Manjunath.R
I had to download the 64 bit librfc32.dll from SAP software download center as outlined in note 413708.
Please note that the librfc32.dll installed as part of SAP GUI is 32 bit. Hence, I was getting the BadImageFormat exception.
Similar Messages
-
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,
LarryI 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 -
How can install SQL Server 2008 Integration Services without CD?
How can install SQL Server 2008 R2 Integration Services without CD?
The PC with Windows 7 32-bits is far away and poor bandwidth . So, I want to install SQL Server 2008 Integration Services without CD.
Does any installer for SSIS only?Copy the install media from a memory stick, portable drive or network.
Arthur My Blog -
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 **
ThanksHi 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 -
UCCX 10 and SQL server 2012 Integration - Read Step returns 0
Hi All,
I managed to integration the UCCX with SQL 2012, when I press Test, it goes successfull.
However, I put the very simple Read step which does : "SELECT * from Table" , but it returns 0.
I put wireshark on SQL Server and found out the communication seems to be OK.I can see
SQL Batch
response
ACK
But still not sure wht the read step return 0.
Thanks,
HamedHi,
if you mean that pressing the Test button returns 0 in the "Number of rows returned" field, it's perfectly normal.
Does the subsequent DB Get step return anything?
G. -
SQL Server JDBC integrated security question
I'm assuming that the only way to create a connection to SQL Server using the JDBC driver is using IntegratedSecurity=false and not IntegrateSecurity=true? I can see the arguments for having it only work with false, but I just wanted to make sure so I can clear any questions up regarding security with our client's DBA. Thanks.
Hi Matt,
It is possible to use integrated security with ODI, you need to have the JDBC driver and the sqljdbc_auth.dll file in your drivers directory.
Your JDBC url will look like this: jdbc:sqlserver://localhost:1113;integratedSecurity=true
It is detailed in a note on Metalink (568070.1), here is an extract:
To implement the solution:
1. Copy the "sqljdbc_auth.dll" file into ODI "/drivers" Folder on the computer where the JDBC driver is installed.
2. In ODI "/bin/odiparams.bat" configuration file, set the "java.libary.path" system property to specify the directory of the "sqljdbc_auth.dll" file, as follows:
set ODI_ADDITIONAL_JAVA_OPTIONS="-Djava.library.path=c:\oracle\oracledi\drivers" or, if ODI_ADDITIONAL_JAVA_OPTIONS has already been set, add "-Djava.library.path=..." to the existing string, as follows:
set ODI_ADDITIONAL_JAVA_OPTIONS="-Duser.language=en" "-Duser.country=US"
"-Djava.library.path=c:\oracle\oracledi\drivers"
3. If using an Agent started with "agent.bat" or "agentscheduler.bat" commands, the Agent should be stopped and restarted (in order to take into account the new Java settings).
4. If using an Agent started as Windows Service, then:
Stop the Agent Service.
Remove the Agent Service with "agentservice -r" command.
Edit the "snpsagent.conf" file (from ODI "/tools/wrapper/conf" Directory).
Add the Java Library Path to specify the Directory of "sqljdbc_auth.dll" File, as
follows:
wrapper.java.library.path.2=c:\oracle\oracledi\drivers
Recreate the Windows Service with "agentservice -i" command.
Start the Windows Service.
Thanks,
Julien -
SQL Server 2005 Integrated Security
Post Author: mudEyes
CA Forum: Data Connectivity and SQL
Hello all,
I've just changed SQL 2000 to 2005 and want to use integrated security when connecting my CRViewer tables via an ADO connection in VB6 but i'm having no joy, I thought this would do it -
For intTablePtr = 1 To intNumberOfTables If blnIntegratedSecurity Then CRReport.Database.Tables(intNumberOfTables).SetLogOnInfo strServer, strDatabase Else CRReport.Database.Tables(intNumberOfTables).SetLogOnInfo strServer, strDatabase, strUser, strPassword End If Next intTablePtr CRReport.Database.LogOnServerEx _ pDllName:="p2ssql.dll", _ pServerName:=strServer, _ pConnectionString:=strConnection
but i can't get it working. Can anyone help me sort it out?Post Author: mudEyes
CA Forum: Data Connectivity and SQL
Found a way that works...
With SQLConnect.Connection .Open For Each tbl In CRReport.Database.Tables With .Properties tbl.ConnectionProperties("Data Source") = .Item("Data Source").Value tbl.ConnectionProperties("Initial Catalog") = .Item("Initial Catalog").Value tbl.ConnectionProperties("Integrated Security") = True tbl.ConnectionProperties("User ID") = "" tbl.ConnectionProperties("Password") = "" If tbl.TestConnectivity Then 'don't know why this works but it does End If End With .Close Next tbl End With -
SQL Server 2005 Dev Integration Services Fail
I've got VS2005 v.8.0.50727.867 (vsvista.050727-8600) on my 64bit Windows 7 box. I am trying to install SQL Server 2005 Integration Services on this Win7 box so I can load and edit the Win XP SSIS projects that I had on my XP box. So far I've
not been able to successfully install the Integration Services with a failed permission on the SQL**DTD.msi file.....I've copied this file locally and tried to run it and it would start but then would give permission error.
Is there an inherent incompatibility running SSIS projects in SQL Server 2005 on a 64bit Win 7 box? Worked great on my XP box.
I've been "upgrading" the SSIS projects to VS2008 since I was able to get SSIS installed. Any ideas what I need to do to get this beast to work?
TIA
HarryThanks Alberto
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Professional Service Pack 1 (Build 7601)
Time : Mon Aug 25 09:31:30 2014
DT0315 : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features,
install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL
Server in Books Online.
DT0315 : Failed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS).
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_1.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_1.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_1.log
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_2.log
Machine : DT0315
Product : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_1.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_2.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_2.log
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_3.log
Machine : DT0315
Product : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_2.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_3.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_3.log
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_4.log
Machine : DT0315
Product : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_3.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_4.log
Machine : DT0315
Product : Microsoft VSS Writer for SQL Server 2012
Product Version : 11.0.2100.60
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SqlWriter_1.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_4.log
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_5.log
Machine : DT0315
Product : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_4.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_5.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BOL_1.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_5.log
Machine : DT0315
Product : Integration Services
Error : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
Machine : DT0315
Product : Microsoft SQL Server 2005 Integration Services (64-bit)
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_DTS.log
Last Action : InstallFinalize
Error String : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
Error Number : 29549
Machine : DT0315
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_1.log
Machine : DT0315
Product : Microsoft SQL Server 2005 (64-bit)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQL.log
Machine : DT0315
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_2.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Analysis Services (64-bit)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_AS.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Notification Services (64-bit)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_NS.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Tools (64-bit)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_Tools.log
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt. -
SQL Server Denali is required to install integration services
Hi,
I've just installed a named instance of SQL Server 2014. I'm trying to create the SSISDB catalog and getting the following error.
"SQL Server Denali is required to install integration services"
I have 3 instances on my machine.
1. Default instance SQL Server 2012 SP1
2. Named instance SQL Server 2008 SP1
3. Named instance SQL Server 2014 SP1
The SSISDB creation works on the 2012 instance.Microsoft SQL Server 2014 Setup Discovery Report
Product
Instance
Instance ID
Feature
Language
Edition
Version
Clustered
Configured
Microsoft SQL Server 2014
SQL2014
MSSQL12.SQL2014
Database Engine Services
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
SQL2014
MSSQL12.SQL2014
SQL Server Replication
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
SQL2014
MSAS12.SQL2014
Analysis Services
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
Management Tools - Basic
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
Management Tools - Complete
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
Client Tools Connectivity
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
Client Tools Backwards Compatibility
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
Client Tools SDK
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
Integration Services
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
LocalDB
1033
Express Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2012
MSSQLSERVER
MSSQL11.MSSQLSERVER
Database Engine Services
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
MSSQLSERVER
MSSQL11.MSSQLSERVER
SQL Server Replication
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
MSSQLSERVER
MSAS11.MSSQLSERVER
Analysis Services
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
Management Tools - Basic
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
Management Tools - Complete
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
Client Tools Connectivity
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
Client Tools Backwards Compatibility
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
Client Tools SDK
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
BIDS
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
Integration Services
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
LocalDB
1033
Express Edition
11.1.3000.0
No
Yes
Microsoft SQL Server 2008
SQL2008
MSSQL10.SQL2008
Database Engine Services
1033
Enterprise Edition
10.0.1600.22
No
Yes
Microsoft SQL Server 2008
SQL2008
MSSQL10.SQL2008
SQL Server Replication
1033
Enterprise Edition
10.0.1600.22
No
Yes -
SQL Server 2008 KB2977321 Failed with Error code 1642
As part of application of security patches via windows update, sql server KB2977321 was applied along with a number of OS security patches.
Prior to applying the patches, I stopped the agent, engine, reporting, analysis and full text services.
The Sql server build prior to windows update was (for both instances):
ProductVersion
ProductLevel
Edition
10.0.5500.0
SP3
Standard Edition (64-bit)
After the update process, my main instance is showing (the second instance is not in use yet and I have left it in its stopped state)
Microsoft SQL Server 2008 (SP3) - 10.0.5520.0 (X64)
Jul 11 2014 16:11:50
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (VM)
In the Administrative Logs after the OS patches were applied (and all were reported as successful by windows update), I found the following errors listed:
Log Name:
Application
Source:
MsiInstaller
Date:
11/18/2014 7:16:45 PM
Event ID:
1024
Task Category: None
Level:
Error
Keywords:
Classic
User:
SYSTEM
Computer:
SJCDB3.intranet.co.st-johns.fl.us
Description:
Product: Microsoft SQL Server 2008 Database Engine Services - Update '{9145CF54-462E-4A28-8FB5-A44C93AD3716}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot
issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MsiInstaller" />
<EventID Qualifiers="0">1024</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-11-19T00:16:45.000000000Z" />
<EventRecordID>1764186</EventRecordID>
<Channel>Application</Channel>
<Computer>SJCDB3.intranet.co.st-johns.fl.us</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data>Microsoft SQL Server 2008 Database Engine Services</Data>
<Data>{9145CF54-462E-4A28-8FB5-A44C93AD3716}</Data>
<Data>1642</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>
</Data>
<Binary>7B38373544383436332D313135422D343444322D414432352D3731454337453833423843437D207B39313435434635342D343632452D344132382D384642352D4134344339334144333731367D2031363432</Binary>
</EventData>
</Event>
In the C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_191448\Detail.txt file I found the following around the time the error was reported
2014-11-18 19:16:30 Slp: Baseline Package Id sql_engine_core_inst_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_engine_core_inst_Cpu64 - NotInstalled on the baseline msi package sql_engine_core_inst_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu32
BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_rs_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_rs_Cpu64 - NotInstalled on the baseline msi package sql_rs_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu32 BaselineVersion=10.3.5500.0;
PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_is_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_is_Cpu64 - NotInstalled on the baseline msi package sql_is_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_is_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_is_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_is.msp PatchCode={E870296C-24CC-4D82-BB59-CD136692E2BD}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_bids_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_bids_Cpu64 - NotInstalled on the baseline msi package sql_bids_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_bids_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_bids_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_bids.msp PatchCode={EA407FA6-C2D1-4D3D-9227-B9E06DDDEFD0}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_ssms_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_ssms_Cpu64 - NotInstalled on the baseline msi package sql_ssms_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_ssms_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_ssms_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_ssms.msp PatchCode={8A81B870-E8F0-415D-AC80-13BEAA3EC8C8}
2014-11-18 19:16:30 Slp: Baseline Package Id: sql_common_core_Cpu64 - No patches are found by SQL Discovery on the installed package whose ProductCode is {5340A3B5-3853-4745-BED2-DD9FF5371331}
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_common_core_Cpu64 - NotInstalled on the baseline msi package sql_common_core_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_common_core_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_common_core_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_common_core.msp PatchCode={CF023E0F-3A19-4DBF-BCA3-0F664B447EDB}
The instance came up successfully and seems to be operating normally. Was there an error or was the KB installed correctly as the result of the windows update process indicated?
Is there a way I can verify this?I did some research on this particular KB article and it seems to be related to Master Data Services which I am not using. The KB was pushed automatically and I am not sure that it was a required update in our situation. I'd like to understand exactly
what caused the error message before initiating a repair as this is a production and not a test environment. Everything appears to be functioning properly and I have received direction from Microsoft in the past that information in some logs identified
as level 'error' are in fact to be ignored. I checked the windows update and this KB shows 'Successful' rather than failed or cancelled.
I would also like more information on why sql server services should not be stopped prior to allowing the OS patches to be applied. I have received messages in the past that stopping the services before service packs are applied
prevent the necessity for a reboot of the machine. I've never heard before that it is a best practice not to stop Sql service prior to applying patches. Once the services are stopped, I have our infrastructure admin start a VM snapshot on
the machine then kick off the windows update process. When done, I reboot the machine, test out Sql Server processes and then if all goes well give the ok to release the VM snapshot. I've supported various databases for 12 years, Sql Server for 5
years and this is the first time I've heard stopping the service manually can cause problems. If that is the case, I will certainly change how I do things....
I did run the discovery report and the results follow:
Microsoft SQL Server 2008 Setup Discovery Report
Product
Instance
Instance ID
Feature
Language
Edition
Version
Clustered
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
SQL Server Replication
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Full-Text Search
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSAS10.MSSQLSERVER
Analysis Services
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSRS10.MSSQLSERVER
Reporting Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
EVAULT
MSSQL10.EVAULT
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Basic
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Complete
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Connectivity
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Backwards Compatibility
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools SDK
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Integration Services
1033
Standard Edition
10.3.5520.0
No -
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.htmSorry 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] -
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.htmPlease 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 -
Installation issue : sql server 2008 r2 some services failed to installed on windows 7
I have been facing this problem while installing sql server 2008 r2.. i tried so many times but same result .. it shows sql server installed with some errors
database engine service : failed
SQL Server Replication : failed
Full-Text Search : failed
Analysis Services : failed
Reporting Services : failed
And my Log file (or) summary file is (it is in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log):
Overall summary:
Final result: User cancelled
Exit code (Decimal): -2068380094
Exit facility code: 1207
Exit error code: 1602
Exit message: User has cancelled.
Start time: 2014-08-14 21:15:26
End time: 2014-08-14 21:23:58
Requested action: AddNode
Machine Properties:
Machine name: MANJU-PC
Machine processor count: 4
OS version: Windows Vista
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER Database Engine Services
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER SQL Server Replication
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER Full-Text Search
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSAS10.MSSQLSERVER Analysis Services
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSRS10.MSSQLSERVER Reporting Services
1033 10.0.1600.22
No
Sql Server 2008
Management Tools - Basic 1033 Developer Edition
10.0.1600.22 No
Sql Server 2008
Management Tools - Complete 1033 Developer Edition 10.0.1600.22
No
Sql Server 2008
Client Tools Connectivity 1033 Developer Edition 10.0.1600.22
No
Sql Server 2008
Client Tools Backwards Compatibility 1033 Developer Edition 10.0.1600.22 No
Sql Server 2008
Client Tools SDK 1033
Developer Edition 10.0.1600.22 No
Sql Server 2008
Integration Services 1033 Developer Edition
10.0.1600.22 No
Package properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: D:\Softwares\JAVA & .NET SW\SQL Server 2008\SQL Server 2008\x86\setup\
Installation edition: DEVELOPER
User Input Settings:
ACTION: AddNode
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: *****
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
CONFIGURATIONFILE:
FAILOVERCLUSTERGROUP:
FAILOVERCLUSTERNETWORKNAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTANCENAME: <empty>
MEDIASOURCE: D:\Softwares\JAVA & .NET SW\SQL Server 2008\SQL Server 2008\
PID: *****
QUIET: False
QUIETSIMPLE: False
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: *****
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140814_210558\ConfigurationFile.ini
Detailed results:
Feature: Integration Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools SDK
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140814_210558\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException
Message:
User has cancelled.
Stack:
at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)Requested action: AddNode
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER Database Engine Services
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER SQL Server Replication
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER Full-Text Search
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSAS10.MSSQLSERVER Analysis Services
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSRS10.MSSQLSERVER Reporting Services
1033 10.0.1600.22
No
Sql Server 2008
Management Tools - Basic 1033 Developer Edition
10.0.1600.22 No
Sql Server 2008
Management Tools - Complete 1033 Developer Edition 10.0.1600.22
No
Sql Server 2008
Client Tools Connectivity 1033 Developer Edition 10.0.1600.22
No
Sql Server 2008
Client Tools Backwards Compatibility 1033 Developer Edition 10.0.1600.22 No
Sql Server 2008
Client Tools SDK 1033
Developer Edition 10.0.1600.22 No
Sql Server 2008
Integration Services 1033 Developer Edition
10.0.1600.22 No
Instead of installing SQL server instance you selected add node which is to be selected when SQL server installation is to be made on Node which is being added to cluster. Since your OS is not clustered I am sure you selected worng option.
Please right click on setup file and select run as administrator. Now installation window which pops up on that on left hand side select
installation and then on page that appears select 'New server standalone installation or add feature to existing installation'.
You already have SQL server 2008 installed on your machine as per feature discovery report
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles -
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 -
Data Streaming Destination in SQL Server 2014?
I would like to publish a SSIS package as a SQL view. I'm working with SQL Server 2014 Developer edition, and
SSDT-BI for Visual Studio 2013.
The instructions for SQL Server 2012 are here:
http://msdn.microsoft.com/en-us/library/dn600376(v=sql.110).aspx
The steps include downloading and installing the
Microsoft SQL Server 2012 Integration Services Data Feed Publishing Components.
I'm not able to find a similar package for SQL Server 2014. I've tried all kinds of maneuvers (installing the SSIS 2012 and SSDT-BI for VS2012 components, attempting to upgrade SSIS 2012 packages with the Data Streaming Destination to SSIS 2014,
etc.), but I've not found any way to be able to use a Data Streaming Destination in SSDT-BI for VS2013 targeting SSIS 2014. Am I missing something?It seems not be supported in BIDS 2013.
Regards, Leo
Maybe you are looking for
-
Reports for Itemwise ageing and Stock with opening and closing
Dear All, Is there any default reports in SAP for Item wise ageing and the stock status with opening stock,In and Out stock and closing stock for a given period. Regards, Shyam
-
Why can't a choose to create a Windows 7 install disk on my 2010 macbook air?
It is a 2010 macbook air, with lion 10.7.2 and bootcamp 4.0.1. the option to create a windows 7 install disk is greyed out, i have a trial version from microsoft website, but i also have a downloaded windows 7 both of them are .iso, i also have a 4gb
-
List of GL required in the integration of FI With SD & MM
Hi, I need a list of all the GL required for integration of FI with SD & MM. Please help me with the same. Regards, SAHU.
-
Just wanted to let everyone know. The StandardGetDirectoryDialog function in the sADMBasic suite does not function correctly. Adobe confirmed this to me when I filed a help request with them. Right now it just gives you back "parent-of-directory-you-
-
I just downloaded iOS 7 and it deleted my apps. I went to the App Store to download them again but it says that it is already downloaded. How do I get it back to my home screen? Please help!!!!