WTF goes on with MS SQL server & CRAP!!!!!

WxMan1 · Oct 16, 2009, 04:35 AM

I could spit nails.

I spent the last week (no joke) trying to get MS SQL Server 2008 Express installed onto my machine (its a requirement for my VB II class).

I spent two weeks I spent two weeks aa;focioicoc s;gh
fdoio
f

dhf'll;f;f;f;f;f

.................................................. ..

.
.
hh

fdrr6

An EXTRA 2 GB?!?!?!?!?!? G*d D*#_n it!

WxMan1 · Dec 7, 2009, 01:09 AM

That probably didn't make a whole lot of sense, but believe me it was an utter nightmare. Read below for salient details.

What I ascertained was that what has to be the absolute first step was if a version of Visual Studio exists on the box to which SQL Server will be installed, VS MUST be uninstalled completely. That WILL necessitate use of MS' VS Uninstall utility AND MS Windows Installer Cleanup Utility. The latter one requires a delicate touch akin to handling fuming nitroglycerin. If you're comfortable editing the registry hive w/out a safety net, you're golden. OTHERWISE: make an image backup prior to embarking upon your quest grasshopper.

This will allow installation and configuration of SQL Server 2008 Express and the SQL Server Configuration Manager patched to the gills w/SP1. Then and ONLY then should one install Visual Studio followed up VS SP1. The reason being is that SQL Server installs VS components that clash with previous VS installation, and file system protection will cause the SQL Server installation to ab-end. Ab-ended installation of either VS OR SQL Server are BAD BAD BAD BAD. DId I say they're not good? I mean they're REALLY REALLY REALLY NOT GOOD. EVERY single installation attempt is a seperate installation (whether successful or not) and you'll NEVER get a clean install if there's a previous installation attempt that failed; hence the neeed to run Windows Installer Cleanup utility.

The MOF entries for WMI namespace issue will still need to be resolved, however, but some things just can't be helped I guess.

Read gory details below about my recent two and half week escapades getting SQL Server installed (you don't even want to know how many times I had to reformat, repartition and restore disk images) - and don't even get me started on the times when the Ghost image wouldn't allow partition restore to systemroot partition of NTFS drive - AAAAAAAARRRRRRGGGGGGGHHHHH:

Aaron Bertrand : The XP SP3 / MSXML6 SP2 / SQL Server debacle

In the following link, scroll down the right pane until you get to the "community review" section: SQL Server Management Studio Express

Visual Studio 2008 Service Pack 1 ATL Security Update (KB971092 - 8/3/2009) - A security issue has been identified that could allow an attacker to compromise your Windows-based system with Visual Studio 2008 Service Pack 1.

(http://www.microsoft.com/downloads/d...displaylang=en)

ATL Security Update KB971092: If Microsoft Update continuously offers this patch, it may be necessary to clear up some disk space. The patch is 365MB and contains headers, libraries, and executables for most of Visual C++ including ATL and the CRT. This patch, however, may require up to 3.7GB to install with a possible residual footprint of about 1.7GB if you have all Visual C++ features installed.

WTF!?!?!??!?!?!?!?!?!?!?!?!?

Workaround:
Heath Stewart's Blog : ATL Security Update KB971092 still offered on Microsoft Update

Microsoft Visual Studio 2008 Service Pack 1 Update (KB974479 - 9/8/2009):
There is a known incompatibility between the Microsoft Windows Software Development Kit for Windows Server 2008 and .NET Framework 3.5, and Microsoft Visual Studio 2008 Service Pack 1 which is manifested when the ATL Security Update (KB971092) is installed. This update addresses the issue.

Download: Download details: Microsoft Visual Studio 2008 Service Pack 1 Update (KB974479)

The default instance name is set incorrectly when you install SQL Server 2008 Express (FIX: The default instance name is set incorrectly to SQLEXPRESS when you install SQL Server 2008 Express)

(Selecting the "Default Instance" option in SQL Server 2008 Express RTM has no effect | Microsoft Connect)

Problem:
Cannot connect to WMI Provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 servers with SQL Server Configuration Manager.

Invalid class [0x80041010]

Solution:

run mofcomp from cmd prompt:

cd C:\Program Files\Microsoft SQL Server\100\Shared

mofcomp sqlmgmproviderxpsp2up.mof

To repair MOF namespace & SQL component WMI entries:
Repairing and re-registering the WMI
AumHa Forums • View topic - [DONE] xp security center +NOD32 +WMIDiag.vbs (script at very end of thread)

Oct 16, 2009, 04:35 AM	#1
WxMan1 HardwareHeaven Lover Join Date: Dec 2007 Posts: 214 Rep Power: 39	WTF goes on with MS SQL server & CRAP!!!!! I could spit nails. I spent the last week (no joke) trying to get MS SQL Server 2008 Express installed onto my machine (its a requirement for my VB II class). I spent two weeks I spent two weeks aa;focioicoc s;gh fdoio f dhf'll;f;f;f;f;f .................................................. .. . . hh fdrr6 An EXTRA 2 GB?!?!?!?!?!? Gd D#_n it!

Dec 7, 2009, 01:09 AM	Thread Starter #2
WxMan1 HardwareHeaven Lover Join Date: Dec 2007 Posts: 214 Rep Power: 39	Re: WTF goes on with MS SQL server & CRAP!!!!! That probably didn't make a whole lot of sense, but believe me it was an utter nightmare. Read below for salient details. What I ascertained was that what has to be the absolute first step was if a version of Visual Studio exists on the box to which SQL Server will be installed, VS *MUST* be uninstalled completely. That WILL necessitate use of MS' VS Uninstall utility AND MS Windows Installer Cleanup Utility. The latter one requires a delicate touch akin to handling fuming nitroglycerin. If you're comfortable editing the registry hive w/out a safety net, you're golden. OTHERWISE: make an image backup prior to embarking upon your quest grasshopper. This will allow installation and configuration of SQL Server 2008 Express and the SQL Server Configuration Manager patched to the gills w/SP1. Then and ONLY then should one install Visual Studio followed up VS SP1. The reason being is that SQL Server installs VS components that clash with previous VS installation, and file system protection will cause the SQL Server installation to ab-end. Ab-ended installation of either VS OR SQL Server are BAD BAD BAD BAD. DId I say they're not good? I mean they're REALLY REALLY REALLY NOT GOOD. EVERY single installation attempt is a seperate installation (whether successful or not) and you'll NEVER get a clean install if there's a previous installation attempt that failed; hence the neeed to run Windows Installer Cleanup utility. The MOF entries for WMI namespace issue will still need to be resolved, however, but some things just can't be helped I guess. Read gory details below about my recent two and half week escapades getting SQL Server installed (you don't even want to know how many times I had to reformat, repartition and restore disk images) - and don't even get me started on the times when the Ghost image wouldn't allow partition restore to systemroot partition of NTFS drive - AAAAAAAARRRRRRGGGGGGGHHHHH: Aaron Bertrand : The XP SP3 / MSXML6 SP2 / SQL Server debacle In the following link, scroll down the right pane until you get to the "community review" section: SQL Server Management Studio Express Visual Studio 2008 Service Pack 1 ATL Security Update (KB971092 - 8/3/2009) - A security issue has been identified that could allow an attacker to compromise your Windows-based system with Visual Studio 2008 Service Pack 1. (http://www.microsoft.com/downloads/d...displaylang=en) ATL Security Update KB971092: If Microsoft Update continuously offers this patch, it may be necessary to clear up some disk space. The patch is 365MB and contains headers, libraries, and executables for most of Visual C++ including ATL and the CRT. *This patch, however, may require up to 3.7GB to install with a possible residual footprint of about 1.7GB if you have all Visual C++ features installed.* *WTF!?!?!??!?!?!?!?!?!?!?!?!?* Workaround: Heath Stewart's Blog : ATL Security Update KB971092 still offered on Microsoft Update Microsoft Visual Studio 2008 Service Pack 1 Update (KB974479 - 9/8/2009): There is a known incompatibility between the Microsoft Windows Software Development Kit for Windows Server 2008 and .NET Framework 3.5, and Microsoft Visual Studio 2008 Service Pack 1 which is manifested when the ATL Security Update (KB971092) is installed. This update addresses the issue. Download: Download details: Microsoft Visual Studio 2008 Service Pack 1 Update (KB974479) The default instance name is set incorrectly when you install SQL Server 2008 Express (FIX: The default instance name is set incorrectly to SQLEXPRESS when you install SQL Server 2008 Express) (Selecting the "Default Instance" option in SQL Server 2008 Express RTM has no effect \| Microsoft Connect) Problem: Cannot connect to WMI Provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 servers with SQL Server Configuration Manager. Invalid class [0x80041010] Solution: run mofcomp from cmd prompt: cd C:\Program Files\Microsoft SQL Server\100\Shared mofcomp sqlmgmproviderxpsp2up.mof To repair MOF namespace & SQL component WMI entries: Repairing and re-registering the WMI AumHa Forums • View topic - [DONE] xp security center +NOD32 +WMIDiag.vbs (script at very end of thread)