November 1, 2006 at 9:21 am
Our DBA's are configuring a new server for MSSQL 2005. Their past practice, with 2000, is to load the clients, such as EM, etc. onto the server so that they can use them locally, when needed. They are having a problem with loading the 2005 clients, such Studio Manager, to the new server. Is this a common problem? Perhaps they are no longer designed to be loaded to the server? Any help would be appreciated.
November 1, 2006 at 10:13 am
The client tools certainly can be loaded on the server.
If you gave us some more information about the specific error or difficulty you are encountering, we might be able to provide better feedback/advice.
/*****************
If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek
*****************/
November 1, 2006 at 10:32 am
The error is:
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=50000&EvtType=packageengine%5cinstallpackageaction.cpp%40InstallToolsAction.10%40sqls%3a%3aInstallPackageAction%3a%3aperform%400x643
November 1, 2006 at 11:23 am
| We're sorry | |
| There is no additional information |
Thank you Microsoft... don't you just HATE those errors? LOL
You're going to have to dig further to find out what's going on... perhaps describe exactly what you were doing, what you were trying to accomplish, etc., to give (or gain) a clue.
What else is on the machine... what OS are you using? patches? other applications?
There's always a solution.
Thank-you,
David Russell
Any Cloud, Any Database, Oracle since 1982
November 1, 2006 at 11:37 pm
When you say bew server, is it a completely new server, or did it have SQL Server installed on it previously? If you are loading SQL 2005 with a different account than was used in the previous install, the SQL Server directory belongs to a different user, and SQL Server can not do everything that it needs to.
If so, uninstall all instances and completely delete the SQL Server directory and everything in it. Then it will install correctly.
November 2, 2006 at 6:59 am
Are you installing from a 2-CD set? If so, the client application is on the second CD. When I tried installing "everything" using the first CD I got an error (but can't recall what it was) so I installed the engine from the first CD then installed the client from the second CD and it worked fine. You'd think the installation would say "insert second CD now" or something. Go figure. Don't know if this is your problem though.
November 2, 2006 at 7:38 am
Robert - this is a brand new server, no previous versions exist. Linda - thanks for the tip, I'll check with the DBA's regarding whether they are using the CDs. Thanks!
November 2, 2006 at 8:08 am
is this with windows 2000? you need IE6 and I forgot what else for the client tools
November 2, 2006 at 8:19 am
The server OS is Windows 2003 Server, R2, Enterprise Edition, SP1.
November 2, 2006 at 9:18 am
If you're installing 2005 from 2 CDs, you must first copy the contents of the 1st CD to a folder called 'servers' and copy the 2nd CD to a folder called 'tools.' These 2 folders must be at the same level. Run the install from the first CD.
November 2, 2006 at 9:47 am
Ronald, thanks for the tip, I've passed it along. I was told that we start with one DVD, but that it was copied to a network drive and the install was being done remotely. They are now going to try it locally with the DVD.
November 7, 2006 at 12:35 pm
FYI - installing locally from the DVD drive on the server solved the problem. Thanks everyone for your advice.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply