I usually install sqlserver 2008r2 on Windows Server 2008
Today, because I want to open a few sqlserver2008r2 virtual machines on the machine for testing
The two virtual machines already on this machine are useful (domain control and shared storage)
If you install windows 2008r2 again, it will be stuck, and your mind will be hot.Install Windows 2003, this thing is relatively light
Temporarily DOWN a SERVER2003 installation package from the Internet
After installing the system, clone the virtual machine, and distribute the domain. After setting up an IP address
Started to install SQLSERVER2008R2
A little setup.exe bang, pop a dialog box. NET Framework 3.5 is not installed
Sick, isn't there Framework 3.5 in the SQLSERVER installation package? Why don't you pretend to be yourself.
In the SQLSERVER installation package, I successfully found the directory where the .NET Framework was placed, and there were 2.0, 3.0, and 3.5 in it
While clicking, I was secretly proud, thanks to the fact that I had installed a lot of SQL over the years, and even remembered the installation package directory clearly
Boom, another dialog box popped up, saying that it was not installed. .NET Framework 2.0sp1 cannot be installed with .NET Framework 3.5
I go, go to the .NET Framework 2.0 directory and look for it, there is no sp1 patch
The virtual machine cannot be connected to the public network due to setting reasons (failover cluster has been prepared, and the network card is not moved)
Back to my PC, I came back with SP1 from a download station DOWN at the risk of poisoning
Pass to the virtual machine and install
Reinstall. NET Framework 3.5 Dong Another dialog box requires sp1 of 3.0
Return to the machine under 3.0sp1 to install
After a toss, finally. NET Framework 3.5 is installed
Then click on the SQLSERVER setup.exe and it will show that .NET Framework 3.5 has SP1
sp1, sp1, sp1, your sister! Can't you make up for it in one go?
Search again, then hit 3.5SP1
Playing a checkmark under WINDOWS2008 has become a nightmare for SP1 when it is put on Windows 2003
Do you think this is the end?
After being teased for a while, I finally saw the familiar SQLSERVER installation interface, and I configured it all the way
At the last step, boom, pop a dialog box saying WINDOWS2003 there is a full-text filtered patch (KB937444) that needs to be installedOtherwise, if you don't continue, your sister, there is still a patch, why didn't you say earlier, I have installed it here Remove the next patch, hit it, and prompt a restart. The SQLSERVER installed to the last step stopped again. I have to do it all over again!
--- above is a true story, a full-time SQLSERVER DBA
It's a shame to be molested SQLSERVER2008 installed under WINDOWS 2003!
|
Posted on 11/26/2014 3:40:46 PM
|
|
|
