October 14, 2014 at 7:56 pm
Today I attempted to install SQL Server 2014 RTM as an upgrade to an existing instance of SQL Server 2008 R2. This existing instance doesn't contain any data that we want to preserve. It was installed by someone about a year ago who didn't know much about SQL Server but who had pretty good Windows Server experience. I also see remnants of a SQL Server 2008 install. When I tried to upgrade I ran into problem after problem with very vague error information in the logs. Another possible variable is I may not have all the local administrator rights as the domain admin might have turned off a few for security purposes.
Tomorrow I will post exact error messages as I try yet again but I hoped to get a few opinions on whether it might be best for me to try to remove every trace of old Sql Server versions first and then try to do a brand new install. I realize this would probably mean hacking the registry (AFTER BACKING IT UP FIRST, OF COURSE). But, before I do that, can some of you weigh in on whether that is a good course of action?
Before I even attempted an upgrade this morning I ran the upgrade advisor and other checks and everything came out with a clean bill of health. I do have .net 3.5 (a prereq) installed as well as 4.0 and 4.5. By †he end of the day I had stripped the features to install down to database engine, report services, and advanced tools. The only thing that id running is the reporting services service.
I've never had problems installing SQL Server before. I will post specifics from logs tomorrow, as I mentioned, but should I start by uninstalling every trace of Sql server and installing 2014 RTM from scratch?
Thanks.
October 15, 2014 at 7:23 am
I would wipe the machine completely.
-- Gianluca Sartori
October 15, 2014 at 8:54 am
Not an option to wipe the server. Only the Network admin can do that and she has the personality of a ferret on double espresso. Does anyone else have an opinion or experience with installing SQL Server 2014 either as an upgrade to SQL Server 2008 R2 or in removing all vestiges of old versions of SQL Server before doing a fresh install of 2014? Thanks.
October 15, 2014 at 9:28 am
pharmkittie (10/15/2014)
...she has the personality of a ferret on double espresso...
😀
Really, trust me... wipe the machine, you'll thank me later.
-- Gianluca Sartori
October 15, 2014 at 9:56 am
Thanks but I meant I am not allowed to and she won't. Period. So I have to find another way. I am in the process of removing old versions now. Wish me luck and/or chime in with any tips. If I get any specific errors in the logs that aren't the kind that can means dozens of things, I'll post again.
October 15, 2014 at 11:31 am
Hooray! I have SQL 2014 installed. I looked in the Windows Registry for any keys that referred to old versions of SQL Server here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and deleted them. I also moved any data files to a new directory with a different name. Before this I had used the Remove Programs option of Control panel to delete any old SQL Server references. I didn't think this would be enough but I got lucky. The only reason I could be pretty reckless in deleting things is: 12) I backed up the Windows Registry before I started hacking it and 2) the server doesn't have anything that is being used right now.
Still, I had to get this working without any help from the "Network Admin" so I'm really relieved it worked.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply