I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has one
physical drive divided into 5 partitions. When I choose to backup or restor
e
I can only see C and E partitions but not the D partition. All three are
NTFS partitions.
Thanks in advance.
JohnI found the problem, but don't understand why. The D partition did not have
the Everyone group define to read the drive, however other groups as well as
myself specifically have rights to it. Why does the group Everyone need to
have read in order to see it?
"John" wrote:
> I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has o
ne
> physical drive divided into 5 partitions. When I choose to backup or rest
ore
> I can only see C and E partitions but not the D partition. All three are
> NTFS partitions.
> Thanks in advance.
> John|||John wrote:
> I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has o
ne
> physical drive divided into 5 partitions. When I choose to backup or rest
ore
> I can only see C and E partitions but not the D partition. All three are
> NTFS partitions.
> Thanks in advance.
> John
Probably a permissions issue. What happens if you use the BACKUP
DATABASE command to send a backup to that volume?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||John wrote:
> I found the problem, but don't understand why. The D partition did not ha
ve
> the Everyone group define to read the drive, however other groups as well
as
> myself specifically have rights to it. Why does the group Everyone need t
o
> have read in order to see it?
>
When you run a backup, it's going to be run within the context of the
user that SQL Server is running under, NOT your personal login. Check
the service account for the SQL Server service, if that user doesn't
have rights to see the D: partition, then it's not going to show up in
your GUI.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Playing some more and comparing to a collegues setup, it appers to be the
local group system was missing.
Thanks so much for the quick responses.
"Tracy McKibben" wrote:
> John wrote:
> Probably a permissions issue. What happens if you use the BACKUP
> DATABASE command to send a backup to that volume?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
Showing posts with label partition. Show all posts
Showing posts with label partition. Show all posts
Monday, March 19, 2012
Can't see D partition
I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has one
physical drive divided into 5 partitions. When I choose to backup or restore
I can only see C and E partitions but not the D partition. All three are
NTFS partitions.
Thanks in advance.
JohnI found the problem, but don't understand why. The D partition did not have
the Everyone group define to read the drive, however other groups as well as
myself specifically have rights to it. Why does the group Everyone need to
have read in order to see it?
"John" wrote:
> I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has one
> physical drive divided into 5 partitions. When I choose to backup or restore
> I can only see C and E partitions but not the D partition. All three are
> NTFS partitions.
> Thanks in advance.
> John|||John wrote:
> I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has one
> physical drive divided into 5 partitions. When I choose to backup or restore
> I can only see C and E partitions but not the D partition. All three are
> NTFS partitions.
> Thanks in advance.
> John
Probably a permissions issue. What happens if you use the BACKUP
DATABASE command to send a backup to that volume?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||John wrote:
> I found the problem, but don't understand why. The D partition did not have
> the Everyone group define to read the drive, however other groups as well as
> myself specifically have rights to it. Why does the group Everyone need to
> have read in order to see it?
>
When you run a backup, it's going to be run within the context of the
user that SQL Server is running under, NOT your personal login. Check
the service account for the SQL Server service, if that user doesn't
have rights to see the D: partition, then it's not going to show up in
your GUI.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Playing some more and comparing to a collegues setup, it appers to be the
local group system was missing.
Thanks so much for the quick responses.
"Tracy McKibben" wrote:
> John wrote:
> > I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has one
> > physical drive divided into 5 partitions. When I choose to backup or restore
> > I can only see C and E partitions but not the D partition. All three are
> > NTFS partitions.
> >
> > Thanks in advance.
> > John
> Probably a permissions issue. What happens if you use the BACKUP
> DATABASE command to send a backup to that volume?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
physical drive divided into 5 partitions. When I choose to backup or restore
I can only see C and E partitions but not the D partition. All three are
NTFS partitions.
Thanks in advance.
JohnI found the problem, but don't understand why. The D partition did not have
the Everyone group define to read the drive, however other groups as well as
myself specifically have rights to it. Why does the group Everyone need to
have read in order to see it?
"John" wrote:
> I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has one
> physical drive divided into 5 partitions. When I choose to backup or restore
> I can only see C and E partitions but not the D partition. All three are
> NTFS partitions.
> Thanks in advance.
> John|||John wrote:
> I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has one
> physical drive divided into 5 partitions. When I choose to backup or restore
> I can only see C and E partitions but not the D partition. All three are
> NTFS partitions.
> Thanks in advance.
> John
Probably a permissions issue. What happens if you use the BACKUP
DATABASE command to send a backup to that volume?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||John wrote:
> I found the problem, but don't understand why. The D partition did not have
> the Everyone group define to read the drive, however other groups as well as
> myself specifically have rights to it. Why does the group Everyone need to
> have read in order to see it?
>
When you run a backup, it's going to be run within the context of the
user that SQL Server is running under, NOT your personal login. Check
the service account for the SQL Server service, if that user doesn't
have rights to see the D: partition, then it's not going to show up in
your GUI.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Playing some more and comparing to a collegues setup, it appers to be the
local group system was missing.
Thanks so much for the quick responses.
"Tracy McKibben" wrote:
> John wrote:
> > I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has one
> > physical drive divided into 5 partitions. When I choose to backup or restore
> > I can only see C and E partitions but not the D partition. All three are
> > NTFS partitions.
> >
> > Thanks in advance.
> > John
> Probably a permissions issue. What happens if you use the BACKUP
> DATABASE command to send a backup to that volume?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
Thursday, February 16, 2012
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
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
Friday, February 10, 2012
Can't get Reporting Services working after reinstall
I had to make room on the system partition so I uninstalled SQL 2005 Ent. and reinstalled it in a different partition, which is mounted in c:\apps. Since doing this, although MSSQL works fine, RS does not respond. During the reinstall, Setup reported that RS was "installed but not configured". I ran the RS Configuration Mgr and went through the config sequence. However, on the Initialization page, which has a red 'x' in the left panel, the local server is not listed -- the grid is empty.
__
EventID 18456: "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'." from MSSQL
The RS service is running, using the same credentials as MSSQL, the admin account .\SQLExec. It logs a normal startup in the Event Log. However, on visiting http://localhost/Reports, I get a message saying that Reporting Services is not responding. SP2 installed OK on the system, and reported that all components were upgraded.
How can I debug this installation?
Check for any other information on windows event log.
Also check under the services whether thye have been started successfully.
|||MSSQL, SSRS, SQL Agent, and IIS are running. I did see some interesting messages in the Application Log:__
EventID 18456: "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'." from MSSQL
EventID 107: "Report Server (MSSQLSERVER) cannot connect to the report server database." From Reporting Svcs.
__
I check in SQL Mgt. Studio: 'NT Authority\Network Service' is set up as a SQL login. The account is in the dbo and RSExecRole roles in the ReportServer database. In the RS Config Mgr, this account is shown as the ASP.NET Service account. The Report Server and Report Manager are both set to "Default Application Pool".
sp_who shows that the 'NT Authority\Network Service' login IS connected to the ReportServer database, along with two other connections to this db from the SQL Service account, .\SQLExec, which is used by all SQL-related services.
When I visit http://localhost/Reports, I now get the message: "Key not valid for use in specified state.
(Exception from HRESULT: 0x8009000B) (rsRPCError)". What does this mean?
One thing I recall seeing when I created the ReportServer database in the RS Configuration Mgr was a warning (yellow '!') saying it was "unable to access internal information" about the installation to verify the connection. Is this a clue?
Any advice how to proceed?|||Further searching revealed this may have to do with a crypto key left over from the prior installation, found under "C:\Documents and Settings\SQLExec\Application
Data\Microsoft\Crypto\RSA" in a file matching "1aedd7b5699f3d6a88e354100b596aae*" Advice was to delete this file and recreate it using the 'rsactivate' utility, which I cannot find. The discussion I found pertained to SSRS 2000 and not in 2005.
What's the correct way to fix this problem in Reporting Services 2005?|||Deleting the 1aedd* key file corrected the problem. I uninstalled SSRS, deleted the old RS databases, deleted the key file, reinstalled SSRS, reapplied SP2. After doing this, each step in the Reporting Svcs Config Mgr then worked correctly.
I would rate this as a serious problem with either SQL Setup or the RS Config Mgr if neither can diagnose nor correct the problem. If I hadn't stumbled across mention of the 1aedd* file on someone's blog I would not have been able to get Reporting Services to work following the reinstallation of MSSQL and its components.
Can't get Reporting Services working after reinstall
I had to make room on the system partition so I uninstalled SQL 2005 Ent. and reinstalled it in a different partition, which is mounted in c:\apps. Since doing this, although MSSQL works fine, RS does not respond. During the reinstall, Setup reported that RS was "installed but not configured". I ran the RS Configuration Mgr and went through the config sequence. However, on the Initialization page, which has a red 'x' in the left panel, the local server is not listed -- the grid is empty.
__
EventID 18456: "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'." from MSSQL
The RS service is running, using the same credentials as MSSQL, the admin account .\SQLExec. It logs a normal startup in the Event Log. However, on visiting http://localhost/Reports, I get a message saying that Reporting Services is not responding. SP2 installed OK on the system, and reported that all components were upgraded.
How can I debug this installation?
Check for any other information on windows event log.
Also check under the services whether thye have been started successfully.
|||MSSQL, SSRS, SQL Agent, and IIS are running. I did see some interesting messages in the Application Log:__
EventID 18456: "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'." from MSSQL
EventID 107: "Report Server (MSSQLSERVER) cannot connect to the report server database." From Reporting Svcs.
__
I check in SQL Mgt. Studio: 'NT Authority\Network Service' is set up as a SQL login. The account is in the dbo and RSExecRole roles in the ReportServer database. In the RS Config Mgr, this account is shown as the ASP.NET Service account. The Report Server and Report Manager are both set to "Default Application Pool".
sp_who shows that the 'NT Authority\Network Service' login IS connected to the ReportServer database, along with two other connections to this db from the SQL Service account, .\SQLExec, which is used by all SQL-related services.
When I visit http://localhost/Reports, I now get the message: "Key not valid for use in specified state.
(Exception from HRESULT: 0x8009000B) (rsRPCError)". What does this mean?
One thing I recall seeing when I created the ReportServer database in the RS Configuration Mgr was a warning (yellow '!') saying it was "unable to access internal information" about the installation to verify the connection. Is this a clue?
Any advice how to proceed?|||Further searching revealed this may have to do with a crypto key left over from the prior installation, found under "C:\Documents and Settings\SQLExec\Application
Data\Microsoft\Crypto\RSA" in a file matching "1aedd7b5699f3d6a88e354100b596aae*" Advice was to delete this file and recreate it using the 'rsactivate' utility, which I cannot find. The discussion I found pertained to SSRS 2000 and not in 2005.
What's the correct way to fix this problem in Reporting Services 2005?|||Deleting the 1aedd* key file corrected the problem. I uninstalled SSRS, deleted the old RS databases, deleted the key file, reinstalled SSRS, reapplied SP2. After doing this, each step in the Reporting Svcs Config Mgr then worked correctly.
I would rate this as a serious problem with either SQL Setup or the RS Config Mgr if neither can diagnose nor correct the problem. If I hadn't stumbled across mention of the 1aedd* file on someone's blog I would not have been able to get Reporting Services to work following the reinstallation of MSSQL and its components.
Subscribe to:
Posts (Atom)