March 22, 2011 at 11:46 am
Hello:
I have attempted the upgrade from SQL 2005 SP4 Standard Edition to SQL 2008 Standard Edition on a Windows server 2008 box. (Both are 32-bit.)
I got an error saying that the upgrade failed, and the error log says to first uninstall SQL 2005: SQL Server upgrade failed. To continue, investigate the reason for the failure, correct the problem, uninstall.
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?
John
March 22, 2011 at 3:09 pm
Have you looked in the setup logs yet to see why it failed?
As an FYI I recently did a SQL Server 2005 to SQL Server 2008 R2 upgrade in place and had no problems. So it is certainly possible.
Here is a link about the setup logs and where they are located: http://msdn.microsoft.com/en-us/library/ms143702(SQL.100).aspx
Here is an article that looks like it might be related: http://support.microsoft.com/kb/955399
March 22, 2011 at 3:16 pm
Have you by chance renamed or deleted the SA account?
March 22, 2011 at 3:26 pm
I did review the log files and they told me to uninstall "MSSQLSERVER". That is not an option, as uninstalling the default SQL 2005 instance would put the client's production environment at risk.
March 22, 2011 at 3:26 pm
The sa account has never been manipulated, no.
March 22, 2011 at 3:36 pm
There has to be more in the log files that state what went wrong, you have to find and correct that before doing anything else. At what point in the upgrade did it fail? If you want to post the logs I am sure some of us would look through them to help you identify the error(s) they contain.
From looking at the KB article I linked to it looks like it is saying to uninstall the partial 2008 upgrade, not the original 2005 install. (Though I can't say for sure that is what would happen as I have never had to do that.)
In any case make sure you have a full backup of the server so you can put things back if anything really goes wrong. (I assume you did that before you started the first upgrade.)
March 22, 2011 at 4:57 pm
Oh, yes, I do backups--all the time!!!!!
What's interesting is that a lot of my co-workers and people out on the various forums have had this same issue. The resolution? Install SQL 2008 on a brand new server and migrate the SQL 2005 databases to it!!!
Anyway, 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, next week.
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.
As the Air Force general in War Games said (sort of), "after careful analysis of the situation, I've come to the conclusion that this system sucks!!!"
John
March 22, 2011 at 5:19 pm
John Roy Ellis (3/22/2011)
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.
I haven't done a 2005 to 2008 upgrade but 2005 to 2008 R2 worked fine for me just a few weeks ago.
I see other people have done it, sometimes running into problems like SA having been renamed, the Program Files directory being compressed (http://troubleshooterms.blogspot.com/2009/10/error-during-sql-2005-to-sql-2008-in.html), or problems upgrading a second instance because of FullText issues, but it can be done.
And you can't upgrade from 32 bit to 64 bit...
Of course going with a new server is safer and will more than likely get you much better performance, but it costs a lot more too.
March 22, 2011 at 5:36 pm
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!
March 22, 2011 at 5:43 pm
As I read it that post is only about cleaning up the failed install so you can try again, nothing about identifying the reason the install failed in the first place so you can try to fix the problem.
March 22, 2011 at 5:51 pm
Look. My point is that others have run into the same issue that the guy at the beginning of the post ran into. As I tried saying several times, the events that that guy had are the exact same events that I and my co-workers have had.
That guy was trying to do an upgrade, ran into the same problems that I did. and no one could find a remedy. Why? There isn't one, unless you either uninstall SQL 2005 or install SQL 2008 on a new server and migrate the databases over.
Whew! This lousy technology exhausts me! If I didn't have a mortgage and two car payments to pay by myself, I'd be getting into another line of work really quick!
March 22, 2011 at 6:05 pm
John Roy Ellis (3/22/2011)
Look. My point is that others have run into the same issue that the guy at the beginning of the post ran into. As I tried saying several times, the events that that guy had are the exact same events that I and my co-workers have had.
That may be, but you haven't shared with us what the error was, or the upgrade logs so we could try to help. You have only told us what it said to do; from your first post: "To continue, investigate the reason for the failure, correct the problem, uninstall."
I haven't seen anything about the error that caused the failure in the first place. (i.e. you haven't given us anything to try to help you with.)
You would have to look at the logs from your first failed upgrade attempt, or if you no longer have those logs you would have to clear all of the failed 2008 upgrade and try the upgrade again so you could get fresh logs with the actual failure reported.
I have seen a number of people that have had issues, dug through the logs, fixed the problems, and tried again and had it work, so it is possible to recover and upgrade, at least in some cases.
March 22, 2011 at 6:13 pm
One last question, which version of SQL Server 2008 were you trying to install?
Have you slip-streamed SP1, SP2 and/or any CUs into your installation source? (I know Microsoft has fixed a lot of setup related problems since the RTM version of 2008 was released.)
March 23, 2011 at 5:20 am
SQL 2008 Standard Runtime. I don't know how to slip-stream. So, the answer is no on the service packs.
If there were a way to attach log files on this forum, I would do so. But, when I click "attachments", nothing happens.
Like I said, though, the client is buying a new server. The point is somewhat moot, though it would be nice to know for future reference how to get around this error.
Regardless of what the log says, you said that I never gave you all the error. Yeah, I did.
I don't know what the cause of that error is. That's why I came to this forum.
Again, though, I have the logs but there is no user-friendly way of attaching them here.
March 23, 2011 at 10:00 am
John Roy Ellis (3/23/2011)
SQL 2008 Standard Runtime. I don't know how to slip-stream. So, the answer is no on the service packs.
Slipstreaming can not only prevent setup/upgrade problems that MS has fixed, but it also makes your setup go faster, as once the setup is done the SP/CU is already installed. (So you only have to go through the setup process once instead of two or three times.)
Here is a link to a MS blog on how to slipstream 2008 SPs: http://blogs.msdn.com/b/petersad/archive/2009/02/25/sql-server-2008-creating-a-merged-slisptream-drop.aspx And here is a link about doing both an SP and a CU: http://blogs.msdn.com/b/petersad/archive/2009/04/16/create-a-merged-slipstream-drop-containing-sql-server-2008-server-pack-1-and-a-cumulative-update-cu-based-on-server-pack-1.aspx
If there were a way to attach log files on this forum, I would do so. But, when I click "attachments", nothing happens.
When you click the "Edit Attachments" button it should pop-up a window where you can attach files. Maybe you have a pop-up blocker that is preventing it from appearing.
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply