SQL 2008 SP3 Fails

I've tried several times (at least 6) to install the SQL 2008 SP3 but it fails every time.  I've attached a screen print of the error and the summary log file from the latest attempt.  
We're currently at SQL version 10.00.1600.22, it's SQL 2008 not SQL 2008 R2.
All the SQL services were stopped when we attempted this update.
If anyone has a work around, please let me know.
Who is Participating?
Ryan McCauleyConnect With a Mentor Data and Analytics ManagerCommented:
Okay - there's a pretty solid error in that log file, near the bottom:

2012-09-13 12:18:14 Slp: Error: Action "ValidateFeatureSettings" threw an exception during execution.
2012-09-13 12:18:14 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Element not found. (Exception from HRESULT: 0x80070490) ---> System.Runtime.InteropServices.COMException (0x80070490): Element not found. (Exception from HRESULT: 0x80070490)

Any chance this applies to you?


There's also another post where somebody refers to that Connect bug (and the work-around), but also mentions having to modify node ownership:


I'm hopeful!
Ryan McCauleyData and Analytics ManagerCommented:
The log file and error you've attached really don't have much detail, and I don't see anything that sheds like on the specifics of your failure reason. Is this the first indication that your installation isn't going to upgrade, or do you get some warnings earlier in the process.

Also, it looks like you're trying to upgrade the database engine and the shared features at the same time and they both fail. Though this is usually fine and I've always done everything at once, do you get the same failure if you only attempt one of them instead? I once saw a case, though on SQL 2005, where we could service pack one instance at a time, but not more than one (the shared features are selected separately, listed alongside the instances as though they're another one).
skbarnardAuthor Commented:
The shared features checkbox is grayed out so I'm unable to deselect it however, I'm attempting a run right now having deselected the MSSQLSERVER instance.
If the shared features upgrade, I will then attempt the instance upgrade.
I'll keep you posted.
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

skbarnardAuthor Commented:
I started the process then I went out to lunch.  The shared resources portion of the update failed too.
I'm attaching the detail log that may help shed more light on what fails (at least for anyone that sees this thread, it's not all that helpful to me; I don't have much programming background)
skbarnardConnect With a Mentor Author Commented:
Sorry I've been remiss at not checking back here until now, we've had a lot of little gremlins running around so fires have had to be put out and took priority.
Our SQL setup is clustered and we have a SAN that has volumes that are presented to the servers.
Based on the links provided by ryanmccauley, I removed those volumes from the server ("unshared" them from the SAN), stopped all the SQL services and tried to install again (as administrator) - still no joy.
I guess my next step would be to remove the node ownership - anyone know how I can do that?
skbarnardAuthor Commented:
Sorry I've been so slow to respond to this question.  If you've looked through this thread you've seen that we're set up in a clustered environment.  It turns out that in addition to stopping all SQL services, we also had to stop the cluster service.  We'd neglected doing that and that interfered with the installation.
All Courses

From novice to tech pro — start learning today.