SQL 2008 Upgrade Fails

I have attempted the upgrade from SQL 2005 SP4 Standard Edition on a Windows server 2008 box.  (Both are 32-bit.)

I got an error saying that the upgrade failed, and the error is detailed in the attached log file.  

I don't want to uninstall SQL 2005 on this box, as it is being used for production.  I simply wanted to do an in-place upgrade.

Next, I tried installing a fresh copy of SQL 2008 into a new instance.  I was going to simply restore the backups of the 2005 databases into the new 2008 instance, in order to do a side-by-side upgrade.

But, I got the same error--just on doing an install.

Somebody suggested that the only way to do a successful upgrade from SQL 2005 to 2008 is to do so by conducting an installation of SQL 2008 on a new box and migrating backups of the 2005 databases from the old server.  I have done this succesfully a lot of times, but I find it hard to believe that an upgrade of SQL 2008 requires a new box.  It looks like that is the case, from what I'm seeing, however,

Any ideas on how to get past this and on how to conduct this upgrade on this box?
Summary-KLASQLII-20110322-094615.txt
LVL 1
apitechAsked:
Who is Participating?
 
Aaron ShiloChief Database ArchitectCommented:
well i suggest you try to install a new instance into a new folder.
i mean that the install directory for sql server under "program files" or what ever should be diferent than the default folder.

may be this way the shared components wont fail to install
0
 
Aaron ShiloChief Database ArchitectCommented:
Can you post the logs from here ?
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\<YYYYMMDD_HHMMSS>\Detail.txt
0
 
Aaron ShiloChief Database ArchitectCommented:
this file as well :
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110322_094615\sqlncli_Cpu32_1.log
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
apitechAuthor Commented:
here they are....
Detail.txt
sqlncli-Cpu32-1.log
0
 
Aaron ShiloChief Database ArchitectCommented:
hi

ok the problem i think is that you have sql client components installed on the machine.

remove all sql server components and then restart the system and reinstall.

Good luck
0
 
apitechAuthor Commented:
Hi Ashilo:

I have Tools, such as Management Studio, installed.  Is that what you mean by "client components"?  If not, please let me know specifically what those are.  Honestly, though, I really do not want to uninstall anything.  What if the upgrade still doesn't work?  Then, I have to scramble to reinstall and, possibly, get myself into a worse position.
0
 
apitechAuthor Commented:
Well, the client tools and those components installed/upgraded fine.  It's the database engine that won't upgrade.

Anyway, I guess this is all a moot point.  I did not have much time today to get this situation fixed.  So, the client is ordering a new server.  I'm just going to do a new install of SQL 2008 on it and migrate the SQL 2005 databases over.

Apparently, you can't do an in-place upgrade, a side-by-side upgrade, or even a new install of SQL 2008 on a box that already has SQL 2005 on it.  Uninstalling SQL 2005 likely would be the remedy, but that is not a good idea in a production environment.

Thanks, just the same, for looking into this.  I appreciate it!
0
 
apitechAuthor Commented:
Also, if anyone is curious, below is a link to a few people that ran into the same issue that I did and did not find a resolution.  The topic that is discussed in the beginning is the exact same issue that I ran into!

This is crazy!

http://social.msdn.microsoft.com/Forums/en/sqlsetupandupgrade/thread/814a42d0-aed4-41f5-b3c7-01eb84ce4e20

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.