Can't start the MSSQLServer Service

I just got a new laptop for work, and our local IT/Hardware guy used
PCMover from Laplink to migrate the apps and settings from my old
machine to this new one. I was skeptical, but it's actually worked
quite well, the biggest issue that I'm having is getting SQL Server to
run on the new machine.
Using SQL Server 2000. Both laptops are Windows XP Pro SP2.
After the migration, I did have to recreate the services for the
server and agent (those services weren't migrated):
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
service MSSQLServer -exepath "c:\Program Files\Microsoft SQL Server
\MSSQL\Binn\sqlservr.exe"
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
service SQLSERVERAGENT -exepath "c:\Program Files\Microsoft SQL Server
\MSSQL\Binn\sqlagent.exe" -dependencies MSSQLServer
If I don't include the SQL Server dependency on the SQL Agent, then
the Agent starts just fine. When I try to start the SQL Server
service, it displays a dialog error:
The MSSQLServer service on Local Computer started and then stopped.
Some Services stop automatically if they have no work to do, for
example, the Performance Logs and Alerts service.
Here's the contents of the server log:
2007-02-08 10:38:58.14 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2007-02-08 10:38:58.14 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-02-08 10:38:58.14 server All rights reserved.
2007-02-08 10:38:58.14 server Server Process ID is 5860.
2007-02-08 10:38:58.14 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-08 10:38:58.17 server SQL Server is starting at priority
class 'normal'(2 CPUs detected).
2007-02-08 10:38:58.84 server SQL Server configured for thread mode
processing.
2007-02-08 10:38:58.84 server Using dynamic lock allocation. [2500]
Lock Blocks, [5000] Lock Owner Blocks.
2007-02-08 10:38:58.87 server Attempting to initialize Distributed
Transaction Coordinator.
2007-02-08 10:38:58.89 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
2007-02-08 10:38:58.89 server Unable to load any NETLIBs. Server
shutting down.
2007-02-08 10:38:58.89 spid4 Starting up database 'master'.
The failure to obtain TransactionDispenserInterface message was
occurring on the old machine, so I conclude that isn't part of the
issue.
The Server Network Utility does show TCP/IP as the only protocol
enabled. The Network Libraries tab does show the TCP/IP SSNETLIB.DLL
listed and that dll is residing in the expected location (C:\Program
Files\Microsoft SQL Server\MSSQL\Binn).
The service properties page page Log On tab shows the Local System
Account to be used for logon.
So, I'm figuring it can't find ssnetlib.dll. Short of uninstalling
and re-installing SQL Server, how can I get my SQL Server back up and
running?
Thanks in advance
Mark>I just got a new laptop for work, and our local IT/Hardware guy used
> PCMover from Laplink to migrate the apps and settings from my old
> machine to this new one. I was skeptical,
And you should have been. The errorlog clearly states that SQL Server cannot load any netlibs, so it
refuses to start. I.e., the installation isn't OK...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<mark.a.lemoine@.gmail.com> wrote in message
news:1170950095.972400.293760@.s48g2000cws.googlegroups.com...
>I just got a new laptop for work, and our local IT/Hardware guy used
> PCMover from Laplink to migrate the apps and settings from my old
> machine to this new one. I was skeptical, but it's actually worked
> quite well, the biggest issue that I'm having is getting SQL Server to
> run on the new machine.
> Using SQL Server 2000. Both laptops are Windows XP Pro SP2.
> After the migration, I did have to recreate the services for the
> server and agent (those services weren't migrated):
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
> service MSSQLServer -exepath "c:\Program Files\Microsoft SQL Server
> \MSSQL\Binn\sqlservr.exe"
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
> service SQLSERVERAGENT -exepath "c:\Program Files\Microsoft SQL Server
> \MSSQL\Binn\sqlagent.exe" -dependencies MSSQLServer
> If I don't include the SQL Server dependency on the SQL Agent, then
> the Agent starts just fine. When I try to start the SQL Server
> service, it displays a dialog error:
> The MSSQLServer service on Local Computer started and then stopped.
> Some Services stop automatically if they have no work to do, for
> example, the Performance Logs and Alerts service.
> Here's the contents of the server log:
> 2007-02-08 10:38:58.14 server Microsoft SQL Server 2000 - 8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
> 2007-02-08 10:38:58.14 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2007-02-08 10:38:58.14 server All rights reserved.
> 2007-02-08 10:38:58.14 server Server Process ID is 5860.
> 2007-02-08 10:38:58.14 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2007-02-08 10:38:58.17 server SQL Server is starting at priority
> class 'normal'(2 CPUs detected).
> 2007-02-08 10:38:58.84 server SQL Server configured for thread mode
> processing.
> 2007-02-08 10:38:58.84 server Using dynamic lock allocation. [2500]
> Lock Blocks, [5000] Lock Owner Blocks.
> 2007-02-08 10:38:58.87 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2007-02-08 10:38:58.89 server Failed to obtain
> TransactionDispenserInterface: Result Code = 0x8004d01b
> 2007-02-08 10:38:58.89 server Unable to load any NETLIBs. Server
> shutting down.
> 2007-02-08 10:38:58.89 spid4 Starting up database 'master'.
> The failure to obtain TransactionDispenserInterface message was
> occurring on the old machine, so I conclude that isn't part of the
> issue.
> The Server Network Utility does show TCP/IP as the only protocol
> enabled. The Network Libraries tab does show the TCP/IP SSNETLIB.DLL
> listed and that dll is residing in the expected location (C:\Program
> Files\Microsoft SQL Server\MSSQL\Binn).
> The service properties page page Log On tab shows the Local System
> Account to be used for logon.
> So, I'm figuring it can't find ssnetlib.dll. Short of uninstalling
> and re-installing SQL Server, how can I get my SQL Server back up and
> running?
> Thanks in advance
> Mark
>sql

Can't start the MSSQLServer Service

I just got a new laptop for work, and our local IT/Hardware guy used
PCMover from Laplink to migrate the apps and settings from my old
machine to this new one. I was skeptical, but it's actually worked
quite well, the biggest issue that I'm having is getting SQL Server to
run on the new machine.
Using SQL Server 2000. Both laptops are Windows XP Pro SP2.
After the migration, I did have to recreate the services for the
server and agent (those services weren't migrated):
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
service MSSQLServer -exepath "c:\Program Files\Microsoft SQL Server
\MSSQL\Binn\sqlservr.exe"
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
service SQLSERVERAGENT -exepath "c:\Program Files\Microsoft SQL Server
\MSSQL\Binn\sqlagent.exe" -dependencies MSSQLServer
If I don't include the SQL Server dependency on the SQL Agent, then
the Agent starts just fine. When I try to start the SQL Server
service, it displays a dialog error:
The MSSQLServer service on Local Computer started and then stopped.
Some Services stop automatically if they have no work to do, for
example, the Performance Logs and Alerts service.
Here's the contents of the server log:
2007-02-08 10:38:58.14 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2007-02-08 10:38:58.14 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-02-08 10:38:58.14 server All rights reserved.
2007-02-08 10:38:58.14 server Server Process ID is 5860.
2007-02-08 10:38:58.14 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-08 10:38:58.17 server SQL Server is starting at priority
class 'normal'(2 CPUs detected).
2007-02-08 10:38:58.84 server SQL Server configured for thread mode
processing.
2007-02-08 10:38:58.84 server Using dynamic lock allocation. [2500]
Lock Blocks, [5000] Lock Owner Blocks.
2007-02-08 10:38:58.87 server Attempting to initialize Distributed
Transaction Coordinator.
2007-02-08 10:38:58.89 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
2007-02-08 10:38:58.89 server Unable to load any NETLIBs. Server
shutting down.
2007-02-08 10:38:58.89 spid4 Starting up database 'master'.
The failure to obtain TransactionDispenserInterface message was
occurring on the old machine, so I conclude that isn't part of the
issue.
The Server Network Utility does show TCP/IP as the only protocol
enabled. The Network Libraries tab does show the TCP/IP SSNETLIB.DLL
listed and that dll is residing in the expected location (C:\Program
Files\Microsoft SQL Server\MSSQL\Binn).
The service properties page page Log On tab shows the Local System
Account to be used for logon.
So, I'm figuring it can't find ssnetlib.dll. Short of uninstalling
and re-installing SQL Server, how can I get my SQL Server back up and
running?
Thanks in advance
Mark>I just got a new laptop for work, and our local IT/Hardware guy used
> PCMover from Laplink to migrate the apps and settings from my old
> machine to this new one. I was skeptical,
And you should have been. The errorlog clearly states that SQL Server cannot
load any netlibs, so it
refuses to start. I.e., the installation isn't OK...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<mark.a.lemoine@.gmail.com> wrote in message
news:1170950095.972400.293760@.s48g2000cws.googlegroups.com...
>I just got a new laptop for work, and our local IT/Hardware guy used
> PCMover from Laplink to migrate the apps and settings from my old
> machine to this new one. I was skeptical, but it's actually worked
> quite well, the biggest issue that I'm having is getting SQL Server to
> run on the new machine.
> Using SQL Server 2000. Both laptops are Windows XP Pro SP2.
> After the migration, I did have to recreate the services for the
> server and agent (those services weren't migrated):
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
> service MSSQLServer -exepath "c:\Program Files\Microsoft SQL Server
> \MSSQL\Binn\sqlservr.exe"
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
> service SQLSERVERAGENT -exepath "c:\Program Files\Microsoft SQL Server
> \MSSQL\Binn\sqlagent.exe" -dependencies MSSQLServer
> If I don't include the SQL Server dependency on the SQL Agent, then
> the Agent starts just fine. When I try to start the SQL Server
> service, it displays a dialog error:
> The MSSQLServer service on Local Computer started and then stopped.
> Some Services stop automatically if they have no work to do, for
> example, the Performance Logs and Alerts service.
> Here's the contents of the server log:
> 2007-02-08 10:38:58.14 server Microsoft SQL Server 2000 - 8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
> 2007-02-08 10:38:58.14 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2007-02-08 10:38:58.14 server All rights reserved.
> 2007-02-08 10:38:58.14 server Server Process ID is 5860.
> 2007-02-08 10:38:58.14 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2007-02-08 10:38:58.17 server SQL Server is starting at priority
> class 'normal'(2 CPUs detected).
> 2007-02-08 10:38:58.84 server SQL Server configured for thread mode
> processing.
> 2007-02-08 10:38:58.84 server Using dynamic lock allocation. [2500]
> Lock Blocks, [5000] Lock Owner Blocks.
> 2007-02-08 10:38:58.87 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2007-02-08 10:38:58.89 server Failed to obtain
> TransactionDispenserInterface: Result Code = 0x8004d01b
> 2007-02-08 10:38:58.89 server Unable to load any NETLIBs. Server
> shutting down.
> 2007-02-08 10:38:58.89 spid4 Starting up database 'master'.
> The failure to obtain TransactionDispenserInterface message was
> occurring on the old machine, so I conclude that isn't part of the
> issue.
> The Server Network Utility does show TCP/IP as the only protocol
> enabled. The Network Libraries tab does show the TCP/IP SSNETLIB.DLL
> listed and that dll is residing in the expected location (C:\Program
> Files\Microsoft SQL Server\MSSQL\Binn).
> The service properties page page Log On tab shows the Local System
> Account to be used for logon.
> So, I'm figuring it can't find ssnetlib.dll. Short of uninstalling
> and re-installing SQL Server, how can I get my SQL Server back up and
> running?
> Thanks in advance
> Mark
>

Can't login into SQL Server Database

Hey
I get the following error when trying to connect to my named instance Sql
Server running locally on my laptop. Does anyone know how to resolve this
I get the following error : Login failed for user:acw
Here is my code:
SqlConnection sConn = new SqlConnection(server=ACLAPTOP\ACSQLSERVE
R;User
id=acw; Password=;Database=BookSpot);
Thanks,
AlAl
Open QA and try to log in with the user. Do you get the same error?
"Al Wilkerson" <ac527@.comcast.net> wrote in message
news:7aCdnUdO-Ipm37zfRVn-gA@.comcast.com...
> Hey
> I get the following error when trying to connect to my named instance Sql
> Server running locally on my laptop. Does anyone know how to resolve this
> I get the following error : Login failed for user:acw
> Here is my code:
> SqlConnection sConn = new SqlConnection(server=ACLAPTOP\ACSQLSERVE
R;User
> id=acw; Password=;Database=BookSpot);
>
> Thanks,
> --
> Al
>|||I assume this is C# code. Did you give this user a blank password?
Double-check the password for this user and the rights/roles granted to this
user in EM. I assume your connection string is properly quoted (or it
wouldn't even compile for you). Finally, are you using Integrated Security
or SQL Server Authentication?
Thx
Mike C.
"Al Wilkerson" <ac527@.comcast.net> wrote in message
news:7aCdnUdO-Ipm37zfRVn-gA@.comcast.com...
> Hey
> I get the following error when trying to connect to my named instance Sql
> Server running locally on my laptop. Does anyone know how to resolve this
> I get the following error : Login failed for user:acw
> Here is my code:
> SqlConnection sConn = new SqlConnection(server=ACLAPTOP\ACSQLSERVE
R;User
> id=acw; Password=;Database=BookSpot);
>
> Thanks,
> --
> Al
>

can't install SQL Server on a partition other than c:\

Hello --
My laptop drive is partitioned into c: and e:. I want to install on
e:.
During Install, in Feature Selection, when I click the icon for Client
Components, the Browse button to allow an install path other than c:
\... is disabled, indicating that the shared path has already been
configured).
Can someone tell me
1 - what I installed prior that does not allow me to install the
complete SQL Server on e:?
2 - what must I uninstall and then reinstall, and, in what sequence,
to be able to install on e:?
Thanks in advance for any help.
Larry MehlYou can't install the whole SQL Server related files into your "e:" drive.
Some files are installed to the default path "C:\Program Files\Microsoft SQL
Server...". Generally, you can say "Common components like SSIS, Client
Components etc. will be installed to this default path"
--
Ekrem Önsoy
"mehlREMOVETHIS@.cyvest.com" <mehl@.cyvest.com> wrote in message
news:5581b71e-f6de-4d58-833e-e931a8d5c3b3@.t12g2000prg.googlegroups.com...
> Hello --
> My laptop drive is partitioned into c: and e:. I want to install on
> e:.
> During Install, in Feature Selection, when I click the icon for Client
> Components, the Browse button to allow an install path other than c:
> \... is disabled, indicating that the shared path has already been
> configured).
> Can someone tell me
> 1 - what I installed prior that does not allow me to install the
> complete SQL Server on e:?
> 2 - what must I uninstall and then reinstall, and, in what sequence,
> to be able to install on e:?
> Thanks in advance for any help.
> Larry Mehl
>
>|||Unfortunately, that's one of the fundamentally flawed design choices that SQL
Server seems to be stuck with. It's fundamentally flawed because this forces
the system to store states on the local machine. Not being able to choose an
arbitrary drive is just a minor inconvenience in comparison.
Linchi
"mehlREMOVETHIS@.cyvest.com" wrote:
> Hello --
> My laptop drive is partitioned into c: and e:. I want to install on
> e:.
> During Install, in Feature Selection, when I click the icon for Client
> Components, the Browse button to allow an install path other than c:
> \... is disabled, indicating that the shared path has already been
> configured).
> Can someone tell me
> 1 - what I installed prior that does not allow me to install the
> complete SQL Server on e:?
> 2 - what must I uninstall and then reinstall, and, in what sequence,
> to be able to install on e:?
> Thanks in advance for any help.
> Larry Mehl
>
>|||On May 4, 2:09 am, Ekrem =D6nsoy <ek...@.compecta.com> wrote:
> You can't install the whole SQL Server related files into your "e:" drive.=
> Some files are installed to the default path "C:\Program Files\Microsoft S=QL
> Server...". Generally, you can say "Common components like SSIS, Client
> Components etc. will be installed to this default path"
> --
> Ekrem =D6nsoy
> "mehlREMOVET...@.cyvest.com" <m...@.cyvest.com> wrote in message
> news:5581b71e-f6de-4d58-833e-e931a8d5c3b3@.t12g2000prg.googlegroups.com...
> > Hello --
> > My laptop drive is partitioned into c: and e:. I want to install on
> > e:.
> > During Install, in Feature Selection, when I click the icon for Client
> > Components, the Browse button to allow an install path other than c:
> > \... is disabled, indicating that the shared path has already been
> > configured).
> > Can someone tell me
> > 1 - what I installed prior that does not allow me to install the
> > complete SQL Server on e:?
> > 2 - what must I uninstall and then reinstall, and, in what sequence,
> > to be able to install on e:?
> > Thanks in advance for any help.
> > Larry Mehl
Ekrem --
Thank you.
How do I install "Common components like SSIS, Client Components
etc. ... to the default path" so that I can then install the remaining
part of SQL Server to my "e:" drive?
Do I execute the install process twice ... so that
- I first install the common components (in c:) and
- then install I install the remaining components in e: ?
Is it only the common components that cause this, or was it the
installation of other applications such as .NET, Document Explorer,
2005 Samples, Native Client, Setup Support Files, VSS Writer that
installed into c: and are consequently causing this limitation?
If I must, I will enlarge the c: partition to allow installation of
everything into c: What partition manager do you recommend for this?
I will appreciate any further information.
Larry Mehl|||You can install services and components to different paths at once.
In SQL Server Setup, click Advanced button in Components to Install window.
Click on the item and then click the Browse button to install it to a
different path in the Feature Selection window.
For example you can install Database Engine, Analysis Services, Reporting
Services to a different path, but you can't change the path of Documentation
and Samples or Client Components...
--
Ekrem Önsoy
"mehlREMOVETHIS@.cyvest.com" <mehl@.cyvest.com> wrote in message
news:24957b8a-c6ce-426e-9221-04e844f32777@.t12g2000prg.googlegroups.com...
On May 4, 2:09 am, Ekrem Önsoy <ek...@.compecta.com> wrote:
> You can't install the whole SQL Server related files into your "e:" drive.
> Some files are installed to the default path "C:\Program Files\Microsoft
> SQL
> Server...". Generally, you can say "Common components like SSIS, Client
> Components etc. will be installed to this default path"
> --
> Ekrem Önsoy
> "mehlREMOVET...@.cyvest.com" <m...@.cyvest.com> wrote in message
> news:5581b71e-f6de-4d58-833e-e931a8d5c3b3@.t12g2000prg.googlegroups.com...
> > Hello --
> > My laptop drive is partitioned into c: and e:. I want to install on
> > e:.
> > During Install, in Feature Selection, when I click the icon for Client
> > Components, the Browse button to allow an install path other than c:
> > \... is disabled, indicating that the shared path has already been
> > configured).
> > Can someone tell me
> > 1 - what I installed prior that does not allow me to install the
> > complete SQL Server on e:?
> > 2 - what must I uninstall and then reinstall, and, in what sequence,
> > to be able to install on e:?
> > Thanks in advance for any help.
> > Larry Mehl
Ekrem --
Thank you.
How do I install "Common components like SSIS, Client Components
etc. ... to the default path" so that I can then install the remaining
part of SQL Server to my "e:" drive?
Do I execute the install process twice ... so that
- I first install the common components (in c:) and
- then install I install the remaining components in e: ?
Is it only the common components that cause this, or was it the
installation of other applications such as .NET, Document Explorer,
2005 Samples, Native Client, Setup Support Files, VSS Writer that
installed into c: and are consequently causing this limitation?
If I must, I will enlarge the c: partition to allow installation of
everything into c: What partition manager do you recommend for this?
I will appreciate any further information.
Larry Mehl|||On May 4, 12:04 pm, Ekrem =D6nsoy <ek...@.compecta.com> wrote:
> You can install services and components to different paths at once.
> In SQL Server Setup, click Advanced button in Components to Install window=.
> Click on the item and then click the Browse button to install it to a
> different path in the Feature Selection window.
> For example you can install Database Engine, Analysis Services, Reporting
> Services to a different path, but you can't change the path of Documentati=on
> and Samples or Client Components...
> --
> Ekrem =D6nsoy
> "mehlREMOVET...@.cyvest.com" <m...@.cyvest.com> wrote in message
> news:24957b8a-c6ce-426e-9221-04e844f32777@.t12g2000prg.googlegroups.com...
> On May 4, 2:09 am, Ekrem =D6nsoy <ek...@.compecta.com> wrote:
>
> > You can't install the whole SQL Server related files into your "e:" driv=e.
> > Some files are installed to the default path "C:\Program Files\Microsoft=
> > SQL
> > Server...". Generally, you can say "Common components like SSIS, Client
> > Components etc. will be installed to this default path"
> > --
> > Ekrem =D6nsoy
> > "mehlREMOVET...@.cyvest.com" <m...@.cyvest.com> wrote in message
> >news:5581b71e-f6de-4d58-833e-e931a8d5c3b3@.t12g2000prg.googlegroups.com...=
> > > Hello --
> > > My laptop drive is partitioned into c: and e:. I want to install on
> > > e:.
> > > During Install, in Feature Selection, when I click the icon for Client=
> > > Components, the Browse button to allow an install path other than c:
> > > \... is disabled, indicating that the shared path has already been
> > > configured).
> > > Can someone tell me
> > > 1 - what I installed prior that does not allow me to install the
> > > complete SQL Server on e:?
> > > 2 - what must I uninstall and then reinstall, and, in what sequence,
> > > to be able to install on e:?
> > > Thanks in advance for any help.
> > > Larry Mehl
> Ekrem --
> Thank you.
> How do I install "Common components like SSIS, Client Components
> etc. ... to the default path" so that I can then install the remaining
> part of SQL Server to my "e:" drive?
> Do I execute the install process twice ... so that
> - I first install the common components (in c:) and
> - then install I install the remaining components in e: ?
> Is it only the common components that cause this, or was it the
> installation of other applications such as .NET, Document Explorer,
> 2005 Samples, Native Client, Setup Support Files, VSS Writer that
> installed into c: and are consequently causing this limitation?
> If I must, I will enlarge the c: partition to allow installation of
> everything into c: What partition manager do you recommend for this?
> I will appreciate any further information.
> Larry Mehl
Ekrem --
Thank you for the method.
Linchi -- Thanks for responding. His response seems to conflict with
yours. What do you think?
Larry|||And just to elaborate, some of the components/items are customizable, some
are not.
Also I don't see how Linchi's reply conflicts with anything else that has
been stated in this thread.
On 5/4/08 3:04 PM, in article
6C568227-DB0D-428C-AF70-BD0AC2BE835E@.microsoft.com, "Ekrem Önsoy"
<ekrem@.compecta.com> wrote:
> You can install services and components to different paths at once.
> In SQL Server Setup, click Advanced button in Components to Install window.
> Click on the item and then click the Browse button to install it to a
> different path in the Feature Selection window.
> For example you can install Database Engine, Analysis Services, Reporting
> Services to a different path, but you can't change the path of Documentation
> and Samples or Client Components...|||To be clearer, what is the confliction do you think?
--
Ekrem Önsoy
"mehlREMOVETHIS@.cyvest.com" <mehl@.cyvest.com> wrote in message
news:ef59ea4d-a2e7-4cb1-af9a-8475dc81f80f@.j9g2000prn.googlegroups.com...
On May 4, 12:04 pm, Ekrem Önsoy <ek...@.compecta.com> wrote:
> You can install services and components to different paths at once.
> In SQL Server Setup, click Advanced button in Components to Install
> window.
> Click on the item and then click the Browse button to install it to a
> different path in the Feature Selection window.
> For example you can install Database Engine, Analysis Services, Reporting
> Services to a different path, but you can't change the path of
> Documentation
> and Samples or Client Components...
> --
> Ekrem Önsoy
> "mehlREMOVET...@.cyvest.com" <m...@.cyvest.com> wrote in message
> news:24957b8a-c6ce-426e-9221-04e844f32777@.t12g2000prg.googlegroups.com...
> On May 4, 2:09 am, Ekrem Önsoy <ek...@.compecta.com> wrote:
>
> > You can't install the whole SQL Server related files into your "e:"
> > drive.
> > Some files are installed to the default path "C:\Program Files\Microsoft
> > SQL
> > Server...". Generally, you can say "Common components like SSIS, Client
> > Components etc. will be installed to this default path"
> > --
> > Ekrem Önsoy
> > "mehlREMOVET...@.cyvest.com" <m...@.cyvest.com> wrote in message
> >news:5581b71e-f6de-4d58-833e-e931a8d5c3b3@.t12g2000prg.googlegroups.com...
> > > Hello --
> > > My laptop drive is partitioned into c: and e:. I want to install on
> > > e:.
> > > During Install, in Feature Selection, when I click the icon for Client
> > > Components, the Browse button to allow an install path other than c:
> > > \... is disabled, indicating that the shared path has already been
> > > configured).
> > > Can someone tell me
> > > 1 - what I installed prior that does not allow me to install the
> > > complete SQL Server on e:?
> > > 2 - what must I uninstall and then reinstall, and, in what sequence,
> > > to be able to install on e:?
> > > Thanks in advance for any help.
> > > Larry Mehl
> Ekrem --
> Thank you.
> How do I install "Common components like SSIS, Client Components
> etc. ... to the default path" so that I can then install the remaining
> part of SQL Server to my "e:" drive?
> Do I execute the install process twice ... so that
> - I first install the common components (in c:) and
> - then install I install the remaining components in e: ?
> Is it only the common components that cause this, or was it the
> installation of other applications such as .NET, Document Explorer,
> 2005 Samples, Native Client, Setup Support Files, VSS Writer that
> installed into c: and are consequently causing this limitation?
> If I must, I will enlarge the c: partition to allow installation of
> everything into c: What partition manager do you recommend for this?
> I will appreciate any further information.
> Larry Mehl
Ekrem --
Thank you for the method.
Linchi -- Thanks for responding. His response seems to conflict with
yours. What do you think?
Larry

Can't install SQL 2005 server components

I've been trying to install SQL 2005 on my development laptop. So far
I've been able to install all client components, but the setup program
never gives me the option to install the server components. I first
tried with the Enterprise edition. I then found out that Enterprise
doesn't run on Win XP Pro SP2. So I uninstalled everything and tried
again with Developer. In the beginning of the setup process, I get 14
successful checks, zero errors, zero warnings. When I then get into the
feature selection screen, all it shows me is "Client Components" and
"Documentation, Samples and Sample Databases".
Nowhere can I get to the server components. I've tried uninstalling,
reinstalling, with VS2005, without VS2005, but to no avail. Can anyone
help me?
Thanks!
DirkHow do you start the setup? There's both a client setup and a server setup. I don't have the DVD
here, so safest bet it to use what autorun uses.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<dcdirk@.gmail.com> wrote in message news:1131557740.758696.14810@.o13g2000cwo.googlegroups.com...
> I've been trying to install SQL 2005 on my development laptop. So far
> I've been able to install all client components, but the setup program
> never gives me the option to install the server components. I first
> tried with the Enterprise edition. I then found out that Enterprise
> doesn't run on Win XP Pro SP2. So I uninstalled everything and tried
> again with Developer. In the beginning of the setup process, I get 14
> successful checks, zero errors, zero warnings. When I then get into the
> feature selection screen, all it shows me is "Client Components" and
> "Documentation, Samples and Sample Databases".
> Nowhere can I get to the server components. I've tried uninstalling,
> reinstalling, with VS2005, without VS2005, but to no avail. Can anyone
> help me?
> Thanks!
> Dirk
>|||Hi Tibor,
I loaded the files from the downloaded ISO files (CD1 and CD2) into a
directory on my harddisk. I simply run the setup program. I did follow
your suggestion, though, and ran splash.hta, which is what would get
run through autorun. The options I have there under "Install" are: 1)
Tools, Books Online, and samples only 2) Run the SQL Native Client
Installation Wizard
SQL Native Client Install wizzard reinstalls, but still no server
components...
Dirk|||OK, it looks like I found what the problem was. I burned the ISO images
to CD instead of to the harddrive, and now the server components
actually show up during install...

Can't install SQL 2005 server components

I've been trying to install SQL 2005 on my development laptop. So far
I've been able to install all client components, but the setup program
never gives me the option to install the server components. I first
tried with the Enterprise edition. I then found out that Enterprise
doesn't run on Win XP Pro SP2. So I uninstalled everything and tried
again with Developer. In the beginning of the setup process, I get 14
successful checks, zero errors, zero warnings. When I then get into the
feature selection screen, all it shows me is "Client Components" and
"Documentation, Samples and Sample Databases".
Nowhere can I get to the server components. I've tried uninstalling,
reinstalling, with VS2005, without VS2005, but to no avail. Can anyone
help me?
Thanks!
Dirk
How do you start the setup? There's both a client setup and a server setup. I don't have the DVD
here, so safest bet it to use what autorun uses.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<dcdirk@.gmail.com> wrote in message news:1131557740.758696.14810@.o13g2000cwo.googlegro ups.com...
> I've been trying to install SQL 2005 on my development laptop. So far
> I've been able to install all client components, but the setup program
> never gives me the option to install the server components. I first
> tried with the Enterprise edition. I then found out that Enterprise
> doesn't run on Win XP Pro SP2. So I uninstalled everything and tried
> again with Developer. In the beginning of the setup process, I get 14
> successful checks, zero errors, zero warnings. When I then get into the
> feature selection screen, all it shows me is "Client Components" and
> "Documentation, Samples and Sample Databases".
> Nowhere can I get to the server components. I've tried uninstalling,
> reinstalling, with VS2005, without VS2005, but to no avail. Can anyone
> help me?
> Thanks!
> Dirk
>
|||Hi Tibor,
I loaded the files from the downloaded ISO files (CD1 and CD2) into a
directory on my harddisk. I simply run the setup program. I did follow
your suggestion, though, and ran splash.hta, which is what would get
run through autorun. The options I have there under "Install" are: 1)
Tools, Books Online, and samples only 2) Run the SQL Native Client
Installation Wizard
SQL Native Client Install wizzard reinstalls, but still no server
components...
Dirk
|||OK, it looks like I found what the problem was. I burned the ISO images
to CD instead of to the harddrive, and now the server components
actually show up during install...

Can't install SQL 2005 server components

I've been trying to install SQL 2005 on my development laptop. So far
I've been able to install all client components, but the setup program
never gives me the option to install the server components. I first
tried with the Enterprise edition. I then found out that Enterprise
doesn't run on Win XP Pro SP2. So I uninstalled everything and tried
again with Developer. In the beginning of the setup process, I get 14
successful checks, zero errors, zero warnings. When I then get into the
feature selection screen, all it shows me is "Client Components" and
"Documentation, Samples and Sample Databases".
Nowhere can I get to the server components. I've tried uninstalling,
reinstalling, with VS2005, without VS2005, but to no avail. Can anyone
help me?
Thanks!
DirkHow do you start the setup? There's both a client setup and a server setup.
I don't have the DVD
here, so safest bet it to use what autorun uses.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<dcdirk@.gmail.com> wrote in message news:1131557740.758696.14810@.o13g2000cwo.googlegroups.co
m...
> I've been trying to install SQL 2005 on my development laptop. So far
> I've been able to install all client components, but the setup program
> never gives me the option to install the server components. I first
> tried with the Enterprise edition. I then found out that Enterprise
> doesn't run on Win XP Pro SP2. So I uninstalled everything and tried
> again with Developer. In the beginning of the setup process, I get 14
> successful checks, zero errors, zero warnings. When I then get into the
> feature selection screen, all it shows me is "Client Components" and
> "Documentation, Samples and Sample Databases".
> Nowhere can I get to the server components. I've tried uninstalling,
> reinstalling, with VS2005, without VS2005, but to no avail. Can anyone
> help me?
> Thanks!
> Dirk
>|||Hi Tibor,
I loaded the files from the downloaded ISO files (CD1 and CD2) into a
directory on my harddisk. I simply run the setup program. I did follow
your suggestion, though, and ran splash.hta, which is what would get
run through autorun. The options I have there under "Install" are: 1)
Tools, Books Online, and samples only 2) Run the SQL Native Client
Installation Wizard
SQL Native Client Install wizzard reinstalls, but still no server
components...
Dirk|||OK, it looks like I found what the problem was. I burned the ISO images
to CD instead of to the harddrive, and now the server components
actually show up during install...