search
Japanese Chinese Nederlands Espanol Italiano Deutsch Francais Twitter Rss Feeds
SQL Server GroupsView
SQL Server Ce
SQL Server Clients
SQL Server Clustering
SQL Server Connect
SQL Server Dts
SQL Server Fulltext
SQL Server Integrationsvcs
SQL Server Msde
SQL Server Newusers
SQL Server Olap
SQL Server Programming
SQL Server Replication
SQL Server Reportingsvcs
SQL Server Security
SQL Server Server
SQL Server Setup
SQL Server Tools
SQL Server Xml

Group SummariesView
.NET Framework
Access
BizTalk
Certifications
CRM
DDK
Exchange Server
FoxPro
French
French .NET
Games
German
German .NET
Graphic Design
IIS
Internet
ISA Server
Italian
Italian .NET
Maps
MCIS
Miscellaneous
Mobile Application Development
Money
MSN
Networking
Office
Ops Mgr
Publisher
Security
SharePoint
Small Business
Spanish
Spanish .NET
SQL Server
Systems Management Server
Transaction Server
Virtual PC / Virtual Server
Visual Studio
Win32
Windows 2000
Windows 2003 Server
Windows 7
Windows Live
Windows Media
Windows Update
Windows Vista
Windows XP
 

View All Microsoft SQL Server Setup Posts  Ask A New Question 

error 1603 installing sql 2005 on windows server 2003 - Eddi

Friday, September 05, 2008 5:08 PM

Hi, I'm trying to install a new instance of sql server 2005 on a Windows 2003
server. This server is running sql 2000, but I want to install sql 2005
instance on a different drive for parallel testing purposes.

How can I accomplish?

Thanks,
Eddie
reply
 

Even you can change some of the components' installation paths, you can't do - ekre

Saturday, September 06, 2008 7:36 AM

Even you can change some of the components' installation paths, you can't do
this changing for the others. You will want to see this page in BOL:
http://msdn.microsoft.com/en-us/library/ms143547.aspx

--
Ekrem Önsoy
reply

I can't even get past installing the support files. - Eddi

Monday, September 08, 2008 10:47 AM

I cannot even get past installing the support files.  How can I change the
installation path?
reply

It obviously seems that I didn't understand your question. - ekre

Tuesday, September 09, 2008 6:16 AM

It obviously seems that I didn't understand your question.

Let's make things clear. You have a SQL Server 2000 instance that runs on a
Windows Server 2003 and you want to install another SQL Server 2005 on the
same Windows Server 2003 but its location will be different than your SQL
Server 2000 instance? Is this what you are trying to do?

--
Ekrem Önsoy
reply

Yes, I want to run both sql2000 and sql2005 on the same server. - Eddi

Tuesday, September 09, 2008 9:25 AM

Yes, I want to run both sql2000 and sql2005 on the same server.

Thanks,
reply

OK, so tell us what's wrong with that? - ekre

Tuesday, September 09, 2008 9:57 AM

OK, so tell us what's wrong with that? You are talking about an "error 1603"
on the topic. When does it occur?

Normally, you can install different versions of SQL Server instances side by
side.

Also, can you tell us your following comment in a different way? (The
following quote is taken from your first post.)


What exactly do you mean by saying "on a different drive"? For example,
let's say you have 3 different drive roots C:\ D:\ E:\ (CD\DVD ROM is not
included) and your SQL Server 2000 is installed on your C:\ drive and you
want to install your SQL Server 2005 instance on drive D:\ or E:\ ? If this
is the situation, then you'll have to revise my first reply which was about
the fixed and configurable installation paths of SQL Server 2005.

--
Ekrem Önsoy
reply

error 1603 installing sql 2005 on windows server 2003 - Eddi

Tuesday, September 09, 2008 10:23 AM

Okay, this server has 3 volumes C: D: E:  Currently sql2000 is loaded on E:
and I wanted to install sql2005 on D:.  But at this point it dosen't matter I
just want to be able to install sql2005 as a different instance.  I get this
error during the install of the setup support files.  this is one of the
errors I get in my app log = Product: Microsoft SQL Server Setup Support
Files (English) -- Error 2908. The installer has encountered an unexpected
error. The error code is 2908. Could not register component
{1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.

Help!
reply

Eddie, you did not mention, however if you google for this problem then you - ekre

Tuesday, September 09, 2008 4:10 PM

Eddie, you did not mention, however if you google for this problem then you
encounter this problem with different products too. So it seems that this is
a Windows Installer issue rather than a SQL Server problem.

I'd like to share with you one link that I found, it may give you an idea
that goes to the solution:
http://icumove.spaces.live.com/blog/cns!FB93073C6534B681!318.entry

It would be great if you come up with a solution and share your experience
about this error with us.

--
Ekrem Önsoy
reply

Previous Microsoft SQL Server Setup conversation.