SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL SERVER 2008 64 bit installation on Windows 2008 - Error code 32


SQL SERVER 2008 64 bit installation on Windows 2008 - Error code 32

Author
Message
EdVassie
EdVassie
SSCertifiable
SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)

Group: General Forum Members
Points: 5721 Visits: 3860
Sounds like you had a problem while the Setup Support Files were being installed. Until this process has got near finishing you do not get any log files.

The most common reason for the Setup Support Files install to fail is a failure to install a pre-requisite component. You are not using Express Edition media so all pre-requisites are packaged with the SQL install media, and the SQL installer will automatically install any missing components.

Having said all this, I recently tried a SQL install on Windows 2008 and had a failure installing .Net 3.5 SP1. I needed to track down the .Net install log files (Google can help in this) and found that the command OCSETUP for component NetFx3 failed because option NetFx3 was unknown. This is very odd, as using OCSETUP with option NetFx3 to install .Net 3.0 is a standard part of Windows 2008. (The .Net 3.5 SP1 install will make sure that all of .Net 2.0, .Net 2.0 SP2, .Net 3.0, .Net 3.5 and .Net 3.5 SP1 are installed, and uses a mixture of .MSI files and OCSETUP to do this.) I have not done much more troubleshooting, but suspect that an update from Microsoft has killed off the ability to use OCSETUP to install .Net 3.0 on W2008.

I have run many .Net 3.5 SP1 installs on W2008 as part of testing FineBuild, and the Windows instance with the problem allowed .Net 3.5 SP1 to install OK until a MS patch update. My FineBuild test instances are typically way behind in MS patching, so I do not know if the problem is caused by a recently-issued patch.

My plan to confirm this is to build a new W2008 instance using just RTM media and rerun the .Net 3.5 SP1 install. This is easy to do with a new guest machine, I just need about 3 hours to do the build and the test.

Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005. 14 Mar 2017: now over 40,000 downloads.Disclaimer: All information provided is a personal opinion that may not match reality.Quote: When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist. - Archbishop Hélder Câmara
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search