Main Area and Open Discussion > General Software Discussion
Help please! - Unable to install MS SQL Express 2012 on laptop.
IainB:
Computer Properties screen:
By the way, the file I designate as 02 SQLEXPR_x64_ENU - v11.0.3000.0 (Express DB only 64-bit).exe has an MD5 sum of 1da4cc5c1711595b91e8f347ded64c33.
I ran the command:
"C:\Workdata.012 (Software)\ARCHIVE\Microsoft software\SQL 2012 Express\64-bit\02 SQLEXPR_x64_ENU - v11.0.3000.0 (Express DB only 64-bit).exe" /log c:\SQL.log
EDIT: 2014-03-30 1139hrs
The result: Abended with the usual error message, and a log file is produced in C:\TEMP:
File: SqlSetup.log:
--- Code: Text ---03/30/2014 01:03:56.694 ======================================================================03/30/2014 01:03:56.698 Setup launched03/30/2014 01:03:56.703 Attempting to determine media source03/30/2014 01:03:56.704 Media source value not specified on command line argument.03/30/2014 01:03:56.705 Setup is launched from media directly so default the value to the current folder.03/30/2014 01:03:56.709 Media source: c:\750914361e488dc81484f630d63c\03/30/2014 01:03:56.713 Attempt to determine media layout based on file 'c:\750914361e488dc81484f630d63c\mediainfo.xml'.03/30/2014 01:03:56.758 Media layout is detected as: Core03/30/2014 01:03:56.760 Media is a slipstream package03/30/2014 01:03:56.763 Only patch related actions can run patch setup.exe, so continuing to run setup.exe from media.03/30/2014 01:03:56.784 Error: This OS is not supported03/30/2014 01:04:03.779 SQM key not found03/30/2014 01:04:03.807 Setup closed with exit code: 0x84C4003403/30/2014 01:04:03.808 ======================================================================
4wd:
It looks like during a normal installation, the log files gets written here:
C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\<date>_<time>\??????????????.log
Any luck with that?
x16wda:
This page looks like a newer version of the page you linked to a few posts above, and it seems to indicate you need .NET 4.0 even for Express installations:
.NET 3.5 SP1 is a requirement for SQL Server 2012 when you select Database Engine, Reporting Services, Master Data Services, Data Quality Services, Replication, or SQL Server Management Studio, and it is no longer installed by SQL Server Setup.
• If you run Setup on a computer with the Windows Vista SP2 or Windows Server 2008 SP2 operating system, and you do not have .NET 3.5 SP1, SQL Server Setup requires you to download and install.NET 3.5 SP1 before you can continue with the SQL Server installation. The error message includes a link to the download center, or you can download .NET 3.5 SP1 from Windows Update. To avoid interruption during SQL Server Setup, you can download and install .NET 3.5 SP1 before you run SQL Server Setup.
• If you run Setup on a computer with the Windows Server 2008 R2 SP1 operating system, you must enable .NET Framework 3.5 SP1 before you install SQL Server 2012.
• If you run Setup on a computer with the Windows Server 2012 or Windows 8 operating system, the SQL Server Setup automatically downloads and installs the .NET Framework 3.5 SP1. This process requires internet access.
If there is no internet access, it is required to download and install .NET Framework 3.5 SP1 before you run Setup to install any of the above mentioned components. For more information about the recommendations and guidance on how to acquire and enable .NET Framework 3.5 in Windows Server 2012 or Windows 8, see Microsoft .NET Framework 3.5 Deployment Considerations (http://msdn.microsoft.com/library/windows/hardware/hh975396).
.NET 4.0 is a requirement for SQL Server 2012. SQL Server installs .NET 4.0 during the feature installation step.
• If you are installing the SQL Server Express editions, ensure that an Internet connection is available on the computer. SQL Server Setup downloads and installs the .NET Framework 4 because it is not included in the SQL Server Express media.
• SQL Server Express does not install .NET 4.0 on the Server Core mode of Windows Server 2008 R2 SP1 or Windows Server 2012. You must install .NET 4.0 before you install SQL Server Express on a Server Core installation of Windows Server 2008 R2 SP1 or Windows Server 2012.
--- End quote ---
Powershell 2.0 also:
SQL Server 2012 does not install or enable Windows PowerShell 2.0; however Windows PowerShell 2.0 is an installation prerequisite for Database Engine components and SQL Server Management Studio. If Setup reports that Windows PowerShell 2.0 is not present, you can install or enable it by following the instructions on the Windows Management Framework page.
--- End quote ---
You can check the Powershell version from a powershell window:
PS C:\windows\system32> echo $PSVersionTable
Name Value
---- -----
PSVersion 3.0
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
CLRVersion 4.0.30319.18449
BuildVersion 6.2.9200.16628
PSCompatibleVersions {1.0, 2.0, 3.0}
PSRemotingProtocolVersion 2.2
--- End quote ---
I hate to suggest to anyone they install any extra .net, but maybe that'll help?
IainB:
@4wd and others: I just found the log file, and inserted the details into my post above, for completeness. It was in C:\TEMP ... (Doh!).
Sorry, I would have found it earlier using Everything search, but my tired mind had forgotten I had left the Enable Regex switch ON, and I only just now discovered that ... :-[
Amazing how a good night's sleep can unfuddle one's mind.
@x16wda: Thanks for the helpful comments. I found it all a bit confusing, but after reading all the references I could find, the situation seems to be that:
* Either .NET Framework 3.5 or 4.0 is a prerequisite for the Express install, but both are not necessary.
* Thus, if you don't have the prerequisite .NET Framework 3.5, then .NET Framework 4.0 is a prerequisite for the Express install. This (.NET 4.0) is fortunately already included in Windows 7 SP1 (e.g. my configuration) by default.
* Powershell is not defined a prerequisite for the Express install (as far as I am aware) and is already in Windows 7 SP1 (e.g. my configuration) by default anyway.
It sometimes seem to me that if MS had deliberately wanted to make the conditional logic for installing their "FREE" proggies so tortuous, then they probably couldn't have done much better than seems to have been achieved in the case of this Express install. Then again, maybe it was just a screwed up afterthought (i.e., not originally planned) to offer the FREE Express install. It'll be great if/when I can get it working... :(
Shades:
Although Windows 7 comes standard with PowerShell, it still can be that the version on your system does not meet the demands of the SQL Server 2012 installer. It doesn't hurt to check and update if need be.
Providing Express as an afterthought I don't know. For years MS gives you Express versions of their development software and that has helped them a lot with snaring/trapping developers. A tactic the Oracle database guys took over and it worked for them too. So Microsoft can't and doesn't stay behind in this field of software.
However, they should have taken a better look at how Oracle did it. Their installer works with a lot less hassle, all dependencies are already integrated and when it is finished you have a nice web-interface to manage the test DB that has been setup for you.
On my system SQL Server 2012 Express installed only after missing dependencies were downloaded and installed. I found the management interface a lot less newbie friendly when comparing to the Oracle XE product. It's not difficult, especially for those who work with MMC consoles regularly.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version