SQL 2012 Installation
Hello,
I'm reading the Hardware and Software requirements to install SQL Server 2012 and I´ve read the this point:
-The installation of SQL Server 2012 fails if you launch the setup through Terminal Services Client. Launching SQL Server Setup through Terminal Services Client is not supported.
Anybody has found with this scenario?
Hi Ruben,
People have faced issues while running setup of MSSQL 2012 using Terminal services Hardware and Software Requirements for Installing SQL Server 2012.
Similar issue is discussed and resolved here
SQL Server 2012 setup fails immediately (Error result: -2067529723)
Best option to take remote desktop of the server and then perform installation using Administrator login.
Hope this helps.
Regards,
Deepak Kori
Similar Messages
-
Hi, My name is Leonard and I am studying SQL. I have downloaded the newest MS SQL 2012 and also MS 2012 Hyper-V. I have set a MS 2012 Hyper-V on a laptop with AMD Turion 64 X2 and 3G of RAM (Planing
to add more to max at 8G).
Following the instructions in the free online
Administering Microsoft SQL Server 2012 Databases” Training Kit, I have set 6 virtual machines as instructed in the Training Kit. While the installation of the MS Server Core 2008 R2 SP1 completed with no
problem, the same cannot be said for the SQL Server 2012 installation. I have encountered an error that I have not seen anyone address in any of the SQL web forums.
After running the unattended setup instruction (Setup.exe /qs /ACTION=Install /FEATURES=SQLEngine /INSTANCENAME=MSSQLSERVER
/SQLSVCACCOUNT="Njowa\Pa$$worD>" /SQLSVCPASSWORD=" Pa$$worD” /SQLSYSADMINACCOUNTS="Njowa\lenny#4!@" /AGTSVCACCOUNT="NT AUTHORITY\Network Service"
/IACCEPTSQLSERVERLICENSETERMS) this is what I get after a series SQL setup
initiation windows popups then disappears.
The following error occurred:
Object reference not set to an instance of an object.
Error result: -2147467261
Result facility Code: 0
Result error Code: 16387
Please review the summary.txt log for further details
My question is: What instance of an object is not properly initialize in the Setup instructionsHello,
Please note that SQL Server requires at least 1 GB of RAM. The operating system (Windows Server) requires 2 GB of RAM (recommended) or 512 MB (minimum). This means any virtual machine that will receive the installation of a SQL Server instance requires 1.5
or 2 GB at least.
The behavior of SQL Server setup tells me that the virtual machine does not have enough memory assigned or .NET Framework 3.5 was not enable on Control Panel->Program
and Features before trying to install SQL Server.
The following thread is about another possible cause of this error:
http://social.msdn.microsoft.com/Forums/mr-IN/sqlsetupandupgrade/thread/575d3025-69f5-4152-a473-44496b008811
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
SQL 2012 installation Error-The MOF compiler could not connect with the WMI server
Hi all,
I am getting below error while installing SQL 2012 Dev edition in Win 8.1 Pro.
I am facing lot of issues while installing SQL 2012 in Win 8.1 Pro.Any other steps we need to take to install SQL 2012 in Win 8.1.
Thanks in advance.Installation:
Installation for SQL Server 2012
Hardware and Software Requirements for Installing SQL Server 2012
Installing the .NET Framework 3.5 on Windows 8 or 8.1
About "The MOF compiler could not connected with the WMI server" error message:
Please, verify the Windows Management Instrumentation has status "started" and is set with Startup Type "Automatic". (Alberto Morillo, SQLCoffee.com).
José Diz Belo Horizonte, MG - Brasil -
SQL 2012 installation for Failover Cluster failed
While installation of SQL 2012 on FOC validation fails on "Database Engine configuration" page with following error:
The volume that contains SQL Server data directory g:\MSSQL11.MSSQLSERVER\MSSQL\DATA does not belong to the cluster group.
Want to know how does SQL installation wizard queries volumes configured with Failover Cluster. does it:
- Enumerate "Physical Disk" resources in FOC
- does it enumerate all Storage Class resources in FOC for getting the volume list
- or it depends on WMI (Win32_Volume) to get volumes ?
The wizard correctly discovers volume g:\ in its FOC group on "Cluster Resource Group" and "Cluster Disk Selection" page. but gives the error on Database configuration page.
Any help in this would be appreciated.
Thanks in advance
Rakesh
Rakesh AgrawalCan you please check if there is any disk in the cluster which is not in online state? Please run below script following the steps.
1. Save a script as "Disk.vbs" and use
use CSCRIPT to run it.
2. Syntax: CSCRIPT <Disk.vbs> <Windows Cluster Name>
< Script>
Option Explicit
Public objArgs, objCluster
Public Function Connect()
' Opens a global cluster object. Using Windows Script Host syntax,
' the cluster name or "" must be passed as the first argument.
Set objArgs = WScript.Arguments
if objArgs.Count=0 then
wscript.Echo "Usage Cscript <script file name> <Windows Cluster Name> "
WScript.Quit
end IF
Set objCluster = CreateObject("MSCluster.Cluster")
objCluster.Open objArgs(0)
End Function
Public Function Disconnect()
' Dereferences global objects. Used with Connect.
Set objCluster = Nothing
Set objArgs = Nothing
End Function
Connect
Dim objEnum
For Each objEnum in objCluster.Resources
If objEnum.ClassInfo = 1 Then
WScript.Echo ObjEnum.Name
Dim objDisk
Dim objPartition
On Error Resume Next
Set objDisk = objEnum.Disk
If Err.Number <> 0 Then
WScript.Echo "Unable to retrieve the disk: " & Err
Else
For Each objPartition in objDisk.Partitions
WScript.Echo objPartition.DeviceName
Next
End If
End If
Next
Disconnect
</Script> -
Good Day
I am trying to install SQL 2012.
during the installation process it halts and I receive the following message:
TITLE: SQL Server Setup failure.
SQL Server Setup has encountered the following error:
Setup encountered a failure while running job UpdateResult.
Error code 0x876E0003.
I have spent hours looking through help blogs and other resources trying to find answers and help but have not been able to find a solution..!
Any advise or how to work around this would be greatly appreciated!
Thank you.Hi BrendanDev,
According to the error message, the issue may occur due to the permission issue with Windows update.
In this case, If you have the DefaultSetup.ini file in the \x86 or \x64 folders at the root level of the SQL Server source media, please open the DefaultSetup.ini file, and then add the UpdateEnabled or UpdateSource parameters to the file. If the DefaultSetup.ini
file does not exist, we can create it and copy it to the \x86 and \x64 folders at the root level of the SQL Server source media. And then we need to modify the "DefaultSetup.ini" file and set the switch "UpdateEnabled=False" which skips the product updates
in the installation.
For the detailed information, please refer to the link below:
http://blogs.msdn.com/b/petersad/archive/2011/07/13/product-update-in-sql-server-code-named-denali.aspx
If you need more assistance, please feel free to let me know.
Regards,
Heidi Duan -
SQL server 2014 and Sql 2012 installation on VMWare machine
Hi ,
Please let me know Can we Install SQL Server 2014 RTM version and SQL Server 2012 SP1 On Vmare machine version 9.
Does it Supports on VMware 9 . If yes please give me the links .
Thanks a lotHello,
You can find that on VMware Web site for their high end products only as you can see in the following URL. For VMware
9 you won't find it.
http://www.vmware.com/resources/compatibility/sim/interop_matrix.php
VMware 9 is a PC product that basically allows to install any product that works on Windows 8 and Windows Server 2012 or earlier. VMware 9 introduces support for Windows 8 and Windows 2012.
So, SQL Server 2012 and SQL Server 2012 should install on Windows 8/Windows 2012 RTM with no issues on a VMware 9 virtual machine. Earlier operating systems may require installation of service packs and updates as explained on the following URLs.
https://msdn.microsoft.com/en-us/library/ms143506(v=sql.120).aspx
https://msdn.microsoft.com/en-us/library/ms143506(v=sql.110).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
SQL 2012 Installation - ProductVersion?
I've been trying to install SQL Server 2012 on a brand new server for days. At first I was getting an error regarding not being able to find certain files - this problem exactly: http://stackoverflow.com/questions/11724160/installing-sql-server-2012-error-the-system-cannot-open-the-device-or-file-spec,
but after trying multiple times, I finally remoted into the server and ran the installation from the CD. From one error to this new one.
SQL Server Setup has encountered the following error:
1: 2228 2: D:\1033_ENU_LP\x64\setup\x64\sqlls.msi 3: Property 4: SELECT `Value` FROM `Property` WHERE `Property` = 'ProductVersion' .
We have a site license for SQL so the CD and key were provided to me. I saw one solution online regarding finding the product code and then looking in the registry. I've seen a bunch of upgrade codes in DLL files (on the CD), but not a product code, and
if I'm supposed to use one of those to lookup in the registry, I don't know which. Also, the product codes from the example solutions look nothing like my product key, so I'm assuming they're the same thing.
Any help would be GREATLY appreciated. The sooner I can install this, the sooner our pharmacy can have a working server.Hi Courtney Kinder,
I’m writing to follow up with you on this post. Was the problem resolved?
If not, I recommend you uninstall SQL Server 2012 completely and reinstall again. According to your description, when you install SQL Server 2012 from the CD, the error will occur. As other post, you should help us to collect the detailed error
message, it is very useful for our research.
In an clean server, you install SQL Server 2012, we need to verify if it meet the hardware and software requirements in the server. You can review the following
article about step by step installation guide for SQL Server 2012.
http://sivasqlbi.blogspot.com/2012/03/sql-server-step-by-step-installation.html
In addition, about finding the product key from an installed instance, you can use T-SQL script or a power shell script. For more information, you can review the following post.
http://social.msdn.microsoft.com/Forums/en-US/0cb2286a-7d0c-49ad-8248-aa4a0e381e52/finding-sql-server-2008-product-key-from-an-installed-instance?forum=sqlgetstarted
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support -
Problem installing SQL Server 2012 SP1: "managed sql server installer has stopped working"
Hello,
I have a big problem.
I just downloaded SQL Server 2012 SP1 and I only want to install SSMS. The installer always crashes with an error message "managed sql server installer has stopped working".
I already tried all solutions from Google for this problem but nothing works.
Can someone help me plase?
My System: Window 8 Pro with Visual Studio 2012.
Thanks
SvenWould you please uplaod/share SQL Server setup logs
C:\Program
Files\Microsoft
SQL Server\110\Setup
Bootstrap\Log\20130125_133342
to file sharing service like SkyDrive.com
FAQ
Regards,
Ahmed Ibrahim
SQL Server Setup Team
My Blog
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and "Vote as Helpful"
on posts that help you.
This can be beneficial to other community members reading the thread. -
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 -
i have a small sharepoint farm "2 servers" (WFE) and SQL Server 2012 ,
i installed rsSharePoint for reporting services , as a read the Reporting services is Application Service with SQL 2012 not as SQL 2008 R2 with SharePoint integrated mode, so after installation when am trying to configure the SQL Server
Reporting Services Application services i got the below error :
"Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key"
any kind of help would be much appreciated .I'm having the same issue, but to me it seems like the instructions I've seen are all over the place. I already have SP 2013 and SQL 2012 SP 1 installed. I already added the features for Reporting Services - Sharepoint and Reporting Services
Add-in for SharePoint Products. I didn't see the Reporting Service service in CA, so I ran the powershell scripts to add SPRSService and SPRSServiceProxy.
My initial quest, was to get the BI features enabled, which took me on the journey of adding the Report Services, then I got the error.
Then when I read this about installing the BI features
http://blogs.msdn.com/b/querysimon/archive/2012/11/26/installing-the-bi-features-of-sharepoint-2013.aspx, which I already had SQL and SP installed. Do I have to rerun and selct the SQL Server PowerPoint for SharePoint option? I have the PowerPoint
Configuration Tool on my SQL server, I run it and I get PowerPivot for SP 2013 Configuranoi is missing prerequisits: SP 2013 EE is required. Which I have EE.
Is Reporting Services different or in addition to the BI Feature (PowerPivot)?
Have I missed a step?
Thanks for you help.
Kim
Kim.Williams -
Change SQL 2012 Security roles after installation
I installed SQL 2012 SP1 Standard edition and during the setup it asked me for the users for various service . I choose to keep them as default
After the installation i could see the services were not started, so i changed everything to Local System
Also in future i may need to change them to run under some domain service account.
What steps do i have to take to make sure approprate rights are granted to the accounts that run the SQL services. I could see Local System just had Public security role.
Can someone guide me on verifying what the security roles for accounts should be.running them as domain account is a good thing and it does not need to part of admin group.
make sure your domain account has access backup paths/locations.
Also, make sure your account has "perform volume maintanence tasks" - to make use of INF.
Is your system 64 bit or 32 bit. if 64 bit, you are okay else you will need to enable lock pages in the memory for the service.
Below are the links to some articles that talk about this:
http://www.mssqltips.com/sqlservertip/2503/how-to-create-secure-sql-server-service-accounts/
http://blogs.msdn.com/b/askjay/archive/2011/02/28/required-rights-for-sql-server-service-account.aspx
http://technet.microsoft.com/en-us/library/ms191543(v=sql.110).aspx
http://blogs.msdn.com/b/sqlserverfaq/archive/2010/05/28/inf-permissions-required-for-sql-server-service-account-to-use-ssl-certificate.aspx
Hope it Helps!! -
SQL 2012 SP1 installation quick questions
I am installing my first SQL 2012 SP1 Enterprise Core (x64). The installation failed to install some services due to an error installing .Net framework 3.5. It was able to install successfully several features including Analysis Services
and Integration services, but not the Database Engine, Management tools and Reporting services.
Note: I ran the set up and my user is an administrator in the target server, but I did not right clicking on setup.exe and "Run as administrator" .
I have two questions
1) Did I had to run the setup by Right clicking on setup.exe and "Run as administrator"?
2) Now that my installation failed. After installing the missing requirements....Do I:
a) Uninstall the current failed installation
b) Do I attempt to install again "on top of the existing installation".
c) Redo the whole server and start fresh.
I am open to expert suggestions. Please help
PaulinoHello,
1. If you are already logged in as Administrator, there is no need to use the Run as Administrator option.
2. I would choose to uninstall everything and install again. Since were are installing from the Command Prompt, and we do not have the
GUI, and we are not familiar with the command line options.
Please use the following article to install SQL Server 2012 on Windows Server Core:
http://www.sqlcoffee.com/SQLServer2012_0005.htm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
SQL Server 2012 Installation Issue
Hi
Not sure if this is the correct forum for this but I'll post anyway.
Ialready have sql 2005 and 2008r2 installed on my local machine running windows 7, 64 bit.
I recently tried to install sql 2012 but ran into a problem that I'm stumped by. The installation runs fine, no errors or issues. When I start 2012 the SS Management studio window appears but the usual splash screen in the middle of the window asking to
to connect to a server does not. If I try hitting any of the meny items at the top of the screen the SSMS window just hangs.
I have service pack 1 installed also. I uninstalled and tried again but still no luck. my SQL 2005 and 2008r2 version are still fine and run as normal. I also tried installing sql 2014 to see if that would work but I had the same issue as with 2012.
Any ideas anyone?
thanks in advance
Hi,
Both SQL Server 2012 and SQL Server 2014 require .NET Framework 4.0 which does not required by the previous versions.
Make sure that . NET Framework 4.0 has been successfully installed on your system before you install SQL Server
Hardware and Software Requirements for Installing SQL Server 2014
http://msdn.microsoft.com/en-us/library/ms143506.aspx
Thanks.
Tracy Cai
TechNet Community Support -
SCOM 2012 Installation problem - SQL Instance name
Hi All
Strange problem here, I wonder if anyone else has had the same issue.
I have a two-node SQL Server 2014 (Enterprise) Database server configured with a "SQL AlwaysOn Availability Group & Listener". The listener DNS name is: sql-ag-listener
On a separate server VM I attempted to install SCOM 2012 R2 - but when it came to the setup prompt to enter the "Servername & Instance" for the SQL server / Databases it will not accept my SQL AG Listener DNS name. However if I enter any
of the two individual SQL node names (SQL1 or SQL2) then it does accept those values and proceeds with the setup wizard. I do have a DNS entry for the SQL AG name.
All VMs are hosted in Azure. The SQL Servers are in their own Cloud Service and the SCOM MS Servers are in their own Cloud service.
I tried moving one of the SCOM MS Servers to the same Cloud Service container as the SQL Servers - still the same result.
Interestingly (as a test) - I started the SCOM 2012 Installation wizard on one of the SQL Servers and it DID accept the SQL AG value as the "Servername & Instance".
No firewalls are on. The VM endpoints allow SQL port 1433. Also, I can Telnet to the SQL Servers using 'telnet > O sql-ag-listener 1433' - response = Connected....
Not sure why this wont accept my virtual SQL AG name....?
thanksHi,
As when you install SCOM on one of your SQL server, then the AG name can be resolved, so it seems like this issue related with network resolution.
On the server where you want to run SCON setup, please use NSLOOKUP command to make sure it can the AG name to an IP address.
In addition, when you run the setup, don't select reporting server, as reporting server role need to install on a SQL server holding SSRS.
We still can install SCOM on normal database, and then add them into availability group later:
Add SCOM Databases to Availability Groups
http://www.tech-coffee.net/alwayson-part-8-methods-to-add-database-scom/
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] -
After
sql server 2012 installation, I attached my production db. Because of some reasons, i
changed sql engine account from network service user to system user by means of sql server configuration manager.
Now , there isn’t
a problem at sql server running system. But
I have doubts that
this can produce problems later. Because sql server database engine account must have privileges that listed below;
Log on as a service (SeServiceLogonRight)
Replace a process-level token (SeAssignPrimaryTokenPrivilege)
Bypass traverse checking (SeChangeNotifyPrivilege)
Adjust memory quotas for a process
(SeIncreaseQuotaPrivilege)
Permission to start SQL Writer
Permission to read the Event Log service
Permission to read the Remote Procedure Call service
While sql server installation, setup gives these
privileges to network service user automatically, but changing user by means of sql confugarition manager does not give these
privileges.
Now, system user has privileges listed below. And sql server has been running for 1,5 months without any problems.
Log on as a service (SeServiceLogonRight)
Bypass traverse checking
(SeChangeNotifyPrivilege) (Everyone user has his privileges. So i think that system user has this privilege also)
What problems can occur because of this situation? Shall i give other privileges to system user and restart sql server or not? And how can i give these privileges to system user listed below;
Replace a process-level token (
this can be set from user rights assignments)
Adjust memory quotas for a process
(this can be set from user rights assignments)
Permission to start SQL Writer (
? - give advice )
Permission to read the Event Log service (
? - give advice )
Permission to read the Remote Procedure Call service (
? - give advice )Our server is windows server 2008 r2 enterprise edition. I have looked the bunch of permissions in user rights menu that is in local security policy settings gui.
And i have seen those permissions below were not granted to system user;
Bypass traverse checking (SeChangeNotifyPrivilege)
Adjust memory quotas for a process
(SeIncreaseQuotaPrivilege)
So, briefly you say, don't panic ?
Maybe you are looking for
-
How to create a key figure in SNP plannignbook which generate FA type order
Hello trying to create a Key Figure in SNP planning book which generates FA type orders could kindly suggest how to do it? thanks elena
-
Where is the Error-Handler config DB file?
Where is the Error-Handler config DB file? <P> All the Config DB files are in the config directory under the postoffice directory. Each config file has the same name as the Module it's the config for (e.g. Error-Handler contains the configs for the E
-
HTML5 Canvas issue with iOS Safari
I am trying to build a painting application in HTML5. I have an HTML5 Canvas in a div. This div is masked with an SVG file using -webkit-mask. On iOS Safari and in iBooks Fixed Layout: When you zoom the page by gesture, the mask suddenly stops workin
-
Load default configuration in BIOS to fix sound, caused another problem
Hey ! I have had problem to get sound in my T61, and used Lenovo support, Troubleshooting, to fix it. I did as it told in Lenovo Support. In BIOS Setup utility menu setup I pressed F9. Then I selected YES to load the default configuration. After that
-
Hidden Classic Report - With Download Links
Hi All, I have a requirement. I am displaying certain user information through a form i.e with all the fields in the form as READ ONLY / DISLAY ONLY. I need a XLS/PDF download button allowing users to click and download the particular details on the