Help please! - Unable to install MS SQL Express 2012 on laptop.

[IainB]

@x16wda + @Shades:
Thanks for the suggestion/reminder. I meant to check  the Powershell version. Here 'tis: (not identical to what @x16wda gave, but same S/V)

Code: Text [Select]

1. Name                           Value                                                                                
2. ----                           -----                                                                                
3. PSVersion                      3.0                                                                                  
4. WSManStackVersion              3.0                                                                                  
5. SerializationVersion           1.1.0.1                                                                              
6. CLRVersion                     4.0.30319.18444                                                                      
7. BuildVersion                   6.2.9200.16481                                                                        
8. PSCompatibleVersions           {1.0, 2.0, 3.0}                                                                      
9. PSRemotingProtocolVersion      2.2

[lanux128]

from my experience, dotnet runtimes are easily broken and a repair/reinstall might help. the following links are useful and i have used them in the past.

• http://blogs.msdn.co...eshooting-guide.aspx
• http://singularlabs....osoft-net-framework/

[4wd]

Was there any log files written to folders under C:\Program Files\Micrsoft SQL Server\110\Setup Bootstrap\Log ?

Supposedly they're written at each attempted installation and contain a lot more information, an example of the logs are in this thread.

[Stoic Joker]

from my experience, dotnet runtimes are easily broken and a repair/reinstall might help. the following links are useful and i have used them in the past.

• http://blogs.msdn.co...eshooting-guide.aspx
• http://singularlabs....osoft-net-framework/

-lanux128 (March 29, 2014, 11:06 PM)

I'm going to +1 this just to draw a bit more attention to it. I've been quietly watching this thread for awhile because I haven't had a lot of SQL installs go bad, so didn't have much to add. However I have been wondering about exactly this, as I have seen .NET flake out and cause all sorts of havoc, which necessitated ripping it out by the roots and starting over. I suspect that the removal tool - one of my favorites - is well worth exploring as it has gotten me out of several tight spots much like what is being described here.

[IainB]

@lanux128:
Figuring that it couldn't hurt, I ran the repair tool from Download Microsoft .NET Framework Repair Tool from Official Microsoft Download Center

(Supports repairing the .NET Framework 4.5.1, 4.5, 4 and 3.5 SP1 (includes .NET 3.0 SP2 and .NET 2.0 SP2).

Then I reran the 02 SQLEXPR_x64_ENU - v11.0.3000.0 (Express DB only 64-bit).exe
Result: It still abended with the same error as before.

@4wd: I do not have a directory C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log
(You missed out an "o" in "Microsoft" there.)

[4wd]

(You missed out an "o" in "Microsoft" there.)

-IainB (March 30, 2014, 08:54 AM)

The joys of Cut/Paste ...