Sql 2005 install gone bad...

May 18, 2006 @ 5:22 pm

I just spent an hour installing SQL 2005 on my server as I would like to slowly move over some of my applications to 2005. Currently the server is running Sql 2000 and it's doing fine, but I'd like to take advantage of some of the new TSQL features.

Unfortunately I've had little luck getting a complete install to work. I installed SQL2005 as a new named instance. s it turns out SQL Server installed just fine as did all the core services, but Integration Services and Notification Services failed to install. I also couldn't get the Client Components to install on the server which really sucks.

The big problem is that I have no indication on what didn't work. There are log files but they give no indication of failure really. One step they're writing files, next step the thing is rolling back. Nice… A retry of the installation had exactly the same results.

So now I have a box with SQL 2005 installed but no local admin tools, which is kinda crucial to set up a matching set of logins to the existing server so I can back up and restore into the new database. I can connect to the server remotely, but because it's remote internet connection I can't create the right domain accounts. Whenever I try to add a Windows account I get the following error:

The program cannot open the dialog box because it cannot determine whether the computer named "IRONFIST" is joined into a domain.

I suppose this is because I'm remotely logging into the server, but frankly I'm not quite sure.

Anybody seen the odd install problems above? Or have an idea on how to deal with the account creation for Windows account?

Any help much appreciated.

Maybe it's better I put this off until after LongHorn Server ships and I can build a whole new box. This box after all is holding up fine even with all the stuff that's running on it these days - 10 years worth of accumulated Web applications <s>. One other I thing I just realized - the server only has 512 megs. Eeek. This server is old enough (5 years!) where 512 megs seemed a heck of a lot of memory. SQL 2005 seems to need a lot more memory than SQL 2000 in minimal installations anyway.

Feedback for this Weblog Entry

re: Sql 2005 install gone bad...
by Sartaga May 19, 2006 @ 5:45 am

I had a lot of trouble with installing the developer edition of SQL 2006. At first i didn't install all the various services because i didn't need them, but it turns out microsoft buries the client admin tool on one of them. The developer edition apparently doesn't have all the tools, but contains an "express" edition of SQL Server Management Studio. The path to this thing is "C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe".
I can't really remember which service i had to install to get the tool. It was either Reporting Services or it might have been the Notification and Integration services you're having trouble with. Make sure your windows firewall has the proper SQL ports open. There's a document i found on the MSDN Site "How to configure SQL Server 2005 to allow remote connections". You have to go thru a bunch of security hoops to get the thing to work, it won't go out of the box. I've had all kinds of trouble upgrading stuff from both SQL 2005 and .NET 2.0. I like the new tools, but doing this massive migration every 18-24 months for every new version of .Net is going to make me want to go back to java. None of the migration stuff works out of the box, you have to fiddle and tweak every little thing to get stuff to work. Management never understands that either, the time it takes to do that.
Personally, i don't see any real benefit to moving to SQL 2005 over 2000. I'm using NHibernate so the new features dont do anything for me. The SQL Server Management Studio is not really new, they just combined enterprise manager and the query tool into one, but the functionality is more or less the same. And i suspect it has bugs in it, i've had columns mysteriously vanish on me when transferring databases, althought that could be I just missed something, being so tired from all the upgrading and fixing.
Good Luck with your upgrade.

re: Sql 2005 install gone bad...
by Rick Strahl May 19, 2006 @ 8:08 am

I've installed SQL Developer on my local machine and it was just fine, so I don't think it's a case of missing components.

re: Sql 2005 install gone bad...
by Jeff Fleitz May 19, 2006 @ 10:37 am

I'd wait for the new server, Rick. The new tools are really slow feeling, so you will need the horsepower.

I just installed the standard edition about a month ago, and the initial installation went fine. Then I installed SP1 which had just come out and it whacked my mirrored RAID set. It freaked me out so bad, I reconfigured the server (same mirrored raid) and reinstalled it again, no problem. Applied the service pack and bam! Trashed my array again. Took about 12 hours to rebuild the array. Everything seems to be working ok now though. I am wary about updating it again though.

re: Sql 2005 install gone bad...
by Steve from Pleasant Hill May 19, 2006 @ 11:25 am

Can anyone document when MS decided to foist software on the public several QA cycles early?

re: Sql 2005 install gone bad...
by Kevin Wright May 19, 2006 @ 11:48 am

I installed the Dev Edition over the 2000 Dev Edition on my laptop. It squeaked about resources - I only had 512Mb RAM, and the Mgt Studio was horribly slow. Doubling the RAM has made it a lot better, and I had no problems later putting on SP1.

Kevin

re: Sql 2005 install gone bad...
by Guest May 24, 2006 @ 1:10 pm

Along these same lines; what is the .msi or .exe on the SQL Server 2005 CD that I can use to install the admin tools only? I'd like to install the admin tools without going through the SQL Server 2005 setup process. Thanks.

re: Sql 2005 install gone bad...
by Steve Savage May 30, 2006 @ 7:51 am

SP1 really screwed me. It upgraded all the components except for the database itself. Reporting services shut down but a blog entry by Lukawz Pawlowski detailed the simple fix to get it going again (whew).

So basically I'm stuck and after hours of surfing the net I find that others are in the same boat.

re: Sql 2005 install gone bad...
by Guest 2 August 14, 2006 @ 1:05 am

I have installed SQL server 2005 developer(server services and analysis services). i cant seem to see it on the programs menu. what did i do wrong.

re: Sql 2005 install gone bad...
by me September 16, 2006 @ 12:28 am

LOL.

re: Sql 2005 install gone bad...
by Ken Hoff February 06, 2007 @ 12:47 pm

I'm having an identical problem. I'm building a VM server with plenty of horse power. My eventual goal is to have SharePoint 2007 running on it, but I can't seem to get past installing SQL 2005. I've built several SQL 2005 servers before. It's usually a pretty easy install. For whatever reason though this install gets to the integration tools and then throws up an error that Microsoft doesn't have in the Knowledge base.

That bad install usually screws up the VM instance to where it won't restart correctly and we have to scrap it. The only difference that I can see between this build and builds I've done in the past is that this OS (2003 standard) is completely patched up and has .NET 2.0 and 3.0 on it before I started the SQL 2005 install. We've even tried several OS CDs (2003 R2, 2003 SP1) and both had the same results.

Can't figure this one out, so if anybody finds a solution, please e-mail me at: Ken.Hoff@Barry-Wehmiller.com.

re: Sql 2005 install gone bad...
by Osnola Legna March 16, 2007 @ 4:21 am

I made a full installation of SQL 2005 Server without any error messages, BUT the Client Components were not installed. It does not matter what I tried, the administration tools could not be installed.

At the end I was able to install them launching directly the following file you can find in CD2:

D:\Setup\sqlrun_tools.msi

re: Sql 2005 install gone bad...
by Rick Strahl March 16, 2007 @ 4:37 am

I had a similar experience and I think it has something to do with SQL Express having been installed before SQL Server. I was able to get the client tools installed on a second installation, but in the first pass - even though checked - the client tools did not install claiming that they were already installed...

I've seen this with several installs and it's a major hassle given that the SQL Install takes a half an hour or more.

re: Sql 2005 install gone bad...
by BOS April 18, 2007 @ 8:01 am

had the same issue that with install was unable to get clients tools:

SQL 2005 ent installed fine on win 2003 64 bit ent

but the client would not install whatever I checked,

ran the tools from D:\Setup\sqlrun_tools.msi and worked

re: Sql 2005 install gone bad...
by Ian M September 06, 2007 @ 7:34 am

Hi all,

I've tried all the above, even the last comment abourt SqlRun_tools.msi and it still doesn't work... even DOS won't get the blinking thing installed!
DOS PROMPT - H:\ENGLISH\SQL2005\DEVELOPER\SQL Server x86\Tools\Setup>start /wait setup.exe /q
b REINSTALL=Client_components REINSTALLMODE=OMUS

Gives me another (different) error.....

ERROR 2711 - An Internal Error has occurred
(client_components )

With the weird spacing......

Any ideas anyone??

re: Sql 2005 install gone bad...
by Tim February 28, 2008 @ 4:33 pm

I've tried to install SQL 2005 on my laptop and it fails with no error my laptop is an xp sp2 and has plenty of power. I had this problem once before with the same laptop and had to run a sepearate microsoft app to back out the originaml install and can't remember what the name of the app is. it is supposed to remove the registry entries i believe but i'm not sure. I've had to rebuild my laptop due to some bad memory which is why i'm installing again. anybody have any ideas i would appreciate it!!

re: Sql 2005 install gone bad...
by gary b November 13, 2008 @ 5:38 am

Don't know if you folks were able to resolve your questions, but here is 0.5 cents worth.

Tim:
M$ has a InstallerCleanUpUtility2.exe (may not be exact name) that 'cleans up' software installations. Research it and see if this applies to your situation.

As far as SQL client tools are concerned, I found that I could not get the tools installed simultaneously with SQL Server 2005 install. Once server was installed, I initiated the SQL Server 2005 install again BUT used 'Advanced' screen to select ONLY the Client Support features. Note that this procedure **is** (up to this point) the very same procedure used to install SQL Server.

If you have SQL Server installed, verify that *none* of the installed SQL components are 'Express' edition. That was one of my original problems -- resulting in a 'Edition Error' and an aborted client tools install. I ended up removing the inherited SQL Server installation and re-installing -- to create a totally 'enterprise' SQL installation. (Couldn't get SKUUPGRADE to work)

Hope this contributes to resolution for you...

gary b